Software Distribution SCCM Integration


About This Integration
SM_IntegrationIntroduction

You can integrate third-party systems with Product name - ev itsm.png in many ways. The method you select will depend on business requirements, architectural and security constraints as well as the characteristics specific to each third-party application or service.

This document describes an integration process that has already been implemented in a customer context. 

To find out more about this integration (e.g. scripts to be used), please contact the Logo - EasyVista.png Consulting & Professional Services team, the Logo - EasyVista.png Support team, or your service provider and integrator.

Integration Summary

For security reasons, to avoid the risk of installing viruses, malware and spyware, and to reduce the number of Service Desk incidents related to the use of non-professional software, the IT Department may not authorize users to install applications on their workstation by themselves. However, the IT Department may give users the possibility of submitting installation requests for whitelisted software available in the Product name - ev itsm.png service catalog. 

You can update the catalog automatically and perform remote software distribution easily by integrating a specialized application such as SCCM (Microsoft System Center Configuration Manager) in Product name - ev itsm.png. Once a service request is created in Product name - ev itsm.png, an installation process, managed by a workflow, is run. Deployment on the workstation is performed interactively using the Microsoft SCCM Distribution functionality.

Supported Versions

Logo - Microsoft System Center.png
SCCM 2007 SP2 SCCM 2012 SCCM 2012 SP1 SCCM 2012 R2 SCCM 2016
Check icon.png Check icon.png Check icon.png Check icon.png Check icon.png

Operating Principle

        SCCM Distribution Process.png

The interactive process between SCCM and Product name - ev itsm.png is run on a regular basis and is made up of several phases:

  • Update the Service Catalog that proposes SCCM software available for installation in Product name - ev itsm.png using an integration model.
  • Users submit installation requests for software using Software service requests which are managed by two workflows, workflow without approval and workflow with management and financial approval.
  • SCCM connects to the Product name - ev itsm.png database to check the presence of new service requests.
  • SCCM deploys the software requested by users and posts two files via FTP: a list of the correctly installed software and a list of the non-installed software whose error code was generated by SCCM.
  • Product name - ev itsm.png processes the SCCM deployment results by updating the status of the service requests using a business rule and a web service to define the progress or closure of the two workflows.

Software deployment can lead to the sending of various notifications based on the workflow managing the process.

Examples of workflows

  • Workflow managing installation requests without approval:
             SCCM Distribution - Workflow without validation.png
  • Workflow managing installation requests with management and financial approval:
             SCCM Distribution - Workflow with validation.png

Notes

  • SCCM interfaces with Product name - ev itsm.png using the Status field in the service request (Available Field 4 = SD_REQUEST.AVAILABLE_FIELD_4). Its value is updated throughout the software deployment process:
    • To Do: To be processed
    • In Progress: Currently in progress
    • Error Integration: Integration error
    • Error Deployment: Deployment error
    • Closed: Closed
  • The statuses must be defined in the reference table.

Procedure: How to deploy software using SCCM

1. Select Transition > References > Workflows in the menu and define the workflow for managing the software deployment process.

2. Define integration models for updating the Service Catalog (software requests) using SCCM software data.

  • Select Integration > Integration models in the menu and define the integration models.
  • Schedule when they should run.

3. Once the Service Catalog is updated, check the list of software available for installation. Note: You can define which software you do not want to make available to users. To do so, open the Service Catalog form and select the Cannot be Requested option.

4. The software deployment process is then performed on a regular basis. If required, correct the errors notified by SCCM to ensure that the software is correctly installed, e.g. user workstations not recognized in Product name - ev itsm.png, integration or deployment errors due to SCCM processing.

Tags:
Last modified by Unknown User on 2017/04/07 12:29
Created by Administrator XWiki on 2015/06/01 10:40

Shortcuts

Recent Updates

Haven't been here in a while? Here's what changed recently:
-   Product name - ev itsm.png
-   Product name - ev sas.png

Interesting Content

Quick Call
SCCM Distribution
Actions
Reporting Tools
Purge of archives

Powered by XWiki ©, EasyVista 2017