Weird, if I do it manually (and reboot)...it works straightaway.
that says to me that the batch file didnt execute properly. make sure you are running the file as an admin. try logging in as local admin and running just the part of the batch file to delete the reg keys.
Will have to log them all on and try it manually in one fell swoop, I think. Got 2 of 3 appearing now, but they rotate depending on which order I log on. Will report back shortly!
EDIT: Sorry Ad, didn't see your post. I was running the batch file as a network admin, which should also be local admin, will try just logging on locally first.
OK Finally got all 16 Suite machines showing!
I had to log on locally, then manually stop the auto update service, delete the two reg keys, restart the update service, reboot and voila!
Glad its working now.
Ok next step...!
WSUS is set to sync at 3am, and that seems to be working fine. The GPO setting is that computers download and schedule updates for 12pm, although
a) it doesn't seem to be doing anything, as you still have to 'install updates and shut down',
and b) windowsupdate.log states that after logon, the AU schedule is set to Friday at 3pm...when you go into the windows update settings locally, it does indeed state Friday 3pm, but these options are greyed out, as you might expect.
a) there is an option within GP to download and install. The first option within the GP is "Do not display 'download and install' option in shut down... , You will want to check the Allow immediate installation of updates too.
b) if you have set the group policy to download updates at a certain time, then if you try to change it locally, you wont be able to. Check the policy to make sure that the time you want is correct.
Have you changed the time recently? run a gpupdate /force and check again.
That's the policy settings at the moment, the auto updates is set to option 4 at 12pm.
I guess the thing that is confusing me is that I'm not sure whether it should be installing quietly in the background, and waiting for any restart to be done by the user, or whether it just does everything it needs to after selecting 'shut down and install updates'
are the updates being installed?? if you look in the WSUS console it will give you a couple of pie charts to give you that info.
Sorry, been caught up with a couple of other things today, so not had much time to have a look.
Just popped on though, and last night's synchronisation downloaded 6 new updates, but they all still show as 'needed', and 12pm has been and gone!
Interesting side note, the 30 netbooks we have, which were also cloned machines, have now shown up successfully, without me having to do any messing about with SIDs.
Well I've left WSUS alone for a few days, and although it is syncing and what not, I'm still not wholly convinced it's actually doing updates at 11am. One of the client machines has this in the logs, still:
2011-01-28 09:09:27:392 1216 144 Agent * WSUS server: http://GATEWAY
2011-01-28 09:09:27:392 1216 144 Agent * WSUS status server: http://GATEWAY
2011-01-28 09:09:27:392 1216 144 Agent * Target group: ICT Suite
2011-01-28 09:09:27:392 1216 144 Agent * Windows Update access disabled: No
2011-01-28 09:09:27:436 1216 144 DnldMgr Download manager restoring 0 downloads
2011-01-28 09:09:27:526 1216 144 AU ########### AU: Initializing Automatic Updates ###########
2011-01-28 09:09:27:526 1216 144 AU AU setting next detection timeout to 2011-01-28 09:09:27
2011-01-28 09:09:27:526 1216 144 AU AU setting next sqm report timeout to 2011-01-28 09:09:27
2011-01-28 09:09:27:526 1216 144 AU # WSUS server: http://GATEWAY
2011-01-28 09:09:27:526 1216 144 AU # Detection frequency: 18
2011-01-28 09:09:27:526 1216 144 AU # Target group: ICT Suite
2011-01-28 09:09:27:548 1216 144 AU # Approval type: Scheduled (Policy)
2011-01-28 09:09:27:548 1216 144 AU # Scheduled install day/time: Friday at 15:00
2011-01-28 09:09:27:548 1216 144 AU # Auto-install minor updates: Yes (Policy)
So it is still insisting on Friday 3pm...
what if you try removing the time schedule policy. gpupdate /force. change the time locally. reinstate policy.see if the time changes back to Friday at 3pm.
Save yourself the effort of running commands on lots of different machines - use psexec from the excellent pstools collection (free).
\pstools\psexec -u administrator -p xxx %1 gpupdate /force /boot /target:computer
Runs gpupdate on machine %1 (stick admin password where xxx is).
For a roomfull, list the machine names in machines.txt and run
\psexec -u administrator -p xxx @machines.txt gpupdate /force /boot /target:computer
There are currently 1 users browsing this thread. (0 members and 1 guests)