Microsoft System Center Configuration Manager
  • 19 Jan 2021
  • 2 Minutes to read
  • Dark
    Light
  • PDF

Microsoft System Center Configuration Manager

  • Dark
    Light
  • PDF

A valid Liquit Release and Patch license is required to configure this connector. Please contact Liquit Sales if the option is not available in your Liquit Workspace environment.

The Microsoft System Center Configuration Manager connector allows you to publish packages to Microsoft System Center Configuration Manager.

The following management tabs are available for a Microsoft System Center Configuration Manager Connector:

Details

The details tab contains the details of the Microsoft System Center Configuration Manager connector you are about to configure:

Name Description Required
Name A friendly name for the connector (e.g. Microsoft System Center Configuration Manager), the name will help you identify the connector. Yes
Server Satellite Server that hosts this connector No
Method Determines how the connector should be synchronized, the following options are available:
  • On-demand Allows you to choose which attached packages should be updated.
  • Synchronize This option will automatically synchronize your packages with new available information.
No
Direction Determines which direction the connector functions
  • Push Connector will create packages in the connected system.
No
Enabled Determines whether or not a connector is available No
Package name prefix The default prefix for package names, this can be helpful to easily identify all packages originating from a certain connector No
Description A description for the connector No

Settings

This tab contains all information on how to connect to your Microsoft System Center Configuration Manager environment.

Name Description Required
Address The DNS name of your Microsoft System Center Configuration Manager Yes
Username The username that should be used for connecting. This should be a AD domain username. If not provided, the Liquit service credentials will be used. No
Password The password used in conjunction with the username to connect Yes
Site Code The site code that should be used (.e.g. "PS1") Yes
Content path The network path to store files for Microsoft System Center Configuration Manager (e.g. "\cm01\d$\liquit") Yes
Assembly path The local path to the 'bin' directory of where the Microsoft System Center Configuration Manager administration console is installed (e.g. "D:\Program Files\Microsoft Configuration Manager\AdminConsole\bin") Yes
Language What language should be set on the newly created applications with Microsoft System Center Configuration Manager Yes
Application folder The Application Management folder within the Microsoft System Center Configuration Manager Software Library where the applications should be moved to after creation. For example "Liquit". This folder must exist in the Applications folder in the Software Library before applications can be moved! No

Scoping

This tab shows you the settings to control which packages will be sended to Microsoft System Center Configuration Manager.

Name Description Required
Unscoped All applicable packages will be synchronized No
Unscoped Stage The stage of the package that will be used as source if unscoped is enabled. No
Identities If unscoped is disabled, this will list all identities that will be used to resolve the packages through entitlements. No

Updates

This tab shows you a list of packages that are ready to be synchronized to Microsoft System Center Configuration Manager. This list includes new and updated packages.

Managed Packages

This tab shows a list of packages that are synchronized to Microsoft System Center Configuration Manager.


Was this article helpful?

What's Next