A) Launch compatibility monitor with run time analysis package:
      Kindly follow below steps to install and launch compatibility monitor tool
    

       Step 1: Create a new Folder (e.g. RunTimeAnalysis) and provide full permission to everyone 
                 (Depends on security policies of the organization).

         Step 2 :  Share the folder with everyone ( Depends on security policiesof the organization ).

       Step 3 : Launch Microsoft Application Compatibility Manager from start menu

       Step 4 : Click on File
       Step 5 : Click on New
       Step 6 : Click on Runtime analysis package button in Create a data-collection package screen

        Step 7 : Enter below information in Set up your runtime analysis package screen
                       Name                  : RunTimeAnalysis
                       Output Location : \\ACT6\RunTimeAnalysys ( location mentioned in step 2 )
                       Label                   : RunTimeAnalysis
           Value in output location must be a network path. It doesn’t work with local paths.

     Step 8 :  Save the package in the location that  is being mentioned in step 1 and 2

      Step 9: Click on Finish  to complete the collection package creation.

     Step 10: Double click on the newly created run time analysis package to install the compatibility monitor. Follow the defaults to install the package.

     Step 11 : Press Windows Key +Q . Type “ Microsoft Compatibility Monitor“ in search box.
                   Click on Microsoft Compatibility Monitor  shortcut to launch Compatibility Monitor.

B)   Automatically monitor applications for  compatibility issues :

               1.  Start the Compatibility Monitor tool.
            2. Click on Start Monitoring in the tool.

            3. Test the application with different operations.
            4. Compatibility information/issues are automatically detected during monitoring and are submitted to the ACT database at regular intervals.
                It basically monitors the control clicks and behavior associated with it.

             5. After you finish testing applications, click Stop Monitoring to stop the monitoring and submission of compatibility information

C)  Provide compatibility information for applications.

               1. Start the Compatibility Monitor tool.
            2. Click on Give Compatibility Feedback in the tool.

            3. Find the application (you can also use search box) for which you want to provide the compatibility feedback and input your ratting. Click on submit to send the feedback to ACT database.
          4. You can attach screenshot and comments for the issues by clicking on the Send Details… link of Details column.

              5. You can submit the feedback irrespective of monitoring is on or off. Also you can provide feedback for more than one application.
            6. You can also provide arbitrary feedback on issues like device doesn’t work because of drivers not available etc.  by clicking on Send other compatibility feedback.

D)  Add a new application to the list :

               1. Start the Compatibility Monitor tool.
            2. Click on Give Compatibility Feedback in the tool.

             3. Click on Add an application to the list.

              4. Browse to the application location and select the application to add to the list.
           5. Once application is added to the ACT database you can provide feedback on the newly added application .

Hope this has helped in your day to day work. keep checking for updates..

Ever annoyed with the application not working in APPV infrastructure. Here you go few steps to make life easier.

1.       APPV  CLIENT TROUBLESHOOTING  :

Users not able to see/access application pushed through APPV server in client machine .Below are few steps to crack it.

 a.   Log off and Login :

Logoff and log back to the machine so that application is streamed properly from the APPV server to client machine and ready for testing.
Publishing refresh can be configured during APPV client installation or through APPV client console.

 b.   Clear APPV Client Cache :

Below are few ways user can clear the APPV cache in client machine and then re-stream/publishing refresh from APPV server for accessing the application or getting updates.

 1 -  Delete all the applications from “Applications” node in APPV client console :

  2  -  Delete all the content from %appdata%\SoftGrid Client directory. 
          This clears the APPV user cache..

                        3 -  Open registry (regedit.exe) with admin credentials and navigate to below hive if present.

                                HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\SoftGrid
                                \4.5\Client\ Applications.
                                Delete all the application entries if available.                                 

                     3 -    Remove all applications and file types from the Soft Grid cache :

                              Sftmime.exe remove obj:app /global /complete
                              The person running the above command must have administrative rights on the client PC 

                      4 -   Reset the Soft Grid Client Cache to a Clean State :

                              Logon to the client PC with a user account that has administrative rights.
                              Set the following registry value to “0” and Reboot the client PC.
                              HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\SoftGrid\4.5\Client \AppFS\State

                     5  - In case user's virtualized application portfolio is huge then
                           Soft Grid client cache size needs to be increased .

                          Below are the steps to achieve the same.
                           HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\SoftGrid\4.5\Client\AppFS\State
                                     ( Value=0  )
                           HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\SoftGrid\4.5\Client\AppFS\FileSize
                                     ( Value=4096* *Desired maximum cache size in KB )
                           Reboot the client PC for changes to take effect.                

                    Once APPV client cache is cleared User can stream the applications from APPV server by publishing refresh.
                     Below is a snapshot how user can refresh the server

                     The publishing refresh process can be initiated in three ways:
                            1.  At Login  :  This is the default option selected during App-V Client setup.
                            2.  Manual   :  This can be done thru App-V Client MMC or command line.
                            3.  Periodic :  This allows for DC refreshes to occur in the background at periodic times while the user is logged in.
                      NOTE: The publishing refresh settings can be modified by adjusting the default provider policy in the App-V Management Console.

                      Few other articles which can be helpful: https://blogs.technet.com/b/appv/archive/2009/02/17/a-story-of-a-publishing-refresh-request.aspx

                      Also users can load/refresh the applications using below command lines.
                          Sfttray.exe /refreshall
                          Sfttray.exe /loadall

                       Few other articles which can be helpful: https://technet.microsoft.com/en-us/library/dd835527.aspx

             c.   Repair the virtualized package :

                       In case package is corrupted you need to repair it to fix the virtualized application.
                       When you repair an application, you remove any custom user settings and restore the default settings.
                       This action does not change or delete shortcuts or file type associations, and it does not remove the application from cache.
                       Repair an application
                              1. Move the cursor to the Results pane.
                              2. Right-click the desired application, and select Repair from the pop-up menu.
                              3. At the confirmation prompt, click Yes to repair the application or No to cancel. 

                              Command Line:    SFTMIME REPAIR APP:application       (where application is the name of the application you want to repair.

              d.    Log file troubleshooting :

                      Below are few log files which can be used for analyzing the errors that occurred during the refresh activity or any other operation.

                      1  -  Sftlog.txt ( SoftGrid Client Log File )

                               Description: The main log used for troubleshooting on the SoftGrid client. Provides general information about App-V Client operations and errors.

                               Path :
                                      Windows XP, Windows Server 2003 : C:\Documents and Settings\All Users\Application Data\Microsoft\Application Virtualization Client
                                      Windows 7 , Windows Vista, Windows Server 2008 : C:\ProgramData\Microsoft\Application Virtualization Client

                               Few other articles which can be helpful: 
                               https://social.technet.microsoft.com/wiki/contents/articles/troubleshooting-some-common-publishing-issues-in-microsoft-app-v.aspx
                               https://support.microsoft.com/kb/931585
                               https://blogs.technet.com/b/virtualworld/archive/2007/08/21/its-all-about-the-logs.aspx
                               https://blogs.technet.com/b/appv/archive/2009/01/26/troubleshooting-app-v-with-log-files.aspx
                               https://blogs.technet.com/b/appv/archive/2007/02/06/some-common-softgrid-errors.aspx

                        2 -  Sft-server.log ( SoftGrid Server Log File )

                               Description: Stores messages from the SoftGrid Virtual Application Server.
                               Path: %ProgramFiles%\Softricity\SoftGrid Server\logs

                                Few other articles which can be helpful: https://support.microsoft.com/kb/930871

                        3 -   SftMMC.log ( SoftGrid Management Console Log File )

                                 Description: Logs errors that occur within the SoftGrid Management Console.
                                 Path: %ProgramFiles%\Softricity\SoftGrid Management Console\sftMMC.log

                                 Few other articles which can be helpful:  https://support.microsoft.com/kb/930846

 2.       TROUBLESHOOTING  OSD  FILE  :

            Most of the time a simple modification to the OSD file can fix the issue and can save lot of time.So you should always edit the OSD file in the App-V client cache on the App-V client machine,
            not on the original package OSD file to quickly apply the alternatives for fixing the issue.

            To find cached OSD for an App-V application, go to the Application Virtualization Client Admin console, highlight the Application node in the left hand pane,
            find the desired application in the right hand pane and double-click on it.
            Find the Local OSD File: parameter on the General Tab and copy the parameter. Open the parameter file in a notepad(Admin).

            notepad C:\Users\Public\Documents\Softgrid Client\SoftGrid Client\OSD Cache\b96b1550-e76f-4ff6-83cb-2d253e6114ed.osd

                Below is a sample OSD file and its content  .

              1 .  NAME & VERSION :

                     Combination of Application Name + version should be unique in the APPV server database to be properly deployed to the client machine.
                     These values are used to identify the application in the APPV database. The name value will be the name of the displayed icon for the application.

               2 .  HREF HOST NAME :

                      Verify that the SoftGrid server hostname of the HREF path is valid in user’s  target environment. Hostname is resolved at stream time by the 
                      SoftGrid client to locate the SoftGrid server. A specific hostname, FQDN or an environment variable can be used to resolve to a single server or a load balanced farm.

                       HREF="rtsp://Hostname:554/

                       Below is an example of an HREF tag for an actual application where the client has an environment variable set
                       %SFT_SOFTGRIDSERVER%=Dvnserver.corp.msft and the package files are located in .\Content\MerickRIO_TTY_723_MNT\:
                       HREF="rtsp://%SFT_SOFTGRIDSERVER%:554/MerickRIO_TTY_723_MNT/MerickRIO_TTY_723_MNT.sft"

                        Note: The SoftGrid client installer does not set the environment variable 
                                   %SFT_SOFTGRIDSERVER%.

                         If you choose to use this method, the variable can be set through GPO or a login script.
                         

                         You can make sure if user can ping and telnet the server with below commands.
                         Open a command prompt and type below.
                          Ping %SFT_SOFTGRIDSERVER%
                                   - If ping command is successful it will show the reply messages.
                           telnet %SFT_SOFTGRIDSERVER% 554 ( telnet ServerName Port )
                                   - If telnet command is successful the window will be blank.                 

                        Few other articles which can be helpful:
                        https://blogs.technet.com/b/appv/archive/2011/06/02/understanding-the-sft-softgridserver-environmental-variable-in-microsoft-app-v.aspx
                        https://support.microsoft.com/kb/2552111
                        https://support.microsoft.com/kb/930702

                3 .  HREF PACKAGE  PATH  :

                       Verify that the SoftGrid relative path to SFT file portions of the HREF path are valid in user target environment.
                       The relative path to SFT file is the relative path under the Content repository in which the package directory is located.
                        HREF="rtsp://Hostname:554/<relative path to SFT file>"
                        e.g. HREF="rtsp://%SFT_SOFTGRIDSERVER%:554/MerickRIO_TTY_723_MNT/MerickRIO_TTY_723_MNT.sft"
                        In order to access the package properly there should be a folder named “MerickRIO_TTY_723_MNT” in the content directory 
                        and sft file named “MerickRIO_TTY_723_MNT.sft” under the “MerickRIO_TTY_723_MNT “  folder.

                  4.   TERMINATECHILDREN :

                          A virtualized application may not shut down completely when user  exit the application in Microsoft Soft Grid. If a virtualized application fails
                          to shutdown properly or causes anomalies with the OS when the application is shutdown, try setting the following value to TRUE.
                          <VIRTUALENV TERMINATECHILDREN="TRUE">

                          Few other articles which can be helpful: https://support.microsoft.com/kb/931589

                   5.    LOCAL_INTERACTION_ALLOWED :

                           When the value is TRUE , it disables the virtual eventing. This enables creation of named objects (events, mutexes, semaphores, file mappings,
                           and mailslots) and COM objects in the global namespace rather than isolated inside a particular virtual environment,
                           which allows virtual applications to interact with the host operating system's applications. This can solve issues when application interacts with the native client components inappropriately blocked.

                            Few other articles which can be helpful:
                            https://blogs.technet.com/b/appv/archive/2007/09/20/a-look-under-the-covers-the-local-interaction-allowed-tag.aspx
                            https://blogs.technet.com/b/deploymentguys/archive/2011/07/05/allowing-better-interaction-to-app-v-virtual-applications.aspx

                    6.     WORKINGDIR :

                             The WORKINGDIR element offers control of the current working directory in virtual environment from within the OSD. 
                             Sometimes the working directory parameter can cause problems, as a test try removing the value altogether.
                             <WORKINGDIR></WORKINGDIR>
                             This is an optional element and is only read by the client.

                              Few other articles which can be helpful:  
                              https://blogs.technet.com/b/virtualworld/archive/2007/11/07/workingdir-examples-specifying-a-working-directory.aspx

                     7.     SUBSYSTEM VALUE :

                              The SubSystem element gives the APP-V client another clue about the type of display that the FILENAME uses so that it can properly launch it.
                              The inline VALUE element indicates if it is a windows or console (DOS).

                               Few other articles which can be helpful:
                               When launching an application virtualized using Microsoft App-V, the application hangs for 10 minutes and then terminates:
                               https://support.microsoft.com/kb/2195120
                               A known good App-V virtual application package may fail with error 19-00001003 after adding a pre-launch script :
                               https://blogs.technet.com/b/appv/archive/2011/10/20/a-known-good-app-v-virtual-application-package-may-fail-with-error-19-00001003-after-adding-a-pre-launch-script.aspx

                   8.      OS VALUE :

                             The OS element is used to specify the operating system the package can run. When no OS tag is included in IMPLEMETATION block,
                              this means the associated .sft can run on any operating system. The values are case sensitive.
                                      < OS VALUE="Win2003TS"/ >
                                      < OS VALUE="WinXP"/ >
                                      < OS VALUE="Win7"/ >

                              Few other articles which can be helpful:
                              https://blogs.technet.com/b/appv/archive/2009/10/29/updated-os-value-xml-tag-reference-and-supported-client-versions.aspx
                              https://blogs.technet.com/b/appv/archive/2008/10/29/error-xxxxxx44-00001007-in-the-sftlog-txt-file.aspx

               Apart from verifying OSD file information inspect the .SPRJ file and verify the <SHORTCUT Path> tag(s) point to the correct names of the OSD file(s) in the package.
              <SHORTCUT Path="TextPad_4.0.7.3.osd"/>

             Few other articles which can be helpful:
              https://blogs.technet.com/b/appv/archive/2012/04/25/app-v-application-is-not-working-as-expected-troubleshooting-check-list.aspx
              https://blogs.technet.com/b/virtualworld/archive/2007/11/14/softgrid-operations-guide-part-1.aspx
              https://support.microsoft.com/kb/940163/
              https://technet.microsoft.com/en-us/library/cc843805.aspx
              https://download.microsoft.com/download/f/7/8/f784a197-73be-48ff-83da-4102c05a6d44/AppPubandClientInteraction.docx

3 .    ADVANCE TROUBLESHOOTING :   

         If your package is still not working properly after the above mentioned aforementioned tips and tricks, grab a cup of coffee and try below advanced troubleshooting options . 

         1.   Troubleshoot using command prompt or Explorer in APPV bubble :

                Try different alternatives or fixes using different debugging tools in virtual command prompt or check the virtual package contents from virtual explorer and perform fix activities.
                To open a command prompt or explorers in virtual bubble follow below activities.
                Create a shortcut to the virtualized application shortcut in desktop. 

               Once shortcut is created go to the properties and Edit the shortcut to launch a command prompt inside the App-V bubble.

                   Right-click on the newly created shortcut on your desktop and choose Properties.Edit the Target: text to include the string /exe cmd.exe between Sfttray.exe and /launch.
                   e.g.                 "C:\Program Files (x86)\Microsoft Application Virtualization Client\sfttray.exe" /exe cmd "Rio 3.6.2010" (If you want to open the virtualized command prompt.)
                                          "C:\Program Files (x86)\Microsoft Application Virtualization Client\sfttray.exe" /exe explorer "Rio 3.6.2010" (If you want to open the virtualized explorer.)

             2 .  Startup Process Monitor in virtual bubble :

                 One of the much handy debugging tool to fix the windows/APPV issues is Process Monitor which logs the file system, registry, network activities etc.
                 To open a Process Monitor in virtual bubble follow the below steps :
                 Open the command prompt in the bubble ( check previous section for more information ).
                 From the command prompt, type the full path to Procmon.exe to launch it (for example c:\temp\procmon.exe).Procmon will have full access to changes occurring inside the bubble at this point.

                 ProcMon.exe /externalcapture can be ran directly from Explorer to capture data from applications running under App-V without first launching a command prompt in the bubble.

              Few other articles which can be helpful:
              https://blogs.technet.com/b/appv/archive/2012/04/24/how-to-run-process-monitor-procmon-inside-the-app-v-virtual-environment.aspx

Hope all these tricks and information will bring every virtualized techy's smile back :) ..... Keep watching for the next post...

Let’s demystify these terms which turns every geek’s smile to a confused novice.

As the saying goes “Every change is for something good” ,Windows 7 features are meant for user friendly , process improvement  and security experiences. Changes in UI , access permission level, user’s data related folders have helped in achieving the appreciation among the community and users. 

 Below are few information/solutions which make Windows 7 experience very user friendly, ease to use and secure.

 1.   User Access Control (UAC) :

 Many a times user is prompted with UAC during software installation or for application specific operations.

 By default, when Microsoft Window XP is installed on User machine, the Windows XP Setup creates all user accounts as local administrators. This type of users can       install,      update,      and  run software since an administrator account has system-wide access. When a user is added to the local administrators group, that user is automatically granted every Windows privilege. Once user get admin privileges it is very easy for any security attacks as all applications runs with admin privileges. So in order to mitigate the impact of security attack such as malwares etc. all users should run as standard user.

  A standard user on a Windows XP computer must use Run as or log on with an administrator account in order to install/uninstall applications. There was no built-in method within the Windows   operating system for a user to “elevate” in flow from a standard user account to an administrator account without logging off, using Run as or switching users. So most user continue to browse the Web as an administrator which opens the gate for security attack. With the introduction of UAC in Vista and Windows 7 this security vulnerable has been overcome. With the built-in UAC elevation component, standard users can easily perform an administrative task by entering valid credentials for a local administrator account.   

UAC is by default enabled in Windows 7 . As a result, user  might encounter some compatibility problems with different applications that have not yet been updated for the Windows 7 UAC component. If an application requires an administrator access token user can run the program as an administrator by using the Run as administrator option on the context menu (right-click).

 In extreme situation, though it is not recommended, user can disable UAC through the User Account tool in the Control Panel. You've to reboot after the changes. Also through registry settings user can disable it. HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System

Users have to set EnableLUA to 0.

   Some of the useful sites regarding UAC - https://windows.microsoft.com/en-US/windows7/products/features/user-account-control

2.   Visit the Windows 7 compatibility Center

         Perform the below task to get more information regarding the Windows 7 compatbility of the software/application/drivers/devices.

              a)     Determine which software and devices are and are not compatible with Windows 7. Also visit the vendor site to get more information.

              b)     Locate links to drivers and upgrades that will make your computer/application compatible.

         Windows 7 compatibility ceter - https://www.microsoft.com/windows/compatibility/windows-7/en-us/Default.aspx?type=Software

3.   Run the program as an administrator

Does an application not work properly or does it throw error message every time it is used, try to run it with additional rights. By default, an application is not started with those additional rights, but this can be done manually by right clicking (the shortcut to) the application and to select Run as administrator. Those administrator rights can also be added by default by right clicking the shortcut to the application and to select Properties, tab Shortcut, Advanced button and to activate the option Run as administrator.

     Some of the useful sites - https://technet.microsoft.com/en-us/magazine/ff431742.aspx

4.   Limited Permission Issue

 Sometimes user is denied access to store/write to certain restricted locations.
The issues concerning the limited permissions are related to administrator rights. Without the permission to modify files in a certain location, an application is not able to save a file in this folder (e.g. C:\Program Files). In most cases this problem can be solved by running an application with administrator rights. A better alternative is adding permissions to modify the concerning folder. This cab be done by right clicking the folder and then Properties, Security tab,  Edit button(or the button Advanced) and provide Full control for the concerning user account.

5.   Compatibility issues with older software

Windows 7 manages the running applications differently as compared to previous windows platforms. This might cause compatibility issues for old software/applications. Few of the issues can be solved by running the application with “Widow XP compatibility mode”. Below are the steps to achieve the same.

 Application -> Right Click -> Properties -> Compatibility tab -> select the compatibility mode from the dropdown - > check “Run this program in compatibility mode for” option.

    For more information regarding compatibility mode please refer below sites.
          https://windows.microsoft.com/en-US/windows-vista/Make-older-programs-run-in-this-version-of-Windows
          https://windows.microsoft.com/en-US/windows7/install-and-use-windows-xp-mode-in-windows-7

 6.   Virtual Store

 In Windows 7, many folders are made secured , which makes it impossible for an application/malware to make changes to the files in the folders. e.g. the folder C:\Program Files is secured. An application with administrator rights can only modify the files. Many older applications continuously try to store/modify files in this folder. To solve this issue, Windows 7 uses virtualization of files i.e. files will be stored in the Virtual Store. The applications are not aware of this virtualization, and thinks the files are stored on the same location. Virtualization is done separately for every user .Files are stored in C:\Users\<loginname>\AppData\Local\VirtualStore location.  Program Files is one of the folders in the Virtual Store, which contains the user specific settings for the applications. All users must change the settings of the virtualized applications separately. This is an advantage as well because the changes won't affect the other users. In case user wants to disable virtualization they can do it by providing  Full Control to the specific folder or by running the application with admin privileges

               . 

      Few useful liks - https://social.msdn.microsoft.com/Forums/en/windowscompatibility/thread/a432f1ab-4b0c-439c-b20a-f35e2c0d18a3

 7.   Troubleshoot Compatibility

       Sometimes applications running in Windows XP or Windows Vista throws error on Windows 7. Windows 7 has a little-known feature that helps you troubleshoot application compatibility. Here's how to use it:

         a)     Right-click the shortcut of the app that's not working properly, then click Troubleshoot compatibility. 

        b)      Windows will try to detect compatibility issues, then give you two options: Try recommended settings and Troubleshoot program. 
                I recommend trying the first option first; if it doesn't work, you can always return and try the second (which gives you the choice of which previous version of Windows you want compatibility with).

          c)       After Windows applies the selected settings, click Start Program and see if that solves the problem. Either way, click Next to have Windows apply the settings "permanently" or try again with

                 different settings.

8.   Program Compatibility Assistant( PCA )

The Program Compatibility Assistant prompt appears if a software, device or driver didn't register correctly in Programs and Features in Control Panel during installation.

The Program Compatibility Assistant (PCA) runs automatically and detects known compatibility issues in older programs. During the installation of older software/application in Windows 7 , PCA notifies the user  if there is a problem and offers to fix it the next time you run the program. User needs to apply the settings by clicking on “Reinstall using recommended settings” option. By applying the settings, no changes are made to the program, itself. for example, the PCA can resolve conflicts with User Account Control(UAC) , it can run the program in a mode that simulates earlier versions of Windows. The changes that Program Compatibility Assistant makes are done automatically, so users don’t need to make them.  If the compatibility issue is serious, the Program Compatibility Assistant might warn you or block the program from running.  Use “This program installed correctly” option to close the Program Compatibility Assistant.

Though it is not recommended, PCA can be disabled from the following location - Start -> Run->gpedit.msc - >Administrative Templates ->Windows Components->Application Compatibility ->"Turn of Program Compatibility Assistant"  policy

PCA runs automatically but there is one more option where user can run "Program Compatibility Wizard" manually for fixing the compatibility issues . location for the same -
Control Panel->Programs -> Under Programs and Features ->Run programs made for previous versions of Windows

Few useful links-
         https://windows.microsoft.com/en-US/windows7/Program-Compatibility-Assistant-frequently-asked-questions
         https://blogs.technet.com/b/askperf/archive/2007/10/05/the-program-compatibility-assistant-part-one.aspx
         https://blogs.technet.com/b/askperf/archive/2007/10/05/the-program-compatibility-assistant-part-two.aspx

9.   Shims

Shim Technology is an elegant technique that is used to fool some applications into running on versions of the operating system they may not have been designed for. It’s a method of 'hooking' the Win32 APIs that are called by a particular application program. Once installed, such hooks permit developers and support engineers to install alternate (stub) functions to be called in place of the original functions. The actions taken by the stub function comprise the fix for a particular application compatibility problem.

There are around 360 plus shims currently available. Shims can be applied for different compatibility issues like OS version lie, registry fix, correct file path etc. Some of the important shims are RunAsAdmin, RunAsHighest, CorrectFilePaths, and WinXpSP2VersionLie etc…

              For more information regarding shims please refer:  https://technet.microsoft.com/en-us/library/dd837644(WS.10).aspx

10.  Advanced Options for troubleshooting

Below are few tools which can be used for advance debugging and fixing application compatibility issues.

     i)       Application Compatibility Toolkit ( ACT ) :

             ACT is a used to support older version of applications in latest windows OS. It solves the compatibility issues of the newer windows application platforms. 
             For example, the windows 7 OS will not  allow IEV6 to get installed in it. But using this tool kit you can install and use the IEV6 in windows 7.   
             Few versions of ACT – ACT 4.1, 5.0, 5.5,5.6 etc.

          Few useful links -
            https://msdn.microsoft.com/en-us/library/dd562082(VS.85).aspx
            https://technet.microsoft.com/en-us/library/cc722055(WS.10).aspx

ii)         Least-privileged User Account (LUA)

       The LUA approach ensures that users follow the principle of least privilege and always log on with limited user accounts.
          This strategy also aims to limit the use of administrative credentials to administrators, and then only for administrative tasks.          Few useful links -
             https://technet.microsoft.com/en-us/library/cc700846.aspx                 
             https://technet.microsoft.com/en-us/edge/ff944922
iii)         Sysinternals tools

           Sysinternals tools is a suite of tools which helps in revealing rootkits, provide kernel level information ,track down and terminate runaway processes,
           remove unwanted   programs   from system start up and provide registry level information for troubleshooting etc.

           Few important tools are – Process Monitor , debug view, Pskill, Logon Sessions etc.

             Few useful links - 
                      https://technet.microsoft.com/en-us/sysinternals/bb842062
                      https://technet.microsoft.com/en-us/sysinternals/default.aspx

 iv)         Windows Debugger (WinDbg )

          The Microsoft Windows Debugger (WinDbg) can be used to debug both user-mode and kernel-mode programs. It uses Microsoft Visual Studio debug symbol formats for source-level debugging.
          It displays function names and variables for any modules compiled using the COFF (common object file format) linker option. It permits you to do the following:

                    a.  Step through your program, viewing the source code
                    b.  Set breakpoints in your code 
                    c.  View CPU registers and flags
                    d.  View a disassembly of your program
                    e.  Watch the values of program variables 
                    f.  View the runtime stack
                    g.  Display blocks of memory
                    h.  Perform remote debugging across a network

                     Few useful links - https://www.microsoft.com/whdc/devtools/debugging/installx86.mspx

        Hope all these tricks and information will bring every app-compat techy's smile back :) ..... Keep watching for the next post "ACT ,  ProcMon & IE Compatibility  in Nutshell …”