Why is it important to Become Familiar with WMI Troubleshooting? Pt. 1

Often in Virtualization and Management Products like SCVMM, MED-V, Config Manager, UE-V, and App-V the symptom of an issue appears in the respective System Center or MDOP product but the root cause is often caused by an anomaly in an underlying operating system component. Often that component is WMI. For this reason, it is invaluable have…


The Case of the Ever-Expanding, Dynamically-Expanding VHD

I recently had an issue where I encountered something quite bizarre. In an effort to reduce size on disk of dynamically expanding virtual hard disks (VHDs) I found myself feeling like I needed to take medication. After sysprepping an operating system image on the disk, the current file consumption on the disk was approximately 12…


Running a MED-V application that depends on presence may not properly show presence when hovering over it in the System Tray

Let’s review some basic information about how MED-V: The way MED-V V2 works is the Windows 7 host machine connects to the Guest Virtual PC through an RDP-style connection. This basically turns the Windows XP Virtual PC into a mini-RDP server. This must always be in the back of your mind while you test your…


MED-V V1 Disaster Recovery

Disaster recovery in MED-V v1 is a very straight-forward and seamless process. Offline access is available for those clients who have already cached their MED-V client authentications. One of the first steps in ensuring a good disaster recovery plan for this version of MED-V is to establish continuity through offline access. This will assume all…


Transitioning Blog to Technet – http://blogs.technet.com/b/gladiatormsft

Effective this week, I will be transitioning this blog over to technet. There will be no more direct posts here. there will be only links referencing new posts on Technet. This site will remain up along with all of the existing posts. Transitional Post Below: http://blogs.technet.com/b/gladiatormsft/archive/2011/08/23/app-v-recommended-upgrade-preparations-and-rollback-procedures-when-upgrading-from-app-v-management-server-4-5-rtm-or-sp1-to-sp2.aspx