XenApp 6 duplicate server name error
I am currently designing and building a XenApp 6 farm upgrade for my organisation. They are moving from Citrix Presentation Server 4 to XenApp 6 in the new year.
Whilst designing the administration console for support staff I came across the following issue.
![](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgC0YJXh94gvJHgGUzLSc_F6K6shyphenhyphenimdQkDPKmhS0QnTcchiZKyz9ICcXx0yRdlXsQgpCsqxrWURYrlzemYZahR62sPpHLDD5WX01MXkHU60Z4INIZs6g1d_Q7GKVX7n6ylFEZRBMPGrc8/s320/error.png)
![](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhAalhqM_pN-W46chVmA_FqacDih-6GG9G8BuEFbeAD8pkK21aQd6g_gTyanAs_xw9PLR383CibjHoF7W7STFx1QP1GMiDYBlyetbAvEQf8LDQr9d1r5HKR6Yl6wFpyAXgYjgKUsNPvs_Q/s320/error+details.png)
![](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh3wsoUv_mDM0Scq8zUubrGAdnlHTSus__ME-o9Yk1Eoe6zi-Rz57UD1QSHbdDUVRyUFP4Stkb4cX9Vws8d_ZfoYOFy8jjRyR7lZGyNpqG44OQwfZMYt0eWoTSQB3GgvzEpcsehC5kAg1w/s320/fix.png)
Whilst designing the administration console for support staff I came across the following issue.
Issue
=========
=========
When specifying more than one server in the discovery list for custom administrators and error message appears with the following text.
![](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgC0YJXh94gvJHgGUzLSc_F6K6shyphenhyphenimdQkDPKmhS0QnTcchiZKyz9ICcXx0yRdlXsQgpCsqxrWURYrlzemYZahR62sPpHLDD5WX01MXkHU60Z4INIZs6g1d_Q7GKVX7n6ylFEZRBMPGrc8/s320/error.png)
"another discovered farm has the same name as the farm to which this server belongs. Connecting to different farms with the same name is not supported"
![](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhAalhqM_pN-W46chVmA_FqacDih-6GG9G8BuEFbeAD8pkK21aQd6g_gTyanAs_xw9PLR383CibjHoF7W7STFx1QP1GMiDYBlyetbAvEQf8LDQr9d1r5HKR6Yl6wFpyAXgYjgKUsNPvs_Q/s320/error+details.png)
Now, these servers are both in the same farm, but for some reason using a custom administrator it does not work.
Fix
====================
After looking through the custom permissions provided to these administrators I found that adding the following permission fixed the problem.
"View Server Information"
![](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh3wsoUv_mDM0Scq8zUubrGAdnlHTSus__ME-o9Yk1Eoe6zi-Rz57UD1QSHbdDUVRyUFP4Stkb4cX9Vws8d_ZfoYOFy8jjRyR7lZGyNpqG44OQwfZMYt0eWoTSQB3GgvzEpcsehC5kAg1w/s320/fix.png)
Make sure when applying this setting you click the button "copy to subfolders"
Once this has permission has been granted, subsequent discovery attempts will work correctly without errors.
Comments
Post a Comment