One more question Doc. On a couple of machines, one NT 4.0 and one Windows 2k, I got a strange bomb out on the script. Here is a before and after for the Windows 2k section.

code:
BEFORE:
CASE @ProductType='Windows 2000 Professional'
        $KBFile='Windows2000-KB823980-x86-ENU.exe'
        IF $RPCver <> "5.00.2195.6753"
          $GetLogServer = GetLogServer()
          $IServer = $GetLogServer[0]
          $LServer = $GetLogServer[1]
          SHELL '%comspec% /c \\'+$IServer+'\'+$KBPath+'\'+$KBFile+' /u /q /z'
        ENDIF

AFTER:
CASE @ProductType='Windows 2000 Professional'
        ;$KBFile='Windows2000-KB823980-x86-ENU.exe'
        IF $RPCver <> "5.00.2195.6753"
          ;$GetLogServer = GetLogServer()
          ;$IServer = $GetLogServer[0]
          ;$LServer = $GetLogServer[1]
          SHELL '%comspec% /c \\servername\netlogon\Patches\KB823980\Windows2000-KB823980-x86-ENU.exe /u /q /z'
        ENDIF
Using kix32.exe /d //path/to/login.kix I walked through the script. When it got to the "$IServer = $GetLogServer[0]" line it went fine. The next line, however, was simply "[0]". Not sure what is happening there. Of course "[0]" is not a valid kixstart command and the script just bombed out.

By the time I got to these 2 machines, the rollout was for the most part done, so having them hit one server was no big deal. I just changed the script to hard code the path and filename. This worked fine and now that things have settled down I was just curious.

I also found out that you at least have to have SP2 for Win 2k and SP6a for NT 4.0. It is sad, but I had one of each in that state. [Frown]

Any thoughts?

BTW: This is a wonderful way to rollout "High Priority" patches. I would like to use it in the future as a template. That ok Doc?