If you just installed Exchange 2013 and you have an Exchange 2010 mailbox you cannot access EAC you get the old ECP management

If you just installed Exchange 2013 and you try to go to http://ServerName/ecp you’ll notice that you get the old Exchange 2010 interface and cannot manage your Exchange 2013 server.  There is a simple fix for this just simply use the following url syntax.

While installing Exchange 2013 it reports there are Exchange 2003 servers in the network when there are not

One or more servers in the existing organization are running Exchange 2000
Server or Exchange Server 2003.

Installation can’t proceed until all
Exchange 2000 or Exchange 2003 servers are removed.

If you previously upgraded from Exchange 2003 to a version before 2013 then you may not have removed Exchange 2003 or 2000 server properly.  If this is the case you can run adsiedit.msc and find the following location.
Load Configuration
services>Microsoft exchange>first organization>administrative groups>  In here find your administrative group.  Then you will see a “servers” container.  Go in there and delete any name references to your old servers that are no longer in your network.

While trying to install Exchange 2013 you receive the error message "A reboot from a previous installation is pending. Please restart the system and rerun setup.

If you receive this error it is a relatively easy fix.  Just go to regedit and find the following key and delete it.
HKLMSYSTEMCurrentControlSetControlSession ManagerPendingFileRenameOperations
Hit the retry button in setup and it will work.

How to burn a disc in Windows 7 or Windows 8 when you're not an administrator

You may notice you cannot burn a disc with your non-administrator account in Windows 7 Windows 8 or Server 2008 or Server 2012.
You will still need the administrator password but while logged in as your normal account just simply do the following.
1.  Copy your ISO to the C: drive.  It will prompt for administrator credentials.
2.  Do a search in start for CMD.  Once it finds it in your start menu right click and say “run as administrator”.
3.  Now anything you do in the command prompt will be ran with administrator privileges.
4. Run the command isoburn followed by the path to your image file.  i.e. isoburn c:MyDisc.ISO

How to fix “the trust relationship between this workstation and the primary domain failed”

If you’ve restored or “rolled back” a PC running Windows 7, Windows 8, or Vista then you may have run into this error message  “the trust relationship between this workstation and the primary domain failed”.
In order to fix this the first thing you need to do is login with a local account as opposed to a domain account.  The reason for this is simple, the server no longer trusts you so you can’t authenticate any domain users.
To do this on Windows7 for the username you will need to use .administrator or .USERNAME  (where USERNAME) is a valid local user name.  Unfortunately if you do not know these then you must use a Windows7 password reset utility first.
Once you have logged in as a local user you need to download RSAT for windows7 this will allow you to run the netdom command- http://www.microsoft.com/en-us/download/details.aspx?id=7887
Once it is downloaded you must go into the control panel to actually enable it.  Go to add remove windows components then browse to this location.
In the treeview, go to Remote Server Administration Tools -> Role Administration Tools -> AD DS and AD LDS Tools and select AD DS Tools. Click OK.
Once this is complete run the following command to reset the trust with your server
netdom.exe resetpwd /s:DomainControllerName /ud:domainDomainAdmin /pd:* 
Replace DomainControllerName with the name of a valid domain controller and replace domainDomainAdmin with your domain name and valid domain administrator account.  You are now finished.  Reboot the PC.
There is also a second method for fixing this error.  It is to login as a local administrator account remove the PC from the domain reboot and then add it back.  This will however reset your users’ profiles.

Migrating a DHCP databse for Windows Server 2003 2008 or 2012 including SBS

Migrating a DHCP database can be done with three steps.
1.  On the old DHCP server run the command netsh dhcp server export C:dhcp.txt all
2.  Copy that file to the new DHCP server.
3.  Run this command to import it netsh dhcp server import C:dhcp.txt all

How to use Powershell to transfer the FSMO roles to a Windows Server 2012

Transferring the FSMO roles to a 2012 using Powershell is relatively easy.  The command is as follows.
Move-ADDirectoryServerOperationMasterRole Identity “ServerName” OperationMasterRole 0 1 2 3 4
Also do not forget to set the tiem service on your new DC.
net stop w32time
w32tm /unregister
w32tm /register
net start w32time
net time /setsntp:
net stop w32time & net start w32time
w32tm /config /manualpeerlist:pool.ntp.org /syncfromflags:manual /reliable:yes /update
w32tm /resync /rediscover
net stop w32time & net start w32time

Once this is done use this command to verify.
w32tm /monitor

How to setup the Samsung S3 for Exchange Account

Setting up a Samsung SIII for an Exchange server can be a little tricky.  But with these steps it will help you get it done.
First you want to click on your bottom right menu button on your phone you will get a menu, select settings.
Once in settings select add account.
Now select Microsoft Exchange Activesync.
On the Exchange server settings window you will want to use the same login and password that you would use when you login to your web interface or OWA to normally check your email.  It is also the same domainusername that you use when you login to your PC.  For the Exchange server name use the name in the URL from OWA.
Click ok on this next screen.
On the next screen you can set your preferences but here is a guide.
optionsOnce you have successfully set it up you now need to look for an email icon on your phone.

Exchange 2010 how to view a users folders sizes in Powershell

If you have a user who is receiving the following message:
“The recipient’s mailbox is full and can’t accept messages now. Microsoft Exchange will not try to redeliver this message for you. Please try resending this message later, or contact the recipient directly.”
They might be asking you what is taking up so much space.  There is a simply Powershell command you can run that will generate what folders are consuming the space.
Get-MailboxFolderStatistics -id Email@domain.com | sort-object foldersize -descending | FT folderpath, foldersize, itemsinfolder -autosize
This will return something like this which you can give to the end user.
FolderPath                            FolderSize                    ItemsInFolder
———- ———- ————-
/Sent Items/Inbox                     1.793 GB (1,925,310,217 bytes)         16941
/Deletions                           1.046 GB (1,123,250,629 bytes)         10579
/Inbox                               865.8 MB (907,805,987 bytes)            7326
/Sent Items                          240.6 MB (252,339,324 bytes)            3194
/Sent Items/Deleted Items             45.5 MB (47,705,521 bytes)              672
/Recoverable Items                   8.272 MB (8,674,112 bytes)             2208
/Calendar                             5.487 MB (5,753,889 bytes)              1095
/Top of Information Store             3.216 MB (3,372,347 bytes)               38
/Drafts                              1000 KB (1,024,409 bytes)                18
/Contacts                             8.507 KB (8,711 bytes)                   20
/Deleted Items                        323 B (323 bytes)                         1
/Junk E-mail                          138 B (138 bytes)                          1
/Purges                               0 B (0 bytes)                             0
/Versions                             0 B (0 bytes)                              0
/Tasks                               0 B (0 bytes)                             0
/Journal                             0 B (0 bytes)                             0
/Conversation Action Settings         0 B (0 bytes)                             0
/Outbox                               0 B (0 bytes)                              0
/Notes                                0 B (0 bytes)                             0

iDrac in Dell Server error – Alert! iDRAC6 not responding. Power required may exceed PSU wattage.

If you receive this error – Alert! iDRAC6 not responding. Power required may exceed PSU wattage.
Try these steps to resolve it:
1.  Turn off your server and disconnect all power.  This step is important as it clears the iDrac memory!  Wait a minute or two before reapplying power.
2.  Hit Ctrl-E when the iDrac boots.
3.  The first option in the menu is “iDRAC6 LAN”.  Highlight this option then push the spacebar to select it “on”.
4.  Push ESC key save changes and exit.
1.  Download the latest version of Dell Systems Build and Update Utility(this updates the firmware for all the devices in your server)  To find the latest version go to Dell.com search drivers and downloads for “Dell Systems Build and Update Utility”  then arrange by date to see the latest version.  The current search link is – http://search.dell.com/results.aspx?c=us&l=en&s=dhs&cat=sup&cs=19&k=dell+systems+build+and+update+utility&rpp=12&p=1&subcat=dyd&rf=all&nk=f&sort=-date&ira=False&~srd=False&ipsys=False&advsrch=False&~ck=anav
2. This will give you an ISO which you need to burn to DVD.
3.  Boot your server to this DVD.  This may require changing the boot order in your server.
4. When the DVD boots select “Dell Systems Build and Update Utility”.
5.  Select firmware update.