[MCS not refreshed at reboot]

Jos,

 

Can you give me a bit more information?

 

What type of machine are you creating, desktop or server?

What hotfixes and version do you have? Specifically do you have 7.6 HF2?

 

Thanks,

 

Mark.

[MCS not refreshed at reboot]

MCS will have done this.

 

Either,

 

 * You are actually looking at a persistent catalog which would be built exactly as you have described, or

 * Somebody has fiddled with the VM setting externally to XenDesktop.

 

Mark.

[FailedToStartImagePreparationVm]

MCS doesn't make any selection about host as that is the responsibility of the hypervisor which is much better placed to make decisions about where VMs should run. If the VM is created with a GPU requirement and ESXi/vSphere chooses to start it on a host with no GPU then that is a flaw in VMware.

 

Mark

[MCS not refreshed at reboot]

That is exactly the reason and I would suspect external interference has caused things to not be configured correctly.

 

When XenDesktop creates non-persistent machines on VMware it uses independent non-persistent disks on the VMs. If you have catalogs that don't have this set then they will not work as clean on boot machines.

 

Mark.

[MCS not refreshed at reboot]

Updated to a VMware template? To update a catalog you have to select a snapshot of a VM and allow XenDesktop to perform the update process. Please detail the steps you've actually performed.

 

Thanks,

 

Mark.

[MCS not refreshed at reboot]

If the machines are showing as "no" in the pending updates then the system doesn't think that there is anything to do. There are a few reasons why this may be the case the most likely being that the catalog update process didn't actually complete successfully and so there is nothing to associate with the machine. I think you'll need to do another catalog update and see if that works.

 

Mark.

[MCS not refreshed at reboot]

Are the machines actually showing that they have an update pending (use the Pending Update filter in Studio search node).

 

Thanks,

 

Mark.

[Increasing disk size MCS]

Campbell, before you do any of this can you please just confirm what version of XenDesktop and VMware you are using?

 

We are aware of an issue with XenDesktop 7.5 & VMware 5.0 that I don't want you to drop into.

 

Thanks,

 

Mark.

MCS Engineering Lead.

[Error Id: XDDS:0DAA3833 while creating machine in MCS]

Citrix.

[Error Id: XDDS:0DAA3833 while creating machine in MCS]

I assume you're also on vSphere?

 

Can you tell us the rough geographic location of the following?

 

* Your XenDesktop Controller

* Your vCenter server

* The ESXi servers on which you're trying to create the machines

 

The previous error was due to a system timeout caused by extreme geographic separation of these infrastructure pieces.

 

Thanks,

 

Mark.

[Error Id: XDDS:0DAA3833 while creating machine in MCS]

Thanks for that, unfortunately without more information we won't be able to progress this.

 

Can you run the Scout Tool that was installed with XenDesktop, enabled CDF Tracing and try again and then email the resulting logs directly to me (my email address is in my profile).

 

Thanks,

 

Mark.

[Error Id: XDDS:0DAA3833 while creating machine in MCS]

What's your hypervisor?

 

Thanks,

 

Mark.

[Add new storage to delivery controller]

Hello,

I have a setup XenDesktop 7.5 on vSphere 5.5.

At the begining, I created a pooled catalog with 20 machines (with PvD).

As this was a quick deploy we only had one storage location to put it.

 

Now we have created 4more datastores, added them to the Hosts connection, but when we add more machines to the existing catalog, they are still created on the first datastore.

 

If we create a new catalog the VMs are spread over all datastores set in the Hosts connection. I believe this is because the catalog contains information about the datastores to put the VMs on, am I correct?

 

My questions:

1. Can I update the existing catalog to also contain the new datastores, or do I need to create a new catalog?

2. What is the best practice in this scenario if we may add more datastores in the future?

 

Thanks for your help,

Fred

That doesn't sound like the correct behaviour. New machines should use the new datastores as well, adding machines should cause the base disk to replicate to the new storage.

 

Mark.

[USB Foot Pedal wont work]

As I understand it that should be all you need. I think you need someone with a better idea of how the USB Redirection currently works to assist.

Mark.

[USB Foot Pedal wont work]

Footpedals are usually some form of Human Interface Device (HID), possibly even pretending to be keyboards. HID devices are denied by default as remoting your USB keyboard or mouse would be quite disastrous. To get this to work you will need to add explicit ALLOW rules into both the client and server USB policies. How to do this is in the product documentation.

Mark.