tristard

Well try it with one (relatively new) update first, and see if it works , if it doesn't, you probably have another problem.

If you really want to install al Windows XP updates, it will most likely fail. You should try these updates one by one, and if an updates doesn't want to install you should consider installing it another way (if it's really necessary). Do not try to install all updates in the task sequence, it's just not possible, there are always updates that are making problems.

The smstslog in c:\smstslog did not change, the last date it has modified was the date that i made the image for the machine. The smstslog in C:\WINDOWS\system32\CCM\Logs says: <![LOG[successfully finalized logs to SMS client log directory from C:\WINDOWS\system32\CCM\Logs]LOG]!><time="10:23:31.092+-120" date="10-20-2009" component="OSDSetupHook" context="" type="1" thread="1488" file="tslogging.cpp:1536"> <![LOG[Cleaning up task sequencing logging configuration.]LOG]!><time="10:23:31.092+-120" date="10-20-2009" component="OSDSetupHook" context="" type="0" thread="1488" file="tslogging.cpp:578"> So not the line you are seeking for, the configmgr status says: The task sequence manager successfully completed execution of the task sequence. And when it has rebooted and shutdown it says: The SMS Advanced client was reassigned. The previous site code was "". The new site code is "XXX". So is this ok or is that missing line you are saying crucial? Edit: nevermind i looked in C:\WINDOWS\system32\CCM\Logs\smsts-20091020-102330.log and i found this <![LOG[Task sequence completed 0x00000000]LOG]!><time="10:23:27.623+-120" date="10-20-2009" component="OSDSetupHook" context="" type="1" thread="1488" file="basesetuphook.cpp:1381"> So i guess it's ok then , the line exists so it successfully completes

We have these advertisements running at night, but it's a waste of energy to let the computers on for the whole night. We do have another shutdown script that runs remotely but with this the computers will shut down almost immediately when they are done, this will save costs because we'll do this almost every night for a certain collection of pc's.

My clients already went installing the updates without configuring the GPO, so just test it out and see if it does what you want.

Your welcome , i even made the post a bit more clear so people can use this in their own envirement.

Well i figured this out myself already, so for people who want to do this, i will explain. The following files are all in: \\<distributionserver>\Package\Shutdown\ install.cmd regedit /s \\<distributionserver>\Package\Shutdown\AutoLogin.reg xcopy /s "\\<distributionserver>\Package\Shutdown\cleanup.cmd" "C:\Documents and Settings\All Users\Start Menu\Programs\Startup" Autologin.reg Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WinLogon] "DefaultUserName"="administrator" "DefaultPassword"="password" "AutoAdminlogon"="1" cleanup.cmd reg delete "HKLM\Software\Microsoft\Windows NT\CurrentVersion\WinLogon" /v DefaultPassword /f reg delete "HKLM\Software\Microsoft\Windows NT\CurrentVersion\WinLogon" /v DefaultUsername /f reg delete "HKLM\Software\Microsoft\Windows NT\CurrentVersion\WinLogon" /v AutoAdminLogon /f shutdown.exe -s Attrib -r DEL %0 EXIT I have a package with the "shutdown" folder as "data source" and i run "install.cmd" as program. In The last step of the task sequence this program will run. After that the computer reboots as usual but logs in automatically, runs a shutdown script and deletes all references (the script will be deleted out of the startup folder and the auto-login registry keys will also be deleted). The base of this script comes from some post from another forum, but it's heavily modified.

Hello, I'm struggling with this for quite some time now. When the Task Sequence is finished it always reboots the computer, i don't want it to reboot but i want it to shutdown. I already tried shut it computer down as the last task of the TS but then it hangs on the SCCM logo screen, it won't shutdown or reboot it all. I am using SCCM 2007 SP1, distributing XP and alot of software with the TS. Is there any way to let the computer shutdown after the task sequence? Thanks .

You do have to configer ip-helper in the switches for all vlans to the pxe server (if you use that), or else it can't pxe boot. Only if you use that ofcourse.