Actions

Application Management P2 Deployment Rings

From Syntaro Help


The Deployment Rings are a feature, which is just available in the P2 Plan of the Module. It allows to deploy an application in multiple stages like the Windows Updates.

Grafik LOB Deployment Groups Syntaro.png

Every customer has two rings available, which are called Production and Archive. Normally all devices are assigned to the Production ring until you define additional rings. The Archive ring will never have a device assigned to it. So as soon you add a package version to the archive ring no device will be able to install it. So the Archive can be used for package versions during testing(by specifying the Required Version ) or when the version should no longer be deployed. Changing an application to Archive will not uninstall the package from the devices.

Create a Deployment Ring

Syntaro-DeploymentRings.png
In the Application Management Module click on Deployment ring.
Syntaro-DeploymentRings2.png
In the deployment ring list you can see the existing rings and create a new one. Per ring is one Azure AD group needed.
Syntaro-DeploymentRings3.png
In the new blade you have to specify a ring name, which can be any free text. The ring order is explained in the next section and should be an integer between 1 and 253. Then you can search for an Azure AD Group which is defining the device memberships of the deployment ring. This means the Azure AD group should contain devices. Users are ignored.

Ring Order

The Ring Order is important, in this example we have the following rings defined. Please note the ring order in the braces:

Insider(1) --> Pilot(2) --> Production(254) --> Archive(255)

This means if we have for example:

  • We have a new package, where we assigned the first version to the Insider ring. If you deploy the Dummy MSI package to all your clients, the package, will only be installed on devices, which belong to the insider ring. The Production devices will not get the package installed.
  • We have a productive package version 2.0 which is assigned and deployed to the production devices. As soon you create now a Version 3.0 and assign it to the Insider ring, then it is only updated on these devices. As soon you have testet it, you can just change the deployment ring to the next ring and it will be rolled out to these devices as soon they check for an update.
  • We have a productive package version 2.0 which is assigned and deployed to the production devices. If you now would like to take this application out of order, then you have to uninstall the application via Intune from all the devices. As soon this happened you can change the assign ring to archive. If you do this before uninstalling the package, then nothing will happen on the clients during an uninstall assignment, because they will no longer see the package in the repository.

Availability Time

Since release 1805 it is possible to specify an availability time of the application. The time specified is enforced according to the client local time. This means if you would like to deploy a package at 9pm in the evening in company which is working around the world, it is available on each client at 9pm in the local time zone of the client.

Important: The clients check once a day for new packages and once a week for updates. Therefore, the availability time does not mean deployment time. If you schedule the availability time, then you can for example use a PowerShell Script add a custom schedule to our Scheduled task when the deployment time should match the availability time. This can be done with the following script:

$trigger = New-ScheduledTaskTrigger -Once -At ([DateTime]"2018-08-03 10:30:00")
$task = get-scheduledtask -TaskName "Syntaro Updater"
Set-ScheduledTask -TaskName "Syntaro Updater" -Trigger ($task.Triggers + $trigger)