{"id":2830,"date":"2014-08-27T18:48:25","date_gmt":"2014-08-28T01:48:25","guid":{"rendered":"http:\/\/www.brainlitter.com\/?p=2830"},"modified":"2014-08-27T18:48:25","modified_gmt":"2014-08-28T01:48:25","slug":"i-want-the-blues-die-event-id-1111-die","status":"publish","type":"post","link":"https:\/\/regroove.ca\/brainlitter\/2014\/08\/27\/i-want-the-blues-die-event-id-1111-die\/","title":{"rendered":"I want the blues – Die Event ID 1111 Die!"},"content":{"rendered":"

What<\/h2>\n

I’ve written about this before, in regards to having clear (anal retentive much?) event logs and the technique was different in Windows Server 2008 R2 and earlier<\/a>. I just can’t stand having to ignore a bunch of red critical errors, especially when they aren’t critical – and more importantly, I don’t think people should learn to ignore the red – Never Cry Wolf and all that, you know?<\/p>\n

The technique in Windows Server 2012 is a little different (well, okay, this was supported in 2008 R2 as well but we just never did it that way typically I suppose\u2026)<\/p>\n

<\/p>\n

So What<\/h2>\n

Red\/Critical Event ID 1111’s like the below are laziness and cause us to waste time sifting through them while we get to real\/current\/valid errors. These errors exist because Terminal Services\/Remote Desktop wants to try and map our local printers for us, when we connect to the server. This is desired if it were a full blown\/proper terminal server but for the rest of us (And us SharePoint admins), we use Remote Desktop Connection (RDP) to “manage” our servers.<\/p>\n

If you, like me, never plan on having anyone map their printers when simply managing a server, there are a few ways you can avoid the errors\u2026<\/p>\n

 <\/p>\n

\"clip_image001\"<\/a><\/p>\n

 <\/p>\n

Error Text is typically something like “Event ID 1111” and “Driver X required for printer Y is unknown. Contact the administrator to install the driver before you log in again”.<\/p>\n

Now What<\/h2>\n

Option 1<\/h3>\n

When establishing your Remote Desktop Connection with the client Software (MSTSC.EXE), you could disable “client redirection” before you connect, like so:<\/p>\n

\"clip_image002\"<\/a><\/p>\n

 <\/p>\n

Meh, there are a few reasons why this isn’t ideal\u2026<\/p>\n

    \n
  1. If you forget to do this, from some machine you connect from, your red errors come back<\/li>\n
  2. No central control of this problem, you have to communicate this to everyone and have them remember to do it<\/li>\n<\/ol>\n

     <\/p>\n

    Option 2 (and 3)<\/h3>\n

    The other option is group policy. The reason I say options 2 and 3 is that you can either do this locally on the server or distributed via Group Policy Management in Active Directory to a number of servers at once (except for your real terminal servers folks!).<\/p>\n

    Here’s how\u2026<\/p>\n