I have a "non offcial" hotfix from Microsoft that is not part of Windows
Update so doesn't get syncronized with WSUS. Is there a (easy) way to add it
to WSUS?
If it's not possible or very complicated what is the best way to deploy the
hotfix?
Any thoughts is very appreciated.
> I have a "non offcial" hotfix from Microsoft that is not part
> of Windows Update so doesn't get syncronized with WSUS. Is
> there a (easy) way to add it to WSUS?
Sorry, not possible.
> If it's not possible or very complicated what is the best way
> to deploy the hotfix?
Is the computers in an Active Directory domain?
If the computers are not in AD, do you run a logon script (NT4,
Netware)?
--
torgeir, Microsoft MVP Scripting, Porsgrunn Norway
Administration scripting examples and an ONLINE version of
the 1328 page Scripting Guide:
http://www.microsoft.com/technet/scriptcenter/default.mspx
Yes I have a Active Directory Domain (WinSrv2003) and all workstations run
WinXP. They all run a vbs logon script.
"Torgeir Bakken (MVP)" <Torgeir.B...@hydro.com> skrev i meddelandet
news:OKhmv5DR...@tk2msftngp13.phx.gbl...
> Hi!
>
> Yes I have a Active Directory Domain (WinSrv2003) and all
> workstations run WinXP. They all run a vbs logon script.
Hi,
As you have AD , you should do it in a computer startup script (with a
GPO that is applied to you computers) instead of a logon script. A
computer startup script runs as part of the boot up process (before the
user logs in). It runs under the system context and has local admin
rights.
As you need to access a file over the network from the computer
startup script, you need to put the file on a network share and
grant read access for the AD group "Domain Computers" to the share.
Below is a VBScript you can put in a computer startup script that will
install a MS update.
Note that the script creates a registry marker when the update is
installed, so the next time the script is run, it sees this marker, and
skips the installation of the update (to avoid repeating installations).
You will need to change the path to the exe file (I have used a dummy
path in the script), and maybe the command line switches for the
update.
I have added the command line switches /u /q /z to the command line in
the script, it should work on all MS updates that uses update.exe to
install (most do).
/u: Unattended mode.
/q: Quiet mode (no user interaction).
/z: Do not restart when installation is complete.
If you want the computer to automatically reboot after the install (if
the update needs it), remove the /z switch.
Script code:
'--------------------8<----------------------
sExePath = "\\server\share\folder\something.exe"
sSwitches = "/u /q /z"
Set oShell = CreateObject("WScript.Shell")
sRegKey = "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate"
' suppress error in case values does not exist
On Error Resume Next
' check for marker
sRegMarkerValue = "" ' init value
sRegMarkerValue = oShell.RegRead( sRegKey & "\Hotfix1Installed")
On Error Goto 0
' to be sure update is installed only once, test on marker
If sRegMarkerValue <> "yes" Then
oShell.Run Chr(34) & sExePath & Chr(34) & " " & sSwitches, 1, True
' create marker
oShell.RegWrite sRegKey & "\Hotfix1Installed", "yes"
End If
'--------------------8<----------------------
WSH 5.6 documentation (local help file) can be downloaded from here
if you haven't got it already:
http://msdn.microsoft.com/downloads/list/webdev.asp
/Ulrik
"Torgeir Bakken (MVP)" <Torgeir.B...@hydro.com> skrev i meddelandet
news:%23y9Q$$FRGHA...@tk2msftngp13.phx.gbl...