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.

Well, as a Citrix Admin, you are able to prevent any users from accessing your Citrix XenApp servers, especially when the server is under maintenance mode, or you purposely want to put the server out-of-loads. there are 2 ways to do this; GUI or command.  But bear in mind 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

Previous post  explained on how to configure Terminal Services License server for server 2008. For this time around I will show on how to configure  Terminal Services License server  for server 2003. Basically, it is more or less the same, just the interface is different. Note that this is for Windows Server 2003. For  Windows Server 2008, please go to here . Description : You want to specify Terminal Services License server, so Terminal Services role can be used by servers. How To Do :  RDP to the server, and go to Start > Administrative Tools > Terminal Services Configuration . Or, go to Start > Run, and type tscc.msc On the left pane, click at Server Settings option. At the right pane, right click at License Server Discovery Mode , and choose Properties .    From this screen, put the TS CAL server name, and press Check Names button.

In previous post  I wrote about what will happen if the Citrix XenApp farm lost connection with its datastore. Well, because of Local Host Cache , users will still be able to access the applications without too much issue. But, what is Local Host Cache (LHC)? LHC is like a mini-DB of the farm, and created on all Citrix XenApp servers. Why I said mini-DB? It is because it contains a portion (subset) of Data Store information.  There are 4 main information stored in the LHC : All servers in the farm, and their basic information. All applications published within the farm and their properties. All Windows network domain trust relationships within the farm. All information specific to itself. (Product code, SNMP settings, licensing information) There are 2 primary functions of LHC : Redundancy - a Citrix XenApp still function as normal if connection to datastore losts. Performance - LHC cache information used by ICA clients for enumeration and application resolution. By

Well, this issue was occurred to me last weekend, when I was busying myself changing my Citrix XenApp servers from farm A to farm B, using GUI. Why? because I have nothing to do (on weekend? seriously??). Please put my forever alone life aside, shall we? Well, this issue occurred to my XenApp 5 for Server 2008 farm. Hmm, Server 2008 is the keyword there... :) Issues : Citrix Admins received below screen after putting the credential for ODBC Driver Access. Citrix Admins can't move forward, as the GIU will froze just after putting the credential. Troubleshooting  Go to Start > Run , and type SecPol.msc   You will be prompted with all UAC permission, so just proceed accordingly Click at I want to complete this task Press Ctrl + Alt + End Press Continue After that, you will see this console. Our focus is on Security Settings > Local Policies > Security Options On the right column, find this configuration, and check the setting con