SCCM design consideration
Hey there I have an sccm system to design. The infrastructure is like following We have to major Data Centres which we can call DC1 and DC2 and to both of them we have branch offices connected by fairly reliable connections. to each one of them is approximately connected 15 sites SCCM server is called SC001 Im looking into deploying SCCM with Software dist and OSD (of course HW ans SW inventory as well) Additionaly to that one there is a DFS which we can call COMPANY.COM which is distributed to all branches. All software is located in COMPANY.COM\Software All images are on COMPANY.com\Images All Windows Instalklation files are on COMPANY.COM\OSD_Source The current plan is to create one major site with one MP and DP with PXE and WDS in all the locations so OSD would be running without any problems. Questions now are : 1) is it a good consideration ? 2) Since every DP would be on server hosting DFS is there any point of making thyem DP ?. So is there sense to do it that way ? Or just to use DFS root namespace for root of the packages and OSD images (since all of them will be replicated if changes occur) because we could just make them local PXE servers responding to clients requests Thanks very much for help in this one. MCSA / MCTS
September 23rd, 2010 10:50pm

AFAIK... there's no way to use a DFS share as a DP so that option is out. I don't like remote DP's at all because you do not get sender controls to them. I'd go with secondary sites until v.Next is released. EDIT..... Microsoft Distributed File System for Distribution Points There is limited support for Microsoft Distributed File System (DFS) in Configuration Manager 2007. Distribution points can be targets of a DFS root, but packages must be deployed to the shared folder on the distribution point, not to the DFS link name. Clients can use programs that point to <DFS root>\<DFS link>\<executable>. John Marcum | http://myitforum.com/cs2/blogs/jmarcum |
Free Windows Admin Tool Kit Click here and download it now
September 23rd, 2010 11:34pm

Well now the question is is it worth to implement like 20+ secondary sites and then wait until vNext is released? Or I should just consider creating one site and create like 20+ DP with PXE ?MCSA / MCTS
September 23rd, 2010 11:45pm

IMO a secondary site is not more work to implement than a DP and it's easier to manage. I'd use seconadry sites. John Marcum | http://myitforum.com/cs2/blogs/jmarcum |
Free Windows Admin Tool Kit Click here and download it now
September 24th, 2010 5:16am

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

Other recent topics Other recent topics