asked on

Exchange 2013 HealthCheck

Hi, about 6 months ago my company Installed an Exchange 2013 server which is running on HyperV-2012 env't. Users and mailboxes were migrated from Exchange 2007. Since the migration the users are experiencing ongoing issues. IE. corrupted EDB file, intermittant exchange 2013 server crashing forcing a reboot, email scan failures, exchange services shut down.

I've only started with this company so I a unsure where to even begin, but any recommendations? Im thinkin - start at least with some sort of Exchange 2013 health check?...

Thanks,

Brad Bouchard

Run the Exchange BPA (Best Practicies Analyzer) and see what it returns as results. Let us know and we can help decipher if needed.

http://technet.microsoft.com/en-us/exchange/bb288481.aspx

SOLUTION

Simon Butler (Sembee)

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

ASKER CERTIFIED SOLUTION

Brad Bouchard

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Simon Butler (Sembee)

Perhaps saying it doesn't exist is too strong. It is a BETA product. Use at your own risk and it doesn't find as much stuff as the previous versions.

It also is not linked to from the link you provided, but it is linked to from Exchange 2013 SP1.

Simon.

nutekconsultant

ASKER

Thanks guys, I am off this week - but back to work next week - I will keep you all informed of my findings.

Thanks,

nutekconsultant

ASKER

Hi all, here is my update on the environment here
1. 2 HyperV Hosts - Host1 - has 2 Vms (Domain Controller and Exchange) Host 2 - 2nd Domain Controller.

Host1 - HP DL380 G8 - 48 GB RAM - ran HP diagnostics no errors, all drivers are uptodate - the VMs are using the local Disk of 3x600GB SAS drives on RAID 5
DC - Win2012 Stand. (not R2) - 4 GB RAM
Exchange 2012 Stand. (not R2)- 24 GB RAM

tests I have done:
DC -
- ran DCDIAG, all were successful
-repadmin /syncall - was successful
dns tests 0

Exchange -
-currently only has 1 C:\ 500GB, the DB is 209GB
-backups are done daily using CA Arcserve
-logs and DB in default location where Exchange was installed....
-NO Windows Updates have been done since server was brought online - July 2013!
-Exchange 2013 CU 1 with CAS role
- GetHealthreport cmdlet was run, HubTransport - State Online, AlertValue reports Unhealthy
-GetServerHealth cmdlet was run - a much more through scan i see, majority are Healthy, a few disabled and once again the HubTransport 'Messages.failed.t.. shows Unhealthy
-Symantec MailSecurity for Exchange v7.x is installed on the Exchange Server - (it is NOT launching, pending a server reboot from colleague here)
-Im unsure about the Email to Scan feauture - as Im told when its not working, they need to reboot the Exchange, then it starts working and all the held up jobs come in...

here are my thoughts on what to do next if you guys can review and provide your comments as well.
1. do windows updates
2. patch Exchange to latest version
3. create a E:\ and F:\ on Exchange Server and put Exchange Logs on E:\ and Exchange DB on F:\

nutekconsultant

ASKER

I will attempt to attach the DNS test txt file.
dns2.txt

Simon Butler (Sembee)

Exchange 2013 CU1 is no longer supported. Therefore I would start by doing the list that you have provided and then see what happens. Exchange 2013 SP1 is the current latest patch level, go straight to that.

Simon.

nutekconsultant

ASKER

is it OK to keep at Windows Server 2012, or should we be considering 2012 R2?

Simon Butler (Sembee)

You cannot upgrade the Windows OS (not supported when Exchange is installed on the server), so unless you are migrating to a new server the question isn't really valid.

Simon.

Brad Bouchard

2012 should be just fine.