For applications to receive the Certified For Windows Vista or Certified For Windows 7 logo, the application must be designed to work well for standard users unless the tool is specifically intended for use by administrators . However, many applications were developed prior to Windows Vista and will not work correctly with UAC enabled. These might include some older antispyware, antivirus, firewall, CD/DVD-authoring, disk-defragmentation, and video-editing tools designed for Windows XP or earlier versions of Windows .
Typically, most features of an application will work correctly with UAC enabled, but specific features might fail. You have several ways to work around this:
■ Run the application with administrator credentials As described in the section titled "How to Control UAC Using Application Properties" earlier in this chapter, you can specify that an application always requires administrator credentials.
■ Modify permissions on the computer If an application requires access to a protected resource, you can change the permissions on that resource so that standard users have the necessary privileges. Instructions on how to isolate the protected resources are provided later in this section .
■ Run Windows XP (or an earlier version of Windows) in a virtual machine If the application fails with administrative privileges or you do not want to grant the application administrative privileges to your computer, you can run the application within a virtual machine . Virtual machines provide an operating system within a sandbox environment, allowing you to run applications within Windows XP without requiring a separate computer. You can maximize virtual machines so that they display full screen, providing a similar experience to running the operating system natively. Virtual machines perform slightly slower than applications that run natively within Windows, however. Windows 7 Professional, Enterprise, and Ultimate operating systems include Windows Virtual PC and the Windows XP Mode environment. For more information about virtual machines, read Chapter 5, "Testing Application Compatibility."
■ Disable UAC You can disable UAC to bypass most application compatibility problems related to the permission changes in Windows Vista. However, this increases the security risks of client computers when running any application, and therefore is not recommended. To disable UAC, read the section titled "How to Configure User Account Control" later in this chapter.
To isolate the protected resources accessed by an application, follow these steps:
1. On a computer running Windows 7 with UAC enabled, download and install the Microsoft Application Verifier from http://www.microsoft.com/downloads /details.aspx?FamilyID=C4A25AB9-649D-4A1B-B4A7-C9D8B095DF18&displaylang=en.
2. On the same computer, install the ACT, which you can download at http://go.microsoft.com/fwlink/?LinkId=23302.
3. Start the Standard User Analyzer (which is installed with the ACT). On the App Info tab, click Browse and then select the application's executable file.
4. Click Launch and then respond to any UAC prompts that appear. The Standard User Analyzer will start the application. Use the application, especially any aspects that might require elevated privileges, and then close the application .
5. Click the View menu and select Detailed Information.
6. Wait a few moments for the Standard User Analyzer to examine the application log file, as shown in Figure 24-5. Browse the different tabs to examine any errors . Errors indicate that the application attempted to perform an action that would have failed if it were not run with administrative privileges .
i Standard User Analyzer | ■=> H B jBïa 1
File View Options Mitigation Help
Was this article helpful?