Jump to content
Welcome to our new Citrix community!
  • How I Upgraded My Site From 7.15 Flat All the Way to 1912


    cugcblogs

    raydavis22rnd-1.jpg by Ray Davis

    This is a guide on how I upgraded my site from 7.15 flat all the way to 1912. I also included moving off 2012R2 to 2016 DDCs with some troubleshooting situations you might run into. I covered the basics of upgrading Licensing, DDC upgrades, Storefront upgrades with NS VIP configuration, PVS upgrades, WEM upgrades, VDA upgrades, and some re-configuration of Snap-ins with Director for ADM and session recording.

    1. References for detailed instructions
    2. https://docs.citrix.com/en-us/citrix-virtual-apps-desktops/upgrade-migrate/upgrade.html
    3. https://www.carlstalhood.com/delivery-controller-1912-ltsr-and-licensing/#licensingupgrade
    davis090820-01.png.87aa85f9e294bc8e273f3c3c22b6ea0e.png
    • Upgrade the licensing Server
    • Go download the version you need. In this case, its 11.16.3.0 Build 29000
    davis090820-02.png.2c10435d88909dddf54ac7eac38cf37c.png

    Run the CTX_licensing installer

    davis090820-03.png.b9d81490fa4e5670e9e87d351dcbe825.png

    Check the box to agree

    davis090820-04.png.53580d2a3d7ff2e97ecf51ff5b5a7424.pngdavis090820-05.png.e13db9d0e9c0527f34c496d981bd44ba.pngdavis090820-06.png.c0f5ec6d66534abdeba819bbdb4469c9.pngdavis090820-07.png.fc70c539e1795ee6ce1060310c2a3896.pngdavis090820-08.png.6e8dd71cb553b015244dc65013f2abe9.pngdavis090820-09.png.44d43e41c92fa3d69b660cf099f61fbb.png
    • After upgrading Citrix Licensing Server, in Citrix Studio, go to Configuration and Licensing.
    • On the right, click Authenticate Certificate.
    davis090820-10.png.2a0a9afaf25ec21dc04801c9c7302206.pngdavis090820-11.png.0b221d3987fdf2b5152239637661bdf5.png

    Open Citrix licensing Manager

    davis090820-12.png.4c4717a09e12f256f66c8ddcf80ce192.png
    • I was prompted to register my licensing server with Citrix Cloud.
    • Licensing Manager might prompt you to register with Citrix Cloud.
    davis090820-13.png.fe72a9c49808a15a95e63e6eaaba1b1e.png

    On the Settings > Usage and Statistics page, in the Share usage statistics with Citrix section, click Register.

    davis090820-14.png.a2384864e77961db4d532854665da214.png

    You’ll see a screen with a registration code. Click the Copy button and then click Register to be taken to Citrix Cloud.

    davis090810-15.png.423fd10f76740f48e97758331bf8fec0.png

    After logging in to Citrix Cloud, on the top left, click the menu (hamburger) icon and then click License & Usage. If you don’t see this link, you might have to logout and log back in.

    davis090820-16.png.168c418bfb2eb3319edc718dadffbc3a.png

    In the License & Usage service, switch to the Registrations tab.

    davis090820-17.png.0c329276aa98646ebe3183f5bb1010ba.png

    Click the blue Register button in the middle of the page to register.

    davis090820-18.png.cf82afd42ba5c6719ed906bd814ac037.png

    Paste in the copied code and then click Continue. Click Register.

    davis090820-19.png.4ae8ee88efc7eee015d457fbfb0076fc.pngdavis090820-20.png.61732c8672a19eeaa1374c48ba87edef.png
    • On-premises Licensing Manager, it will eventually show as Registered.
    • On the same Usage & Statistics page, scroll down, and then click Upload now. This should cause data to upload to Citrix Cloud and show up in Citrix Cloud License & Usage.
    • Citrix.cloud.com reporting
    davis090820-21.png.a04353d497d9d8d2b79bd4bb3a81fbca.pngdavis090820-22.png.be8a0a0c00a1e1c6995c0b7dbe0594d0.png
    • *Note* For me, I always check and make sure it shows activated within Studio and is set to the right product edition
    • Upgrade VDA to 1912
    • I also upgrade my VDAs ahead of time. It’s easy and something I just do.
    • Depending on your provision side. PVS, MCS or old fashion servers( which is still used)
    • Mount ISO and upgrade
    davis090820-23.png.cbe5e28689605076276c32bf3d40886f.pngdavis090820-24.png.ccc2bddc349bad202c6156a4ef72c7bb.pngdavis090820-25.png.e65d6b67a9f8a3d5a6d02e04f533d3b7.pngdavis090820-26.png.9bb1a2e926262fa2cde9be6724da2500.pngdavis090820-27.png.7cc3cf0776609473b1d6f8c662612aa5.pngdavis090820-28.png.7c6c7c7d707fd6e0db10926977acc636.pngdavis090820-29.png.d63d4d8ed4cc9bc89c6d7012e07a6756.png
    • Upgrade Delivery Controllers 7.15.5000
    • Snapshot your Delivery controller
    • Backup your SQL databases
    •  Attach the 7.15 CU5 media
    • Run the Studio and Server Components for the upgrade
    davis090820-30.png.fd3fe049547728f02befa3028408b5cf.png

    Read and Accept

    davis090820-31.png.92ff01b8f1834b2894298d26376cf8ac.png

    Read and make sure you take the correct actions you need in your environment.

    davis090820-32.png.16e48650699e3187990d25c272dc4e58.png

    Start your Preliminary Test and make sure you are good!

    davis090820-33.png.05ec4aba5d42208bbd26e138e1d9196d.pngdavis090820-34.png.39bf36ae20ad8af411bbc5eb4916f357.png

    Firewall Ports

    davis090820-35.png.532c83820547e4c674079df327681d70.png

    Summary

    davis090820-36.png.7edc82b3f2ca2b0326c5f153d3074a28.pngdavis090820-37.png.ed876c3dfe9282ae1d21e873908ea799.png

    Upgraded process started.

    davis090820-38.png.8d7f5796faf40d2f2131de95e9a89a46.pngdavis090820-39.png.1949621b87e1b0c64dd6c2ffe4269001.pngdavis090820-40.png.59950bbda37861a5c1aed7ba5545c4a2.pngdavis090820-41.png.91129edad679ead2e1a1d29c1d08cddd.pngdavis090820-42.png.692011cfdaa0f5c13a748b1465a26a92.pngdavis090820-43.png.1b23467e1c326a15b29cba852de96a70.pngdavis090820-44.png.99a424f944c6cf2414844b567cac8dd2.png

    Connect to Call home if you need to.

    davis090820-45.png.a644373293d95fd6a866474452341a34.png

    13 Launch Studio

    davis090820-46.png.a4f4cb52217a3e98fcb04d5e6443731b.pngdavis090820-47.png.5b6410d3a16870c8f305691513130edb.pngdavis090820-48.png.daa74c511b30fe916182a5e7d35dd7f6.pngdavis090820-49.png.c537c0b078e77d54c738fe1dec13b2de.pngdavis090820-50.png.238fbeb85b1cad1b5cf6068f1c34fec4.pngdavis090820-51.png.59b2025bba0b97a23c342febdaea7964.png
    • **NOTE**
    • “If you already have 2 controllers then In Load Balancing, reactivate the servers with the new Delivery Controller version and set the second half of the servers to Down. Follow the top steps on the second half of the Delivery Controller Server Activate each server with the new Delivery Controller Server version in Load Balancing again.”
    • 14. For me I am adding a 2016 server to move off 2012R2. I will add the Second 2016 server in, then make sure the 2016 is handling the connections. Then Decom 2012R2 and add a new second (replacement of 2012R2 as 2016 server.
    • 15. Attach the 7.15.5000 ISO, click on XenDesktop or XenApp (depends on your deployment)
    • 16. XenDesktop allows for both XenApp and XenDesktop. XenApp is only XenApp.
    davis090820-52.png.d9e804d212e6c994c5dcc80015408d47.png

    Select Delivery Controller

    davis090820-53.png.a1b094439e5d15a366cf7ad36c1ce5a9.png

    Read and Understand, accept.

    davis090820-54.png.71e55df07146f99be23a62a4930be70c.png

    We only want, Delivery Controller, Studio and Director.

    davis090820-55.png.782932f009bb8d0c25dd1d3bbed351d0.png

    I don’t want SQL express in the step, Uncheck it.

    davis090820-56.png.c11fe9f0472fbaf61ac28c649e02bf87.png

    Review and make sure firewall is configured based on your environment.

    davis090820-57.png.41277fae23d6146b209403c6706edb22.png

    Installs

    davis090820-58.png.f0f3dbef04fe291073e2532d6de48409.png

    This will take about 5-7 minutes.

    davis090820-59.png.a999b13c805a22b1a1d439257b1d80ed.png

    Select call home options.

    davis090820-60.png.b07649c3a7b19449393e823b564ccedc.png

    Finish, reboot and then launch Studio.

    davis090820-61.png.fb735976bf9533f31d37646d629916bd.png

    After Studio is opened, select “Connect this Delivery controller to an existing site”

    davis090820-62.png.bd274faad013dca74467221e7628d03d.png

    Add the primary DDC.

    davis090820-63.png.505341a44498e926eb86d390726dca95.png

    It will ask to update the DB automatically, I select yes and will put in my SQL creds.

    davis090820-64.png.d08dcfa9272d6ad688f739495040afbd.pngdavis090820-65.png.aadba0909d86ddbbb60c8828de3b0005.pngdavis090820-66.png.f29534327507d64f852d8622028388ca.png

    Studio will open and show the Site.

    davis090820-67.png.8da7ed01ccce54da3e55a92cb1ae0e8b.png

    Run a Site check to make sure it’s good.

    davis090820-68.png.89563b476df19e6efe74470aae722296.png

    This will take 10 minutes.

    davis090820-69.png.82ca8aaf7ab827c931501ceff135ba61.png

    Looks good.

    davis090820-70.png.ecf6d2626d5c99447ea4d83c0e8798aa.png
    1. At this point I have the following:
    1. 2012R2 715.5000 Deliver Controller
    2. 2016 7.15.5000 Delivery Controller.
    3. Bother are upgraded from 7.15 to 7.15.500
    davis090820-71.png.91130de610c1d2de8371ef3be9c7d4a1.png
    • Now we will begin the 7.15.500 upgrade to 1912 LTSR.
    • Snapshot your Delivery controller
    • Backup your SQL databases
    •  Attach the 1912 media
    • Run the Studio and Server Components for the upgrade
    davis090820-72.png.4838e1d860164ae4570b181a63eb9fd3.png

    Read and accept.

    davis090820-73.png.cc9c7c8e98b514dccf4d57e5299a8725.png

    Make sure the following has been completed to ensure a upgrade will go smooth.

    davis090820-74.png.eb0b61dafdf86ca6db68b4b99c9719f3.png

    Licensing Error I received when I clicked next. Even though I upgraded my licensing version to 11.16.3.0 build 29000,I had to update my licensing files past November 2019. I logged into my Citrix Licensing manager. Https://yourCTXlicServer.FQDN:8083, then selected check for available renewals. Follow the prompts to get an updated timestamp.

    davis090820-75.png.c61c8ea77a0217a41b912cd305e0a252.png

    Before:

    davis090820-76.png.82d6c0948ba6ac677026ff54c40569ef.png

    After:

    davis090820-77.png.4c776c2a7a46892c6e57405fcddbdc69.png

    This is not production; my specs are lower than what it wants. However, I will meet the minimum to ensure the upgrade is solid.

    davis090820-78.png.fa54e7f8ad9f8de3418b672c78d1f073.pngdavis090820-79.png.8fb16e4c3d0a9752ac2eb6d6df0196f8.png

    Let's pick back up where I left off. Preliminary Site Test (Run this to ensure no errors exist).

    davis090820-80.png.8ef7ce002c1c3438dddc653f57ce971a.png

    Test in progress.

    davis090820-81.png.697f007c3958e0031c0abce07573ec06.png

    Two tests will not run, as they don’t apply.

    davis090820-82.png.08d591537b8f13fbc30c8ebf17ddbadb.png

    Results go through and test all the orchestrations of the environment.

    davis090820-83.png.58830433780ee778629356785a86e3e2.png

    Firewall ports.

    davis090820-84.png.1aa51dbea32fc4963afc3f56217617d2.png

    Summary, then click upgrade.

    davis090820-85.png.792fe0f78388c5b4d0fd046e27512f15.pngdavis090820-86.png.646979e6ff40faa2f55200f83731257c.png

    Upgrade progress.

    davis090820-87.png.cf9841ff991ecf33b3afc265e740a7b0.pngdavis090820-88.png.0795bd93e824b571ef014a0804b69680.png

    Upgraded, but Reboot needed.

    davis090820-89.png.cb671610c12f61177abfd0049a7bd518.pngdavis090820-90.png.9cde23baf18e882e68cae5f7676c0054.png

    After Reboot it will resume. Now on Post Install….

    davis090820-91.png.5499373b1368e9ca110dcfa9dd01b461.png

    Connect to Citrix Cloud for Diagnostics data if needed in your environment.

    davis090820-92.png.ce1354a3399fdb3a0f0170c76a5e6472.png

    Finished and now open Studio.

    davis090820-93.png.66f4f2d971612ed106de6f384897d37a.png

    Now upgrade the Database through Studio (my service account has permissions).

    davis090820-94.png.9d8cbc10c369f223089bf8c834ecb81c.png

    It will ask you again, about backing up the DB.

    davis090820-95.png.723bc7486e96e7d0436b2a1d90edef7a.png

    Add the Creds, unless you are logged into the server as the account (Account needs proper permissions, in Citrix, and on the servers).

    davis090820-96.png.2a72d013659fedf59ee3079154186e53.png

    It’s now started.

    davis090820-97.png.9d13404fc9cf4c78718fe066a24a59d6.png

    Going, 9 successful… GOOOD so far.

    davis090820-98.png.05c674e1d5a44aa7e412a07560078f6b.png

    Still going well.

    davis090820-99.png.c7ee0974a085074c5d41f586844c8c1e.png

    Finished.

    davis090820-100.png.5d767b4f91833e46b41c19ec0323093f.png

    You now need to do the second Delivery controller we added early in the process. It’s the 2016 server.

    davis090820-101.png.d9e636aebe791ab7bc0cc64c46279d47.png

    Remote to the Server, Attach the Media, and I double click on the mounted ISO from my hypervisor.

    davis090820-102.png.a2f3f7965f0527441b349856e2150a65.png

    Click Upgrade on Studio and Server components.

    davis090820-103.png.041fcddcbab3d6e7b7df869b051ee376.png

    Read and Agree.

    davis090820-104.png.10e9847e6f600a62be2840e6368bc8aa.png

    Ensure the following is completed, although it’s a second DDC.

    davis090820-105.png.61bb204d4e8dc90d92279b454bdb254d.png

    Firewall for DDC and Director.

    davis090820-106.png.5e2fab356c0f5dc5b4c6753811362413.png

    Summary.

    davis090820-107.png.59d98eae2cf85ac70c93b4c772de1694.png

    Warning pop up about not being able to stop it once it starts.

    davis090820-108.png.d4755f054d1e3b863ba36747fb31a2c7.png

    Upgrading has started ( The Time says 13 minutes) Sometimes it's accurate, or not accurate.

    davis090820-109.png.02149a9af330690636bb398e10924c25.png

    Machine needs to be rebooted to apply some .Net settings/updates.

    davis090820-110.png.0eab2113919735798e7b1a9aa34f06ef.pngdavis090820-111.png.3b02d03e76e4e48ca6a08ae4c0d9cfe1.pngdavis090820-112.png.859e0fee9cf12c7b781232c5b074dcf2.png

    Rebooted, and now it’s still applying them.

    davis090820-113.png.0577d96de34a86475803d3710bed2db6.png

    Log back in, and it will resume back to the place it was at. Be patient!

    davis090820-114.png.626659cbceae7190cae6bd3450752909.pngdavis090820-115.png.4d95ebf26f8ceaa51735cbd7ed1580f0.png

    Connect to Citrix Cloud for Diagnostics data if needed in your environment.

    davis090820-116.png.69d2c081e5c6935015f856f8dc70f646.pngdavis090820-117.png.ac92a426a265a39bda57c1f8443c6368.png

    Now launch Studio.

    davis090820-118.png.e6956d2243ecafb3b58847ea1f2ae413.png

    Start the automatic site upgrade.

    davis090820-119.png.a22dc2637862abb524b0ed0d82f0bc3e.png

    Since this has already run, it shouldn’t take long.

    davis090820-120.png.193ca50a4102af2f4279d7d451f9e3b5.png

    Studio is now launched.

    davis090820-121.png.8c93e301c51792e068d7a39f73977507.png

    Let's do a site test on the Delivery controller.

    davis090820-122.png.f3e63b63e479f0cae395511eca59744a.png

    Things passed, and look good.

    davis090820-123.png.a59e51424387f5a65e3a108d9d2e73d0.png
    • Let’s do a Machine Catalog and Delivery group test. (Failed)?!! Looks like my Delivery controllers don't have the updated vcenter cert. Let me fix this. I simulated a failure to show the value of running the tests.
    • I fixed my cert by following this: https://support.citrix.com/article/CTX138640
    davis090820-124.png.451eb72e8a65e9509b8b1030978f0a28.png

    Now once both had updated 1912 Software, go into the first Delivery Controller and finish the “upgrade remaining delivery Controllers”

    davis090820-125.png.142a4292c70ed47e2d92f565a8111111.png
    • Once all the Delivery Controllers and VDAs are upgraded, within Citrix Studio, view your Catalog for the current functional level (Set to VDA version you have in the catalogs). Citrix Virtual Apps and Desktops (CVAD) 1912 lets you upgrade your Catalogs and Delivery Groups to functional level 1811 if needed.
    • **WARNING****Don’t upgrade the Catalog or Delivery Group until all VDAs with the Catalog and Delivery Group are VDA version 1811 or newer.
    davis090820-126.png.c1825e4794def6d6470b37c686cf2f47.pngdavis090820-127.png.63390039d24d2361eec299e74643d47e.png

    Then upgrade the Delivery Groups by right-clicking on a Delivery Group and clicking Upgrade Delivery Group.

    davis090820-128.png.49ef6b59aa8025fa4489c4f20c16d33f.pngdavis090820-129.png.fe15b58ea55480b6e699963690fdb098.png
    • This concludes the upgrade for the Delivery controller.
    • Now let’s Decom one Delivery controller, that is 2012R2.
    • *Note* https://discussions.citrix.com/topic/388816-decommission-delivery-controller/
    • https://docs.citrix.com/en-us/citrix-virtual-apps-desktops/manage-deployment/delivery-controllers.html
    • Active connections should not be dropped if you remove a delivery controller from the site. Remove the controllers from Storefront first, then from studio. Any VDAs registered to the controller should re-register with the remaining controllers, however this may take a few minutes, so a resource that hasn't registered yet might be unavailable for a relatively short time.
    • You could also stop the Broker service on the redundant controllers which would also cause any registered VDAs to de-register.
    • Whilst doing this during business hours should be OK, there's always a risk that for some reason a VDA doesn't register with the remaining controllers, so unless you can't avoid it, doing it out of hours, or during low use phases is always preferable.
    • Remove the controllers from Storefront first.
    davis090820-130.png.6d6482cb0f8f6a64aa34ab4d3eecd888.png
    • Then from Studio:
    • Make sure the Controller is powered on so that Studio loads in less than one hour. Once Studio loads the Controller you want to remove, power off the Controller when prompted to do so.
    • Select Configuration > Controllers in the Studio navigation pane and then select the Controller you want to remove.
    davis090820-131.png.62534cc73ad127fef366de8ee8ac5232.png

    Select Remove Controller in the Actions pane. If you do not have the correct database roles and permissions, you are offered the option of generating a script that allows your database administrator to remove the Controller for you.

    davis090820-132.png.f858f878822a2840c730596009b91a94.pngdavis090820-133.png.bcc14c640442071559e6a3c7d54f5063.pngdavis090820-134.png.c8955390fe41499973bb1b8d64d0e782.pngdavis090820-135.png.f3c791dc3acfccaa7dff82bd57de1566.png

    This error is out. So, I did it and selected no, here.

    davis090820-136.png.009bdff4731f926df85327a06def20d0.png

    Then it asked to generate a DB script, for the Database guys.

    davis090820-137.png.02e6bb553f02411e45fffed307d4fa12.pngdavis090820-138.png.3fa6f57de555cb2810fbb288c07e42d6.png
    • Run “Get-BrokerController”
    davis090820-139.png.ab86c3cf1cc9a41e6a4473ad64750a4c.png

    Then run this POSH Script:

    davis090820-140.png.ef5d3da06e92c69bf6802cee8dc9042b.png
    • It will put a Evict.txt file in either your profile %userprofile% or C:\windows\system32. Give this file to your DBA.
    • Then Run it on the database.
    davis090820-141.png.24df6a8e267b1c8a903f8a2cbc9f80bd.png

    Check Studio and it's gone.

    davis090820-142.png.5fee86663226c1ac81afc210239b9e3d.png
    • Any VDAs registered to the controller should re-register with the remaining controllers
    • Adding a second 2016 Delivery controller now to slit the broker balancing out
    • Install Virtual apps and Desktops
    davis090820-143.png.2b702fde443cb8629c8cecf423f69f48.png

    Select Delivery Controller.

    davis090820-144.png.1d5ac237843735798ea74504f246134d.png

    Read and accept.

    davis090820-145.png.a33135c3742ec8c3cb2b5600965f0785.png

    Select the components you need.

    davis090820-146.png.946ec86a1540d47730eeb6125b3652b6.png

    Install the Feature you need (NO Local SQL for me).

    davis090820-147.png.95aa45719f5d874cbee03737a9ee0b05.png

    Firewall ports.

    davis090820-148.png.d6d6cef43658cd87ba07f2d7f20571fc.png

    Summary.

    davis090820-149.png.05721dc4791dfe57ebdcfd1a5bf57a15.png

    Extracting Files.

    davis090820-150.png.39c66194ec6c4a8ee67bbcf1ee987146.png

    Machine needs to reboot.

    davis090820-151.png.77eed7f8f71279edc49831eeac66b842.png

    Collect diagnostic information.

    davis090820-152.png.31cb6004148cc4cbbe6e5d072d9e5d38.png

    Finished, now launch Studio.

    davis090820-153.png.75f48d46c42427f8dc29276224de23b0.png

    Connect the delivery controller to an existing site.

    davis090820-154.png.8c54be99ef8e60032242d973b36c1ff1.png

    Add the delivery controller address that is already a part of the site.

    davis090820-155.png.d377805cb328a886ddbfbcaa85dd86fa.png

    For this part, in my environment I selected yes.

    davis090820-156.png.246b983d5005f6d736cdbd2190b04028.png

    Enter my creds to add to the database, then let the process begin.

    davis090820-157.png.0831cda82207746edca2f6cb9d0a28b4.png

    I now have 2 controllers that are 2016.

    davis090820-158.png.db0afcb82ea9d697f4b1ee6e38ae5539.png

    Both servers are.

    davis090820-159.png.3efe29c5677f0155af037e4370c1df79.png
    • Finalize Citrix Director
    • Finalize Director upgrade run this.c
    • C:\inetpub\wwwroot\Director\tools\Directorconfig.exe /upgrade
    • If you use Citrix ADM, and Citrix Session Recorder you will need to register the Snap In back after all the upgrades. This is so you can control the feature in Director
    • Register Director ADM MAS back
    • If using HTTPS to connect to Insight Center then the Insight Center certificate must be valid and trusted by both the 22.
    • Director Server and the Director user’s browser.
    • To link Citrix Director with NetScaler HDX Insight, on the Director server run C:\inetpub\wwwroot\Director\tools\DirectorConfig.exe /confignetscaler.
    • Enter Machine name or IP: Netscaler Insights machine or IP vs1ctxadm01.jaxnavy.org
    • Enter 1 for Citrix ADM (aka MAS).
    • Rest is self-explanatory.
    davis090820-160.png.6ddfb2ccc1ee69020e58d5dbb037648b.png
    • Register Director Snapin back for Session recording
    • Run C:\inetpub\wwwroot\Director\tools\DirectorConfig.exe /configsessionrecording
    • Enter the Session Recording FQDN (server.FQDN)
    • Enter 1 for HTTPS.
    • Enter 443 as the port
    davis090820-161.png.8d0eeda49dcf14d4eff0d8715485f0ff.png

    Upgrading or replacing the SQL LocalDB for Local Host Cache for 1912 or 1912 CU1

    There has been some recent change to the LTSR article around Local Host Cache upgrades

    https://docs.citrix.com/en-us/citrix-virtual-apps-desktops/upgrade-migrate/upgrade.html#replace-sql-server-express-localdb

    • When upgrading Delivery Controllers to Citrix Virtual Apps and Desktops version 1912 or 2003: Upgrading SQL Server Express LocalDB is optional. Local Host Cache works properly, with no loss of functionality, regardless of whether you upgrade SQL Server Express LocalDB. We added the option to move to a newer version of SQL Server Express LocalDB in case there are concerns about the end of support from Microsoft for SQL Server Express LocalDB 2014.
    • When upgrading Delivery Controllers to Citrix Virtual Apps and Desktops versions newer than 2003: The minimum supported version is SQL Server Express 2017 LocalDB Cumulative Update (CU) 16. If you originally installed a Delivery Controller earlier than version 1912, and have not replaced SQL Server Express LocalDB with a newer version since then, you must replace that database software now. Otherwise, Local Host Cache will not work.

    As you can see here, at one time it stated you needed to upgrade, or it would not work. However, it doesn’t seem that it is 100% anymore. I think that’s why Citrix updated the doc. 

    As can be seen here some had the same concerns or questions around it. I most certainly did.

    davis090820-162.png.796ba16010d34499884e31c38c948c79.png
    • So, let’s get started. I always do a snapshot first. Which is completed. 
    • Complete the upgrade of your Citrix Virtual Apps and Desktops components, databases, and site. (Those database upgrades affect the site, monitoring, and configuration logging databases. They do not affect the Local Host Cache database that uses SQL Server Express LocalDB.)
    • As you can see, I am on 1912 CU1 and have MSQL Express 2014.
    davis090820-163.png.acd8177093a401b45c03038ed139ac2d.png

    On the Delivery Controller, download PsExec from Microsoft. See the Microsoft document PsExec v2.2.

    davis090820-164.png.60fb548300a87931f0b1be900cc1bbda.pngdavis090820-165.png.f3bd3a4ab1acd7c53eda2abe521f3972.png
    • Open CMD as Admin and open PsExec.exe

    psexec -i -u "NT AUTHORITY\NETWORK SERVICE" cm

    davis090820-166.png.2278aa98fffde2498775bfe47a15e1a2.pngdavis090820-167.png.dea8a492466b4eeb9718611adbfe6c48.png
    • Move to the folder containing SqlLocalDB.

    cd "C:\Program Files\Microsoft SQL Server\120\Tools\Binn"

    davis090820-168.png.c0901cff079230bb8f56533d61c52f2c.png
    • Stop and delete CitrixHA (LocalDB).
    • If you don’t stop is you will get this error (Me not paying attention).
    davis090820-169.png.db251442f8cf9db44ba1205ca1678fa4.png

    SqlLocalDB stop Citrix

    SqlLocalDB delete Citrix

    davis090820-170.png.aa65617e9a77a86165432ec21e4e931d.png

    Remove the related files in C:\Windows\ServiceProfiles\NetworkService

    davis090820-171.png.88de8a264499c41263f7e96f82dbe59e.png

    Uninstall SQL Server Express LocalDB 2014 from the server, using the Windows feature for removing programs.

    davis090820-172.png.e78d2009e220309b69628626325657fc.png

    Install SQL Server Express LocalDB 2017. In the Support > SQLLocalDB folder on the Citrix Virtual Apps and Desktops installation media, double-click sqllocaldb.msi

    davis090820-173.png.9d7ecae5837dd138c788cf22787b0eb6.pngdavis090820-174.png.a4187ee36f8ebbb9f66b891abfb141ba.pngdavis090820-175.png.579c854336abef7dd9644ea1280e27f3.pngdavis090820-176.png.803b1776e11af9afc151d576ffc6065d.pngdavis090820-177.png.0540a591635ef856470c7412e3e40b66.pngdavis090820-178.png.a1eb2ed430f5c49149f89fef12111739.png

    Reboot the server and make sure this is started “Citrix High Availability Service”.

    davis090820-179.png.01a35f5fee8c185c27b4622cdc44d820.png

    Logged on and it took about 15 seconds to show up.

    davis090820-180.png.415897691e70475fd36c1605d70c904a.png

    Then 60 seconds or so on this:

    davis090820-181.png.4c72aeb3b04c3aed8b788d953e15e7f8.png

    Check if the Citrix Db is created.

    CitrixHA is re-created the next time a configuration sync occurs. After a minute or two, use the SqlLocalDB utility to confirm that CitrixHA has been re-created.

    SqlLocalDB i

    CitrixHA

    MSSQLLocalDB

    Example: While still in the PsExec session run this:

    C:\Program Files\Microsoft SQL Server\120\Tools\Binn>SqlLocalDB i

    CitrixHA

    MSSQLLocalDB

    davis090820-182.png.d7288aa9fe911171c45bd5386bf0ef22.pngdavis090820-183.png.2b8c2b111bf248a35c6e0f54e66b18c9.pngdavis090820-184.png.787880098d02fcb7c7750a68b74261c6.png

    You will see this until you do the second broker.

    davis090820-185.png.5c5f3f4674e2060e5ddacc430d77d08d.png

    After I did my second Broker this was in the logs:

    davis090820-186.png.1b1f4d281d7fc876424217ecb6014794.pngdavis090820-187.png.b6d89e9186086c99602ab4f4911fadd4.png

    But then I see this almost every 2 minutes. I remember reading about this. But I thought it was fixed many versions ago.

    davis090820-188.png.5cd156ab9fcea4f17e425c5d1e0085e2.png

    Did some Google on the Errors and came up with the 2 links below.

    https://support.citrix.com/article/CTX230775

    1. LHC DB upgrade reference

    https://docs.citrix.com/en-us/citrix-virtual-apps-desktops/upgrade-migrate/upgrade.html#replace-sql-server-express-localdb

    • Turns out some AD accounts were deleted over time, and it had some bad SIDs.
    • So, I ran the quick script to get the output.

    Get-BrokerApplication |foreach {if ($_.AssociatedUserNames -match "S-1-5-21") {$_.Name; $_.AssociatedUserNames -match "S-1-5-21"; ""}}

    davis090820-189.png.0cb74497e1647c899689b0fdcdbbe23b.png
    • Went into Studio and deleted them from the location it displayed above. Which was in a Published application visibility.
    • Then CTX230775 was needed to redo the LHC DB. So quickly ran through the process and it fixed the error. 

    So, in summary, this is how I upgraded the LHC DB and some minor troubleshooting. Hope it helps someone

    • Citrix StoreFront 7.15 to 1912 (Example I did on one SF server on the upgrade. But you would want 2 servers)
    • If you have a Load balancer, disable it in your load balancer. This way traffic doesn’t route to it. (Assuming you have 2 or more storefront servers)
    • In my case I have a LB Vserver and IP is X.X.X.X  and back end servers are A.A.A.A  and B.B.B.B
    • Server A.A.A.A is disabled
    • Browse the ISO
    davis090820-190.png.4aab13dfdc3ad8bd5056d43a364edfe9.pngdavis090820-191.png.b1d31e6b7ac1b793857a8d3131894321.png

    Accept the terms.

    davis090820-192.png.7fed27f9dc412a68a39d73e4282aff21.png

    Ready to install.

    davis090820-193.png.8109549ccd3de3a95df7c6cc49c77108.png

    Installing.

    davis090820-194.png.ef9eb8b8a5cc031c070f1810e37be9b2.png

    Upgrade has finished.

    davis090820-195.png.ec6102ff23d3ccfaaafe461c2b12563c.png

    I am adding a new StoreFront Server, so this will be a new install and add to the Storefront store. I just browse to the StoreFront application and run it.

    davis090820-196.png.81b6978ef7553006266361092b44d2f0.pngdavis090820-197.png.a5108eb8f207c6b1eefcb710fa7454b7.png

    License agreement.

    davis090820-198.png.c3b683fbb59273d702ada6a716e1cedd.png

    Review prerequisites.

    davis090820-199.png.a1c9bd6908f1b541fd92eb974e9226d9.png

    Ready to install.

    davis090820-200.png.5582d7549d4ace203bb23d62953f65df.png

    Installing Software.

    davis090820-201.png.6c28111ba1849f528a56cc2d7c660795.png

    Successfully installed StoreFront.

    davis090820-202.png.f99ec3f904b07566547525a200d811f8.png

    Join existing server group.

    davis090820-203.png.34c678724fcacbc519f8659c6953851d.png

    On the Primary StoreFront Server click “Add Server” here to get an Authorization Code.

    davis090820-204.png.1c033a69acdd8eb63c85cd91cd6dc03a.png

    Take this information and input it on the secondary StoreFront Server.

    davis090820-205.png.92076096bebf8a49e8b534bb22c2acc1.png

    Input information on Second server.

    davis090820-206.png.671a2d65911ab32803eb0d7b1b2488ed.png

    Joining.

    davis090820-207.png.64ce8a2f95877b400bbda1e8c7ed5dab.pngdavis090820-208.png.d7aaf359ebb0bcb682569f9c9a45a241.pngdavis090820-209.png.964ea18ea7924ff834186739d2889c50.png
    • Sever joined
    • Now Add IIS Cert and Bind it to 443 in IIS
    davis090820-210.png.5e3ab44164d5e81ef808766ec4d2c717.png
    • Add Server in netscaler>Traffic Management>Load Balancing>Servers
    • Add Server
    davis090820-211.png.0e1582b8f3e70fef2323283430513cbd.png

    Add service.

    davis090820-212.png.8968bc2022c43295cba07fd4e0d8fd62.png

    Add monitor.

    davis090820-214.png.577f76feb6b6e8d8023b26db5de908d9.png

    Now go bind it, once you bind it to the Service you will notice its down. Which is normal, from what I have gathered.

    davis090820-215.png.9a1d5d0aa9c2de0cb0fe68879c2d5a65.png
    • The StoreFront monitor by default is only via HTTP.I created earlier is trying to probe the backend services of our server through HTTPS.
    • To fix this do this:
      • Run PowerShell as an administrator.
      • PS C:\Program Files\Citrix\Receiver StoreFront\Scripts> .\ImportModules.ps1
    davis090820-216.png.67c281ed2110ae835291d7c4b3454ac2.pngdavis090820-217.png.5b3133e6379b8c9ec930f85291a157bf.png

    PS C:\Program Files\Citrix\Receiver StoreFront\Scripts> Get-DSServiceMonitorFeature http://localhost:8000/StorefrontMonitor

    davis090820-218.png.a247af206c25965d6bb1e788b55de702.png

    Now run the command Set-DSServiceMonitorFeature -ServiceURL https://localhost:443/StoreFrontMonitor.

    davis090820-219.png.6f4fd344b6bb8936533c7102ff167e0a.png

    All steps outlined in Red:

    davis090820-220.png.2d38de8b63e9fc467003d15f8c22f0d3.png

    Now you will see the monitor come alive on the Service.

    davis090820-221.png.9ab44dd9bab1a646b6e6995daf33065c.png
    • Now bind it to the main Vserver
    • Provisioning Server 1808 to 1912
    1. Please check if the previous version needs to be uninstalled first. Some versions, Citrix wanted you to uninstall the older version first. But most of the time you don’t. 
    2. Example here: https://discussions.citrix.com/topic/400292-pvs-server-upgrade-1808-to-1811-please-uninstall-pvs-server/
    3. We are updating 1808 to 1912 so an in place upgrade is good.
    4. Before I start I make sure I use a service account that is tied to the database so it can upgrade the database.
    5. I put the account in the local admin of the PVS servers and use it to do the upgrades
    davis090820-222.png.45b40be9bc7f807a9cf401ecc2a88922.png
    • After the uninstall has completed, restart the server. When it comes back up, log back in with the service account.
    • Attach the ISO.  Run Server installation.
    davis090820-223.png.85973ef87f51c568f485219e130564a0.png

    Click "Install", the process will begin and then the window will disappear for a couple of minutes while it installs some of the pre-requisites.

    davis090820-224.png.bd3b930a1e98b03981cd8f178e628831.png

    When the window pops back up Click "Next." 

    davis090820-225.png.437c3e77b7776f3948d90edaba9e1035.png

    Accept the License Agreement and click "Next."

    davis090820-226.png.08f34201f896389c5eaeef157ece3775.pngdavis090820-227.png.b548d93a46f643a2e164499e115f7775.png

    Enter "Something" in the User Name and Organization Fields, then click "Next."

    davis090820-228.png.af45e20ccfb3ef4e144331ec644465bd.png

    Click "Next."

    davis090820-229.png.920406cbf1815597633211fb035ce8bd.png

    Click "Install."

    davis090820-230.png.a839382bd0973e35568a77fb141e42bd.png

    Installing.

    davis090820-231.png.de2c92241837bd45997059784eab0a7d.png

    Click "Finish."

    davis090820-232.png.7f0fdffe3e9a23584f072196bc2b1fa5.png

    The Configuration wizard will start.

    davis090820-233.png.51c8a5b3bafd0fd1200515b973566f9b.pngdavis090820-234.png.16b67d1e6f58a757ab69dbe38a92d0e4.pngdavis090820-235.png.af15d8659dfae007b397b14fe998a532.pngdavis090820-236.png.e197ca85c94563c044b2ea6a3bc5ee47.pngdavis090820-237.png.541ddb83acdebbfbd5ee1149eecdf08f.pngdavis090820-238.png.9790bc1cccc0c26026be5635fff5559f.pngdavis090820-239.png.85d556f73df8a8ef323e3c1497536cf4.pngdavis090820-240.png.4b9bfadf3456cff3f77677fa2b28dab2.pngdavis090820-241.png.13786d408e6cd091df882dc47e717d41.png

    For this screenshot I have 2 PVS servers, depending on your Farm you could have 1 or more. The PVS servers IP address will show here. If you have 1 server then  1 Ip will show. If you have 2 then 2 will show.

    davis090820-242.png.6a702110e28a598602bb3af2e6ea965c.pngdavis090820-243.png.9d2d319a486e60729bc42d1f20d456e2.pngdavis090820-244.png.a9e52ebce50a3ecb4d340f16d57bbe0e.pngdavis090820-245.png.456793efebd65f5111bff8ce32c0182b.pngdavis090820-246.png.7bd098812f9776db0d94167cf93d850c.png

    Backup your database before starting.

    davis090820-247.png.8dfca825f37f6e70c6613030f7947a76.pngdavis090820-248.png.8d0968c4289ea513497d30722fd20939.pngdavis090820-249.png.84421576f38eafa95feb31d9515a5ed0.png
    • PVS console upgrade
    • Log into the server with the service account.
    • In C:\SRC\1906 open the "Console" Folder. 
    • Right click on "PVS_Console_x64.exe" and run as administrator. 
    • Once the .exe has launched Click next through the installation.
    davis090820-250.png.382baa176c616515170c282264cce82c.png
    1. If you run into any issues during the installation of the pre-requisites refer to 
    2. https://www.carlstalhood.com/provisioning-services-server-install/
    3. Accept licensing terms
    davis090820-251.png.da843afa7b9ae7ae1099a3cc1385991f.png

    Fill in the names.

    davis090820-252.png.1b094c8d187648a08541496ba59ccee1.png

    Install in the default directory.

    davis090820-253.png.b604b286eb4fddc5f030b9dbfa60cc2a.png

    Install.

    davis090820-254.png.56d1f6a1b5f4f3660e75b8eb70f06771.png

    Installing.

    davis090820-255.png.68641b76aafbfeee26e29fbb9e9935dc.png

    Finish.

    davis090820-256.png.30191a4de41e26df3c66dda3d89ee595.png

    Open the console and check the version.

    davis090820-257.png.b8bc3d6aaad38cf018905b148732aeda.png

    You need to re-register those PowerShell snap-ins. Reregistering Citrix.PVS.Snapin.dll is well-known, but here are 5 other snap-ins that are necessary as well.

    • On the PVS server, run CMD as Administrator. Then in each of these folders:
    • CD \Windows\Microsoft.NET\Framework64\v4.0.30319
    • CD \Windows\Microsoft.NET\Framework\v4.0.30319
    • Run all of these commands:
      • .\InstallUtil.exe "C:\Program Files\Citrix\Provisioning Services Console\Citrix.PVS.Snapin.dll"
      • .\InstallUtil.exe "C:\Program Files\Citrix\Broker\Snapin\v2\BrokerSnapin.dll"
      • .\InstallUtil.exe "C:\Program Files\Citrix\Configuration\SnapIn\Citrix.Configuration.Admin.V2\Citrix.Configuration.PowerShellSnapIn.dll"
      • .\InstallUtil.exe "C:\Program Files\Citrix\ConfigurationLogging\SnapIn\Citrix.ConfigurationLogging.Admin.V1\Citrix.ConfigurationLogging.PowerShellSnapIn.dll"
      • .\InstallUtil.exe "C:\Program Files\Citrix\DelegatedAdmin\SnapIn\Citrix.DelegatedAdmin.Admin.V1\\Citrix.DelegatedAdmin.PowerShellSnapIn.dll"
      • .\InstallUtil.exe "C:\Program Files\Citrix\Host\SnapIn\Citrix.Host.Admin.V2\\Citrix.Host.PowerShellSnapIn.dll"

    PVS Targets upgrades:

    1. You will need to go to the PVS server that you are working on and open the PVS console.
    2. Then go to vDisk Pools and create new versions. If you have 5 versions, then the 6th version will need to be merged with the last base and updates or updates only and needs to be Maintenance mode. It will take some time to create the merge base.
    3. Now go into your Hypervisor and power on the Master VM up that has the new version.
    4. Open the console so you can see the VM.
    5. It will ask you to press 1 for the new Maintenance version. Press 1, and it will boot into windows.
    6. Now bring over the PVS software, and put it on the C or D drive of the Target
    davis090820-258.png.c651145c84a704bec94af1f7f7c4294b.pngdavis090820-259.png.1f68f4ad1b2f630a0891e136d9ea2d3a.png

    Click Next at Welcome to the Installation Wizard for Citrix Provisioning Service Target Device x64.

    davis090820-260.png.684a5b07886e700ef38473428a344f5d.png

     Select I accept the terms in the license agreement, click Next.

    davis090820-261.png.251077980dc0509c00fa0680ed8c019d.png

    Leave as default, click Next.

    davis090820-262.png.e34d2091d3b91563c85deb540f6b02a9.png

    Leave as default, click Next.

    davis090820-263.png.6947a42b0158862179787fa42cc50861.png

    At Ready to install the program, click Install.

    davis090820-264.png.80cdda3264299eade56d9482f89043c9.png

    Installation will begin and take a few minutes to complete.

    davis090820-265.png.810efefa0003db7d1824c4975a596335.png

    Click Finish at Installation Wizard Completed.

    davis090820-266.png.c9ed46c73f6b00ef46dd597a156b1219.png

    At this stage the vDisk should be re-sealed ( based on your sealing techniques and re-distributed/Coped to each Provisioning Server

    Update the BDM ISO.

    We use the BDM ISO.

    davis090820-267.png.5514b951b7f6171f6ddcb1f43572704e.pngdavis090820-268.png.fad42ab265bbba8680c88a8ca18f974a.png

    Information

    • Remember don’t check this unless your troubleshooting: https://support.citrix.com/article/CTX230333

    • Reason why is here: https://discussions.citrix.com/topic/363293-pvs-76-xa65-tds-taking-10mins-to-boot/

    davis090820-269.png.d42442e5dffda00b9f78af9988d606dc.pngdavis090820-270.png.27ef8f8595c0627f7189907be729dcbd.pngdavis090820-271.png.c9a856eba8880682fb37aea8bd12d1c1.png

    Upload to your hypervisor storage. Datastor/Container

    Now attach that ISO to the PVS Targets you upgraded on 4c. It will need a new ARDBIN file. ( If you forget this step, it will still boot. But will be slower and could get stuck in a loop.

    1. Citrix WEM 1811 upgrade to 1912 LTSR
    davis090820-272.png.815b35efd76c500cbaac150f2d66c861.png

    The Workspace Environment Management components must be upgraded in the following order:

    Infrastructure services: https://docs.citrix.com/en-us/workspace-environment-management/current-release/upgrade.html#step-1-upgrade-the-infrastructure-services

    Database: https://docs.citrix.com/en-us/workspace-environment-management/current-release/upgrade.html#step-2-upgrade-the-database

    Administration console: https://docs.citrix.com/en-us/workspace-environment-management/current-release/upgrade.html#step-3-upgrade-the-administration-console

    Agent: https://docs.citrix.com/en-us/workspace-environment-management/current-release/upgrade.html#step-4-upgrade-the-agent

    The following changes are going to occur so be ready:

    • A new clean installation of the WEM Agent will result in a complete change of Service Names and Folder Structures as below
    • The new Service name is: Citrix WEM Agent Host Service
    • The new process name is: Wem.Agent.Service.exe
    • The new path structure is: %ProgramFiles%\Citrix\Workspace Environment Management Agent
    • An upgraded installation of the WEM agent will result in partial changes to your environment:
    • The new Service name is: Citrix WEM Agent Host Service
    • The new process name is: Wem.Agent.Service.exe
    • The path on the file system will not be altered and will remain as it was: %ProgramFiles%\Norskale\Norskale Agent Host
    • Be aware also that in both clean and upgraded deployments, the Windows Event logs will change from Norskale Agent Service to WEM Agent Service 
    • Source: https://jkindon.com/2019/09/11/citrix-wem-updated-start-up-scripts/

    Infrastructure services:

    davis090820-273.png.78f0d250594ec67fc97ae950fb931493.png

    I need .Net 4.7.1

    davis090820-274.png.27b80374eabc3ba5cb0d8fdcdd81da33.pngdavis090820-275.png.600b988676357effdff1e8131a382db5.png

    For me, I selected yes now.

    davis090820-276.png.68a251ff00ade5e25f8bb276e49df925.png

    Reboot and logged in.

    davis090820-277.png.007cce015257a464ee6b8fc96a8e568a.pngdavis090820-278.png.fcf215e380e9b6e1264c6591314bb17b.pngdavis090820-279.png.d906945895d820b655a8a61da2b2cb30.pngdavis090820-280.png.942abbbeb011c80ea1d858b2994927b1.pngdavis090820-281.png.b385d7c9053bf15f76c0a5edb94ac48f.pngdavis090820-282.png.4a6ca014ac602cf1a51722a5bcb3ca34.pngdavis090820-283.png.814b221fc8cd65a9c00890ce0999d4a2.pngdavis090820-284.png.b198c80fb0953904a014ca1a4298b42b.pngdavis090820-285.png.707eb3364a97981526180d88136996fe.png

    Database:

    Open the database management Utility

    davis090820-286.png.2064b9a95d8546d9b30ac168a1cf2906.pngdavis090820-287.png.86095f0c08835f04e69078da8d94d4f8.pngdavis090820-288.png.1a14bfa5d652bd1c520c121300b399bc.pngdavis090820-289.png.895455e833fa7a6eb5bd368a3a546333.pngdavis090820-290.png.4ab55c5a0ec86b5413166919952a03c6.pngdavis090820-291.png.edf3bfd6c5c1c7880cc59b6f5c0a399b.png
    • I at this point just restarted the server
    • Check Database parameters (open the WEM Infrastructure Service Configurations).
    davis090820-292.png.d36ad523e70bac0ce4a7b08aba4f83ec.png

    You will notice the Port and old name (1811).

    davis090820-293.png.f3b5e2e180c68b444b033e186329a517.png

    You will notice the Port and new name -1912.

    davis090820-294.png.9853ebd739e892f4cf064a66015602d3.png
    • *One thing to note on Port* 
    • Cache synchronization port. (Applicable to Workspace Environment Management 1909 and earlier; replaced by Cached data synchronization port in Workspace Environment Management 1912 and later.) The port on which the agent cache synchronization process connects to the infrastructure service to synchronize the agent cache with the infrastructure server. The cache synchronization port must be the same as the port you configured for the cache synchronization port (WEM Infrastructure Service Configuration > Network Settings) during the infrastructure services configuration. The port defaults to 8285 and corresponds to the AgentCacheSyncPort command-line argument.
    • Cached data synchronization port. (Applicable to Workspace Environment Management 1912 and later; replaces Cache synchronization port of Workspace Environment Management 1909 and earlier.) The port on which the agent cache synchronization process connects to the infrastructure service to synchronize the agent cache with the infrastructure server. The cached data synchronization port must be the same as the port you configured for the cached data synchronization port (WEM Infrastructure Service Configuration > Network Settings) during the infrastructure services configuration. The port defaults to 8288 and corresponds to the CachedDataSyncPort command-line argument. Alternatively, you can specify the port using a command-line option in the silent installation of the WEM agent 
    • Wayne Lui states its backwards compatible and still listens, but I would add this into your Firewall Rule set. 
    davis090820-295.png.7d7b3bb4dd3d1fc0105f2c3912de1437.png

    Admin Console:

    davis090820-296.png.da2984daac8899655439813e0deb29ff.pngdavis090820-297.png.49d8d48817f123606540af58e03c105a.pngdavis090820-298.png.c7344b3107f7d1db4c4a6abfc5905084.pngdavis090820-299.png.1147a8ceef2d7e84cbfde1ec4bc52953.pngdavis090820-300.png.4ebccddb4a9fe968c6aed39e6ed6151e.pngdavis090820-301.png.76b839aef397f1d1378ef9d07158f4c3.pngdavis090820-302.png.b69c088f03d16a80f06cca657872de43.pngdavis090820-303.png.59b6d34cb50747213ec0756beb7a0204.pngdavis090820-304.png.4987b4039a96d8e5749a7cd671cfc96a.pngdavis090820-305.png.50d97add7e41e05f26f695eb52943261.png

    Agents

    • Upgrade the Agent on the machines 
    • I did this with the GUI, but I do this in production.
    • ##Install CMDLine with a SCCM task

    Task 1:

    "Citrix Workspace Environment Management Agent Setup.exe" Cloud=0 VUEMAppCmdDelay=5 WaitForNetwork=30 SyncForegroundPolicy=1 GpNetworkStartTimeoutPolicyValue=5 /log WEM2003.txt /quiet

    Task 2:

    ##Copys Startup script 

    xcopy "\\server\Citrix\Upgrade Files\WEM\2003\Workspace-Environment-Management-v-2003-01-00-01\WemRefreshCache\RefreshWEMAgentonReboot.bat" c:\scripts\refreshWemAgent /h /i /c /k /e /r /y

    Task 3:

    Then it runs a 

    C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe update

    C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe eqi 3

    I took James Kindon's script: https://jkindon.com/2019/09/11/citrix-wem-updated-start-up-scripts/

    Then it’s called the same name as my older script (RefreshWEMAgentonReboot.bat), does a xcopy and places it in the same location. This way the scheduled task will still have the same name it runs. The CLI parameters are different but will do the same deal.

    davis090820-306.png.5e8a991bb35bf96dbfffe85f4c1104d0.pngdavis090820-307.png.4027ffb598910218fbace9fc39b9bcfa.pngdavis090820-308.png.e4dd9fdf9e210942208f4062a8263171.pngdavis090820-309.png.0ef9e31543131510a9c3cd193625bb09.png

    We use BISF to handle this during our sealing process.

    davis090820-310.png.15c6b9d687e4e50c7b32f4b7ab908c1e.pngdavis090820-311.png.f2e6c786b0a6003dfdc4033fcdca2185.pngdavis090820-312.png.d4486d397bd4e8390d7ccc43e56b6122.pngdavis090820-313.png.0e99a5d75ce9b2d8d91fde93688d2136.pngdavis090820-314.png.ad86f6f6400b1bb1d72e71706a43e21b.pngdavis090820-315.png.81a0a4f3e72258bf621d9b48e1aa9958.png

    Agents are completed.


    User Feedback

    Recommended Comments

    Guest Top 10 Most-Read Blogs in 2021 – BLOGS

    Posted

    […] How I Upgraded my Site from 7.15 Flat all the Way to 1912 by Ray […]
    Link to comment
    Share on other sites

    Guest Citrix WEM Database Migration | BLOGS

    Posted

    […] I won’t delve into the nitty-gritty details of those upgrades because there are already countless blogs out there that can walk you through the process. I even have one on CUGC that you can use as a reference if needed. It goes over just about everything. It’s older, but it will guide you. How I Upgraded My Site From 7.15 Flat All the Way to 1912 | BLOGS (mycugc.org) […]
    Link to comment
    Share on other sites



    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now

×
×
  • Create New...