wsusmigrationexpert

i'm migrating our old wsus server our new wsus. synced new server old

now i'm running wsusmigrationexpert getting.

c:\program files\update services 3.0 api samples , tools\wsusmigrate\wsusmigra
tionexport>wsusmigrationexport.exe settings.xml
wsusmigrationexport failed below exception!
system.net.webexception: operation has timed out
   @ system.web.services.protocols.webclientprotocol.getwebresponse(webrequest
request)
   @ system.web.services.protocols.httpwebclientprotocol.getwebresponse(webrequ
est request)
   @ system.web.services.protocols.soaphttpclientprotocol.invoke(string methodn
ame, object[] parameters)
   @ microsoft.updateservices.internal.apiremoting.executespsearchupdates(strin
g updatescopexml, string preferredculture, int32 publicationstate)
   @ microsoft.updateservices.internal.databaseaccess.admindataaccessproxy.exec
utespsearchupdates(string updatescopexml, string preferredculture, extendedpubli
cationstate publicationstate)
   @ microsoft.updateservices.internal.baseapi.update.searchupdates(updatescope
 searchscope, extendedpublicationstate publicationstate, updateserver updateserv
er)
   @ microsoft.updateservices.internal.baseapi.updateserver.getupdates()
   @ microsoft.wsusmigrationtools.exportserverstatus.dumpdata(xmltextwriter dat
awriter)
   @ microsoft.wsusmigrationtools.wsusmigrationtool.main(string[] args)

we had db stored locally on old server. part of migration configured our db our sql ent. cluster

our old server using built in wus db, new wsus server i,m using our ent. sql cluster.

yes, stated synchronized new server old. point, aquire migrationexport tool on new server. thing not there actual computers, there pointed new server.

the other approach have worked, have been migrate database wid back-end server, , install new server pointing back-end server, no synchronization necessary. (you would, of course, need copy ~\wsuscontent\* subfolders old server new server in scenario.)

either way, a couple of notes of interest about the "samples , tools" kit.

first, even though named "wsus 3.0 samples , tools" kit, code written wsus v2, , not of updated wsus v3. (some of built-in wsus v3 product , abandoned in-place in kit.)

second, code 'unsupported' -- means: has bugs in , microsoft isn't going fix it. none of ever intended actual working code, although wsus v2 did, rather sample of how use api achieve objectives. believe others have had issues particular utility well, , search of forum utility name should pull conversations.

if did perform synchronization of new server old server, shouldn't need else except make new server upstream server , point clients it.

if you did not sync new server old, if still have original installation , susdb.mdf windows internal database installation (and using utility export data suggest true), suggest migrating entire database sql cluster, , reinstalling wsus on new system pointing new cluster instance of original database -- rather trying hassle through using less-than-optimal migration tool.

---

lawrence garvin, m.s., mcitp:ea, mcdba, mcsa
product manager, solarwinds
microsoft mvp - software distribution (2005-2012)
mvp profile: http://mvp.support.microsoft.com/profile/lawrence.garvin

Windows Server  >  WSUS