Deploying the Cirros Windows client

This page is for IT teams who deploy and manage the Cirros Windows client. It covers how to install the client with your Company Code, how updates are released in phases, and how to check which version each workstation is running.

Applies to Cirros Client 1.4.

How deployment works

• One generic build. The same installer (an MSI) is used for every organisation. There is no separate installer per customer.
• A Company Code binds each install to your organisation. You supply it when you install. Without it, the client is not linked to your organisation and the install will not complete as expected.
• One package for x64 and ARM. The same build is designed to run on Windows on ARM (ARM64) as well as standard x64 hardware.
• Updates arrive in phases. Workstations follow one of three release channels, and each update cycle moves only a set percentage of them to the new version.

Before you start, check the workstation minimum specification.

What you need

• The generic Windows client installer (MSI).
• Your Company Code. If you do not have it, ask servicedesk@cirros.net.
• Your deployment tool, if you are installing at scale, for example Configuration Manager (SCCM), Intune or Group Policy.
• For the release steps below, access to the Cirros Dashboard with a role that includes release management.

Install with your Company Code

Install the MSI on each workstation and pass your Company Code to the installer. Cirros gives you the installer file and the exact install command, including the Company Code property, for your organisation.

• Use the command you were given. Use the file name and property exactly as supplied. If you do not have them, ask servicedesk@cirros.net before a wide deployment.
• Always supply the Company Code. Leaving it out is a common cause of failed or incomplete deployments.
• Use the same package on ARM. Windows on ARM devices do not need a separate package.

Deploying at scale

• Put the property in the deployment. Add the Company Code property to the install command or properties in SCCM, Intune or Group Policy. A package that installs on a test machine but fails when pushed through your tool is often missing this property.
• Pilot first. Install on one pilot workstation before deploying widely. Include an ARM device if you have any in scope.

Release channels

Each workstation follows one of three channels.

Versions are promoted from Beta to Early Adopter to Stable. To choose which of your workstations sit in Beta or Early Adopter, see Enabling a workstation for client updates. Machines in neither group follow Stable.

Set the phased rollout

Cirros Dashboard › Releases › Manage Windows Releases

Cirros assigns each client build to your organisation and sets which version each channel runs (see Cirros assigns the builds). On this page you set how fast the standard rollout moves.

1. Open the page. Sign in to the Cirros Dashboard, expand Releases in the left-hand navigation and select Manage Windows Releases.
2. Set the pace. Set Auto Update Percentage (how much of the eligible fleet updates in each cycle, for example 10), Auto Update Interval (how often a cycle runs, for example Weekly) and Auto Update Day (the day it runs).
3. Apply. Select Submit.

On each update cycle, the percentage you set of eligible machines moves to the target version, so a release reaches the fleet gradually. Start with a low percentage and raise it as you gain confidence.

The right-hand side of the page shows a chart of workstation versions and a Workstations pending stable version count, so you can watch progress against the Stable target.

Read the release notes

Read the notes for a version before you assign it to a channel.

1. Open the page. In Releases, open Release Update.
2. Pick the tab. Choose Workstation Client Update for the Windows client.
3. Select a version. The release notes show the release date and a summary of what changed.

Monitor the rollout

Cirros Dashboard › Workstations

The Workstations list shows each machine's Name, Serial, IP Address, Version, Admin flag and Last Heartbeat, with an online or offline indicator on each row.

• Confirm the version. Sort or filter by Version to check the expected proportion of machines has moved to the new build.
• Check the count. The Workstations pending stable version count on Manage Windows Releases should trend towards zero.
• Report on progress. Use Export to Excel to keep a record of the rollout over time.

Recommended rollout sequence

1. Beta. Put a few test machines in the Beta ring, so they get a new build first.
2. Early Adopter. Put a larger validation group in the Early Adopter ring.
3. Start slowly. Keep the Auto Update Percentage low for the standard rollout.
4. Ramp up. Raise the Auto Update Percentage over successive cycles while you watch for problems.
5. Verify. Watch the Workstations list and the pending count until the fleet is on the target version.

Troubleshooting

Install fails or the client is not linked to your organisation

• Check that the Company Code property is being passed and is correct.
• In SCCM or Intune, check the property is in the deployment definition, not only in a manual test command.

Install fails during service startup

• Install with logging, for example msiexec /i <installer>.msi /l*v install.log, and check the log and Windows Event Viewer for the failing component.
• Check the workstation meets the minimum specification and that the installer ran with administrator rights.

A workstation is not updating

• Check which channel the machine is on, and which version is set for that channel on Manage Windows Releases.
• Check the Auto Update Percentage, Interval and Day. The machine may not yet be within the percentage for the current cycle.
• Check Last Heartbeat in Workstations to confirm the machine is online.
• Restart the machine properly. On PCs with Windows Fast Startup, shutting down does not always apply a pending update. See Enabling a workstation for client updates.

If you are still stuck, contact servicedesk@cirros.net with the client version and what you saw.