I can confirm what Brian is saying.
In my environment the WSUS and all other company wide infrastructure servers are in their own domain in our forest. Each physical site (36 across the country) has it's own domain in the forest as well, with DNS working fine across all domains as long as I use the FQDN which always ends in '.local'
I have tested the System Center Updates Publisher 2011 to deploy the same update, within it's system and the only thing I do different is that I am able to specify the FQDN in the download URL field and it does deploy the updates to the client machines across the various domains with success. But, I do not like the SCUP interface at all, and would much prefer to use WPP, even if I have to go manually make a DB edit in SQL each time.
My site is approx 8000 Windows clients and approx 400 MS servers of various 2008 and 2012 versions.
In my environment the WSUS and all other company wide infrastructure servers are in their own domain in our forest. Each physical site (36 across the country) has it's own domain in the forest as well, with DNS working fine across all domains as long as I use the FQDN which always ends in '.local'
I have tested the System Center Updates Publisher 2011 to deploy the same update, within it's system and the only thing I do different is that I am able to specify the FQDN in the download URL field and it does deploy the updates to the client machines across the various domains with success. But, I do not like the SCUP interface at all, and would much prefer to use WPP, even if I have to go manually make a DB edit in SQL each time.
My site is approx 8000 Windows clients and approx 400 MS servers of various 2008 and 2012 versions.