Citrix XenMobile 9 Partner License

I wanted to trial out Citrix XenMobile in our Demo Lab this week. I installed the software but had problems with the license file provided to Citrix Partners. The file is provided as a CRT. As such this cannot be installed on the central License server as i had hoped. For customer this would not be a problem as they would receive a .LIC file and be able to upload to the license server as expected.

Continue Reading

Fusion-IO Aquired by SANDisk

RealServe IT has been a Fusion-IO partner since our first steps into Desktop virtualisation. We have always liked their flashed based cards for our XenApp and Pooled desktop solutions. Using local storage where it makes sense keeps the design simple , performance high and at a great cost. At small scale for non-persistent data this really made sense.

We wish Fusion-IO well and will keep an eye on what happens now.

Manage Printers without the overhead of GPO, Scripts, Appsense or Citrix Session Policies

A rather common but boring problem is a solution to map users to their required printers.

We commonly group people into AD groups. Then using the information use a logon solution to map those users their printers. The downside with all these common solutions is they have the following downsides :

Continue Reading

XenDesktop Personal VDisk Backup and Restore

Citrix have an detailed article on Managing Personal Vdisks and backing up and restoring them.
This is detailed in the E-docs here

http://support.citrix.com/proddocs/topic/xendesktop-7/cds-manage-personal-vdisks.html

The following shows the process used by RealServe IT in our labs to test the process.
This process is designed to help move a users Personal Vdisk to another catalog.
This could be used to migrate users to a newer environment or recover from a failure.
Essentialy the scripts attach the users personal Vdisk to another Virtual Machine.

The document says the personal Vdisk can only be moved however to a catalog with a master related to the original catalog the Vdisk started life from. This could limit the flexibilty of this process.

Vmware Powershell CLI
Download the Vmware PowerCLI tools. (eg. Vmware-PowerCLI-5.1.0-793510)
I installed this onto my DDC where i am going to run the scripts.

Citrix Scripts
I grabbed the Citrix scripts from the Xendesktop source media.
(inside \support\tools\scripts)

Certificate Error
When running the script I received a certificate error for Vcenter. Im not sure why as my VSphere client works as expected from the same box.

I found a workaround is to ignore cert errors. To set this run the following powershell commands

ASNP VM*
Set-PowerCLIConfiguration -invalidcertificateaction ignore

Backup Script
From the DDC with the Vmware PowerCLI installed i ran the migration-backup.ps1 script.

VM not Assigned
When running the migration-backup.ps1 script I was getting an error VMs not assigned. This was correct, some of my VMs were not directly assigned to a user yet. This is just a warning.

Restore (Option 1)

1.)Create a new catalog from the same master as the original catalog.
2.)Assign the new catalog to the same delivery group
3.)Put the delivery group into maintenance mode and shut-down machines
4.)Move the Personal Vdisks as required to new storage (xxx_pvdisk.vmdk)
5.)Edit the XML file changing “diskname” to the new storage location
6.)Run migration-restore.ps1 , choose new Catalog, Choose storage, Choose XML file
7.)Remove maintenance mode

Notes

(Note : I received an error about maintenance mode, however the process worked)
(Note : The original Catalog with PVDisks remain and can be deleted once we are happy the process has worked)
(Note : to use powershell to check no-one is assigned to the machines use the following code

(Note : If you clean up the XML to remove unrequired machines, you need to ensure you keep the DUMMY section at the bottom or the script simply exits at the end.)

get-brokerdesktop -machinename domain\machinename

(Note: to manually connect to vmware and add the disk
connect-viserver server servername
new-harddisk -vm xxxx -diskpath “[storage name] folder/xxxx_pvdisk.vmdk”)

Script Change for Vmware Datastore Issue

I had a problem with the restore script running at a customer site. The error log file said the store name was “null” I correct this by amending the script slightly.

I amended the add-harddisk command to use the [$SRname] and $Diskname and this proved to work.
(Note there is a space required between SRname and Diskname)

Other handy VMWare CLI commands                    

get-datastore -vmhost hostname  (this gets a list of the datastore names attatched to that host)
get-harddisk -vm “vmname”   (gets list of harddisk for that VM)

In the case of failure to connect to vmware the proxy connection may need to be disabled.
Set-PowerCLIConfiguration -ProxyPolicy NoProxy -Confirm