Cab Window
Cab Window ...girls would you ride in a 1992 ford ranger 4.0 extended cab, white w/ window tint, black rims,flowmaster-? exhaust, aftermarket pioneer cd player, and the seats redone? i dont know ...
Cab Window
![Microsoft Office Student and Teacher Edition 2003 [OLD VERSION]](http://www.apexmoulding.com/media/images/i/21Zx%2BiBClzL._SL75_.jpg)
Msi Integration Into Vista and Windows 4.0
Whereas previous Msi releases used to be backward-compatible, the new Msi 4.x version - which was developed to integrate with new Vista features (e.g. UAC, RM, WRP, etc.) - is not redistributed for down-level systems. Instead, Microsoft’s new release enables down-level systems to simply ignore the reference to the new Vista features, thus allowing full compatibility of packages created by Msi 4.x.
Still, a good developer must know how to use the UAC and Msi 4.0 integration in Vista, in order to create a better user-experience.
Here’s a list of behavior tips that you can refer to while creating packages for Vista:
- Try as much as possible to use Msi packages rather than “setup.exe”.
Note: If you need to perform a “Silent Install”, it is impossible to install a package marked as “requiring admin credentials” from an un-elevated process”!!
- Although most Installs indeed require elevated privileges when running under UAC, you can mark packages as “not requiring credentials” by setting the “Word Count” (MsidbSumInfoSourceTypeLUAPackage) in the “Summary Information Stream” from 4 to12.
- As described in one of my previous Blogs, Windows Vista is checking the signature on Windows Installer Packages. The signature information is displayed in a “UAC dialogue”. It’s highly recommended to also sign any CAB file included in your package.
- Any name of an application which includes the words “setup”, “install”, “update” or “patch” is automatically marked by Vista as requiring elevated privileges (a shield will appear on its icon), even if the application’s manifest doesn’t include such information or doesn’t exist at all. This behavior derives from the UAC and the user will probably think twice before double-clicking this application.
- Credential prompt-free patching or “sticky elevation” can be used for packages that their “MsiDigitalCertificate” and “MsiPatchCertificate” tables were authored to include the certificate file which builds the digital signature, in both the original package and the patch. The patch will be able to execute silently.
- Adding the “shield” icon to UI – The new “shield” icon is used to indicate that elevation is required.
Note: By adding the “shield” icon to the last button, you will be simplifying the experience of the installation user, sparing him from encountering the “UAC dialogue”, which usually prompts a few seconds after he completes the “UI interview”. It is such a bad experience for a user when he gets notified that elevation is required after he clicks on “install/remove”. - Due to the UAC integration into Vista, “AdminUser” property equals to true at the “UI sequence”; a fact which might cause failures during the “LaunchConditions” CA, when verification is needed to whether the user is a full admin. You can avoid this situation by using the “MSIUSEREALADMINDETECTION” property, which was added in Msi 4.x.
Note: The entire “UI sequence” runs under the user context and might include elevated actions.
- Automatic logging may be used after populating the “EnableMsiLogging”. You may select the log files location by populating the “MsiLogFileLocation” property.
Note: This feature can be enabled / disabled when the “DisableLoggingFromPackage” policy is used.
This article was written by Albert Shamsiyan, Technology business developer, and one of the writers at www.easysetup.org blog, sponsored by www.pantaray.com.
About the Author
Albert Shamsiyan, is an expert in MSI development.