

Only the VPX was being affected of the packet loss! We started some ping requets and found out something interesting: At least round robin and the users can login into the store 🙂

To get back users on the XenDesktop Site as soon as possible, we changed the StoreFront DNS A-Record to SF01,SF02 directly. (The load balanced services havent been accessible most of the time) Sometimes the secondary note switched to the primary node and backover. StoreFront and DNS Monitors went online/offline every few minutes. Two weeks ago one of my customers had huge problems with their internal load-balancing NetScaler.
