I received a request by my clients to enable pass-through to their Citrix Web Interface site. Not more than a few minutes after completion, they made a few complaints, saying that they needed to supply their credentials every time they launched published applications, which defeats the Single Sign-On (SSO) purposes. After a few minutes of troubleshooting, I realized that, in order to enable pass-through, there are more steps need to be taken, not simply enabling the feature. Description : Properly enabling Pass-Through, so users wot have to supply credentials every time they launched Citrix published applications, as below : How To Do :  Uninstall current installed Citrix Receiver Once un-installation completed, open command prompt, and type CMD  Browse to the installer location, and run command (  CitrixReceiver.exe /includeSSON )to install Receiver with SSON enabled Proceed with installation When you can see this in P

So a couple weeks ago I had been asked by my colleague to put some of my servers out of load for maintenance. Then I was like,  "okay, just disable logon  then!". Then, he made some weird face to me while saying "Fool, if you disable logon, how am I suppose to login, then? I don't want to trouble myself with console... go figure it out!".. aaaaaannd yes, I figured it out (or was I?? :D) Description : Put Citrix servers out of Citrix load (some sort of private mode / maintenance mode). How To Do : From the Citrix server (or from your local machine of you has it installed), launch XenApp Advanced Configuration Console . Right click at Load Evaluator , and click at New Load Evaluator .  You will see this screen. Put a name of your Load Evaluator (ie. Out of Loads), and at the Available Rules section, click at Scheduling .  Add Scheduling Rule (you will see it moved from left section to right.  Now, at every single day, press Remove Interv

This would be my first post regarding Server 2012 (pretty cool, huh?) So this is the case. I just created a lab environment for my XenDesktop 7. Because of this new classy environment, so I decided to use Server 2012. I have a server act as a DHCP, DNS and DC (have to, not enough resources), and another server as member server. So when I wanted to add this member server to my domain, I received error as in Issue section. Issues : Facing with this error while adding member server to domain. The following error occurred attempting to join the domain <domainName> : The specified domain either does not exist or could not be contacted. Troubleshooting  It turned out that my DNS server is not properly configured. It is not configured to any server, thus resulting member server cannot contact to any DNS server. Resolution : Configure the correct DNS server. Depending on your environment, you may want to set it manually at servers, or at Scope

I got this issue when I want to perform change farm on one of my Citrix XenApp farms. The installed version is Citrix XenApp 5 for Server 2008. I have not encountered any issue before while using Windows Server 2003, so I believe this issue is somehow related to the differences between those 2 Windows versions, well, particularly the UAC.  Issues : CHFARM utility failed in the middle, with below error : Troubleshooting   It is due to UAC permission, it blocks CHFARM utility from properly running because it ran in Admin Approval Mode. Resolution : Go to Start > run, and type secpol.msc    When you see this UAC permission control screen, choose I want to complete this action option, and press Ctrl + Alt + End as requested after that.  Press Continue   Browse to Security Options as below  Search for this option : User Account Control : Rul all administrators in Admin Approval Mode  Right click at the option, and choose Properties

After we talked on how to disable logon using command , this post will show on how to disable logon using Citrix Console. Note that :- Users are not able to remote to the server, no RDP, no ICA, nothing. Once logon disabled, users only able access the server via virtualization Console like VMware Client or XenCenter (Virtual server). For physical server, it is either physically sitting before the server, KVM or Remote Access Card (DRAC, or HP iLO) For Command Line , it only can be used locally. I haven't try using PSTOOL yet, but I will update this post whether I can access the server using PSTOOL after logon disabled. For GUI , as we will use Citrix Console, hence it can be done remotely from other Citrix XenApp servers, within the same farm. Hence, if the farm only has one Citrix XenApp server, then you need to get in the box via physically there or virtualization client. Description Disable / enable logon for Citrix XenApp servers via Command Line.