WSUS server in DMZ?

Why do you want to put WSUS into DMZ? DMZ is for services available for outside. Put WSUS into your internal network. It is the place for it. You will not have problems with a firewall either.

Agreed. WSUS belongs in the internel network, not the DMZ where it's publicly available.

I don't want to place my internal WSUS server into the DMZ, but I would like to control what updates my users receive while in the field. There have been too many cases where an update from MS has broken one of our systems and we're not able to address it when the user is half way around the world. I'm not aware of a way to do this without a WSUS server; if there is a way to do please enlighten me.

I would like to have a secondary WSUS server located in the DMZ strictly for these remote users I want to do so without opening any ports from the DMZ into my internal network.

More specifically I'm looking for a way to synchronize the approvals from the internal to the external server.  

You need to deploy WSUS on Replica mode:

http://technet.microsoft.com/en-us/library/cc720448(WS.10).aspx

downstream and upstream server.
depends on you config; allow https(s) from DMZ to internal..

Many thanks gentlemen. The disconnected network configuration looks appealing. Is there a way to use that configuration with the meta data only?

Just skip step 2 :)

Why don't you want to copy updates? Do you want to download them twice from the Internet?

I want my clients to connect to the MS site for retrieving the windows updates, not the local WSUS server in the DMZ. My bandwidth is provided by a co location facility and we pay for overages - I'd rather our users not be retrieving publicly available files on our dime.