SC Server/Client Installation for Workgroup
The following are the additional steps required to set a client server system in Security Commander.
1 Install server
2 Add windows operators to Alliance Admin & AllianceGroup
Check secure is also a member of these groups and a member of the Administrators Group (This is based on Pre-Security Commander 2.0 install and may not apply to post 2.0 builds)
3 DCOM Permissions for the server
In Start ->Run type dcomcnfg
Go to Component Services->Computers->My Computer
Right click my Computer and go to properties then the COM Security tab
You need to set the permissions in edit limits and edit defaults for Access Permissions and for Launch and Activation Permissions for secure and SYSTEM to allow remote launch and remote activation
5 Install client
License client to server
6 DCOM Permissions for the client
Repeat steps 2 & 3 on the client machine(s)
Security commander currently uses NTLMv1 server authentication, this needs to be enabled as below.
To edit the group policy:
1. In Search programs and files, type “gpedit.msc”, and then press Enter to run the Group Policy editor.
2. Click the + boxes to navigate to Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options.
3. In the right-hand pane, ensure that LAN manager authentication level is set to any that does not "Refuse LM".
4. Exit from the Group Policy editor.
File sharing needs to be enabled on the client and server for the following folders in C:\Program Files\UTC Fire & Security\Security Commander
Configure or create the following items:
Ensure File and Printer Sharing is on.
Assign security and sharing privileges to the Windows 7 user account to allow access to the shared folder.
Ensure that the Windows user has been allowed access to the shared folders.
Ensure you can ping the host-name of the client from the server and vice versa.
If not enable the following services on both the server and client then retry connection in Security Commander