If you have read the previous articles on creating a minimal infrastructure App-V environment (Here) then you will have seen that you can use FsLogix Apps to manage the availability of globally published App-V applications. The only slightly sticky point is creating the FsLogix .fxr rules for each App-V package. Whilst the steps aren't overly time consuming (see here for an overview) they do require a manual set of steps to create a rule for each application. If you have 50 App-V applications this might take the better part of a day importing the app into the cache, creating a new rule, browsing for the App-V Package Root Path etc. If the app needs to be run through the sequencer again then the PackageID and VersionID are going to change meaning recreating the .fxr. The goal of this tools is to reduce the time, effort and increase the accuracy when creating rules for FsLogix. (At least until the FsLogix guys implement a CLI/API to play with ;-) ;-) ).
With the ".frx from .appv" tool you can point it at your app-v package repository and click go. It will read the important information from the .appv file and create you a rule for the App-V application automatically. You can also create a rule from the app-v package that will mask the application as an installed application (should testing show the application is not suitable when virtualised).
This mean that you can convert your apps to App-V format automatically using Anberreef AR.c (or any other way). You can then create an FsLogix Rule for the application as both a virtual and installed application automatically with "AR.c FXRfromAPPV". Once you have been through your testing and remediation phases and determined your application profile (i.e. the applications that will App-V and those that you can either use as a vendor installation or re-engineered as MSI for installation into the image) you can then apply and test the appropriate FsLogix .fxr rule ("v_" or "p_") to the release.
Using the Tool
You can download the tool HERE:
Unzip the download and place the files somewhere. Run "FXRAuto.exe" and you will get the following:
||The location where the App-V packages are stored. You will need write access as the application will extract various files from the App-V package to enable it to create the FsLogix Rules. These will be placed in a \AR.c folder under each package folder.
|| Click to open the directory browser to select your Source Path
|| The Save Path will default to the FsLogix Rules folder in the current users documents folder. This can be changed.
||Browse Save Path
|| Click to open the directory browser to select you Save Path
||Change PKG Install Root
|| the application makes an assumption when creating the rules, that the App-V Package installation Root is in the default App-V location of %programdata%\App-V (You can check this value with the get-appvclientconfiguration PowerShell command). If this is not the case (e.g. you have an RDS implementation and the App-V installation Root has been changed to D:\APP-V then change this value). This will allow the rules to Mask the App-V package directories appropriately when creating a rule for an App-V Package.
||Browse PKG Install Root
|| Click to open the directory browser to select your Package installation Root Path.
FRXfromAPPV can be downloaded from the Download Page HERE: (Download Name - AR.c FXRfromAPPV 1.1)
Not currently tested against App-V 5.1:
Does NOT create the .fra assignment files (feature for a future release)
The Tool is free to use but not abuse.
Being able to use App-V and FsLogix together is an excellent combination. The ability to automate parts of the "route to live" should be something that everyone is trying to achieve and hopefully this is another helpful little step. Please download and give it a try. If you find any issues please let me know and I'll add features / fixes as they come in.
Happy Masking :-)