I have written another article for the May edition of the magazine IT-Administrator. This time I describe the features and functions of the Citrix Cloud Gateway. Hope you enjoy reading the article. And here is the german teaser:
“Ein neues Produkt aus dem Hause Citrix ist das CloudGateway. Damit möchte Citrix Administratoren die zentrale Bereitstellung aller Enterprise-Anwendungen ermöglichen. Hierzu gehören sowohl klassische Windows-, als auch Software-as-a-Service, sowie Web- und native iOS- und Android-Anwendungen. Ebenfalls ist es hierüber möglich, die von den Benutzern benötigten Daten gesichert bereitzustellen.”"
If you try to configure the Citrix AppController this may fail with the following message:
The administrator’s email address does not exist in Active Directory. Please enter a valid email address.
This error might also occur if you have entered an existing email address. The configuration not only checks if it’s an valid email address for an Active Directory User – it also checks if the corresponding user has a first and a last name. So if you see this message just open the corresponding user and enter a first and last name. After this the error message should be gone.
For the March edition of the IT-Magazine “IT-Administrator” I have written an article about managing Office licenses with the help of the AppSense Application Manager. The Magazine was released yesterday. Hopefully you will like the article. (Sorry for the german teaser – but the article is also in german…. )
“In Zeiten von BYOD und virtuellen Desktops besteht neben den technischen Herausforderungen auch eine große organisatorische Hürde: die Lizenzierung. Denn nach wie vor gibt es nicht wenige Programme, die pro Gerät zu lizenzieren sind. Angesichts der Fülle an Geräten, mit denen Benutzer auf zentral bereitgestellte Anwendungen zugreifen, ist mit explosionsartig steigenden Lizenzkosten zu rechnen. Um hier für mehr Kontrolle zu sorgen, erlaubt es der AppSense Application Manager, den Start einer zentralen Applikation auf bestimmte Geräte einzuschränken. Wir zeigen Ihnen in diesem Workshop, wie das geht.”
One of our customers recently upgraded his VMWare enviroment from Version 4 to Version 5.1 He is using Provisioning Services to deploy some of his servers.
In the past it was necessary to use the "E1000” Network-Adapter to start the PVS Target Devices. With release 5 of VMWare this changed and it’s now necessary to use the VMXNet3 Network-Adapter. Thus we changed the network adapter (which are saved in the image) from E1000 to VMXNet3 – following these steps:
1. Re-image the PVS-vDisk to a local Hard-Drive from a Virtual-Server
2. Uninstall Citrix PVS Target Device Tools
3. Update of the VMWare Tools
4. Remove the E1000 Network Adapater and add the VMXNet 3 Adapter
5. Reboot the server
6. Install PVS 6.1 Hotfix 16 Target Device Tools
7. Create a new PVS-vDisk (with the updated settings and drivers)
Until now everything worked fine – but if we tried to start any server (except of the master) with this PVS vDisk a blue screen was displayed. Unfortenately we were not able to read the full message because the server was directly rebooted. To stop this you have to press F8 before Windows boots (to get the selection menu with “Safe Mode” and so on) and select “Disable automatic restart on system failure” – now the system is not automatically restarted and you can read the full blue screen message. Interestingly the blue screen only displayed a stop 0x0000007B error – with no further details.
We started to check why this error occured. The vDisk was neither created using a Static IP nor something of the E1000 Adapter was left in the image. Furthermore it didn’t help to activate the “Interrupt Safe Mode” in the Bootstrap settings of the PVS-Servers (which should be ok because it was only needed for VMware 5.0).
Even a clone of the original master crashed with a blue screen while booting from the vDisk.
In Citrix KB125361 exactly our problem “Target Device Fails to Start with VMXnet3 Drivers” and “The target device fails with a STOP 7B Blue Screen error.” is descripe. Inside of this article a Microsoft Hotfix is mentionend which fixes the following problem “0x0000007B" Stop error after you replace an identical iSCSI network adapter in Windows Server 2008 R2 SP1 or in Windows 7 SP1“ – sounds like our problem.
We removed the PVS Target Device Tools, installed the mentionend Microsoft Hotfix (KB 2550978), installed the PVS Target Device Tools again and created another image and tried to boot our PVS-Targets. Again a blue screen – except of the cloned servers which worked fine.
Oh ok?!? – But where is the difference? After checking the VM-Settings we found an interesting difference:
The cloned servers had the same “Ethernet???.pci” value (you can find these settings under VM-Properties => General => Configuration Parameters) – the new created servers had a different value. After changing this to the same value on the newly created servers they booted withoud any problems.
Conclusively we had two problems to fix:
1. Install a Windows Hotfix to solve a problem with changing iSCSI Network Adapters
2. Change the Network Adapter ID inside the VM-Settings to the same number
With the help of Santosh Tilagul (a nice guy from Citrix) we have been able to fix this. So first of all a big thanks to him for his assistance.
Instead of using the configuration tool you manually do the steps which are normaly automated by the configuration tool.
1. Install the HTML5 HDX Engine on the StoreFront Server
2. Open the explorer and open “C:\Program Files (x86)\Citrix\HTML5 Management”
3. Extract the file “HTML5Client”
4. Copy the extracted folder “HTML5Client” (make sure that there is no subfolder HTML5 Client) into the following path: “C:\inetpub\wwwroot\Citrix\STORENAMEWeb”
5. Open the file “C:\inetpub\wwwroot\Citrix\STORENAMEWeb\web.config”
6. Search for “html5”
7. You should see something like: <html5 enabled=”true” platforms=Firefox;Chrome” launchUrl=…..
8. Modify the launch Url so that it looks like: “HTML5Client/src/SessionWindow.html” (IMPORTANT: with quotations)
9. Save the file (and restart IIS)
10. That’s it: Now StoreFront is able to “deliver” a HTML5 Client
There is one other thing I would like to mention about configuring the HTML5 Client:
In the XenApp Policies it’s really important that you activate all three WebSocket policies. After activating the policies you either have to restart your XenApp Servers or restart the Citrix IMA Service and (with a delay of 15seconds after restarting the IMA service) the Citrix XTE Service.
Now you can start access your Applications using a HTML5 “Client”.
If your StoreFront Server is not (!) connected to the Internet the service “Citrix Credential Wallet service” may fail to start with the following error:
The Citrix Credential Wallet service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.
Evemt ID: 7000
Source: Service Control Manager
To fix this you have to change a setting in the following file:
C:\Program Files\Citrix\Receiver Storefront\Services\CredentialWallet\ Citrix.DeliveryServices.CredentialWallet.ServiceHost.exe.config
Open this file (e.g. with Notepad) and search for the following entry:
<!– Set enabled=false, if this machine does not have external access to the internet –>
Change the setting “generatePublisherEvidence enabled=”true”” into “generatePublisherEvidence enabled=”false”” and save the file. After changing this setting you should be able to start the “Citrix Credential Wallet service” even if your StoreFront-Server is not connected to the Internet.