Hi,

I'm trying to configure a user account to automatically restart a
Virtual Machine after the restart of the Virtual Server but I'm not
succeeding ...

My Virtual Server is on a DC (I'm just testing). I've created a simple
Domain User but how do I give him the necessary right? Because when I
try to use this user I get this error:

"The account name and password could not be set. The virtual machine
account could not be set. The account has not been granted the requested
logon type."

How do I grant this requested logon type? I even added it under the
Group Policy setting of those users who are allowed to logon locally but
that didn't ...

Any ideas?

Thank you very much!

Jerome

Hiya,

On our setup we run with a dedicated domain user in order to automatically
start our virtual servers if the host fails. In case of unexpected power cuts
or similar.

The user is running as local admin on each of the host servers.

"Jesper Arnecke" <JesperArnecke@discussions.microsoft.com> wrote in message
news:077845DF-F66F-46AD-A265-4B271F7E76B1@microsoft.com...
> Hiya,
>
> On our setup we run with a dedicated domain user in order to automatically
> start our virtual servers if the host fails. In case of unexpected power
cuts
> or similar.
>
> The user is running as local admin on each of the host servers.

The user does not have to be a local admin. Make it a standard domain user,
then on the host machine give it Modify rights to the folder(s) holding your
VHD/VSV/VUD files and Read rights to c:\documents and settings\all
users\documents\shared virtual networks.

Sweet, just noticed that from another thread.
Cheers!

"PM" wrote:

>
> "Jesper Arnecke" <JesperArnecke@discussions.microsoft.com> wrote in message
> news:077845DF-F66F-46AD-A265-4B271F7E76B1@microsoft.com...
> > Hiya,
> >
> > On our setup we run with a dedicated domain user in order to automatically
> > start our virtual servers if the host fails. In case of unexpected power
> cuts
> > or similar.
> >
> > The user is running as local admin on each of the host servers.
>
> The user does not have to be a local admin. Make it a standard domain user,
> then on the host machine give it Modify rights to the folder(s) holding your
> VHD/VSV/VUD files and Read rights to c:\documents and settings\all
> users\documents\shared virtual networks.
>
>
>

Thanks for answering but that's apparently not enough ... I still get
the same message:

"The account name and password could not be set. The virtual machine
account could not be set. The account has not been granted the requested
logon type."

My domain admin gets accepted though. But I don't want to use that one.
Unfortunately it's not a stand-alone server so I can't just make the
domain user a local admit, the server is a DC.

Any suggestions?

Thanks!


PM wrote:
> "Jesper Arnecke" <JesperArnecke@discussions.microsoft.com> wrote in message
> news:077845DF-F66F-46AD-A265-4B271F7E76B1@microsoft.com...
>> Hiya,
>>
>> On our setup we run with a dedicated domain user in order to automatically
>> start our virtual servers if the host fails. In case of unexpected power
> cuts
>> or similar.
>>
>> The user is running as local admin on each of the host servers.
>
> The user does not have to be a local admin. Make it a standard domain user,
> then on the host machine give it Modify rights to the folder(s) holding your
> VHD/VSV/VUD files and Read rights to c:\documents and settings\all
> users\documents\shared virtual networks.
>
>

I am not sure this will you but here is how I solved it for myself

1. Create domain user account (password never expires/changes)
2. Add domain user to VS2K5 Server Properties,,Virtual Server Security,,Full
Control
3. Add domain user MODIFY permissions to c:\documents and settings\all
users\documents\shared virtual networks
4. Add domain user MODIFY permissions to c:\documents and settings\all
users\documents\shared virtual machines
5. Edit DC or Server Group Policy and set: ComputerAcct,,Security
Setting,,User Rights..,, Allow Logon Locally for the new USER ACCT.
6. Refresh the Domain Policy using start,,run,,gupudpate.exe /force
7. Edit Config of Virtual Machine and add new domain user,, General
Properties,,Startup account as per normal procedure

The only security hole is the user's ability to log on to the server console
locally. (Do not grant 'Allow Logon to Terminal Server Right' in the Group
Policy). This way you are able to lock the server room for security. And of
course there is always Auditing.

Just an idea.


Regards,

Joe Fenninger, MCSA
MS Small Business Specialist


"Jerome" wrote:

> Thanks for answering but that's apparently not enough ... I still get
> the same message:
>
> "The account name and password could not be set. The virtual machine
> account could not be set. The account has not been granted the requested
> logon type."
>
> My domain admin gets accepted though. But I don't want to use that one.
> Unfortunately it's not a stand-alone server so I can't just make the
> domain user a local admit, the server is a DC.
>
> Any suggestions?
>
> Thanks!
>
>
> PM wrote:
> > "Jesper Arnecke" <JesperArnecke@discussions.microsoft.com> wrote in message
> > news:077845DF-F66F-46AD-A265-4B271F7E76B1@microsoft.com...
> >> Hiya,
> >>
> >> On our setup we run with a dedicated domain user in order to automatically
> >> start our virtual servers if the host fails. In case of unexpected power
> > cuts
> >> or similar.
> >>
> >> The user is running as local admin on each of the host servers.
> >
> > The user does not have to be a local admin. Make it a standard domain user,
> > then on the host machine give it Modify rights to the folder(s) holding your
> > VHD/VSV/VUD files and Read rights to c:\documents and settings\all
> > users\documents\shared virtual networks.
> >
> >
>