SCCM Software Update Basics | Troubleshooting Technics |Tips by Kannan HTMD Live Ep #2 | ConfigMgr

preview_player
Показать описание
SCCM Software Update Basics | Troubleshooting Technics |Tips by #Kannan HTMD Live Ep #2 | ConfigMgr

How to get started with Software Updates/Patching?
What is the Architecture of Software Updates/Patching infrastructure of SCCM?
How to Configure patching infra in the SCCM world?
What are the top tasks of SCCM patching?
What is the core concept of ConfigMgr Patching?

👉5th April 2020 Device Management Live Event
========
More Blog posts related to SCCM/Intune/Windows 10/Hyper-V/Cloud/IT Pro/Azure -

#SCCM #ConfigMgr #SCCMVideos #SCCMTutorials #SCCMStudyVideos #SCCMFreeTraining #SCCMTraining #HowtoManageDevices
Рекомендации по теме
Комментарии
Автор

Good content but don't allow it to be interactive in the future. All the questions mid presentation took away from the content. They pulled the discussion away from the real presentation.

NeilNatic
Автор

What are the reasons of pathces moving to superseded mode??

bhavithd
Автор

The Installation Source for this product is not available verify that the source exists and that you can access it


how to fix this error please tell me

Application deployment error

jakeersyed
Автор

Hi Anoop,


I got question which is related to Protected DP (feature in 2007 SCCM).

Site server A - Primary site with roles for DP, MP and SUP
Site server B - DP role only

There are boundary groups for each site. Boundary group for server A has only the secondary site server defined. Boundary group for server B has both server A and B defined in the references tab. Apparently this configuration was chosen because if you don't have the server A in Boundary group B then the machines from Boundary B does not scan against WSUS at all. At the moment this works, but now we are seeing machines from Boundary group B using the DP from Server A where the secondary site is. This seems logical as you are effectively giving Boundary B more than one DP site server, but we need to restrict boundary B to use only the local DP.

What is the best way to achieve this? I am thinking of doing the following:

On boundary group B remove server A from the references tab. Then on the Relationships tab add a Fallback Boundary Group to Boundary A and tick the option for Never Fallback for the distribution point, but leave the Software Update Point Config as is. Will this still allow machines in boundary B to use the SUP in boundary A (secondary site), but not the DP in boundary A?

callvirender