We have an install that supports all OS's except for Win9x, WinNT and Windows 2000. We set this all up though Project Assistant - Installation Requirements and the condition looks like the following: (Not Version9X) And (Not VersionNT=400) And (Not VersionNT=500) Now we have decided that this app will NO longer support Vista and therefore in the Installation Requirements I unselected Windows Vista and the new condition looks like the following: (Not Version9X) And (Not VersionNT=400) And (Not VersionNT=500) And (Not (VersionNT=600 And (MsiNTProductType=1))) So the new entry: And (Not (VersionNT=600 And (MsiNTProductType=1))) basically states that to not install if VersionNT is 600 and it's MsiNTProductType is 1, which means it is Windows 2000 Professional and later. The MsiNTProductType can be: 1 - Windows 2000 Professional and later 2 - Windows 2000 domain controller and later 3 - Windows 2000 Server and later So it looks basically correct as Vista should be under (1) as a Windows professional version and not a domain controller or server. But the issue is if I then go back to Project Assistant - Installation Requirements I notice that Windows 2008 Server is no longer selected. This condition seems to have turned off Vista and Windows 2008 Server. So I just want to confirm that this condition will make it so that it does not install on Vista, but if ran on 2008 Server that it would still install. Not that any of our customers will, but I just want to verify. So will this condition work as expected or do I have to manually change it to work as expected? Thanks, ... View more

I am using the System Search to find a file .exe that has a specific version range. So I set the Minimum version to 11.1.0.0 and Maximum Version to 11.1.999.0 so that it will, if the file exist within that version range, set the FILE_FOUND property. Now I am doing testing on this property and my first test was to install on a system that has this file installed with the version number of 11.0.579.0. The property got set even though the version of the file does not fall within the min/max range. Why did this not work in this case? I tryed with a few more apps that had to be looked for and again I am installing on a system with all the .exe file version lower than the Min version entry and again all of the properties were set as if it passed the versioning check. So am I doing something wrong in the App search and therefore it is ignoring the version check and just setting the property because it found the file? If this is the case then how do I get it to correct use the versioning range for the condition to set the property? Thanks for any help. ... View more

We have an install that has some public properties that are defaulted to 1 that will enable some custom actions to be triggered. If the admin does not want these custom actions to trigger then they set these 2 properties to 0 and push them to the installer. Now this works correctly as expected, but we have now ran into an issue where we created a hotfix patch (.msp) for our product that simply only has some file changes and then when we apply this patch it seems that the 2 custom actions that were not triggered in the original install are suddenly triggered in the patch. Checking it looks like the patch simply used the default values of these properties and therefore triggered these custom actions. So I would like to know why the patch did not use the cached value of these properties? How do we prevent propeties that were changed from default re-verting back to default on a patch/minoro upgrade? Any help with this would be appreciated. Thanks, ... View more

Has anyone started looking at installs on Windows 8 and the new Metro interface? We have just started noticed some issues already with icons desktop shortcuts... What kinds of issues can we expect and work arounds that we would have to support before an updated IS can come out? Thanks, ... View more