User Profile
GrahamGB
Brass Contributor
Joined 3 years ago
User Widgets
Recent Discussions
MECM Supersedence issues with resigned MSIX packages
Without access to a time stamp server solution, we've needed to re-sign a selection of MSIX packages deployed to windows 10 devices with a new code signing certificate previously. That time has come around again and thinking ahead as we prepare for windows 11, we know the list of packages will increase as we convert more AppV packages, a review of the MSIX toolkit has been started. A couple of observations, I'll also place on the github issues list, perhaps somecan provide feedback and sights in to. jvintzel Firstly the packages get updates with the new certificate and publisher information as checked using the get-appxpackage cmdlet; however the publisherid is not substituted in the msix package name as per the MPT default naming standard when saving msix packages, so these have needed to be renamed with another powershell script afterwards. Secondly, we have seen some unexpected results when deploying the resigned packages via MECM targeting the previously signed application with supersedence rules to swap the packages around without an application version update. Scenarios where with the uninstall tick box selected the previous package is removed but MECM doesn't proceed to attempt to install the new replacement package. Or the uninstall selection is not made an the update results in the new package passing for detection but leaving only the previous package actually installed. Whilst I know some of this could be added to a MECM community thread, any shared experiences with using the toolkit would be welcome.97Views0likes0CommentsWindows Desktop (App) Runtime with latest MSIX Packaging Tool
I've noticed with the latest v1.2023.1212.0 release of the MSIX Packaging Tool, that several applications are now presenting the dependency for Microsoft.Windows.AppRuntime.1.4 where the same application version would not have presented this in the manifest in the earlier version of the tool. There is no mention of this in the release notes, as a consideration, and thought this would normally be added automatically if the packaged application indicated this requirement in their own release notes. The application works as expected without the runtime installed on the device, if this omitted from the manifest manually using the Package Editor. Any thoughts / justification / considerations to excluding this?Solved2.9KViews2likes3CommentsMSIX Packaging Tool - Package Analyzer
I was using the 1.2023.1005 release of MSIX Packaging Tool after the October and November announcements and trying to experiment with the new Package Analyzer capabilities with a packaged MSIX through the Package Editor options. However, when I initiate theAnalyze Package option from the Package Editor, it moves through creating the temporary MSIX package, which I can see is created in %Appdata%/Local/Temp/MsixPackagingTool/DiagOutDir/Logs_*number*\ along with a number of other files including a config.json & other manifest files. However once it moves the progress toInstall MSIX Package it seems to stall. The log file in the same temporary folder location, denotes the last entries show that it successfully signed the .MSIX package without warnings or errors, however there is no further information listed showing it is doing something. I am carrying this analysis out in a HyperV virtual machine and have tried increasing the assigned memory from 2048mb to 4096mb and it isn't trying to use all that much of that. In the absence of an up to date HyperV Quick Create iso image with an up to date MSIX Packaging Tool configured with this update, I have configured this in a disconnected environment. I have since seen the recent updates including some bug fixes with version 1.2023.1212.0 and initially having installed this update, one of the MSIX packages I was trying to analyse passed through all the expected steps and return no fixup recommendations. However checking other packages has resulted in the same progress bar stuck atInstalling MSIX Packageand after reverting the snapshots and trying with the same successful package it has hit similar issues. Clearing the temporary files in the Settings area, doesn't appear to have helped either. Are there any checks I need to make in terms of configuration to make this more reliable?1.8KViews0likes9CommentsManaging configuration in [Profile] folder.
I've put RationalPlan Viewer through MSIX Packaging Tool and it appears to work fairly well through the basic steps without PSF, however noticed that to turn off Automatic Updates in the application, files get saved to C:\Users\<User>\.RationalPlan which appear under VFS\Profile during the capture. With previous applications that save appdata files we've used the PSF inject script option to have a powershell script copy the contents of "C:\Program Files\WindowsApps\<AppName>\VFS\Appdata\<AppName>\" to $env:\LOCALAPPDATA\Packages\<AppName>\LocalCache\Roaming However copying the \VFS\Profile\.RationalPlan\ structure to the same location doesn't work. I've attempted to copy the structure to the different folders created under Packages\AppName to identify what it prefers with no luck. I'm fairly new to PSF Tooling and not sure whether the MFRFixup / File-Redirection area would handle this better. I've attempted to use the MFRFixup with the Personal folder selected but the application now errors on launch, even though I have incorporated the manifest changes it suggested. Any guidance on handling this folder structure would be helpful.728Views1like4CommentsMSIX cache on MECM clients
Recently became aware of an issue where an AppV package that had not been launched after install and therefore not streamed the full 100% from the MECM distribution point and that DP had been decommissioned. Unlike MSI that maintains a source list, AppV doesn't appear to maintain this information and therefore the registry keys for package URI have to be updated manually on affected clients. Would like to know if MSIX will work in a similar way to MSI to help with this in the future.680Views0likes1CommentAzure Virtual Desktop Requirements - Azure Active Directory Services / M365
I am looking at how I can configure the requirements for an Azure Virtual Desktop environment to communicate with a Azure Active Directory service in different subscriptions. I have a Microsoft 365 E5 subscription through the Microsoft 365 Developer Program using my work email address. How can I have this communicate with the an Azure subscription that is using the same work email address under a different directory/organization? I can't find a way to link them. The azure subscription is a sandbox development environment which has an active directory with other members of the company that have their own subscriptions I would imagine. I have discussed this through a support request with Microsoft and there suggestion is to register for a free trial but that isn't possible with a work email address and don't want to go down the PAYG model. I have a support request open with Microsoft 365 and they believe I can link them but I can't see a method for that. I am just learning about this technology through the Microsoft Learn material, so not sure if Azure AD Connect is part of the solution here, and if so if i have permission to create these connections with my azure subscription permissions.999Views0likes1Comment