Citrix XenApp 6 farm



  • Anyone have specifics on adding a 2008 R2 server to a 4 node 2008 server farm running Citrix 6?

    The goal is to present IE11 natively instead of through an RDP session as currently configured.



  • @kyle do you mean you will publish the application to the desktop?



  • It is usually done when you install Xenapp on the server itself. You join it to the server farm then.


  • Service Provider

    @penguinwrangler said in Citrix XenApp 6 farm:

    @kyle do you mean you will publish the application to the desktop?

    It'll still use RDP.



  • @scottalanmiller said in Citrix XenApp 6 farm:

    @penguinwrangler said in Citrix XenApp 6 farm:

    @kyle do you mean you will publish the application to the desktop?

    It'll still use RDP.

    Yes, I just wanted to caution that some users will be confused because they will try to upload something to a website but can't find documents on their "Desktop" because IE isn't really running on their desktop. That is why we publish a whole desktop instead of just apps.



  • @penguinwrangler said in Citrix XenApp 6 farm:

    @kyle do you mean you will publish the application to the desktop?

    We currently have 4 2008 servers running XenApp 6. IE 11 doesn't support IE11 but 2008 R2 does.

    I was looking at adding a 2008 R2 node to the 4 2008 servers and wondered if there is any issues or beat practices to mixing 2008 & 2008 R2 in a clustered XenApp farm to publish a newer app only supported on 1 server.



  • @kyle said in Citrix XenApp 6 farm:

    @penguinwrangler said in Citrix XenApp 6 farm:

    @kyle do you mean you will publish the application to the desktop?

    We currently have 4 2008 servers running XenApp 6. IE 11 doesn't support IE11 but 2008 R2 does.

    I was looking at adding a 2008 R2 node to the 4 2008 servers and wondered if there is any issues or beat practices to mixing 2008 & 2008 R2 in a clustered XenApp farm to publish a newer app only supported on 1 server.

    I can't testify to that as all of our servers in our farm are 2008 R2, we are looking at putting some 2016 in there soon to "play" with for ourselves to see how it is, and to do up some user documentation before we throw them on 2016.



  • @penguinwrangler said in Citrix XenApp 6 farm:

    @kyle said in Citrix XenApp 6 farm:

    @penguinwrangler said in Citrix XenApp 6 farm:

    @kyle do you mean you will publish the application to the desktop?

    We currently have 4 2008 servers running XenApp 6. IE 11 doesn't support IE11 but 2008 R2 does.

    I was looking at adding a 2008 R2 node to the 4 2008 servers and wondered if there is any issues or beat practices to mixing 2008 & 2008 R2 in a clustered XenApp farm to publish a newer app only supported on 1 server.

    I can't testify to that as all of our servers in our farm are 2008 R2, we are looking at putting some 2016 in there soon to "play" with for ourselves to see how it is, and to do up some user documentation before we throw them on 2016.

    On XenApp 6?



  • @kyle said in Citrix XenApp 6 farm:

    @penguinwrangler said in Citrix XenApp 6 farm:

    @kyle do you mean you will publish the application to the desktop?

    We currently have 4 2008 servers running XenApp 6. IE 11 doesn't support IE11 but 2008 R2 does.

    I was looking at adding a 2008 R2 node to the 4 2008 servers and wondered if there is any issues or beat practices to mixing 2008 & 2008 R2 in a clustered XenApp farm to publish a newer app only supported on 1 server.

    I remember, and this is a long time ago, issues with adding an R2 server to a 2008 RDSH farm and having temporary profile issues. It was common to see someone add an 2008 R2 RDHS server to a 2012 RDSH to provide IE11 support. I think the connection broker needs an update.

    2016 RDSH is a big change. I have been testing Citrix vs 2016 RDSH and for full desktop Citrix doesnt add anything more than I have found with cheaper add-on products. I realize you are probably serving apps up though.

    But I would google about temp profile issues before doing what you are doing. And again, not sure that would affect your XenApp situation.



  • @bigbear said in Citrix XenApp 6 farm:

    @kyle said in Citrix XenApp 6 farm:

    @penguinwrangler said in Citrix XenApp 6 farm:

    @kyle do you mean you will publish the application to the desktop?

    We currently have 4 2008 servers running XenApp 6. IE 11 doesn't support IE11 but 2008 R2 does.

    I was looking at adding a 2008 R2 node to the 4 2008 servers and wondered if there is any issues or beat practices to mixing 2008 & 2008 R2 in a clustered XenApp farm to publish a newer app only supported on 1 server.

    I remember, and this is a long time ago, issues with adding an R2 server to a 2008 RDSH farm and having temporary profile issues. It was common to see someone add an 2008 R2 RDHS server to a 2012 RDSH to provide IE11 support. I think the connection broker needs an update.

    2016 RDSH is a big change. I have been testing Citrix vs 2016 RDSH and for full desktop Citrix doesnt add anything more than I have found with cheaper add-on products. I realize you are probably serving apps up though.

    But I would google about temp profile issues before doing what you are doing. And again, not sure that would affect your XenApp situation.

    This is litteraly a temp fix as prior to my joining the team they're moving away from Citrix to RDS.

    The problem with the workaround that's in place is is It a thin client to connect to Citrix and launch IE11 tthrough a RDP into another server running IE11 which prevents the user from performing some tasks.