INSTALL Windows Update Service

Content Authoring
1

(imported topic written by weberch)

When we created our corporate image a year ago, it was decided that we should remove the Windows Update service so that end users could not update I.E., java, etc. In retrospect it wasn’t the wise choice.

Now we have Win7 patches failing due to the service missing. We need to re-install the service.

The following commands will work when run at the local level (with local admin rights), but they do not work properly when run in TEM. the commands run successfully, however the service isn’t installed (due to the account that is running the command I suspect.

// register DLLS to enable Windows Update Service

wait cmd.exe /C c:\windows\SysWOW64\Regsvr32.exe /s c:\windows\SysWOW64\wuapi.dll
wait cmd.exe /C c:\windows\SysWOW64\Regsvr32.exe /s c:\windows\SysWOW64\wuaueng.dll
wait cmd.exe /C c:\windows\SysWOW64\Regsvr32.exe /s c:\windows\SysWOW64\wups.dll
wait cmd.exe /C c:\windows\SysWOW64\Regsvr32.exe /s c:\windows\SysWOW64\wups2.dll
wait cmd.exe /C c:\windows\SysWOW64\Regsvr32.exe /s c:\windows\SysWOW64\wuwebv.dll
wait cmd.exe /C c:\windows\SysWOW64\Regsvr32.exe /s c:\windows\SysWOW64\wucltux.dll

I am looking for thoughts on how to modify the action script above in order to get the service to install. (on Win7 32 and 64)

Thank you for any information you may have.

2

(imported comment written by weberch)

BUMP

3

(imported comment written by liuhoting)

On the BES Support fixlets (139 and 140) that enable and disable encryption, they register the dlls this way:

waithidden cmd.exe /C regsvr32.exe /s 
"
{parameter "cryptoFilePath"}"

Which look pretty similar to your setup.
If that doesn’t work I’d try to use appendfile and maybe create some sort of .bat or .vbs to see if it runs that way.

4

(imported comment written by weberch)

Yeah, your idea is using the same command though ‘
cmd.exe /C regsvr32.exe /s’ , and just calling out a script variable. Thanks for the idea!

What is odd is I am watching the logs, and it states the commands running successfully, yet the service is not yet there. If run local, as local admin, the commands work fine. Im running into an issue I believe that the local admin and system account that the agent uses differ in some small way.