Unresponsive Servers due to DST and an unsupported registry key

re: Unresponsive Servers due to DST and an unsupported registry key

Jeffrey S. Patton — Fri, 09 Mar 2012 22:15:51 GMT

fwiw

code.google.com/.../Check-DTSRegIssue.ps1

re: Unresponsive Servers due to DST and an unsupported registry key

Jeffrey S. Patton — Fri, 09 Mar 2012 21:45:44 GMT

@Jonathan

DOH! gigo...needs to be a built-in trim() in my copy/paste!

thanks!

re: Unresponsive Servers due to DST and an unsupported registry key

Ryan Ries — Fri, 09 Mar 2012 21:13:48 GMT

Here it is in crusty old VBScript. Just easier for me since I have lots and lots and lots of machines to check, many of them very old:

Const HKEY_LOCAL_MACHINE = &H80000002

Dim strData

Set objReg = GetObject("winmgmts:{impersonationLevel=impersonate}!\\.\root\default:StdRegProv")

objReg.GetDWORDValue HKEY_LOCAL_MACHINE,"System\CurrentControlSet\Control\TimeZoneInformation","RealTimeIsUniversal",strData

If strData Then

' Alert

End If

If isObject(objReg) Then Set objReg = Nothing

re: Unresponsive Servers due to DST and an unsupported registry key

Jonathan Stephens, MSFT — Fri, 09 Mar 2012 21:12:51 GMT

@Jeffrey

By the way, we checked the blog post itself and discovered that there was a trailing space after the registry value name above. We've corrected that.

re: Unresponsive Servers due to DST and an unsupported registry key

Jonathan Stephens, MSFT — Fri, 09 Mar 2012 21:01:45 GMT

@Jeffrey

By any chance did you create the value in the registry by cutting the value name out of the post above and pasting it into the Registry Editor? If so, double-check to see if you have a trailing space after the value name -- "RealTimeIsUniversal ".

A wild-card would catch that, but the explicit property check will return nothing.

re: Unresponsive Servers due to DST and an unsupported registry key

Jeffrey S. Patton — Fri, 09 Mar 2012 20:55:29 GMT

@Jonathan

Weird, I rebooted and tried that again and it didn't go, only after I posted how I got it did I see your post.

re: Unresponsive Servers due to DST and an unsupported registry key

Jeffrey S. Patton — Fri, 09 Mar 2012 20:54:13 GMT

Ok, for the record this works, but looks gross

jspatton@L1132C-PC01 | 14:51:48 | 03-09-2012 | C:\scripts\powershell\production #

$RegValue.PSBase.Members |Where-Object {$_.MemberType -eq 'NoteProperty'} |Where-Object {$_.Name -like 'RealTimeIsUniversal*'}

MemberType : NoteProperty

IsSettable : True

IsGettable : True

Value : 1

TypeNameOfValue : System.Int32

Name : RealTimeIsUniversal

IsInstance : True

jspatton@L1132C-PC01 | 14:51:54 | 03-09-2012 | C:\scripts\powershell\production #

($RegValue.PSBase.Members |Where-Object {$_.MemberType -eq 'NoteProperty'} |Where-Object {$_.Name -like 'RealTimeIsUniversal*'}).Value

jspatton@L1132C-PC01 | 14:52:12 | 03-09-2012 | C:\scripts\powershell\production #

Not entirely sure what the deal is, but the only way I could get it to show up at all was to use -like and tack a wildcard onto the end of the key name. This was only AFTER I had to walk through psbase.members

re: Unresponsive Servers due to DST and an unsupported registry key

Jonathan Stephens, MSFT — Fri, 09 Mar 2012 20:53:29 GMT

@Jeffrey -

There is nothing wrong with your PowerShell. When I do the same on my Windows 7 workstation, I get the following:

PS C:\> Get-ItemProperty HKLM:\SYSTEM\CurrentControlSet\Control\TimeZoneInformation

PSPath : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation

PSParentPath : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control

PSChildName : TimeZoneInformation

PSDrive : HKLM

PSProvider : Microsoft.PowerShell.Core\Registry

Bias : 300

DaylightBias : -60

DaylightName : @tzres.dll,-111

DaylightStart : {0, 0, 3, 0...}

StandardBias : 0

StandardName : @tzres.dll,-112

StandardStart : {0, 0, 11, 0...}

TimeZoneKeyName : Eastern Standard Time

DynamicDaylightTimeDisabled : 0

ActiveTimeBias : 300

RealTimeIsUniversal : 1

PS C:\> (Get-ItemProperty HKLM:SYSTEM\CurrentControlSet\Control\TimeZoneInformation).RealTimeIsUniversal

re: Unresponsive Servers due to DST and an unsupported registry key

Jeffrey S. Patton — Fri, 09 Mar 2012 20:43:08 GMT

I'm attempting to write a PowerShell script to test for the existence of this key across 30 odd servers. To test I created this key on my workstation and gave it a value of 1. But when I attempt to filter on that key I get nothing returned.

Here is the output:

jspatton@L1132C-PC01 | 14:36:17 | 03-09-2012 | C:\scripts\powershell\production #

Get-ItemProperty HKLM:\SYSTEM\CurrentControlSet\Control\TimeZoneInformation

PSPath : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SYSTEM\Curren

imeZoneInformation

PSParentPath : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SYSTEM\Curren

PSChildName : TimeZoneInformation

PSDrive : HKLM

PSProvider : Microsoft.PowerShell.Core\Registry

Bias : 360

DaylightBias : -60

DaylightName : @tzres.dll,-161

DaylightStart : {0, 0, 3, 0...}

StandardBias : 0

StandardName : @tzres.dll,-162

StandardStart : {0, 0, 11, 0...}

TimeZoneKeyName : Central Standard Time

DynamicDaylightTimeDisabled : 0

ActiveTimeBias : 360

RealTimeIsUniversal : 1

jspatton@L1132C-PC01 | 14:36:45 | 03-09-2012 | C:\scripts\powershell\production #

(Get-ItemProperty HKLM:\SYSTEM\CurrentControlSet\Control\TimeZoneInformation).RealTimeIsUniversal

jspatton@L1132C-PC01 | 14:36:57 | 03-09-2012 | C:\scripts\powershell\production #

Any thoughts would be greatly appreciated.

re: Unresponsive Servers due to DST and an unsupported registry key

LA Richards — Fri, 09 Mar 2012 18:35:54 GMT

Watching the show is about as far as my wife will let me go. Though she does enjoy the show too. Jonathan, if that was a Facebook status I would have totally "liked" it. :)