Wednesday, April 22, 2009 12:31 PMWe need to move our SCCM 2007 SP1wR2 install from a Windows 2003 32-bit install to a 2008 64 bit install on a new server. All the threads about this basically say run a backup, shut down the sccm services, take the box out of the domain, and rename it. Setup the new server with the same name, drive configs. Nobody really talks about how to get the packages over to the new server. We have about 600 apps and the source of the apps resides on E:\Apps In addition, the primary acts as a DP. Obviously for the source (e:\apps), we will just copy that over.
What about the smspkge$, smspkg, smspkgsig, and smssig$? Do you install SCCM on the new server first and then copy the contents over to the new smspkge$ or do you copy it over first then install SCCM?
What about the accounts, Senders, Security Rights, etc? Will they be restored or will that need to be recreated?
I think I read we will lose all the clients and they will repopulate. Is that true? I don't want apps rerunning like we had when we upgraded to SCCM.
What else will be lost during the move?
Wednesday, April 22, 2009 1:12 PMModeratorHi,
When you perform the restore process you are asked if you want to update the DP's. If you select Yes, packages will be refreshed and the various SMSpkge$ folders will be recreated.
Security rights will also be restored, along with clients and other settings. Information about the apps is stored locallay on the client. They wont start to reinstall the apps after a restore.
Kent Agerlund | http://agerlund.spaces.live.com/blog/
Wednesday, April 22, 2009 3:08 PMI have a vmware setup that had a Win2K3 Primary server with 2007SP1wR2 and a database on a seperate box (2005SP2) I created a Win2008 Server to simulate moving to a new os and hardware. I go to run the sccm setup and it gets to Create and Initialize site database and get a pop-up
Setup has detected that data SMS_XYZ on SQL Server SQLSVR is not empty (of course not) Do you want to empty the database and continue (no way). When I say no...I get a fatal error
How then do you get around this issue when it wants to create a new db when one with data already exists. The log is worthless
Setup has encountered fatal errors during database initialization. Contact your SQL administrator
Wednesday, April 22, 2009 4:15 PM
Do you want to empty the database and continue (no way).
Wednesday, April 22, 2009 4:22 PM
Assume I was in production, you are telling me to blow everything away in the database? Are you saying do it and then use the backup to recover? I'm obviously tesing this for when I do these steps in prod.
Wednesday, April 22, 2009 4:57 PM
Gatorcb I am getting the same error when trying to reinstall SCCM on a new site server. I have the database on a separate server as well. Just wanted to let you know that I tried selecting yes when prompted to empty the database and continue but it did not make a difference. I got the same error.
Wednesday, April 22, 2009 5:08 PMI get a slightly different error when I say yes...it says setup cannot drop the database on the specified SQL devices...Trent are you trying on W2K8 64-bit as well?
Wednesday, April 22, 2009 5:10 PMNo I am still on 2003 32 bit. You are right I get the drop error in the ConfigMgr log as well.
Wednesday, April 22, 2009 6:51 PM
Assume I was in production, you are telling me to blow everything away in the database? Are you saying do it and then use the backup to recover?Yes, that's what I am telling you. ConfigMgr takes care of all data (WMI, registry, database, inboxes, etc) for a successful restore. The important thing is that all those objects have to be "in sync". So make sure that you have got a successful backup, blow away the database manually and restore again.
Thursday, April 23, 2009 3:29 PMPlease forgive my ignorance. What's the correct way to blow away the database? Go into SQL Management Studio and do what? I generally let the sql team deal with the database stuff
Thursday, April 23, 2009 5:05 PM
I finally succeeded in restoring my site server after hardware failure. My database is on a different server and was intact. Disclosure, I am not a SQL admin or a qualified server admin, but I know enough to get by. Also I had tape backups of all servers involved so I knew that I could always revert back to my starting point if needed.
This is what I did, it may help you guys out.
1. I had a current site backup. I created a databse backup in SQL Management Studio on the database server.
2. I then deleted the current database (yes this is scary but it was the only way I could make the process work).
3. On the site sever I installed SCCM and let it create a new database with the same name (this is why you have to delete the old one, it wont let you create the new one if you dont.)
4. Power down the site server so you can rename the newly created database in SQL Management Studio, doesnt matter what you call it. I suppose you could delete the new database here as well.
5. Power the site server back up and restore the original database with the backup created in step 1 in SQl Management Studio.
6. Run the Site Repair Wizard on the site server.
7. You can then delete the extra database created in step 3 it still exists.
I have not seen this process written anywhere and believe me I looked. I dont know if it will work for everyone but it worked for me.