When deploying DAS, we recommend that you read and follow the best practices listed here:
Develop specific use case scenarios with the users on multi-user workstations.
If you are currently using network login scripts, analyze them to determine the steps that can be streamlined or determine specific actions such as mapping the drives that can be accounted.
Prepare an inventory of all the applications and their versions on the workstation.
Determine if there are any security policies or other technical aspects that might affect the deployment.
Make a note of the processes running in the task manager when a user is logged in to the network. This helps to determine whether there are any applications that must be auto-launched or excluded during a logout event.
If a use case requires applications to be shut down as part of user logout or a time-out event, access each applicationcarefully to ensure that Desktop Automation Service does not have any adverse effect in the application sessions. For example, terminal emulator sessions or unsaved logout (graceful logout).
Analyze each application to determine the best way to handle a fast shutdown.
When updating actions.xml files, if you want to activate the latest changes without rebooting the workstation, issue a command to the workstation to ARS.exe to reload the actions.xml: "C:\Program Files\Novell\SecureLogin\Desktop Automation Services\ars.exe" /refresh