Monday 23 August 2010

AD Group policy editor - Client

gpedit.msc

refresh

Handy Shortcuts

http://mypchell.com/guides/34-guides/69-156-useful-run-commands

WSUS Log

%systemroot%\SoftwareDistribution\ReportingEvents.log

Force client PC to check in with WSUS

wuauclt.exe /detectnow

W32Time (Windows Time Service)

command line

w32tm /config /computer:BHLHRDC.ad.bhworldwide.com /manualpeerilst:time.windows.com /syncfromflags:manual /update

Stop/Start service
net stop w32time && net start w32time

Thursday 12 August 2010

Event ID 56, TermDD

"The Terminal Server security layer detected an error in the protocol stream and has disconnected the client."

http://blogs.technet.com/b/askperf/archive/2010/03/25/the-curious-case-of-event-id-56-with-source-termdd.aspx


To decipher the codes, you can download Err.exe from:
http://www.microsoft.com/downloads/details.aspx?familyid=be596899-7bb8-4208-b7fc-09e02a13696c&displaylang=en

113996 INFO: Mapping NT Status Error Codes to Win32 Error Codes
http://support.microsoft.com/default.aspx?scid=kb;EN-US;113996

From command prompt navigate to the downloaded/extracted err.exe

Just open the event in event viewer and copy the Binary Data "in words"

for example:  output for "err 0032000AD0"






Windows 2008 - Terminal Server - Investigate Locked sessions

One BIG reason why a session is locked is that it don't unload the profile correctly when the user disconnects. The reason for profile not being released is that the user Registry hive has to be closed (and saved as NTUSER.DAT, BTW), but the server updates it at logoff.

Logged sessions will be logged as (UserEnv) events in the Windows logs on the Terminal Server

Wednesday 11 August 2010