Citrix Cloud with AWS VDA Servers are going to unregistered mode
We are using Citrix cloud and managing only VDAs at AWS.
VDA version is 1906.
Everyday morning between 9am - 11am random VDAs are going to unregistered mode.
When I try to RDP, I can't reachable in network itself, even unable to ping.
Troubleshoot:
It requires a reboot to bring it to service and running normally for the rest of the day.
I suspect it is not OS issue as we have same image running across the estate without an issue.
We are receiving Event id 1002 - Citrix desktop service failed to register.
Please suggest .
VDA version is 1906.
Everyday morning between 9am - 11am random VDAs are going to unregistered mode.
When I try to RDP, I can't reachable in network itself, even unable to ping.
Troubleshoot:
It requires a reboot to bring it to service and running normally for the rest of the day.
I suspect it is not OS issue as we have same image running across the estate without an issue.
We are receiving Event id 1002 - Citrix desktop service failed to register.
Please suggest .
Also I would seriously look at updating the VDAs
ASKER
OK, that looks like a bit of an issue, being unable to contact the domain. This is on the VDA right? Doesn't look like port exhaustion (you'd expect to see thousands of connections in the wait status). Can you contact a domain controller OK when this occurs? Which domain controller is it trying to connect to (do you have one in your AWS VPC, or is it reaching back on-premises)?
ASKER
Yes, it is reaching Domain Controller in AWS itself. We can't try testing the domain from the VDA as it is going out of the network.
So, domain reachability can't be tested in this scenario.
So, domain reachability can't be tested in this scenario.
Can't be tested? I don't follow - the VDA, if it is in an AD domain, needs to be able to contact a domain controller to function. If it can't you will get an error. If it is becoming unreachable, and that coincides with an AD error indicating no domain connectivity - then I think that's pretty much a smoking gun.
Is your VDA in AWS as well as the domain controller? If so, are they in different VPCs?
Is your VDA in AWS as well as the domain controller? If so, are they in different VPCs?
ASKER
Can't be tested means,.. when it goes unregistered the VDA is out of the network, so how can I connect to VDA and ping DC. If it is in VMware , we can take console whereas in AWS, no console access.
Don't you have access to the cloud management console? You should be able to access it from there
ASKER
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-console.html
For MS Windows instances we can get the console screenshot only.
It is just a print screen of the instance and you will see Microsoft genie screen. It is not like VMware console.
It’s product limitation from AWS.
For MS Windows instances we can get the console screenshot only.
It is just a print screen of the instance and you will see Microsoft genie screen. It is not like VMware console.
It’s product limitation from AWS.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
We have VDAs in AWS and we frequently saw port exhaustion occurring as well. If possible, check the amount of open ports via netstat -anob