The documentation for the FirewallException element states that the Firewall Exception Element "Registers an exception for a program or a specific port and protocol in the Windows Firewall on Windows XP SP2, Windows Server 2003 SP1, and later".
Should I infer from this description that the Wix element is properly supported on Windows Server 2008 R2? The reason that I ask is that when I use the following XML it results in one firewall exception on Windows Server 2003 and Windows Server 2008, whereas it results in two exceptions (one for UDP and the other for TCP) on Windows Server 2008 R2. I really do not need the UDP exception, only the TCP one, and had therefore hoped that specifying the Protocol attribute might have allowed me to restrict the exception, but that appears to have no effect when used with the Program attribute: <File Id="Concentrator_EXE" Name="PCMConcentrator.exe" DiskId="1" Source="$(var.CONCENTRATOR_BIN_DIR)\PCMConcentrator.exe" Vital="yes" KeyPath="yes"> <fire:FirewallException Id="Concentrator" Name="$(var.FW_Concentrator_Exception)" Scope="any" IgnoreFailure="yes"/> </File> Also, given that Windows Server 2008 R2 firewall supports three profile types, i.e. Domain, Private and Public I would like to be able to select all three items, but the FirewallException Wix element only appears to set the Public profile irrespective of the value that I choose for the Scope attribute. Any direction greatly appreciated. Thanks, will ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users