LUCS Preconditions
LUCS Prerequisites
- The following chapters list the minimum requirements for any LUCS installation as well as necessary Windows components that need to be installed in preparation prior to any LUCS components.
- These prerequisites apply for both an upgrade and a first-time installation of LUCS. Please refer to the specific sections of our Knowledgebase for detailed instructions.
Compatibility statement
All tested compatibility (e.g. for Operating Systems, SfB, SQL Server) is documented in the LUCS prerequisites / preconditions chapters . Other combinations may work, but are not tested.
Server Requirements
The LUCS system can be installed on a virtual system. Supported virtualization platforms are VMware ESX, Citrix XenServer and Microsoft Hyper-V.
Please note, it is not supported to perform checkpoints/snapshots or Live Migrations while the LUCS Server is running.
Please see the recommended minimum specifications table below (when running LUCS Server on the supported platforms):
CPU | 4 dedicated cores |
---|---|
Memory | Fixed 16 GB |
Hard disk | Fixed 80 GB or more |
Network | Max. one Ethernet with Gigabit or higher speed |
Server Operating System
The LUCS system requires a Windows Server operating system. We recommend installing the latest security updates from Microsoft prior to installing LUCS.
LUCS only supports the operating systems listed in the table below.
Operating System | Windows Server 2012 R2 *When using newer .NET versions than recommended below, please read Microsoft's article on dotNET Version Compatibility |
---|---|
SfB Requirements |
|
.NET | .NET Framework 4.7.2 for Skype for Business Server 2015 CU 5 or later releases
|
Windows Features | A full list can be found in PowerShell commands (see below). The following are the top mentions:
|
Editor | Windows Editor or Notepad++ (http://notepad-plus-plus.org/download/) |
ISO Binaries | Access to Lync Server 2013 / SfB Server 2015 / SfB Server 2019 ISO Binaries |
Windows OS / SfB Server Compatibility
Windows Server Version → SfB Version ↓ | Windows Server 2008 R2 | Windows Server 2012 R2 | Windows Server 2016 | Windows Server 2019 | Related Microsoft Links |
---|---|---|---|---|---|
Skype for Business 2015 |
|
|
|
| |
Skype for Business 2019 |
|
|
|
|
SQL Server
Operating System | Windows Server 2012 R2 |
---|---|
MS SQL Server | SQL Server 2012 |
Collation | Latin1_General_CI_AS |
Protocols | Named Pipes / TCP/IP enabled |
Database-Encryption | Not supported (untested) |
Database-Compression | Not supported (untested) |
SqlServer Authentication | MIXED mode or Windows authentication |
Memory Limit | Configuration of Memory-Limit is recommended. |
Instance | Luware recommends having a dedicated instance for the Luware products. The instance can be shared, but under no circumstances with Skype for Business backend. |
Reporting Services
If LUCS SSRS Reporting is used then the SQL Reporting Services needs to be installed.
Required Powershell Commands
In some cases your IT policy or access rights might restrict the use of Powershell commands. Here is a list of required commands used during installation and setup:
Required Lync Powershell Commands
- Get-CsTrustedApplicationEndpoint
- Set-CsTrustedApplicationEndpoint
- Remove-CsTrustedApplicationEndpoint
- New-CsTrustedApplicationEndpoint
- Grant-CsVoicePolicy
- Get-CsVoicePolicy
- Get-CsVoiceRoute
- Get-CsPool
- Get-CsServerVersion
- Grant-CsConferencingPolicy
- New-CsConferencingPolicy
- Get-CsConferencingPolicy
- Set-CsConferencingPolicy
- Remove-CsConferencingPolicy
- Get-CsExternalAccessPolicy
- Grant-CsExternalAccessPolicy
Required Active Directory Powershell Commands
- Get-ADObject
- Set-ADObject
Required Windows Features
These Windows features are required on every machine (instance) acting as LUCS Server. PowerShell can be used to quickly check and install all Windows features required for LUCS.
Set ExecutionPolicy to "RemoteSigned"
The following PowerShell sessions must be started with Administrator rights on each LUCS Server machine.
To execute Lync/SfB PowerShell commands, the execution Policy must be set to "RemoteSigned". This setting must be run on each machine where you are planning to install Luware products and their required Windows feature prerequisites.
Set-ExecutionPolicy RemoteSigned -Force
→ No error must occur when executing this command.
The following Powershell script will check and install all necessary Windows features.
If errors occur, try to execute the script again, as download from Microsoft and back-to-back installation may fail.
Please read before executing the Windows Features Powershell Script
This script installs .NET Framework 4.6. Depending on your Operating System and LUCS version to be installed it might not be necessary to do so as a more current .NET version is already present.
- Please refer to your LUCS .NET compatibility statements in the "Prerequisites" chapter.
- Install any required .NET versions manually and install other dependencies using the script.
- Also refer to the related Microsoft source on .NET version dependencies: https://docs.microsoft.com/en-us/dotnet/framework/migration-guide/versions-and-dependencies
PowerShell Script: Windows Features Installation
Import-Module ServerManager
[System.Collections.ArrayList]$features = @(
"NET-Framework-Features",
"RSAT-ADDS",
"NET-Framework-Core",
"NET-Framework-45-Features",
"NET-Framework-45-Core",
"NET-Framework-45-ASPNET",
"NET-WCF-Services45",
"NET-WCF-HTTP-Activation45",
"NET-WCF-Pipe-Activation45",
"NET-WCF-TCP-Activation45",
"NET-WCF-TCP-PortSharing45",
"Web-Server",
"Web-WebServer",
"Web-Common-Http",
"Web-Default-Doc",
"Web-Dir-Browsing",
"Web-Http-Errors",
"Web-Static-Content",
"Web-Http-Redirect",
"Web-Health",
"Web-Http-Logging",
"Web-Log-Libraries",
"Web-Request-Monitor",
"Web-Http-Tracing",
"Web-Performance",
"Web-Stat-Compression",
"Web-Dyn-Compression",
"Web-Security",
"Web-Filtering",
"Web-Basic-Auth",
"Web-Client-Auth",
"Web-Digest-Auth",
"Web-Cert-Auth",
"Web-IP-Security",
"Web-Url-Auth",
"Web-Windows-Auth",
"Web-App-Dev",
"Web-AppInit",
"Web-Net-Ext",
"Web-Net-Ext45",
"Web-Asp-Net",
"Web-Asp-Net45",
"Web-ISAPI-Ext",
"Web-ISAPI-Filter",
"Web-WebSockets",
"Web-WHC",
"Web-Mgmt-Tools",
"Web-Mgmt-Console",
"Web-Scripting-Tools",
"Telnet-Client",
"Desktop-Experience",
"Windows-Identity-Foundation")
$winversion = [environment]::OSVersion.Version
If($winversion.Major -ge 10){
$features.Remove("Desktop-Experience")
}
foreach ($f in $features) {Install-Windowsfeature $f}
Network Requirements
The local network / firewall policy needs to be updated to allow passthrough for LUCS Ports. Refer to the following installation chapters
- Architecture - for an overview of components (services) that run on the target machines
- Installation Environment Requirements for Network Ports and AV Exclusion Lists
- Environment Preparation - For necesary DNS, AD entries, Trusted Applications, SRV records
Client-Side Requirements
- Agent Assistant runs as tray-application with no further administration needed past initial configuration.
- Web-Configurator supports the following browsers:
- Microsoft Edge (latest version).
- Google Chrome (latest version).
The required screen resolution for Web-Configurator is Full HD (1920x1080) and higher. On lower screen resolution horizontal/vertical scrolls will be added in the browser.
Architecture
In this section you learn how LUCS components and how they interact with each other. Below is a brief overview diagram on how the structure is accessed via supervisor or agent roles, as well as how customers interact with the system.
More details on Network ports and configuration can be found on the Network Port Configuration section.
Components
LUCS consists of the following components.
Component | Description | |
---|---|---|
AC | Agent Controller |
|
AM | Agent Manager / Monitor |
|
CI | Calendar Integrator |
|
CIC | Customer Interface Connector |
|
CR | Conversation Recording |
|
FE | FeCore & FrontEnd |
|
ICH | Interactive Conversation Handler |
|
MM | Mail Manager Service also known as | A service that handles the full cycle of email activities in a contact center, for example:
Client: Silverlight Application for post calls. Allow agents to answer incoming E-Mails directly within SfB |
PS | Persistence Service |
|
SMD | SIP Message Dispatcher | The SMD is running on the front-end of the Lync Server and forwards all relevant LUCS/TeamManager SIP messages to the AM. Relevant Request/Response messages are messages from team members which establish a call. The SMD is responsible for detecting team member related Lync / SfB actions and for the busy on busy feature. |
Component installation is covered in the chapter: Installation and Upgrades
External System Infrastructure Access
External / Internal Server Topology
Network Configuration
Running LUCS and TM simultaneously? TM uses LUCS Ports +2000 flat value added.
Example:
PS Service LUCS: 19400
PS Service TM : 21400
Used Protocols and Ports
This article illustrates the network connectivity requirements using a typical LUCS deployment model as an example. Below are two diagrams one highlights the Application Network Ports used for control, signalling and data. The other highlights the Media requirements in order for the LUCS Contact Centre Solution to stream and receive media via the conferencing services on the SfB Pools.
Agent to Server Connection
The Agent to Server Connection Ports are as follows:
Source | Destination | Protocol | Destination Server Port (Default) | Comment |
---|---|---|---|---|
Agent PC (LUCS FE) | LUCS Server 01 | TCP | 443 | LUCS Front-End |
Agent PC (LUCS FE) | LUCS Server 02 | TCP | 443 | LUCS Front-End |
Agent PC (LUCS-Webconfigurator) | LUCS Server 01 | TCP | 4443 | LUCS Web Configurator |
Agent PC (LUCS-Webconfigurator) | LUCS Server 02 | TCP | 4443 | LUCS Web Configurator |
Agent PC (LUCS-API) | LUCS Server 01 | TCP | 4444 | LUCS Web API |
Agent PC (LUCS-API) | LUCS Server 02 | TCP | 4444 | LUCS Web API |
Agent PC (Browser) | SQL Server | TCP | 443 | SQL Server Reporting Services (SSRS) |
Agent PC (Excel) | SQL Server | TCP | *1443 | Excel PowerPivot Reporting |
Agent PC (LUCS AA Client) | LUCS Server 01 | TCP | 19412 | LUCS-AA |
Agent PC (LUCS AA Client) | LUCS Server 02 | TCP | 19412 | LUCS-AA |
Agent PC (Lync / SfB Client) | Lync / SfB Server | UDP/TCP | *49'152 – 57'500 | Lync / SfB Media Traffic |
Agent PC (Lync / SfB Client) | Lync / SfB Server | UDP/TCP | *49'152 – 57'500 | Lync / SfB Media Traffic |
Agent PC (Lync / SfB Client) | Lync / SfB Server | UDP/TCP | *49'152 – 57'500 | Lync / SfB Media Traffic |
Agent PC (Lync / SfB Client) | Lync / SfB Server | UDP/TCP | *49'152 – 57'500 | Lync / SfB Media Traffic |
Agent PC (Lync / SfB Client) | Lync / SfB Edge Server | UDP | 3478 | SfB Media Relay Port |
Agent PC (Lync / SfB Client) | Lync / SfB Edge Server | TCP | 443 | SfB Media Relay Port |
* Media-Ports can be different depending on your environment configuration
* SQL Ports can be different depending on your environment configuration
Server to Server connection ports
Source | Destination | Protocol | Destination Server Port (Default) | Comment |
---|---|---|---|---|
LUCS Server 01 | SQL Server | TCP | *1433 | Read/write configuration to database. |
LUCS Server 02 | SQL Server | TCP | *1433 | Read/write configuration to database. |
LUCS Server 01 | Exchange Server (EWS) | TCP | 443 | Checking calendar for opening hours. |
LUCS Server 02 | Exchange Server (EWS) | TCP | 443 | Checking calendar for opening hours. |
LUCS Server 01 | Lync / SfB Edge Server | UDP | 3478 | SfB Media Relay Port |
LUCS Server 02 | Lync / SfB Edge Server | UDP | 3478 | SfB Media Relay Port |
LUCS Server 01 | Lync / SfB Edge Server | TCP | 443 | SfB Media Relay Port |
LUCS Server 02 | Lync / SfB Edge Server | TCP | 443 | SfB Media Relay Port |
LUCS Server 01 | Lync / SfB Front End Pool | TCP | 5060/5061 | Lync / SfB SIP Traffic |
LUCS Server 02 | Lync / SfB Front End Pool | TCP | 5060/5061 | Lync / SfB SIP Traffic |
LUCS Server 01 | Lync / SfB Front End Pool | UDP/TCP | *49'152 – 57'500 | Lync / SfB Media Traffic |
LUCS Server 02 | Lync / SfB Front End Pool | UDP/TCP | *49'152 – 57'500 | Lync / SfB Media Traffic |
Lync / SfB Front End Pool | LUCS Server 01 | UDP/TCP | *49'152 – 57'500 | Lync / SfB Media Traffic |
Lync / SfB Front End Pool | LUCS Server 02 | UDP/TCP | *49'152 – 57'500 | Lync / SfB Media Traffic |
Lync / SfB CMS Master Replicator Agent | LUCS Server 01 | SMB/TCP | 445 | Used to push configuration data from the Central Management store to servers running Skype for Business Server. |
Lync / SfB CMS Master Replicator Agent | LUCS Server 02 | SMB/TCP | 445 | Used to push configuration data from the Central Management store to servers running Skype for Business Server. |
* Media-Ports can be different depending on your environment configuration
* SQL Ports can be different depending on your environment configuration
Source | Destination | Protocol | Destination Server Port | Comment |
---|---|---|---|---|
LUCS Server 01 | Lync / SfB Front End Pool | TCP | 443 | Create LUCS Services and update user information. |
LUCS Server 02 | Lync / SfB Front End Pool | TCP | 443 | Create LUCS Services and update user information. |
Lync / SfB Front End Pool | LUCS Server 01 | TCP | *6000 | Communication from Lync / SfB to Trustedapplication. Ports based on LUCS Configuration. |
Lync / SfB Front End Pool | LUCS Server 02 | TCP | *6000 | Communication from Trustedapplication to Lync / SfB. Ports based on LUCS Configuration. |
Lync / SfB Front End Pool | LUCS Server 01 | TCP | *7000 | Communication from Lync / SfB to Trustedapplication. Ports based on LUCS Configuration. |
Lync / SfB Front End Pool | LUCS Server 02 | TCP | *7000 | Communication from Trustedapplication to Lync / SfB. Ports based on LUCS Configuration. |
Lync / SfB Front End Pool | LUCS Server 01 | TCP | *7100 | Communication from Lync / SfB to Trustedapplication. Ports based on LUCS Configuration. |
Lync / SfB Front End Pool | LUCS Server 02 | TCP | *7100 | Communication from Trustedapplication to Lync / SfB. Ports based on LUCS Configuration. |
Lync / SfB Front End Pool | LUCS Server 01 | TCP | *7200 | Communication from Lync / SfB to Trustedapplication. Ports based on LUCS Configuration. |
Lync / SfB Front End Pool | LUCS Server 02 | TCP | *7200 | Communication from Trustedapplication to Lync / SfB. Ports based on LUCS Configuration. |
Lync / SfB Front End Pool | LUCS Server 01 | TCP | *7300 | Communication from Lync / SfB to Trustedapplication. Ports based on LUCS Configuration. |
Lync / SfB Front End Pool | LUCS Server 02 | TCP | *7300 | Communication from Trustedapplication to Lync / SfB. Ports based on LUCS Configuration. |
Lync / SfB Front End Pool | LUCS Server 01 | TCP | *7400 | Communication from Lync / SfB to Trustedapplication. Ports based on LUCS Configuration. |
Lync / SfB Front End Pool | LUCS Server 02 | TCP | *7400 | Communication from Trustedapplication to Lync / SfB. Ports based on LUCS Configuration. |
Lync / SfB Front End Pool | LUCS Server 01 | TCP | *6100 | Communication from Lync / SfB to Trustedapplication. Ports based on LUCS Configuration. |
Lync / SfB Front End Pool | LUCS Server 02 | TCP | *6100 | Communication from Trustedapplication to Lync / SfB. Ports based on LUCS Configuration. |
Lync / SfB Front End Pool | LUCS Server 01 | TCP | *6200 | Communication from Lync / SfB to Trustedapplication. Ports based on LUCS Configuration. |
Lync / SfB Front End Pool | LUCS Server 02 | TCP | *6200 | Communication from Trustedapplication to Lync / SfB. Ports based on LUCS Configuration. |
Lync / SfB Front End Pool | LUCS Server 01 | TCP | *6300 | Communication from Trustedapplication to Lync / SfB. Ports based on LUCS Configuration. |
Lync / SfB Front End Pool | LUCS Server 02 | TCP | *6300 | Communication from Trustedapplication to Lync / SfB. Ports based on LUCS Configuration. |
Lync / SfB Front End Pool | LUCS Server 01 | TCP | *7500-7999 | Optional:Additional Connectors for high load environments. Not neccessary for smaler installations. |
Lync / SfB Front End Pool | LUCS Server 02 | TCP | *7500-7999 | Optional:Additional Connectors for high load environments. Not neccessary for smaler installations. |
*TrustedApplication Ports can be different depending on Trustedapplication registration on your environment
Source | Destination | Protocol | Destination Server Port | Comment |
---|---|---|---|---|
LUCS Server 01 | LUCS Server 02 | TCP | 19400 | LUCS-PS |
LUCS Server 02 | LUCS Server 01 | TCP | 19400 | LUCS-PS |
Lync / SfB Front End Pool | LUCS Server 01 | TCP | 19400 | SMD to LUCS-PS |
Lync / SfB Front End Pool | LUCS Server 02 | TCP | 19400 | SMD to LUCS-PS |
Lync / SfB Front End Pool | LUCS Server 01 | TCP | 19432 | SMD to LUCS-AM |
Lync / SfB Front End Pool | LUCS Server 02 | TCP | 19432 | SMD to LUCS-AM |
LUCS Server 01 | Lync / SfB Front End Pool | TCP | 19433 | LUCS-AM to SMD |
LUCS Server 02 | Lync / SfB Front End Pool | TCP | 19433 | LUCS-AM to SMD |
LUCS Server 01 | LUCS Server 02 | TCP | 4570 | LUCS-PS Activation Election |
LUCS Server 02 | LUCS Server 01 | TCP | 4570 | LUCS-PS Activation Election |
LUCS Server 01 | LUCS Server 02 | TCP | 4670 | LUCS-CIC Activation Election |
LUCS Server 02 | LUCS Server 01 | TCP | 4670 | LUCS-CIC Activation Election |
LUCS Server 01 | LUCS Server 02 | TCP | 4770 | LUCS-FeCore- Activation Election |
LUCS Server 02 | LUCS Server 01 | TCP | 4770 | LUCS-FeCore- Activation Election |
LUCS Server 01 | LUCS Server 02 | TCP | 4871 | LUCS-AM Activation Election |
LUCS Server 02 | LUCS Server 01 | TCP | 4871 | LUCS-AM Activation Election |
LUCS Server 01 | LUCS Server 02 | TCP | 4881 | LUCS-AC Activation Election |
LUCS Server 02 | LUCS Server 01 | TCP | 4881 | LUCS-AC Activation Election |
LUCS Server 01 | LUCS Server 02 | TCP | 4882 | LUCS-MM Activation Election |
LUCS Server 02 | LUCS Server 01 | TCP | 4882 | LUCS-MM Activation Election |
Internal Communication for LUCS components
If the components below are collocated on the same server, the following connections are attempted first (over net.pipe). If this is not possible then TCP will be used.
Source | Destination | Protocol | Destination Server Port | Comment |
---|---|---|---|---|
LUCS Server 01 | LUCS Server 01 | Net.pipe / TCP |
| LUCS-CIC |
LUCS Server 02 | LUCS Server 01 | TCP | 19415 | LUCS-CIC |
LUCS Server 01 | LUCS Server 01 | Net.pipe / TCP |
| LUCS-CI |
LUCS Server 02 | LUCS Server 01 | TCP | 19417 | LUCS-CI |
LUCS Server 01 | LUCS Server 01 | Net.pipe / TCP |
| LUCS-FeCore |
LUCS Server 02 | LUCS Server 01 | TCP | 19418 | LUCS-FeCore |
LUCS Server 01 | LUCS Server 01 | Net.pipe / TCP |
| ICH to FE-Core |
LUCS Server 02 | LUCS Server 01 | TCP | 19419 | ICH to FE-Core |
LUCS Server 01 | LUCS Server 01 | Net.pipe / TCP |
| CI to FE-Core |
LUCS Server 02 | LUCS Server 01 | TCP | 19421 | CI to FE-Core |
LUCS Server 01 | LUCS Server 01 | Net.pipe / TCP |
| AMCore |
LUCS Server 02 | LUCS Server 01 | TCP | 19422 | AMCore |
LUCS Server 01 | LUCS Server 01 | Net.pipe / TCP |
| MM to FE-Core |
LUCS Server 02 | LUCS Server 01 | TCP | 19423 | MM to FE-Core |
LUCS Server 01 | LUCS Server 01 | Net.pipe / TCP |
| AM to FE-Core |
LUCS Server 02 | LUCS Server 01 | TCP | 19430 | AM to FE-Core |
LUCS Server 01 | LUCS Server 01 | Net.pipe / TCP |
| AcPresenceInformation |
LUCS Server 02 | LUCS Server 01 | TCP | 19431 | AcPresenceInformation |
LUCS API | LUCS Server 01 | TCP | 19413 | How Luware-API connects to other Luware components through WCF channel |
LiveReporting | LUCS Server 01 | TCP | 19413 | How Luware-API connects to other Luware components through WCF channel to get additional Reporting (Statistics) information
|
Debugging / Troubleshooting
These ports are only used for debugging / troubleshooting. Before using these ports please consult with Luware.
*Source depends from where the telnet session will be opened.
Source | Destination | Protocol | Destination Server Port | Comment |
---|---|---|---|---|
* | LUCS Server 01 | TCP | 19513 | LUCS-LM (FE-Core) |
* | LUCS Server 02 | TCP | 19513 | LUCS-LM (FE-Core) |
* | LUCS Server 01 | TCP | 19515 | LUCS-CIC |
* | LUCS Server 02 | TCP | 19515 | LUCS-CIC |
* | LUCS Server 01 | TCP | 19517 | LUCS-CI |
* | LUCS Server 02 | TCP | 19517 | LUCS-CI |
* | LUCS Server 01 | TCP | 19518 | LUCS-ICH |
* | LUCS Server 02 | TCP | 19518 | LUCS-ICH |
* | LUCS Server 01 | TCP | 19519 | LUCS-SMD |
* | LUCS Server 02 | TCP | 19519 | LUCS-SMD |
* | LUCS Server 01 | TCP | 19520 | LUCS-AC |
* | LUCS Server 02 | TCP | 19520 | LUCS-AC |
* | LUCS Server 01 | TCP | 19521 | LUCS-AM |
* | LUCS Server 02 | TCP | 19521 | LUCS-AM |
* | LUCS Server 01 | TCP | 19522 | LUCS-MM |
* | LUCS Server 02 | TCP | 19522 | LUCS-MM |
AntiVir Exclusion Lists
Below is a list of executables, paths and files that you may need for your antivirus software exclusion rules.
LUCS Clients
Services/Processes
Role | Processes |
---|---|
Agent Assistant | LUCS.AA.Application.exe |
Directories
Component | Location |
---|---|
Installation directory (any Luware App) | "C:\Program Files (x86)\Luware AG" |
User Profile Folder | "%userprofile%\Tracing" |
File Types used by Luware | log, config, dll |
LUCS Server
Services/Processes
Role | Processes |
---|---|
Skype Core | ABServer.exe |
IIS | %systemroot%\system32\inetsrv\w3wp.exe |
SQL Front End Lync Local | %ProgramFiles%\Microsoft SQL Server\MSSQL12.LYNCLOCAL\MSSQL\Binn\SQLServr.exe |
SQL Front End RTC Local | %ProgramFiles%\ Microsoft SQL Server\MSSQL12.RTCLOCAL\MSSQL\Binn\sqlservr.exe |
SQL Front End RTC | %ProgramFiles%\Microsoft SQL Server\MSSQL12.RTC\MSSQL\Binn\sqlservr.exe |
SQL Front End Standard Edition | %ProgramFiles%\Microsoft SQL Server\MSSQL12.RTC\MSSQL\Binn\SQLServr.exe |
Windows Fabric | **\Windows Fabric |
Luware Services | LUCS.AC.Service.exe |
Directories
Component | Location |
---|---|
Windows Operating System | %systemroot%\System32\LogFiles |
%systemroot%\SysWow64\LogFiles | |
Windows Operating system .NET | %systemroot%\Microsoft.NET\assembly\GAC_MSIL |
Skype Program | %programfiles%\Skype for Business Server 2015 |
Skype Common files | %programfiles%\Common Files\Skype for Business Server 2015 |
Skype Online files | %programfiles%\Common Files\Skype for Business Online |
SQL | %ProgramFiles%\Microsoft SQL Server |
Office Web Apps | C:\Program Files\Microsoft Office Web Apps |
Office Web App Logs, Cache Location | C:\ProgramData\Microsoft\OfficeWebApps |
Windows assembly | **\assembly\GAC_MSIL |
Binaries | **\Binaries\ |
System log files | **\System32\LogFiles\ |
File Types used by Lync & Skype | AVI, SPX, TN, VF, WAV, WF, WMV, XML, BAK, EAS, LDF, MDF, NDF, TRN, VHD |
File Types used by Luware | WMA, log, config, dll |
Luware products (Default Path) | C:\Program Files\Luware AG* |
Registry | HKEY_LOCAL_MACHINE\SOFTWARE\Luware AG* |
Skype for Business Frontend Server(s)
The following items need to be excluded from scanning on all Skype for Business servers where the SMD component is installed.
Services/Processes
Role | Processes |
---|---|
Luware Services | LUCS.SMD.Service.exe |
Directories
Component | Location |
---|---|
File Types used by Luware | log, config, dll |
Luware products | C:\Program Files\Luware AG* |
Registry | HKEY_LOCAL_MACHINE\SOFTWARE\Luware AG* |
Environment Preparation
Creating DNS Entry in AD for the trusted application pool
The DNS entries must be created for each machine that will belong to the trusted application pool. This is done in the DNS section (forward lookup zones) of the server manager application.
Follow the steps:
- Go to the machine where Active Directory is configured
- On Windows Server 2008, go to Start> Run.
On Windows Server 2012, press Windows key + r. - Type msc, and then choose OK.
- In DNS Manager, expand <DNS server name>> Forward Lookup Zones.
- From the expanded list, click to select and then right-click the domain name.
From the displayed context menu, click the New Host (A or AAAA) option
DNS Manager - Creating New Host- On the opened "New Host" dialog, in the "Name" (uses parent domain name if blank) field, type the hostname of the computer or application pool FQDN for which you want to create a new record in the DNS server.
- Type the IP address of the target computer in the IP address
- Repeat step 7 and 8 for each host in the trusted application pool.
Example 1: Single Server
Type | FQDN | IP Address | Comment |
---|---|---|---|
A | TrustappPool.local-domain.com | x.x.x.101 | DNS Record for Lync/SfB TrustedapplicaitonPool One entry for every host inside pool. |
A | TrustAppServer1.local-domain.com | x.x.x.101 | DNS Record for Host within Lync/SfB TrustedapplicaitonPool |
The TrustAppServerX.local-domain.com record is the A record from the server, the A Record is normally created when joining the server to Active Directory.
Example 2: High Available / Two Servers
Type | FQDN | IP Address | Comment |
---|---|---|---|
A | TrustappPool.local-domain.com | x.x.x.101 x.x.x.102 | DNS Record for Lync/SfB TrustedapplicaitonPool One entry for every host inside pool |
A | TrustAppServer1.local-domain.com | x.x.x.101 | DNS Record for Host within Lync/SfB TrustedapplicaitonPool |
A | TrustAppServer2.local-domain.com | x.x.x.102 | DNS Record for Host within Lync/SfB TrustedapplicaitonPool |
The TrustAppServerX.local-domain.com record is the A record from the server, the A Record is normally created when joining the server to Active Directory.
Registering Trusted Application Pool on SfB Server Machine
One of the steps to set up the machines for LUCS installation is to run PowerShell scripts to manage SfB Server applications and trusted third-party applications.
On the machine where SfB Server is installed run the SfB Server Management Shell and follow the steps:
Create trusted application pool:
- Run "Get-CsSite"
Note down the SiteID you get as response
- Run "Get-CsService–Registrar"
Note down the Registrar you get as response
- Run New-CsTrustedApplicationPool –Identity [PoolName] –Registrar [Registrar] –Site [SiteId] -ComputerFqdn [First Computer’s FQDN]
- Run Enable-CsTopology
Example
New-CsTrustedApplicationPool -Identity lucs.dev.local -Registrar lyncserver.dev.local -Site: MainSite -ComputerFqdn lucs01.dev.local
If you have only one machine, the Identity and ComputerFqdn is the same. In this case the -ComputerFqdn can be skipped
Add computers to the pool:
If there are multiple computers that will host trusted applications, add them to an existing pool:
- Run Get-CsTrustedApplicationPool
Note down the "TrustedApplicationPool" you get as response
- Run "New-CsTrustedApplicationComputer -Identity [Computer‘s FQDN] -Pool [TrustedApplicationPool]"
- Run "Enable-CsTopology"
Example
New-CsTrustedApplicationComputer -Identity lucs02.dev.local -Pool lucs.dev.local
If a you want to add more computers later, you only need to run this command again.
More information about Power Shell commands is available in ‘Application management cmdlets in SfB Server’ section in the TechNet Library.
Register Trusted Applications Script
Register Trusted Application Endpoints Script
##############################################
# Script Name: Registering_LUCS_TM_TrustedApps.ps1
# Description: Create TrustedAppPool / Apps / Endpoints
#
#V1.0.0.0: Initial - Davide Iadarola
#V1.0.0.1: Update: Feature - Create default endpoint - Davide Iadarola
#V1.0.0.2: Update: Feature - Add ApplicationPrefix - Davide Iadarola
#V1.0.0.3: Update: Feature - Create LUCS/TM Conference Policy if not exists / Bugfix - Outputfile folder not created /
# Feature - Assign Conference Policy to Endpoints - Davide Iadarola
##############################################
#Config section:
$Application = "lucs"; #Options: lucs / tm
$ApplicationPrefix = ""; #Placeholder for TrustedappPoolName in TrustedApps and SipAddresses - Option is not required
$TrustedAppPool = ""; #LUCS or TM TrustedAppPool - FQDN
$SfBRegistrar = ""; #Skype for Business Registrar - FQDN
$SfBSite = ""; #Skype for Business Site
$TrustedAppComputers = @(
""
,""
,""
); #Hostname.domain.local
$SipDomain = ""; #Customer SIP Domain - sipdomain.local
$InstallMMSwitch = $false; #Options: $true / $false - Install LUCS MM?
$AdditionalEndpointsSwitch = $false; #Options: $true / $false - Add more Endpoints to the System
$AdditionalEndpointsStart = 10; #First Additional Endpoint
$AdditionalEndpointsEnd = 20; #Last Additional Endpoint
$ConfigOutputPath = "C:\Temp\LuwareTrustedAppConfig.txt"; #Path to Config Export
$DefaultEndpointSwitch = $false; #Options: $true / $false - Create default endpoint for failover scenarios
$DefaultEndpointPrefix = "defaultendpoint"; #Default endpoint name - "sip:" and "@sipdomain" will be added automaticaly
#------------------------------------------------------------------------------------------------------
#Do not Change below
#Add "-" to $Applicationprefix if used
if($ApplicationPrefix -ne ""){
$ApplicationPrefix = ($ApplicationPrefix + "-")
}
#Check if ConferencePolicy Tag:LucsService exists -> if not -> create ConferencePolicy
if((Get-CsConferencingPolicy -Identity "Tag:LucsService" -ErrorAction SilentlyContinue) -eq $null){
New-CsConferencingPolicy -Identity "Tag:LucsService" -AllowIPAudio $true -AllowIPVideo $true -AllowMultiView $false `
-Description "Lucs Contact Center Conferencing Policy" -AllowParticipantControl $true -AllowAnonymousParticipantsInMeetings $true `
-AllowExternalUserControl $true -EnableDialInConferencing $true -AllowConferenceRecording $false -EnableDataCollaboration $true `
-MaxVideoConferenceResolution "VGA"
}
#Save AdditionalEndpointsStart Var for Output
if($AdditionalEndpointsSwitch -eq $true){
$AdditionalEndpointsStartOutput = $AdditionalEndpointsStart;
}
else{
$AdditionalEndpointsStartOutput = "";
}
#Create TrustedAppPool
New-CsTrustedApplicationPool -Identity $TrustedAppPool -Registrar $SfBRegistrar -Site Site:$SfBSite -ComputerFqdn $TrustedAppComputers[0];
#Add Computers to Pool
Foreach($TrustedAppComputer in $TrustedAppComputers){
if($TrustedAppComputer -ne "" -and $TrustedAppComputer -ne $TrustedAppComputers[0]){
New-CsTrustedApplicationComputer -Identity $TrustedAppComputer -Pool $TrustedAppPool;
}
}
#Set Port Numbers
if ($Application -eq "lucs"){
$PortPrefix = 6;
$StartDefaultPort = 7000;
$StartAddPort = 7500;
}
elseif ($Application -eq "tm"){
$PortPrefix = 8;
$StartDefaultPort = 9000;
$StartAddPort = 9500;
}
# ICH Registration - Create TrustedApp ICH
New-CsTrustedApplication -ApplicationId ($ApplicationPrefix + $Application + "-ich") -TrustedApplicationPoolFqdn $TrustedAppPool `
-Port ("$PortPrefix" + "000");
#Create Default TrustedApps + Endpoints
$Count = 0;
Do{
New-CsTrustedApplication -ApplicationId ($ApplicationPrefix + $Application + "-connector-" + $Count) `
-TrustedApplicationPoolFqdn $TrustedAppPool -Port $StartDefaultPort;
New-CsTrustedApplicationEndpoint -ApplicationId ("urn:application:" + $ApplicationPrefix + $Application + "-connector-" + $Count) `
-TrustedApplicationPoolFqdn $TrustedAppPool `
-SipAddress ("sip:" + $ApplicationPrefix + $Application + "-connector-" + $Count + "@" + $SipDomain);
Get-CsTrustedApplicationEndpoint ("sip:" + $ApplicationPrefix + $Application + "-connector-" + $Count + "@" + $SipDomain) `
| Grant-CsConferencingPolicy -PolicyName "Tag:LucsService";
$StartDefaultPort = $StartDefaultPort + 100;
$Count++;
}
While($Count -le 4)
#Additional Endpoints
if($AdditionalEndpointsSwitch -ne $false){
Do{
New-CsTrustedApplication -ApplicationId ($ApplicationPrefix + $Application + "-connector-" + $AdditionalEndpointsStart) `
-TrustedApplicationPoolFqdn $TrustedAppPool -Port $StartAddPort;
New-CsTrustedApplicationEndpoint -ApplicationId ("urn:application:" + $ApplicationPrefix + $Application + "-connector-" `
+ $AdditionalEndpointsStart) -TrustedApplicationPoolFqdn $TrustedAppPool -SipAddress ("sip:" + $ApplicationPrefix + $Application `
+ "-connector-" + $AdditionalEndpointsStart + "@" + $SipDomain);
Get-CsTrustedApplicationEndpoint ("sip:" + $ApplicationPrefix + $Application + "-connector-" + $AdditionalEndpointsStart + "@" + $SipDomain) `
| Grant-CsConferencingPolicy -PolicyName "Tag:LucsService";
$StartAddPort = $StartAddPort + 1;
$AdditionalEndpointsStart++;
}
While($AdditionalEndpointsStart -le $AdditionalEndpointsEnd)
}
#CR Registration
$Count = 1;
New-CsTrustedApplication -ApplicationId ($ApplicationPrefix + $Application + "-cr") -TrustedApplicationPoolFqdn $TrustedAppPool `
-Port ("$PortPrefix" + "200");
Do{
New-CsTrustedApplicationEndpoint -ApplicationId ($ApplicationPrefix + $Application + "-cr") -TrustedApplicationPoolFqdn $TrustedAppPool `
-SipAddress ("sip:" + $ApplicationPrefix + $Application + "-conversationrecording-" + $count + "@" + $SipDomain);
$Count++;
}
While($Count -le 2)
#MM Registration
if($InstallMMSwitch -eq $true -and $Application -eq "lucs"){
New-CsTrustedApplication -ApplicationId ($ApplicationPrefix + $Application + "-mm") -TrustedApplicationPoolFqdn $TrustedAppPool -Port 6300;
New-CsTrustedApplicationEndpoint -ApplicationId ("urn:application:" + $ApplicationPrefix + $Application + "-mm") `
-TrustedApplicationPoolFqdn $TrustedAppPool -SipAddress ("sip:" + $ApplicationPrefix + $Application + "-mailmanager@" + $SipDomain);
}
#AC Registration
New-CsTrustedApplication -ApplicationId ($ApplicationPrefix + $Application + "-ac") `
-TrustedApplicationPoolFqdn $TrustedAppPool -Port ("$PortPrefix" + "100");
New-CsTrustedApplicationEndpoint -ApplicationId ("urn:application:" + $ApplicationPrefix + $Application + "-ac") `
-TrustedApplicationPoolFqdn $TrustedAppPool -SipAddress ("sip:" + $ApplicationPrefix + $Application + "-agentcontrol@" + $SipDomain);
#SMD Registration
$ServerAppPrio = Get-CsServerApplication | ?{$_.Identity -like "*$SfBRegistrar/TranslationService"} | Select-Object Priority;
$ServerAppPrio.Priority = $ServerAppPrio.Priority + 1;
New-CsServerApplication -Identity ("Registrar:$SfBRegistrar/" + $Application + "-SMD") -Uri ("http://www.luware.net/" + $Application `
+ "-SMD") -Priority $ServerAppPrio.Priority -Critical $False -Enabled $True;
#Default endpoint
if($DefaultEndpointSwitch -eq $true){
#Create default endpoint
New-CsTrustedApplicationEndpoint -ApplicationId ($ApplicationPrefix + $Application + "-ich") -TrustedApplicationPoolFqdn $TrustedAppPool `
-SipAddress ("sip:" + $ApplicationPrefix + $Application + "-" + $DefaultEndpointPrefix + "@" + $SipDomain) `
| Grant-CsConferencingPolicy -PolicyName "Tag:LucsService";
}
#------------------------------------------------------------------------------------------------------
# Output
$ichport = ("$PortPrefix" + "000");
$acport = ("$PortPrefix" + "100");
$crport = ("$PortPrefix" + "200");
$connectorprefix = ("$ApplicationPrefix" + "$Application" + "_connector");
$connector0 = ("$ApplicationPrefix" + "$Application" + "_connector0");
$connector1 = ("$ApplicationPrefix" + "$Application" + "_connector1");
$connector2 = ("$ApplicationPrefix" + "$Application" + "_connector2");
$connector3 = ("$ApplicationPrefix" + "$Application" + "_connector3");
$connector4 = ("$ApplicationPrefix" + "$Application" + "_connector4");
#Change Var if
if($AdditionalEndpointsSwitch -eq $false){
$AdditionalEndpointsStart = "";
$AdditionalEndpointsEnd = "";
$connectorprefix = "";
}
if($InstallMMSwitch -eq $true){
$mmurn = ("urn:application:" + $ApplicationPrefix + $Application + "-mm");
$mmport = ("$PortPrefix" + "300");
$mmuseragent = ($ApplicationPrefix + $Application + "-mm");
$mmtrustedapppool = "$TrustedAppPool";
$mmservertype = "MM";
}
else{
$mmurn = "";
$mmport = "";
$mmuseragent = "";
$mmtrustedapppool = "";
$mmservertype = "";
}
if($DefaultEndpointSwitch -eq $true){
$DefaultEndpointSipAddress = "sip:$DefaultEndpointPrefix@$SipDomain";
}
else{
$DefaultEndpointSipAddress = "";
}
$ApplicationPrefixAndApplication = ($ApplicationPrefix + $Application);
$OutputConfig = @("
Please enter those settings in the Webconfigurator under the following chapters:
Settings -> Topology -> Frontendpools:
Name: $SfBRegistrar
-------------------------------------------------------------------------------------------------------
Settings -> Topology -> Trusted Application Pools
FQDN: $TrustedAppPool
Select: $SfBRegistrar
-------------------------------------------------------------------------------------------------------
Settings -> Topology -> Trusted Applications
********* ICH *********
URN: urn:application:$ApplicationPrefixAndApplication-ich
Port: $ichport
User Agent: $ApplicationPrefixAndApplication-ich
Application Pool: $TrustedAppPool
Server Type: ICH
********* AC *********
URN: urn:application:$ApplicationPrefixAndApplication-ac
Port: $acport
User Agent: $ApplicationPrefixAndApplication-ac
Application Pool: $TrustedAppPool
Server Type: AC
********* CR *********
URN: urn:application:$ApplicationPrefixAndApplication-cr
Port: $crport
User Agent: $ApplicationPrefixAndApplication-cr
Application Pool: $TrustedAppPool
Server Type: CR
********* MM *********
URN: $mmurn
Port: $mmport
User Agent: $mmuseragent
Application Pool: $mmtrustedapppool
Server Type: $mmservertype
-------------------------------------------------------------------------------------------------------
Settings -> Topology -> Components
********* CR *********
SipUris: sip:$ApplicationPrefixAndApplication-conversationrecording-1@$SipDomain;
sip:$ApplicationPrefixAndApplication-conversationrecording-2@$SipDomain
********* ICH *********
ConnectorApplicationURN: urn:application:$connector0
ConnectorApplicationURN1: urn:application:$connector1
ConnectorApplicationURN2: urn:application:$connector2
ConnectorApplicationURN3: urn:application:$connector3
ConnectorApplicationURN4: urn:application:$connector4
ConnectorEnd: $AdditionalEndpointsEnd
ConnectorPrefix: urn:application:$connectorprefix
ConnectorStart: $AdditionalEndpointsStartOutput
DefaultEndpointSipAddress: $DefaultEndpointSipAddress
********* SMD *********
ManifestURI: http://www.luware.net/$ApplicationPrefixAndApplication-AgentMonitor
-------------------------------------------------------------------------------------------------------
PLEASE BE AWARE THAT YOU NEED TO FINALIZE THE CONFIGURATION OF EACH COMPONENT
")
#Create Output
if(Test-Path ($ConfigOutputPath.Substring(0, $ConfigOutputPath.lastIndexOf('\')))){
$OutputConfig > $ConfigOutputPath;
}
else{
New-Item -Path ($ConfigOutputPath.Substring(0, $ConfigOutputPath.lastIndexOf('\'))) -ItemType Directory;
$OutputConfig > $ConfigOutputPath;
}
#------------------------------------------------------------------------------------------------------
Write-Host "Script finished - Please Run Enable-CsTopology command and check the output file - Path: $ConfigOutputPath" `
-ForegroundColor Yellow;
Registering Trusted Applications and Endpoints on SfB Server Machine
The following services requires SfB trusted applications:
- ICH (Interactive Conversation Handler)
- AC (Agent Controller or Agent Configurator)
- CR (Conversation Recording)
- MM (Mail Manager)
For the registration of each trusted application the following command is used:
Register Trusted Applications
New-CsTrustedApplicationComputer -Identity lucs02.dev.local -Pool lucs.dev.local
New-CsTrustedApplication –ApplicationId […] -TrustedApplicationPoolFqdn […] -Port […]
After that for each trusted application a trusted application endpoint should be created:
Register Trusted Application Enpoints
New-CsTrustedApplicationEndpoint -ApplicationId […] -TrustedApplicationPoolFqdn […] -SipAddress […]
The information about registered applications and endpoints ports can be received using the following commandlet:
Get Trusted Applications and Endpoints
Get-CsTrustedApplication –Filter *trust*
Get-CsTrustedApplicationEndpoint
When several machines are used as application servers, the services have to be configured and installed on each of them.
Note : Some configuration properties (e.g. activity order) depend on the machine where the service is installed. When the activity order is the same for an active-passive service, the first started instance will become active.
Some of the information that should be entered into LUCS Configurator during service configuration (relates to ICH, AC, CR, MM services) can be obtained over the SfB Server Management Shell:
Get-CsTrustedApplication
If for the registration of the SfB Applications the default settings are used, the following components use the listed ports:
ICH | Connector 0-4 (Belongs to ICH) | AC | CR | MM | SMD |
---|---|---|---|---|---|
6000 | 7000 | 6100 | 6200 | 6300 | no port |
This is a recommendation, but the final port choice depends on the availability of these ports. The trusted applications should be registered to free ports that are not used by other applications. E.g. If a trusted application is registered on the port used by another application, it will be written in the log file and the trusted application will not work.
Some services are required to have SRV records created in AD. They must be created for each machine where LUCS will be installed:
- Go to your Active Directory Machine and run DNS Manager
- Select and expand Forward Lookup Zone domain name and after that select _tcp folder
- Right-click the _tcpfolder and theOther New Records option
As Resource Record Type select Service Location (SRV) option
Service location selection in DNS managerCreate new SRV records with the following parameters:
Service
Protocol
Priority
Port
Host
_lucsps
_tcp
1
19400
FQDN of the target host where service installed
_lucsaa
_tcp
1
19412
FQDN of the target host that where service installed
_lucslm
_tcp
1
19418
FQDN of the target host that where service installed
Since LUCS 2.5 SRV records became "instance name"-dependent and have to be configured in the following format:
- If the ‘Instance Name’ is set (not null or empty) use format < old SRV record >-< Instance Name>
Example: _lucsps-red.dev.local
- If the ‘Instance Name’ is null or empty, use old SRV record format e.g. _lucsps.dev.local
LUCS System Componets | Protocol | Priority | Port | Host
|
---|---|---|---|---|
_lucsps-<instancename> | _tcp | 1 | 19400 | FQDN of the target host where service installed |
_lucsaa-<instancename> | _tcp | 1 | 19412 | FQDN of the target host that where service installed |
_lucslm-<instancename> | _tcp | 1 | 19418 | FQDN of the target host that where service installed |
SRV Record Examples
For Single LUCS Server
Example Single Server, Without Instance Name
Service | Protocol | Domain | Prio | Weight | Port | Host offering the service | Comment |
---|---|---|---|---|---|---|---|
_lucsps | _tcp | >local-domain.com | 1 | 0 | 19400 | TrustAppServer1.local-domain.com | Local domain where the server is joined |
_lucslm | _tcp | >local-domain.com | 1 | 0 | 19418 | TrustAppServer1.local-domain.com | Local domain where the server is joined |
_lucsaa | _tcp | >sip-domain.com | 1 | 0 | 19412 | TrustAppServer1.local-domain.com | SIP domain of the agents’ sip-address |
Example Single Server, With placeholder for Instance Name
Service | Protocol | Domain | Prio | Weight | Port | Host offering the service | Comment |
---|---|---|---|---|---|---|---|
_lucsps-<instancename> | _tcp | >local-domain.com | 1 | 0 | 19400 | TrustAppServer1.local-domain.com | Local domain where the server is joined |
_lucslm-<instancename> | _tcp | >local-domain.com | 1 | 0 | 19418 | TrustAppServer1.local-domain.com | Local domain where the server is joined |
_lucsaa-<instancename> | _tcp | >sip-domain.com | 1 | 0 | 19412 | TrustAppServer1.local-domain.com | SIP domain of the agents’ sip-address |
Example Single Server, With Instance Name PRODUCTION
Service | Protocol | Domain | Prio | Weight | Port | Host offering the service | Comment |
---|---|---|---|---|---|---|---|
_lucsps-PRODUCTION | _tcp | >local-domain.com | 1 | 0 | 19400 | TrustAppServer1.local-domain.com | Local domain where the server is joined |
_lucslm-PRODUCTION | _tcp | >local-domain.com | 1 | 0 | 19418 | TrustAppServer1.local-domain.com | Local domain where the server is joined |
_lucsaa-PRODUCTION | _tcp | >sip-domain.com | 1 | 0 | 19412 | TrustAppServer1.local-domain.com | SIP domain of the agents’ sip-address |
For High-Availability LUCS Server
Example High Availability / 2 Servers, Without Instance Name
Service | Protocol | Domain | Prio | Weight | Port | Host offering the service | Comment |
---|---|---|---|---|---|---|---|
_lucsps | _tcp | >local-domain.com | 1 | 0 | 19400 | TrustAppServer1.local-domain.com | Local domain where the server is joined |
_lucsps | _tcp | >local-domain.com | 1 | 0 | 19400 | TrustAppServer2.local-domain.com | Local domain where the server is joined |
_lucslm | _tcp | >local-domain.com | 1 | 0 | 19418 | TrustAppServer1.local-domain.com | Local domain where the server is joined |
_lucslm | _tcp | >local-domain.com | 1 | 0 | 19418 | TrustAppServer2.local-domain.com | Local domain where the server is joined |
_lucsaa | _tcp | >sip-domain.com | 1 | 0 | 19412 | TrustAppServer1.local-domain.com | SIP domain of the agents’ sip-address |
_lucsaa | _tcp | >sip-domain.com | 1 | 0 | 19412 | TrustAppServer2.local-domain.com | SIP domain of the agents’ sip-address |
Example High Availability / 2 Servers, With placeholder for Instance Name
Service | Protocol | Domain | Prio | Weight | Port | Host offering the service | Comment |
---|---|---|---|---|---|---|---|
_lucsps-<instancename> | _tcp | >local-domain.com | 1 | 0 | 19400 | TrustAppServer1.local-domain.com | Local domain where the server is joined |
_lucsps-<instancename> | _tcp | >local-domain.com | 1 | 0 | 19400 | TrustAppServer2.local-domain.com | Local domain where the server is joined |
_lucslm-<instancename> | _tcp | >local-domain.com | 1 | 0 | 19418 | TrustAppServer1.local-domain.com | Local domain where the server is joined |
_lucslm-<instancename> | _tcp | >local-domain.com | 1 | 0 | 19418 | TrustAppServer2.local-domain.com | Local domain where the server is joined |
_lucsaa-<instancename> | _tcp | >sip-domain.com | 1 | 0 | 19412 | TrustAppServer1.local-domain.com | SIP domain of the agents’ sip-address |
_lucsaa-<instancename> | _tcp | >sip-domain.com | 1 | 0 | 19412 | TrustAppServer2.local-domain.com | SIP domain of the agents’ sip-address |
Example High Availability / 2 Servers, With Instance Name PRODUCTION
Service | Protocol | Domain | Prio | Weight | Port | Host offering the service | Comment |
---|---|---|---|---|---|---|---|
_lucsps-PRODUCTION | _tcp | >local-domain.com | 1 | 0 | 19400 | TrustAppServer1.local-domain.com | Local domain where the server is joined |
_lucsps-PRODUCTION | _tcp | >local-domain.com | 1 | 0 | 19400 | TrustAppServer2.local-domain.com | Local domain where the server is joined |
_lucslm-PRODUCTION | _tcp | >local-domain.com | 1 | 0 | 19418 | TrustAppServer1.local-domain.com | Local domain where the server is joined |
_lucslm-PRODUCTION | _tcp | >local-domain.com | 1 | 0 | 19418 | TrustAppServer2.local-domain.com | Local domain where the server is joined |
_lucsaa-PRODUCTION | _tcp | >sip-domain.com | 1 | 0 | 19412 | TrustAppServer1.local-domain.com | SIP domain of the agents’ sip-address |
_lucsaa-PRODUCTION | _tcp | >sip-domain.com | 1 | 0 | 19412 | TrustAppServer2.local-domain.com | SIP domain of the agents’ sip-address |
It is recommended to use a dedicated Local Computer Network Service Account to start LUCS services.
Active Directory Service Accounts and Groups
The following service account and groups are mandatory:
Name |
| Comment |
---|---|---|
CIC User like “srv_lucs_cic” | Member of Group: Csadministrator | The service „Customer Infrastructure Connector CIC“ need a user to connect the Lync PowerShell to subscribe services. |
LucsSystem | Type: AD Security Group Scope, Global | All computer-FQDN in this group has read and write access to the LUCS database. This function requires LUCS version 2.3 or above. |
LucsFEAdmin | Type: AD Security Group Scope, Global | This group is needed for the LUCS Front-End system admins. |
Optional Groups
The following service account and groups are optional based on requirements:
Name |
| Comment |
---|---|---|
Exchange User account like “srv_lucs_ci” | Full Access (read and write) to LUCS related exchange mailboxes | The service „Calendar Integrator CI“ is used to get the opening hours. |
LucsExcelReporting | Type: AD Security Group Scope, Global | All users in this group has the right, to synchronize the Excel reports. |
LucsSsrsReporting | Type: AD Security Group Scope, Global | All users in this group has the right, to synchronize the SSRS reports. |
UCID | UC LUCS Application 026 |