What is the Updater service and what does it do?

Updater Service

Introduction

The Updater Service is responsible for applying no-touch push deployment for all of our client and remote server applications and services. The components of the Updater Service include the Microsoft Application Blocks (Updater Application Blocks 2.0) and Microsoft BITS (Background Intelligent Transfer Service). The Windows NT Service is responsible for checking for and applying updates to end-user systems.
NOTE: As of CCM version 5.7 GA, updates are now downloaded via the HTTP protocol on port 80. 

Fundamentals

The Updater Service uses manifests as a control system for updates. The manifest file contains the following information about the update:

• The application to update
  
• The file(s) to download
  
• The location to download files from
  
• The actions to take after the download has completed. (This can include waiting for a specific application to exit, copy files to a specific location or writing registry keys; among many other options).
  
• The updater will check for an update at least every 10 minutes, however; this is also done as an on-demand check for certain applications (Contact Center Client, Contact Center Scheduling, Flexible Reporting).
  
• The updater service will check the remote manifest file located on the server and will compare this, first against the initial manifest (these are the manifests which are included with the initial installation to avoid redundant updates) and then any applied manifests (downloads which have already been completed).
  
• The goal of the updater service is to synchronize itself with the server. This means that if an older version is present on the server and this update has not been downloaded by the Updater Service, it will be applied to the client system. This is by design.

Application ID for MiCC Version 6.X and older

{81de90ae-dd42-4a5f-9863-6af36710f8a1} – App Start
{18103119-79d5-448c-8bdb-0bf47b1482e4} – Client Role Selector
{22daf34a-4df5-40e3-92fd-384e607e3fb7} – Contact Center Client
{9777fcc1-0c66-41a9-8f36-6cfc95aaf089} - Contact Center Client Plugins
{b14f8206-576d-41cc-b653-00a046bc5e02} – Collector
{80220a90-c6bf-45ae-92b1-3f519350b391} - Exchange Diagnostics
{3e36bf38-ecc0-4b5a-bd42-298888f20049} - Exchange Router
{ea74f016-f381-4d1d-b3d0-96c0a0d30e36} – Flexible Reporting
{f5b0dc9e-df6b-42ce-81e3-131ce8e892c6} - IVR Inbound (only Version 6.X)
{e3942ddd-5901-4970-8c41-df2ef2c838d0} - IVR Music (only Version 6.X)
{dbd69198-aee8-4b20-8e6b-0a06197c5546} - IVR Outbound (only Version 6.X)
{b4aa1591-6e39-4e9b-878a-6dc8dcf69f55} - IVR UPiQ (only Version 6.X)
{9c906b25-cbee-4068-aece-125c7cb5751d} - MBG Connector
{06212cb9-e38c-48eb-bfe5-7f6fe554dea7} - MiAudio Emulation Server
{5b412099-8e25-48a2-b80d-1c4e9c5e5925} - MiTAI Proxy Server
{7326380c-59f9-4f80-b7d7-22188f7e00c1} – Outlook Plugin
{cc0ff296-047e-4606-9e20-e13379da2ff1} - SalesForce Integration
{3466d18f-7db4-4b6e-8bd2-0dfbd45918c8} - Server Monitoring Agent (only Version 6.X)
{627ce24a-399a-4141-a86e-d7877a5aaaa7} – Updater Service
{94rde9faw-ed12-fa23-9j0n-br2g5730g8h1} – Wallboarder
{ae0fb07b-0927-427d-a037-de41aea3f2c2} – Workforce Scheduling
{5F571C5F-4C31-430a-8D3E-EEB920BB53CB} - YourSite Explorer

Application ID for MiCC Version 7.X and newer

{81de90ae-dd42-4a5f-9863-6af36710f8a1} – App Start
{18103119-79d5-448c-8bdb-0bf47b1482e4} – Client Role Selector
{22daf34a-4df5-40e3-92fd-384e607e3fb7} – Contact Center Client
{9777fcc1-0c66-41a9-8f36-6cfc95aaf089} - Contact Center Client Plugins
{b14f8206-576d-41cc-b653-00a046bc5e02} – Collector
{ea74f016-f381-4d1d-b3d0-96c0a0d30e36} – Flexible Reporting
{e3942ddd-5901-4970-8c41-df2ef2c838d0} - IVR Music
{9c906b25-cbee-4068-aece-125c7cb5751d} - MBG Connector
{06212cb9-e38c-48eb-bfe5-7f6fe554dea7} - MiAudio Emulation Server
{5b412099-8e25-48a2-b80d-1c4e9c5e5925} - MiTAI Proxy Server
{D352857D-4EA7-4431-95B0-75FCD66904DE} - Routing Inbound
{F9198994-4D01-423F-8C02-8158756D7AB9} - Routing Outbound
{A34ECB98-24E9-4A4A-AA72-AF08569A92E5} - Routing Media
{71F41B54-EF51-4630-9B0D-9F406C6F51F0} - Routing UPiQ
{cc0ff296-047e-4606-9e20-e13379da2ff1} - SalesForce Integration
{3466d18f-7db4-4b6e-8bd2-0dfbd45918c8} - Server Monitoring Agent
{627ce24a-399a-4141-a86e-d7877a5aaaa7} – Updater Service
{94rde9faw-ed12-fa23-9j0n-br2g5730g8h1} – Wallboarder
{ae0fb07b-0927-427d-a037-de41aea3f2c2} – Workforce Scheduling
{5F571C5F-4C31-430a-8D3E-EEB920BB53CB} - YourSite Explorer

Details

The Updater Service has a workspace in the following folder [INSTALLDIR]\Updater. There should be three folders Applications, Downloader, Registry. Each of these folders has a specific function:

1. Applications: stores a list of the updates which have been downloaded and applied already. Each application will have a folder, which is named after the application ID.
2. Downloader: the temporary download location for an update
3. Registry: the current download information (if a download is currently occurring), otherwise empty.

Troubleshooting

1. Check the logs: The logs are located in the folder [INSTALLDIR]\Services\UpdaterService\UpdaterService Files\Logs
2. Force a download: Delete the appliedmanifest files for a specific application. These files are found in the [INSTALLDIR]\Updater\Applications\<ApplicationID> folder.
3. Check firewalls and proxy servers, these can sometimes interfere with the update process.  Disable them as a troubleshooting step.
4. Ensure the Windows user has write permissions on the [INSTALLDIR] folder and all sub-folders.
5. Ensure the [INSTALLDIR] folder, sub-folders, and files do not have the Read-only attribute enabled.

NOTE: The [INSTALLDIR] can be found in the registry under HKEY_LOCAL_MACHINE\SOFTWARE\prairieFyre Software Inc\CCM\Common\InstallDir

Keywords: ccc client updates updater service