cc3 network - rebuild using windows deployment services

[sandeep2504]

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?

[webman]

On our CC3 network, an RM Restore image is taken just after Windows is installed but before packages are installed. Can you not just restore workstations to this image to get the same effect?

[circlestech]

What does RM use to restore machines I didn't think it was WDS?

[sandeep2504]

yeah i wanted to use wds so i can use updated drivers when i want rather than waiting for RM to release their hardware support packs.

 

I also wanted to integrate software that involves a manual installation or involves a member of ict support having to login into individual pcs such installing scanner drivers.

[synaesthesia]

If you've mostly got the same machines, how about setting up vanilla windows XP SP3 on one, carrying out the pre-requisites for a CC3 slipstream install and starting the process. Turn it off when it does the restart, take the image from there. So when that deploys out to your stations via the normal WDS method, all you have to do is potter up to it, slap in the relevant domain, password and CC3 location details and away it goes - pretty much straight to the package installation state after a few minutes of CC3isation.

[sandeep2504]

I got this working yesterday.

 

The location in the management console was corrupt; that's why packages were not allocating.

[webman]

sandeep2504: Re Drivers - just import them into the build area using RM Build Manager?