Citrix App Controller Devices tab shows no listed devices

Citrix App Controller enables publication and access control of many types of applications to mobile devices. Administrators can publish iOS & Android apps, Windows applications published as published application by Citrix XenApp, full SBC/VDI desktops and SaaS based web applications.

App Controller also handles single sign on to on-premise applications (like XenApp published applications) and internet SaaS application using NetScaler. Authentication to Active Directory is done once at deployment of the Worx Home app. Additionally authentications can be forced by having the enduser type in a pincode at the mobile device.


Connectivity between the mobile device and Citrix App Controller is done via the Worx Home app. Worx Home also starts the Citrix receiver or WorxWeb app.

Citrix App Controller allows to selectively wipe  applications and erase associated data located on the mobile device.

App Controller can also be used to lock access to company published apps and applications. For instance when the device is lost. When the owner of the devices leaves the organization the IT department wants to erase company apps and data. While private apps and data installed by the user  remain accessible. Perfect for a BYOD scenario.


Locking apps and erase of data is done from the Devices tab in Citrix App Controller. However when selecting this tab initially no devices are listed.

citrix App controller


To show devices registered in App Controller, simply type in an user id or device name in the search field. Or just type in the letter ‘a’. It willl show all devices registered by WorxHome into App Controller having letter ‘a’ in one of the fields.

To make sure Worx Home succesfully registered the mobile device in App Controller, take the mobile device and start Worx Home app. Select the user id shown in the upper left corner. Select Account. You will see a devicename listed (like iPad (4). This device should be visible in App Controller as well.



This Citrix post shows info on locking and erasing data.


App Controller 2012 R2 unable to deploy Linux images

System Center App Controller is a self-service portal which allows non-IT staff to deploy virtual machines to clouds on-premise, in Service Provider clouds or in Windows Azure.

Windows Azure supports both Windows Server and Linux as guest operating system in a virtual machine.

However when using App Controller 2012 R2 those Linux images are not available for deployment. Three different Linux images are shown but are greyed out.


When using the Azure Management Portal a choice of 9 different Linux images is available:  various versions of Ubuntu, CentOS (Openlogic distribution), SUSE and Oracle Linux.

This is caused by a limitation of App Controller. When preparing a deployment of a virtual machine App Controller creates a so called Configuration Set. This is an XML file which has information like the computername, user account and password or certificate. When user input has been recieved App Controller transmit this information to Azure.

At this moment App Controller 2012 R2 lacks the ability to deploy Linux images.

Unable to deploy A5, A6 or A7 size Windows Azure virtual machine using App Controller 2012 R2

System Center App Controller 2012 R2 is a self service portal which can be used to deploy virtual machines on on-premise clouds managed by System Center Virtual Machine Manager, Service Provider Clouds using Windows Azure Pack  and Windows Azure.

Windows Azure offers so called t-shirt sized virtual machines. These have a Microsoft determined number of virtual cores and  virtual memory size. The size of virtual machines is identified as extra small, small, large etc. Recently Microsoft started to offer large sized virtual machines which are identified as A5, A6 and A7.

Using App Controller 2012 R2 the virtual machine / instance  size A5 , A6 and A7 are missing in the dropdown list showing available virtual machine sizes for deployment.


This is caused by a limitation of App Controller 2012 R2. App Controller maintains a hard coded list of virtual machine sizes that it is able to deploy. A5, A6 and A7 are not in that list. Future new instance sizes available in Azure will not available either as long as the code of App Controller is not updated by Microsoft. This issue is caused by the service management API which is queried by App Controller. This API does not allow to query for available virtual machine sizes hence the hardcode virtual  machine sizes.

Virtual machines sized A5, A6 or A7 can be managed by App Controller. Deployment however of instances with these sizes should be done using the Azure Management Portal, Visual Studio, Azure command-line tool or PowerShell.

%d bloggers like this: