1++
From: [email protected] [mailto:[email protected]] On Behalf Of Marcum, John Sent: Mittwoch, 3. Juni 2015 17:19 To: [email protected] Subject: RE: [mssms] RE: SUP and Group Policy Did you just say that you have less than 500 clients in this entire hierarchy???? I was really hoping you were gonna say 500,000. Man, you REALLY need to scale that back to a single primary site and some remote DP's if you are supporting 500 clients. All your traffic is going to come from the DP's. The MP and SUP traffic is very small. From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of David McSpadden Sent: Wednesday, June 3, 2015 9:57 AM To: [email protected] <mailto:[email protected]> Subject: RE: [mssms] RE: SUP and Group Policy I keep seeing that on the list but if I want the updates to be on the local branch servers how to I get it there without a secondary? What is the reason for not have secondary's at local server that are a less than perfect T1 away? Before I had to have WSUS at each location because even a small update would take the T1 down. To me it doesn't make much sense not to have the secondary at these locations. I know as far as clients go I could do it with just the primary. Less than 500 total in the entire site. But the mechanics of it dictate, to me, a primary for management and secondary's for bandwidth control? To all you big shops this would be a waste of space but just have the DP to rely on scares me. Please correct me so I can get the best implementation though. Always open for comments. From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Roland Janus Sent: Wednesday, June 03, 2015 10:33 AM To: [email protected] <mailto:[email protected]> Subject: RE: [mssms] RE: SUP and Group Policy Right, haven't thought about that. But I also wouldn't do secondaries unless you really have a lot of clients. From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of David McSpadden Sent: Mittwoch, 3. Juni 2015 16:03 To: [email protected] <mailto:[email protected]> Subject: RE: [mssms] RE: SUP and Group Policy Along with that I do not need to install WSUS on the branch servers (Secondary sites) because the SUP will add what it needs for the WSUS, that is installed at the Primary, to push down to them? From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Wednesday, June 03, 2015 9:55 AM To: [email protected] <mailto:[email protected]> Subject: RE: [mssms] RE: SUP and Group Policy 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]> [mailto:[email protected]] On Behalf Of Roland Janus Sent: Wednesday, June 3, 2015 8:25 AM To: [email protected] <mailto:[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 <http://imcu.com/> <https://www.facebook.com/IndianaMembersCU> <https://twitter.com/IndMembersCU> 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. 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. _____ Confidentiality Notice: This e-mail is from a law firm and may be protected by the attorney-client or work product privileges. If you have received this message in error, please notify the sender by replying to this e-mail and then delete it from your computer.
