Open these files in WinMerge ( ) and it will highlight any discrepancies between the old and new Citrix environments.
I recommend using the open source tool “WinMerge” to diff these files as the diff command in windows is less than optimal. On the new server: C:\temp\ctxpolicy-new.txt.On the old server: C:\temp\ctxpolicy-old.txt.If you followed all of the steps from the export and import process you should have 2 new files. Otherwise you may need to repeat this process for the next policy mentioned in the error message. If you see your policies you are done with this step. Refresh the policy view in Citrix Studio. Replace the ‘-value’ property with the priority value that is appropriate to your environment. If you wish to switch to the user policy run: cd ".\user\Random-Citrix-Policy".Since ware already in the computer directory, we can change to the “Random-Citrix-Policy” policy and execute the following commands In this case I want the priority to be 4. We need to adjust one of these so that it matches the other. The user policy priority is 4, and the computer is 1. Note the priority on the same policy is different between the user and computer policies. Ls | where name -eq "Random-Citrix-Policy” New-PSDrive Site -PSProvider CitrixGroupPolicy -Root \ -Controller localhost Use the policy names from your environment in the ‘where’ filters. Return to your admin Powershell session and execute the below commands. * Please note: In these examples I am censoring the actual policy name and using a made up name, ‘Random-Citrix-Policy’ for privacy. While this message is misleading, it does give us a valuable bit of information, the other policy mentioned is called “Random-Citrix-Policy”. There is no priority interference with the “unfiltered” policy as indicated in the message. * Note the name of the policy given in the error message. Open Citrix studio and click on policies, If you added several policies, there is a good chance you will be presented with the below screen After an import, studio attempts to merge user policies with computer policies of the same name and applies filters for the various users and computers. Instead policies use filters that can be applied to users and computers. Separate user and computer policies no longer exist inside the GUI. Resolve Merge Discrepancies with Citrix StudioĬitrix 7.xx Studio handles policy filtering in a different manner than 6.5. \User\$($p.name) -Recurse |where enabled -eq true |Out-File $outfile -Append \User\$($p.name) -Recurse |where state -eq enabled |Out-File $outfile -Append
\User\$($p.name) |Out-File $outfile -Append On your 6.5 server run the below commands: if (!(Get-PSDrive | where name -eq LocalFarmGpo)) You can use to your compare current policies the to the new farm later on.
If you have a large number of policies you will want to generate a verification file now. \policy-export.logĪfter the policy export completes, copy the policies.xml file from the 6.5 server to a 7.xx delivery controller and place in C:\temp\ImportFMA Note if you get security warnings press “R” to ignore and load scriptsĮxport-Policy -XmlOutputFile. Open and administrator command prompt and execute the following:
Important note, be sure to download the migration “scripts”, not the migration “tool”.Download the Citrix Migration Tool from the xenapp 7.6 download page: Citrix 7.6 Downloads.The process is broken down into 4 parts below. If you are uncomfortable with PowerShell this is a great learning opportunity. It is quick and relatively painless, however, you will need to use and modify PowerShell modules. If you are in a similar situation or if you would like to try a more streamlined approach, the procedure below will help you save some time.
Unfortunately, many discover this only after their brand new 7.7 or higher farm is stood up.
Per Citrix, there is no direct path to migrate policies from xenapp version 6.5 to 7.7 or above, you must first install and migrate to 7.6, then do an in-place upgrade to the desired version. In this post I will outline the process I used to overcome the limitations of existing Citrix policy migrating tools. Migrate Citrix Policies from XenApp 6.5 to >7.6