Hello – We installed XenDesktop 5 – We created a Catalog for machine type streamed to use our existing Provisioning server 5.6 deployment. When we try to add the existing machines to the catalog it fails.

# Add machines to a streamed desktop Catalog
#
# This script add machines into a streamed desktop Catalog
# 12/12/2010 9:25 AM
#
Set-PvsConnection -server '172.17.101.40' -port 54321 -domain 'mydomain.com’

Get-PvsVersion

Get-SimplePvsCollection -collectionId @('a57e4996-a174-4cda-b2c8-a39b87db3afe')

Get-SimplePvsDevice -collectionId @('a57e4996-a174-4cda-b2c8-a39b87db3afe')

Get-SimplePvsADAccount -domain 'mydomain.com’-name 'xp01'
# Get-SimplePvsADAccount : The server is not operational.
#
# + CategoryInfo : ObjectNotFound: (:) [Get-SimplePvsADAccount], COMException
# + FullyQualifiedErrorId : Citrix.PVS.PowerShell.Commands.GetPvsADAccountCommand
# Get-SimplePvsADAccount : The server is not operational.
#
# + CategoryInfo : ObjectNotFound: (:) [Get-SimplePvsADAccount], COMException
# + FullyQualifiedErrorId : Citrix.PVS.PowerShell.Commands.GetPvsADAccountCommand
# Script failed

Not very familiar with Powerscript – Maybe something simple.

Additional information – The provisioning server is currently being used by our production XenDesktop 4 deployment – Works great

XenDesktop 5 and Provisioning server 5.6 are running on Windows 2008 R2 VM’s 64 bit
XenServer 5.6 are the hosts being used – There are two host – These are the same host being used in our production deployment of 50 XenDesktops
We tried several things – Created new target devices – New device collection – Verified AD account information – No active directory replication error – DNS verified.
We can successfully create a new and existing catalog and use the existing VM’s on the XenServer.
Anything new works great – We just can’t seem to add machines from our exsisting Provisioning server
Thank you for your help.

Is you controller in the same domain as your PVS server? (This is an XD5 requirement).

I have the issue and yes ddc in the same domain as PVS

Edited by: Sergey Mikhalchenko on Dec 15, 2010 8:55 AM

I've got the same problem. It seems to be an error finding the correct domain. If I change the domain name from 'Kreis-Soest.intern' to the Netbios Name 'i200d01' the power shell script run. But unfortuanally i cannot change the domain name in the Add Catalog Funktion to the Netbios Name.Only the DNS Name ist in the pull down field.

New-BrokerCatalog -AllocationType 'Random' -CatalogKind 'Pvs' -Description 'dummy' -MachinesArePhysical $False -Name 'dummy' -PvsAddress '10.48.192.94' -PvsDomain 'Kreis-Soest.intern' -AdminAddress 'I200D01S126.Kreis-Soest.intern:80'

Set-PvsConnection -server '10.48.192.94' -port 54321 -domain 'Kreis-Soest.intern'

Get-PvsVersion

Get-SimplePvsCollection -collectionId @('d4adeaaf-3eac-461a-b03b-98d3ad5026e8')

Get-SimplePvsDevice -collectionId @('d4adeaaf-3eac-461a-b03b-98d3ad5026e8')

Get-SimplePvsADAccount -domain 'Kreis-Soest.intern' -name 'win7master'
# Get-SimplePvsADAccount : Der Server ist nicht funktionstüchtig.

#
# + CategoryInfo : ObjectNotFound: (:) [Get-SimplePvsADAccount], COMException
# + FullyQualifiedErrorId : Citrix.PVS.PowerShell.Commands.GetPvsADAccountCommand
# Get-SimplePvsADAccount : Der Server ist nicht funktionstüchtig.

#
# + CategoryInfo : ObjectNotFound: (:) [Get-SimplePvsADAccount], COMException
# + FullyQualifiedErrorId : Citrix.PVS.PowerShell.Commands.GetPvsADAccountCommand
# Script failed

PS > Get-SimplePvsADAccount -domain 'i200d01' -name 'win7master'

Domain Name Sid DomainController
------ ---- --- ----------------
i200d01 win7master S-1-5-21-1182950876-1552108062-93...

Greetings
Olaf

I have the same problem. Thanks for posting the lead on the FQDN versus the netbios name of the domain being the source of the issue. In my environment, the netbios name is completely different than the FQDN of the domain. Most AD domains are named like "domain.local" with "domain" as the netbios name. In my case, the netbios name is not a subset of the FQDN. Don't know if that makes any difference. Anyone been able to find the full powershell script somewhere? I think we could just run this script via powershell with edits in the Desktop Studio tab if we had the whole script. It seems like all I can get from the error details is the script only up to the error.

This error has halted my migration to XD5 from XD4. Hope they fix this bug soon or come up with a workaround.

I'm having the same error when there are no machine accounts created in the AD. When I create the accounts using the Provisioning Services console everything works out fine.

I already have machine accounts created for all the machines on my provisioning server. I am actively using them in XD4. I just cannot import them into the XD5 catalog because the powershell script that runs behind the scenes uses the FQDN and not the netbios name of the domain.

Below is what the powershell looks like for the command that is failing within Desktop Studio. I have changed the name of the domain for security reasons. So, let's say that in my enviroment "domaincu_nt "is the netbios name and "domain.org" is the FQDN of the domain. The script built into Desktop Studio for importing streamed devices into the catalog uses the FQDN, which gives an error when the command is run. If I alter the command to be the netbios name instead, I get a successful result, as was discussed earlier in this thread.

USING NETBIOS NAME

PS C:\Windows\system32> Get-SimplePvsADAccount -domain 'domaincu_nt' -name 'Desktop1'

Domain Name Sid DomainController
domaincu_nt Desktop1 S-1-5-21-2066839...

USING FQDN NAME

PS C:\Windows\system32> Get-SimplePvsADAccount -domain 'domain.org' -name 'Desktop 1'
Get-SimplePvsADAccount : The server is not operational.
At line:1 char:23
+ Get-SimplePvsADAccount <<<< -domain 'domain.org' -name 'Desktop1'
+ CategoryInfo : ObjectNotFound: (:) [Get-SimplePvsADAccount], COMException
+ FullyQualifiedErrorId : Citrix.PVS.PowerShell.Commands.GetPvsADAccountCommand

Edited by: WILLIAM DANIELS on Jan 1, 2011 1:17 PM

I am having the exact same issue. I can access the command using the netbios domain name but not the FQDN. how can I get past this?

Unfortunately, there is no known workaround for this issue at the moment unless you can rename your domain appropriately. If you have a support contract, please raise it via that route.

This needs to be fixed please.

Citrix needs to fix this. I am not going to change my NETBIOS Domain Name of AD just because Citrix cannot fix their powershell script. That's just not going to get approved.

Hi All,

I am in exactly the same boat, or at least I was.

Not being able to deploy 600+ Desktops because of this was not an option and I think I have a work around for you all.

I inititally thought it was an XD 5 issue (and it might be still) but I have been working on a solution across two companies and for some strange reason it seemed to work at one company and not the other, so I have battled most of the night and come up with the following.

Caveat, no responsibility etc.. and can someone please test and post your results.

First off I am making an assumption that you are using XD 4 and are standing up an XD 5 environment in parallel.
Make sure you install the latest XenDesktop Setup Wizard (for XD4 only) on the PvS Server, I am using XDE400SWX64001 for this.
Create the desktops as normal adding them to a new Collection in PvS 5.6 SP1 and a new XD 4 Desktop Group.

Go into the XD 4 Desktop Group and set the Idle Pool to 0 and shut down any machines that have started and adjust Users as necessary. It doesn't matter we are going to delete the Desktop Group soon anyway.

After making sure that no machines are running in the new Desktop Group go into Desktop Studio and add a Streamed Catalog as you would normally.

Delete the Desktop Group from XD 4.

I found that it worked!

If it doesn't, create the Collection in PvS manually and add the Desktops to it using the XenDesktop Seyup Wizard rather than creating a new Collection. I am not sure if it was the Collection that was causing the issues or the older version of XenDesktop Setup Wizard.

Hope that helps someone

Cheers
Grant

Hi all,
i have done this with the lmhost file (at the DDC V5).

1.2.3.4 TheDomain <00> #PRE

take a look at
http://support.microsoft.com/kb/314108
this works for me

Dirk, I'd be interested to know your set-up where that worked. I thought that might be a way round it - but whatever I try doesn't work. I even dusted off a WINS server and tried using that. Did you have both IPv6 and IPv4 enabled? Do you have multiple NICs?

I also tried using powershell to change the domain value on the catalogue - however when you then try and go and add machines using the GUI the first set of steps resets the domain back to the non-working one. :X

Philip, I think if you consider what it is you're asking you'd realise that its just not practical to implement such a major change: and more importantly the question was "what is the code that is missing" - if we'd had that its possible to workaround the problem. However, luckily I've got a spare domain where this isn't an issue - so I could set up another* PVS server, and *another XD5 environment and then found that the full script is:

#create the catolog - which likely has already been done..
New-BrokerCatalog -AllocationType 'Random' -CatalogKind 'Pvs' -MachinesArePhysical $False -Name 'Test' -PvsAddress '192.168.0.3' -PvsDomain 'dev.local' -AdminAddress 'WIN-LAR4QSB1OHV.dev.local:80'

#get the information about the PVS server
Set-PvsConnection -server '192.168.0.3' -port 54321 -domain 'dev.local'
Get-PvsVersion

#find out about teh devices in the appropriate collection
Get-SimplePvsCollection -collectionId @('b225c46a-1f51-4962-a94f-a07b0c6d015d')
Get-SimplePvsDevice -collectionId @('b225c46a-1f51-4962-a94f-a07b0c6d015d')

#Here's where the script fails if the netbios name doesn't match the start of the dotted domain name
Get-SimplePvsADAccount -domain 'dev.local' -name 'PRVXP3D2'
Get-SimplePvsADAccount -domain 'dev.local' -name 'PRVXP3D3'

#here's the missing pieces to the puzzle:

# get the mac address of the host
Get-HypVMMacAddress -LiteralPath 'xdhyp:\connections\Xen3' -AdminAddress 'win-lar4qsb1ohv.dev.local'

#get the full details of each of the machines that is being brokered
Get-BrokerMachine -SID 'S-1-5-21-1057035504-2046278662-1236480638-1108' -MaxRecordCount 2147483647
Get-BrokerMachine -SID 'S-1-5-21-1057035504-2046278662-1236480638-1109' -MaxRecordCount 2147483647

#by now you've got all the information you need - run New-BrokerMachine for each device.
New-BrokerMachine -CatalogUid 1 -HostedMachineId '70b40948-7ebf-a1c4-f856-f2fe9cbcfe6f' -HypervisorConnectionUid 1 -MachineName 'S-1-5-21-1057035504-2046278662-1236480638-1108' -AdminAddress 'WIN-LAR4QSB1OHV.dev.local:80'

New-BrokerMachine -CatalogUid 1 -HostedMachineId 'b65e1111-a404-0132-a820-3916556c5210' -HypervisorConnectionUid 1 -MachineName 'S-1-5-21-1057035504-2046278662-1236480638-1109' -AdminAddress 'WIN-LAR4QSB1OHV.dev.local:80'

So.. change to suit as needed for your environment and rather than use the GUI to add machines, use powershell. Its a pity that the method of learning about powershell appears to be based on reading the scripts - because if the scripts fail you've nowhere to go.

..and if you need to determine the HypervisorConnectionUid run Get-BrokerHypervisorConnection -Name [name of your HV connection]

So has anybody found a full fix for this yet? I tried the LMHOSTS trick but that didn't work for me. I'll try manually inputting the powershell next but that obviously just a cumbersome work around and not a solution.

Nearly 2 months later, I can't believe they haven't released a hot fix for what amounts to a simple powershell script issue. I couldn't follow the steps in the "workaround" post on page 1, so we're kind of sitting dead in the water at the moment.

In all fairness John, you are not dead in the water. It is solvable with a modification to the powershell script. If you look back in the thread the script steps have been explained. It'd take you about .5/1 day to sort to it for your environment

Granted, that's not great. Granted its an extremely poor turnaround on Citrix's behalf given this is a likely scenario for a number of organisations. Granted you'll have to delve into powershell - but frankly XD5's interface is so cumbersome learning powershell is going to save you a great deal of time and effort.

There is apparently a hotfix available for this (CPR 254234). But you have to subscribe to Citrix Support, which is of course, chargeable.

Some additional information on the issue. Looks like it will be released as a fix for the PVS Powershell SDK

http://forums.citrix.com/message.jspa?messageID=1533868

When is the question. I am trying to get more information on this.

Bill