I have a script that I need to run daily (via Package/Program deployment). Not a problem, set it to always re-run & it does it fine at scheduled times. But on weekly basis the script changes (version number inside). I can re-distribute it & add another schedule, but the new .bat never makes to the client from DP Client keeps re-running the existing (by now old) local cache .bat Only way I found is to re-create whole Package/Program & deploy it again. But I find it rath

Question... Once i import the patches into packages do I need to retain the patch files that were down loaded from MS?

Hi experts, We have been experiencing some issues with our SCCM CB infrastructure. Completed about a week of troubleshooting and another week with Microsoft with no resolution. We have decided to to build a new server and decommission the old one.  My current setup is Windows Server 2012 R2, SQL 2012, and CD 1706 for my primary site with 5 DPs I have decided to go with Windows 2016, SQL 2016 and CB 1802 for the new build. Everything will remain same (roles, site code etc.) My

We are mostly a HP shop here.  I'm running SCCM 1802 (latest w/patches).  I have been contemplating installing the HP MIK kit in my SCCM environment.  For those who have it or have used it...is it worth it? I like the idea of updating the drivers much easier and the option for BIOS updates, but any 3rd party solution that integrates directly into an existing application is always something to be concerned about.  Just looking for some guidance.  Thanks.

I noticed this morning (after patch tuesday) that some patches were missing on our SUP. Furthermore, SMS_WSUS_SYNC_MANAGER had this weird error: WSUS Synchronization failed.  Message: ImportUpdateError: .  Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS.   And wyncmgr.log had this: Sync failed: ImportUpdateError: . Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS

I ran a software syn update and now I have this strange error on my SCCM sever. Has anybody seen this and know what causes this?  This has caused the system health on COMPONENT_MANAGER AND DISTRIBUTION_MANAGER to be critical   On 2018-06-13 05:13:21 PM, component SMS_WSUS_SYNC_MANAGER on computer <myserver> reported:   WSUS Synchronization failed.  Message: The operation has timed out.  Source: Microsoft.UpdateServices.Internal.DatabaseAccess.ApiRemotingCompressionProxy.

I’m having issues capturing an image I built of a windows 10 1803 machine, it fails every time with error 0x00004005.  This seems to be an ongoing issue I had the same problem with 1709 and I was hoping that Microsoft would have fixed this before putting out the next successor.  Oddly enough If I install windows 10 1607 without updating capture works fine, but once I bring it to the 1700’s or 1800’s level everything goes to hell, I’ve tried disabling the apps, I also ensured that the NAA had acc

Not sure if this is a bug in SCCM 1802 or if it is a new "feature" but I am seeing it in the production environment and also my lab. Anyone else notice this and any idea what may be going on?   When looking at the "Devices" collection, all the columns for Primary User(s) , Last Logged on User, and Last Logon Timestamp show data correctly.    When I create a new collection, for example a Windows 10 Workstations and add Primary User(s) , Last Logged on User, and Last Logon Time