Yep-same and then we let stats roll up. Also, not sure what your AD is like but although I originally had WSUS policies applied to OUs, I eventually made them the only site-level policies we had assigned. It worked a lot better, as if someone goes to another branch/location and plugs in (say with a laptop), they get directed to the local WSUS server rather than getting update errors.
For example, before the change it was a big problem for our techs when imaging, as much of that is done in our central office. The tech would drop the machine in the destination ou and then WSUS wouldn't get any more updates until they went onsite (or clicked to go straight to Microsoft). After assigning WSUS per AD site, those issues went away. -Bonnie From: [email protected] [mailto:[email protected]] On Behalf Of David McSpadden Sent: Wednesday, April 23, 2014 9:20 AM To: [email protected] Subject: [NTSysADM] RE: WSUS tutorial So your reporting and stats servers were always the same, policy(OU) Dependant. I will modify a couple tonight and see if they play better. Thanks From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Miller Bonnie L. Sent: Wednesday, April 23, 2014 12:13 PM To: [email protected]<mailto:[email protected]> Subject: [NTSysADM] RE: WSUS tutorial Hmm... we used to have a similar setup with 2003/2008 and a lot of secondary servers. The only thing I see different from what we used to do is that the statistics server was always the local/downstream WSUS box. Then in the WSUS configuration of the master server, we set the reporting to roll up from the downstream servers (options, reporting rollup). I've never tried it the way you have described, so don't know if that should work. -Bonnie From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of David McSpadden Sent: Tuesday, April 22, 2014 6:13 AM To: [email protected]<mailto:[email protected]> Subject: [NTSysADM] WSUS tutorial Ok feeling real kind of dumb. Everytime I go to work on this something gets goobered up and I quit. New day. I have a WSUS 2012 as my Upstream server and it updates from Microsoft. I have a test group associated with it. I have a GPO that has it as the update server and stat server. That part is good. Even approved and pushed out some updates this way. Now the funky part. Adding 2008 and 2003 replica servers at 24 branch (T1 connected) locations. I have 1 group per each location. (all the pc's and servers have an OU in AD for that location.) I have a GPO per OU that has the Replica server as the update server and the above WSUS 2012 as the Stat server. The pc's and servers in the OU are detected but do not report. So what the hell.... I have tested getting to the iuident.cab and wuident.cab at each OU with success. But no dice getting these pc's and servers in the WAN OU's to report back or fall into their correct group in WSUS. Just want to get this working so I can take it off my plate. Thanks for the immediate bashing and hassling and then the actual help later. This e-mail and any files transmitted with it are property of Indiana Members Credit Union, are confidential, and are intended solely for the use of the individual or entity to whom this e-mail is addressed. If you are not one of the named recipient(s) or otherwise have reason to believe that you have received this message in error, please notify the sender and delete this message immediately from your computer. Any other use, retention, dissemination, forwarding, printing, or copying of this email is strictly prohibited. Please consider the environment before printing this email. This e-mail and any files transmitted with it are property of Indiana Members Credit Union, are confidential, and are intended solely for the use of the individual or entity to whom this e-mail is addressed. If you are not one of the named recipient(s) or otherwise have reason to believe that you have received this message in error, please notify the sender and delete this message immediately from your computer. Any other use, retention, dissemination, forwarding, printing, or copying of this email is strictly prohibited. Please consider the environment before printing this email.
