Search the Community

Hi There, I am in the middle of a OS refresh of our estate (XP to Windows 7) and many of the sites are running 20+ machines on slow links (20mb or less) and the OS refresh must be ran outside of hours We have a very tight timescale for the OS refresh so i would like to create a protected distribution point that can be taken to these slow sides and run upgrades locally rather than pulling down the wim 20+times over a slow link. Unfortunately i only have desktop PC's i5 4GB memory at the moment to use for the DP's and plan on once the OS refresh is completed at a site, remove this DP and take it to the next site. I would like to know if i can just use Windows 7 and set this as a protected branch distribution point or if i would be best to install Server 2008 and set it up as a full DP with PXE support? The important aspect is being able to move the protected DP between sites (reassigning the protected boundary each time) SCCM 2007 SP2 R3, 1 primary site server, no secondary sites and a couple of main DP's in main sites. Thanks

Hi, we recently installed a Branch DP for a remote Site and today we got response from the IT Guy over there that OS Deployment was very slow. When looking at the logfiles we noticed that the content wasn't copied from the Branch DP, but instead it was being copied from the Secondary Site server. Both the Branch DP as the Secondary Site server are set as Protected Site System for the boundary the client falls in. What I found so far (Google) is that the client prefers to use BITS and therefore connects to the Secondary Site server instead of the Branch DP (which uses plain SMB). What is the best way to deal with this? Thanks in advance. Kind Regards, Mario