Another of my KB articles got published on the knowledgebase of Citrix.
Creating a vDisk from the target device fails before completion with the following error message:
"Management Interface: vDisk properties were lost."
Multiple server farms with incorrect vDisk settings for Load Balancing. In this example, the error was produced in a simple 2-server Provisioning Server farm configured with local storage as displayed:
There is no solution at this moment for creating a vDisk in this way. A workaround is available by creating the vDisk on the Provisioning Server host itself.
This error is created because of the fact that the 2-local stores are not synchronized and Load Balancing assumes that the stores it connects to are synchronized. With two unsynchronized local stores, it is not possible to create the vDisk from the target device.
CTX129993 – Provisioning Services 6.0 Administrator’s Guide
CTX129994 – Provisioning Services 6.0 Installation and Configuration Guide
CTX121090 – Planning and implementing a Provisioning Server high availability (HA) solution
You can view the original article here.
In VMware and Provisioning Server 6.0 and later, you cannot successfully connect to virtual disk while starting from the local Hard Drive because the 6.0, 6.1 Target Device software is binding to one of these ghost NICs producing a Red X in the virtual disk status tray. In the Event Viewer you see the following Event ID 7026:
The following boot-start or system-start driver(s) failed to load:
When installing the Provisioning Server Target Device software on the virtual machine you are trying to capture an image from are the “Ghost NICs” in Device Manager that the Target Device software is binding to.
- Uninstall the Provisioning Server Target Device software from the virtual machine and restart.
- System Properties dialog box appears.
- Select the Advanced tab and click Environment Variables.
- Click the New button below the System Variables panel.
- In the New System Variable dialog box, type devmgr_show_nonpresent_devices in the Variable Name text box and 1 in the Variable Value text box.
- Click OK to return to the System Properties dialog box and then click OK again.
- Access Device Manager.>.View > Show Hidden Devices.
- Expand the network adapters in the device tree and look for the inactive icons, which indicate unused device drivers.
Note: To remove an unused device driver, right-click the icon and select Uninstall
- Reinstall the Provisioning Server 6.0 or 6.1 Target Device software and restart. You should now be able to connect to the virtual disk.
The ghost NICs are as displayed in the following screen shot:
Note: Ensure to remove the environmental variable after completing the procedure.
You can read the original post here.
Issue(s) Resolved in this Hotfix
This Hotfix addresses the following issues reported against Provisioning Services 6.0 release:
BUG313632 Windows 7 and Windows 2008 targets do not boot up with the correct subnet mask when using CIDR addressing
Installing this Hotfix
• The user must have administrative rights to the server and target device.
To install this hotfix: Continue reading “Hotfix for Citrix Provisioning Services 6.0”
Here’s an overview of a few TechEdge videos (and links to the powerpoint presentations). Each video takes between 38 and 45 minutes each so sit back and enjoy.
Successfully Deploying and Upgrading PVS
PPT Continue reading “TechEdge 2012”
As you could read in this post Citrix has released a patch/update for all of its Provisioning Services versions.
This post is written with PVS 6.1 in mind and is only the PVS server side. The target device update will be posted on a different post.
The user must have administrative rights to the server.
• The server install consists of the console and server installation programs
• You must uninstall before using any of the installations included in hotfix
• Included with the target installation programs are the binaries so that they can be used to replace the present binaries without reimaging the target device.
Continue reading “Installing patch for PVS vulnerability–Step-by-step guide”