Blightster

Thanks Lucid, your help has been fantastic!

Hi Lucid Thanks for your reply I think i have somehow worked it out in my head?? What i am going to try is the following. Create collections in SCCM based on OU so it drags in those machines. Set an deployment advertisement for that OS of the room for example and use the OSDComputername varible to set the PC name and not set the task as mandatory so our Techs can boot into PE and see what they are installing and thenn enter the PC name. I'll also set that advertisement to place the PC in the OU concerned and then copy that process. I like the your idea of the techie being able to select the OU the PC will reside in, could you please point me to some resources to set that up, i could then add that to the things the Techie needs to do. What does HTA mean? sorry for such a noob question! Again thank you very much for your help!!

Hi, Please bear with me as although i setup our SCCM and configured it all so far we are only using it for Application Deployment. I am only just starting to try and unearth the OS Deployment side of it! I'm woundering if someone can help me? Sorry its a bit long winded! Our current setup we have used for a few years and im looking to expand our use of SCCM more and more. Currently we have a WINPE environment, if we need to rebuild a PC or a whole suite of PC's we simply PXE boot each of them into our PE enviornment, her we have a GUI where we can stipulate a few items PC Name PC Model Screen Resolution (2 predefined and a a custom res option) We enter the Name of the client, select the PC model, resolution then select the OS we want, all it does then is write that info to an unattend file and begins the build process using the drivers for that PC model. Happy days, If the PC name entered is already in AD it just overwrites the existing computer object and the current location in AD is in tact which is vitally important as our OU structure is quite complex and multiple group policies then kick in for that particular PC or room its in etc etc. SCCM client is pushed out to the client and the object is pulled into a specific collection by its AD OU membership and then application deployment is kicked off! We do not then have to revisit the PC one its finished its ready to use by the end user Can SCCM offer this type of routine? I have already seen a VB way of prompting for a computer name so thats perfect, if i chose not to set an OU on the task sequence will it just update the existing Computer object in AD if the routine is set to join it to a domain? As i said above we need to be able to stipulate what OS is installed from being at the physical machine without any prep work on the SCCM server, is this possible? I have followed the guides on here for OS deployment and i'm somewhat confused by the deploy and capture process? Can SCCM just install from an OS image location? Normally we slipstream any windows updates directly into the OS directory so when its rolled out its already patched. (we currently dont use the software updates side of SCCM) thats another job for later! Sorry for all the questions but any help would be great! Thanks