[SOLVED] enterprise IT

Issue: Content index errors may prevent you from performing DAG Database switchovers:  "Error: An error occured while trying to validate the specified database copy for possible activation. Error: Database copy on server has content index catalog files in the following state: 'Failed'" Resolution: The following Exchange Management Shell commands can be used to troubleshoot failed or corrupt DAG Database Content Index.  These commands will identify and re-build/re-seed any  bad content indexes Read more [...]

Simplified process: 1) Copy the Exchange 2010 SP3 media to the hard drive of your Exchange server(s) 2) Right click the setup.exe and click ‘run-as-administrator’ 3) Proceed through the upgrade process and reboot the server at the end Note: I recommend upgrading servers one at a time. More complex environments:  If you are upgrading an Exchange 2010 DAG to SP3 you can follow these steps for installing Exchange Service Packs and Rollups on DAG Members.  If you have servers with Read more [...]

Care needs to be taken when rebooting Exchange DAG Members.  Rebooting an Exchange server that is in a DAG requires switching the active database to the member not being rebooted. 0) Check that all DB's are healthy and check which servers is currently the active server.  Run the following from Exchange Management Shell: Get-MailboxDatabaseCopyStatus * -- At this point if you find there is an Exchange server with no active databases, it is considered a Passive DAG Member and you can reboot Read more [...]

Issues: email is backing up in the Exchange Submission Queue and the following errors are displayed in Queue Viewer: 432 4.3.2 storedriver component has been retired 432 4.3.2 STOREDRV.Deliver; mailbox database thread limit exceeded Processor is also pegged at 100% or close to it on the hub transport server Potential causes of this issue for others but were not the cause in my cause: -exceeded mailbox size quotas on the database, especially a journal mailbox / database -under-powered Hub Read more [...]

Issue: While installing Exchange 2010 SP3 you get the error "IIS 6 WMI Compatibility component is required" Cause: Exchange 2010 SP3 requires additional IIS pre-requisites that were not required by previous versions of Exchange 2010.  Note: if this is a new Exchange 2010 installation make sure you install all of the Exchange 2010 pre-requisites. Solution: Add the IIS 6 WMI Compatibility role feature 1) open Server Manager 2) click Roles > scroll down to "Web Server (IIS)" > click Read more [...]