I just noticed a flaw in our install. On our Primary site server CCM has been installed partly in C:\Program Files\Microsoft configuration manager\.... and partly in C:\Program Files (x86)\Microsoft configuration manager\..... This is a problem when installing addons and even R3. I had to copy the sms_def.mof from Program Files to Program Files (x86) to be able to install R3. The site works in general but I'm worried this will break down the line. How is it even possible that the installation could split like this. Anyhow I'm thinking I will have to reinstall the primary site but that results in more than a few questions. The same server has the database stored on it. Also we are running in native mode so certificates are there. We also have 3 secondary sites at the moment and more to come. If I reinstall the primary site, what will happen to the secondary sites? Will the primary site be able to get the old settings,certificates etc or will I have to start from scratch? The problem right now is I'm trying to install the Dell management pack for SCCM and it wont install because it looks for files in X86 and not the normal Program files directory.MCITP Server Administrator Blog: http://www.nixadmins.net

Hi, 1) If you reinstall a primary site then you will have to reinstall the secondary site 2) You can use the Transfer Settings wizard in your existing site and export the setting to a XML file.Kent Agerlund | http://scug.dk/ | The Danish community for System Center products

Out of curiosity and for informational purposes, how did you accomplish installing ConfigMgr in two directories? I've never seen that before and can't come up with any way of actually achieving that result.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

Out of curiosity and for informational purposes, how did you accomplish installing ConfigMgr in two directories? I've never seen that before and can't come up with any way of actually achieving that result. Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys This is something I would really like to know also. All secondary site servers are correct. How this standard install could be messed up like this I have no idea. EDIT: Also looking at the site Properties from the console installation directory is C:\Program Files\Microsoft Configuration Manager. Says nothing about C:\Program Files (x86). But there are files there. MCITP Server Administrator Blog: http://www.nixadmins.net

Persoanlly I'd reinstall just to get it off the C drive but I'm with Jason I don't think it's possible to be in two locations. If you change the location you'll basically be starting over from scratch if you want to reuse the same hardware. If you have more hardware you could make a new site that's a child of the current site, reinstall the secondary and make it a child of the new site then simply remove the parent/child relationship of the new priamry and the current one. Can you post a directory listing of each of those two directories? I suspect one is add-ons like the toolkit or something. John Marcum | http://myitforum.com/cs2/blogs/jmarcum |

The hardware is just as old as the installation, 5 months. So I don't have anything to replace it with. I could user VMWare and virtualize this server and reinstall a fresh install on the server after a sucessfull VMWare capture. Still I don't understand how this is possible, and why none of the addons can find the install. This goes for R3 install media and the KB977384 also. It did install the patch but the KB977384 - Advance Client Hotfix did not work with the KB installer. I had to manually extract it from C:\Program Files (X86)\... The file listings can be found at http://www.nixadmins.net/files/Files1.txt and http://www.nixadmins.net/files/Files2.txtMCITP Server Administrator Blog: http://www.nixadmins.net

Right click and save target as, the formating on the file when you open it from the webserver is not good.MCITP Server Administrator Blog: http://www.nixadmins.net

Mats, Shoot me an email offline john marcum at gmail dot com if you want to I'll setup a live meeting and try to help you get this working. John John Marcum | http://myitforum.com/cs2/blogs/jmarcum |

I'm just looking at your txt files. It almost looks like SCCM is installed twice on this server. You have two inboxes directories for instance. That's not good. I don't mind trying to help you but this is really something you need to get CSS involved in. Something is really wrong here. John Marcum | http://myitforum.com/cs2/blogs/jmarcum |

I actually opened a case with Microsoft as soon as the replies started dropping in here. This server isn't healty and before we go any further I'd really like to fix it. I still have 6 more secondary sites to get up and running. It will be a big job to reinstall evertything but if that's the only way then be it. Theoretically though, wouldn't it be possible to shut all SCCM services down, move everything to one folder, change the registry keys to point to that location and live on happily ever after. John, I might just take you up on your offer. Microsoft support should be in contact with me on monday since the C class case should be replied to in 1 working day and the case was opened on friday. Anyhow, I have no idea on how the installer was able to mess this up, I've never in my career seen anything like it and I'll be sure to post the resolution here. No matter if it's a reinstall or if Microsoft's support engineers come up with a different sollution.MCITP Server Administrator Blog: http://www.nixadmins.net

Without knowing the root cause of why there are two folders there it's hard to say. My guess, and this is only a gues, is that someone somehow managed to install SCCM twice on this server. Maybe they installed it, uninstalled it, then installed again in a different directory which left junk in the old directory. I'd say find the install path from SCCM, check the other path to see if ANY file have been updated recently. If not get rid of that directory. If both directories have files being updated I'm clueless. Worst case, blow it all away, reinstall SCCM to the directory where it thinks it's installed now and restore from the SCCM backup and hope and pray nothing goes wrong. John Marcum | http://myitforum.com/cs2/blogs/jmarcum |

I was the one who originally installed the server so I'm sure it hasn't been installed twice. And yes, some files in the x86 directory also get updated. This case is with the Microsoft engineers right now so let's see if they come up with a reason and a sollution.MCITP Server Administrator Blog: http://www.nixadmins.net

I was really hoping you were going to say you inherrited this server. There's another post simlar to this here. I wonder if this could possibly be the same thing? http://social.technet.microsoft.com/Forums/en-US/configmgrsetup/thread/74c0c50e-04b2-447c-8fd8-65e1a9de73c8/ John Marcum | http://myitforum.com/cs2/blogs/jmarcum |

I have a similar situation. The split installation is actually an R2 thing. Uninstall R2 and any tools/hotfixes that would copy to the 'x86' directory and you will find basically nothing left. SCCM fully installs to C:\Program Files\Microsoft Configuration Manager but R2 and R3 target C:\Program Files (x86)\Microsoft Configuration Manager. This can be duplicated and is not a result of you doing anything wrong. For my situation, we upgraded from 2003 x86 to 2008 R2 (which is x64) and kept the same file path. This meant not using the default directory. John, I would venture to say that if your install is on a different drive letter than C, the feature packs are able to discern the change and install to the correct location. If the path is still on C but not the default installation directory, the feature packs can't tell the difference. Other logs indicate the correct installation directory. Only the feature packs and hotfixes do not. For R2 to work, I had to copy the ddm.box files from the x86 path to the real location. Once copied, reinstalling R2 worked for me. Now I am stuck on installing R3 because the hotfix 977834 goes to the x86 path instead of the real path so it does not get installed.

Hi 195, I got R3 installed by manually copying the file site_def.mof from C:\Program Files\CCMDIR to C:\Program Files (x86)\CCMDIR. I had a case open with Microsoft support for four weeks and they were not able to help in any way since they just insisted the install was working fine. Which it was, but I could not get any addons working, like Dell SCCM adons, SCUP etc. I finally went and uninstalled all secondary sites. Uninstalled our SCCM and reinstalled from scratch. And now everything is working as it should. The install is on D:\ now also.MCITP Server Administrator Blog: http://www.nixadmins.net

Thanks Matt, I did that same thing last night and it worked for me too. For the hotfix, the msi would not install at the correct location on the server (installed to the x86 directory). Installing the .msp within the msi worked fine though. So now I have the hotfix and R3 correctly installed. Logs look good and site status is green for all sites.

I have a similar situation. The split installation is actually an R2 thing. Uninstall R2 and any tools/hotfixes that would copy to the 'x86' directory and you will find basically nothing left. SCCM fully installs to C:\Program Files\Microsoft Configuration Manager but R2 and R3 target C:\Program Files (x86)\Microsoft Configuration Manager. This can be duplicated and is not a result of you doing anything wrong. For my situation, we upgraded from 2003 x86 to 2008 R2 (which is x64) and kept the same file path. This meant not using the default directory. John, I would venture to say that if your install is on a different drive letter than C, the feature packs are able to discern the change and install to the correct location. If the path is still on C but not the default installation directory, the feature packs can't tell the difference. Other logs indicate the correct installation directory. Only the feature packs and hotfixes do not. For R2 to work, I had to copy the ddm.box files from the x86 path to the real location. Once copied, reinstalling R2 worked for me. Now I am stuck on installing R3 because the hotfix 977834 goes to the x86 path instead of the real path so it does not get installed. I had to follow the same upgrade path moving SCCM from x86 to x86_64. It is very annoying that any hotfix I install cannot tell the appropriate installation directory for SCCM. I have to copy all the new files from %PROGRAMFILES(X86)% to %PROGRAMFILES% then change all the registry keys created with the wrong path. It would be nice if Microsoft allows you to verify the location of the SCCM install or use the registry key SCCM uses for Installation Directory. I'll have to keep in mind the method you used for R3 install when we get to that point.Allen Anderson Systems Support Specialist Arizona State University - OKED Knowledge Informatics

I have successfully migrated SCCM from Program Files to Program Files (x86) and I'll outline the steps I took and made some comments of the steps that I think could be omitted in solving this issue. Senario: Documentation suggests that moving SCCM to a 64-bit server should retain the original install paths. If you kept the default path on a 32-bit system, that path is C:\Program Files. The default path on a 64-bit machine is C:\Program Files (x86). It is possible to install to C:\Program Files on a 64-bit machine, however new releases and hotfixes will not install to the correct path as they default to C:\Program Files (x86). Steps: 1. Backup your current configuration. I can't say that this will work because I possibly got lucky in migrating install directories. Perform a site backup using the SQL task in ConfigMgr. Save this data. Backup your applicationHost.config from the IIS directory if you've made modifications to this file. 2. Completely uninstall SCCM, IIS, BITS, WebDAV, and WSUS from the machine (if your on one site system). I made sure all configmgr VD's were removed from IIS and the related application pools. 3. Reinstall IIS, BITS, WebDAV, and WSUS. Configure them as if you were doing a fresh install. 3. Install SCCM including the service releases to its proper location. I also installed all the hotfixes. 4. Begin the site restoration process using your backed-up SCCM data. This will likely break the current install and this is expected. Hopefully the restore process will complete without issue. 5. Open up the sitectrl.ct0 file in C:\Program Files (x86)\Microsoft Configuration Manager\inboxes\stiectrl.box in notepad. You should see your old path in there. Replace it with the new path. There are also UNC paths that point to the old path. You will need to change those too. 6. Launch SCCM setup again. You should have the option to Upgrade an existing Configuration Manager or SMS 2003 installation. If you dont, launch regedit and follow this step: a. Launch regedit and found every configmgr related key and fixed all file paths to point to the proper location. I did a search in the registry for ' C:\Program Files\Microsoft Configuration Manager' 7. Hopefully everything installs successfully. At this point, start checking logs to make sure everything is functioning correctly. You may need to uninstall the management point and reinstall it. I had to, along with the SMP point. MP.msi may not be able to create the CCM_Incoming VR in IIS when you reinstall it. If this is the case, uninstall BITS and reinstall it, then try the MP reinstall. 8. Re-install all the required hotfixes, update your DP, etc. Your hotfixes should install correctly to the correct directory. I didn't have to re-install R2 but if you find you do, it should install successfully too. 9. Setup WSUS as you would for a new install. SCCM will likely have to be reconfigured for this. Mine just finished doing a full sync after about 3 hours. This is probably a totally unsupported way of doing this, but it worked for me and hopefully will work for someone else too. Allen Anderson Systems Support Specialist Arizona State University - OKED Knowledge Informatics