SMS 2003 remote OS deployment
Hi all
Running SMS 2003 SP3 over here and using OSD feature pack and MDT 2008 to deploy an Windows XP Pro image (WinPE booted via PXE/WDS). All works fine but within a year we'll have to restage all clients with an update image, preferably remotely without the need of a local technician or user hitting F12 to initiate a network boot.
Are there within the current setup (SMS, ZTI deployment using BDD 2007...) any possibilities to initiate the deployment of an image remotely?
Running SMS 2003 SP3 over here and using OSD feature pack and MDT 2008 to deploy an Windows XP Pro image (WinPE booted via PXE/WDS). All works fine but within a year we'll have to restage all clients with an update image, preferably remotely without the need of a local technician or user hitting F12 to initiate a network boot.
Are there within the current setup (SMS, ZTI deployment using BDD 2007...) any possibilities to initiate the deployment of an image remotely?
0 Comments
[ + ] Show comments
Answers (7)
Please log in to answer
Posted by:
renio
15 years ago
An advertisement of the operating system deployment package...? Will that suffice for booting the clients into WinPE and running the task sequence?
Posted by:
aleinss
15 years ago
Yes, you can push images via advertisements. I upgraded our XP kiosks to Vista that way.
SMS/SCCM will pull down WinPE onto the hard drive, reboot the PC and on first boot, loads WinPE instead of your regular operating system.
SMS/SCCM will pull down WinPE onto the hard drive, reboot the PC and on first boot, loads WinPE instead of your regular operating system.
Posted by:
renio
15 years ago
Does that mean SMS 2003 is capable of pushing a WinPE boot partition towards the remote client?
Note that the boot order of our desktops/notebooks are set to hard disk first and not network controller...
I feel like I'm asking noob-questions here... it's been a few years that I've worked with SMS 2003 and never had the chance to play with OSD in it. I know how it works with SCCM but I believed remote OSD deployment with SMS 2003 isn't possible out of the box...
Note that the boot order of our desktops/notebooks are set to hard disk first and not network controller...
I feel like I'm asking noob-questions here... it's been a few years that I've worked with SMS 2003 and never had the chance to play with OSD in it. I know how it works with SCCM but I believed remote OSD deployment with SMS 2003 isn't possible out of the box...
Posted by:
revizor
15 years ago
Does that mean SMS 2003 is capable of pushing a WinPE boot partition towards the remote client?
Think Two installations of Windows on the same PC - boot.ini tells you which one is the default one. During first reboot, WinPE files load and do their dirty job...
Posted by:
renio
15 years ago
and how should the system (partition-wise) be prepped with WinPE??
I must be missing something.. but I don't see how an SMS (2003) package can install WinPE next to the running XP OS.
I must be missing something.. but I don't see how an SMS (2003) package can install WinPE next to the running XP OS.
Posted by:
revizor
15 years ago
It just does... [:D]
Renio, you are overthinking - just set it up and run once, and everything will become apparent...
OSD package takes care of the WinPE download, boot.ini modification and the sequence of steps required to (re)install OS on a PC.
Renio, you are overthinking - just set it up and run once, and everything will become apparent...
OSD package takes care of the WinPE download, boot.ini modification and the sequence of steps required to (re)install OS on a PC.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.