I have 2 WSUS servers on 2 different networks. WSUS Server A is connected to the internet and WSUS Server B is NOT. WSUS Server B has not been able to download updates recently because of issues with the Upstream Server on that network (beyond our control). Instead of waiting for them to fix the issue on their end, we'd like to maintain patching on this network..
Is there a way I can manually export the data/patches from WSUS Server A and import it into Server B? Is it easy as exporting the database and importing it in? Or is it more complicated than that??
And if I can't do that, is there anyway I can manually download the patches themselves and somehow make it available to our disconnected WSUS server for deployment?
Server A is a Windows 2003 Server, WSUS 3.0 SP1
Server B is a Windows 2008 Server, WSUS 3.0 SP1
.. And is there issues if one is a 2003 server and the other is 2008??
Our Dev teams are like yours. They’re continually cranking out code for new features/bugs fixes, testing, deploying, testing some more, responding to production monitoring events and more. It’s complex. So, we thought you’d like to see what’s working for us.
You might have come across a situation when you have Exchange 2013 server in two different sites (Production and DR). After adding the Database copy in ECP console it displays Database copy status unknown for the DR exchange server. Issue is strange…
This tutorial will show how to configure a new Backup Exec 2012 server and move an existing database to that server with the use of the BEUtility.
Install Backup Exec 2012 on the new server and apply all of the latest hotfixes and service packs. The…
This tutorial will walk an individual through setting the global and backup job media overwrite and protection periods in Backup Exec 2012.
Log onto the Backup Exec Central Administration Server. Examine the services. If all or most of them are stop…