This message was deleted.

So you want the external beacon gone correct?

Yes do rather, or just to disable the probe process via reg key or something on the VDI's. the store they connect too is set to internal only but networks are telling me receiver is still probing

are you doing single fqdn?

Yes that a important question. You said no VDI used outside the network? So the clients machines say in the corporate lan? Depending on the answer will let me k ow what to say accurately next.

nope no single fqdn, when I meant VDI wont be used outside I meant that receiver is installed on the VDI's with accounts configured for the local lb storefront instances. its the receiver on the VDI's themselves that are generating the beacon traffic but the VDI's with receiver on will never be outside the network so theres no real need for them to do that. Clients can roam internally and externally however majority of clients use a browser to initiate a session so beacons not used too much for BYOD clients. It would be nice if you could set beacons per-store or disable the beacon probing from the receiver side with a reg key or similiar.

Ok then update the beacon for extern to point to the intern vip DNS is using.

check the provisioning file and see where it's pointing people, that's where it gets the beacon from.

True, but if he is using one store, wouldnt it come back?

looks like different stores for internal and external from the first comment

Looks like he is. Looks like this is what he is doing 1. Desktop(receiver)> storefront URL> internal beacon> VDI desktop 2. VDI(receiver)> storefront URL> internal beacon> apps Something with DNS and beacon not correct. It should never hit "external beacon" inside the double hop. IMO.

Thanks for the replies, I'm not quite sure that I'm outlining the issue properly. So beacons are configured correctly DNS is working ok. This issue is that VDI's with receiver/workspace installed in them is doing beacon probing at all. Because we have SSO enabled and stores configured within the VDI's to launch xenapp resources from inside a VDI instance I know why its doing it, but the process is unnecessary within a VDI itself. From what I can see receiver is pinging/contacting all 3 configured beacons at the same time so its not doing something sensible like probing the internal URL's and if getting no response then probing the external URL's. So if we have the external beacons set to ping.citrix.com and google.com for example the networks team are complaining that receiver is probing those resource at all. What I would like to do is disable beacon probing entirely in receiver or getting receiver to assume its always inside the network on the VDI's. As beacon probing is set at a storefront server level and not per store I cannot create dummy enteries there as the same storefront instances are utilised for external connectivity and internal load balancing I'll probably just end up changing the hostfile on the VDI's to stop them hitting those locations but if there was a reg key solution or somthing that would have been handy.