In order to secure the access to SDLIBRARY$, its access can be set to a specific
userid that can be a local or domain userid making sure that its password never expires.
Also remove access to Everyone.
Configure SS via sd_ccmd addshare and libraryaccess.
CA Client Automation - All versions
When the Agent can not access the share SDLIBRARY$ on the Scalability Server it downloads the package from it using its internal file transfer.
You need to check if the SDLIBRARY$ share is active on the Scalability Server and if it has the right permissions for the Agent to access it. The shared directory is %SDROOT%\SD\LIBRARY.
If the share is not defined yet, use the following command to create it:
sd_sscmd addshare sdlibrary
In order to secure the access to SDLIBRARY$, its access can be set to a specific userid that can be a local or domain userid making sure that its password never expires. In order to secure the share it is also suggested that after add the specific user, access to other users including Everyone can be removed.
**Important: Make sure that the password of the user account being used to access the SDLIBRARY$ does not expire.
After set the settings on the share, you must instruct the Agents to use the defined user to access the share and this can be done using the following configuration policies that must be configured and deployed to the agent machines.
DSM > Software Delivery > Shared:
If only a user will be used for all Scalability Servers, they can be set to Centrally Managed. It also prevents manual changes on the Scalability Servers using the command sd_sscmd libraryaccess mentioned below.
If different users are needed on each Scalability Server, the following command can be used to set the credentials:
sd_sscmd libraryaccess {user=(Domain or Local\)User password=Password}
To remove the credentials the following command can be used:
sd_sscmd libraryaccess REMOVE