® place at the SQL Server.

At the SQL Server run the new

Upgrade#.SQL script files through the SQL Server
Management Studio.

8. At the Comm Server in the WinDSX folder locate the

[Link] file. Edit the file and change the 0 to a 1 and
save and close. Locate the [Link] and right click and
select "Run as Administrator". Login and check the
database. If you had selected this PC is Comm Server,
WinDSX SQL Upgrade uncheck it now and Restart the Program. If configured
Follow these simple steps and you will be on your way to to AutoStart, Workstation should show Comm Loss in
using the latest DSX SQL Software. Read through all the bottom right. Start the DSX Comm Service and the
steps in this document before proceeding. Make a Comm Loss in Workstation should change to show
backup of AcsData / AcsLog databases. Primary Online.

1. Locate the WinDSX folder on the Comm Server. Inside 9. At each Client PC, perform steps 3 - 5. Once the
the WinDSX folder locate the MdbStruc subfolder, for software is installed locate the [Link] program in the
example C:\WinDSX\MdbStruc\. WinDSX folder. Right click on [Link] and select “Run
Look in this folder and note the highest numbered as Administrator”. Repeat this for all Client PCs. Run
Upgrade#.sql script file. Once the new software is [Link] from the \WinDSX folder to attach to a
loaded you will view this same folder to see what new different SQL Server if needed.
Upgrade Script files are present that will need to be ran
at the SQL Server in the Management Studio. NOTE: Access Levels are upgraded at 4.5.12 and at
4.8.50 at the Comm Server or DailyOps PC. The
2. At the Comm Server, in DataBase go to Setup/System [Link] Process may have to be done Twice.
Parameters/Yes/No Options and make sure “This PC is
Comm Server” is selected. Close the program on all PCs. SCRIPTS When running Scripts if you receive
The DSXComm, DSXKey, and DSXDbas services, if found, “Completed with Errors”, move on to the next script.
will need to be stopped. It is ok to run a script more than once.
• From WinDSX SQL 4.0 – 4.7.15 run all scripts.
3. Navigate to the Install folder containing the new [Link] – Up
software and locate the [Link]. Right click and select • From WinDSX SQL 4.7.16 and higher - run
“Run as Administrator”. The system will respond by [Link] – Up
displaying what version is currently installed. When • From WinDSX SQL 4.8.65 and higher - run
prompted for “Repair or Remove” select “Remove” as this [Link] – Up
removes the program but leaves the folders and • From SQL Server 2008 to SQL Server 2012 and
configuration data. higher - Run Upgrade to [Link]

4. From the Install folder containing the new software, Important Docs on the Flash Drive
right click on [Link] and select “Install”. An older \Docs - Hardware - Hardware Installation Manuals,
version may have to be uninstalled before this one can Quick Cards, LAN-D Instructions, and UL Manuals.
be installed. \Docs - Mobile - Mp4 that shows how to use the mobile
app and a pdf on how to configure it.
5. From the Install folder containing the new software, \Docs - Software - Software installation and API
right click on [Link] and select “Run as configuration docs. Special application instructions.
Administrator” making sure to install it to the same \Docs - User - Power Point, Mp4, PDF Training
folder the older version was installed in. materials on new software. Enrollment Readers.
6. In the WinDSX folder on the Comm Server right click
on the [Link] file and select “Run as Administrator”.
Remote Sessions –
If the DataBase will be managed remotely, it is best to
Do Not Log In. Cancel and Exit.
remote into a Client PC instead of the Comm Server. If
you remote into the Comm Server, it should be set as a
7. From the upgraded Comm Server locate the
Service.
\WinDSX\MdbStruc subfolder, locate the new
Upgrade#.sql script files and copy them to a temporary

DSX Access Systems, Inc. 214-553-6140 [Link] (10/2023)

Permissions Moving Databases to new
All Users require Full Control over their Local WinDSX SQL Server
folder and the Shared WinDSX folder (typically the There are two SQL databases that need to be moved,
Comm Server). SQL Server 2019 and higher require AcsData and AcsLog. If you are moving from SQL 2012
Windows Authentication. and lower to SQL 2016 or higher you must run the
\WinDSX\mdbstruc\[Link] script using the
For Mixed or SQL Server Authentication select SQL SQL Management Studio.
Server Authentication and enter a Login and Password.
When setting up the Client PCs the first time [Link] If all you are doing is moving to a different SQL Server,
is started it will launch SQLSetup. Enter the Name of the go to each DSX client, and with the program closed, run
SQL Server and the Username and Password you \WinDSX\[Link]. This program will allow you to
entered in the SQL Server. This will be done on all PCs enter the connection properties of the new SQL server
the first time the program is run. for WinDSX to use. Start the program and set the
DataBase Path to the Shared Folder if it changed. UNC is
For Windows Authentication or Named Pipes select preferred. Close/Restart.
Windows Authentication. When setting up the Client
PCs, the first time [Link] is started, it will launch Moving the Comm Server to a
SQLSetup. Enter the Name of the SQL Server. Do not
enter a Username or Password. This will be done on all
Virtual Server
PCs the first time the program is run. Rights and To migrate the Comm Server to a Virtual or new PC.
permissions must be given to the user in the SQL 1. Exit the program and Stop all DSX Services on the
Management Studio and AD. For more info see Active Comm Server and all clients. Sort the WinDSX folder by
Directory Auth on this page. file type and show file extensions. There should be no
.ldb files. If there are, delete them. If you can’t, there is a
If the system is on a Domain, it requires a Domain User program or service still running.
Account with Local Administrative Rights to the Local
folder, the Comm Server PC folder or Shared database 2. Copy the WinDSX folder from the old Comm Server to
folder if different and both SQL databases. the new one. Leave all subfolders. Remove all files from
the root of \WinDSX that do not have a .mdb extension.
If the System is in a WorkGroup and the Comm Server is
also the SQL Server, Create the Users for each Client 3. Install the WinDSX software into the \WinDSX folder
and Comm Server in Computer Management\Local that was just copied to the new server. It may be
Users and Groups\Users. In the SQL Management necessary to adjust IP Addresses under System
Studio \Security\Logins add these same accounts from Parameters, Comm Ports and in the LAN Modules.
the local Comm Server and set them to Windows Recreate the Services and Make a new Softkey.
Authentication and give them Data_Reader,
Data_Writer, Owner, and Public rights to the AcsData IMPORTANT The DSX program and services must be
and AcsLog databases. closed before Sharing the WinDSX folder or setting
Permissions to it.
SQL 2012 and up Additional
Configuration Active Directory Authentication
In SQL 2012 and up the TCP/IP protocol and Named Operator Logins can be authenticated by Active
Pipes must be enabled. Start the SQL Server Directory instead of WinDSX. To configure this, the
Configuration Manager navigate to Protocols for WinDSX SQL Operators use the same Login Name as
MSSQL Server. Enable Named Pipes & TCP/IP. Double they do in Windows™. Their Login name is entered like
click on the TCP/IP protocol name. On the TCP/IP always under Operator Passwords. The Operator is
Properties window, Click the IP Addresses tab. Scroll all assigned a Password Profile but is not assigned a
the way down to the bottom. Make sure the TCP Port is Password. When WinDSX SQL receives a login from an
set to 1433. Operator that does not have a password stored in
In SQL Server 2012 and up you must manually turn on WinDSX SQL, it sends the login request to Active
the SQL Server Browser Service. Go to Services and find Directory (AD) for authentication. If AD authenticates
SQL Server Browser. Double click the Service. Change the operator, they are given access to WinDSX SQL
the startup type from “Disabled” to “Automatic.” Click according to the Password Profile assigned to them. To
the START button. Enable AD Authentication run Upgrade Script # 9 at the
SQL Server. When entering the Operator in WinDSX skip

DSX Access Systems, Inc. 214-553-6140 [Link] (10/2023)

the Password Fields just entering the Operator name between the Communication Server and the field
and assigning a Password Profile. If you click on the controllers and between Comm Server and
password field, you must cancel and start over adding Workstations. This feature requires firmware version
the Operator. 3214 or higher in all controllers and that the feature be
enabled in the DSX SoftKey. With Version 5 and 6
Primary and Backup SQL Servers Software there is no charge for this feature, but it will
WinDSX SQL allows for the definition of both a primary have to be enabled in the software license
and backup SQL Server and Database Path. If the [Link]. You will need to email the file to DSX
primary SQL Server fails, the software can be shut down Technical Support so it can be changed.
and restarted and it will connect to the backup SQL Each Location can have an Encryption Key entered to
Server and Database Path. DSX does not automatically encrypt the communications between the Comm Server
reconcile the databases when the primary returns. This and that Location’s controllers. The AES 256-bit
feature will facilitate off site backup SQL Servers that Encryption propagates itself from the Master Controller
cannot use SQL Clustering. Once the software has been to all subsequent controllers at power up.
upgraded, run the [Link] program in the
WinDSX folder. Each time you run it you can define a For Controllers (Location)
SQL Server to attach to and specify if it is the primary or To enable encryption, enter up to 32 keyboard
backup SQL Server. characters in the "Encryption Key" field on the General
Tab of each Location. The key cannot be viewed once
Reports .RPT files entered. Starting at the Master Controller power each
When loading 6.0.24 and up the Report templates are controller down and back up.
TLS1.2 only, unless you are using Windows Auth. If SQL
Auth is being used on a non TLS1.2 SQL Server, the For Client PCs (Workstations)
alternate TLS reports must be unzipped into the root of To enable encryption between the Comm Server and
all \WinDSX Folders including the Shared Folder. the Client PCs edit the System Parameters at the Comm
Server and go to the Communications Server Tab. Enter
Software License Key- SoftKey up to 32 keyboard characters in the Encryption Key
All New Version 6 Installations, Upgrades from 4.8 or field. Close and restart the program and close and
lower, and Upgrades from Version 5 will require the restart the DSX Comm Service. Restart the program on
purchase of a WinStart-SQL and the creation of a all Client PCs.
SoftKey using the USB flash drive Media from DSX.

SQL Upgrade Software does not contain the ability to Deleting and Creating Services
create or modify a softkey. If the Key needs to be When upgrading from 4.8 or below, the DSX Services
updated, you will need to send the [Link] and need to be deleted and recreated. The same is true
a PO to Orders@[Link] when the Operating System is upgraded on the Comm
Server PC in place.

DSX Key Monitor Notes: Check for the following services and if found, Stop them
and look at the logon properties at the Logon Tab
• There is a 30 second delay between the DSX
specifically to see what account is assigned to them.
Comm Server program being started and the program
Once Stopped, delete the services with the instructions
allowing access to Card Holders.
below: DSXComm, DSXDbas, and DSXKey. Once the
• The DSX_Key_Monitor.exe program will be
Services are deleted, the DSXComm and DSXDbas can
started and stopped by the Comm Server program. If
be recreated with newer provided tools and the
you configure Comm Server to run as a Service, it will
instructions on the next page. The DSXKey service is
start the DSX_Key_Monitor.exe program without
deleted but not recreated.
configuring the Key Monitor program as a Service.
• The DSX-USB Flash Drive contains a copy of To Delete a Service, Open an Administrative Command
your [Link] Softkey. If needed, it can be Prompt and Type: SC Delete ServiceName and press
copied onto a new computer in the same domain. Enter.

AES 256 Comm Encryption

DSX communications can now be secured using AES
256-bit Encryption. The encryption can be implemented

DSX Access Systems, Inc. 214-553-6140 [Link] (10/2023)

Comm Server as a Service DataBase as a Service
The Communications Server program typically runs as a The DataBase typically runs as an application and is
process in the background and is usually started by the usually started by the launching of the [Link] and is
launching of the Workstation program ([Link]) and is terminated when the program is exited. The DataBase
terminated when the Workstation program is closed. program can be configured to run as a Service. This will
The Comm Server program can run as a Service without allow the program to run as a Service on a PC that does
having a user logged into the Windows operating not have a user logged into the Desktop. Requires
system. 5/6.0.17 and up.

Below are the steps involved with setting the 1. You must login as a user with full administrative
Communications Server program up as a Service. rights; you cannot install Services if your login
account is not an Administrator.
1. You must log in as a user with full administrator 2. Load the WinDSX or WinDSX-SQL software on the
rights. PC that is to perform the Service duties. If this is the
2. Make sure Comm Server is fully operational, Comm Server configure Comm Server to be a Service
communicating with controllers and with Client before creating the DataBase Service.
Workstations before configuring it to be a Service. 3. Make sure the DB/DBSQL program is fully
Close the DataBase and Workstation Programs. operational and able to make database changes
3. Copy the [Link], [Link], and before configuring it to be a Service.
CS as a [Link] programs from the Utilities 4. Create an API password profile that can view a
folder on the distribution CD and paste them into Location and an Image Source. Create an Operator
the WinDSX directory where the software was Login and assign it the API profile along with a 6-15
installed on the Comm Server PC. alphanumeric and keyboard character password.
4. Right click on "CS as a [Link]" and select "Run 5. Copy the [Link], [Link], and
as Administrator". Select “This PC should do daily [Link] programs from the Utilities
operations” unless you are setting another folder on the distribution media and paste them into
workstation to perform DailyOps. the WinDSX directory where the software was just
5. Click on "Create Registry Values". Click on "OK". installed on this PC.
6. In Windows go to Services and verify that the 6. Right Click and select Run as Administrator on
DSXComm Service appears in the list of Services. [Link]. Enter the DSX Operator
7. Right click on DSXComm and select properties. Name and Operator Password for the DataBase
Change the “Startup Type” to: Automatic (Delayed Service to use for DSX program access and
Start). Go to the Log on Tab and change the “Log- permissions. This must be a Password stored in
On As” to a valid account that has the appropriate WinDSX.
privileges for your system. Click OK to save. Close 7. Click on the “Create Registry Values” button. When
Services. this button changes to Done, Click on OK to close.
8. If you are going to use a shared directory on some 8. Go to Start/Windows Admin Tools/Services and
other PC, you will have to enter the Database Path verify that the DSXDBAS service was added. It
using UNC. You cannot use a shared drive letter to should appear in the list of Services.
refer to the Database Path. This can be 9. Right click on DSXDBAS and select properties.
\\servername\windsx or \\[Link]\windsx Change the “Startup Type” to: Automatic (Delayed
9. Start the DataBase and Workstation programs. Start). Go to the Log on Tab and change the “Log
Workstation should show "Comm Loss" in Red in the On As” to a valid account that has the appropriate
bottom right corner. This is correct. privileges for your system. Click OK to save the
10. Start the DSXComm Service. Within seconds the changes. This could be the same service account
Workstation program should show "Primary OnLine" assigned to the DSXComm Service. Close Services.
in Green in the bottom right corner. 10. Place API import files in the Shared WinDSX\API
folder or in the Local WinDSX\API folder on the PC
where DataBase runs as a Service. DataBase must
be run as a Service to process API import files. Start
the DSXDBAS Service.

DSX Access Systems, Inc. 214-553-6140 [Link] (10/2023)