Distributing Freelance Security Lock user/password database (digimat.uid)
Hello everyone
I'm rolling out Freelance Security Lock in a Freelance v9.1 installation.
The configured users and passwords are saved locally in the digimat.uid file. To avoid changing passwords separately on every station, I'd like to distribute digimat.uid automatically.
I thought about using a batch file and Windows network shares, but the Security Lock manual says that it isn't possible to distribute the user database when Digivis is running. So I'd have to close Digivis, distribute the file and open it again -- correct?
Does anyone have a suggestion for automating this, are there any best practices?
Thanks and best regards
Björn
I'm rolling out Freelance Security Lock in a Freelance v9.1 installation.
The configured users and passwords are saved locally in the digimat.uid file. To avoid changing passwords separately on every station, I'd like to distribute digimat.uid automatically.
I thought about using a batch file and Windows network shares, but the Security Lock manual says that it isn't possible to distribute the user database when Digivis is running. So I'd have to close Digivis, distribute the file and open it again -- correct?
Does anyone have a suggestion for automating this, are there any best practices?
Thanks and best regards
Björn
Answers
Hello again
Well, contrary to the manual it seems to work, at least for password changes. I changed passwords on one station and distributed C:\WINDOWS\DIGIMAT.UID using CIFS network shares. The new passwords were in effect immediately. This also seems to work for ADMIN.PWD which contains the Security Lock administrative password.
I'm going to write a small batch script for this utilising robocopy, time permitting, which will be scheduled to run on a regular basis (probably daily). I'll update this question then.
Take care
Björn
Well, contrary to the manual it seems to work, at least for password changes. I changed passwords on one station and distributed C:\WINDOWS\DIGIMAT.UID using CIFS network shares. The new passwords were in effect immediately. This also seems to work for ADMIN.PWD which contains the Security Lock administrative password.
I'm going to write a small batch script for this utilising robocopy, time permitting, which will be scheduled to run on a regular basis (probably daily). I'll update this question then.
Take care
Björn
Add new comment