The Gears Inside My Head

In my never ending quest to rid myself of time sync issues I created the following PowerShell script.  I wrote it some time ago and can't recall if I borrowed bits so if you see what looks like your code snippets in there forgive me. The script scans the current domain using the current users credentials.  It generates an Excel spreadsheet and populates it with the names of all Windows systems it finds.  I have an exclusion to bypass anything with ESX in the name so my VMware hosts are ignored.  It then does a time comparison between the PDC and the target PC and logs the results to the spreadsheet. <#==============================================================================          File Name : Domain-Time-Validator.ps1    Original Author : Kenneth C. Mazie (kcmjr AT kcmjr DOT com)                    : ...

I haven't been able to post in a while due to the workload at work.  I though this was important enough to post in the event anyone else ran into it.  From my research dealing with the Windows time service it is something that will bite EVERYONE at one time or another.   For years I've been battling with time sync in the various domains I've managed, and it's always a nightmare. Considering that Bill Gates is the only person I've ever found that has successfully altered the flow of time, (Windows file copy dialog status bar sitting at 98% for hours...) this issue should never have been an issue. But, I think I just found the answer. Microsoft has plenty of documentation about W32TM and I cannot recall seeing this noted anywhere. I find it really hard to believe that Microsoft has never hammered all the nails in the coffin of this service.  I've read KB article after KB article, blog after blog, and never found the definitive answer to what the heck is going ...

I recently had an issue where a Windows 2012 R2 VM would hand in the middle of the night.  No clue why.  Event logs were of no help.  Our best guess is that our internal vulnerability scan made it upset.  Either way this server was a major departmental file store and if it isn't up in the morning we get hammered with tickets. I decided to create a script to manage this issue.  It uses 2 text files for input located in the samne folder as the script..  It requires the VMware PowerShell extensions.  It only works on virtual servers as written.  If the server is running but not reponding vSphere will reset it.  I have this running on a recurring 15 minute scheduled task. Param ( $Debug = $False ) #====================================================================================== #         File Name : Server-Alive.ps1 #   Original Author : Kenneth C. Mazie (kcmjr AT kcmjr.co...