Over the past couple weeks the Exchange team has been implementing a side-by-side install of Exchange 2013 with Exchange 2007. To my knowledge they haven't ran into any major issues. After they had their first 2013 server up however we had a DC reboot in the middle of the day. Throwing .. "A critical system process, c:\windows\system32\lsass.exe, failed with status code 255. The machine must now be restarted". We troubleshot and installed a few patches including KB2732595. No reboots for a few days. Then, in the middle of the day 2-3 DC's rebooted. The Exchange team had added 2 more CAS and Mailbox servers. We searched logs on the DC's with nothing obvious anywhere. So we continue to troubleshoot but nothing "obviously" points to the Exchange 2013 servers.
Last night, the Exchange team configured their DAG's and last CAS servers and throughout the night we had the same DC rebooting every 1-2 hours like clockwork. You would be RDP'd into the DC, nothing going on then error, computer shutting down with the above mentioned error. During the day 3-4x other DC's were rebooting every 2-3 hours. Fortunely it was a day off for most employees so we troubleshot internally without calling Microsoft. After several hours of reboots (again with nothing specifically pointing to Exchange 2013), we opt'd to shutdown all Exchange 2013 CAS and backend servers, reboots of the DC's immediately stopped. We're going into this weekend crossing our fingers with the intention of calling Microsoft support monday first thing.
I've searched quite a few forums and keep hitting old KB's or posts regarding Exchange 2010 etc. All KB's mentioned for Windows 2008 R2 are applied (unless I missed something obvious).
Note: Exchange 2013 servers are Windows 2012. DC's are Windows 2008 R2 SP1.
Any ideas between now and when I place the call with Microsoft ?