• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Windows Update registry setting missing

Status
Not open for further replies.
S

Shambler

Supreme [H]ardness
Joined
Aug 17, 2005
Messages
6,419
Server 2003 Service Pack 2 x64

HKey Local Machine\Software\Policies\Microsoft\Windows\
as well as
Hkey Local Machine\Software\Wow6432Node\

Both sections are missing a Windows Update folder. Ideas?
 
That old OS (and XP Pro x64) used a totally different method for updates, and they were both using older versions of Windows Update as well, like v2 or v3. They're basically still useful but those Registry entries only relate to Vista and Windows 7 from what I can gather.

It's a non-issue really unless you're spending time going in and digging into the Registry poking around for things best left alone when they're actually working. ;)
 
Well, what got me started on this is:

A GPO applied to this machine should be setting ServerA@DomainA.lol as the WSUS server.

SCCM WUAHandler.log shows:
Unable to read existing Policy. Policy overwritten. (blah blah blah)

WindowsUpdate.log shows ServerB@DomainA.lol as the WSUS server.

I'm trying to track down where the ServerB policy is coming from.

Looking in gpedit on the machine, the GPO looks like it is coming into play. It shows the server I want. Next step for me was to check the registry and that is where the above issue came into play.
 
Checked a functioning Server 2003 SP2 x64 Standard.

The functioning server has the appropriate entries which match the Local Policy and GPO.

Still confused.
 
rops.msc should be able to help you identify which policies are getting applied and which are not.
 
RSOP
Computer Configuration: Admin Templates: Windows components
No Windows Update entry listed.

It threw an error that it cannot find a few ADM files in \\Domain\SYSVOL\Policies\{hashblahblah}\ADM. There are 3 that are missing. However, the wuau.adm file is there. I do not see any entries for either server in the wuau.adm file. Keep in mind, I'm not exactly sure how adm files work and/or how they are modified and used by the system.
 
When I check the properties of the Computer Configuration and view Error Information: The machine is unable to create reg key InProcServer32 as well as access the registry.pol file.

The pol file has local administrators and the System account as having full control.

Ran RSOP on another server, same OS and similar function, no issues reported.

I blame SAP. :(


Also, the mother freaking registry.pol file lists the server I want this machine to look to for WSUS. Mother fudge rage! Wonder if I should just manually create the damn reg keys as the Pol file, GPO, and Local Policy all have exactly what I want. Still unsure as to why the WindowsUpdate.log is looking for some phantom server.
 
Simplified:
SAPServer's WindowsUpdate log is pointing to a WSUS server that does not exist. The registry.pol, GPO, and local policy all show the server I want to point to.

I'm not sure where to check next for this phantom server entry in this SAPServer's Windows Update log.
 
Locking thread.
Stopped AU service
Renamed Windows Update log
Started AU service
New Windows Update log file was created. Looking... decent so far.

WUAHandler.log is still throwing errors regarding policy. I still blame SAP.
 
Status
Not open for further replies.
Back
Top