Windows Update problems after a re-image.
albion last edited by
I basically use fog as a workstation backup solution. After I install a PC, updates and software for a user I use fog to take an image of that machine. One problem that I see reoccuring after a re-image is a failure to run Windows Updates. Is there something I need to do before I try to run Windows updates on the re-imaged machine?
albion last edited by
@george1421 Even though the machine “seems” to be connected to the domain after reimage, I always remove and readd the machine to the domain.
On my current “problem” I had to use the manual complete reset method to get Windows Update working again. And I’m still not sure because it’s “Checking for Updates” on 2 years worth of updates.
@Wayne-Workman: Fog version 1.2.0. Linux CentOS 6.7 server, Windows 7 SP1 Workstation clients.
@MRCUR: I am using WSUS. But, points at george1421. Each Workstation image will only be restored to that Workstation with a new same model hard drive. The impression I always got was that sysprep wasn’t necessary in my case.
@MRCUR I read what the OP is doing is using FOG to create a DR backup of the target system.
That is where I wanted to confirm same image to same hardware (which could be misunderstood as a one to many of the same model.). I meant make an image of computer A and if computer A fails that image would be restored to that same computer (computer A). If this is the case then sysprep is not needed. I can see AD being an issue, requiring the AD computer account to be reset since the system password would no longer match.
If you’re using WSUS, you should be running a sysprep generalize (at a minimum) before capturing the image. Otherwise you’ll have conflicting computer ID’s in WSUS.
Fog version? Windows version?
Is this the original image to the original hardware?
When you reimage the machine, does it connect to AD OK?
It would be interesting to see what happens if you stop the windows update service, and bits service and then delete the c:\windows\software update folder. Then restart the windows update service. See if that resync’s your windows updates.