Jump to content


EngiNerd

SCCM 2007 SP2 prerequisites download

Recommended Posts

Hello,

I am trying to set up SCCM 2007 SP2 in a lab environment to simulate the migration to something newer and supported. However, when the setup program tries to download the prerequisites off the internet, it stops and complains that some files cannot be found. I also tried to download the prerequisites before doing the actual setup by using the /download switch with no success.

Thus, I was wondering if any of you have experienced the same issues - as I suspect that Microsoft has simply deleted the files from their servers once SCCM 2007 reached EOL - and have found a way to bypass the prerequisites download step and let the setup program continue. Alternatively, if any of you has saved the downloaded prerequisite files and could provide them to me, it would be great.

Thanks for your attention.

Share this post


Link to post
Share on other sites

so I found the original media (not the pre-reqs) is still on Microsoft Volume License Service Center, when you try to install it is it giving you errors on all the files or just some ?

Share this post


Link to post
Share on other sites

I checked the logs, and it complains it can't download the file ccmsetup.cab at the following address: http://download.microsoft.com/download/E/9/D/E9D843B7-8F1C-4C27-9328-6205B557730F/ccmsetup.cab

I tried to download that file with a web browser and I received a 404 error, confirming my suspicions that the file is no longer available. I also tried looking for that file on archive.org wayback machine, but unfortunately it wasn't archived.

Also, I forgot to mention that I'm trying to install SCCM 2007 SP2 on a Windows Server 2008 R2 VM, though I think it shouldn't be relevant at this step.

Share this post


Link to post
Share on other sites

if you mount the SCCM 2007 SP2 iso you might find what you need, like here for example, i'm not sure if this is enough but it might help

 

 

image.png

Share this post


Link to post
Share on other sites

Hello, I tried with that file, but then the setup program failed halfway during install. I checked the logs, and I found out the cause:

When the prerequisites are downloaded, the setup program tries to download the file configmgr.manifest.cab from http://go.microsoft.com/fwlink/?LinkId=141733, which in turn redirects to https://download.microsoft.com/download/2/9/2/292BF5ED-DACB-4525-91C7-93978CC714C3/configmgr.manifest.cab. Unfortunately, also that file has been deleted from Microsoft servers, yet it was archived by archive.org, so I managed to download it and place it in the prerequisites folder.

That configmgr.manifest.cab contains an XML file with the URLs of the component files that setup needs to download, among which there is ccmsetup.cab. However, that copy is newer/different than the one included in SCCM installation files, as it has a different MD5 hash. Thus, when that file is replaced with the one included in SCCM installation file, setup detects an inconsistency in the MD5 and fails.

In theory, one may try to bypass this issue by replacing the MD5 string in the XML file in configmgr.manifest.cab. Problem is, configmgr.manifest.cab is digitally signed by Microsoft, so it would be impossible to repack the modified XML in that CAB archive.

To sum up, without the copy of ccmsetup.cab that was deleted from Microsoft servers, SCCM 2007 SP2 cannot be installed 😞

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...



×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.