The following manual is written for both Luware LUCS and TM products in mind. Whenever a special step applies to either one product this is marked accordingly.

Please note that there are a lot of possible LUCS installation variants, and configuration possibilities, so not all steps can be provided in full detail. Consider the steps below more as a guideline and checklist to go through.

(tick) In order to remove your LUCS, perform the following steps.

On your LUCS Server

(warning) In the rare case you have multiple Luware products installed simultaneously, make sure to only stop the services and uninstall the components needed.


  1. Depending if you are using LUCS or TM:
    1. TM: Deactivate active Teams in your LUCS configuration UI
    2. LUCS: Remove all service entries in your LUCS configuration UI
  2. Open Task Manager > Services for LUCS related component services. (lightbulb) Look for "Luware-LUCS-Componentname" service names and end their task.
  3. Check in Windows Internet Information Services for running Luware Frontend and API services:
    1. Start > run "Inetmgr" > Sites) for any running LUCS frontend sites and stop them.

    2. (lightbulb) You might want to clear the related IIS logfiles as well (default: %SystemDrive%\inetpub\logs\LogFiles). Also refer to the Microsoft IIS Log documentation.
  4. Once all services and sites are stopped, uninstall all LUCS related components from your server.
  5. Check the component install directories (default: Program Files\Luware AG) and remove - or backup - any leftover folders.
    (question) Why do these folders remain? Old log and configuration files are left in case a new component gets installed.

Network Service Account removal 

Network Service account to the RTC (Real Time Communications) Local Read-only Administrators group may remain on the machines where LUCS was installed.

Please note that these accounts may be used for other RTC related services (Lync / SfB). You may not want to remove them for that reason.

  1. On Windows Server 2008, go to StartRun.
    On Windows Server 2012, press the Windows key + r.
  2. Type lusrmgr.msc and then open it. (Local Users and Groups)
  3. Select Groups
  4. Add Network Service user to RTC Local Read-only Administrators group:
    1. Open the Properties of the RTC Local Read-only Administrators
    2. Remove the members not requiring admin access anymore.

On the Active Directory Server

Remove LUCS Active Directory-Groups → See Steps below

(info) TM Only: For each team you might have several AD Groups "per Team / Organization Unit (OU)" defined. You need to remove each of those manually from your AD server. 

Network Service Account removal

  1. Remove LUCS CIC-Service-Users in the Group "CS-Administrator"
    1. On Windows Server 2008, go to StartRun.
      On Windows Server 2012, press the Windows key + r.
    2. Find and open Active Directory Users and Computers.
    3. Expand the folder tree and select Service Accounts.
    4. Check Menu of the Service Accounts folder or
    5. Add the rights to the created user:
      1. Open Properties of the created user and choose Member Of tab
      2. ... remove the CS Administrator objects and confirm the changes.

On your DNS Server

  1. Remove SRV-Entries in your DNS server.
  2. You may want to purge DNS entries at the end of the procedure.

(info) This is more of a general recommendation. You might also find this Microsoft Blog useful.

On the SfB Server

(info) Now its time to remove the trusted application pool on your Skype for Business server. Pool removal should automatically remove related LUCS endpoints and servers. Links below lead to the official SfB documentation by Microsoft.

  1. Remove SMD (SIP Message Dispatcher) components on the SfB Server
  2. With Powershell locate and remove SMD topology permissions:

    Get-CsServerApplication | ?{$_.Name -like "lucs-SMD"} | Remove-CsServerApplication
    CODE

    (lightbulb) Replace lucs-SMD with tm-SMD accordingly.

  3. With Powershell, use the following commands to locate LUCS related endpoints:
    1. Get-CsTrustedApplicationPool
    2. Get-CsTrustedApplication
    3. Get-CsTrustedApplicationComputer
    4. Get-CsTrustedApplicationEndpoint
  4. With Powershell, use the following commands to remove the LUCS related endpoints:
    1. Remove-CsTrustedApplicationPool
    2. Remove-CsTrustedApplication
    3. Remove-CsTrustedApplicationComputer
    4. Remove-CsTrustedApplicationEndpoint
  5. Get and Remove Conference Policies:
    1. Get-CsConferencingPolicy -Identity Tag:LUCSService 
      (lightbulb) Replace LUCS with TM accordingly.
    2. Remove-CsConferencingPolicy
  6. Remove SMD (SIP Message Dispatcher) Frontend server (Uninstall via LUCS component setup)

Network Service Account removal 

Network Service accounts Local Read-only Administrators group may remain on the machines where LUCS was installed.

  1. Remove machine where SMD will be run add the Network Service account to RTC Server Applications group:

    1. On Windows Server 2008, go to StartRun.
      On Windows Server 2012, press the Windows key + r.
    2. Type lusrmgr.msc and open it.  (Local Users and Groups)
    3. Select Groups
    4. Locate the RTC Server Applications group
    5. Open the Properties of the RTC Server Applications
    6. Remove Network Service Object users to and confirm the changes.

On the SQL Server

(info) These steps are installation dependent and based on your SQL Database. Consider the steps below as a checklist.

  1. Delete or Stop associated SQL agent jobs
  2. Create a SQL Backup (if necessary)
  3. Delete LUCS database
  4. Remove SQL-Integration order and any related running jobs
  5. Remove SQL security logins related to LUCS

On the Agent Machines

(info) The Agent Machine applications have no server hosting capabilities by themselves, but may cause errors on startup each when there are no more LUCS server components and services to connect with. We therefore recommend their removal as well.


  1. LUCS only: Uninstall Agent Assistant from each client machine (default: Program Files\Luware AG\LUCS-AA)
  2. LUCS and TM:
    1. Remove any leftover the folders in Program Files\Luware AG\
    2. Optionally clear the browser cache and stored passwords to remove traces of login sessions

Recommended Post-Cleanup

  1. Remove global Firewall and Antivirus exceptions made for all LUCS products. Check for Port Forwarding rules for these applications as well.

    LUCS ComponentsTM Components
    Luware-LUCS-AC (Agent Controller)
    Luware-LUCS-AM (Agent Manager)
    Luware-LUCS-API (Application program interface)
    Luware-LUCS-CI (Calendar Integration)
    Luware-LUCS-CIC (Customer Infrastructure Connector)
    Luware-LUCS-CR (Conversation Recording)
    Luware-LUCS-FE (Frontend of the Web Application).
    Luware-LUCS-ICH (Interactive Conversation Handler)
    Luware-LUCS-LC (LUCS Configurator)
    Luware-LUCS-MM (Mail Manager) - for handling Exchange and O365 Mailboxes and for using Mail Services. 
    Luware-LUCS-MMClient (Silverlight Application for post calls, allows E-Mail handling in SfB)
    Luware-LUCS-PS (Persistence Service)
    Luware-LUCS-SMD (SIP Message Dispatcher) – the SMD component is installed on the Lync server machine.
    Luware-TM-AC (Agent Controller)
    Luware-TM-AM (Agent Manager)
    Luware-TM-API (Application Programming Interface)
    Luware-TM-CI (Calendar Integration)
    Luware-TM-CIC (Customer Infrastructure Connector)
    Luware-TM-CR (Conversation Recording)
    Luware-TM-CWS (Configuration Web Service for TM)
    Luware-TM-Configurator (System configuration definition)
    Luware-TM-FE (Frontend of the Web Application)
    Luware-TM-GalReader (Global Address List Reader)
    Luware-TM-ICH (Interactive Conversation Handler)
    Luware-TM-PS(Persistence Service)
    Luware-TM-SMD (SIP Message Dispatcher) – the SMD component is installed on the Lync server machine

    (info) Note: Not all components are installed on every system. The list contains all potential 

  2. Remove may Exchange Calendars related to LUCS Mail Services.

Related Pages

Related Chapters

The following installation chapters might be useful to roll back any steps performed: