Hi all,

I'm learning SCCM 2012 R2 and I have a few questions about it. So I have configured a remote Software Update Point and it is working fine. But I realised that if I create a deployement package from the updates, then (certainly) I have to choose a DP to which the package will be copied to (for distribution). I have one Primary site server which is my only DP. And here comes my questions:

1. What if I use my Primary site server as distribution point and I enter the remote site server as path for the package? Is it a supported/recommended way to ditribute updates?

2. If the 2nd option is not recommended then should I install DP role on my remote SUP?

3. If I understand right how SCCM works, I think both solutions will create 2 copies of the updates that I deploy (One in WSUS used by SUP and another on the DP for package distribution). The only difference is that in 2. case I have 2 copies on the same server. Am I right?

4. What is the best way to handle updates in case of a remote SUP (if I have only two Site Systems)? 1st or 2nd (is there a 3rd one)?

Thanks for any infos and best practices.

Kind regards,

Dvijne

• Edited by Dvijne Sunday, March 22, 2015 4:19 PM

Thank you both for making it clear to me.

@ Jason: I have created a remote SUP just to see how it could be done, there is no other reason for it. As I'm a rookie in SCCM I thought that separating the roles is more sophisticated and effective. And I didn't find the logic in storing the same updates in multiple locations on the same server. Now I understand that if I download some updates (In SCCM), then it will download these files to a folder which was set during the WSUS installation on the SUP and after that it will copy these updates to a DP (Content library).

Kind regards,

Dvijne

• Edited by Dvijne 16 hours 38 minutes ago

Now I understand that if I download some updates (In SCCM), then it will download these files to a folder which was set during the WSUS installation on the SUP and after that it will copy these updates to a DP (Content library).

No, that is not correct. As mentioned, WSUS will not download any updates (or really should not because if you directly approve updates in the WSUS console -- which you shouldn't do -- then it will download them). ConfigMgr downloads them directly from Microsoft to the package source location and then copied them from there to the content library of the primary site server.

OK. So I just double checked my test environment and now it's clear. I didn't even started WSUS console on the SUP. I always use SCCM console only. When I said WSUS I meant the integrated SUP.

So to summarize my understandings::

1. When you install WSUS binaries to a SUP (WS2012R2) then at the installation you must define a folder for the updates. This folder will be used only for metadata informations because the updates will be downloaded to the deployment package folder.

2. When this package is distributed, then the updates are copied to the Content library on every targeted DP.

Is it correct then?

(Thanks for your patience. ;) )

Kind regards,

Dvijne

• Edited by Dvijne 13 hours 2 minutes ago

#1: yes (but you don't "install WSUS binaries to a SUP". WSUS is a prerequisite for installing a SUP though)
#2: yes (given that you added every DP as a target when distributing content)

1. Correct in spirit. The update metadata is actually stored in the DB. The folder you specify during WSUS setup stores update EULAs that the WUA on clients must be able to access (most updates don't have EULAs though) along with the binaries for a handful of automatically approved updates in WSUS.

2. Correct.

Thank you Torsten & Jason.