This is not the latest version of Ivanti Workspace Control documentation.
View available documentation.

Microsoft System Center icon Microsoft System Center

Microsoft System Center Configuration Manager Integration

With Microsoft System Center ConfigMgr Integration enabled in Workspace Control, it is possible to deploy software distribution Programs on Workspace Control Agents on which a Microsoft System Center Configuration Manager client is running. It allows you to deliver, install, and configure software at the start of a Workspace Control session or when the user clicks on the application shortcut.

At Microsoft System Center in the Setup menu, you can integrate the installation feature of Microsoft System Center Configuration Manager (SCCM) in your environment. To set up the integration, provide credentials of an administrator with at least the "Application Administrator role" within SCCM.

Global software distributions can be configured at Composition > Actions By Type > Microsoft ConfigMgr. Configure the software distributions for Applications on the Actions tab of the Configuration section of an application.

Communication

Workspace Control uses Windows Management Instrumentation (WMI) to communicate with both Microsoft Configuration Manager server and client.

When configuring Microsoft System Center Configuration Manager Integration Workspace Control queries the configured Management Server for available software distribution Packages. This is to verify the correct Management Server has been specified.

When configuring Software distributions (Microsoft ConfigMgr), Workspace Control queries the configured Management Server for available software distribution Packages and Programs. After selecting a Program, a reference is stored in the Workspace Control Datastore.

For global software distributions, the Workspace Control Agent creates an advertisement for the selected Program on the Microsoft System Center Management Server at the start of a session. For software distributions configured for an application, the advertisement for the selected Program on the Microsoft System Center Management Server is created when the user starts the application.

The advertisement that was created is based on a temporary Collection that contains only the Configuration Manager client from the computer on which the Workspace Control Agent is running.

The Workspace Control Agent, then notifies the Configuration Manager client about this new advertisement.

If the option Create subfolder for the temporary Device Collection is selected, you can specify the Subfolder name used by Workspace Control. The sub-folder that will be used for the temporary Device Collection, will be created in the SCCM Console in the Devices folder (at Overview > Devices).

  • Microsoft System Center does not support the following characters in the sub-folder names for the temporary Device Collection: \ / : * ? " < > |. If unsupported characters are used in the sub-folder name, when saving, a message is displayed informing you about replacing these characters with an underscore ("_"). You can then also decide to change the name and save again.

If the Wait for action to finish before continuing is enabled for a software distribution action for an application, a Dismiss and notify me when done notification is displayed in the user session when a user starts the application and the package is deployed. This allows the user to continue working with already available applications while the package is being installed. The user receives a message once the installation is completed.

After deployment of the program, the Workspace Control Agent removes the advertisement from the Management Server.

Editing applications that are configured with Microsoft ConfigMgr tasks using a Workspace Control Console older than 2014 RC may lead to datastore integrity errors.

  • Software distributions require a Microsoft System Center Configuration Manager client to be installed on the Workspace Control Agent.
  • See the Compatibility Matrix Workspace Control for supported versions of Configuration Manager.
  • For more information, refer to Microsoft documentation.