Client Automation - RC Session disable autologon

Document ID : KB000120692
Last Modified Date : 21/11/2018
Show Technical Document Details
Issue:
ForceAutoLogon is set to 1 on the machines

HKLM\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\ForceAutoLogon = 1

Sometimes after a RC session the parameter ForceAutoLogon is changed to 0 or -1

 
Environment:
CA Client Automation 14.0 SP2
Cause:
This problem could occur when :

- ForceAutoLogon has type REG_DWORD (and not REG_SZ)
 
User-added image

Windows accepts both type for this setting.

or

- There is a problem at beginning of RC session when rchost tries to validate credentials to rcserver

Example :
"Unable to establish a remote control session: 
The Remote Control Management Server is not available to validate the credentials supplied." 


 
Resolution:

Open a case at CA Technical Support requesting the fix T5SD200 for Client Automation 14.0 SP2

 
Additional Information:
With this fix :

- If ForceAutoLogon is a REG_SZ with Value = 1, rchost correctly changes the value to 0 when RC connection starts and to 1 when RC connection ends.

- If ForceAutoLogon is a REG_SZ with Value = 0, rchost does not change the value when a RC connection starts and when RC connection ends.

- If ForceAutoLogon is a REG_DWORD with Value = 1, rchost correctly changes the value to 0 with type REG_SZ when RC connection starts and set it to 1 with type REG_SZ when RC connection ends.
The type is changed from REG_DWORD to REG_SZ but this does not cause any problems as Windows accepts both type.

- If ForceAutoLogon is a REG_DWORD with Value = 0, rchost does not change the value and type when a RC connection starts and changes it to REG_SZ with value 0 when RC connection ends.
The type is changed from REG_DWORD to REG_SZ but this does not cause any problems as Windows accepts both type.