search cancel

Profile failed verification due to error (12) login failed, failed to access xendesktop with given credentials, Error code: 401

book

Article ID: 112570

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction



Profile failed verification due to error (12) login failed, failed to access sendesktop with given credentials, Error code: 401

Environment

Release:
Component: UIMXDK

Resolution

The following should be reviewed to verify the connection:

- Is the probe installed local to the xendesktop environment?

If yes make sure that there is a key called localhost and is set to true in the Raw Configure interface > Resources section.  

- Is the probe installed in the same domain as the xendesktop environment?

If not it must be. 

- Is the realm in the krb5.conf correct, and is it all in uppercase?

Perform the following to get the values for updating the template file:

echo %userdnsdomain% 
echo %LOGONSERVER% 

Also the realm must be entered in all caps.

- Make sure the nimsoft robot watcher service on the probe machine been configured to use the same account that is being used in the profile.

- Make sure that the user that you are using is part of the Administrators and Performance Log Users groups on the xendesktop machine.

- Make sure that the user has been added a Read Only Administrator in Citrix Studio.

- Validate the winrm configuration (example):

winrm identify -r:http://winrm_server:5985 -auth:kerberos -u:user_name -p:password -encoding:utf-8

- Make sure that "Get-ExecutionPolicy" in PowerShell returns "RemoteSigned".

- Make sure that "winrm get winrm/config/service" shows "AllowUnencrypted = true" and "Kerberos = true"

- Make sure that "winrm get winrm/config/client" shows the trusted host or *.

- Make sure that "winrm get winrm/config/winrs" shows "MaxMemoryPerShellMB = 1024"

- Make sure that "winrm e winrm/config/listener" shows the "Address = *" and the "Transport" is consistent with the connection method being used. 





 

Additional Information

If scripts are at a custom location it can be added via raw configure

After probe has been started, do the following

a. Open the adminconsle ui and navigate to the probe.

b. Edit the probe ‘Raw Config’ section of the probe

c. Select Setup section

d. Click on +(plus) button at top right corner to add a key

e. Add a new key as 'scriptExecPath' and value as desired path for scripts execution (Eg: ‘C:\Scripts’ for windows)

Note: Please make sure the specified directory exists before making the probe configuration changes.

f. Click on CREATE to save the key value pair

h. Click on UPDATE to update the probe configuration