Creating a Windows 10 Target Device with Citrix Provisioning Services 7.8

Reading Time: 7 minutes

Citrix Provisioning Services (PVS) is a great way for running your virtual desktop infrastructure (VDI). In my recent blog here I showed you how to setup Citrix Provisioning Services 7.8.

In this blog I will show you how to create a Windows 10 target device running from Citrix Provisioning Services. I will then use this target device disk (vDisk) as a template (golden image) to create multiple target devices running from the same vDisk. I will cover this in another post using Citrix XenDesktop 7.8. For now let’s focus on creating the Windows 10 Target Device vDisk.

In this post I will show you how to:

  • Create a Windows 10 Target Device vDisk
  • Configure a Target Device to use said vDisk and boot from PVS

My lab setup:

  • Windows 2012 R2 server with Citrix Provisioning Services 7.8 installed (pvs01.vikash.nl)
  • Local domain (vikash.nl)
  • Domain controller (dc01.vikash.nl)
  • Hypervisor Hyper-V 2012 R2
  • Windows 10 desktop with latest updates
  • All servers and desktops are running as virtual machines
  • DHCP running on my router
  • Citrix Provisioning Services Boot Disk (blog here)

Make sure that the virtual machine configured in Hyper-V for Windows 10 PVS target is setup as Gen 1 (generation 1) virtual machine, and that the network card is a Legacy network adapter. Otherwise the virtual machine will not be able to boot using PVS. Sources tell me that the next version of Citix Provisioning Services will be able to work with Gen 2 (generation 2) virtual machines in Hyper-V.

Target Device Installation

Now we have to install the Citrix Provisioning Services components in the Windows 10 desktop from which we will create the vDisk.

Mount the PVS ISO on the Windows 10 virtual machine.

pvs78_w10_target_01

Start the autorun and choose Target Device Installation.

pvs78_w10_target_02

Click on Target Device Installation.

pvs78_w10_target_03

Click Install to install the requirements.

pvs78_w10_target_04

Click on Next to start the installation.

pvs78_w10_target_05

Accept the license agreement and click on Next.

pvs78_w10_target_06

Enter your customer information and click on Next.

pvs78_w10_target_07

Select the Destination Folder for installation and click on Next.

pvs78_w10_target_08

We are now ready to install. Click on Install.

pvs78_w10_target_09

After installation has finished, make sure to select Launch Imaging Wizard option and click on Finish.

pvs78_w10_target_10

Now the Imaging Wizard will start. Click on Next.

pvs78_w10_target_11

Enter the name of the PVS server. Make sure you have the right port and use the correct credentials for the PVS server. This can be a domain admin account, provided that they have admin rights on the PVS server. Because I am on my homelab I used my Administrator account.

pvs78_w10_target_12

Select Create a vDisk. Click Next.

pvs78_w10_target_13

The wizard will create a new target device on the PVS server. Choose a device collection to put the newly created target device in. Click on Next.

pvs78_w10_target_14

Enter a name for the vDisk. Select the the correct store and choose the vDisk type. Click on Next.

pvs78_w10_target_15

Choose the activation type for Windows 10. This depends on the license model you have from Microsoft. Click on Next.

pvs78_w10_target_16

Choose to image the entire boot disk. Click Next.

pvs78_w10_target_17

Select the option to Optimize the hard disk and then click on Next. You can adjust the options according to your needs, I choose the defaults because I my experience that is fine.

pvs78_w10_target_18

You will be presented with a summary screen. Check that everything is entered according to your needs and then click Create.

pvs78_w10_target_19

The wizard will create the vDisk and the target device on the PVS server, after optimising the virtual machine. It needs to restart the virtual machine to start the imaging process. Click on Continue.

pvs78_w10_target_20

Now you will be asked to reboot the device. If you choose Yes the Imaging Wizard will restart the virtual machine. At this point you have to make sure that the virtual machine will boot from network or the PVS boot iso. If you choose No the virtual machine will be shut down.

pvs78_w10_target_21

In my case I have to choose No because I can’t change the boot order of a Gen 1 Hyper-V virtual machine while it is powered on. Check if your hypervisor is able to adjust while the virtual machine is powered on.

So I have to adjust the settings of my virtual machine.

pvs78_w10_target_22

First I have to mount the PVS boot iso. Go to the DVD Drive and select the iso.

pvs78_w10_target_23

Now we have to adjust the boot order. Go to BIOS, select the CD and move it to the top of the list. Then click OK.

pvs78_w10_target_25

We can now power on the virtual machine. Connect to the console and check that it is booting from the PVS boot iso and connecting to the PVS server.

pvs78_w10_target_26

Now logon to the virtual machine so the Image Wizard can continue.

pvs78_w10_target_27

The Image Wizard will continue automatically and start with taking a snapshot.

pvs78_w10_target_28

Then the Image Wizard will start the copy process to the PVS server.

pvs78_w10_target_29

After the Image Wizard completed the copy process successfully click on Done.

pvs78_w10_target_30

Time for testing

Now shutdown the virtual machine and disconnect the local “physical” disk, because now we want to start from the newly created vDisk from the PVS server. This has to be done using the hypervisor manager, in my case Hyper-V mmc. Go to settings to remove the locally attached “physical” disk.

pvs78_w10_target_31

Go to IDE Controller 0 and Remove the disk. This will only disconnect it and make it invisible to the virtual machine, the virtual disk file will not be deleted.

pvs78_w10_target_32

When the target device is created on the PVS server, it is set to boot from hard disk. This is done to complete the image proces but can also be used to make changes to the virtual disk. Now we have to tell the target device that is has to boot from the vDisk.

Go to your PVS console and select the Properties from you target device.

pvs78_w10_target_33

In the General tab choose vDisk in the Boot from dropdown menu. Then click on OK.

pvs78_w10_target_34

Also we want to set the Access mode for the vDisk to Standard Image. This is necessary if we want to start multiple virtual machines using the same vDisk (in the future). Go to the vDisk Pool in your PVS console and select the Properties for the vDisk we just made.

pvs78_w10_target_35

In the General tab set the Access mode to Standard Image. Then click OK.

pvs78_w10_target_36

Now it is time to boot the virtual machine and see some PVS magic! Connect to the console of the virtual machine using your hypervisor tools, in my case Hyper-V mmc, so you can see what is happening during boot.

pvs78_w10_target_37

As you can see the virtual machine is booted from my PVS boot iso and logged in to PVS. PVS is accepting the connection and providing the virtual machine with a vDisk.

Logon to the virtual machine to check if the Virtual Disk Status.

pvs78_w10_target_38

In the General tab you can see that the vDisk is now Read Only. This is exactly what we wanted.

pvs78_w10_target_39

In the Statistics tab you can see some diagnostic information.

pvs78_w10_target_40

This concludes this tutorial. Feel free to contact me of you have any questions or comments.

You can also follow me on twitter or add the rss feed from the blog and you will be notified when I add new posts.

Creating a Windows 10 Target Device with Citrix Provisioning Services 7.8 Read More
Create Bootable ISO for target devices

Citrix Provisioning Services create bootable ISO for target devices

Reading Time: 3 minutes

The target devices booting from Citrix Provisioning Services (PVS) server can boot using PXE or using a bootable ISO. I choose to boot my devices using a bootable ISO. This method is very reliable, as it doesn’t rely on PXE services or network connections.

My lab setup:

  • Windows 2012 R2 server running Citrix Provisioning Services 7.8.

In this post I will show you how to:

  • Create a bootable ISO for PVS target devices

Create a bootable ISO for your PVS target devices

Go to the Start Menu and select Provisioning Services Boot Device Manager.

Create Bootable ISO for target devices

 

In my experience many boot related problems can be solved when you enter the IP address of the PVS server here instead of the hostname or fqdn. So I selected Use static ip for the server. Then click on Add.

Create Bootable ISO for target devices

 

Enter the network settings and fill in the IP address of your PVS server. Click on OK.

Create Bootable ISO for target devices

 

Click on Next.

Create Bootable ISO for target devices

 

In the Set Options window enable Verbose Mode. This is very useful in case you have to troubleshoot, and the added boot delay can be neglected. Then click on Next.

Create Bootable ISO for target devices

 

Select Citrix ISO Image Recorder in the dropdown menu and click on Burn.

pvs78_boot_iso_06

 

Choose a location to save the ISO file and click on Save.

pvs78_boot_iso_07

 

When the ISO has been created successfully, click on OK.

pvs78_boot_iso_08

You can now close the Boot Device Management window.

pvs78_boot_iso_09

 

Check that you have the ISO file.

pvs78_boot_iso_10

This concludes this tutorial. Feel free to contact me of you have any questions or comments.

You can also follow me on twitter or add the rss feed from the blog and you will be notified when I add new posts.

Citrix Provisioning Services create bootable ISO for target devices Read More

Setup and configuration of Citrix Provisioning Services 7.8

Reading Time: 6 minutes

Recently Citrix has released Citrix Provisioning Services 7.8 (PVS). I wanted to see how this works, so I decided to set it up in my homelab and share the setup and configuration steps with you guys.

I will be needing this component to stream my desktops and servers. Citrix Provisioning Services (PVS) eliminates the need to manage, update and patch individual systems. Instead it allows us to use a master image to provision computers. This master image (vDisk) can be used simultaneously by multiple computers.

In this post I will show you how to:

  • Install PVS
  • Basic configuration using the PVS wizard
  • Create a PVS farm

My lab setup:

  • Windows 2012 R2 server with patches and updates which I will be using to install PVS
  • Downloaded PVS ISO from www.citrix.com
  • Service Account in Active Directory
  • Local domain (vikash.nl)
  • Domain controller (dc01.vikash.nl)
  • Hypervisor Hyper-V 2012 R2
  • SQL server (sql01.vikash.nl)
  • Citrix License Server (dc01.vikash.nl)
  • All servers running as virtual machines

Install Citrix Provisioning Services 7.8

Mount the ISO to using Hyper-V manager on your virtual server and start the setup. Click on Server Installation.

pvs_78_01

 

The setup wizard will automatically detect the required components and will prompt to install them. Click on Install.

pvs_78_02

 

Click on Yes to install the SQL components.

pvs_78_03

 

Click on Next on the welcome screen.

pvs_78_04

 

Accept the license agreement and click on Next.

pvs_78_05

 

Enter the username and organization name. Select the all users option and click on Next.

pvs_78_06

 

Choose the installation folder. In my case I left this default. Then click on Next.

pvs_78_07

 

Click on Install to start the installation.

pvs_78_08

 

Click on Finish to finish the installation.

pvs_78_09

 

You will get a warning message about the PVS Console. We will install this later. Click on OK.

pvs_78_10

 

Now the Provisioning Services Configuration Wizard will automatically start. Click on Next.

pvs_78_11

 

You will now be prompted to choose a DHCP option. When the PVS server is running DHCP (local service), choose The service that runs on this computer. In my case my DHCP is running on my router, so I choose The service that runs on another computer. Click on Next.

pvs_78_12

 

Choose the PXE options. If your virtual machines will boot using the PXE service, enable this. In my environment I will be using a bootable ISO for all the virtual machines running from PVS. You can see  here how to create a bootable ISO. So I choose The service that runs on another computer and click on Next.

pvs_78_13

 

Now we have to create a new farm since this is my first PVS server. Choose Create farm and click on Next.

pvs_78_14

 

The wizard will create the database now. The active directory account running the configuration wizard should have rights to create the database on the SQL server. Otherwise make sure the database is created beforehand and that you have the correct account to login to the database. Enter the SQL fqdn and click on Next.

pvs_78_15

 

Enter the database name. If this is an existing database, choose the name using the dropdown menu. Make sure to select the correct Active Directory group to manage the PVS server (Farm Administrator group). Enter the other information needed to create the farm and click on Next.

pvs_78_16

 

Select the destination to store the virtual disks for the virtual machines running from PVS. Give it a name and click on Next.

pvs_78_17

 

Enter the license server fqdn. Click on Next.

pvs_78_18

 

Now we have to specify an account for running the PVS service. This will be used to run the Stream and Soap service. Enter the correct information and click on Next.

pvs_78_19

 

The target devices running from PVS cannot update their own password in the Active Directory, so we must enable PVS to do this for us. Make sure this is enabled and click on Next.

pvs_78_20

 

Check the network communication settings for management and streaming. Select the correct interface, check with your network admin in case this is not clear. In my case my PVS server has one NIC. Click on Next.

pvs_78_21

 

Next you will be prompted to enter the TFTP options. Enable it and click on Next.

pvs_78_22

 

Now everything is setup to finish the configuration wizard. Click on Finish.

pvs_78_23

 

If you have Windows Firewall running on your server, you will get a message about that. Make sure you disable it later or open the necessary ports. Click on OK.

pvs_78_24

 

Click on Done after the configuration wizard has finished.

pvs_78_25

 

Install the Citrix Provisioning Services Console

In order to manage Citrix Provisioning Services you need to install the console. Run the setup from the Citrix Provisioning Services ISO and this time click on Console Installation.

pvs_78_26

 

Click Next in the welcome screen.

pvs_78_27

 

Accept the License Agreement and click on Next.

pvs_78_28

 

Enter the Customer Information and click on Next.

pvs_78_29

 

Choose the installation path and click on Next.

pvs_78_30

 

Click on Install to begin the installation.

pvs_78_31

 

After the installation is finished, click on Finish.

pvs_78_32

 

Now go to the Start Menu and start the Provisioning Services Console.

pvs_78_33

 

Right click Provisioning Services Console and click on Connect to Farm….

pvs_78_34

 

Enter the correct fqdn, select Auto-login on application start or reconnect to automatically connect to the PVS server and then click on Connect.

pvs_78_35

 

Now you should be able to manage the PVS server.

pvs_78_36

This concludes this tutorial. Feel free to contact me of you have any questions or comments.

You can also follow me on twitter or add the rss feed from the blog and you will be notified when I add new posts.

 

 

Setup and configuration of Citrix Provisioning Services 7.8 Read More

How to setup and configure Citrix Licensing Server 11.13.1.2

Reading Time: 3 minutes

I already did a setup and installation of Citrix Licensing Server 11.12.1 here, but it is always nice to have a setup guide for a new version.

Adding a Citrix Licensing Server to your environment is important if you are going to setup and use Citrix products and solutions. So let me show you how to:

  • install the license server
  • configure the license server
  • add a license file to the license server

My environment for the installation:

  • downloaded the Citrix Licensing Server 11.13.1.2 (Build 16002) for Windows (www.citrix.com)
  • Windows 2012 R2
  • domain name: VIKASH (vikash.nl)
  • account for setup: Administrator (VIKASH\Administrator)

Installing Citrix Licensing Server 11.13.1.2

Unpack the .zip file and start the installer.

lSrv_11.13.1.2_01

 

You will be presented with the screen below. Accept the license agreement and click on Next.

lSrv_11.13.1.2_02

 

Choose your installation path and click on Next.

lSrv_11.13.1.2_03

 

Next you will be presented by the port for the Licensing Server. Change it as you prefer, just make sure that it doesn’t interfere with services using those same ports on your server. Click on Next and the installation will begin.

lSrv_11.13.1.2_04

 

After the installation has finished, you will be presented with a summary screen. I selected the option not to participate in the Customer Experience Improvement Experience Program. Make your choice and click on Finish.

lSrv_11.13.1.2_05

 

Now it is time to upload your license. Go to the Start Menu and start the Citrix License Administration Console.

lSrv_11.13.1.2_06

 

Your default browser will open with the correct URL for the Citrix License Administration Console. Click on “Continue to this website” to move past the SSL warning. We can fix this later, for now it is not important. Your session will be encrypted using the SSL certificate installed with the Citrix Licensing Server anyway.

lSrv_11.13.1.2_07

 

Click on Administration.

lSrv_11.13.1.2_08

 

You will be prompted to log on. Use your Domain Administrator (or the user used to install the Citrix Licensing Server) to log on. Click on Submit.

lSrv_11.13.1.2_09

 

Click on Vendor Daemon Configuration in the menu on the left site. Then click on Import License.

lSrv_11.13.1.2_10

 

Now click on Browse to locate your license file. Then click on Import License.

lSrv_11.13.1.2_11

 

Click on OK after the import is finished.

lSrv_11.13.1.2_12

 

The Citrix Licensing Server will only read the imported licenses after a reboot, or after the Citrix Licensing Server has been restarted. Let’s restart the license server. In the Run dialogue box enter services.msc and click on OK.

lSrv_11.13.1.2_13

 

Locate the Citrix Licensing service, select it and click on the reboot icon in the menu.

lSrv_11.13.1.2_14

 

Now switch back to your browser and reload (or re-open) the Citrix License Manager Console and go to the Dashboard. Your licenses should now be visible.

lSrv_11.13.1.2_15

How to setup and configure Citrix Licensing Server 11.13.1.2 Read More

Apple Airport Extreme “disable” DHCP and keep NAT

Reading Time: 3 minutes

The Apple Airport Extreme is my home router and access point. Recently I wanted to use DHCP on my Synology NAS and disable it on the Airport Extreme. Guess what, when you disable DHCP on the Airport Extreme, it also disables NAT! Not what I had in mind. I am a fan of Apple products, and wanted to keep using the Airport Extreme for my WAN -> LAN connection (internet), because I am pleased with the performance and stability.

There are only three options to choose from:

  • DHCP and NAT (which I am using currently)
  • DHCP only
  • Off (Bridge Mode)

See the screenshot below:

airport_extreme_dhcp_01

None of the options suited my needs, so what I found out is that I can keep the DHCP and NAT option enabled, but deplete the DHCP servers IP address scope. So basically I am going to setup my DHCP server on the Airport Extreme with a scope of two IP addresses and then immediately reserve those ip’s with fake MAC addresses. This way the Airport Extreme will not be able to serve IP addresses in my network, and I can now setup another DHCP server to fit my needs. In another post I will explain why I need another DHCP server.

Let me walk you trough the procedure using the screenshots below.

First let’s start by opening the Airport Utility, select your Airport Extreme Base Station and click on Edit:

airport_extreme_dhcp_02

Then go to the Networking Tab and click on Network Options…:

airport_extreme_dhcp_03

Setup the DHCP scope according to the settings in the screenshot below. The IP address space on my LAN is 192.168.1.x. You can have another range, adjust it to your needs. So I basically setup a DHCP scope consisting of two IP addresses. When you’re done, click on Save.

airport_extreme_dhcp_04

Now we have to add the fake IP reservations. In the DHCP Reservations section click on the + sign.

airport_extreme_dhcp_05

I then add Dummy 1 and Dummy 2 clients using a fake MAC address. Click on Save

airport_extreme_dhcp_06

airport_extreme_dhcp_08

Now your Network tab should look something like this:

airport_extreme_dhcp_07

Click on Update and that’s it! DHCP is now “turned off” on the Airport Extreme, and you are free to use another DHCP server for more flexibility in your LAN.

 

Apple Airport Extreme “disable” DHCP and keep NAT Read More

Thin clients and HDX 3D Pro support demystified

Reading Time: 3 minutes

Recently I was presented with the following case. I was migrating from a Citrix XenDesktop 5.6 environment to a Citrix XenDesktop 7.6 environment. The new environment was running XenDesktop VDI’s with Windows 7 on Citrix XenServer. Because CAD and 3D application support was a requirement, the customer decided to use nVidia grid cards and use HDX 3D Pro.

Everything was running fine in the new XenDesktop 7.6 environment (server wise) and I started testing with thin clients which the customer already had. The thin clients did support HDX 3D Pro according to the manufacturer, so we were good to go. After logging in to the virtual desktop using said thin client, I got the little icon in the task bar telling me that HDX 3D Pro was enabled. But the desktop graphics performance was very poor. It was lagging, slow and was absolutely not fast in response. It felt a lot slower then the XenDesktop 5.6 environment.

Now after investigation I found that these thin clients did not support the H.264 codec fully. Using the HDX monitor I could see that they were using Deep Compression V2. But the cpu of the thin client was being hammered to the max when working on the XenDesktop 7.6 VDI.

The old XenDesktop 5.6 environment was running fine, but the graphics were off course Legacy mode. So the next step now was testing without the nVidia vGPU support in the VDI and enable Legacy mode graphics. That means disable vGPU support in the virtual machine in XenServer, disable desktop composition redirection and enable Legacymode graphics in the Citrix policies. Still the graphics performance was very poor, and HDX monitor showed me that Deep Compression V2 codec was still being used! I was not alone on this, searching the Citrix Forum resulted in:

Contacting Citrix support they eventually told me that I also had to reinstall the VDA agent in the virtual desktop and choose the option not to enable HDX 3D Pro support during installation. When this option is enabled during installation, it is not possible to use Legacymode graphics. This worked, the Windows 7 VDI reverted back to Legacymode graphics and the performance on the thin client was now very good.

So now the next step was to find out what thin client really supports HDX 3D Pro. Not partial support for the H.264 codec, but fully support it so we know for sure that Deep compression V2 codec performance would be good. I found out that manufacturers brand their thin clients with support for HDX 3D Pro or Citrix Certified or Citrix Ready, but they were unclear of the actual performance with HDX 3D Pro. Then I found some information which made clear what the HDX and Certified for Citrix should mean:

 HDX 3D Pro

Check out the website here. Ok, this makes sense. With this new information I started searching for thin clients which are HDX 3D Pro Verified and with this feature enabled. Searching the Citrix Ready Marketplace I found a list of thin clients which were fully certified for HDX 3D Pro! Check the list here. A few of them were already mentioned in a Citrix Forum post here (mentioned earlier).

So this is something that is a little bit of a grey area. Looks like thin clients enabled for HDX 3D Pro does not mean automatically a good performance in the VDI where HDX 3D Pro is a requirement. You have to test, make sure, and then re-test. Otherwise you and your customer will end up with very disappointing results, making you and Citrix look bad while it is the manufacturers of the thin clients who are to blame in not being utterly clear on what their product do support and what you can expect performance-wise (yes I am looking at you Dell).

This is my experience, and I could be wrong on this off course. What are your thoughts in this?

Thin clients and HDX 3D Pro support demystified Read More