This message was deleted.

if you look in the registry you can see. this is from memory, but it's like HKLM\Software\Citrix\VirtualDesktopAgent\State you should see a number of entries that show if it is registered, when it registered, and which DDC it is registered to.

It is not about which DDC it is registered to. If I have 10 DDCs, When user clicks on the app, I'd like to track which DDC is that connection going to, which VDA etc.. if possible which SF server provided ica file.

hmm. most of that information should be available using Director. I'm sure someone with more knowledge about this could tell you where to find it. For the SF you could modify the front end to display the name of the storefront machine somewhere on the page.

After connection is made the SF server is in Director, but since you are troubleshooting a connection issue most likely, you need to know before the user clicks the link. I have an HTTP response header configured in my SF servers that can be seen in the Developer tools of the browsers when looking at the network tab. Each server is identified by a number that really only means something to me. Doesn't really help with the DDC side of things, but often the SF logs will point at a DDC, if not, I only have 3 DDCs to look at for any specific issue.

Reason why I ask is, we got an issue where user clicks on the app, and it throws cannot start the application error. I had to open all 4 ddcs event viewers, all 4 sf event viewers and vda server’s event viewers and refresh all of them to see which which servers are serving the connection. Wanted to know If there a simplified way for this?

Set up event log forwarding, forward all the logs to another server and then run something like @Guy Leech’s event log aggregator script. https://github.com/guyrleech/Microsoft/blob/master/event%20aggregator.ps1

That's a good script, but in this case, it would be killing the disease by killing the patient. 🙂 I wanted to know from Citrix end if there is a way to figure out which citrix infra components are brokering the session.

Not easily, you can see in Studio which VDAs are using which DDCs for brokering but that’s about it