Migration Help......

Migration Help...... (Full Version)

All Forums >> [Management Products] >> System Center Products >> System Center Configuration Manager

Message

aburnside -> Migration Help...... (6/27/2008 3:14:04 AM)
I'm currently working on a migration plan for my company. Currently we have Configmgr 2007 implemented in our environment with one primary site and 30 secondary sites. We are moving our entire server infrastructure into a new Data Centre facility and as a result, the new facility will house new server hardware and subnet range. My dilemma is how to move the primary site to a “new server” while ensuring the entire SMS infrastructure is maintained i.e. database, secondary sites, collections, packages and so on. Is it right to assume the following high-level plan? I understand I need to create a new child site of the existing primary (as objects will replicate down the hierarchy). After all objects have replicated down, can I than break the connection of the old primary? I understand that collections will be locked on the child primary in the data centre. When I break the connection of the existing primary with the new DC server, will the collections be unlocked on the new primary site in the DC? or does this require SQL changes to unlock collections? To retain client historical data of my existing site, will I than need to make the existing primary a child site of the newly installed site at the DC after completing step 1 listed above? (As the client historical data will flow up the hierarchy and be retained after I decommission the old primary site) or will this information be replicated when I create the DC primary site a child of the existing primary listed in step 1? It was my understanding if I wanted to move secondary sites from one parent to another; I must completely uninstall the secondary site first and then reinstall it from the new parent. Or is it possible to retain my 30 secondary sites by changing the senders to point to the new primary in the DC? If i am required to uninstall secondary sites is it possible to simply remove all references of the secondary site from its parent while leaving the local secondary server installation intact? (I know there is a removal option from the console to complete this action) and than somehow create the new relationship to the new primary? I have tried to find documentation on Microsoft web site but I am unable to find what im looking for. I don’t know if its due to this product being new on the market or my search skills are just shocking J Any suggestion would be much appreciated.

skissinger -> RE: Migration Help...... (6/27/2008 8:16:57 AM)
I haven't done that scenario, but I've heard of it: new child to get data to flow down, then break and re-parent the other way to get data to flow up. I don't believe packages replicate, though. Those you would need to recreate, and plan for the fact that it will be a new package id/advertisement id and "new" to your clients. Your collections should unlock when the parent-child relationship is broken. I've heard of specific instances where that didn't happen, though, and did require some sql commands to unlock. As far as I know, you cannot rehome a secondary from 1 parent to another. There is simply too much in WMI and elsewhere referencing the parent site code. It is an uninstall/reinstall. It's not that big of a deal. I do it all the time during lease returns. I assume you're concerned about re-replicating packages? Preloadpkgonsite is a wonderful utility to avoiding most of the heavy lifting. With all that said...why can't you just name the server in the data center the same as your existing, and restore the database there? That would be, oh.. about a days work, possibly less. Vs. weeks of work to plan moving everything over--just so that the server name matches whatever the standard is in the data center. Try to get an exception from the standard server name convention!

aburnside -> RE: Migration Help...... (6/27/2008 8:37:40 AM)
Hi Skissinger, Thanks for your reply and input. I'm not too concerned about re-replicating packages. It’s all the work to uninstall/reinstall and also re configure secondary sites. Is it possible to take advantage of the copy site server settings and copy back the settings once I bring up the new secondary server? Are you able to suggest a high-level design about your suggested idea of naming the server in the DC the same as my existing server, and restore the database there? I'm very interested in knowing the steps required to complete this tasks as i didn’t know it was possible. My guess is to save existing database, remove old server from domain, let the changes replicated in AD, add new server to domain with same name, reinstall ConfigMgr on new server with same primary site code???? and restore database? I would appreciate your feedback. Thanks.

aburnside -> RE: Migration Help...... (6/27/2008 8:41:20 AM)
Has anyone found Microsoft documentation suggesting the correct strategy for this type of implementation / requirement???

skissinger -> RE: Migration Help...... (6/27/2008 8:59:18 AM)
Just think of it as a hardware lease return... just that the hardware happens to be in a different city. Review these: http://technet.microsoft.com/en-us/library/bb693882(TechNet.10).aspx And on your server, look for the Recovery Wizard. Basically, backup your existing site (using the ConfigMgr Backup task, and SQL backup is NOT enough), stop services on current site, and rename the server. Name your new server the same name as your current. Personally, I recommend waiting until the new server is named before you install IIS or SQL (if it's local)--but that might be bad memories from years ago. The latest versions of IIS and SQL might be more forgiving about a server rename these days. Once SQL (the exact same version) is installed, install ConfigMgr with the same site code & in the same directory as on the original. Then you just run through the Site Recovery Wizard and do exactly what it tells you to do to restore from the backup you took. Edit: the reason I say stop/disable services on your renamed site is just in case things go horribly wrong, you can just rename everything back, and restart those services; and try again another day.

aburnside -> RE: Migration Help...... (6/29/2008 11:04:27 PM)
Will this solution work if the current primary server has a local ConfigMgr SQL database but the new server in the datacentre will have a remote ConfigMgr SQL database? Are you able to provide a high-level design for the other solution ie creating a child primary?

aburnside -> RE: Migration Help...... (6/30/2008 8:19:52 PM)
I just have a couple of other questions I would love to ask: 1. I know my boss will be asking this question so I am thinking ahead here. The new datacenter servers will have a new naming standard applied to the servers. I know in option 2 we are required to keep the same name as the existing primary site. Is it possible to rename the current primary site server now to the new name which we would like in the datacenter? That way when we migrate to the new environment, we will have the server name that we want? Or renaming the current server to a different name will cause SCCM to stop working? 2. Just considering different options here in my migration plan. We have only had SCCM working in production for 3 – 4 months now; the only major deployments have been SOE updates to our production desktop machines. MS Software Updates, software meeting have not been configured yet in SCCM. If my boss elects to blow away the current SCCM database and build a new one in the datacenter, is it possible to take advantage of the “Transfer site server settings”. Meaning can I take a current settings backup of primary site and secondary sites, create the new primary in the datacenter (Don’t link the new and existing site) import the server settings on the new primary and install secondary sits to new primary and import server settings on secondary. Will this option work? Any feedback would be much appreciated. Thanks.

Page: [1]

Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI

0.21875