Skip to Main Content
Patch My PC Feature and Application Request

A community where customers and the community can provide feedback to make a better product for everyone! For more details on how we prioritize request, please see:

1 VOTE
Status NOTED
Categories Application Request
Created by Guest
Created on Jan 6, 2020

Instead of triggering a SUP sync after publishing, create a one time scheduled SUP sync.

One of the features of running a scheduled SUP sync is the cleanup process that follows. The current option in PatchMyPC to trigger the SUP sync is not considered a scheduled sync so the cleanup does not occur. The PowerShell cmdlets are there for creating a non-recurring one-time scheduled sync in order to get the full functionality of triggering the SUP sync and getting the cleanup features too. Perhaps even having a timer option (in minutes) to set the one-time scheduled sync once publishing is complete.

  • Attach files
  • Admin
    Justin Chalfant
    Reply
    |
    Jan 7, 2020

    Ah, bummer, I don't think we would create a feature to perform a one-time schedule sync, but we do log out to Windows Event logs, and you could create a Powershell script to trigger a sync whoever you need based on our sync completed event. https://patchmypc.com/windows-event-logging-details-for-patch-my-pc-publishing-service

  • Guest
    Reply
    |
    Jan 7, 2020

    I ran a full sync and the expired cleanup process that runs after a scheduled sync does not happen. You will see the following line in the Wsync.log:

     

    Skipping Delete Expired Update relations since this is not a scheduled sync

  • Admin
    Justin Chalfant
    Reply
    |
    Jan 7, 2020

    I will do a little research, I thought a full sync would perform cleanup. If it requires us to set a schedule in your SUP we probably wouldn't make that type of one-time change.

  • Guest
    Reply
    |
    Jan 7, 2020

    Hi Justin,

    I can check whether a Full-Sync performs the clean-up process at the end but my guess is it does not. The way you are triggering the sync after publishing, is the same as if you would manually kick off a sync from within the SCCM console which will not perform the cleanup.  In order for the cleanup to occur, the Sync must be a scheduled sync. Fortunately,  the commands (cmdlets) for creating a scheduled sync are real simple which would allow you to create a one time non- recurring scheduled sync after every Publishing task. If you email me directly, I can explain this in more detail and show you what I mean.   

  • Admin
    Justin Chalfant
    Reply
    |
    Jan 7, 2020

    Hey Steve,

    I believe you are talking about how we perform a delta sync vs full sync (https://docs.microsoft.com/en-us/archive/blogs/connector_space/the-complete-synchronization-process-part-4-deltafull-importsynchronization-explained) during the SUP sync after updates are published?

    We actually added an option in the advanced tab to trigger a full-sync (Only manually available today). It sounds like you would like a checkbox to have the SUP sync perform a full sync vs. delta for the sync triggered after updates have been published?