mizkitty

Just curious if it makes any difference what the time stamp is on the files in my un-attended builds. I've just noticed that the .cmd I've used to make all my SP2 un-attended ISO's is set for a time stamp of Dec. 31/2002. Am I going to run into problems later with the SP2 files having earlier dates? Should I reset everything to an Aug. 4/2004? Anyone know what the timestamps are in the "official" integrated SP2 builds from Microsoft?

Found a solution...added this to my regtweaks file: ;Manage Automatic Windows Updates [HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\WindowsUpdate\AU] "NoAutoUpdate"=dword:00000000 "AUOptions"=dword:00000004 "ScheduledInstallDay"=dword:00000000 "ScheduledInstallTime"=dword:00000003 Enables Autoupdates, with installs @ 3AM. It also greys out the options on the security panel so the customer can't turn it off. B)

If you're talking about skipping the "Welcome to Windows" screens where you have to enter at least one user name...this is taken care of in winnt.sif with the line: [unattended] UnattendSwitch="yes" You'll end up with only the Admin account.

Tried both...the updated ref.chm for SP2 Deployment Tools also lists both. The "Help Protect Your PC" page is skipped during install, but the "automatic updates" isn't enabled when I check it later.

Thanks for the quick reply...but it was happening even before I added a regtweaks file. Is there something I can add to "regtweaks" to enable it?

adding this to your winnt.sif should work: [shell] DefaultStartPanelOff=Yes

I think he wanted to know how... B)

I don't get any warnings or setup screens during install...everything runs fine with no user input. But when I check Security Center after install is finished...the "automatic updates" needs to be enabled manually. I've got this line already in my winnt.sif: [Data] AutomaticUpdates=yes Is there another entry or reg. setting I can add so the end user doesn't have to enable "automatic updates"?

I slipstreamed SP2 into SP1 myself today (not sp1a) VM doesn't show up in Windows Update after installing. Weird thing though, I also did a fresh install of SP1 no updates, then added SP2 seperately just to test the upgrade process. When I rebooted that machine, the first thing it did on its own was update the VM.

I used "update.exe -s" Worked fine for me.