|
cjones464 -> RE: How to advertise a capture image to a bare bone system (9/17/2008 9:27:29 PM)
|
I have just completed this exact process with my Build technician.
I know SMS, he knows xp and ads and the OLD bdd.
Jason and Rbennett and both make good points.
Firstly I wanted to do it using the Bennett approach. I was more comfortable with that
My build technician wanted to do it Jason’s method.
I conceded and let him do the formal wizard driven method. In a way I am glad because I u’stand so much more about the op sys deployment methodology in general. We have not quite got all the oem drivers working yet because some are multi layered. But we can lay down a functional operating system on bare metal, from PXE boot, using one OS image, across two manufacturers, (2 models of ibm & 3 models of HP) and install apps.
You will also need MDT (well I think you will but some bright spark will come along later and say different)
There are many many gotchas in the whole process though and you allude to one in your final sentence
“Can I use the boot image 86x that come with SCCM to deploy windows XP SP2?”
If you use the boot image that comes with sccm to deploy XP you MUST remember that the boot image is actually a VISTA shell. This is good for SCCM OSD because it gives you more features whilst the client is running under the boot image phase/s (both for the capture and the deploy phases).
But the hardware must be vista compliant. (even though you are deploying XP when running under winpe you will be in Vista land so your nic and video ect must be “Vista capable” .) you can prove this to yourself because as the client boots you will see a vista style progress bar.
Also, I have read, and I am told, my build tec says he addressed this, that when the drive is formatted by the deployment process it formats with a vista file system which gives grief when you try to subsequently lay down XP on top of that. I understand there is a known fix /workaround for this.
Now, about your collection question.
SCCM will not deploy to a client that it does not recognise.
So there is this “nasty secret” bit of VBS that “helps you out “
Create an empty collection in sccm,
You edit this pxefilter.vbs and tell it the site server, site code, and the collection number (not collection name) you created.
The PXEFilter “intercepts” the PXE boot process and populates your collection with the MAC address of the client as it boots.
SCCM now “knows about the client" and can run the capture and or the deployment task sequence against this.
Search the Microsoft website for sccm_MDT_configuration.wmv it is a very good video it is actually for Vista deployment but is great for understanding the process. I’d a been lost without it. Also it was done on a different version of sccm and MDT but the theory is sound.
There seems to be a lot of conflicting advice about dhcp scope settings for SCCM PXE booting but I have found a mixture of settings that work for me in my lab. At least I know what to look out for when we move into live.
I actually feel confident now that I could attempt Rob Bennitt’s approach now that I know what is required.
But… You say you know SMS well so I assume you know many of its little idiosyncrasies too. There are quite a few non default settings that you will have to adjust Just to get a client to SCCM PXE boot.
Finally, Not to sound patronising but Please try it in an offline lab first ! there are a few steps that if you get wrong you will NOT be able to clean out fully successfully without uninstalling your PXE point if not rebuilding your site completely.
If you are interested, time for us to get from building the lab to first successful test lab deployments – two guys – three weeks.
You may rate my post if even if the text is rubbish the pointer to Microsoft’s sccm_MDT_configuration.wmv is worth one out of ten ? ;)
|
|
|
|
