locked
Azure File Sync Agent + SCCM RRS feed

  • Question

  • Hu guru's

    Is it possible to 'update' the Azure File Sync agent from SCCM and if so how?

    Also, if it is supported - will updating via SCCM have any impact to the server already being onboarded to Azure File Sync (Storage Sync Services).

    thanks

    K

    Monday, April 20, 2020 3:31 PM

Answers

  • Thanks for raising this question:

    You can update the storage sync agent via SCCM. The agent updates are published as a Microsoft update KB. (As compared to a Windows update KB.)

    So, you need to configure SCCM to take Microsoft Updates into account and just patch the server on normal cadence.

    There is no need to “wait” or “evaluate” a new agent version, you can and should take the updates as they come out – they are of GA quality.

    Another way to update is to do it automatically.

    In the agent install wizard, there is an optional checkbox. You can check that, and the agent will self-apply the KB when it becomes available.

    Now to your second question: sometimes an agent update requires a reboot (really rare but it can happen).

    In these cases the agent will update (though either of you selected ways) and then still operate under the old agent bits until you reboot the server as part of your normal, scheduled maintenance cycle.

    So, the agent updates won’t cause reboots and updating an agent, even if you can’t reboot the server for a while, will not interrupt the server’s ability to sync.

    We have all bases covered

    We can also use PowerShell cmdlets to update the agent.

    It will check and apply an update on demand. You can include that even in SCCM but this really is a manual-intervention way vs. something you’d use with System center or other management software.

    This is more like an admin saying: “I don’t want to wait for regular maintenance processes and need to apply the latest KB now.” So PS is convenient, vs. manually finding the KB and applying.

    Hope this helps!

    Kindly let us know if the above helps or you need further assistance on this issue.

    ------------------------------------------------------------------------------------------

    Do click on "Mark as Answer" on the post that helps you, this can be beneficial to other community members.
    Tuesday, April 21, 2020 5:13 AM

All replies

  • Thanks for raising this question:

    You can update the storage sync agent via SCCM. The agent updates are published as a Microsoft update KB. (As compared to a Windows update KB.)

    So, you need to configure SCCM to take Microsoft Updates into account and just patch the server on normal cadence.

    There is no need to “wait” or “evaluate” a new agent version, you can and should take the updates as they come out – they are of GA quality.

    Another way to update is to do it automatically.

    In the agent install wizard, there is an optional checkbox. You can check that, and the agent will self-apply the KB when it becomes available.

    Now to your second question: sometimes an agent update requires a reboot (really rare but it can happen).

    In these cases the agent will update (though either of you selected ways) and then still operate under the old agent bits until you reboot the server as part of your normal, scheduled maintenance cycle.

    So, the agent updates won’t cause reboots and updating an agent, even if you can’t reboot the server for a while, will not interrupt the server’s ability to sync.

    We have all bases covered

    We can also use PowerShell cmdlets to update the agent.

    It will check and apply an update on demand. You can include that even in SCCM but this really is a manual-intervention way vs. something you’d use with System center or other management software.

    This is more like an admin saying: “I don’t want to wait for regular maintenance processes and need to apply the latest KB now.” So PS is convenient, vs. manually finding the KB and applying.

    Hope this helps!

    Kindly let us know if the above helps or you need further assistance on this issue.

    ------------------------------------------------------------------------------------------

    Do click on "Mark as Answer" on the post that helps you, this can be beneficial to other community members.
    Tuesday, April 21, 2020 5:13 AM
  • Thank you kindly for the info! great help - is there any published documentation from Microsoft around this process and best practices? I couldn't find any...
    Tuesday, April 21, 2020 7:30 AM