Why just that? Because that’s where things “actually” are located. In Version 5, running Process Monitor as normal will capture access to the actual locations including registry, package store, as well as VFS (Virtual File System) COW (Copy-on-Write) locations. In App-V 4.6 and earlier, if you did not launch process Monitor in the virtual application’s environment (usually through a command prompt) all you would capture related to the virtual application would be operations to file and registry resources outside the virtual environment. The reason behind this is simple: unlike previous versions of App-V, the REAL registry as well as the native file system – NTFS – is used in App-V 5.
You could run process Monitor inside the virtual bubble, but it will not yield you much more results. If – by that question you want to know if you must start an instance of Process Monitor within the virtual application like you did in 4.x – no.
0 kommentar(er)
