hotfixHere’s a new MED-V KB article we published this morning that shows you how to use ProcMon to generate a log file for an application in the MED-V virtual environment:

=====

Summary

This article describes how to use the Process Monitor tool (ProcMon.exe) to generate a log file for an application in the Microsoft MED-V virtual environment. The log file provides information about the files and about the registry keys that an application accesses inside the workspace when Process Monitor is running.

More Information

Obtaining and Preparing Process Monitor:

Option 1

1.) If you have not already done so, add in a published Command Prompt shortcut (%SYSTEMROOT%\system32\cmd.exe) in the All Users Start Menu Folder (C:\Documents and Settings\All Users\Start Menu\Programs) in the Windows XP workspace.
2.) Ensure that in the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Medv\v2\UserExperience registry key, the value AppPublishingEnabled is set to 1.
3.) Restart the MED-V Host Agent.
4.) Launch the legacy published Command Prompt.
5.) In the command prompt, trigger the legacy browser (the instance of Internet Explorer running inside the Windows XP workspace) by typing it along with URL:

start iexplore http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx

6.) Click Download Process Monitor (913K), and then click Save. Save to local directory on XP Workspace.
7.) Type “Explorer” in the command prompt. This will bring up an Explorer window inside the MED-V workspace.
8.) Locate and extract Process Monitor.
9.) From the command prompt, navigate to the directory where you extracted Process Monitor and type:

procmon /accepteula /noconnect

10.) On the Options menu, click Enable Advanced Output.
11.) When you are ready to reproduce the issue, start capturing from within Process Monitor. While Process Monitor is capturing, reproduce the issue.
12.) Once you have finished, save the file as PML and place it in the “My Documents” folder inside the workspace.


Option 2

1.) From the MED-V Host computer (Windows 7) download Process Monitor. To do this, visit the following Microsoft Web site:

http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx

2.) Click Download Process Monitor (913K), and then click Save.
3.) Save the file to the host to the current user’s Documents folder.
4.) If you have not already done so, add in a published Command Prompt shortcut (%SYSTEMROOT%\system32\cmd.exe) in the All Users Start Menu Folder (C:\Documents and Settings\All Users\Start Menu\Programs) in the Windows XP workspace.
5.) Ensure that in the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Medv\v2\UserExperience registry key, the value AppPublishingEnabled is set to 1.
6.) Restart the MED-V Host Agent.
7.) Launch the legacy published Command Prompt.
8.) Type “Explorer” in the command prompt. This will bring up an Explorer window inside the MED-V workspace.
9.) Locate and extract Process Monitor (which is located in the “My Documents” folder.)
10.) From the command prompt, navigate to the directory where you extracted Process Monitor and type:

procmon /accepteula /noconnect

11.) On the Options menu, click Enable Advanced Output.
12.) When you are ready to reproduce the issue, start capturing from within Process Monitor. While Process Monitor is capturing, reproduce the issue.
13.) Once you have finished, save the file as PML and place it in the “My Documents” folder inside the workspace.

=====

For the most current version of this article please see the following:

2616986: How to use the Process Monitor tool to generate a log file for an application in the MED-V virtual environment

J.C. Hornbeck | System Center Knowledge Engineer

App-V Team blog: http://blogs.technet.com/appv/
AVIcode Team blog: http://blogs.technet.com/b/avicode
ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
DPM Team blog: http://blogs.technet.com/dpm/
MED-V Team blog: http://blogs.technet.com/medv/
OOB Support Team blog: http://blogs.technet.com/oob/
Opalis Team blog: http://blogs.technet.com/opalis
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
OpsMgr Support Team blog: http://blogs.technet.com/operationsmgr/
SCMDM Support Team blog: http://blogs.technet.com/mdm/
SCVMM Team blog: http://blogs.technet.com/scvmm
Server App-V Team blog: http://blogs.technet.com/b/serverappv
Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials
WSUS Support Team blog: http://blogs.technet.com/sus/

clip_image001 clip_image002