+1 * *
*ASB* *http://XeeMe.com/AndrewBaker* *Harnessing the Advantages of Technology for the SMB market… * On Mon, Jun 11, 2012 at 3:20 PM, Kennedy, Jim <[email protected]>wrote: > That was me and just bring up the new server and repoint was how I ended > up doing it. It went fine, a complete non-event. If you have a ton of > complicated groups for your desktops/server in WSUS then you could bring up > the second as a replica but without a complicated grouping structure that > is not worth the effort either. > > > -----Original Message----- > From: Stefan Jafs [mailto:[email protected]] > Sent: Monday, June 11, 2012 3:16 PM > To: NT System Admin Issues > Subject: New WSUS server > > I know this came up about 1 month ago, any reason why I can’t just install > a new 2008 R2 WSUS server from scratch, download everything from Microsoft > again, then change the Intranet server name in GPO? Retire the old 2003 > server. > I know the initial download will take some time but I have a pretty good > pipe. I looked at some Microsoft papers how to move WSUS from One server to > Another, but seems overly complicated. > > Stefan > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
