Windows XP Mode VM Credentials on Windows 7

Okay, this may be a stupid question, but I'm going to ask it anyway.  I have recently made the move to Windows 7 SP1 for my primary development machine, with only a few "hiccups" along the way.  I've finally gotten all of my development tools installed, but due to the fact that I have a number of legacy applications written in VB6 that are still requiring programming modifications from time-to-time, I've found that the best solution for my environment is to install the Windows XP VM with a copy of the VB6 IDE for compiling new executables from that code.  Yeah, I know that there's a "backwards compatability" library available, but this method really seems to be a better solution for my situation for now.

Anyway, to the question.  After a bit of shoe-horning, I was able to get the XP VM joined to the domain to provide access to all of the network resources I require for development.  The only thing is that, anytime the window for my VM is "refreshed" (e.g., when the full screen window is restored down, or vice-versa), I'm prompted for my domain credentials over and over again.  Is it possible to simply have the VM use the domain credentials from my already logged on Windows 7 machine?  I can't really have it save the password due to password security policies in place that will require a password change every few months, so I'm trying to find a more effective solution.  Thanks for your input.
LVL 2
G_Hosa_PhatAsked:
Who is Participating?
 
cwstad2Commented:
looks like it is an inherent problem from virtual PC. Quote from MS own web page. Great advice lol

When I try to resize the virtual machine window, a logon screen appears.

Cause: Windows Virtual PC reconnects to the session each time you try to change the window size. This occurs when there is an error while trying to reconnect to the session.

Solution: Close the virtual machine and then open it again.
0
 
cwstad2Commented:
Hi there this looks like a well documented problem i found this. looks like credential manager is the only way to store the password. Hope this helps

http://social.technet.microsoft.com/Forums/en-US/w7itprovirt/thread/a4e3bb1e-438e-413d-a546-a5b301a0965b
0
 
G_Hosa_PhatAuthor Commented:
@cwstad2 -Thanks for the link.  Yeah, that's kinda what I've seen as well, but I don't know if that's going to work for me due to my domain password policy.  My concern would be my VM locking me out of my domain account if I've changed my domain password.  I've seen similar situations occur with stored credentials for users on laptops connecting to mapped drives if they've recently updated their password getting locked out.  One would think that MS would've made it possible to just check a box for something like "Use my current credentials", or something.  I'm going to keep digging a little more as well.
0
Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
cwstad2Commented:
Why not make a separate account but with password never expires, and using that with the VM
0
 
G_Hosa_PhatAuthor Commented:
Why not make a separate account but with password never expires, and using that with the VM
I can do that, I suppose.  I had thought of that, although, IMHO, it seems a bit of a sledgehammer method to provide what I would think is a thumbtack situation.  Of course, to me it seems that, due to this "issue" I'm running into, MS's implementation of this seems a bit poor to begin with.  I love the fact that it's available at all, so I don't suppose I should complain too much.  This is just one of those little annoyances that really seems silly to be experiencing at all.

I found some additional information on MED-V, which looks basically like a "beefed-up" version of the basic XP Mode functionality for running individual applications (see http://www.microsoft.com/en-us/windows/enterprise/products-and-technologies/mdop/med-v.aspx).  Personally, though, not thinking that's a great solution either as the whole reason I started down this path was to basically get out of Windows 7 to prevent some of the strange versioning issues with ADODB connections created within my VB6 code after Win7 SP1 was installed.  Hopefully I'm going to be getting out of VB6 entirely at some point when I completely rewrite the application in .NET anyway, but that's currently a long way off with all of the other projects queued up right now.
0
 
cwstad2Commented:
if you dont necessarily want to use xpmode the try virtul box. Its free and very good

https://www.virtualbox.org/

VirtualBox is a powerful x86 and AMD64/Intel64 virtualization product for enterprise as well as home use. Not only is VirtualBox an extremely feature rich, high performance product for enterprise customers, it is also the only professional solution that is freely available as Open Source Software under the terms of the GNU General Public License (GPL) version 2. See "About VirtualBox" for an introduction.
0
 
G_Hosa_PhatAuthor Commented:
Hmmm.  Interesting thought.  I'll definitely look into this one.
0
 
cwstad2Commented:
you should, its very good
0
 
cwstad2Commented:
If you feel the information has been useful then please feel free to rate.
0
 
G_Hosa_PhatAuthor Commented:
Well, I determined that, because I don't need to use my XP VM all that much (really only for compiling my VB6 code), and I unfortunately don't have a lot of time to really test the other solution, I'm just going to leave things as is.  I may look into Virtual Box later when I have a little more time to play with it.  Thank you for your assistance.  All points awarded to you.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.