![]() Deleting the catalog component in SCUP simply deletes the SCUP reference to the package component. For example, you could have an Active Directory Server define the managed domain anything outside that domain will not be managed by my SCCM server.ĭo not delete SCUP catalog components. If you accidentally choose the wrong date or use the wrong UTC date setting, updates won’t be issued in the managed client.ĭefine boundaries for the managed environment.Įnsure all your managed clients are hosted within the desired domain, and that clients that should not be managed similarly are outside of that domain. Once an update has expired, it will no longer be offered by the SCCM client. Always refresh using the Refresh link or context sensitive menu item.Ĭonsider whether or not you should mark an expiration time (deadline) for publication. ![]() Refresh often: Often once a task completes, updates may not appear in the various UI components and you may not see changes take affect. Doing so ensures the WSUS and Configuration Manager Console gets synchronized. Run Synchronization), some operations are batch processes that run in the background and take some time to complete.Īlways Run Synchronization after integrating a SCUP catalog. Verify patch installation on the intended target for a manual install first (outside SCCM context).ĭon’t test deployments during SCCM server changes.īe patient: While operations appear to return UI control back to the user immediately (i.e.
0 Comments
Leave a Reply. |