Display Name: Desktop Authority Administrative ServiceService Name: DAAdminSvc
Historical Data: Formerly known as the ScriptLogic Service
Location: For 64-bit OS: “C:\Windows\SysWOW64”. For 32-bit OS: “C:\Windows\System32”
Executable file name: DAAdminSvc.exe
Purpose: Provides the “Run as admin” technology and remotely installs the Client Install Service on client machines.
The Desktop Authority Administrative service enables Desktop Authority to perform tasks that require administrative rights without sacrificing user-level security at the workstation. This service helps Desktop Authority perform these specialized tasks by installing a client version of the Desktop Authority Administrative service to each client machine and a complementary version of the DA Administrative service to one or more Domain Controllers within the domain.
This service requires two unique user accounts. The Server user account (server side service) must have Local Admin rights to all workstations. In most circumstances, this account will be one that is a member of the Domain Admins group.
The Client User account (client side service) is used on each workstation to make registry changes, install software, add printers, synchronize time and perform any other task that may require elevated privileges during the logon, logoff or shutdown events. The Client User account (client side service) should be a member of the Domain Users group.
This service is also used by Server Manager to report back on the User and Computer Management replication status.
Display Name: Desktop Authority Manager Service
Service Name: Desktop Authority Manager Service
Historical Data: New service introduced in DA 9.0
Location: \\DA_Server_Name\slogic$
Executable file name: ScriptLogic.Manager.WinSvc.exe
Purpose: The Manager Service is used to manage the Web based Manager, replication, and connectivity and communication between the Manager and the database.
This service requires the credentials for a user account that is local administrator of OpsMaster server
and any other servers that will host Desktop Authority services.
The Manager Service is given SA access to the SQL database server during the installation of Desktop Authority.
The installation defaults this service to port 8085, but it can be changed during the install to suit the specific environment. This port can also be changed using the Desktop Authority Setup Tool.
Display Name: Desktop Authority Operations ServiceService Name: Desktop Authority OpsMaster Service
Historical Data: Formerly known as the DA OpsMaster Service
Location: \\DA_Server_Name\slogic$\OpsMasterService\bin
Executable file name: ScriptLogic.Server.exe
Purpose: The Operations Service is a background service that is used to manage and configure Desktop Authority's plugins. The ETLProcessor and ReportScheduler plugins are used to manage collected data and execute scheduled reports.
This service requires the credentials for a user account that is local admin of OpsMaster server and any other servers that host the DA Administrative services in order to collect data.
This service moves files from the server that hosts the DA Administrative service (default path - C:\Program Files\Dell\Desktop Authority\etl cache for versions: 9.2, 9.3, 10.0.x and 10.1.x upgraded/above or C:\Program Files\Quest\Desktop Authority\etl cache for new installations) to the OpsMaster server where Desktop Authority is installed to (default path - C:\Program Files\Dell\Desktop Authority\Desktop Authority Manager\OpsMasterService\ETLFileRepository for versions: 9.2, 9.3, 10.0.x and 10.1.x upgraded/above or C:\Program Files\Quest\Desktop Authority\Desktop Authority Manager\OpsMasterService\ETLFileRepository for new installations). Since the ETLProcessor plugin connects to the "\\ServerName\slETL$ (file://servername/slETL$)" share, the user account configured for the Operations Service must have access to that share where the DA Administrative service is installed to.
The Operations service is given SA access to the SQL database server during the installation of Desktop Authority.
The installation defaults this service to port 8017, but it can be changed during the install, to suit the specific environment. This port can also be changed using the Desktop Authority Setup Tool.
Display Name: Desktop Authority Update ServiceService Name: UpdateService
Historical Data: Formerly known as the Update Service
Location: "C:\Program Files (x86)\Dell\Desktop Authority\Update Service\" for versions: 9.2, 9.3, 10.0.x and 10.1.x upgraded/above or "C:\Program Files (x86)\Quest\Desktop Authority\Update Service\" for new installations.
Executable file name: Daupdsvc.exe
Purpose: The Update Service offers an encrypted and secure connection to Quest owned websites.
The user account configured for this service must be a member of the Local Administrators group on the server in which the service is being installed to. This account must have Local Administrator access to the Operations Master server share \\Servername\slogic$ in order to read the Register.ini file for licensing purposes, as well as for access to the Internet.
IIS Application Pool
Name: DaAppPool
Location: IIS Management Console
Purpose: Desktop Authority’s web based Console uses IIS to host the application. The IIS Application pool identity is used to allow IIS to host web applications/virtual folders as standalone processes to avoid application crashes. Port 443 is required for IIS.
Domain user credentials are required so it can log information to the database. If Windows Authentication is chosen for the SQL database authentication, the account selected for the IIS Application pool will need to have login access to the database.