On Tue, Feb 5, 2013 at 2:54 PM, Robert Peterson <robert.peter...@prin.edu> wrote: > The actual moving of the database to another server is not difficult as long > as you don't change from internal to SQL database. The problem is in > renaming the server. When you do that you have to remember to change any > GPO's that are associated with WSUS. The database export and import > procedures are still the same that I'm aware of, use the WSUSutil command > line.
That's not working for me. wsusutil export Old-Server-CAB.CAB Old-Server-LOG.LOG give me a binary file as the LOG, and an empty zero-byte CAB file. > If the environment is not very large About 130 servers ... > you could just install a fresh copy of WSUS on the new server, re-point the > GPO's and let the clients populate the new database on their own. Then import > only the metadata of approved updates. That way you're not getting old > machines that may not be on the network any longer and you start with a much > cleaner database. That's what I am hoping to do. I have installed WSUS on the new server, and am about to synchronize updates. Then I was going to change the GPO and let it re-populate the DB. But I have nothing to import metadata from ... I can approve everything up till last Patch Tuesday date, of course. ~ 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 listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin
