How do you handle OSD RE-Deployments (Full Version)

All Forums >> [Management Products] >> System Center Products >> System Center Configuration Manager



Message

xneilpetersonx -> How do you handle OSD RE-Deployments (9/30/2008 2:53:43 PM)

I am setting OSD up in a very distributed support environment in which computers are re imaged and redistributed quite often. I am using OSD with the R2 Unknown Computer support, along with MDT. I am trying to come up with a method by which no matter what the scenairo (new computer, old computer), when a mahcine is booted (PXE or Media) there is always a TS advertised to said machine. Obviously if a mahcine is in the CM DB unknown computer will not work. My next thought is to have two TS one advertised to Unknown Computer and the other advertised to all computers (non manditory); however this still pops up an OS deployment notification - very bad. I have seen a few myitforum members mention setting the TS to only run on windows 2000 this supressing the notification etc. but this seems kind of hackey.

What is everyone else dooing - certinaly this issue comes up quite often?

Thanks

neilp



egiroux -> RE: How do you handle OSD RE-Deployments (9/30/2008 8:01:36 PM)

I'm in kind of the same boat as you.  I have a vbscript setup to add a direct membership rule to a collection for the machine on which it is run.  This works fine if you want to advertise the TS to a standalone collection and move machines into it in a just-in-time basis.  This can be executed using the MediaHook functionality with the TS media. 

The challenge in my environment is with our test labs/groups.  These computers may be rebuilt multiple times per day.  The challenge is with obsolete records in the database hanging around after the machine gets built.  These have to be cleaned up to get the task sequence to load.



rbennett806 -> RE: How do you handle OSD RE-Deployments (10/1/2008 6:11:04 PM)

We treat every OS deployment as a bare metal scenario - we have a custom .HTA that kicks in at the start of the OSD process that deletes any existing resource objects for the machine from the SCCM database and creates a new one. Of course, if you want to rely on the history information for things, this won't really work for you...

Here's an old post about this same topic: http://www.myitforum.com/forums/m_181969/mpage_1/key_/tm.htm#181988



xneilpetersonx -> RE: How do you handle OSD RE-Deployments (10/1/2008 11:11:21 PM)

Thanks Rick..



Page: [1]

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
0.4414063