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

Okay this is interesting. In my previous post , I said some candidates did not manage to get the answer correct. But for this question, they got all correct! they even mentioned how many hours rather than how many days. ( how they maange to calculate that fast? Did they have calculator in hand? ahh! smartphones!) Again, back to the real business. if it happens that the Citrix farm lost connectivity with Citrix license, users still be able to launch the Citrix published application. However, there is 30 days / 720 hours grace period. After this grace period, users won't be able to launch any Citrix published applications. Question... If my Citrix XenApp servers lost connections to DataStore, I can't reboot my Citrix XenApp servers. But what if the servers lost connections to Citrix License server? The answer is, no problem! it will not give any impact on the grace period or Citrix functionality within grace period. The information stored  in mps-wsxica_mps-wsxica.ini, thus

This is one of my favorite interview question, I just don't know why. it seems simple, but some candidates failed to give a proper answer (poor them). I wish all of them better luck next time. Okay, now back to the real business. From Citrix Administrators Point-of-View, losing a DB may cost chaos, depending on how severe the issue is. However, from user perspective, nothing is different. Users wont really impacted of this. They still be able to launch Citrix published applications and works as normal. Thanks to  Local Host Cache (LHC) , it eases the burden of Citrix Admins (oh really?) However, although all Citrix XenApp servers have LHC, there are some conditions that Citrix Admins need to remember : There is no grace period for this (MPS 3.0 and above). Users still be able to connect to the Citrix farm (lucky!) Only static information  available to users. No new info can be added and current info cannot be changed  (not really...) In any circumstances, DO NOT : Resta

This time, I want to discuss on an error occurred when users want to access Citrix Web Interface. This may happen for new farms or when new XML servers added to the farm.  Issues : Users received below error when accessing Citrix Web Interface : Troubleshooting  From Citrix Web Interface server, go to application log, and search for Event ID 31003 and Event ID 30110. Those Event IDs indicates that XML service transition failed. Event ID 31003 in Application Log Event ID 30110 in Application Log Check which server(s) is/are configured as XML Service servers for the farm, and RDP to the server(s).  Resolution : go to Start > run , type regedit and press Enter.  browse to  HKLM\Software\Citrix\IMA Add a new registry value (ensure it is DWORDS (32-bit) Value ) Set the name as  UseNetworkLogon Right-click at the newly created key, and click Modify... Change the value data to 1 . Ensure the base is Hexadecimal.

Some people are having difficulties to differentiate between Universal, Global and Domain Local groups (including me, sometimes).  The table below illustrates the differences between those group scopes. Some lesson learnt :- Global groups can be added to Domain Local groups (from the same domain or crossed-domain), but not vice versa For Global groups, you only can add accounts from its domain and its parent Global groups In order to add accounts from any domain, you need to have Local Domain groups, Global groups won’t allow you to do so. Converting a group to Domain Local, add those crossed-domain users, and convert it back to Global group won’t do the trick. Domain Local groups cannot be added to Domain Local groups from any domain except for its domain and the parent. Group scope Group can include as members… Group can be assigned permissions in… Group scope can be converted to… Universal ·       Accounts from any domain within t

Citrix XTE Server service is one of the essential service in Citrix XenApp. it is directly relates to Session Reliability. What is Session Reliability? Please read from here and here . Is Session Reliability Goood? Hmm, read this article and go figure it out. ( such a lazy bum of me, huh? ) It might occurred in your environment that XTE Server service can't be started at one server, while the rest are fine. Session Reliability option is enabled from Citrix Console.  So, what's next?   Issues : You may received below error when you want to start XTE Server service.   Troubleshooting  browse to  %programfiles%\Citrix\XTE\Conf , check whether file httpd.conf is existed / is there any content inside the file. Resolution : Copy the file from server that is working fine. 

Users reports that they are not able to perform printing. Services are up and running, but issue still persist, although after you restarted those Printer Spooler and Citrix Print Management services.  In addition, required Service IDs are properly configured. Users reboot their workstations, but to no avail. So, what is next? Issues : Users may received one or more errors regards to printing. Below are some of the error examples :  - or -  Meanwhile from server perspective, no printers listed in  Printer and Faxes Upon checking the services, both  Printer Spooler  and  Citrix Print Management  services are started. Issue remains although those services restarted. Required Service ID ( ctx_cpsvcuser ) is in place. Troubleshooting  Press Start , hover to Administrative Tools , click at Terminal Service Configuration . Or, press Start , choose run type tscc.msc , and press enter. Right click at ICA-tcp listener, and choose Properties

After installing Terminal Services Role to a server, you may want to specify the license server. The Terminal Server will make an attempt to locate the Terminal Service License servers first, before make an attempt to follow automatic license server discovery process. You may see below balloon : Note that this is for Windows Server 2008. For Windows Server 2003, 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 : Go to Start > Administrative Tools > Terminal Services > Terminal Services Configuration . Or you can type tscc.msc in  Run box. Right click at License server discovery mode , and click at Properties .

As mentioned in previous post ,  ctx_cpsvcuser can be created and configured with a tool, but it is limited to certain Citrix XenApp versions only : Feature Pack 1 for Presentation Server 4.5 Presentation Server 4.5 for Windows Server 2003 Presentation Server 4.5 for Windows Server 2003 x64 Edition XenApp 5.0 for Windows Server 2003 x64 XenApp 5.0 for Windows Server 2003 x86 Description : Using tool to create Service ID  ctx_cpsvcuser  in Citrix XenApp servers. How To Do : Download the re-creation tool here . Upload the files to Citrix server. Run command prompt, browse to the uploaded folder, and run below command. 32-bit :  CtxCpsvc10.exe –install  | 64-bit :  CtxCpsvc10_x64.exe –install once done, double check the Citrix Print Management service. Ensure it can be started and set to Automatic. Reference : http://support.citrix.com/article/CTX113554/