http://www.windowsitpro.com/authors/author/author/5301237/rsscomment/5301237en-USSun, 27 May 2012 06:12:59 GMTSun, 27 May 2012 06:12:59 GMThttp://www.windowsitpro.com/article/scripting/event-log-scanner#commentsAnchorWed, 29 Sep 2010 11:23:03 GMT
While SCHELLENGER makes a valid point on the age and condition of XP, it’s still going to be with us for a long time to come. Over 95% of my customers are running XP and most will probably only move to 7 through attrition. This is an EXCELLENT tool to add to my diagnostic arsenal.]]>LORENTZENWed, 29 Sep 2010 11:23:03 GMThttp://www.windowsitpro.com/article/scripting/event-log-scanner#commentsAnchorhttp://www.windowsitpro.com/article/scripting/event-log-scanner#commentsAnchorTue, 28 Sep 2010 15:56:08 GMT
Here we are well into Windows 7 and you are still providing scripts that run as-is for XP. It seems to me that to ecourage the move away from the nearly obsolete, security vulnerable XP you would be offering script that run well as-is on Windows 7, but can be modified to run on earlier OS versions.]]>SCHELLENGERTue, 28 Sep 2010 15:56:08 GMThttp://www.windowsitpro.com/article/scripting/event-log-scanner#commentsAnchorhttp://www.windowsitpro.com/article/tips/get-updates-on-microsoft-updates#commentsAnchorThu, 10 Dec 2009 08:03:34 GMT
You can improve the reliability of the script by replacing: "\c$\Windows" with: "\admin$" in the second line of the "CheckUpdates" subroutine. The Admin$ hidden share is created by Windows (NT 4.0 and newer) during installation and always points to the Windows installation directory, so it will be valid even if Windows is installed in a directory other than C:\Windows. It will also be valid on a Windows 2000 computer where the default installation directory is C:\WinNT.]]>JIMThu, 10 Dec 2009 08:03:34 GMThttp://www.windowsitpro.com/article/tips/get-updates-on-microsoft-updates#commentsAnchorhttp://www.windowsitpro.com/article/tips/get-updates-on-microsoft-updates#commentsAnchorWed, 02 Dec 2009 10:59:51 GMT
Hi I ran the script and the csv was created - all PC’s came back as "OFF LINE", including my own PC. This was run as domain account that has admin privileges on all the machines. Any ideas? cheers Ian]]>IanWed, 02 Dec 2009 10:59:51 GMThttp://www.windowsitpro.com/article/tips/get-updates-on-microsoft-updates#commentsAnchorhttp://www.windowsitpro.com/article/tips/get-updates-on-microsoft-updates#commentsAnchorTue, 01 Dec 2009 18:33:13 GMT
The code has a bug on the following line: Set objFolder = objFSO.GetFolder("\\" & strComputer & "\c$\Windows") This assumes that windows has been installed into c:\windows (not the case where I’m currently working) - it should instead use the %systemroot% environment variable.]]>DuncanTue, 01 Dec 2009 18:33:13 GMThttp://www.windowsitpro.com/article/tips/get-updates-on-microsoft-updates#commentsAnchorhttp://www.windowsitpro.com/article/tips/get-updates-on-microsoft-updates#commentsAnchorTue, 01 Dec 2009 17:43:15 GMT
Hmmm. If your company uses WSUS [or some of the equivalents], it keeps track of updates that have and have not been installed [and I don’t think a worm can trick it]. So this script is unnecessary - unless you want a second opinion.]]>EdTue, 01 Dec 2009 17:43:15 GMThttp://www.windowsitpro.com/article/tips/get-updates-on-microsoft-updates#commentsAnchor