I didn't see the CAS in the diagram (was just reading the text), but yes, it's valid to question that. Don't do a CAS!!!
J From: [email protected] [mailto:[email protected]] On Behalf Of Roland Janus Sent: Wednesday, June 3, 2015 8:25 AM To: [email protected] Subject: RE: [mssms] RE: SUP and Group Policy And you didn't ask about the CAS?? :) From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Mittwoch, 3. Juni 2015 15:12 To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: SUP and Group Policy Yes, however there is no need to explicitly set the WSUS instance to use as the ConfigMgr client agent will do this for you. Also remember that update (binaries) do *not* come from WSUS when integrated into ConfigMgr. J From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of David McSpadden Sent: Wednesday, June 3, 2015 7:32 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] SUP and Group Policy When I had WSUS at my branches I had GP for each branch and set the clients to pull the updates from the local server and report to the upstream server. Now I am trying to implement Secondary Sites with SUP at each site. Can I use the same GP or do I do something different with CM12r2sp5 in place. C AS SC1 (All roles applied) Primary site | //|\\ / / | \\ / / | \ \ / | | | \ | | | | | S01 S02 S03 S04 S05 (MP,SP,DP) roles applied. (secondary sites over a less than nice T1) David McSpadden Systems Administrator Indiana Members Credit Union P: 317.554.8190 | F: 317.554.8106 [Description: imcu email icon]<http://imcu.com/> [Description: facebook email icon] <https://www.facebook.com/IndianaMembersCU> [Description: twitter email icon] <https://twitter.com/IndMembersCU> [Description: email logo] [mcp2] 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.
