Within Windows* every process that runs is run in a user context.  The context is used by Windows to determine the permissions.  These permissions include items such as access to a network share, access to the registry, permission to install software, etc. 

Task Manager can be used to determine the context of a process. In Task Manager there is a column 'user name'.

SDCLIENT.EXE is a client piece of LANDesk Software that is used in Software Distribution and OSD.   As with all Windows processes, SDCLIENT.EXE must have permission to install software and access network drives.By default SDCLIENT.EXE will run as local system. 

Troubleshooting SDCLIENT.EXE permissions requires that we start a job in the same context that SDCLIENT.EXE runs under.  Testing as the logged-in user is not a valid test.  This is because the behavior, when testing as the logged-in user, won't necessarily be the same as when run under the service account or local system.   The valid ways of testing access rights involving SDCLIENT.EXE is to also run the test under the Local System account.  Open an interactive command prompt that runs as Local System.  The following steps will open an interactive command prompt.

1. Open a command prompt  > CMD

2. Run the 'at' command with the following  syntax:   "at hh:mm /interactive cmd "

3. At the time in the command a new command prompt window will open.  This window is running as local system.

4. In the new command window test the permissions. Example: "net use *
server\share"

hh:mm = is the time in 24 hour time at which you want the new DOS box to open.

Now in the new Command Prompt window, permissions can be tested in the same context as SDCLIENT.EXE.

Note:  Also changing the account under which LANDesk Management Agent service runs to an administrator account.  If changing the account resolves issues then Local System does not have permissions to accomplish the task.