System Center Configuration Manager TechCenter >
System Center Configuration Manager Forums
>
Configuration Manager Operating System Deployment
>
OSD advertisement to pcs which are running...
OSD advertisement to pcs which are running...
- Hi All,
is it possible to run an OSD Advertisement to pcs which are running ?
OSD with PXE, when the pcs are off, works fine but sometimes one or two pcs are still on and I´d like to have a OSD task sequence wich reboots the machine if running while sheduled time.
Unfortunately I found nothing realated if this is possible.
Thx in advance
Markus
Configuration:
SCCM 2007 R2
MDT 2008
Answers
- If you create a task sequence using the MDT wizard, that sequence can be advertised to a running computer, as well as being used for bare metal deployments.
When advertising the task sequence the default behavior is to backup the old machine (user state and data), apply a new image, and then restore the backup. If you don't want the backup/restore but just the apply image part, you can simply skip (disable) the backup actions... this scenario is called refresh...
To test... do this...
1. Create a virtual machine, name it say PC0001
2. Deploy your image to PC0001 (bare metal) now you have a running machine, with the ConfigMgr client on it.
3. Take a snapshot (so you can revert later if this goes wrong)
4. Create a collection in ConfigMgr, add the PC0001 computer to it, and advertise your Task Sequence to this collection, make it mandatory
5. Watch the PC0001 being reimaged (fully automated)- Marked As Answer byEric Zhang - MSFTMSFT, ModeratorWednesday, October 21, 2009 1:00 PM
All Replies
- Sure, a Task Sequence can be advertised as any other package/program. And a Task Sequence doesn't have to deploy an operating system either, it's just a general mechanism for getting flow control...
- in theory but it does´nt work... for me :-/
The first step in my tasksequence is "reboot to winPE"
Should´nt it do the trick?
I imported another MDT task sequence... the first step is like mine... what could it be ?
Configuration: SCCM 2007 R2 with MDT 2008 - Why don't you just advertise the same task sequence (refresh), if you don't want the backup part, skip it...
A refresh will stage winpe on disk, reboot and the continue the task sequence. - Unfotunately I don´t know what you mean Johan.
I have no Backup Part. I need always a clean Machine without user state migration.
What do you mean with "refresh" ?
Configuration: SCCM 2007 R2 with MDT 2008 - If you create a task sequence using the MDT wizard, that sequence can be advertised to a running computer, as well as being used for bare metal deployments.
When advertising the task sequence the default behavior is to backup the old machine (user state and data), apply a new image, and then restore the backup. If you don't want the backup/restore but just the apply image part, you can simply skip (disable) the backup actions... this scenario is called refresh...
To test... do this...
1. Create a virtual machine, name it say PC0001
2. Deploy your image to PC0001 (bare metal) now you have a running machine, with the ConfigMgr client on it.
3. Take a snapshot (so you can revert later if this goes wrong)
4. Create a collection in ConfigMgr, add the PC0001 computer to it, and advertise your Task Sequence to this collection, make it mandatory
5. Watch the PC0001 being reimaged (fully automated)- Marked As Answer byEric Zhang - MSFTMSFT, ModeratorWednesday, October 21, 2009 1:00 PM
- What logfile could help me to troubleshoot why this does´nt work in my environment?
Configuration: SCCM 2007 R2 with MDT 2008 - Well it depends, but the core logfile to look in is the smsts.log file (assuming the task sequence actually starts).
