The Problem:

Sometimes installers for Windows applications add rules into the local Windows Firewall configuration.

When repackaging these applications, consideration must be made as to if those rules should travel with the package and be implemented in the end-user configuration of the local firewall, or if they should be excluded, and dealt with by policy.

The Microsoft MSIX Packaging Tool accidentally excludes these during the capture, resulting in packagers not being aware when an application expected the support.

The Solution:

Using new cmdlets added to our PassiveInstall powershell module in the wrapper script used to custom install the application during repackaging, we can force the rules to be captured.

The MSIX Packaging tool will now have the registry entries, but not make use of them in the new AppXManifest schema extensions.  But this makes them application request visible to our TMEditX software.  Based on TMEditX policy, or manual selection, you can choose to add the necessary entries into the AppXManifest (with a push of a button). 

Even if you leave them out of the AppXManifest, it still highlights what rules were desired by the application and you can work with the security team to get them implemented in policy.

Windows Firewall Rules and MSIX Packages.pdf