Multiple addresses for a standard sender?
I'm designing ConfigMgr 2007 SP2 address structure for a large organization with 100+ remote sites using a variety of WAN technologies (Microwave/VSAT/Point-to-Point VPNs). Some of these connections are slow links and/or high latency. The client's requirements are to prioritize new client discovery and hardware inventory over other site-to-site communications. I would like to utilize data prioritization for this versus using pulse modes since this will slow down all traffic. But I believe I am getting conflicting information from other architects and TechNet on the right approach. According to TechNet (http://technet.microsoft.com/en-us/library/bb693508.aspx), "It is possible to create more than one address for a specific sender to communicate with the same site. Address properties also allow prioritization of site-to-site communications. For example, you can set one address to a site to throttle low-priority data transfers, and another address to the same site to schedule high-priority site-to-site data transfers at different times of the day." This quote (http://technet.microsoft.com/en-us/library/bb632857.aspx)(and our lab testing) seems to me to say there can be only address per sender type: "Configuration Manager 2007 addresses are used by senders to find the site servers of destination sites. You can create several types of addresses, each of which corresponds to a different type of sender." When I attempt to create a new address within the admin console to an existing site code (with a pre-existing standard sender) and provide the NetBIOS or FQDN for that server, I receive an error stating that the SMS_SCI_Address instance already exists. Am I encountering a bug or am I mistaken about how multiple addresses work or how they are implemented? I can't really see how to utilize data prioritization/scheduling without them. I would also appreciate any advice from those of you out there managing remote sites over slow links. By the way, our expected distribution point footprint is expected to be 3TB to start, and 6TB within 5 years. :-) Thank you in advance! - Jon Connery
May 20th, 2010 4:43am

I think I understand what you are trying to achieve, just not sure whether it can be done. Afaik, there is no way of giving certain replication data a higher precedence than other replication data. "Everyone is an expert at something" Kim Oppalfens Configmgr expert for lack of any other expertise. http://www.scug.be/blogs/sccm
Free Windows Admin Tool Kit Click here and download it now
May 21st, 2010 12:18pm

10% is the lowest max transfer rate per hour. However, if that site's NIC is on a 1Gbit ethernet segement that equates to 100Mbit which may still overwhelm our 4mbit WAN link. That's not the way it works. See http://social.technet.microsoft.com/Forums/en-US/configmgrgeneral/thread/883ce15c-0c48-46d9-b192-e0d9694ee96d for additional information.
May 21st, 2010 12:40pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics