Think IPM

Monday, October 22, 2012

XenDesktop Setup Wizard fails after PVS upgrade.

After upgrading from Citrix Provisioning Server 5.6 to 6.1, I noticed that the XenDesktop Setup Wizard began to fail by tossing up a snap-in error and complaining that a Broker.Admin PowerShell snap-in was not loaded.

image

This was actually a super easy fix and an equally easy post so here’s the fix. Winking smile

Just rerun the \Console\ISSetupPrerequisites from either the XD or PVS CD.

Broker_PowerShellSnapin_xXX.msi
Host.PowerShellSnapIn.msi
Configuration_PowerShellSnapIn_xXX.msi

Be sure to run the appropriate 64 or 32 bit versions for your Provisioning Server. (It should be 64 bit by now though!)

A quick repair on all of them and you will be up and running without even rebooting.image
Pretty Straightforward. 

By the way, every so often, I like to be thrown an easy one.  Thanks Universe.

Click Here to Continue Reading >>

Wednesday, October 17, 2012

PVS Target Blue Screen of Death: 0x0000050 [Resolved]

image5

While implementing a new Citrix Provisioning Server 6.1 at a client site, I was stumped by this BSOD popping up when trying to Network boot a Windows 7 x64 bit VM.  Boot up the VM via it’s hard drive and there were no problems.  As soon as you tried the network boot, Blue Screen Of Death!

Inspecting the Windows 7 event log and I was finding an Event ID 7026 error.

The following boot-start or system-start driver(s) failed to load:
Bnistack

That error lead me to this KB article. [http://support.citrix.com/article/CTX133188
Nothing particularly helpful in there unfortunately since I had already made sure to remove all ‘ghost ‘ NICs already.

Since I was pretty sure this was NIC related, I did some more Googling around and found this KB Article [http://support.citrix.com/article/CTX131993].  Although not completely identical to my blue screen, it did have a piece of information in it that was useful (and at the time, NEW to me).

Provisioning Server 5.6.x and 6.0 are now supported on vSphere 5 with an updated Bootstrap configuration change on VMXNet3 NIC’s only.
E1000 NIC’s are not supported on vSphere 5.

A quick double check of my VM’s properties and I verified that we were using the E1000 NIC on the Windows 7 virtual machines.  I actually had explicitly decided to use the E1000 since I was under the impression that it was the most compatible NIC for such basic operations such as the PXE Boot.   I made a quick change to the VM’s properties, added in the VMXNet 3 Network card, restarted to a network boot and was off to the races.

Click Here to Continue Reading >>

Wednesday, October 10, 2012

Reader Question : Ask the Readers about VPLEX Backups

A reader asked me this question and I unfortunately did not know of any answers so I thought I would post it up and see if anyone could shed some light on it.  If you have any answers or experiences, please share them in the comments.  Thanks!  - Carlo

 

Yesterday I went to the 2012 EMC Forum at the Hilton in New York City, and while sitting in a session regarding active/active datacenters I realized something important. 

How do you properly architect your backup for an active/active datacenter using VPLEX and the Nexus OTV transport? 

Today I have an active/passive architecture and my backups remain local to the servers at the active site.  If I enable an active/active configuration, I wouldn’t want the backup traffic to have to travel across my point to point connection because it could easily saturate the line.  I am curious to hear if there are any backup solutions that exist today that are VPLEX/OTV aware? 

 

In an ideal scenario when the Guest Virtual Machine was moved to another site, the backup software would become aware and run the backup to an appliance/storage local to the VM at the site.  In order for this to work properly, the backup data should be replicated to both sites in case you need to restore at any given time.  As long as the backup data was in sync at both sites, after a guest was migrated, the backup appliance would already have the full backups and should be intelligent enough to know it now only needs to run a differential backup.

 

Does anything exist, or is anyone aware of anything coming soon that will address this?

Click Here to Continue Reading >>