Anyone using Image Portability Service? If so, are...
# citrix-provisioning
n
Anyone using Image Portability Service? If so, are you able to list multiple cloud connectors in the Prepare script? I have tried every combination I can think of, and the script errors out every single time unless I list a single controller. Example:
Copy code
$Controllers = "cc1.site.com,cc2.site.com,cc3.site.com"
$PrepareParams = @{
     XdReconfigure = @(
          [pscustomobject]@{
               ParameterName = 'controllers'
               ParameterValue = $Controllers
          }
     )
}
This is required for some reason, and it's the last hurdle for us to get a functional image. Save me, @Rob Zylowski.
j
I've successfully set it up a few times, I had a fair share of issues but not this one. I'll see if I still have access to the env to check the prepare script. That said, can you not just inject the required controllers/connectors with a GPO bound to the OU containing the image? cheers
n
We do use GPO to set these, but given how much of a clusterfuck our environment is, I don't trust it entirely. I'd like to be able to add all three controllers, just in case. I honestly have no idea why this is a requirement, because it's dumb.
j
Try not storing in a variable. We just have them listed and it runs ok..
n
I've tried that, too - same error/failure/
j
Weird, this works for us (VMware to AWS)
n
I'll run it again
šŸ‘ 1
j
Whats the error you see in the prepare log? ta
n
Usually "invalid controller 'cc1.site.com cc2.site.com cc3.site.com'
Yep, just got that error using your example.
j
We did have something similar but it was due to networking / rules for controller access from the target AWS region to the local contollers..
r
Nick try escaping single quoptyes around the controllers variabel like this$Controllers = "cc1.site.com,cc2.site.com,cc3.site.com" $PrepareParams = @{ XdReconfigure = @( [pscustomobject]@{ ParameterName = 'controllers' ParameterValue = `'$Controllers`' } ) }
i think commas or spaces will actually work
n
I'll try that again, but I swear I've tested every combination, including leaving the variable with spaces instead of commas
r
commas is fine
but i think the parameters value needs the quotes in it which you wont have by just using the variable
Does it work wihtout using a variabke
n
Nope, can't add the cloud connectors in the object directly. It works when I use a single connector
r
ok then dotn bother my test above let me test a little
n
Appreciate it!
r
my prepare is running btw do you get an error?
n
Running it now. Give me a minute and I'll grab the error.
ERROR: Job 19fa50c5-aa56-499b-81be-4ce510a54607 error: Job failed at step PrepareForCreateCeVm with the error: Error validating the job parameters. See additionalInfo for details: Invalid controller ā€˜cc1.site.com cc2.site.com’,
j
Does the connector appliance in the target site/region have connectivity to the controllers/ddcs?
n
Yes. If I list a single controller, it runs just fine.
šŸ‘ 1
I guess I can try each CC and see if it works for all three, though I assume if one works they all would.
r
Ok im way past that ill let you know if mine finishes. But rioght now im just running wiht $contrllers="one,two"
n
wtf
r
but lets wait see if it actually finishes
n
This always fails in the first minute
j
Wondering if maybe the 2nd, 3rd controller has an issue with validation.
r
then ill ask you to send me your script so i can look at it
n
I can do that, just know that I'm using Azure cmdlets to grab data interactively instead of typing it out each time in the script
r
yea thats fine
n
I just PM'd you the script
That's just one example. I have tried every combination of single quotes and double quotes.
j
Another option to try is prepare the image with a single connector/ddc, boot it, manually add the others via the registry, reboot and run the citrix health check tool to ensure connectivity to all is healthy from the azure region/master image, cheers
n
Yeah, I know that's an option, but I'm not jumping through those hoops, lol
šŸ‘ 1
My script is still running, but I'm finally past the first stage, so I think we're good. In my case, the issue was that our CC appliance was very out of date, and there was a bug that affected this value. I think we're all set now.
Since upgrading the appliances to the latest build, our prep scripts all fail... lol. Ticket opened with Citrix, but this is almost comical irony.
Copy code
ERROR: Job ###### error: Job failed at step WaitForCeToCleanup with the error: Failed to setup target image. Script error: Timed out during processing while target image booted
r
What version of pvs is on your vdisks
n
Good chance that it's 2203 CU3. I'm waiting for a new image from those guys.
It was built in May of this year, so it shouldn't be older than that.
I'd be able to tell you for sure if people actually put this information in the image/layer description here...
We used this same VHD before the appliance upgrade, and it worked fine. Though I guess that doesn't matter now.
r
Were going to change it but i think we still only allow the latest two versions of each supported platform like cr and each ltsr. If not one of those it fails.
Could be something else but that is often an issue
n
If we're on 2203 CU3, wouldn't that meet the requirement? PVS is only at CU4 there
Wait, nevermind, I see CU5 out there.
r
That could be it. We are going to change that requirement very soon. Ill try to find out when
n
Hopefully the logs show that so that whoever has my ticket sees it. I'll just keep pushing to get that new image so that we can test.
I'm being told that this image does not have a PVS agent installed, just the VDA. Does this make sense, or should we be including the PVS agent?
Yeah, no PVS in this image. It has the VDA installed using the MCS switch, so this would be an MCS to MCS process.
I take it that puts the kibosh on your version theory?
r
I dont know for sure i think we just reconfigure mcs rather than unihstalling and reinstalling like pvs. Your error though is that the prepare machine never finsihes rebooting back into the ce so its getting stuck for some reason
MCS to MCS will only reconfigure controllers
So youre aving some other issue
n
Okay. Should have a new image to test soon, but I guess I'll see what comes of this ticket.
Joell is also having the issue, so it's not isolated to me or my machine.
Tried prepping a newly compiled S16 image, and that also failed. Same type of error (timed out), but different stage. Hopefully development can see something on their end, because we're now dead in the water with this.