Skip to content

Windows 2012R2 stops at Boot screen while Network Boot is activated for Citrix Provisioning Server

During my last Citrix Provisioning Server deployments I had an interesting problem. The Windows 2012R2 Master Template always stopped at the Boot screen. This happened even before it was converted into a PVS Device (Disk) nor the Target Device Tools had been installed.

The VM was running on VMWare ESXi 5.5 and we used Citrix Provisioning Server 7.6. After changing the first boot device to Network – though that an initial connection to Citrix PVS happened – the boot stopped while showing the Windows Boot screen. Although we were still booting from the local hard drive – so it didn’t make any sense why this was happening.
2014-10-13 08_25_32-DEDAM-CTXSV0011

After some more testing we discovered that this was not happening with all Windows 2012R2 VMs – only with new deployed ones. Ok let’s check where the difference between the VMs are.

New VMs where running in the ESXi Compatibility mode 5.5 (VM-Version 10).
2014-10-15 12_49_19-vSphere Web Client

While old VMs where still running in the ESXi Compatibility mode 5.0 (VM-Version 8).
2014-10-15 12_52_16-vSphere Web Client

After checking what has changed we saw the new VMs were using a SATA-Controller for the CD-/DVD-Drive instead of an IDE-Controller.

Old VM (Version 8):
2014-10-15 12_56_00-vSphere Web Client

New VM (Version 10):
2014-10-15 13_00_00-vSphere Web Client

Though we removed the CD-/DVD-Drive and SATA Controller from a new VM and added the CD-/DVD-Drive using an “old” IDE-Port.
2014-10-13 08_27_33-vSphere Web Client

After this change the VM was booting without any problems.
2014-10-13 08_30_00-DEDAM-CTXSV0011

I don’t know what causes this problem – but hopefully it will be fixed from either Citrix or VMWare in one of their next versions.

(Undocumented) Issues when Upgrading to XenDesktop / XenApp 7.6

During the last days I tested the Upgrade from XenDesktop 7.5 to XenDesktop 7.6. I found some interesting “Issues” during the upgrade which seem to be not documented.

Upgrading StoreFront on a separate System

If you upgrade StoreFront on a separate Server and use the Upgrade Wizard you receive the following message:
2014-10-07 11_45_22-RDS - DEDAM-SV361 - Royal TS

As you can see the Upgrade process try’s to check something which is not available on a standalone StoreFront system. Luckily you can ignore the warning and continue with your installation. Actually StoreFront even doesn’t check the licenses later – so even if no licenses are available StoreFront works.

Upgrading Citrix License Server on a separate System

The more confusing message is shown if you use the Upgrade Wizard to upgrade the Citrix License Server which is not installed on a Delivery Controller. If you try to upgrade the following message is displayed:

2014-10-07 14_56_37-RDS - DEDAM-SV367 License Server - Royal TS
This product requires a newer license. You must install a license with a Subscription Advantage date of “2014.0815” or later.

Even if you have licenses with a Subscription Advantage date after “2014.0815” the message is displayed. Luckily you can also safely ignore this message (of course only if your Subscription Advantage date is after 2014.0815) – your users will still be able to access their Desktops and Applications.

Auto Fill User Start Menu with Citrix Receiver 4.x

One of the biggest challenges in a lot of migrations to Citrix Receiver 4.x (and XenDesktop / XenApp 7.x) is the (missing) function to automatically fill the users start menu. In the past it was quite easy to push all published applications for the user into his start menu using the Citrix Receiver Enterprise (aka. Online Plugin). Citrix decided to stop the development of the Citrix Receiver Enterprise and fully switched to the Citrix Receiver.
But how can we now automatically fill the user start menu without any user interaction?

First of all you need to make sure that the Receiver Single-Sign-On is working. If you don’t know how to configure this read the article “Citrix Receiver Single-Sign-On (Pass-through Authentication) does not work with StoreFront”.

Also it is necessary to configure the Receiver automatically with your StoreFront Store. You can either achieve this by creating a GPO (with the Receiver adm) or using another command line parameter (next to /includeSSON for Single-Sign-On). To use a GPO import the Receiver ADM-File into the GPO. You can find the ADM-File on a computer with an installed Receiver in the following path:
C:\Program Files (x86)\Citrix\ICA Client\Configuration   (or C:\Program Files\….)

After importing the icaclient.adm you find the following settings inside the GPO:
Computer Configuration => Administrative Templates => Classic Administrative Templates (ADM) => Citrix Receiver => Storefront => Storefront Accounts List
2014-09-03 08_39_59-RDS - DEDAM-SV421 - Royal TS

Change the setting to enable and enter the Store (account) details under “Show”.
2014-09-03 08_41_11-RDS - DEDAM-SV421 - Royal TS

Enter your StoreFront Store in the following format:
STORE NAME;STOREURL;ON;STORE DESCRIPTION
2014-09-03 08_40_36-RDS - DEDAM-SV421 - Royal TS

Alternatively you can add the following parameter to your Receiver-Installation:
STORE0="STORE NAME;STORE URL;On;STORE DESCRIPTION"

The next step is to add the following registry keys under the path HKLM\SOFTWARE\Wow6432Node\Citrix\Dazzle (if it’s a 32Bit-System without Wow6432Node):

Name Type Data
InitialRefreshMinMs REG_SZ 1
InitialRefreshMaxMs REG_SZ 1
DontWarnOfRemovedResources REG_SZ True

The last one (DontWarnOfRemovedResources) is optional – if you activate this a user is not informed if one of his applications is removed.
For adding the keys the following commands can be used:

REG ADD HKLM\SOFTWARE\Wow6432Node\Citrix\Dazzle /f /v InitialRefreshMinMs /t REG_SZ /d 1
REG ADD HKLM\SOFTWARE\Wow6432Node\Citrix\Dazzle /f /v InitialRefreshMaxMs /t REG_SZ /d 1
REG ADD HKLM\SOFTWARE\Wow6432Node\Citrix\Dazzle /f /v DontWarnOfRemovedResources /t REG_SZ /d True

Don’t forget to change the path on a 32Bit-System.
2014-09-02 11_26_27-dedam-wv210 CTX Test - Copy

Now you need to create a new Shortcut in the Startup Folder. With this Shortcut the Receiver automatically connects to Storefront and receives the subscribed applications of the user after he logged in. For every application a Shortcut is created in the Start Menu. The Shortcut gets the following settings:

Target:
"C:\Program Files (x86)\Citrix\SelfServicePlugin\SelfService.exe" -logon -poll
Start in:
"C:\Program Files (x86)\Citrix\SelfServicePlugin\"

2014-09-08 08_12_21-dedam-wv210 - Remote Desktop Connection

If your users now log in not all of their available applications won’t be published to the Start Menu. The reason for this is that the user first needs to subscribe all of his available applications. The good thing is: You can also automate this Smiley

Switch to your Delivery Controller and start the Desktop Studio. Now open  “Delivery Groups => Applications” and change the Settings of one Application. You need to change the “Description and keywords”. Either enter
KEYWORDS:mandatory
or enter
KEYWORDS:auto
In this situation both keywords have the same effect – after the user logs on and the SelfService is triggered with –logon and –poll every application is subscribed for the user. Of course only applications with a configured Keyword are subscribed.2014-09-09 10_16_04-RDS - DEDAM-SV421 - Royal TS

The difference between the keywords is that with “auto” the application is only once subscribed – if the user removes it from his applications inside the Receiver it stays removed. If the keyword is “mandatory” the application is subscribed with every user logon. Don’t forget to enter the Keyword for every application which should be automatically published to the Start Menu.

That’s it – now Applications are automatically pushed to the user start menu after he logged in – if anything is unclear feel free to contact me.

Book: Citrix XenDesktop 7.5 and XenApp

51G-KY1yyuL

In the last week I finally received a copy of the book  about Citrix XenDesktop and XenApp 7.5 which Nico Luedemann and I have written.

It’s an absolutely awesome feeling to see the printed book after a lot of work (and time of waiting). I can only suggest everyone to try and write his own book – it’s a really interesting experience.

A big thank you goes to my family for beeing so patient with me while I was spending such a lot of time for writing the book.

Many thanks also go to Sebastian Kestel from Galileo Computing – thanks for the good collaboration during the whole project.

I hope you all enjoy reading the book – if you have any questions feel free to contact me. The book is published by Galileo Computing. You can buy it as a print copy or ebook.

XenDesktop 7.5 and XenApp

Updated Citrix XenDesktop / XenApp 7.x PowerShell Documentation Script

I have updated the XenDesktop / XenApp 7.x PowerShell Documentation Script. Next to a small bugfix I have added the Documentation of the Hosting-Connections. Thus the following things are now documented:

  • General Site Informations
  • Logging Settings
  • Licensing
  • Controllers
  • Databases
  • Administrators
  • Machine Catalogs
  • Applications
  • Hosting
  • Storefront Servers (not the StoreFront Config)
  • App-V Server

The following main thing is missing:

  • Policies

Files

The script is divided into two files:
jhmeier-xd7-xa-7.x-documentation-v04.ps1
en-US.xml

The first file is the script himself, while the second file is for an easy modification of the script-output for other languages.

Script Usage

To use the scripts a few prerequisites must be fulfilled:

  • XenDesktop / XenApp PowerShell Extensions
  • Microsoft Word
  • XenDesktop / XenApp Admin Account (with at least Read privileges)
  • PowerShell Execution Policy
  • The script and the language file need to be in the same location.

That should it be – just execute the script. The script starts and creates an (invisible) Word-Document in the background. When it’s finished it saves the document with the name XD-XA-SITE-NAME.docx in the script folder.

Parameters

The script supports (but doesn’t need) the following parameters:
-TextLanguage en-US
If you don’t want to have an output in the default language (English) you need to define the wanted language. Attention: Therefore you need a separate language xml file – see Language Files.
-DeliveryControllerAddress DeliveryControllerFQDN
If you run the script without this parameter it tries to connect to localhost – but if that’s not a Delivery Controller you need to specify it

Language Files

If you run the script – without creating a language specific xml file – the output looks like this:
Description: Description in the System language
If that’s ok for you – you have nothing to do – but if you prefer a complete output in your language like (in German):
Beschreibung: Beschreibung in Deutsch
you need to copy the file en-US.xml and rename it to e.g. de-DE.xml. After that open the new file with an editor of your choice. You now find a lot of entries which look like the following:
<Description>Description</Description>
Now you need to translate the middle for every necessary line so that it looks like this:
<Description>Beschreibung</Description>

License

The script is published under the GPL.

Download

jhmeier-xd-xa-7.x-documentation-v04.zip

Feedback

Any feedback would be really welcome – if you have something to make the script better or have any questions – feel free to contact me.

IT-Administrator Article – Citrix XenMobile

I have written another article for the print magazine IT-Administrator. This time it’s an article about Mobile Device and Mobile Application Management with Citrix XenMobile. You can find the full article in the May edition.

ita201405-titel

Mobile Geräte drängen in die Unternehmen. Kein Wunder, dass die großen Software-Anbieter sich immer stärker diesem Thema widmen. Seit der Übernahme von Zenprise hat sich auch bei Citrix im Bereich Mobile viel getan. So konnte Citrix das Mobile Device Management ursprünglich nicht bedienen. Im neuen XenMobile ist dies nun möglich. Das ehemalige Cloud Gateway hat Citrix gleich mit hineingepackt. Doch welche Editionen enthalten welche Funktionen und wofür benötigen Sie die einzelnen Komponenten? Diese Fragen klären wir für Sie in diesem Beitrag.

Citrix XenDesktop / XenApp 7.x PowerShell Documentation Script

Hi everyone,

I think you all know the absolute fantastic PowerShell Documentation Scripts for Citrix XenApp (up to 6.5) and PVS created by Carl Webster. With these scripts it’s absolutely easy to create a Documentation of a XenApp- or PVS-Farm. Unfortunately Carl didn’t create (or release) a documentation script for XenDesktop / XenApp 7.x yet, so I decided to create my own script. It’s not comparable (and actually that’s not my intention) to Carls scripts but documents the following things (in a more basic way):

  • General Site Informations
  • Logging Settings
  • Licensing
  • Controllers
  • Databases
  • Administrators
  • Machine Catalogs
  • Applications
  • Storefront Servers (not the StoreFront Servers)
  • App-V Server

The following main things are missing:

  • Policies
  • Hosting

The script is divided into two files:
jhmeier-xd7-xa-7.x-documentation-v03.ps1
en-US.xml

The first file is the script himself, while the second file is for an easy modification of the script-output for other languages.

Script Usage

To use the scripts a few prerequisites must be fulfilled:

  • XenDesktop / XenApp PowerShell Extensions
  • Microsoft Word
  • XenDesktop / XenApp Admin Account (with at least Read privileges)
  • PowerShell Execution Policy
  • The script and the language file need to be in the same location.

That should it be – just execute the script. The script starts and creates an (invisible) Word-Document in the background. When it’s finished it saves the document with the name XD-XA-SITE-NAME.docx in the script folder.

Parameters

The script supports (but doesn’t need) the following parameters:
-TextLanguage en-US
If you don’t want to have an output in the default language (English) you need to define the wanted language. Attention: Therefore you need a separate language xml file – see Language Files.
-DeliveryControllerAddress DeliveryControllerFQDN
If you run the script without this parameter it tries to connect to localhost – but if that’s not a Delivery Controller you need to specify it

Language Files

If you run the script – without creating a language specific xml file – the output looks like this:
Description: Description in the System language
If that’s ok for you – you have nothing to do – but if you prefer a complete output in your language like (in German):
Beschreibung: Beschreibung in Deutsch
you need to copy the file en-US.xml and rename it to e.g. de-DE.xml. After that open the new file with an editor of your choice. You now find a lot of entries which look like the following:
<Description>Description</Description>
Now you need to translate the middle for every necessary line so that it looks like this:
<Description>Beschreibung</Description>

License

The script is published under the GPL.

Download

jhmeier-xd-xa-7.x-documentation-v03.zip

Feedback

Any feedback would be really welcome – if you have something to make the script better or have any questions – feel free to contact me.

That’s it – hopefully the script is useful for some of you.

Follow

Get every new post delivered to your Inbox.

%d bloggers like this: