Hello to all, I have a standalone SCCM R2 Siteserver (Server 2003 x86, Sql 2005). I want to move it to a new machine with new!! servername (Server 2008 x64, Sql 2008). Old Sitecode should be hold. What is best practice? Thanks

It's not possible to use the old site code with a new server name. John Marcum | http://myitforum.com/cs2/blogs/jmarcum |

install a new site with a new sitecode or use backup/restore to keep the old information.Kent Agerlund | http://scug.dk/ | The Danish community for System Center products

use backup/restore to keep the old information. Kent Agerlund | http://scug.dk/ | The Danish community for System Center products The backup and restore will NOT work with a NEW server name. He has only two options: Backup and restore but keeping the old server name + disk layout Start over with new server name and site code. http://www.enhansoft.com/

The backup and restore will NOT work with a NEW server name. He has only two options: Backup and restore but keeping the old server name + disk layout Start over with new server name and site code. Isn't that what I said? Oh.. you were saying it in Canadian. I get it now. LOL John Marcum | http://myitforum.com/cs2/blogs/jmarcum |

LOL... yes you more or less said that but I didn't quote you, I quoted Kent. I guess it is OK since you are from the south. Jhttp://www.enhansoft.com/

Thanks, that's what I thought. 1. What about renaming the server? Using Sysinternals ChangeSID? Why is it so difficult? Did anybody test Changing Servername? Of course, it will be necessary to adapt SCCM Active Directory System Container to new server name using AdsiEdit. 2. What about this: - Shutdown Old Site Server - Start over on new hardware with new servername and new Site Server and hold the old Site Code? J

#1: renaming is not supported and will break ConfigMgr #2: can be done, but it's not recommended. You have to clean up AD (and maybe WINS depending on your setup) and make sure that the clients are assigning correctly to the new site (which will get a new trusted root key). See "resetkeyinformation" in the docs.

Let me echo Torsten statement. 1) Is not supported. 2) Guaranteed that you will have issues with 2, IMO it is not worth the headache that you will get by re-using the same cite code. http://www.enhansoft.com/

Thank you, great help. So i resume what i have to do: - Export all needed objects. A lot to do! Any help accepted! - Shutdown old site server (or is coexistance possible?) - Remove Sccm AD system container. - Install new primary site with new site code, import objects. But, how do i join my clients to the new site? I know there's a way to change site code by script, see http://www.myitforum.com/forums/tm.aspx?high=&m=155586&mpage=1 But what about the rootkey, as Torsten wrote? Because the clients have a wrong rootkey from the old server, softwaredistribution will not work with new site server, at first. So deploying a package/program with CCMSetup.exe RESETKEYINFORMATION=TRUE will not work. But I could use client push installation wizard (client repair), to reset clients, but I don't think that a repair resets the keyinformation?

You could make new server a child of current server, reassign clients then break the parent/child relationship. John Marcum | http://myitforum.com/cs2/blogs/jmarcum |

Ok, I will do a Side-By-Side-Migration following technet. It is stated for SMS 2003 to SCCM 2007, but I read that it works also for SCCM to SCCM. I will reply, when done. Thanks a lot. Seiba

Puh, an amazing job! There were many things to do, and it is documented very bad. A big problem is moving AppV Packages from one site to the other. I'm lucky, that there were only few!! Got it to work, New SCCM Site is now running on new server. I recognized, that some clients automatically assigned the new Site Code. These clients are server operating systems. I cannot find any reasons for this, did not find any instances in SCCM Site Server Logfiles. In what Logfile the information for assigning Site Code is stored. Thanks

Hi, Check the clientlocation.log file on the client.Kent Agerlund | http://scug.dk/ | The Danish community for System Center products

Thanks Kent, a bit late, sorry. Set SCCM Group Policy with Site Code, now all clients got the right side code, and are assigned to new side.

There is a problem with my reporting point. Reports do not work. (Site not found). I configured Server 2008 an IIS7 as stated here: http://technet.microsoft.com/en-us/library/cc431377.aspx Any ideas?

What does the rsetup.log say?

Hello Torsten, i solved the problem, reports are working now. I had to install "ASP" additionally. The document above did only require installing "ASP.NET". Microsoft should correct this. By the way, I did not find an 'rsetup.log'!?

On the link that you pointed to before, the docs do say that you need ASP. Note The ASP check box must also be selected if the site system will be configured as a reporting point. http://www.enhansoft.com/

Now, I see it too, sorry ...

Don't feel bad, EVERYTIME I've run an SCCM class at least one person misses that and their reports don't work. I think I even made it bold in my manual but someone will still miss it. John Marcum | http://myitforum.com/cs2/blogs/jmarcum |