Working on a new ask for a customer, and wonder if...
# citrix-provisioningj
Jeff Riechers
06/17/2024, 11:31 PMWorking on a new ask for a customer, and wonder if anyone has done something similar. Looking to use IPS to convert an on-premise vdisk setup for vmware that has been replicated to an azure PVS server to be used by machines running in Azure. Customer is 100% on-prem and looking to stay that way. Anyone have a good rundown on how to use Image Portability Service to make the necessary changes to the vdisk in Azure to make it bootable
r
Ray Davis
06/18/2024, 12:28 AMI went from pvs on Prem to azure via mcs. Did it once.
Being it was Pvs on Prem, it was already in a VHDX state so the rest was injecting parts for azure that’s needed for the upload script parts. Doesn’t sound the same though for you
b
Benjamin Crill
06/18/2024, 12:33 AMThey want to stay on prem yet make the image available in azure?
⤴️ 1
r
Rob Zylowski
06/18/2024, 2:31 AMWhats your question that is what IPS was developed for. You use a poweshell upload script then the prepareandpublish script to convert the vdisk and put it in the store. I wrote a script to automate migrating all vdisks to azure https://community.citrix.com/citrix-community-articles/pvs-disk-migration-automation-r616/
❤️ 1
j
Jeff Riechers
06/18/2024, 10:15 AMThey are a large on-prem customers, not looking to move anything to Citrix cloud. Azure will just become a third data center so if 1 of the other 2 go down it will provide that overflow. I'll check out your article Rob, I opened up the IPS module and started digging through the powershell modules looking specifically for the one to inject the Azure networking info into the vhdx image either before or after it was replicated to the PVS store.
r
Rob Zylowski
06/18/2024, 12:44 PMwhat its doing is reinstalling the pvs dvice drivers during the prepare phase of the process
j
Jeff Riechers
06/18/2024, 12:49 PMSo I am just wondering if there is a process to call just the device driver process. No copying of images, no registering in Citrix Cloud. Just strip it down to just the process of modifying the vdhx with the Azure components to allow boot. The PVS images will be controlled 100% from an onpremise CVAD farm, but the PVS will live in Azure.
r
Rob Zylowski
06/18/2024, 12:54 PMno this requires a kind of significant process where we are reinstalling pvs is a differnetn install in azure
j
Jeff Riechers
06/25/2024, 2:34 PMThanks Rob. Once I got all my authentication sorted and got to testing this I am at a road block. The script is working fine with the cloning the image up to Azure, but then when it starts the prep section it fails. I wrote a very simple Prep script of my my work and it just seems to hang at booting the machine after it gets it all setup. Can I send you my logs from running your awesome scripts and you point me in the right direction? These were the last items listed in the logs, but I can backtrack to what is missing or wrong in my setup.
Jeff Riechers
06/25/2024, 2:34 PM2024-06-25T120502.1905Z: Failed to start prepareAndPublish: Post REST method failed: {"type":"invalidData","detail":"Errors were found in the input data. See the parameters for specific errors.","parameters":[{"name":"outputStorageLocation.location","value":"This field is required. Ensure that it is not missing or empty."}]}
2024-06-25T120502.1905Z: Workflow failed: Failed to start prepareAndPublish: Post REST method failed: {"type":"invalidData","detail":"Errors were found in the input data. See the parameters for specific errors.","parameters":[{"name":"outputStorageLocation.location","value":"This field is required. Ensure that it is not missing or empty."}]}
2024-06-25T120502.1905Z: New log
2024-06-25T120502.2062Z: Wait-IpsJob called with params: @{ErrorAction=, Output=False, Verbose=False, PollSeconds=60, OutVariable=, LogFileName=2308PVS-Job-log.txt, InformationAction=, WarningVariable=, Debug=, CustomerId=CDWCorporati, PipelineVariable=, OverwriteLog=False, SecureSecret=, OutBuffer=, Deployment=, LogFileDir=C:\temp\ips\Logs, ErrorVariable=, SecureClientId=, WarningAction=, JobId=Job failed to start, InformationVariable=} from Powershell 5.1.20348.2400
2024-06-25T120502.2062Z: Citrix.Workloads.Portability version 2.4.1 from C:\Program Files\WindowsPowerShell\Modules\Citrix.Workloads.Portability\2.4.1\Citrix.Workloads.Portability.psm1
r
Rob Zylowski
06/25/2024, 3:42 PMHey Jeff download again. They changed the underlying powershell and i had to update the script. Its dtill not perfect hhe reporting at ghe end is broken for success snd failure but the migrations should work now
👍 1
j
Jeff Riechers
06/25/2024, 3:43 PMI was thinking it was me having 2402 on everything, so I downgraded to 2308 same thing. Let me test it out and get back to you. Thanks for your hard work on this.
Jeff Riechers
06/25/2024, 3:52 PMAlready further than it was before. Thanks man!
Jeff Riechers
06/25/2024, 6:28 PMIt said it errored out, but the logs said I had a disk. Success!!
r
Rob Zylowski
06/25/2024, 7:29 PMyep still working on how to catalog success. Its a little hard due to the parallel processing. I think im going to get it fmo the prepareandpublish logs, then write to a csv and use the csv to report.
Rob Zylowski
06/25/2024, 7:29 PMLet me know if you have reocmmendations for changes
j
Jeff Riechers
06/25/2024, 7:30 PMI have a pretty big client that I will be leveraging this with. So thanks for the hardwork!
r
Rob Zylowski
06/25/2024, 7:32 PMglad to help
Rob Zylowski
06/30/2024, 6:19 PM@Jeff Riechers Here is a new version that fixes skipping migrated vdisks and logging success and failure. Let me know if you have any questions.
👍 1
2 Views