Learn how to a build a cloud-first strategyRegister Now

x
?
Solved

virtual server 2005 - can not use cached account details

Posted on 2008-11-18
12
Medium Priority
?
1,038 Views
Last Modified: 2012-05-05
Using Microsoft Virtual Server 2005 on a Vista Buisness Laptop, remote from office (and hence domain controller).
I have a domain account with local admin rights, and for all normal purposes it validates my password using locally cached security information when away front he office network.
However, last night I set-up Virtual server (I previously used Virtual PC) and successfully fired up several virtual machines. But when I set one of them to start automatically, using specified account, it refuses to start; giving the error:
"The virtual machine could not be started. The account name and password are invalid"
I have worked around this by creating a new local admin  account (which Vista allows me to do away from the domain controller) and using that.

Can anyone explain what is happening here? Is the problem:
- Vista needs to connect to domain controller to validate a domain account
- Virtual Server needs to connect to domain controller to validate a domain account
- Would it work OK if I had run it once whilst connected to the domain controller?

0
Comment
Question by:dcp002
  • 6
  • 6
12 Comments
 
LVL 2

Expert Comment

by:hughespat57
ID: 22989478
Virtual server must authenticate the user to a DC if it is a domain account.

You can create a local user just to run the VMs as you did. It does not need to be an admin account however, it just has to have full rights to the VM configuration files and the VHDs

It will not work with any cached credentials.
0
 
LVL 2

Author Comment

by:dcp002
ID: 22992826
Thanks for comment.
The local account allowed me to manually start the virtual server.
However, if I set the server to automatically start under this account, it has no network access. (Just says network cable is disconnected).  Starting manually, not referencing this account, and it works OK.

The reason I was doing this was an investigation into the possibility of running a Windows Server Small Business Server as a virtual machine in the event of a disaster recovery situation. In that situation, the domain controller which is on the SBS would not be available until AFTER the virtal server was running -with network access.  So it looks like in the disaster recovery situation, if this approach was adopted, it would not be possible to have the virtual server auto-start on re-start of the host pc?
0
 
LVL 2

Expert Comment

by:hughespat57
ID: 22994567
In addition to the folder where the VM VHD files are kept grant full permissions on the host to the default folders:

C:\Documents and Settings\All Users\Documents\Shared Virtual Machines
C:\Documents and Settings\All Users\Documents\Shared Virtual Networks

The network folder is what is stopping you right now.
0
Fill in the form and get your FREE NFR key NOW!

Veeam is happy to provide a FREE NFR server license to certified engineers, trainers, and bloggers.  It allows for the non‑production use of Veeam Agent for Microsoft Windows. This license is valid for five workstations and two servers.

 
LVL 2

Author Comment

by:dcp002
ID: 22998683
Is there any accont I can use on the host PC that would enable automatic startup of the virtual domain server, where the host pc is a member of the domain managed by the virtual server ?
0
 
LVL 2

Expert Comment

by:hughespat57
ID: 22999466
Not sure I follow that question, are you saying if the virtual server is the domain controller?
but maybe this example will explain, this is our production environment:

I have:
VSHOST1 (physical system) Windows 2003 R2 SP2 64 bit Two Dual core AMD, 10GB RAM - HP DL145
       hosts guest VMs:
               ADC1 (Windows 2003 R2 SP2 32 bit - Active Directory Controller, master, FSMOs, DNS, DHCP )
               PS1   (Windows 2003 R2 SP2 32 bit - print server)
               Netmanage (Windows 2003 R2 SP2 32 bit - WSUS, WDS-RIS)
VSHOST2 (physical system) Windows 2003 R2 SP2 64 bit Two Dual core AMD, 10GB RAM - HP DL145
       hosts guest VMs:
               ADC2 (Windows 2003 R2 SP2 32 bit - Active Directory Controller, secondary, DNS, DHCP)
               Netmanage2 (Windows 2003 R2 SP2 32 bit - AntiVirus Master, othe IIS network services )

If both VSHOST systems reboot at the same time (such as during patch management maintenance windows) then the VMs can NOT auto-start because there is no active DC to authenticate a domain user against.
So I set ADC1 and ADC2 to use local accounts created for them alone on VSHOST1 and VSHOST2 respectively.
All other VMs use a domain account that is explicitly for VMs only.

The local account can be either a member of the local system administrors group (not neccessary but easier) or a special user with the file permissions as described previously.

Remember this user does not have any rights to/on the guest VM after it starts. I just has to have sufficient rights on the physical host to start the VM up. Access to the configuration files and vhd files.

0
 
LVL 2

Author Comment

by:dcp002
ID: 23002525
You say:
So I set ADC1 and ADC2 to use local accounts created for them alone on VSHOST1 and VSHOST2 respectively.

So do these auto-start using these local accounts? I was finding that when I used local accounts the virtual server would not auto-start, but cold be started manually.

0
 
LVL 2

Expert Comment

by:hughespat57
ID: 23003970
Mine autostart fine with the local accounts.
On shut down of the host are you doing a "Saved State" of the VM? That combination will not autostart. You need to have the VM do a shutdown when the Host Virtual Server Service stops. Virtual Server 2005 sees a "Saved State" and it considers that VM already started. It's a Microsft thing.
0
 
LVL 2

Author Comment

by:dcp002
ID: 23006397
Doing that I have managed to get the virtual server to auto-start - BUT I then get a problem that the virtual server can not access the network - it just shows "network cable is unplugged" against the network adaptors.

If I run the server up manually under my domain account it has network connectivity.

The local account I am using has administrator privilidges on the host machine, but it seems no network access.
0
 
LVL 2

Expert Comment

by:hughespat57
ID: 23007672
That is odd to confirm the details I just tested it again on my desktop system.

My desktop is Windows Vista 64 bit, Virtual Servr 2005 R2 64 bit, Virtual Machine is WIndows XP 32 bit
I use VMRC Plus v1.8 to manage my VMs.

I changed my XP VM to auto-start as a local user with only User rights, and modify to the shared Virtual Network folder and share Virtual Machines folders.

On Vista:
C:\Documents and Settings\Public\Documents\Shared Virtual Machines
C:\Documents and Settings\Public\Documents\Shared Virtual Networks

My VHD folder for this system:
E:\Virtuals\ITDirector

Full network access.

 
0
 
LVL 2

Author Comment

by:dcp002
ID: 23033782
Sorry for delay in coming back, and thanks for going to trouble of testing.
I have re-checked , and with following:
Host = Vista Business 64Bit fully patched to date,
VirtualServer 2005 R2 64 bit
Virtual machine = Windows Server 2003 R2 (32 bit) fully patched to date.
Virtual machine set to turn off when virtual server stops.
If I use a local administrator account from the host to automatically start the virtual machine, it starts OK, but has no network access - it just shows "network cable is unplugged" against the network adaptors.
But if I start it manually when logged onto the host with my (cached) domain account which is a member of the local admin group on the host, then the virtual server starts and has full network access.

I am using 2 network adaptors on the host  - a gigabit physical network, and a wireless network. Both are affected in the same way.

0
 
LVL 2

Accepted Solution

by:
hughespat57 earned 1000 total points
ID: 23037595
Interesting, I would have to conclude it is a quirk with Vista as the host system.
I can not duplicate the problem using Server 2003 as host, works as described.
Would be interesting to see if this issue is reproducable on Windows Server 2008.
0
 
LVL 2

Author Closing Comment

by:dcp002
ID: 31517797
Thanks for your help, and time.
0

Featured Post

Veeam Disaster Recovery in Microsoft Azure

Veeam PN for Microsoft Azure is a FREE solution designed to simplify and automate the setup of a DR site in Microsoft Azure using lightweight software-defined networking. It reduces the complexity of VPN deployments and is designed for businesses of ALL sizes.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Introduction RemoteFX is already in use today, but you're probably not aware of it.  With the advent of Windows 2012 and Windows 8, RDP has gotten a whole lot better due to the fact that RDP now uses even more RemoteFX technologies to make desktop …
Background Information Recently I have fixed file server permission issues for one of my client. The client has 1800 users and one Windows Server 2008 R2 domain joined file server with 12 TB of data, 250+ shared folders and the folder structure i…
The Task Scheduler is a powerful tool that is built into Windows. It allows you to schedule tasks (actions) on a recurring basis, such as hourly, daily, weekly, monthly, at log on, at startup, on idle, etc. This video Micro Tutorial is a brief intro…
Is your data getting by on basic protection measures? In today’s climate of debilitating malware and ransomware—like WannaCry—that may not be enough. You need to establish more than basics, like a recovery plan that protects both data and endpoints.…
Suggested Courses
Course of the Month20 days, 14 hours left to enroll

810 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question