Replacing a Secondary site server
I am replacing a secondary site server (w2K3) with new hardware (w2K8). I have read the posts on using PreloadPkgOnSite, and I can do that but have a different idea in mind. The new w2K8 server is online in the same physical location as my only primary, so I want to: 1) Install the new w2K8 server as a new secondary site with a new site code. The server name will be different than the existing secondary Don't set any boundaries. 2) use the copy packages wizard to get all packages onto the new w2K8 secondary server that are currently on the old w2K3 secondary. Since primary and new w2K8 server are currently both at the same physical location I will save on WAN traffic 3) Once the copy packages wizard is complete, ship the new server to its final location and rack/cable 4) uninstall the old w2k3 secondary site server, and set those boundaries on the new w2k8 secondary site. Am I missing something in the above? My initial concern is that I don't want any client disruptions. Didn't mention it but I would also make the new seconsary an MP like the old secondary is currently. Any feedback on anything I might be overlooking is appreciated, thanks
May 26th, 2012 10:30am

That should work.Torsten Meringer | http://www.mssccmfaq.de
Free Windows Admin Tool Kit Click here and download it now
May 26th, 2012 11:00am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics