none
Autodeployment of system updates and auto download to DP

    Question

  • SCCM 2007 had option on it if client requires some update and update is not found on it's local BDP, BDP intiates update download from central server. BDP do not exist anymore, so i'll call them DP and i can't find that option in 2012.

     

    When i create autodeployment rules or even software update package, i have to select DP on which i want to send the package. In my case where i have only 2Mbit link to Secondary server which is DP and if i have 30 DP under secondary SCCM server each connected with 512k link (all belonging to a secondary site server) when i select those 30 DP, primary server will start to send package to those 30 DPs and then cause congestion on the 2Mbit link. What i want is that package is sent to Secondary server 1st and then distributed to 30DPs under it. Is this possible and how?

    Wednesday, November 14, 2012 2:26 PM

All replies

  • I haven't explicitly used this, but there is an On-Demand Content Distribution feature in 2012 also: http://technet.microsoft.com/en-us/library/gg712321.aspx#BKMK_OnDemandContent

    Jason | http://blog.configmgrftw.com

    Wednesday, November 14, 2012 2:56 PM
  • I've not used remote DP'd prior to 2012 and I have not used remote DP's off a secondary site in 2012 but logically I'd think the network traffic would follow your heirarchy. I'd think it would go to the secondary site, get uncompressed then off to the DP's.

    In 2007 you could use the addresses to define the traffic flow from site-to-site. In 2012 they added throtteling to remote DP's but not full fledged sender addresses so I don't see a way to define that flow. If it doesn't work out of the box I'd think that the only way to do this, and I hate to say it, would be use a child primary below a CAS.


    John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|

    Wednesday, November 14, 2012 6:40 PM
  • Thanks for the answers. I tried today to create software update package for a remote computer at remote branch which has local DP. When i was deploying the package to DP, selected only Secondary server and later on the package selected option "Distribute this content to preferred distribution point". Now with package deployment tool from system center 2012 toolkit i can see that package is assigned to the client computer but download to local DP is not happening (don't see anything in log). Also when i refresh machine policy on end computer, scan for available software updates don't see download initiated. 
    Thursday, November 15, 2012 12:07 PM