Hello.

I am wondering if there is any whitepaper or guide out there that describes a upgrade scenario from and SMS 2003 enviroment with OSD feature pack to a SCCM 2007 solution. Focusing on the deployment part.

Or any real life experience, after upgrading SMS2003 to SCCM2007 the old OSD packaes is to be found under OSD FP Packages, but one cant do anything with them.

My idea was to upgrade the SMS2003 to SCCM and have the BDD2007 solution running in the background, the only thing that BDD really need the SMS infrastructure for is the ask the MP for the nearest DP.

Then doing new images in the SCCM enviroment.

But the problem is that after upgrading to SCCM the build has stop working, right after the PE has been initialized you get a 80004005 error.

In the C:\minint\smsosd\osdlogs is only one log file created with is OSDInstallWizard.log witch says:

--------------------------------------------------------------------------------------

Using custom package location with user specified credentials

Initializing failure: Package path not set.

Successfully unregisterd OSD enviroment objects.

----------------------------------------------------------------------------------

The builds worked fine in this enviroment just before upgrading to SCCM 2007.

Any ideas.

Thanks. !

Ok, here it is:

OS builds (wim-files) that have been build for SMS 2003 OSD Feature pack won't work with SCCM.

That is because SMS 2003 OSDF added some custom variables to the wim format used by imagex.exe

That's also why you can't open your old wim files with imagex.

What you need to do is really build new reference machines and capture them again but this time either manually with imagex or with the SCCM capture wizard.

//Paul