I want to throttle and schedule bandwidth from my primary site to my DP's and remote location. What do I need to do ? create secondary site and add DP role and use no_sms_on_disk files for controlling the location of the DP. create secondary site and optional create Server Share so i can control where to place the DP location or ? I am a bit confused and am wondering if with option 2 bandwidth throttling can be used or not ?

just do number 1 and set the restrictions in the sender address. John Marcum | http://myitforum.com/cs2/blogs/jmarcum |

You can do both as long as you install the DP in another site or install a Branch Distribution Point.Kent Agerlund | http://scug.dk/ | The Danish community for System Center products

You can do both as long as you install the DP in another site or install a Branch Distribution Point. Kent Agerlund | http://scug.dk/ | The Danish community for System Center products So if i create a Secondary Site and in that site i create a "Server Share" DP with a predefined share, then packages send to the DP Server Share will be controlled (bandwidth throttling and scheduling) by the site-to-site connection ? Are there pros or cons of using Server Share DP instead of normal DP ?

Hi, Packages send to the secondary site can be controlled and compressed. For pros and cons check http://technet.microsoft.com/en-us/library/bb892801.aspxKent Agerlund | http://scug.dk/ | The Danish community for System Center products

Hi, Packages send to the secondary site can be controlled and compressed. For pros and cons check http://technet.microsoft.com/en-us/library/bb892801.aspx Kent Agerlund | http://scug.dk/ | The Danish community for System Center products Last check..i want to be sure that it works as i think it should be: When I create a remote Server Share DP on a remote server, then files are copied using SMB. When I then make that server a secondary site and do not make any changes to the Server Share DP on that server, the files will be copied accross the site-to-site link ?

It does not make sense to create a DP share first and then installing a secondary site. That DP share needs to be a site system of an existing site (most likely an existing primary in your scenario). Installing a secondary on top will result in having a server that shares roles for different sites (-> unsupported)! Site to site -> sender -> throttling, compression, scheduling Site server to site system -> SMB

It does not make sense to create a DP share first and then installing a secondary site. That DP share needs to be a site system of an existing site (most likely an existing primary in your scenario). Installing a secondary on top will result in having a server that shares roles for different sites (-> unsupported)! Site to site -> sender -> throttling, compression, scheduling Site server to site system -> SMB That is exactly my point and I want to be sure that evenryone does understand me....not I guess. My situation: I have a primary site and a secondary site. On the secondary site I create an additional Windows share and create a Server Share within SCCM. This comes up within the console as a Distribution Point and a Site System role. I would guess then that the communication from my primary to the DP is SMB traffic. When I add on the secondary site the Distribution Point role then that role comes up within the console as a Distribution Point, Site System, Site Server and Component Server role. I would guess then that the communication from my primary to the DP is by the sender. Am I right ? If I am right that mean that having a secondary site AND a Server Share DP (to be able to controll the location) on the same server, the communication to the DP is SMB traffic although you will expect sender traffic.

My situation: I have a primary site and a secondary site. On the secondary site I create an additional Windows share and create a Server Share within SCCM. This comes up within the console as a Distribution Point and a Site System role. I would guess then that the communication from my primary to the DP is SMB traffic Which site does that DP belong to? When I add on the secondary site the Distribution Point role then that role comes up within the console as a Distribution Point, Site System, Site Server and Component Server role. I would guess then that the communication from my primary to the DP is by the sender. So you've got a secondary site that also hosts a DP for the primary site? That's (a) not supported and (b) makes no sense (just get rif of the primaries DP and create a DP for the secondary). If you want to place a DP at the other end of a WAN link (depending on the number of clients etc): set up a secondary site there that also got a DP (that belongs to that secondary). If I am right that mean that having a secondary site AND a Server Share DP (to be able to controll the location) on the same server, the communication to the DP is SMB traffic although you will expect sender traffic. It's SMB if the DP (or DP share) does belong to the secondary site. No sender involved, because - again - senders are only used between sites.

My situation: I have a primary site and a secondary site. On the secondary site I create an additional Windows share and create a Server Share within SCCM. This comes up within the console as a Distribution Point and a Site System role. I would guess then that the communication from my primary to the DP is SMB traffic Which site does that DP belong to? The DP belongs to the secondary site When I add on the secondary site the Distribution Point role then that role comes up within the console as a Distribution Point, Site System, Site Server and Component Server role. I would guess then that the communication from my primary to the DP is by the sender. So you've got a secondary site that also hosts a DP for the primary site? That's (a) not supported and (b) makes no sense (just get rif of the primaries DP and create a DP for the secondary). If you want to place a DP at the other end of a WAN link (depending on the number of clients etc): set up a secondary site there that also got a DP (that belongs to that secondary). No the secondary site host the DP for the secondary site. If I am right that mean that having a secondary site AND a Server Share DP (to be able to controll the location) on the same server, the communication to the DP is SMB traffic although you will expect sender traffic. It's SMB if the DP (or DP share) does belong to the secondary site. No sender involved, because - again - senders are only used between sites. Still I don't understand it completely....to much miscommunication I guess....maybe I need to draw something of post some screenshots from my management Console....

You create a package on the parent primary site. You then assign it to a DP of the secondary child site. Parent site compresses the packages and sends it down to the secondary (using the sender). The secondary site receives the compressed package files, decompresses them and copies it to its DP using SMB. That's it.

Ok perfect... I need to implement 600 secondary sites with on that same seconday site server a DP SHARE. Does someone know if there are scripts to create such automatically ? I saw some script related to SMS2003...but those seems not to work :-(

There's an unattended setup available: http://technet.microsoft.com/en-us/library/bb693561.aspx or an installation initiated using the console: http://technet.microsoft.com/en-us/library/bb633289.aspx. Configuration can be done using the SDK (see the SDK subforum).

Unattended Secondary site install is possible with that way...but a DP Share not. i wil check the SDK subforum Tnx