cc3 network - rebuild using windows deployment services
I am trying to reduce the rebuild times on our cc3 network.
I have set up a WDS server on our network and created a cc3 station image.
The idea i have is to skip the windows installation part on rebuilds by taking an image of the OS as a "fresh" pc and then smart client it to the network.
I also want to avoid any potential problems with the RM CC3 SP3 update/
I am aware that you can slipstreamed SP3 into the build image and rebuild PCs; unfortunately i wont have enough time to rebuild pcs.
By imaging the os i am hoping this will reduce the amount of time our machines are unavailable whilst rebuilding.
I can restore the image to a cc3 PC without any problems.
The only problem I'm having is stopping main site system packages deploying.
In the management console i have a set up a new container as i want to keep machines that are imaged separate from machines that are made using the normal cc3 rebuild method.
I have also blocked inheritance of packages yet main site system packages are still deploying to the container.
Does anyone know how to block main site system packages on a cc3 network?