Restart behavior for Patching through SCCM 2007 SUP

I am not sure how i can assign restart settings for servers/workstations

We  are moving the patches into sccm 2007 and want to make sure the Workstations or some servers do not restart without user interaction.

I tested sending patches to some test machines and they all rebooted immediately after patches.

I want to make sure users get a prompt for reboot after patching on workstations/LOB machines  and it is upto them to decide when to reboot.

But then make sure that if they do not reboot in 1 week a forced reboot is initiated by sccm after notifying the users a couple of times.

Can i achieve this with SCCM 2007 SUP

no, you can either force restart or suppress restart once patches installed after deadline but can't control time of the same... alternatively you may try to set collection specific restart setting where you are deploying patches & set restart countdown to higher one after that system will reboot automatically

You have the default restart behavior, the collection control but you still only have a strict restart countdown.

What you will need to do is similar to what we did, create you own programmable tool that uses the registry to detect if a restart is required.  Then give the use the option to restart.  Update the registry with the flag and the date/time.  Then keep showing it to them (Scheduled task or Advertisement) when they fail to do this before the deadline then you can create a program the does nothing and set to ConfigMgr restarts machine. Then they will get the standard restart schedule (or different one if you have collection settings or Maintenance Windows) the time will hit zero and the reboot will occur.

Theres 2 things you could do here 

1) As recommended by Prashant you could either set the default computer client agent restart countdown timer (minutes) to a higher number so users have alot more time before the reboot happens or modify the collection specific restart setting so only specific machines you place in that collection have this setting. So really you could set this to hours if you wanted to. For example if you deploy patches to install at 3pm then set the countdown timer to be over the time ppl finish work and would shut there machines down. ie 180 minutes (equates to 3 hours so reboot would happen after 6pm)

2) The other suggestion is to a have separate deployment for these machines which you place in a collection. On the deployment, schedule the start time for say today and then the deadline date in 1 week. This will give the users one weeks grace period (or whatever time period you decide) to install the patches at a time convenient to them.

Suki