Last week I upgraded our production XenMobile environment to version 8.7, after which I wanted to enroll a Windows 8.1 RT. Unfortunately there is no Worx Home application in the Windows Store, nor does Citrix offer a WorxMail of WorxWeb client. The Windows 8.1 enroll process is slightly different than a iOS of Android device and can be found in the eDocs. Ok, let’s enroll a Windows 8.1 RT and let us see what we can do with it.

Click “Settings”                                                               Click “Change PC Settings”

XD87-016    XD87-017

Read More →

Lately, more and more customers are asking for a solution to manage their mobile devices. While discussing the Citrix XenMobile architecture question regarding High Availability (HA) and Load balancing (LB) are crucial for a solid design. How to configure the Citrix AppController for HA & LB is pretty straightforward and well documented. The Citrix Device Manager however is a different ball game and the documentation isn’t very clear. A full architecture with High Availability should look something like this:

Image

The eDocs states:

Configure the Windows servers as a cluster, while the installation instructions tell you to configure a Tomcat cluster

The Citrix Reference Architecture for XenMobile 8.7 doesn’t mentions a Windows Cluster.

can be configured with multiple servers load-balanced behind a NetScaler appliance or another hardware load-balancing solution. The Device Managers work in an active-active configuration. In this environment, ports 80, 443, and 8443 are load-balanced. For SSL connections (ports 443 and 8443), make sure to turn on SSL session persistence in the load balancing rules. XDM requires a shared SQL server and NTP configured on each server.

At first I was a bit confused about all the different parts of information, what information is correct and what information is not? I contacted Citrix hoping to get a straightforward answer. Citrix came up with the following high level guidelines:

  1. Install for example two standalone XDM server (No MS Clustering)
  2. Place a network load balancer in front of the XDM server. In my case this will be a Netscaler (NS).
  3. Install/Configure the first XDM server and LB on the NS with only one XDM server active
  4. Test if the setup works as a expected
  5. Install/Configure the second XDM server and cluster (Yes, a Tomcat cluster) the two XDM servers as described in the installation guide (forget the part about the MS clustering).
  6. Configure the NS LB to support both XDM servers (Don’t forget session persistence)
  7. Retest if the setup still works as expected

Following this guidelines I was able create a fully working load balanced configuration for the XDM servers. For information about scaling a XenMobile environment take a look at this Citrix Blog!

During a XenMobile training last  month I got a error message while logging on to the XenMobile 8.6 Device Manager Console. Didn’t pay much attention to it then, because i assumed something went wrong during the install of Citrix XenMobile Device Manager, a simple reinstall of XDM resolved the error message. Prior to upgrading an existing XenMobile 8.6 production environment to 8.7 I got the same error message again “Cannot load labels files”

XD87-022

 

Read More →

Recently Citrix released XenMobile 8.7 which includes updates and enhancements to the following components: App Controller, Device Manager, WorxHome, and WorxMail. The complete overview can be found in Citrix eDocs. In addition to the support of the Dutch language in WorxHome & WorxMail we have several users equipped with a Windows 8.1 RT tab, which couldn’t be managed by the previous version 8.6. We decided to be a early adaptor and upgrade our existing environment! The recommended upgrade order for the several components is:

  1. Netscaler (NS)
  2. XenMobile Device Manager (XDM)
  3. XenMobile Netscaler Connector (XNC)
  4. XenMobile AppController (XAC)
  5. MDX Toolkit to wrap .ipa & .apk files (WorxMail/WorxWeb)

This article will only cover upgrading XenMobile Device Manager 8.7 & XenMobile AppController 2.10.

Read More →

Recently one of our customers migrated from an environment with several print queue’s to a centralized solution using ‘follow me printing’. Over time several users started complaining that their print jobs were not being displayed when the logged on to the printer.Instead other print jobs were visible. The problem was very inconsistent and difficult to reproduce.

In the knowledgebase of Microsoft we found an article what seemed to be our problem:

Http://support.microsoft.com/kb/958741

Unfortunately we were already running Windows 2008 R2, in which the problem should have been solved.

Read More →

This morning I was confronted with an email from the service desk because the Wi-Fi BYOD network authentication had been changed. All existing accounts were removed and BYOD users had to apply for a new user account.  I created a new user account and tried connecting to the existing WiFi BYOD network. Windows 8 detected my old username/password were not valided and requested the new password. Unfortunattely not only my password, but also my username had been changed.

BYOD

For some reason it’s not possible to delete the username of WiFI Profile from within the GUI in Windows 8 anymore. Luckily  there are several other alternatives to delete or manage an existing WiFi profile. Read More →

In the process of upgrading an old Citrix PVS 5.6 Farm I did a fresh installation of Citrix Provisioning Server 6.1 ( CPVS61016v2) on Windows 2008 R2.  First I wanted to add some existing vDisks, which were located on the local PVS store. Unfortunately I was unable to add an existing vDisks, according to the PVS Console no new disk where found.

1

After I had checked that the vDisk files (.vdk/.pvp) were actually present I decided to validate the path for my store.

2

The validation tool stated a IPC error. The Citrix KB contains an article which sounded familiar “CTX134158 IPC Error when Validating Paths for Store on Provisioning Services Server”. This problem would have been solved with update CPVS61E003, the only problem was I’m running update CPVS61016v2

Read More →

Today I finally received a new laptop (HP Elitebook 8760W) which is on the Citrix XenClient HCL. Due to a ‘small’ primary SSD disk (160GB) I exchanged the cd-rom device for a additional harddisk, to store additional virtual machines. Without the cd-rom drive I had to install Citrix XenClient 2.1 with a bootable USB Key. Creating a bootable USB Key was pretty straight forward:

  • Download Universal USB Installer
  • Download Citrix XenClient 2.1 ISO
  • Start Universal USB Installer
    • Step 1: Try Unlisted Linux ISO (New Syslinux)
    • Step 2: Select the XenClient ISO
    • Step 3: Select your USB Key
    • Step 4: Select Format Drive
    • Step 5: Hit Create !

Read More →

After analyzing the release notes of RES WM 2011 SR2/SR3, we decided to upgrade our customer site from RES WM SR1. As usual the upgrade went very smooth and seemed like a walk in the park.

A couple of days after the upgrade to SR3 we suddenly received a lot of support calls regarding blocked applications. We noticed that the AppGuard log was full of processes being blocked. This was quite strange because no new applications were deployed in the last couple of weeks.

Prior to SR2 the authorized process name field could only contain 15 characters. A long filename like “LongProcessName.exe” was registered as “LongProcessName”. No options were available to change this.

Read More →

Met RES WM is het mogelijk om netwerk printers te koppelen binnen de gebruikerssessie. Op deze manier kan een beheerder vooraf precies instellen welke printers een gebruiker toegewezen krijgt binnen zijn of haar sessie, afhankelijk van authorisatie of groepslidmaatschap.

Het toewijzen van een printer kan op verschillende manieren worden gedaan, bijvoorbeeld aan de hand van een AD Groepslidmaatschap, Powerzone, Clientnaam of Workspace.Wij maken in veel gevallen gebruik van een AD Groepslidmaatschap, zodat het toekennen van printers door authoristiebeheer in de AD kan worden uitgevoerd en hiervoor geen mutaties in de RES WM configuratie behoeven te worden gemaakt.

Buiten deze statische printers (toegekend op basis van een groepslidmaatschap) is het voor zwervende gebruikers ook handig als men in ieder geval één printer krijgt op de locatie waar men op dat moment werkzaam is. Hiervoor maken we gebruik van Powerzones, waarbij we bijvoorbeeld een client VLAN kunnen gebruiken voor het koppelen van printers.

Read More →