> VS runs after I freshly install it, but when I reboot the service does not
> start. It states a dependency service has failed to start. When i research
> this the VMM device is in a disabled state and I cna not re-enable it. Any
> thoughts?

> Did you change the account that the VS Service runs under? If so - this
> is a known issue and you should reinstall VS and not change the account.
> --
> Cheers,
> Benjamin Armstrong
> ===============================
> Virtual machine Program Manager
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
> You assume all risk for your use.
>
> Rick L. wrote:
> > VS runs after I freshly install it, but when I reboot the service does not
> > start. It states a dependency service has failed to start. When i research
> > this the VMM device is in a disabled state and I cna not re-enable it. Any
> > thoughts?
>

> No, I did not change the account. I can actually do a fresh install, the
> service starts fine, unitl I reboot my machine or stop the service. I get a
> an error stating a dependecy failed to start or is missing error. I have
> traced it to the Virtual Machine Monitor device, it shows disabled but it
> will not let me re enable it
>
> "Ben Armstrong [MSFT]" wrote:
>
> > Did you change the account that the VS Service runs under? If so - this
> > is a known issue and you should reinstall VS and not change the account.
> > --
> > Cheers,
> > Benjamin Armstrong
> > ===============================
> > Virtual machine Program Manager
> >
> > This posting is provided "AS IS" with no warranties, and confers no rights.
> > You assume all risk for your use.
> >
> > Rick L. wrote:
> > > VS runs after I freshly install it, but when I reboot the service does not
> > > start. It states a dependency service has failed to start. When i research
> > > this the VMM device is in a disabled state and I cna not re-enable it. Any
> > > thoughts?
> >

> I had the same problem. This boiled down to permissions. We take the local
> users away from data and apps drives. However, taking the users group away
> from the directory that VM is installed, the service will not start. Trust
> me this was three days of reboots. And Ben is right, don't change the
> account. (tried that as well) Hope this helps!
>
> "Rick L." wrote:
>
> > No, I did not change the account. I can actually do a fresh install, the
> > service starts fine, unitl I reboot my machine or stop the service. I get a
> > an error stating a dependecy failed to start or is missing error. I have
> > traced it to the Virtual Machine Monitor device, it shows disabled but it
> > will not let me re enable it
> >
> > "Ben Armstrong [MSFT]" wrote:
> >
> > > Did you change the account that the VS Service runs under? If so - this
> > > is a known issue and you should reinstall VS and not change the account.
> > > --
> > > Cheers,
> > > Benjamin Armstrong
> > > ===============================
> > > Virtual machine Program Manager
> > >
> > > This posting is provided "AS IS" with no warranties, and confers no rights.
> > > You assume all risk for your use.
> > >
> > > Rick L. wrote:
> > > > VS runs after I freshly install it, but when I reboot the service does not
> > > > start. It states a dependency service has failed to start. When i research
> > > > this the VMM device is in a disabled state and I cna not re-enable it. Any
> > > > thoughts?
> > >

> As I stated earlier in this thread, no permissions have been changed. Again,
> this occurs right after I install it. The error is related to the Virtual
> Machine Monitor dependency missing.
>
> "Jmuadib" wrote:
>
> > I had the same problem. This boiled down to permissions. We take the local
> > users away from data and apps drives. However, taking the users group away
> > from the directory that VM is installed, the service will not start. Trust
> > me this was three days of reboots. And Ben is right, don't change the
> > account. (tried that as well) Hope this helps!
> >
> > "Rick L." wrote:
> >
> > > No, I did not change the account. I can actually do a fresh install, the
> > > service starts fine, unitl I reboot my machine or stop the service. I get a
> > > an error stating a dependecy failed to start or is missing error. I have
> > > traced it to the Virtual Machine Monitor device, it shows disabled but it
> > > will not let me re enable it
> > >
> > > "Ben Armstrong [MSFT]" wrote:
> > >
> > > > Did you change the account that the VS Service runs under? If so - this
> > > > is a known issue and you should reinstall VS and not change the account.
> > > > --
> > > > Cheers,
> > > > Benjamin Armstrong
> > > > ===============================
> > > > Virtual machine Program Manager
> > > >
> > > > This posting is provided "AS IS" with no warranties, and confers no rights.
> > > > You assume all risk for your use.
> > > >
> > > > Rick L. wrote:
> > > > > VS runs after I freshly install it, but when I reboot the service does not
> > > > > start. It states a dependency service has failed to start. When i research
> > > > > this the VMM device is in a disabled state and I cna not re-enable it. Any
> > > > > thoughts?
> > > >

> I'm having the same problem. The users group has the "normal" permissions
> for C:\Program Files", and the install still fails even if the users group
> has full control.
>
> I'm using Win2K3 with SP1
>
> "Rick L." wrote:
>
>> As I stated earlier in this thread, no permissions have been changed. Again,
>> this occurs right after I install it. The error is related to the Virtual
>> Machine Monitor dependency missing.
>>
>> "Jmuadib" wrote:
>>
>>> I had the same problem. This boiled down to permissions. We take the local
>>> users away from data and apps drives. However, taking the users group away
>>> from the directory that VM is installed, the service will not start. Trust
>>> me this was three days of reboots. And Ben is right, don't change the
>>> account. (tried that as well) Hope this helps!
>>>
>>> "Rick L." wrote:
>>>
>>>> No, I did not change the account. I can actually do a fresh install, the
>>>> service starts fine, unitl I reboot my machine or stop the service. I get a
>>>> an error stating a dependecy failed to start or is missing error. I have
>>>> traced it to the Virtual Machine Monitor device, it shows disabled but it
>>>> will not let me re enable it
>>>>
>>>> "Ben Armstrong [MSFT]" wrote:
>>>>
>>>>> Did you change the account that the VS Service runs under? If so - this
>>>>> is a known issue and you should reinstall VS and not change the account.
>>>>> --
>>>>> Cheers,
>>>>> Benjamin Armstrong
>>>>> ===============================
>>>>> Virtual machine Program Manager
>>>>>
>>>>> This posting is provided "AS IS" with no warranties, and confers no rights.
>>>>> You assume all risk for your use.
>>>>>
>>>>> Rick L. wrote:
>>>>>> VS runs after I freshly install it, but when I reboot the service does not
>>>>>> start. It states a dependency service has failed to start. When i research
>>>>>> this the VMM device is in a disabled state and I cna not re-enable it. Any
>>>>>> thoughts?

> By "normal" do you mean read and execute only? Only Admins / power
> users / SYSTEM should have write access to Program Files.
> --
> Cheers,
> Benjamin Armstrong
> ===============================
> Virtual machine Program Manager
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
> You assume all risk for your use.
>
> Robert Slaney wrote:
> > I'm having the same problem. The users group has the "normal" permissions
> > for C:\Program Files", and the install still fails even if the users group
> > has full control.
> >
> > I'm using Win2K3 with SP1
> >
> > "Rick L." wrote:
> >
> >> As I stated earlier in this thread, no permissions have been changed. Again,
> >> this occurs right after I install it. The error is related to the Virtual
> >> Machine Monitor dependency missing.
> >>
> >> "Jmuadib" wrote:
> >>
> >>> I had the same problem. This boiled down to permissions. We take the local
> >>> users away from data and apps drives. However, taking the users group away
> >>> from the directory that VM is installed, the service will not start. Trust
> >>> me this was three days of reboots. And Ben is right, don't change the
> >>> account. (tried that as well) Hope this helps!
> >>>
> >>> "Rick L." wrote:
> >>>
> >>>> No, I did not change the account. I can actually do a fresh install, the
> >>>> service starts fine, unitl I reboot my machine or stop the service. I get a
> >>>> an error stating a dependecy failed to start or is missing error. I have
> >>>> traced it to the Virtual Machine Monitor device, it shows disabled but it
> >>>> will not let me re enable it
> >>>>
> >>>> "Ben Armstrong [MSFT]" wrote:
> >>>>
> >>>>> Did you change the account that the VS Service runs under? If so - this
> >>>>> is a known issue and you should reinstall VS and not change the account.
> >>>>> --
> >>>>> Cheers,
> >>>>> Benjamin Armstrong
> >>>>> ===============================
> >>>>> Virtual machine Program Manager
> >>>>>
> >>>>> This posting is provided "AS IS" with no warranties, and confers no rights.
> >>>>> You assume all risk for your use.
> >>>>>
> >>>>> Rick L. wrote:
> >>>>>> VS runs after I freshly install it, but when I reboot the service does not
> >>>>>> start. It states a dependency service has failed to start. When i research
> >>>>>> this the VMM device is in a disabled state and I cna not re-enable it. Any
> >>>>>> thoughts?
>

> Yes. The Users security group has Read & Execute, List Folder contents and
> Read permissions.
>
> I logged in and installed as an Admin.
>
> Even giving the User security group "Full Control" before installing did not
> prevent the issue from occurring.
>
> "Ben Armstrong [MSFT]" wrote:
>
>> By "normal" do you mean read and execute only? Only Admins / power
>> users / SYSTEM should have write access to Program Files.
>> --
>> Cheers,
>> Benjamin Armstrong
>> ===============================
>> Virtual machine Program Manager
>>
>> This posting is provided "AS IS" with no warranties, and confers no rights.
>> You assume all risk for your use.
>>
>> Robert Slaney wrote:
>>> I'm having the same problem. The users group has the "normal" permissions
>>> for C:\Program Files", and the install still fails even if the users group
>>> has full control.
>>>
>>> I'm using Win2K3 with SP1
>>>
>>> "Rick L." wrote:
>>>
>>>> As I stated earlier in this thread, no permissions have been changed. Again,
>>>> this occurs right after I install it. The error is related to the Virtual
>>>> Machine Monitor dependency missing.
>>>>
>>>> "Jmuadib" wrote:
>>>>
>>>>> I had the same problem. This boiled down to permissions. We take the local
>>>>> users away from data and apps drives. However, taking the users group away
>>>>> from the directory that VM is installed, the service will not start. Trust
>>>>> me this was three days of reboots. And Ben is right, don't change the
>>>>> account. (tried that as well) Hope this helps!
>>>>>
>>>>> "Rick L." wrote:
>>>>>
>>>>>> No, I did not change the account. I can actually do a fresh install, the
>>>>>> service starts fine, unitl I reboot my machine or stop the service. I get a
>>>>>> an error stating a dependecy failed to start or is missing error. I have
>>>>>> traced it to the Virtual Machine Monitor device, it shows disabled but it
>>>>>> will not let me re enable it
>>>>>>
>>>>>> "Ben Armstrong [MSFT]" wrote:
>>>>>>
>>>>>>> Did you change the account that the VS Service runs under? If so - this
>>>>>>> is a known issue and you should reinstall VS and not change the account.
>>>>>>> --
>>>>>>> Cheers,
>>>>>>> Benjamin Armstrong
>>>>>>> ===============================
>>>>>>> Virtual machine Program Manager
>>>>>>>
>>>>>>> This posting is provided "AS IS" with no warranties, and confers no rights.
>>>>>>> You assume all risk for your use.
>>>>>>>
>>>>>>> Rick L. wrote:
>>>>>>>> VS runs after I freshly install it, but when I reboot the service does not
>>>>>>>> start. It states a dependency service has failed to start. When i research
>>>>>>>> this the VMM device is in a disabled state and I cna not re-enable it. Any
>>>>>>>> thoughts?

> Giving any other groups / users than those below "full control" might
> actually cause this problem.
> --
> Cheers,
> Benjamin Armstrong
> ===============================
> Virtual machine Program Manager
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
> You assume all risk for your use.
>
>

> The first time I installed the Users group had the standard permissions.
>
> Given some of the responses indicated that lack of permissions can cause
> this error, I tried installed with the Users group have full control, and
> this still failed with exactly the same behaviour. I have reset the user
> permissions and tried re-installing the product numberous times. The VMM
> driver fails to installed/configured very time.
>
> I doubt that permissions is involved, at least with the installation folder.
>
> Is there any setup logs that I can look for more information in, or can I
> install in a verbose mode for diagnostics.
>
> "Ben Armstrong [MSFT]" wrote:
>
>> Giving any other groups / users than those below "full control" might
>> actually cause this problem.
>> --
>> Cheers,
>> Benjamin Armstrong
>> ===============================
>> Virtual machine Program Manager
>>
>> This posting is provided "AS IS" with no warranties, and confers no rights.
>> You assume all risk for your use.
>>
>>

> Wait. Are you seeing installation issues? Or are you seeing that the
> VMM is not loaded after the first reboot? The latter is almost always
> caused by the Virtual Server service running under an account that has
> been given too many permissions.
> --
> Cheers,
> Benjamin Armstrong
> ===============================
> Virtual machine Program Manager
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
> You assume all risk for your use.
>
> Robert Slaney wrote:
> > The first time I installed the Users group had the standard permissions.
> >
> > Given some of the responses indicated that lack of permissions can cause
> > this error, I tried installed with the Users group have full control, and
> > this still failed with exactly the same behaviour. I have reset the user
> > permissions and tried re-installing the product numberous times. The VMM
> > driver fails to installed/configured very time.
> >
> > I doubt that permissions is involved, at least with the installation folder.
> >
> > Is there any setup logs that I can look for more information in, or can I
> > install in a verbose mode for diagnostics.
> >
> > "Ben Armstrong [MSFT]" wrote:
> >
> >> Giving any other groups / users than those below "full control" might
> >> actually cause this problem.
> >> --
> >> Cheers,
> >> Benjamin Armstrong
> >> ===============================
> >> Virtual machine Program Manager
> >>
> >> This posting is provided "AS IS" with no warranties, and confers no rights.
> >> You assume all risk for your use.
> >>
> >>
>

> hi out there!
>
> a collegue of mine had the same problem and found out the following:
>
> 1) the registry key that loads the driver is removed after starting up the
> services(HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\vmm)
> 2) it seems to be a "too much" rights problem --> which actually must be a
> bug after all!
>
> workaround solution:
> 1) under this key, change the "start" key to "1" (as this is the normal
> "automaticlly start service" setting)
> 2) grant ONLY READ rights to this key (which will avoid removing the key)
> 3) reboot the machine --> service is running!
>
> BUT
> stopping & starting the service with the service manager does NOT work....
> so this is a bug for sure (i guess :-)
>
> hope that helps
> reini
>
>
> "Robert Slaney" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
> > The VM service is running using the network service account.
> >
> > I'm not seeing installation issues, but if you look at the VMM driver
> > immediately after the installation has completed, then it's status is
> > "unknown". I cannot launch the administration website as it rejects all
> > authentication, including the local administrator account, if you attempt
> > to
> > restart the VM service it fails and the VMM driver dissappears after
> > reboot
> > and thus the service fails to start.
> >
> > I was looking to see if I could see any hints as to the cause in any
> > installation logs, if they can be produced.
> >
> > "Ben Armstrong [MSFT]" wrote:
> >
> >> Wait. Are you seeing installation issues? Or are you seeing that the
> >> VMM is not loaded after the first reboot? The latter is almost always
> >> caused by the Virtual Server service running under an account that has
> >> been given too many permissions.
> >> --
> >> Cheers,
> >> Benjamin Armstrong
> >> ===============================
> >> Virtual machine Program Manager
> >>
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights.
> >> You assume all risk for your use.
> >>
> >> Robert Slaney wrote:
> >> > The first time I installed the Users group had the standard
> >> > permissions.
> >> >
> >> > Given some of the responses indicated that lack of permissions can
> >> > cause
> >> > this error, I tried installed with the Users group have full control,
> >> > and
> >> > this still failed with exactly the same behaviour. I have reset the
> >> > user
> >> > permissions and tried re-installing the product numberous times. The
> >> > VMM
> >> > driver fails to installed/configured very time.
> >> >
> >> > I doubt that permissions is involved, at least with the installation
> >> > folder.
> >> >
> >> > Is there any setup logs that I can look for more information in, or can
> >> > I
> >> > install in a verbose mode for diagnostics.
> >> >
> >> > "Ben Armstrong [MSFT]" wrote:
> >> >
> >> >> Giving any other groups / users than those below "full control" might
> >> >> actually cause this problem.
> >> >> --
> >> >> Cheers,
> >> >> Benjamin Armstrong
> >> >> ===============================
> >> >> Virtual machine Program Manager
> >> >>
> >> >> This posting is provided "AS IS" with no warranties, and confers no
> >> >> rights.
> >> >> You assume all risk for your use.
> >> >>
> >> >>
> >>
>
>
>

> The VM service is running using the network service account.
>
> I'm not seeing installation issues, but if you look at the VMM driver
> immediately after the installation has completed, then it's status is
> "unknown". I cannot launch the administration website as it rejects all
> authentication, including the local administrator account, if you attempt
> to
> restart the VM service it fails and the VMM driver dissappears after
> reboot
> and thus the service fails to start.
>
> I was looking to see if I could see any hints as to the cause in any
> installation logs, if they can be produced.
>
> "Ben Armstrong [MSFT]" wrote:
>
>> Wait. Are you seeing installation issues? Or are you seeing that the
>> VMM is not loaded after the first reboot? The latter is almost always
>> caused by the Virtual Server service running under an account that has
>> been given too many permissions.
>> --
>> Cheers,
>> Benjamin Armstrong
>> ===============================
>> Virtual machine Program Manager
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> You assume all risk for your use.
>>
>> Robert Slaney wrote:
>> > The first time I installed the Users group had the standard
>> > permissions.
>> >
>> > Given some of the responses indicated that lack of permissions can
>> > cause
>> > this error, I tried installed with the Users group have full control,
>> > and
>> > this still failed with exactly the same behaviour. I have reset the
>> > user
>> > permissions and tried re-installing the product numberous times. The
>> > VMM
>> > driver fails to installed/configured very time.
>> >
>> > I doubt that permissions is involved, at least with the installation
>> > folder.
>> >
>> > Is there any setup logs that I can look for more information in, or can
>> > I
>> > install in a verbose mode for diagnostics.
>> >
>> > "Ben Armstrong [MSFT]" wrote:
>> >
>> >> Giving any other groups / users than those below "full control" might
>> >> actually cause this problem.
>> >> --
>> >> Cheers,
>> >> Benjamin Armstrong
>> >> ===============================
>> >> Virtual machine Program Manager
>> >>
>> >> This posting is provided "AS IS" with no warranties, and confers no
>> >> rights.
>> >> You assume all risk for your use.
>> >>
>> >>
>>

> VS runs after I freshly install it, but when I reboot the service does not
> start. It states a dependency service has failed to start. When i research
> this the VMM device is in a disabled state and I cna not re-enable it. Any
> thoughts?

>> VS runs after I freshly install it, but when I reboot the service does not
>> start. It states a dependency service has failed to start. When i research
>> this the VMM device is in a disabled state and I cna not re-enable it. Any
>> thoughts?
>
> I had this problem too. I looked at the registry key above and changed the "start" key value to 1, but still at reboot the service was gone. Checking regedit after the reboot revealed that the entire vmm tree was gone.
>
> I reinstalled, and had a look at the registry, and found a key called "deleteflag" which was set to 1. This tells windows to delete the service! I changed this to 0, changed the start key to 1 and rebooted and the service started properly.
>
> Now I've looked at the vmm key again, and the values have been changed back! I will change these manually for now, but best guess is that changing permissions on them will fix it once and for all.
>
> Cheers,
> Max.
>
> Posted via http://www.VirtualServerFaq.com - Brought to you by Business Information Technology Shop - http://www.bitshop.com

> This has been shown to occur due to three possible changes to the system:
>
> 1. The Virtual Server service (vssrvc.exe) has been changed to run under
> an account other than Network Service.
>
> 2. The NetworkService account has been given excessive power –
> specifically, if it has been added to the Administrators group. This
> defeats the purpose of having low-privilege service user accounts like
> NetworkService and LocalService.
>
> 3. NetworkService has been granted the “Load and unload device drivers”
> privilege in the Local Security Policy MMC snap-in.
>
> If you have done any of the above - please don't.
> --
> Cheers,
> Benjamin Armstrong
> ===============================
> Virtual machine Program Manager
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> You assume all risk for your use.
>
> Max wrote:
>>> VS runs after I freshly install it, but when I reboot the service does
>>> not start. It states a dependency service has failed to start. When i
>>> research this the VMM device is in a disabled state and I cna not
>>> re-enable it. Any thoughts?
>>
>> I had this problem too. I looked at the registry key above and changed
>> the "start" key value to 1, but still at reboot the service was gone.
>> Checking regedit after the reboot revealed that the entire vmm tree was
>> gone.
>>
>> I reinstalled, and had a look at the registry, and found a key called
>> "deleteflag" which was set to 1. This tells windows to delete the
>> service! I changed this to 0, changed the start key to 1 and rebooted
>> and the service started properly.
>>
>> Now I've looked at the vmm key again, and the values have been changed
>> back! I will change these manually for now, but best guess is that
>> changing permissions on them will fix it once and for all.
>>
>> Cheers,
>> Max.
>>
>> Posted via http://www.VirtualServerFaq.com - Brought to you by Business
>> Information Technology Shop - http://www.bitshop.com

> Hello,
>
> Having the same problem.
>
> VS 2005 R2 is install on a DC, running under Network Service, SPN has
> been registered.
>
> Everytime I start I have 3 error in the event log
>
> 1. A connection couldn't be created to the Virtual Machine Helper
> service. Virtual Server cannot run without a connection to the Virtual
> Machine Helper service.
>
> 2. The service principal names for Virtual Server could not be
> registered. Constrained delegation cannot be used until the SPNs have been
> registered manually. Error 0x80072098 - Insufficient access rights to
> perform the operation.
>
> 3. A connection couldn't be created to the Virtual Machine Helper
> service.
>
> Any idea / suggestion...
>
> Also all your 3 suggestions are not involved in my case
>
> Thank
>
> ML
> "Ben Armstrong [MSFT]" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
>> This has been shown to occur due to three possible changes to the system:
>>
>> 1. The Virtual Server service (vssrvc.exe) has been changed to run under
>> an account other than Network Service.
>>
>> 2. The NetworkService account has been given excessive power –
>> specifically, if it has been added to the Administrators group. This
>> defeats the purpose of having low-privilege service user accounts like
>> NetworkService and LocalService.
>>
>> 3. NetworkService has been granted the “Load and unload device drivers”
>> privilege in the Local Security Policy MMC snap-in.
>>
>> If you have done any of the above - please don't.
>> --
>> Cheers,
>> Benjamin Armstrong
>> ===============================
>> Virtual machine Program Manager
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> You assume all risk for your use.
>>
>> Max wrote:
>>>> VS runs after I freshly install it, but when I reboot the service does
>>>> not start. It states a dependency service has failed to start. When i
>>>> research this the VMM device is in a disabled state and I cna not
>>>> re-enable it. Any thoughts?
>>> I had this problem too. I looked at the registry key above and changed
>>> the "start" key value to 1, but still at reboot the service was gone.
>>> Checking regedit after the reboot revealed that the entire vmm tree was
>>> gone.
>>>
>>> I reinstalled, and had a look at the registry, and found a key called
>>> "deleteflag" which was set to 1. This tells windows to delete the
>>> service! I changed this to 0, changed the start key to 1 and rebooted
>>> and the service started properly.
>>>
>>> Now I've looked at the vmm key again, and the values have been changed
>>> back! I will change these manually for now, but best guess is that
>>> changing permissions on them will fix it once and for all.
>>>
>>> Cheers,
>>> Max.
>>>
>>> Posted via http://www.VirtualServerFaq.com - Brought to you by Business
>>> Information Technology Shop - http://www.bitshop.com
>
>

> Hi Michel,
>
> Your problem is completely different. The issue being discussed here does
> not involve SPNs or the VM Helper.
>
> Are you still able to launch virtual machines? Is the Virtual Machine
> Helper service running?
> --
> Cheers,
> Benjamin Armstrong
> ===============================
> Virtual machine Program Manager
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> You assume all risk for your use.
>
> Michel Lapointe wrote:
>> Hello,
>>
>> Having the same problem.
>>
>> VS 2005 R2 is install on a DC, running under Network Service, SPN has
>> been registered.
>>
>> Everytime I start I have 3 error in the event log
>>
>> 1. A connection couldn't be created to the Virtual Machine Helper
>> service. Virtual Server cannot run without a connection to the Virtual
>> Machine Helper service.
>>
>> 2. The service principal names for Virtual Server could not be
>> registered. Constrained delegation cannot be used until the SPNs have
>> been registered manually. Error 0x80072098 - Insufficient access rights
>> to perform the operation.
>>
>> 3. A connection couldn't be created to the Virtual Machine Helper
>> service.
>>
>> Any idea / suggestion...
>>
>> Also all your 3 suggestions are not involved in my case
>>
>> Thank
>>
>> ML
>> "Ben Armstrong [MSFT]" <(email address - cut out)> wrote in message
>> news:(email address - cut out)...
>>> This has been shown to occur due to three possible changes to the
>>> system:
>>>
>>> 1. The Virtual Server service (vssrvc.exe) has been changed to run under
>>> an account other than Network Service.
>>>
>>> 2. The NetworkService account has been given excessive power –
>>> specifically, if it has been added to the Administrators group. This
>>> defeats the purpose of having low-privilege service user accounts like
>>> NetworkService and LocalService.
>>>
>>> 3. NetworkService has been granted the “Load and unload device drivers”
>>> privilege in the Local Security Policy MMC snap-in.
>>>
>>> If you have done any of the above - please don't.
>>> --
>>> Cheers,
>>> Benjamin Armstrong
>>> ===============================
>>> Virtual machine Program Manager
>>>
>>> This posting is provided "AS IS" with no warranties, and confers no
>>> rights.
>>> You assume all risk for your use.
>>>
>>> Max wrote:
>>>>> VS runs after I freshly install it, but when I reboot the service does
>>>>> not start. It states a dependency service has failed to start. When
>>>>> i research this the VMM device is in a disabled state and I cna not
>>>>> re-enable it. Any thoughts?
>>>> I had this problem too. I looked at the registry key above and changed
>>>> the "start" key value to 1, but still at reboot the service was gone.
>>>> Checking regedit after the reboot revealed that the entire vmm tree was
>>>> gone.
>>>>
>>>> I reinstalled, and had a look at the registry, and found a key called
>>>> "deleteflag" which was set to 1. This tells windows to delete the
>>>> service! I changed this to 0, changed the start key to 1 and rebooted
>>>> and the service started properly.
>>>>
>>>> Now I've looked at the vmm key again, and the values have been changed
>>>> back! I will change these manually for now, but best guess is that
>>>> changing permissions on them will fix it once and for all.
>>>>
>>>> Cheers,
>>>> Max.
>>>>
>>>> Posted via http://www.VirtualServerFaq.com - Brought to you by Business
>>>> Information Technology Shop - http://www.bitshop.com
>>

> Unless I change the user account for the services, no I can't launch any
> virtual machine.
>
> If I don't update the SPN manually I will get the SPN failure.
>
> Helper service is running, and If I change the password for the VServer
> service, it will start properly (however I will have the dissapearing
> vmm.sys problem_
>
> Thank
>
> ML
> "Ben Armstrong [MSFT]" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
>> Hi Michel,
>>
>> Your problem is completely different. The issue being discussed here does
>> not involve SPNs or the VM Helper.
>>
>> Are you still able to launch virtual machines? Is the Virtual Machine
>> Helper service running?
>> --
>> Cheers,
>> Benjamin Armstrong
>> ===============================
>> Virtual machine Program Manager
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> You assume all risk for your use.
>>
>> Michel Lapointe wrote:
>>> Hello,
>>>
>>> Having the same problem.
>>>
>>> VS 2005 R2 is install on a DC, running under Network Service, SPN has
>>> been registered.
>>>
>>> Everytime I start I have 3 error in the event log
>>>
>>> 1. A connection couldn't be created to the Virtual Machine Helper
>>> service. Virtual Server cannot run without a connection to the Virtual
>>> Machine Helper service.
>>>
>>> 2. The service principal names for Virtual Server could not be
>>> registered. Constrained delegation cannot be used until the SPNs have
>>> been registered manually. Error 0x80072098 - Insufficient access rights
>>> to perform the operation.
>>>
>>> 3. A connection couldn't be created to the Virtual Machine Helper
>>> service.
>>>
>>> Any idea / suggestion...
>>>
>>> Also all your 3 suggestions are not involved in my case
>>>
>>> Thank
>>>
>>> ML
>>> "Ben Armstrong [MSFT]" <(email address - cut out)> wrote in message
>>> news:(email address - cut out)...
>>>> This has been shown to occur due to three possible changes to the
>>>> system:
>>>>
>>>> 1. The Virtual Server service (vssrvc.exe) has been changed to run under
>>>> an account other than Network Service.
>>>>
>>>> 2. The NetworkService account has been given excessive power –
>>>> specifically, if it has been added to the Administrators group. This
>>>> defeats the purpose of having low-privilege service user accounts like
>>>> NetworkService and LocalService.
>>>>
>>>> 3. NetworkService has been granted the “Load and unload device drivers”
>>>> privilege in the Local Security Policy MMC snap-in.
>>>>
>>>> If you have done any of the above - please don't.
>>>> --
>>>> Cheers,
>>>> Benjamin Armstrong
>>>> ===============================
>>>> Virtual machine Program Manager
>>>>
>>>> This posting is provided "AS IS" with no warranties, and confers no
>>>> rights.
>>>> You assume all risk for your use.
>>>>
>>>> Max wrote:
>>>>>> VS runs after I freshly install it, but when I reboot the service does
>>>>>> not start. It states a dependency service has failed to start. When
>>>>>> i research this the VMM device is in a disabled state and I cna not
>>>>>> re-enable it. Any thoughts?
>>>>> I had this problem too. I looked at the registry key above and changed
>>>>> the "start" key value to 1, but still at reboot the service was gone.
>>>>> Checking regedit after the reboot revealed that the entire vmm tree was
>>>>> gone.
>>>>>
>>>>> I reinstalled, and had a look at the registry, and found a key called
>>>>> "deleteflag" which was set to 1. This tells windows to delete the
>>>>> service! I changed this to 0, changed the start key to 1 and rebooted
>>>>> and the service started properly.
>>>>>
>>>>> Now I've looked at the vmm key again, and the values have been changed
>>>>> back! I will change these manually for now, but best guess is that
>>>>> changing permissions on them will fix it once and for all.
>>>>>
>>>>> Cheers,
>>>>> Max.
>>>>>
>>>>> Posted via http://www.VirtualServerFaq.com - Brought to you by Business
>>>>> Information Technology Shop - http://www.bitshop.com
>

> What account is the VM Helper running as?
> --
> Cheers,
> Benjamin Armstrong
> ===============================
> Virtual machine Program Manager
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> You assume all risk for your use.
>
> Michel Lapointe wrote:
>> Unless I change the user account for the services, no I can't launch any
>> virtual machine.
>>
>> If I don't update the SPN manually I will get the SPN failure.
>>
>> Helper service is running, and If I change the password for the VServer
>> service, it will start properly (however I will have the dissapearing
>> vmm.sys problem_
>>
>> Thank
>>
>> ML
>> "Ben Armstrong [MSFT]" <(email address - cut out)> wrote in message
>> news:(email address - cut out)...
>>> Hi Michel,
>>>
>>> Your problem is completely different. The issue being discussed here
>>> does not involve SPNs or the VM Helper.
>>>
>>> Are you still able to launch virtual machines? Is the Virtual Machine
>>> Helper service running?
>>> --
>>> Cheers,
>>> Benjamin Armstrong
>>> ===============================
>>> Virtual machine Program Manager
>>>
>>> This posting is provided "AS IS" with no warranties, and confers no
>>> rights.
>>> You assume all risk for your use.
>>>
>>> Michel Lapointe wrote:
>>>> Hello,
>>>>
>>>> Having the same problem.
>>>>
>>>> VS 2005 R2 is install on a DC, running under Network Service, SPN
>>>> has been registered.
>>>>
>>>> Everytime I start I have 3 error in the event log
>>>>
>>>> 1. A connection couldn't be created to the Virtual Machine Helper
>>>> service. Virtual Server cannot run without a connection to the Virtual
>>>> Machine Helper service.
>>>>
>>>> 2. The service principal names for Virtual Server could not be
>>>> registered. Constrained delegation cannot be used until the SPNs have
>>>> been registered manually. Error 0x80072098 - Insufficient access
>>>> rights to perform the operation.
>>>>
>>>> 3. A connection couldn't be created to the Virtual Machine Helper
>>>> service.
>>>>
>>>> Any idea / suggestion...
>>>>
>>>> Also all your 3 suggestions are not involved in my case
>>>>
>>>> Thank
>>>>
>>>> ML
>>>> "Ben Armstrong [MSFT]" <(email address - cut out)> wrote in message
>>>> news:(email address - cut out)...
>>>>> This has been shown to occur due to three possible changes to the
>>>>> system:
>>>>>
>>>>> 1. The Virtual Server service (vssrvc.exe) has been changed to run
>>>>> under an account other than Network Service.
>>>>>
>>>>> 2. The NetworkService account has been given excessive power –
>>>>> specifically, if it has been added to the Administrators group. This
>>>>> defeats the purpose of having low-privilege service user accounts like
>>>>> NetworkService and LocalService.
>>>>>
>>>>> 3. NetworkService has been granted the “Load and unload device
>>>>> drivers” privilege in the Local Security Policy MMC snap-in.
>>>>>
>>>>> If you have done any of the above - please don't.
>>>>> --
>>>>> Cheers,
>>>>> Benjamin Armstrong
>>>>> ===============================
>>>>> Virtual machine Program Manager
>>>>>
>>>>> This posting is provided "AS IS" with no warranties, and confers no
>>>>> rights.
>>>>> You assume all risk for your use.
>>>>>
>>>>> Max wrote:
>>>>>>> VS runs after I freshly install it, but when I reboot the service
>>>>>>> does not start. It states a dependency service has failed to start.
>>>>>>> When i research this the VMM device is in a disabled state and I cna
>>>>>>> not re-enable it. Any thoughts?
>>>>>> I had this problem too. I looked at the registry key above and
>>>>>> changed the "start" key value to 1, but still at reboot the service
>>>>>> was gone. Checking regedit after the reboot revealed that the entire
>>>>>> vmm tree was gone.
>>>>>>
>>>>>> I reinstalled, and had a look at the registry, and found a key called
>>>>>> "deleteflag" which was set to 1. This tells windows to delete the
>>>>>> service! I changed this to 0, changed the start key to 1 and
>>>>>> rebooted and the service started properly.
>>>>>>
>>>>>> Now I've looked at the vmm key again, and the values have been
>>>>>> changed back! I will change these manually for now, but best guess
>>>>>> is that changing permissions on them will fix it once and for all.
>>>>>>
>>>>>> Cheers,
>>>>>> Max.
>>>>>>
>>>>>> Posted via http://www.VirtualServerFaq.com - Brought to you by
>>>>>> Business Information Technology Shop - http://www.bitshop.com
>>

> Helper = Local System
> VServer = Network System
>
> Thank
> ML
> "Ben Armstrong [MSFT]" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
>> What account is the VM Helper running as?
>> --
>> Cheers,
>> Benjamin Armstrong
>> ===============================
>> Virtual machine Program Manager
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> You assume all risk for your use.
>>
>> Michel Lapointe wrote:
>>> Unless I change the user account for the services, no I can't launch any
>>> virtual machine.
>>>
>>> If I don't update the SPN manually I will get the SPN failure.
>>>
>>> Helper service is running, and If I change the password for the VServer
>>> service, it will start properly (however I will have the dissapearing
>>> vmm.sys problem_
>>>
>>> Thank
>>>
>>> ML
>>> "Ben Armstrong [MSFT]" <(email address - cut out)> wrote in message
>>> news:(email address - cut out)...
>>>> Hi Michel,
>>>>
>>>> Your problem is completely different. The issue being discussed here
>>>> does not involve SPNs or the VM Helper.
>>>>
>>>> Are you still able to launch virtual machines? Is the Virtual Machine
>>>> Helper service running?
>>>> --
>>>> Cheers,
>>>> Benjamin Armstrong
>>>> ===============================
>>>> Virtual machine Program Manager
>>>>
>>>> This posting is provided "AS IS" with no warranties, and confers no
>>>> rights.
>>>> You assume all risk for your use.
>>>>
>>>> Michel Lapointe wrote:
>>>>> Hello,
>>>>>
>>>>> Having the same problem.
>>>>>
>>>>> VS 2005 R2 is install on a DC, running under Network Service, SPN
>>>>> has been registered.
>>>>>
>>>>> Everytime I start I have 3 error in the event log
>>>>>
>>>>> 1. A connection couldn't be created to the Virtual Machine Helper
>>>>> service. Virtual Server cannot run without a connection to the Virtual
>>>>> Machine Helper service.
>>>>>
>>>>> 2. The service principal names for Virtual Server could not be
>>>>> registered. Constrained delegation cannot be used until the SPNs have
>>>>> been registered manually. Error 0x80072098 - Insufficient access
>>>>> rights to perform the operation.
>>>>>
>>>>> 3. A connection couldn't be created to the Virtual Machine Helper
>>>>> service.
>>>>>
>>>>> Any idea / suggestion...
>>>>>
>>>>> Also all your 3 suggestions are not involved in my case
>>>>>
>>>>> Thank
>>>>>
>>>>> ML
>>>>> "Ben Armstrong [MSFT]" <(email address - cut out)> wrote in message
>>>>> news:(email address - cut out)...
>>>>>> This has been shown to occur due to three possible changes to the
>>>>>> system:
>>>>>>
>>>>>> 1. The Virtual Server service (vssrvc.exe) has been changed to run
>>>>>> under an account other than Network Service.
>>>>>>
>>>>>> 2. The NetworkService account has been given excessive power –
>>>>>> specifically, if it has been added to the Administrators group. This
>>>>>> defeats the purpose of having low-privilege service user accounts like
>>>>>> NetworkService and LocalService.
>>>>>>
>>>>>> 3. NetworkService has been granted the “Load and unload device
>>>>>> drivers” privilege in the Local Security Policy MMC snap-in.
>>>>>>
>>>>>> If you have done any of the above - please don't.
>>>>>> --
>>>>>> Cheers,
>>>>>> Benjamin Armstrong
>>>>>> ===============================
>>>>>> Virtual machine Program Manager
>>>>>>
>>>>>> This posting is provided "AS IS" with no warranties, and confers no
>>>>>> rights.
>>>>>> You assume all risk for your use.
>>>>>>
>>>>>> Max wrote:
>>>>>>>> VS runs after I freshly install it, but when I reboot the service
>>>>>>>> does not start. It states a dependency service has failed to start.
>>>>>>>> When i research this the VMM device is in a disabled state and I cna
>>>>>>>> not re-enable it. Any thoughts?
>>>>>>> I had this problem too. I looked at the registry key above and
>>>>>>> changed the "start" key value to 1, but still at reboot the service
>>>>>>> was gone. Checking regedit after the reboot revealed that the entire
>>>>>>> vmm tree was gone.
>>>>>>>
>>>>>>> I reinstalled, and had a look at the registry, and found a key called
>>>>>>> "deleteflag" which was set to 1. This tells windows to delete the
>>>>>>> service! I changed this to 0, changed the start key to 1 and
>>>>>>> rebooted and the service started properly.
>>>>>>>
>>>>>>> Now I've looked at the vmm key again, and the values have been
>>>>>>> changed back! I will change these manually for now, but best guess
>>>>>>> is that changing permissions on them will fix it once and for all.
>>>>>>>
>>>>>>> Cheers,
>>>>>>> Max.
>>>>>>>
>>>>>>> Posted via http://www.VirtualServerFaq.com - Brought to you by
>>>>>>> Business Information Technology Shop - http://www.bitshop.com
>
>

> Okay - that is correct. It is strange that the Service cannot access the
> helper. What other applications do you have running on the computer?
> Have you made any non-standard configuration changes?
> --
> Cheers,
> Benjamin Armstrong
> ===============================
> Virtual machine Program Manager
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> You assume all risk for your use.
>
> Michel Lapointe wrote:
>> Helper = Local System
>> VServer = Network System
>>
>> Thank
>> ML
>> "Ben Armstrong [MSFT]" <(email address - cut out)> wrote in message
>> news:(email address - cut out)...
>>> What account is the VM Helper running as?
>>> --
>>> Cheers,
>>> Benjamin Armstrong
>>> ===============================
>>> Virtual machine Program Manager
>>>
>>> This posting is provided "AS IS" with no warranties, and confers no
>>> rights.
>>> You assume all risk for your use.
>>>
>>> Michel Lapointe wrote:
>>>> Unless I change the user account for the services, no I can't launch
>>>> any virtual machine.
>>>>
>>>> If I don't update the SPN manually I will get the SPN failure.
>>>>
>>>> Helper service is running, and If I change the password for the VServer
>>>> service, it will start properly (however I will have the dissapearing
>>>> vmm.sys problem_
>>>>
>>>> Thank
>>>>
>>>> ML
>>>> "Ben Armstrong [MSFT]" <(email address - cut out)> wrote in message
>>>> news:(email address - cut out)...
>>>>> Hi Michel,
>>>>>
>>>>> Your problem is completely different. The issue being discussed here
>>>>> does not involve SPNs or the VM Helper.
>>>>>
>>>>> Are you still able to launch virtual machines? Is the Virtual Machine
>>>>> Helper service running?
>>>>> --
>>>>> Cheers,
>>>>> Benjamin Armstrong
>>>>> ===============================
>>>>> Virtual machine Program Manager
>>>>>
>>>>> This posting is provided "AS IS" with no warranties, and confers no
>>>>> rights.
>>>>> You assume all risk for your use.
>>>>>
>>>>> Michel Lapointe wrote:
>>>>>> Hello,
>>>>>>
>>>>>> Having the same problem.
>>>>>>
>>>>>> VS 2005 R2 is install on a DC, running under Network Service, SPN
>>>>>> has been registered.
>>>>>>
>>>>>> Everytime I start I have 3 error in the event log
>>>>>>
>>>>>> 1. A connection couldn't be created to the Virtual Machine Helper
>>>>>> service. Virtual Server cannot run without a connection to the
>>>>>> Virtual Machine Helper service.
>>>>>>
>>>>>> 2. The service principal names for Virtual Server could not be
>>>>>> registered. Constrained delegation cannot be used until the SPNs have
>>>>>> been registered manually. Error 0x80072098 - Insufficient access
>>>>>> rights to perform the operation.
>>>>>>
>>>>>> 3. A connection couldn't be created to the Virtual Machine Helper
>>>>>> service.
>>>>>>
>>>>>> Any idea / suggestion...
>>>>>>
>>>>>> Also all your 3 suggestions are not involved in my case
>>>>>>
>>>>>> Thank
>>>>>>
>>>>>> ML
>>>>>> "Ben Armstrong [MSFT]" <(email address - cut out)> wrote in message
>>>>>> news:(email address - cut out)...
>>>>>>> This has been shown to occur due to three possible changes to the
>>>>>>> system:
>>>>>>>
>>>>>>> 1. The Virtual Server service (vssrvc.exe) has been changed to run
>>>>>>> under an account other than Network Service.
>>>>>>>
>>>>>>> 2. The NetworkService account has been given excessive power –
>>>>>>> specifically, if it has been added to the Administrators group.
>>>>>>> This defeats the purpose of having low-privilege service user
>>>>>>> accounts like NetworkService and LocalService.
>>>>>>>
>>>>>>> 3. NetworkService has been granted the “Load and unload device
>>>>>>> drivers” privilege in the Local Security Policy MMC snap-in.
>>>>>>>
>>>>>>> If you have done any of the above - please don't.
>>>>>>> --
>>>>>>> Cheers,
>>>>>>> Benjamin Armstrong
>>>>>>> ===============================
>>>>>>> Virtual machine Program Manager
>>>>>>>
>>>>>>> This posting is provided "AS IS" with no warranties, and confers no
>>>>>>> rights.
>>>>>>> You assume all risk for your use.
>>>>>>>
>>>>>>> Max wrote:
>>>>>>>>> VS runs after I freshly install it, but when I reboot the service
>>>>>>>>> does not start. It states a dependency service has failed to
>>>>>>>>> start. When i research this the VMM device is in a disabled state
>>>>>>>>> and I cna not re-enable it. Any thoughts?
>>>>>>>> I had this problem too. I looked at the registry key above and
>>>>>>>> changed the "start" key value to 1, but still at reboot the service
>>>>>>>> was gone. Checking regedit after the reboot revealed that the
>>>>>>>> entire vmm tree was gone.
>>>>>>>>
>>>>>>>> I reinstalled, and had a look at the registry, and found a key
>>>>>>>> called "deleteflag" which was set to 1. This tells windows to
>>>>>>>> delete the service! I changed this to 0, changed the start key to
>>>>>>>> 1 and rebooted and the service started properly.
>>>>>>>>
>>>>>>>> Now I've looked at the vmm key again, and the values have been
>>>>>>>> changed back! I will change these manually for now, but best guess
>>>>>>>> is that changing permissions on them will fix it once and for all.
>>>>>>>>
>>>>>>>> Cheers,
>>>>>>>> Max.
>>>>>>>>
>>>>>>>> Posted via http://www.VirtualServerFaq.com - Brought to you by
>>>>>>>> Business Information Technology Shop - http://www.bitshop.com
>>

> This is a DC with DNS/WINS/DHCP running on it.
>
> No change as been made
>
> ML
> "Ben Armstrong [MSFT]" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
>> Okay - that is correct. It is strange that the Service cannot access the
>> helper. What other applications do you have running on the computer?
>> Have you made any non-standard configuration changes?
>> --
>> Cheers,
>> Benjamin Armstrong
>> ===============================
>> Virtual machine Program Manager
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> You assume all risk for your use.
>>
>> Michel Lapointe wrote:
>>> Helper = Local System
>>> VServer = Network System
>>>
>>> Thank
>>> ML
>>> "Ben Armstrong [MSFT]" <(email address - cut out)> wrote in message
>>> news:(email address - cut out)...
>>>> What account is the VM Helper running as?
>>>> --
>>>> Cheers,
>>>> Benjamin Armstrong
>>>> ===============================
>>>> Virtual machine Program Manager
>>>>
>>>> This posting is provided "AS IS" with no warranties, and confers no
>>>> rights.
>>>> You assume all risk for your use.
>>>>
>>>> Michel Lapointe wrote:
>>>>> Unless I change the user account for the services, no I can't launch
>>>>> any virtual machine.
>>>>>
>>>>> If I don't update the SPN manually I will get the SPN failure.
>>>>>
>>>>> Helper service is running, and If I change the password for the VServer
>>>>> service, it will start properly (however I will have the dissapearing
>>>>> vmm.sys problem_
>>>>>
>>>>> Thank
>>>>>
>>>>> ML
>>>>> "Ben Armstrong [MSFT]" <(email address - cut out)> wrote in message
>>>>> news:(email address - cut out)...
>>>>>> Hi Michel,
>>>>>>
>>>>>> Your problem is completely different. The issue being discussed here
>>>>>> does not involve SPNs or the VM Helper.
>>>>>>
>>>>>> Are you still able to launch virtual machines? Is the Virtual Machine
>>>>>> Helper service running?
>>>>>> --
>>>>>> Cheers,
>>>>>> Benjamin Armstrong
>>>>>> ===============================
>>>>>> Virtual machine Program Manager
>>>>>>
>>>>>> This posting is provided "AS IS" with no warranties, and confers no
>>>>>> rights.
>>>>>> You assume all risk for your use.
>>>>>>
>>>>>> Michel Lapointe wrote:
>>>>>>> Hello,
>>>>>>>
>>>>>>> Having the same problem.
>>>>>>>
>>>>>>> VS 2005 R2 is install on a DC, running under Network Service, SPN
>>>>>>> has been registered.
>>>>>>>
>>>>>>> Everytime I start I have 3 error in the event log
>>>>>>>
>>>>>>> 1. A connection couldn't be created to the Virtual Machine Helper
>>>>>>> service. Virtual Server cannot run without a connection to the
>>>>>>> Virtual Machine Helper service.
>>>>>>>
>>>>>>> 2. The service principal names for Virtual Server could not be
>>>>>>> registered. Constrained delegation cannot be used until the SPNs have
>>>>>>> been registered manually. Error 0x80072098 - Insufficient access
>>>>>>> rights to perform the operation.
>>>>>>>
>>>>>>> 3. A connection couldn't be created to the Virtual Machine Helper
>>>>>>> service.
>>>>>>>
>>>>>>> Any idea / suggestion...
>>>>>>>
>>>>>>> Also all your 3 suggestions are not involved in my case
>>>>>>>
>>>>>>> Thank
>>>>>>>
>>>>>>> ML
>>>>>>> "Ben Armstrong [MSFT]" <(email address - cut out)> wrote in message
>>>>>>> news:(email address - cut out)...
>>>>>>>> This has been shown to occur due to three possible changes to the
>>>>>>>> system:
>>>>>>>>
>>>>>>>> 1. The Virtual Server service (vssrvc.exe) has been changed to run
>>>>>>>> under an account other than Network Service.
>>>>>>>>
>>>>>>>> 2. The NetworkService account has been given excessive power –
>>>>>>>> specifically, if it has been added to the Administrators group.
>>>>>>>> This defeats the purpose of having low-privilege service user
>>>>>>>> accounts like NetworkService and LocalService.
>>>>>>>>
>>>>>>>> 3. NetworkService has been granted the “Load and unload device
>>>>>>>> drivers” privilege in the Local Security Policy MMC snap-in.
>>>>>>>>
>>>>>>>> If you have done any of the above - please don't.
>>>>>>>> --
>>>>>>>> Cheers,
>>>>>>>> Benjamin Armstrong
>>>>>>>> ===============================
>>>>>>>> Virtual machine Program Manager
>>>>>>>>
>>>>>>>> This posting is provided "AS IS" with no warranties, and confers no
>>>>>>>> rights.
>>>>>>>> You assume all risk for your use.
>>>>>>>>
>>>>>>>> Max wrote:
>>>>>>>>>> VS runs after I freshly install it, but when I reboot the service
>>>>>>>>>> does not start. It states a dependency service has failed to
>>>>>>>>>> start. When i research this the VMM device is in a disabled state
>>>>>>>>>> and I cna not re-enable it. Any thoughts?
>>>>>>>>> I had this problem too. I looked at the registry key above and
>>>>>>>>> changed the "start" key value to 1, but still at reboot the service
>>>>>>>>> was gone. Checking regedit after the reboot revealed that the
>>>>>>>>> entire vmm tree was gone.
>>>>>>>>>
>>>>>>>>> I reinstalled, and had a look at the registry, and found a key
>>>>>>>>> called "deleteflag" which was set to 1. This tells windows to
>>>>>>>>> delete the service! I changed this to 0, changed the start key to
>>>>>>>>> 1 and rebooted and the service started properly.
>>>>>>>>>
>>>>>>>>> Now I've looked at the vmm key again, and the values have been
>>>>>>>>> changed back! I will change these manually for now, but best guess
>>>>>>>>> is that changing permissions on them will fix it once and for all.
>>>>>>>>>
>>>>>>>>> Cheers,
>>>>>>>>> Max.
>>>>>>>>>
>>>>>>>>> Posted via http://www.VirtualServerFaq.com - Brought to you by
>>>>>>>>> Business Information Technology Shop - http://www.bitshop.com
>

> Have you performed any security hardening on this system that may be
> causing a problem?
> --
> Cheers,
> Benjamin Armstrong
> ===============================
> Virtual machine Program Manager
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> You assume all risk for your use.
>
> Michel Lapointe wrote:
>> This is a DC with DNS/WINS/DHCP running on it.
>>
>> No change as been made
>>
>> ML
>> "Ben Armstrong [MSFT]" <(email address - cut out)> wrote in message
>> news:(email address - cut out)...
>>> Okay - that is correct. It is strange that the Service cannot access
>>> the helper. What other applications do you have running on the
>>> computer? Have you made any non-standard configuration changes?
>>> --
>>> Cheers,
>>> Benjamin Armstrong
>>> ===============================
>>> Virtual machine Program Manager
>>>
>>> This posting is provided "AS IS" with no warranties, and confers no
>>> rights.
>>> You assume all risk for your use.
>>>
>>> Michel Lapointe wrote:
>>>> Helper = Local System
>>>> VServer = Network System
>>>>
>>>> Thank
>>>> ML
>>>> "Ben Armstrong [MSFT]" <(email address - cut out)> wrote in message
>>>> news:(email address - cut out)...
>>>>> What account is the VM Helper running as?
>>>>> --
>>>>> Cheers,
>>>>> Benjamin Armstrong
>>>>> ===============================
>>>>> Virtual machine Program Manager
>>>>>
>>>>> This posting is provided "AS IS" with no warranties, and confers no
>>>>> rights.
>>>>> You assume all risk for your use.
>>>>>
>>>>> Michel Lapointe wrote:
>>>>>> Unless I change the user account for the services, no I can't launch
>>>>>> any virtual machine.
>>>>>>
>>>>>> If I don't update the SPN manually I will get the SPN failure.
>>>>>>
>>>>>> Helper service is running, and If I change the password for the
>>>>>> VServer service, it will start properly (however I will have the
>>>>>> dissapearing vmm.sys problem_
>>>>>>
>>>>>> Thank
>>>>>>
>>>>>> ML
>>>>>> "Ben Armstrong [MSFT]" <(email address - cut out)> wrote in message
>>>>>> news:(email address - cut out)...
>>>>>>> Hi Michel,
>>>>>>>
>>>>>>> Your problem is completely different. The issue being discussed
>>>>>>> here does not involve SPNs or the VM Helper.
>>>>>>>
>>>>>>> Are you still able to launch virtual machines? Is the Virtual
>>>>>>> Machine Helper service running?
>>>>>>> --
>>>>>>> Cheers,
>>>>>>> Benjamin Armstrong
>>>>>>> ===============================
>>>>>>> Virtual machine Program Manager
>>>>>>>
>>>>>>> This posting is provided "AS IS" with no warranties, and confers no
>>>>>>> rights.
>>>>>>> You assume all risk for your use.
>>>>>>>
>>>>>>> Michel Lapointe wrote:
>>>>>>>> Hello,
>>>>>>>>
>>>>>>>> Having the same problem.
>>>>>>>>
>>>>>>>> VS 2005 R2 is install on a DC, running under Network Service,
>>>>>>>> SPN has been registered.
>>>>>>>>
>>>>>>>> Everytime I start I have 3 error in the event log
>>>>>>>>
>>>>>>>> 1. A connection couldn't be created to the Virtual Machine
>>>>>>>> Helper service. Virtual Server cannot run without a connection to
>>>>>>>> the Virtual Machine Helper service.
>>>>>>>>
>>>>>>>> 2. The service principal names for Virtual Server could not be
>>>>>>>> registered. Constrained delegation cannot be used until the SPNs
>>>>>>>> have been registered manually. Error 0x80072098 - Insufficient
>>>>>>>> access rights to perform the operation.
>>>>>>>>
>>>>>>>> 3. A connection couldn't be created to the Virtual Machine
>>>>>>>> Helper service.
>>>>>>>>
>>>>>>>> Any idea / suggestion...
>>>>>>>>
>>>>>>>> Also all your 3 suggestions are not involved in my case
>>>>>>>>
>>>>>>>> Thank
>>>>>>>>
>>>>>>>> ML
>>>>>>>> "Ben Armstrong [MSFT]" <(email address - cut out)> wrote in
>>>>>>>> message news:(email address - cut out)...
>>>>>>>>> This has been shown to occur due to three possible changes to the
>>>>>>>>> system:
>>>>>>>>>
>>>>>>>>> 1. The Virtual Server service (vssrvc.exe) has been changed to run
>>>>>>>>> under an account other than Network Service.
>>>>>>>>>
>>>>>>>>> 2. The NetworkService account has been given excessive power –
>>>>>>>>> specifically, if it has been added to the Administrators group.
>>>>>>>>> This defeats the purpose of having low-privilege service user
>>>>>>>>> accounts like NetworkService and LocalService.
>>>>>>>>>
>>>>>>>>> 3. NetworkService has been granted the “Load and unload device
>>>>>>>>> drivers” privilege in the Local Security Policy MMC snap-in.
>>>>>>>>>
>>>>>>>>> If you have done any of the above - please don't.
>>>>>>>>> --
>>>>>>>>> Cheers,
>>>>>>>>> Benjamin Armstrong
>>>>>>>>> ===============================
>>>>>>>>> Virtual machine Program Manager
>>>>>>>>>
>>>>>>>>> This posting is provided "AS IS" with no warranties, and confers
>>>>>>>>> no rights.
>>>>>>>>> You assume all risk for your use.
>>>>>>>>>
>>>>>>>>> Max wrote:
>>>>>>>>>>> VS runs after I freshly install it, but when I reboot the
>>>>>>>>>>> service does not start. It states a dependency service has
>>>>>>>>>>> failed to start. When i research this the VMM device is in a
>>>>>>>>>>> disabled state and I cna not re-enable it. Any thoughts?
>>>>>>>>>> I had this problem too. I looked at the registry key above and
>>>>>>>>>> changed the "start" key value to 1, but still at reboot the
>>>>>>>>>> service was gone. Checking regedit after the reboot revealed that
>>>>>>>>>> the entire vmm tree was gone.
>>>>>>>>>>
>>>>>>>>>> I reinstalled, and had a look at the registry, and found a key
>>>>>>>>>> called "deleteflag" which was set to 1. This tells windows to
>>>>>>>>>> delete the service! I changed this to 0, changed the start key
>>>>>>>>>> to 1 and rebooted and the service started properly.
>>>>>>>>>>
>>>>>>>>>> Now I've looked at the vmm key again, and the values have been
>>>>>>>>>> changed back! I will change these manually for now, but best
>>>>>>>>>> guess is that changing permissions on them will fix it once and
>>>>>>>>>> for all.
>>>>>>>>>>
>>>>>>>>>> Cheers,
>>>>>>>>>> Max.
>>>>>>>>>>
>>>>>>>>>> Posted via http://www.VirtualServerFaq.com - Brought to you by
>>>>>>>>>> Business Information Technology Shop - http://www.bitshop.com
>>

> No
>
> This is a freshly installed DC with Virtual Server
>
> ML
> "Ben Armstrong [MSFT]" <(email address - cut out)> wrote in message
> news:%23$(email address - cut out)...
>> Have you performed any security hardening on this system that may be
>> causing a problem?
>> --
>> Cheers,
>> Benjamin Armstrong
>> ===============================
>> Virtual machine Program Manager
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> You assume all risk for your use.
>>
>> Michel Lapointe wrote:
>>> This is a DC with DNS/WINS/DHCP running on it.
>>>
>>> No change as been made
>>>
>>> ML
>>> "Ben Armstrong [MSFT]" <(email address - cut out)> wrote in message
>>> news:(email address - cut out)...
>>>> Okay - that is correct. It is strange that the Service cannot access
>>>> the helper. What other applications do you have running on the
>>>> computer? Have you made any non-standard configuration changes?
>>>> --
>>>> Cheers,
>>>> Benjamin Armstrong
>>>> ===============================
>>>> Virtual machine Program Manager
>>>>
>>>> This posting is provided "AS IS" with no warranties, and confers no
>>>> rights.
>>>> You assume all risk for your use.
>>>>
>>>> Michel Lapointe wrote:
>>>>> Helper = Local System
>>>>> VServer = Network System
>>>>>
>>>>> Thank
>>>>> ML
>>>>> "Ben Armstrong [MSFT]" <(email address - cut out)> wrote in message
>>>>> news:(email address - cut out)...
>>>>>> What account is the VM Helper running as?
>>>>>> --
>>>>>> Cheers,
>>>>>> Benjamin Armstrong
>>>>>> ===============================
>>>>>> Virtual machine Program Manager
>>>>>>
>>>>>> This posting is provided "AS IS" with no warranties, and confers no
>>>>>> rights.
>>>>>> You assume all risk for your use.
>>>>>>
>>>>>> Michel Lapointe wrote:
>>>>>>> Unless I change the user account for the services, no I can't launch
>>>>>>> any virtual machine.
>>>>>>>
>>>>>>> If I don't update the SPN manually I will get the SPN failure.
>>>>>>>
>>>>>>> Helper service is running, and If I change the password for the
>>>>>>> VServer service, it will start properly (however I will have the
>>>>>>> dissapearing vmm.sys problem_
>>>>>>>
>>>>>>> Thank
>>>>>>>
>>>>>>> ML
>>>>>>> "Ben Armstrong [MSFT]" <(email address - cut out)> wrote in message
>>>>>>> news:(email address - cut out)...
>>>>>>>> Hi Michel,
>>>>>>>>
>>>>>>>> Your problem is completely different. The issue being discussed
>>>>>>>> here does not involve SPNs or the VM Helper.
>>>>>>>>
>>>>>>>> Are you still able to launch virtual machines? Is the Virtual
>>>>>>>> Machine Helper service running?
>>>>>>>> --
>>>>>>>> Cheers,
>>>>>>>> Benjamin Armstrong
>>>>>>>> ===============================
>>>>>>>> Virtual machine Program Manager
>>>>>>>>
>>>>>>>> This posting is provided "AS IS" with no warranties, and confers no
>>>>>>>> rights.
>>>>>>>> You assume all risk for your use.
>>>>>>>>
>>>>>>>> Michel Lapointe wrote:
>>>>>>>>> Hello,
>>>>>>>>>
>>>>>>>>> Having the same problem.
>>>>>>>>>
>>>>>>>>> VS 2005 R2 is install on a DC, running under Network Service,
>>>>>>>>> SPN has been registered.
>>>>>>>>>
>>>>>>>>> Everytime I start I have 3 error in the event log
>>>>>>>>>
>>>>>>>>> 1. A connection couldn't be created to the Virtual Machine
>>>>>>>>> Helper service. Virtual Server cannot run without a connection to
>>>>>>>>> the Virtual Machine Helper service.
>>>>>>>>>
>>>>>>>>> 2. The service principal names for Virtual Server could not be
>>>>>>>>> registered. Constrained delegation cannot be used until the SPNs
>>>>>>>>> have been registered manually. Error 0x80072098 - Insufficient
>>>>>>>>> access rights to perform the operation.
>>>>>>>>>
>>>>>>>>> 3. A connection couldn't be created to the Virtual Machine
>>>>>>>>> Helper service.
>>>>>>>>>
>>>>>>>>> Any idea / suggestion...
>>>>>>>>>
>>>>>>>>> Also all your 3 suggestions are not involved in my case
>>>>>>>>>
>>>>>>>>> Thank
>>>>>>>>>
>>>>>>>>> ML
>>>>>>>>> "Ben Armstrong [MSFT]" <(email address - cut out)> wrote in
>>>>>>>>> message news:(email address - cut out)...
>>>>>>>>>> This has been shown to occur due to three possible changes to the
>>>>>>>>>> system:
>>>>>>>>>>
>>>>>>>>>> 1. The Virtual Server service (vssrvc.exe) has been changed to run
>>>>>>>>>> under an account other than Network Service.
>>>>>>>>>>
>>>>>>>>>> 2. The NetworkService account has been given excessive power –
>>>>>>>>>> specifically, if it has been added to the Administrators group.
>>>>>>>>>> This defeats the purpose of having low-privilege service user
>>>>>>>>>> accounts like NetworkService and LocalService.
>>>>>>>>>>
>>>>>>>>>> 3. NetworkService has been granted the “Load and unload device
>>>>>>>>>> drivers” privilege in the Local Security Policy MMC snap-in.
>>>>>>>>>>
>>>>>>>>>> If you have done any of the above - please don't.
>>>>>>>>>> --
>>>>>>>>>> Cheers,
>>>>>>>>>> Benjamin Armstrong
>>>>>>>>>> ===============================
>>>>>>>>>> Virtual machine Program Manager
>>>>>>>>>>
>>>>>>>>>> This posting is provided "AS IS" with no warranties, and confers
>>>>>>>>>> no rights.
>>>>>>>>>> You assume all risk for your use.
>>>>>>>>>>
>>>>>>>>>> Max wrote:
>>>>>>>>>>>> VS runs after I freshly install it, but when I reboot the
>>>>>>>>>>>> service does not start. It states a dependency service has
>>>>>>>>>>>> failed to start. When i research this the VMM device is in a
>>>>>>>>>>>> disabled state and I cna not re-enable it. Any thoughts?
>>>>>>>>>>> I had this problem too. I looked at the registry key above and
>>>>>>>>>>> changed the "start" key value to 1, but still at reboot the
>>>>>>>>>>> service was gone. Checking regedit after the reboot revealed that
>>>>>>>>>>> the entire vmm tree was gone.
>>>>>>>>>>>
>>>>>>>>>>> I reinstalled, and had a look at the registry, and found a key
>>>>>>>>>>> called "deleteflag" which was set to 1. This tells windows to
>>>>>>>>>>> delete the service! I changed this to 0, changed the start key
>>>>>>>>>>> to 1 and rebooted and the service started properly.
>>>>>>>>>>>
>>>>>>>>>>> Now I've looked at the vmm key again, and the values have been
>>>>>>>>>>> changed back! I will change these manually for now, but best
>>>>>>>>>>> guess is that changing permissions on them will fix it once and
>>>>>>>>>>> for all.
>>>>>>>>>>>
>>>>>>>>>>> Cheers,
>>>>>>>>>>> Max.
>>>>>>>>>>>
>>>>>>>>>>> Posted via http://www.VirtualServerFaq.com - Brought to you by
>>>>>>>>>>> Business Information Technology Shop - http://www.bitshop.com
>
>

>I have no idea why this is failing then. If it really is a fresh install
>of the host this should just work.
> --
> Cheers,
> Benjamin Armstrong
> ===============================
> Virtual machine Program Manager
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> You assume all risk for your use.
>
> Michel Lapointe wrote:
>> No
>>
>> This is a freshly installed DC with Virtual Server
>>
>> ML
>> "Ben Armstrong [MSFT]" <(email address - cut out)> wrote in message
>> news:%23$(email address - cut out)...
>>> Have you performed any security hardening on this system that may be
>>> causing a problem?
>>> --
>>> Cheers,
>>> Benjamin Armstrong
>>> ===============================
>>> Virtual machine Program Manager
>>>
>>> This posting is provided "AS IS" with no warranties, and confers no
>>> rights.
>>> You assume all risk for your use.
>>>
>>> Michel Lapointe wrote:
>>>> This is a DC with DNS/WINS/DHCP running on it.
>>>>
>>>> No change as been made
>>>>
>>>> ML
>>>> "Ben Armstrong [MSFT]" <(email address - cut out)> wrote in message
>>>> news:(email address - cut out)...
>>>>> Okay - that is correct. It is strange that the Service cannot access
>>>>> the helper. What other applications do you have running on the
>>>>> computer? Have you made any non-standard configuration changes?
>>>>> --
>>>>> Cheers,
>>>>> Benjamin Armstrong
>>>>> ===============================
>>>>> Virtual machine Program Manager
>>>>>
>>>>> This posting is provided "AS IS" with no warranties, and confers no
>>>>> rights.
>>>>> You assume all risk for your use.
>>>>>
>>>>> Michel Lapointe wrote:
>>>>>> Helper = Local System
>>>>>> VServer = Network System
>>>>>>
>>>>>> Thank
>>>>>> ML
>>>>>> "Ben Armstrong [MSFT]" <(email address - cut out)> wrote in message
>>>>>> news:(email address - cut out)...
>>>>>>> What account is the VM Helper running as?
>>>>>>> --
>>>>>>> Cheers,
>>>>>>> Benjamin Armstrong
>>>>>>> ===============================
>>>>>>> Virtual machine Program Manager
>>>>>>>
>>>>>>> This posting is provided "AS IS" with no warranties, and confers no
>>>>>>> rights.
>>>>>>> You assume all risk for your use.
>>>>>>>
>>>>>>> Michel Lapointe wrote:
>>>>>>>> Unless I change the user account for the services, no I can't
>>>>>>>> launch any virtual machine.
>>>>>>>>
>>>>>>>> If I don't update the SPN manually I will get the SPN failure.
>>>>>>>>
>>>>>>>> Helper service is running, and If I change the password for the
>>>>>>>> VServer service, it will start properly (however I will have the
>>>>>>>> dissapearing vmm.sys problem_
>>>>>>>>
>>>>>>>> Thank
>>>>>>>>
>>>>>>>> ML
>>>>>>>> "Ben Armstrong [MSFT]" <(email address - cut out)> wrote in
>>>>>>>> message news:(email address - cut out)...
>>>>>>>>> Hi Michel,
>>>>>>>>>
>>>>>>>>> Your problem is completely different. The issue being discussed
>>>>>>>>> here does not involve SPNs or the VM Helper.
>>>>>>>>>
>>>>>>>>> Are you still able to launch virtual machines? Is the Virtual
>>>>>>>>> Machine Helper service running?
>>>>>>>>> --
>>>>>>>>> Cheers,
>>>>>>>>> Benjamin Armstrong
>>>>>>>>> ===============================
>>>>>>>>> Virtual machine Program Manager
>>>>>>>>>
>>>>>>>>> This posting is provided "AS IS" with no warranties, and confers
>>>>>>>>> no rights.
>>>>>>>>> You assume all risk for your use.
>>>>>>>>>
>>>>>>>>> Michel Lapointe wrote:
>>>>>>>>>> Hello,
>>>>>>>>>>
>>>>>>>>>> Having the same problem.
>>>>>>>>>>
>>>>>>>>>> VS 2005 R2 is install on a DC, running under Network Service,
>>>>>>>>>> SPN has been registered.
>>>>>>>>>>
>>>>>>>>>> Everytime I start I have 3 error in the event log
>>>>>>>>>>
>>>>>>>>>> 1. A connection couldn't be created to the Virtual Machine
>>>>>>>>>> Helper service. Virtual Server cannot run without a connection to
>>>>>>>>>> the Virtual Machine Helper service.
>>>>>>>>>>
>>>>>>>>>> 2. The service principal names for Virtual Server could not
>>>>>>>>>> be registered. Constrained delegation cannot be used until the
>>>>>>>>>> SPNs have been registered manually. Error 0x80072098 -
>>>>>>>>>> Insufficient access rights to perform the operation.
>>>>>>>>>>
>>>>>>>>>> 3. A connection couldn't be created to the Virtual Machine
>>>>>>>>>> Helper service.
>>>>>>>>>>
>>>>>>>>>> Any idea / suggestion...
>>>>>>>>>>
>>>>>>>>>> Also all your 3 suggestions are not involved in my case
>>>>>>>>>>
>>>>>>>>>> Thank
>>>>>>>>>>
>>>>>>>>>> ML
>>>>>>>>>> "Ben Armstrong [MSFT]" <(email address - cut out)> wrote in
>>>>>>>>>> message news:(email address - cut out)...
>>>>>>>>>>> This has been shown to occur due to three possible changes to
>>>>>>>>>>> the system:
>>>>>>>>>>>
>>>>>>>>>>> 1. The Virtual Server service (vssrvc.exe) has been changed to
>>>>>>>>>>> run under an account other than Network Service.
>>>>>>>>>>>
>>>>>>>>>>> 2. The NetworkService account has been given excessive power –
>>>>>>>>>>> specifically, if it has been added to the Administrators group.
>>>>>>>>>>> This defeats the purpose of having low-privilege service user
>>>>>>>>>>> accounts like NetworkService and LocalService.
>>>>>>>>>>>
>>>>>>>>>>> 3. NetworkService has been granted the “Load and unload device
>>>>>>>>>>> drivers” privilege in the Local Security Policy MMC snap-in.
>>>>>>>>>>>
>>>>>>>>>>> If you have done any of the above - please don't.
>>>>>>>>>>> --
>>>>>>>>>>> Cheers,
>>>>>>>>>>> Benjamin Armstrong
>>>>>>>>>>> ===============================
>>>>>>>>>>> Virtual machine Program Manager
>>>>>>>>>>>
>>>>>>>>>>> This posting is provided "AS IS" with no warranties, and confers
>>>>>>>>>>> no rights.
>>>>>>>>>>> You assume all risk for your use.
>>>>>>>>>>>
>>>>>>>>>>> Max wrote:
>>>>>>>>>>>>> VS runs after I freshly install it, but when I reboot the
>>>>>>>>>>>>> service does not start. It states a dependency service has
>>>>>>>>>>>>> failed to start. When i research this the VMM device is in a
>>>>>>>>>>>>> disabled state and I cna not re-enable it. Any thoughts?
>>>>>>>>>>>> I had this problem too. I looked at the registry key above and
>>>>>>>>>>>> changed the "start" key value to 1, but still at reboot the
>>>>>>>>>>>> service was gone. Checking regedit after the reboot revealed
>>>>>>>>>>>> that the entire vmm tree was gone.
>>>>>>>>>>>>
>>>>>>>>>>>> I reinstalled, and had a look at the registry, and found a key
>>>>>>>>>>>> called "deleteflag" which was set to 1. This tells windows to
>>>>>>>>>>>> delete the service! I changed this to 0, changed the start key
>>>>>>>>>>>> to 1 and rebooted and the service started properly.
>>>>>>>>>>>>
>>>>>>>>>>>> Now I've looked at the vmm key again, and the values have been
>>>>>>>>>>>> changed back! I will change these manually for now, but best
>>>>>>>>>>>> guess is that changing permissions on them will fix it once and
>>>>>>>>>>>> for all.
>>>>>>>>>>>>
>>>>>>>>>>>> Cheers,
>>>>>>>>>>>> Max.
>>>>>>>>>>>>
>>>>>>>>>>>> Posted via http://www.VirtualServerFaq.com - Brought to you by
>>>>>>>>>>>> Business Information Technology Shop - http://www.bitshop.com
>>

> Ok... So what do we do when it won't ? :)
>
> THank
>
> ML
> "Ben Armstrong [MSFT]" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
>> I have no idea why this is failing then. If it really is a fresh install
>> of the host this should just work.
>> --
>> Cheers,
>> Benjamin Armstrong
>> ===============================
>> Virtual machine Program Manager
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> You assume all risk for your use.
>>
>> Michel Lapointe wrote:
>>> No
>>>
>>> This is a freshly installed DC with Virtual Server
>>>
>>> ML
>>> "Ben Armstrong [MSFT]" <(email address - cut out)> wrote in message
>>> news:%23$(email address - cut out)...
>>>> Have you performed any security hardening on this system that may be
>>>> causing a problem?
>>>> --
>>>> Cheers,
>>>> Benjamin Armstrong
>>>> ===============================
>>>> Virtual machine Program Manager
>>>>
>>>> This posting is provided "AS IS" with no warranties, and confers no
>>>> rights.
>>>> You assume all risk for your use.
>>>>
>>>> Michel Lapointe wrote:
>>>>> This is a DC with DNS/WINS/DHCP running on it.
>>>>>
>>>>> No change as been made
>>>>>
>>>>> ML
>>>>> "Ben Armstrong [MSFT]" <(email address - cut out)> wrote in message
>>>>> news:(email address - cut out)...
>>>>>> Okay - that is correct. It is strange that the Service cannot access
>>>>>> the helper. What other applications do you have running on the
>>>>>> computer? Have you made any non-standard configuration changes?
>>>>>> --
>>>>>> Cheers,
>>>>>> Benjamin Armstrong
>>>>>> ===============================
>>>>>> Virtual machine Program Manager
>>>>>>
>>>>>> This posting is provided "AS IS" with no warranties, and confers no
>>>>>> rights.
>>>>>> You assume all risk for your use.
>>>>>>
>>>>>> Michel Lapointe wrote:
>>>>>>> Helper = Local System
>>>>>>> VServer = Network System
>>>>>>>
>>>>>>> Thank
>>>>>>> ML
>>>>>>> "Ben Armstrong [MSFT]" <(email address - cut out)> wrote in message
>>>>>>> news:(email address - cut out)...
>>>>>>>> What account is the VM Helper running as?
>>>>>>>> --
>>>>>>>> Cheers,
>>>>>>>> Benjamin Armstrong
>>>>>>>> ===============================
>>>>>>>> Virtual machine Program Manager
>>>>>>>>
>>>>>>>> This posting is provided "AS IS" with no warranties, and confers no
>>>>>>>> rights.
>>>>>>>> You assume all risk for your use.
>>>>>>>>
>>>>>>>> Michel Lapointe wrote:
>>>>>>>>> Unless I change the user account for the services, no I can't
>>>>>>>>> launch any virtual machine.
>>>>>>>>>
>>>>>>>>> If I don't update the SPN manually I will get the SPN failure.
>>>>>>>>>
>>>>>>>>> Helper service is running, and If I change the password for the
>>>>>>>>> VServer service, it will start properly (however I will have the
>>>>>>>>> dissapearing vmm.sys problem_
>>>>>>>>>
>>>>>>>>> Thank
>>>>>>>>>
>>>>>>>>> ML
>>>>>>>>> "Ben Armstrong [MSFT]" <(email address - cut out)> wrote in
>>>>>>>>> message news:(email address - cut out)...
>>>>>>>>>> Hi Michel,
>>>>>>>>>>
>>>>>>>>>> Your problem is completely different. The issue being discussed
>>>>>>>>>> here does not involve SPNs or the VM Helper.
>>>>>>>>>>
>>>>>>>>>> Are you still able to launch virtual machines? Is the Virtual
>>>>>>>>>> Machine Helper service running?
>>>>>>>>>> --
>>>>>>>>>> Cheers,
>>>>>>>>>> Benjamin Armstrong
>>>>>>>>>> ===============================
>>>>>>>>>> Virtual machine Program Manager
>>>>>>>>>>
>>>>>>>>>> This posting is provided "AS IS" with no warranties, and confers
>>>>>>>>>> no rights.
>>>>>>>>>> You assume all risk for your use.
>>>>>>>>>>
>>>>>>>>>> Michel Lapointe wrote:
>>>>>>>>>>> Hello,
>>>>>>>>>>>
>>>>>>>>>>> Having the same problem.
>>>>>>>>>>>
>>>>>>>>>>> VS 2005 R2 is install on a DC, running under Network Service,
>>>>>>>>>>> SPN has been registered.
>>>>>>>>>>>
>>>>>>>>>>> Everytime I start I have 3 error in the event log
>>>>>>>>>>>
>>>>>>>>>>> 1. A connection couldn't be created to the Virtual Machine
>>>>>>>>>>> Helper service. Virtual Server cannot run without a connection to
>>>>>>>>>>> the Virtual Machine Helper service.
>>>>>>>>>>>
>>>>>>>>>>> 2. The service principal names for Virtual Server could not
>>>>>>>>>>> be registered. Constrained delegation cannot be used until the
>>>>>>>>>>> SPNs have been registered manually. Error 0x80072098 -
>>>>>>>>>>> Insufficient access rights to perform the operation.
>>>>>>>>>>>
>>>>>>>>>>> 3. A connection couldn't be created to the Virtual Machine
>>>>>>>>>>> Helper service.
>>>>>>>>>>>
>>>>>>>>>>> Any idea / suggestion...
>>>>>>>>>>>
>>>>>>>>>>> Also all your 3 suggestions are not involved in my case
>>>>>>>>>>>
>>>>>>>>>>> Thank
>>>>>>>>>>>
>>>>>>>>>>> ML
>>>>>>>>>>> "Ben Armstrong [MSFT]" <(email address - cut out)> wrote in
>>>>>>>>>>> message news:(email address - cut out)...
>>>>>>>>>>>> This has been shown to occur due to three possible changes to
>>>>>>>>>>>> the system:
>>>>>>>>>>>>
>>>>>>>>>>>> 1. The Virtual Server service (vssrvc.exe) has been changed to
>>>>>>>>>>>> run under an account other than Network Service.
>>>>>>>>>>>>
>>>>>>>>>>>> 2. The NetworkService account has been given excessive power –
>>>>>>>>>>>> specifically, if it has been added to the Administrators group.
>>>>>>>>>>>> This defeats the purpose of having low-privilege service user
>>>>>>>>>>>> accounts like NetworkService and LocalService.
>>>>>>>>>>>>
>>>>>>>>>>>> 3. NetworkService has been granted the “Load and unload device
>>>>>>>>>>>> drivers” privilege in the Local Security Policy MMC snap-in.
>>>>>>>>>>>>
>>>>>>>>>>>> If you have done any of the above - please don't.
>>>>>>>>>>>> --
>>>>>>>>>>>> Cheers,
>>>>>>>>>>>> Benjamin Armstrong
>>>>>>>>>>>> ===============================
>>>>>>>>>>>> Virtual machine Program Manager
>>>>>>>>>>>>
>>>>>>>>>>>> This posting is provided "AS IS" with no warranties, and confers
>>>>>>>>>>>> no rights.
>>>>>>>>>>>> You assume all risk for your use.
>>>>>>>>>>>>
>>>>>>>>>>>> Max wrote:
>>>>>>>>>>>>>> VS runs after I freshly install it, but when I reboot the
>>>>>>>>>>>>>> service does not start. It states a dependency service has
>>>>>>>>>>>>>> failed to start. When i research this the VMM device is in a
>>>>>>>>>>>>>> disabled state and I cna not re-enable it. Any thoughts?
>>>>>>>>>>>>> I had this problem too. I looked at the registry key above and
>>>>>>>>>>>>> changed the "start" key value to 1, but still at reboot the
>>>>>>>>>>>>> service was gone. Checking regedit after the reboot revealed
>>>>>>>>>>>>> that the entire vmm tree was gone.
>>>>>>>>>>>>>
>>>>>>>>>>>>> I reinstalled, and had a look at the registry, and found a key
>>>>>>>>>>>>> called "deleteflag" which was set to 1. This tells windows to
>>>>>>>>>>>>> delete the service! I changed this to 0, changed the start key
>>>>>>>>>>>>> to 1 and rebooted and the service started properly.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Now I've looked at the vmm key again, and the values have been
>>>>>>>>>>>>> changed back! I will change these manually for now, but best
>>>>>>>>>>>>> guess is that changing permissions on them will fix it once and
>>>>>>>>>>>>> for all.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Cheers,
>>>>>>>>>>>>> Max.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Posted via http://www.VirtualServerFaq.com - Brought to you by
>>>>>>>>>>>>> Business Information Technology Shop - http://www.bitshop.com
>

> Contacting Microsoft Product Support is probably your best option. If
> you want an unsupported (but working) configuration - check the rest of
> this thread and you should find a comment about how to tweak the
> registry such that you can run the Virtual Server service as a standard
> user account without the VMM getting removed.
> --
> Cheers,
> Benjamin Armstrong
> ===============================
> Virtual machine Program Manager
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
> You assume all risk for your use.
>
> Michel Lapointe wrote:
> > Ok... So what do we do when it won't ? :)
> >
> > THank
> >
> > ML
> > "Ben Armstrong [MSFT]" <(email address - cut out)> wrote in message
> > news:(email address - cut out)...
> >> I have no idea why this is failing then. If it really is a fresh install
> >> of the host this should just work.
> >> --
> >> Cheers,
> >> Benjamin Armstrong
> >> ===============================
> >> Virtual machine Program Manager
> >>
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights.
> >> You assume all risk for your use.
> >>
> >> Michel Lapointe wrote:
> >>> No
> >>>
> >>> This is a freshly installed DC with Virtual Server
> >>>
> >>> ML
> >>> "Ben Armstrong [MSFT]" <(email address - cut out)> wrote in message
> >>> news:%23$(email address - cut out)...
> >>>> Have you performed any security hardening on this system that may be
> >>>> causing a problem?
> >>>> --
> >>>> Cheers,
> >>>> Benjamin Armstrong
> >>>> ===============================
> >>>> Virtual machine Program Manager
> >>>>
> >>>> This posting is provided "AS IS" with no warranties, and confers no
> >>>> rights.
> >>>> You assume all risk for your use.
> >>>>
> >>>> Michel Lapointe wrote:
> >>>>> This is a DC with DNS/WINS/DHCP running on it.
> >>>>>
> >>>>> No change as been made
> >>>>>
> >>>>> ML
> >>>>> "Ben Armstrong [MSFT]" <(email address - cut out)> wrote in message
> >>>>> news:(email address - cut out)...
> >>>>>> Okay - that is correct. It is strange that the Service cannot access
> >>>>>> the helper. What other applications do you have running on the
> >>>>>> computer? Have you made any non-standard configuration changes?
> >>>>>> --
> >>>>>> Cheers,
> >>>>>> Benjamin Armstrong
> >>>>>> ===============================
> >>>>>> Virtual machine Program Manager
> >>>>>>
> >>>>>> This posting is provided "AS IS" with no warranties, and confers no
> >>>>>> rights.
> >>>>>> You assume all risk for your use.
> >>>>>>
> >>>>>> Michel Lapointe wrote:
> >>>>>>> Helper = Local System
> >>>>>>> VServer = Network System
> >>>>>>>
> >>>>>>> Thank
> >>>>>>> ML
> >>>>>>> "Ben Armstrong [MSFT]" <(email address - cut out)> wrote in message
> >>>>>>> news:(email address - cut out)...
> >>>>>>>> What account is the VM Helper running as?
> >>>>>>>> --
> >>>>>>>> Cheers,
> >>>>>>>> Benjamin Armstrong
> >>>>>>>> ===============================
> >>>>>>>> Virtual machine Program Manager
> >>>>>>>>
> >>>>>>>> This posting is provided "AS IS" with no warranties, and confers no
> >>>>>>>> rights.
> >>>>>>>> You assume all risk for your use.
> >>>>>>>>
> >>>>>>>> Michel Lapointe wrote:
> >>>>>>>>> Unless I change the user account for the services, no I can't
> >>>>>>>>> launch any virtual machine.
> >>>>>>>>>
> >>>>>>>>> If I don't update the SPN manually I will get the SPN failure.
> >>>>>>>>>
> >>>>>>>>> Helper service is running, and If I change the password for the
> >>>>>>>>> VServer service, it will start properly (however I will have the
> >>>>>>>>> dissapearing vmm.sys problem_
> >>>>>>>>>
> >>>>>>>>> Thank
> >>>>>>>>>
> >>>>>>>>> ML
> >>>>>>>>> "Ben Armstrong [MSFT]" <(email address - cut out)> wrote in
> >>>>>>>>> message news:(email address - cut out)...
> >>>>>>>>>> Hi Michel,
> >>>>>>>>>>
> >>>>>>>>>> Your problem is completely different. The issue being discussed
> >>>>>>>>>> here does not involve SPNs or the VM Helper.
> >>>>>>>>>>
> >>>>>>>>>> Are you still able to launch virtual machines? Is the Virtual
> >>>>>>>>>> Machine Helper service running?
> >>>>>>>>>> --
> >>>>>>>>>> Cheers,
> >>>>>>>>>> Benjamin Armstrong
> >>>>>>>>>> ===============================
> >>>>>>>>>> Virtual machine Program Manager
> >>>>>>>>>>
> >>>>>>>>>> This posting is provided "AS IS" with no warranties, and confers
> >>>>>>>>>> no rights.
> >>>>>>>>>> You assume all risk for your use.
> >>>>>>>>>>
> >>>>>>>>>> Michel Lapointe wrote:
> >>>>>>>>>>> Hello,
> >>>>>>>>>>>
> >>>>>>>>>>> Having the same problem.
> >>>>>>>>>>>
> >>>>>>>>>>> VS 2005 R2 is install on a DC, running under Network Service,
> >>>>>>>>>>> SPN has been registered.
> >>>>>>>>>>>
> >>>>>>>>>>> Everytime I start I have 3 error in the event log
> >>>>>>>>>>>
> >>>>>>>>>>> 1. A connection couldn't be created to the Virtual Machine
> >>>>>>>>>>> Helper service. Virtual Server cannot run without a connection to
> >>>>>>>>>>> the Virtual Machine Helper service.
> >>>>>>>>>>>
> >>>>>>>>>>> 2. The service principal names for Virtual Server could not
> >>>>>>>>>>> be registered. Constrained delegation cannot be used until the
> >>>>>>>>>>> SPNs have been registered manually. Error 0x80072098 -
> >>>>>>>>>>> Insufficient access rights to perform the operation.
> >>>>>>>>>>>
> >>>>>>>>>>> 3. A connection couldn't be created to the Virtual Machine
> >>>>>>>>>>> Helper service.
> >>>>>>>>>>>
> >>>>>>>>>>> Any idea / suggestion...
> >>>>>>>>>>>
> >>>>>>>>>>> Also all your 3 suggestions are not involved in my case
> >>>>>>>>>>>
> >>>>>>>>>>> Thank
> >>>>>>>>>>>
> >>>>>>>>>>> ML
> >>>>>>>>>>> "Ben Armstrong [MSFT]" <(email address - cut out)> wrote in
> >>>>>>>>>>> message news:(email address - cut out)...
> >>>>>>>>>>>> This has been shown to occur due to three possible changes to
> >>>>>>>>>>>> the system:
> >>>>>>>>>>>>
> >>>>>>>>>>>> 1. The Virtual Server service (vssrvc.exe) has been changed to
> >>>>>>>>>>>> run under an account other than Network Service.
> >>>>>>>>>>>>
> >>>>>>>>>>>> 2. The NetworkService account has been given excessive power –
> >>>>>>>>>>>> specifically, if it has been added to the Administrators group.
> >>>>>>>>>>>> This defeats the purpose of having low-privilege service user
> >>>>>>>>>>>> accounts like NetworkService and LocalService.
> >>>>>>>>>>>>
> >>>>>>>>>>>> 3. NetworkService has been granted the “Load and unload device
> >>>>>>>>>>>> drivers” privilege in the Local Security Policy MMC snap-in.
> >>>>>>>>>>>>
> >>>>>>>>>>>> If you have done any of the above - please don't.
> >>>>>>>>>>>> --
> >>>>>>>>>>>> Cheers,
> >>>>>>>>>>>> Benjamin Armstrong
> >>>>>>>>>>>> ===============================
> >>>>>>>>>>>> Virtual machine Program Manager
> >>>>>>>>>>>>
> >>>>>>>>>>>> This posting is provided "AS IS" with no warranties, and confers
> >>>>>>>>>>>> no rights.
> >>>>>>>>>>>> You assume all risk for your use.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Max wrote:
> >>>>>>>>>>>>>> VS runs after I freshly install it, but when I reboot the
> >>>>>>>>>>>>>> service does not start. It states a dependency service has
> >>>>>>>>>>>>>> failed to start. When i research this the VMM device is in a
> >>>>>>>>>>>>>> disabled state and I cna not re-enable it. Any thoughts?
> >>>>>>>>>>>>> I had this problem too. I looked at the registry key above and
> >>>>>>>>>>>>> changed the "start" key value to 1, but still at reboot the
> >>>>>>>>>>>>> service was gone. Checking regedit after the reboot revealed
> >>>>>>>>>>>>> that the entire vmm tree was gone.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> I reinstalled, and had a look at the registry, and found a key
> >>>>>>>>>>>>> called "deleteflag" which was set to 1. This tells windows to
> >>>>>>>>>>>>> delete the service! I changed this to 0, changed the start key
> >>>>>>>>>>>>> to 1 and rebooted and the service started properly.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Now I've looked at the vmm key again, and the values have been
> >>>>>>>>>>>>> changed back! I will change these manually for now, but best
> >>>>>>>>>>>>> guess is that changing permissions on them will fix it once and
> >>>>>>>>>>>>> for all.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Cheers,
> >>>>>>>>>>>>> Max.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Posted via http://www.VirtualServerFaq.com - Brought to you by
> >>>>>>>>>>>>> Business Information Technology Shop - http://www.bitshop.com
> >
>