Jump to content
Welcome to our new Citrix community!
  • 1

Linux vda 19.9 installation breaks domain connectivity


Bernd Ziegler1709157774

Question

Hello together,

 

we have a n unattended provisioning for our linux clients with automatic domain integration via sssd. When I follow the installation steps of the Linux VDA, the script always trys to join the domain although the client was already successfully joined. Additionally the existing sssd and kerberos config ist also been changed. Is there a customized install script to avoid problems? I The older versions of the install scripts (in prvious VDA versions) were able to detect the existing domain join.

 

best regards

 

Bernd

 

 

Link to comment

2 answers to this question

Recommended Posts

  • 1

Hi jigaoh,

 

thank you for your reply. I am now a step forward to the goal. But I have problems with the VDA registration. I followed the hints in the Trouble Shooting Guide (https://www.citrix.com/blogs/2015/10/21/troubleshooting-linux-vda-registration-issues/), but this dis not the trick.

 

I get the fowwing message in the VDA log (xendesktopvda_19.9.0.3-1.ubuntu18.04_amd64):

 


[2019/10/23 13:04:23.2724969] [BrokerAgentAoTracing] [Information] BROKER AGENT -> HDX STACK Enumerate Sessions Request: Transaction unique ID: 12a29c30-1093-466b-b9fb-15c366dfefd3, VDA IP: 127.0.1.1
[2019/10/23 13:04:23.2725242] [BrokerAgent] [Information] VdaMetaData.SessionMetaDataAuditMethod - Waking up...
[2019/10/23 13:04:40.0284785] [BrokerAgent] [Information] FindThisComputerSid: found as
[2019/10/23 13:04:40.0286529] [BrokerAgent] [Information] CompterSid: Failed to obtain
[2019/10/23 13:04:40.0286891] [BrokerAgentAoTracing] [Error] Get ComputerSID Failed: System.NullReferenceException
[2019/10/23 13:04:40.0287212] [BrokerAgent] [Information] RegistrationManager.WaitUntilComputerSidIsObtained: Failed to obtain Computer SID from AD; attempts: 49
[2019/10/23 13:04:40.5297952] [BrokerAgent] [Information] nonDomainJoinedMode = False
[2019/10/23 13:04:40.5341621] [BrokerAgent] [Information] LdapProxy: Send Ldap search request to Ldap proxy service.
[2019/10/23 13:05:41.6249427] [BrokerAgent] [Information] FindThisComputerSid: found as
[2019/10/23 13:05:41.6251170] [BrokerAgent] [Information] CompterSid: Failed to obtain
[2019/10/23 13:05:41.6251562] [BrokerAgentAoTracing] [Error] Get ComputerSID Failed: System.NullReferenceException
[2019/10/23 13:05:41.6251874] [BrokerAgent] [Information] RegistrationManager.WaitUntilComputerSidIsObtained: Failed to obtain Computer SID from AD; attempts: 50
[2019/10/23 13:05:42.1260410] [BrokerAgent] [Information] nonDomainJoinedMode = False
[2019/10/23 13:05:42.1304389] [BrokerAgent] [Information] LdapProxy: Send Ldap search request to Ldap proxy service.


NDS and LDAP was setup correctly and therefore I don't where to look to find the  root cause. By the way the VDA resides in a different dns domain  like the DDCs.

Hope you have also some hints for me.

 

Sorry for my questions, but I am comming from the windows world and must now take also care on Linux VDAs.

 

best regards

 

Bernd

 

  • Like 1
Link to comment
  • 0
On 10/21/2019 at 8:56 PM, Bernd Ziegler1709157774 said:

Hello together,

 

we have a n unattended provisioning for our linux clients with automatic domain integration via sssd. When I follow the installation steps of the Linux VDA, the script always trys to join the domain although the client was already successfully joined. Additionally the existing sssd and kerberos config ist also been changed. Is there a customized install script to avoid problems? I The older versions of the install scripts (in prvious VDA versions) were able to detect the existing domain join.

 

best regards

 

Bernd

 

 

Which script did you use to do the installation? Is it ctxinstall.sh? The older versions of ctxinstall.sh also weren't able to detect the existing domain join.  If you do the installation manually, and configured it with ctxsetup.sh, it won't try to join the domain again and change the existing sssd and kerberos config.

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...