User Profile
Nick-S
Copper Contributor
Joined 5 years ago
User Widgets
Recent Discussions
Re: MSIX app attach, disks are mounted but shortcuts are not published
I have something similar (kind of). App Attach applications are showing in Start Menu and launch fine. However, on removing app attach application, app shortcut remains in users start menu (FSLogix Profile). Also occurs if I log onto a separate AVD (which has never had the app attach app presented to it). So 100% profile related. Only way to resolve currently is to reset FSLogix Profile (which is a hammer to break a walnut approach). Have logged a support call with MS. Be interested to know if others are experiencing this? Many thanks NickRe: Registry settings missing on app launch, but exists in User.dat in msix package
Hi Timothy, Thanks for the reply. Yes you are correct, I am using the latest MS MSIX packaging tool, creating the MSIX then migrating to a VHDX for App Attach. I can confirm that when I open the MSIX I can see both registry.dat and user.dat, and when I import either or BOTH into a dummy key, I can see my HKCU hive entries just fine. Would I be correct in thinking that when the MSIX is installed (ignoring App Attach), the embedded HKCU hive should be visible within my HKCU, and again gets removed on uninstallation? (As I am NOT seeing this). Interestingly, if I simply mount the VHDX disk and browse the VFS to my application launcher, everything appears to work fine. I have downloaded your PsfTooling from the store, but am unable to see how the RegLegacyFixup works, as when I select it for HKCU, I do not get any option to "Apply to Proposed Changed List" and the JSON file does not get modified. Do you have any guides on how this tool should be used? Thanks Again NickRe: Registry settings missing on app launch, but exists in User.dat in msix package
pysjkrig and TIMOTHY_MANGAN I know this is an old post, but did either of you discover a workaround / solution to this? I am having a very similar issue: 1. Package up ARCGisPro as a MSIX, and confirm that I have some required keys under HKCU within the user.dat (within the package) 2. Install MSIX (via App Attach) and the HKCU keys are not available. On a thick install, the process of launching the product would generate the required keys (linked to licensing), however with the MSIX, it will NOT generate the HKCU key. My only workarounds are: 1. Run the application elevated as ADMIN, still I can't see the keys get generated, but it appears to launch the product with the information previously captured in the user.dat (its a unique license portal URL) 2. Manually create the HKCU keys for the logged on user, then the application will launch. Any help / ideas on how you resolved your similar issue would be greatly appreciated. Thank youMSIX package Support Framework JSON Argument issue
I am trying to create some additional app shortcuts for Python (as part of ARCGISPro). Firstly, I find it incredible that MS have not included basic shortcut functionality within MSIX, and we have to utilize PSF for some pretty basic requirements. However, I guess this is where we are.. I have a problem with my config.json file as the arguments for Python also include file paths, and the .json file does not seem to accept these. My local installation shortcut for iPython looks like this: "C:\Program Files\ArcGIS\Pro\bin\Python\cwp.exe" "C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3" "C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3\python.exe" "C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3\Scripts\ipython-script.py" So cwp.exe is calling 1. arcgispro-py3, 2. python.exe, 3. ipython-script.py I have created my config.json file as follows: { "applications": [ { "id": "iPython", "executable": "VFS/ProgramFilesX64/ArcGIS/Pro/Bin/cwp.exe "arguments":"VFS/ProgramFilesX64/ArcGIS/Pro/Bin/python/envs/arcgispro-py3""VFS/ProgramFilesX64/ArcGIS/Pro/Bin/python/envs/arcgispro-py3/python.exe" "VFS/ProgramFilesX64/ArcGIS/Pro/Bin/python/envs/arcgispro-py3/scripts/ipython-script.py" } ] } But I keep getting a failure of: I'm not sure how the "arguments" should be recorded: 1. Should I still be using the full VFS path for each call 2. Should I remove / add the " marks 3. Is this at all possible? I can get it to work n more simple applications with standard "/argument " context, but not with this long VFS imbedded string. Any help would be greatly appreciated. ThanksManage Remote Apps StartMenu structure / naming
I have AVD setup with a selection of Remote Apps available via Remote Desktop for WVD From within Remote Desktop I can list and access all my available applications, with the apps named correctly: However, the application list via the webfeed in the Start Menu shortcuts are named as such: AppName(TennantName)(username) e.g. VLC (WVD-GPU)(mailto:first.last@mycompany.net) Is there any method where I can: 1. Create a Startmenu Folder Structure 2. Ensure the RemoteApps just display the shortened Application name I know I can modify within the %username%\AppData\Roaming|microsoft\Windows\Startmenu\Programs, but this will only hold for that session only, and on refresh get re-created. Thanks allApp Attach issue with remote app with multiple applications / entry points
I have AppAttach running in a POC environment and am running in to something a little odd, but repeatable. Sample Application eg "TeraTerm" – packaged as MSIX (confirmed working) then converted to a AppAttach VHDX. Application consists of several start menu shortcuts (entry points), for example 4. (below) AppAttach works fine in a desktop session, and all 4 start menu items are visible, any of these can be launched – the correct destination binaries launch without issue. However in a Remote App scenario, regardless of the MSIX application that is selected (below), it always launches the last application / entry point in the list (last application in the XML) eg we can specify that the application is Collector and the application will appear in RD Client, but on launch TTPMENU will launch This is consistent regardless which application I choose (Collector, CygLaunch, TTermPro, TTPMenu), it is always TTPMenu that launches (despite shortcut icon appearing correct for the selected application). I have tried removing the unwanted shortcuts from the AppXManifest.XML, but this just causes the app to break (they don't seem to be as configurable as AppV XML files). Simple apps with only the one application / single entry point within all work fine. Help?
