SMS 2003 OSD/BDD and SCCM 2007

myITforum.com Community Forum

Home Forums Blogs Live Support chat Search Articles Wiki FAQ Email Lists Register Login My Profile Inbox Address Book My Subscription My Forums

Photo Gallery Member List Search Calendars FAQ Ticket List Log Out

All Forums RSS Feed Subscription:

SMS 2003 OSD/BDD and SCCM 2007

View related threads: (in this forum | in all forums)

Logged in as: Guest

Printable Version

All Forums >> [Management Products] >> System Center Products >> System Center Configuration Manager >> SMS 2003 OSD/BDD and SCCM 2007

Page: [1]

Message

<< Older Topic Newer Topic >>

SMS 2003 OSD/BDD and SCCM 2007 - 3/25/2008 10:15:05 AM

BCM4309

Posts: 25
Score: 0
Joined: 6/4/2007
Status: offline

All,

I have a question for everyone that has implemented SMS 2003 OSD / BDD and then upgraded to SCCM 2007. We recently completed our SMS 2003 SP3 design and implementation and that is working great. We're now beginning to design and implement SMS 2003 OSD / BDD to replace our Ghost Solution Suite imaging implementation. We recently began this work with SMS 2003 OSD / BDD. In several months we are scheduled to implement SCCM 2007 in an effort to maintain currency in our environment.

My question revolves around our SMS 2003 OSD / BDD implementation. What are the issues when we go to SCCM 2007 in terms of OSD / BDD? Will we lose anything that we implemented in SMS 2003 OSD / BDD, will there be "rework"? Does it make more sense to hold off on implementing SMS 2003 OSD / BDD and wait till we get to SCCM 2007 and then implement the SCCM 2007 version of OSD and then use Microsoft Deployment Toolkit (MDT) 2008 considering we're only several months away from our SCCM implementation?

I'm hoping those of you that had SMS 2003 OSD / BDD implemented and working and then upgraded to SCCM 2007 will have the time to respond. I need to provide this information to my manager and director so we can make the best and most informed decision as time is precious!

Thank you,

BCM

Post #: 1

RE: SMS 2003 OSD/BDD and SCCM 2007 - 3/27/2008 1:43:44 PM

rheuermann

Posts: 253
Score: 4
Joined: 7/11/2002
Status: offline

We decided to wait. I'm seeing in the Technet Library that OSD would be a legacy upgrade and there would be a lot of conversion work or it looks to me that it would be less work to simply recreate in SCCM. I would say with SP1 pending, to plan on deploying SCCM sooner rather than later and a side by side upgrade looks cleaner if you don't mind re-creating your software deployment packages and advertisements and can afford the new hardware...

(in reply to BCM4309)

Post #: 2

RE: SMS 2003 OSD/BDD and SCCM 2007 - 3/31/2008 5:13:21 PM

MhermanNBME

Posts: 62
Score: 3
Joined: 4/4/2007
Status: offline

I've upgraded to sccm, and I am suprised in how difficult the OSD process is (i don't really know anything about the BDD). For just the OSD, we used a boot CD, then chose the computer name, image then the image came down. The biggest problem i have with the new process requres the computer to be in SCCM for you to image it. We get a lot of "bare bones" systems, and it seems unnecessairly tedious to have to type in the computer name and MAC address of every computer that you want to image, then advertise to it, then you can boot off the cd. PXE should automate the booting of the cd part, but so far I'm not seeing a way around having to enter the mac address and advertising. I heard there is something comming in SP1 with PXE that will let it automatically generate a name, but it doesn't seem like it will just let you type the name you want.

(in reply to BCM4309)

Post #: 3

RE: SMS 2003 OSD/BDD and SCCM 2007 - 4/25/2008 12:32:45 PM

jason.galbreath

Posts: 27
Score: 7
Joined: 9/28/2006
Status: offline

We've recently begun our SCCM upgrade from SMS2003/OSD. There's a lot of work involved in upgrading OSD. Basically everything you've done in the old OSD will have to be redone in SCCM. I've figured out a way to keep my current images without recapturing them but it's not supported by MS (seems to work good though

). That saved us a little time but all of our actions had to be manually put into the SCCM task sequencer. If you're close to your SCCM implementation I would suggest waiting so you don't have to "rework" everything when SCCM comes in.

(in reply to MhermanNBME)

Post #: 4

RE: SMS 2003 OSD/BDD and SCCM 2007 - 4/28/2008 9:48:41 AM

rjarrett

Posts: 589
Score: 17
Joined: 5/26/2004
Status: offline

This is NOT gospel, but I can swear I read that you are supposed to remove your SMS 2003 OSD feature pack before upgrading. I don't have a reference and that doesn't mean your model cannot work once upgraded, but it is not "easy" to transition.

Follow-Up:

I saw this post when researching this topic
http://blogs.technet.com/smsandmom/archive/2007/11/14/upgrading-to-system-center-configuration-manager-2007.aspx
It says, you can "upgrade from SMS 2003 SP2 or SP3 to Configuration Manager 2007. You have your choice of doing an in-place upgrade or side by side. There's one catch though, in that you must uninstall the OSD Feature Pack prior to the upgrade. Configuration Manager 2007 includes that functionality so you don't need the OSD Feature Pack (FP) anyway."

I have not been able to verify this on MS website, except one bullet on
http://technet.microsoft.com/en-us/library/bb693927.aspx
It says, you should "Uninstall any installed SMS 2003 feature packs, except for the Inventory Tool for Microsoft Updates"

< Message edited by rjarrett -- 4/28/2008 10:02:06 AM >

_____________________________

Let me know if this helped...

Rob Jarrett
SMS\VB Development

(in reply to jason.galbreath)

Post #: 5

RE: SMS 2003 OSD/BDD and SCCM 2007 - 4/28/2008 1:13:36 PM 1 votes

jason.galbreath

Posts: 27
Score: 7
Joined: 9/28/2006
Status: offline

You're correct about the OSD FP having to be uninstalled before the upgrade. I also agree that it's not an "easy" upgrade. Here's some of the steps we've had to take during the upgrade:

Recapture all images in SCCM (or you can manually remove the old OSD components from the images (I'll give some more info on that below).
Import all of your device drivers into SCCM.
Manually transfer all OSD custom actions into the SCCM task sequencer.

Some areas which have hit us hard in the upgrade are manual re-imaging (lite touch), bare-metal imaging, and installing updates from full media. MDT 2008 provides a web service which is supposed to help with the bare-metal imaging but the web service has a bug in it (waiting on a fix from MS) which doesn't allow the service to connect to child primary sites and create the computer resource. As far as lite touch goes, MS doesn't provide anything for re-imaging without having the image advertised to it. I'm in the process of writing another web service which will work in conjunction with the MTD web service which will dynamically place the computers in our OSD collection when a tech tries to re-image.

As promised, here's how we got around the requirement of having to re-capture our images in SCCM:
If you're on OSD Rev. 2 which uses WIM 0.9 you have to convert your WIM to 1.0. You can use my ImageX09 utility at http://www.mountain-webs.com/Downloads/tabid/55/Default.aspx for converting WIM 0.9 to 1.0.
Mount your image with ImageX and delete the following items:

Mount the WIM's software registry hive from the file: \WINDOWS\system32\config\software
Remove the registry key: HKLM\Microsoft\Windows NT\CurrentVersion\Winlogon\Notify\OSDWinlogon
Unmount the WIM's software registry hive.
Remove the file: \WINDOWS\system32\OSDWinLogon.dll
Unmount and commit changes back to your WIM.

You should now have a WIM which you can import into SCCM. I've done this with about half of our old OSD FP 0.9 WIM's and it seems to work without any problems.

(in reply to rjarrett)

Post #: 6

RE: SMS 2003 OSD/BDD and SCCM 2007 - 4/28/2008 3:21:48 PM

rjarrett

Posts: 589
Score: 17
Joined: 5/26/2004
Status: offline

Excellent information to consider. Thanks for the post!

_____________________________

Let me know if this helped...

Rob Jarrett
SMS\VB Development

(in reply to jason.galbreath)

Post #: 7