I was doing some research on the rate limiting features recently and found a really great article that broke each option down very thoroughly.
From: [email protected] [mailto:[email protected]] On Behalf Of Roland Janus Sent: Tuesday, October 15, 2013 6:49 AM To: [email protected] Subject: RE: [mssms] Tips to conserver bandwidth in SCCM 2012 Weekly inv is probably not current enough. That amount of traffic is not the killer, especially since it is delta. The killer is always content and QoS would help not killing the network, but not reduce the amount of content. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Justin P. White Sent: Dienstag, 15. Oktober 2013 14:47 To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Tips to conserver bandwidth in SCCM 2012 Thanks for the tips! We haven't had a meeting on setting the frequency of these policy refreshes, ect. But I would say that a weekly inventory and a daily/12hr policy retrieval is likely to come out from them. Compliance rules and scans will also be on the table later on. I totally agree with keeping the components to a minimum. This gives me more confidence moving forward, thanks again! Justin White DAK Americas LLC.- Cooper River Site Infrastructure Technology 3350 Cypress Gardens Road Moncks Corner SC 29461 (843)797-9190 [O] (843)709-0152 [C] [email protected]<mailto:[email protected]> www.dakamericas.com<http://www.dakamericas.com/> From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Trevor Sullivan Sent: Tuesday, October 15, 2013 8:28 AM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Tips to conserver bandwidth in SCCM 2012 Justin, How frequently do you plan to perform policy refreshes on Configuration Manager clients? How often are you planning on performing hardware and software inventories, software updates scan cycles, compliance rule reporting, and so on? These are all factors that will play into your decision to implement a Secondary Site as well. If you configure the above-mentioned intervals low enough (eg. Inventory every 5 days, policy retrieval every 4 hours), don't have a lot of compliance rules, and have infrequent compliance rule scans, then you could probably get away with having just a Distribution Point in that site. Secondary Sites are generally just extra components (including its own database) waiting for something to go wrong. Wherever possible, try to limit the number of infrastructure components, and your life will be made much easier. As it stands right now, with the information that I have been made aware of, I don't think there's a very strong justification for needing a Secondary Site. Cheers, Trevor Sullivan From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Justin P. White Sent: Tuesday, October 15, 2013 7:16 AM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Tips to conserver bandwidth in SCCM 2012 The remote site has about 200 clients. By RDC, I mean Remote Data Center Sorry I meant to say its just a Primary Site. When I mentioned 'central' it was just to say that its central geographically. Justin White DAK Americas LLC.- Cooper River Site Infrastructure Technology 3350 Cypress Gardens Road Moncks Corner SC 29461 (843)797-9190 [O] (843)709-0152 [C] [email protected]<mailto:[email protected]> www.dakamericas.com<http://www.dakamericas.com/> From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Trevor Sullivan Sent: Monday, October 14, 2013 1:51 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Tips to conserver bandwidth in SCCM 2012 I don't see this mentioned anywhere, but how many clients are in this remote site? If there's only one client in the location, then you probably don't need a Secondary Site or a Distribution Point, because content will only get downloaded once anyway. On the other hand, if you have 1,000 clients behind a 1.5Mbit/sec pipe, then you'll probably need a Secondary Site (and Distribution Point) in that location to proxy management traffic and handle content distribution. FYI, there is no such thing as a "Central Primary Site Server" in ConfigMgr 2012. There is a Central Administration Site (CAS), or Primary Site, or Secondary Site. I'm not sure what you mean by "RDC." That could potentially mean: Remote Different Compression, which is a service provided by the operating system, or it could mean a Read-only Domain Controller. Or does it maybe mean "Remote Datacenter," since you referenced that a couple of times? Cheers, Trevor Sullivan From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Justin P. White Sent: Monday, October 14, 2013 10:26 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] Tips to conserver bandwidth in SCCM 2012 Hi, I'm on the testing phase of integrating a site with low bandwidth into our SCCM environment. Looks like their WAN speed clocks in around 1.5mb to give you guys an idea. I have installed a distribution point and a management point active on their local server. We have a central primary site server on our remote data center that talks to it. Should I try to just set up a secondary site instead? Or just use the bandwidth throttling in BITS to contain the amount of traffic being sent to our RDC? How would you guys approach integrating a low bandwidth site? Does having that Management Point installed locally automatically control the clients to use that management point or will it try to talk over the WAN to the management point set up at my RDC? Justin White DAK Americas LLC.- Cooper River Site Infrastructure Technology 3350 Cypress Gardens Road Moncks Corner SC 29461 (843)797-9190 [O] (843)709-0152 [C] [email protected]<mailto:[email protected]> www.dakamericas.com<http://www.dakamericas.com/> ________________________________ Please consider the environment before printing this email. This message and any attachments may contain privileged, confidential, or copyrighted information property of the sender. The information is intended only for the use of the person to whom it was addressed. Any interception, copying, accessing, or disclosure of this message and its attachments are prohibited. The sender takes no responsibility for any unauthorized reliance on this message. If you have received this message and/or attachments in error, please immediately notify the sender via e-mail and purge the message you received. Do not forward this message without written permission. This message is not intended as an offer, or acceptance, or amendment of a contract. Este mensaje y sus anexos pueden contener información confidencial, privilegiada o protegida bajo derechos de autor propiedad del emisor. La información enviada es para el uso exclusivo del destinatario. Cualquier intercepción, copiado o acceso a este mensaje y anexos están prohibidos. El emisor no es responsable por el uso no autorizado de este mensaje. Si usted recibió este mensaje y sus anexos por error, le suplicamos se lo notifique al emisor via correo electrónico y borre el presente mensaje y sus anexos de su computadora sin retener una copia de los mismos. No tranfiera este mensaje sin permiso expreso del emisor. Este mensaje no constituye una oferta, aceptación o modificación a un contrato. This message and any attachments may contain privileged, confidential, or copyrighted information property of the sender. The information is intended only for the use of the person to whom it was addressed. Any interception, copying, accessing, or disclosure of this message and its attachments are prohibited. The sender takes no responsibility for any unauthorized reliance on this message. If you have received this message and/or attachments in error, please immediately notify the sender via e-mail and purge the message you received. Do not forward this message without written permission. This message is not intended as an offer, or acceptance, or amendment of a contract. Este mensaje y sus anexos pueden contener información confidencial, privilegiada o protegida bajo derechos de autor propiedad del emisor. La información enviada es para el uso exclusivo del destinatario. Cualquier intercepción, copiado o acceso a este mensaje y anexos están prohibidos. El emisor no es responsable por el uso no autorizado de este mensaje. Si usted recibió este mensaje y sus anexos por error, le suplicamos se lo notifique al emisor via correo electrónico y borre el presente mensaje y sus anexos de su computadora sin retener una copia de los mismos. No tranfiera este mensaje sin permiso expreso del emisor. Este mensaje no constituye una oferta, aceptación o modificación a un contrato. This message and any attachments may contain privileged, confidential, or copyrighted information property of the sender. The information is intended only for the use of the person to whom it was addressed. Any interception, copying, accessing, or disclosure of this message and its attachments are prohibited. The sender takes no responsibility for any unauthorized reliance on this message. If you have received this message and/or attachments in error, please immediately notify the sender via e-mail and purge the message you received. Do not forward this message without written permission. This message is not intended as an offer, or acceptance, or amendment of a contract. Este mensaje y sus anexos pueden contener información confidencial, privilegiada o protegida bajo derechos de autor propiedad del emisor. La información enviada es para el uso exclusivo del destinatario. Cualquier intercepción, copiado o acceso a este mensaje y anexos están prohibidos. El emisor no es responsable por el uso no autorizado de este mensaje. Si usted recibió este mensaje y sus anexos por error, le suplicamos se lo notifique al emisor via correo electrónico y borre el presente mensaje y sus anexos de su computadora sin retener una copia de los mismos. No tranfiera este mensaje sin permiso expreso del emisor. Este mensaje no constituye una oferta, aceptación o modificación a un contrato.
