I’m sure many who have had to deploy XenApp servers in the past have had to configure policies that customize XenApp server’s internet explorer browser. Whether it’s to lockdown the controls or simply for cosmetics
As with one of my previous posts: Notes on Citrix XenApp 6.5 PowerShell cmdlets https://blog.terenceluk.com/2012/02/notes-on-citrix-xenapp-65-powershell.html … I’ve been trying to keep track of the cmdlets I’ve been using to make my life a bit easier
I’ve been asked a few times by a few ex-colleagues why they can’t seem to find the option for the amount of Machines to be powered on in Citrix XenDesktop 5.5’s Edit Desktop Group menu
To follow up with my previous post: Configuring Citrix NetScaler VPX (1000) 9.3 for publishing Web Interface server access by authenticating against Active Directory One item I forgot to include was how to redirect http
I don’t usually configure NetScaler VPX appliances as this was always left for the networking team when I still lived and worked in Canada. Bermuda, on the other hand, sometimes tend to blur the lines
Problem You would like to direct the INSTALL link that is presented by your Web Interface 5.4 server when a Citrix client isn’t detected directly to a link that downloads a specific client. Solution Note
This didn’t take me too long to figure out but I noticed that a lot of the hits on Google brings you to Web Interface version 4.x Citrix KBs so I figure writing this post
Problem You’ve completed the configuration of your Citrix NetScaler VPX 9.3 as an Access Gateway to your internal Web Interface servers but when you attempt log in: … the web interface login splash page flashes
Problem You’ve completed the configuration of your Citrix NetScaler VPX 9.3 as an Access Gateway to your internal Web Interface servers but when you attempt log in: … you receive the following error: The website
Problem You’re attempting to change the vCenter server instance that your XenDesktop 5.5’s DDC uses via “Change Host Details” in Desktop studio but after entering the new Address for vCenter: … you receive the error:
