Turns out that XP Mode is per-user, meaning each user has their own VM/VHD (unless you manually configure things otherwise). This host actually had two VMs on it-one that popped up when my tech logged in, and a different one that popped up when my end-user logged in. Thus, changes made by my tech when she was logged in weren't reflected when she logged out and logged in as the end-user.
D'oh! From: John Hornbuckle Sent: Friday, February 18, 2011 12:23 PM To: NT System Admin Issues ([email protected]) Subject: OT: Windows XP Mode Question Totally not NT-related, but maybe someone can answer. We're using the Windows XP Mode feature on a Windows 7 machine to run an app that doesn't play nice with Win7. It mostly works, but with one problem: The app behaves differently depending on who we're logged into the host computer as. I'm sure I'm totally misunderstanding how XP Mode works, but I don't get how this is possible. I wouldn't think it would matter who you were logged into the HOST machine as-only who you were logged into the GUEST machine as. And the way it looks to me is that there's a special account on the guest machine ("xpmuser") that's used by everyone who accesses the VM, regardless of what they're logged into the host machine as. So theoretically, no matter who's logged into the host, they should see the exact same thing in the guest. But not so. Why for? John Hornbuckle MIS Department Taylor County School District www.taylor.k12.fl.us NOTICE: Florida has a broad public records law. Most written communications to or from this entity are public records that will be disclosed to the public and the media upon request. E-mail communications may be subject to public disclosure. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
