We have a test/integration environment (rig) running Windows HyperV with server VMs inside it.

I'd like to manage patches in the rig (the hyper V hosts and the VMs inside, which are all on their own domain) but we cannot connect the rig to the internet (or even our corporate network) due to security issues.

Is it possible to download the patch info for WSUS (or whatever technology/application is appropriate) from a browser and then load it into the rig manually? If not, do you have recommendations for managing patches on a server that is disconnected (and cannot, ever, under any circumstances be connected to the internet or corporate network)?

  • 1
    Please be more descriptive with your question. What does "rig" refer to? The WSUS server? The physical host? The VMs? The whole infrastructure? – MDMarra May 24 '13 at 1:17
  • Updated my question, I want to manage the whole infrastructure via WSUS and maintain patches. I don't know whether this is possible and my googling hasn't been very enlightening to whether this is a supported scenario. – Spence May 24 '13 at 1:26
  • Did anyone actually read the other question? It's not answered and it's not asking what I'm asking. It's alluding to the solution of my problem in their /question/ and does not actually answer it at all. – Spence May 24 '13 at 3:30

Your options so far:

Note that a WSUS server, even when online, can be configured to present basically negligible security risk to your domain. It can be placed in the DMZ, the clients do not need to be in the same domain as the WSUS server and update signatures are checked by the clients against Microsoft's public keys, so it should be impossible to forge updates as long as the corresponding private keys are not subverted (which would pose a problem no matter if you are using WSUS to install updates or not). So you could set up an onlined WSUS server and set up your test network's filters to allow nothing but HTTP/HTTPS connections to this server without compromising security.

  • Your second option is pretty much the only solution here. – Spence Sep 16 '16 at 0:02

The Configure a Disconnected Network to Receive Updates chapter in the WSUS documentation describes the officialy supported way to use WSUS in a disconnected environment. You need to have a second WSUS installation which can download updates from Microsoft servers.

First you need to synchronize the metadata on the connected WSUS server; then you must make it download the update files in some way (e.g., by approving updates for some dummy group). After doing this you need to export metadata from the connected WSUS server:

 wsusutil.exe export packagename.cab logfile.log

Then transfer packagename.cab and everything in the WsusContent folder to the disconnected WSUS server, and import metadata there:

 wsusutil.exe import packagename.cab logfile.log

Wait while WSUS validates the update files, then work with it as usual (approve updates, etc.).

The main problem with this workflow is that there seems to be no way to transfer approvals between the disconnected WSUS server (where you can see what updates are required by clients) and the connected WSUS server (where you need to download updates).

Also see this article, which describes a recent update for the WSUS server; this update removes the 2 GB limitation on the export file size, which can be exceeded if you synchronize updates for lots of products. The update changes the export file format from CAB to gzipped XML, which does not have a 2 GB limitation.

  • Thank you for reading then answering the question. I think some people forget that the enterprise exists and there are scenarios where connecting systems to the internet isn't about Mordac saying no.... – Spence Sep 16 '16 at 0:01

You cannot connect it to "the internet" due to unspecified security issues, but surely you can create a firewall rule allowing only the WSUS server to connect only to Microsoft Update servers, followed by an explicit deny any/any rule. If your colleagues/superiors believe that there is a reasonable argument against this, we would like to hear it.

  • when the government writes the security rules, you can't change them... – Spence May 24 '13 at 8:35
  • @spence Too bad. The rules seem to make little sense in this case. – the-wabbit May 24 '13 at 15:35

In principle the following might work: Create a WSUS server and regularly

  1. plug it into a LAN with internet (or internal upstream WSUS) access and sync it.
  2. down and unplug it and carry it to the security lan
  3. connect it there and let clients update and report

You may have a considerable delay in upgrades because it may take a few back and forth movements antil this mobile WSUS learns which of the updates are actually needed and should be downloaded.


I have an isolated network and run into the same issues. Now that our WSUS (Server2008R2 STD) won't export \ import the .cab file because it's greater than 2GB. There's no cleaning mine up... I need to provide 9,000+ updates to a classified, isolated network... I use VMwarePlayer and create a virtual Server2008R2 WSUS give it plenty of virtual drive space 150+GB then after a couple days of the virtual WSUS server collecting the updates I put the VMwarePlayer and machine on the network via sacrificial 500GB usb portable hard drive. I join the virtual server to the domain and make it the upstream WSUS. Then I change the actual WSUS to be the downstream server. After they sync\update\download (a day or so) I shutdown and delete the virtual WSUS then change the real WSUS back to the Upstream server. run gpupdate /force on all the workstations in the WSUS pool and they begin updating. This is a quarterly process, so we do a VERY LARGE update initially to these isolated systems, then the quarterly updates can be done the same way (if you want) or clean up the WSUS files and just go back to doing the wsusutil.exe export \ import with .cab files smaller than 2GB.


O totally understand where you are coming from and I have a similar situation. We have an isolated patch test rig to test updates and approve them prior to deploying in production.

So this is situation:

  1. Live environment has no internet access
  2. Test rig (ESXi environment hosting a domain environments on vms with 1 sccm server) has no internet access.
  3. WSUS server connected directly to internet.

Our plan:

  1. Download and approve updates on WSUS.
  2. Export downloaded approved updates/metadata (possibly using WSUSutil)
  3. Copy exported metadata and WSUSContent to removable hard disk.
  4. Import data into test rig environments SCCM server.
  5. Deploy to environment for testing.
  6. Approval after testing to implement in production.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.