This is EventID 1111 on a Windows Server 2012 server. Opening up the system event log, we are greeted with the below errors: Let’s look at manually getting rid of the errors, and then using Group Policy to effectively manage multiple servers. Since our venerable friend, Windows Server 2003, is going to exit extended support in a little over a year, I’ve based this post on a Server 2012 R2 box, but the principles still hold true for our trusty friend! As you would expect, this is fluff that I just do not want to see. Opening up the system event log on numerous customer’s servers I’m pretty much guaranteed to see errors related to mapping printer drivers in the Terminal Services/Remote Desktop session. That is there should be no errors as that indicates something is not quite right and should be addressed. After doing Exchange Risk Assessment ( ExRAP) and Exchange Risk Assessment As A Service for almost four years, one thing continues to irritate my OCD personality! When I look at the event logs on an Exchange server, the logs should be a sea of blue.
0 Comments
Leave a Reply. |