Sign in
 
HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums
Windows Server TechCenter >
> 
> 
Windows Server 2012 Hyper-V managment service shutsdown when connection to RDS connection broker

Proposed Windows Server 2012 Hyper-V managment service shutsdown when connection to RDS connection broker

  • Wednesday, October 10, 2012 6:41 PM
     
     
    Sign In to Vote
    0

    Hi

    I have three Hyper-V 2012 servers all running the RDS virtualisation host service in order to host a Windows 8 VDI infrastructure.  I have started to received an issue that occurs every night at 00:45 hrs.  The VMMS service stops on all three of the hosts at this time and there for stops serving the desktop images.

    If I remove the RDS virtualisation host role from one of the Hyper-V servers but leave the desktop VM's running the service is stable and does not shut down nightly.

    I have been through the VMMS log files and see nothing un ordinary.  There is an event stating that the service has received a stop command and then that's it.

    I am running Windows Server 2012 RTM with GUI on all three of the host servers as well as the separate server hosting the RDS connection broker role.  All installs were clean installs i.e not upgrades from 2008 R2

    Has any one come across this issue?

     

All Replies

  • Friday, October 12, 2012 2:27 AM
    Moderator
     
     
    Sign In to Vote
    0

    Hi,

    Thank you for your question.
    I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience.

    Thank you for your understanding and support.

    Best Regards,
    Aiden

    TechNet Subscriber Support

    If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.

    Aiden Cao

    TechNet Community Support

     
  • Friday, October 12, 2012 7:49 AM
     
     Proposed
    Sign In to Vote
    0

    Hi,

    Could you please try below information:

    a. Please check whether there are any scheduled tasks running at that time.

    b. Please check whether theses servers are overload when the issue occurs.

    c. If you try to start the VMM service manually when the issue ocucrs, does the issue turn to normal? If that is the case, we can consider to write a script to start the service at that time.

    d. Have you installed any applications/softwares (such as antivirus)on these servers? Please try to disable them and reproduce the issue

    Regards,

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

     
  • Thursday, October 18, 2012 5:35 AM
     
     
    Sign In to Vote
    0

    Hi,

    How are things going? I am just writing in to see if you need any further assistance from me. If there is anything I can do, feel free to let me know.

    Regards,

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

     
  • Tuesday, October 23, 2012 10:07 AM
     
     
    Sign In to Vote
    0

    Hi sorry for the slow response this has been causing me a few issues.  I actually have got a task in SCOM to restart the VMM service when it sees a failure over night.  the only scheduled task that runs on these machines around this time is an SCCM 2012 SP1 agent task to collect a hardware and software inventory.

    I have since disabled this task and the service is still stopping daily.  I would really like to get to the bottom of this rather than rely on a work around to resolve the issue.

    there are three Hyper-V servers all running server 2012 RTM that do this.  the servers are not actually running that much the busiest server is running 10 windows 8 virtual images and the servers each have 2 x 8 Core CPU's and 96Gb of RAM so certainly are not stretched.

     
  • Wednesday, October 24, 2012 4:11 AM
     
     
    Sign In to Vote
    0

    Hi,

    From your previous description you had mentioned that whent the issue occurred, there was  an event stating that the service has received a stop command, could you please show this event to us?

    If possible, please do a clean boot(http://support.microsoft.com/kb/929135) and check whether it causes by some third party applications on the Hypre-V host server.

    Besides, I would like to introduce a tool named Process Monitor http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx to you, this is an advanced monitoring tool for Windows that shows real-time file system, Registry and process/thread activity.

    Regards,

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

     
  • Thursday, January 10, 2013 1:24 PM
     
     
    Sign In to Vote
    0

    Hi

    I have the same issue as Mark. Daily and sometimes more than daily, the VMM service appears to be running, users that have disconnected from their remote VDI sessions are able to re connect via the broker, however if new users connect via the broker it fails to deliver them a session. At this point when you connect to the hyper-v server and try and start one of the VDI desktops it will not start, this is the same for any of the VMs on the host that are not currently running.

    The only way to resolve the problem is to restart the VMM service. This it’s self is becoming problematic as the VMM service fails to stop in a timely fashion and gets stuck in the stopping state for a good 10 mins; after which you can then manually start the VMM service and then new VDI sessions can be delivered once again.

     
  • Thursday, January 31, 2013 10:30 PM
     
      Has Code
    Sign In to Vote
    0

    Hi All,

    Get the same issue. Seems every night the SCVMMAgent and VMMS services fail. Although I believe it is the VMMS service that fails causing the SCVMMAgent to then stop and only on our Server 2012 machines.

    I had noticed that this happened on the RC version and now on the RTM. As I don't have SCOM I wrote a script (That I am having trouble running as a scheduled task from server 2012 and has to be run from a 2008 R2 machine) wihch is not a great solution at all :( - Would love a more permanent resolution.

    Here is the script, would love any suggestions to either make it shorter or better as I am still a student of powershell ;).

    # Collects hosts that are "Not Respsonding" in SCVMM and restarts the hosts services that have failed

# Start Logging through transcript
Start-Transcript -Path "D:\Scripts\CheckSCVMMServices\Log.txt" -Force

# Add a human readable date to the log
$Date = Get-date -Format "hh-mm dd-MM-yyyy"
$Date

# Import SCVMM Modules
Import-Module virtualmachinemanagercore,virtualmachinemanager

# Define the Library server
$Library = "MyLibrary"

New-Item -Path "D:\Scripts\CheckSCVMMServices\" -Name $Date.txt -ItemType File

# Ensure the Library / Management server services are up and running first
Write-Host ""
Write-Host ('Checking Services on the Management/Library server '+$Library)

# Logic to see if any commands need to be done on the library/management server
$VMMServices = Get-Service -name WinRM,SCVMMAgent,SCVMMService -ComputerName $Library | Where {$_.Status -eq "Stopped"}
    IF ($VMMServices -eq $Null)
    {
        Write-Host ""
        Write-Host "No Services to start on library server, moving to host check"
    }
    ELSE
    {
        Get-Service -name WinRM,SCVMMAgent,SCVMMService -ComputerName $Library | Start-Service

        Write-Host ""
        Write-Host ('Services on '+$Library+' should now be running')
        Start-Sleep -Seconds 2
    }

# Create the collection of objects (hosts)
$VMHosts = Get-SCVMHost -VMMServer $Library | Where {$_.ComputerState -eq "notresponding"}

# Logice to see if any commands need to be run on the host servers
    IF ($VMHosts -eq $null)
    {
        Write-Host ""
        Write-Host "All hosts are already responding & services are working"
        Start-Sleep -Seconds 2
    }
    ELSE
    {
        Write-Host ""
        Write-Host "Hosts with failed SCVMM Services are...."
        $VMHosts | FT Name
        
        # Loop through the object
        ForEach ($VMHost in $VMHosts)
	    {
		    Get-Service WinRM,SCVMMAgent,VMMS -ComputerName $VMHost | Start-Service
	    }
        Write-Host "Hosts should now be running"
		Start-Sleep -Seconds 2
    }

# Let the user know we are all 
Write-Host ""
Write-Host "This script no longer has any work. Ending"

# Close off the log
Stop-Transcript

     
     
  • Thursday, January 31, 2013 10:32 PM
     
      Has Code
    Sign In to Vote
    0

    Just found this information that may be what I am looking for as we do run SCCM 2012 (non SP1)

    <header style="font-family:'Helvetica Neue', Helvetica, Arial;font-size:17px;line-height:24.640625px;background-color:rgba(255, 255, 255, 0.901961);">

    VMM 2012 SP1 Service Stops Every Night

    </header>

    If you have the System Center Configuration Manager 2012 RTM agent installed on a Windows Server 2012 server also running the System Center Virtual Machine Manager 2012 SP1 agent, you might find the VMM service unexpectedly stops each night. There is nothing obvious in the event logs about why the service stops, but each night the hosts will move to “Not responding” in VMM because the service is not running.

    This is caused by an inventory process in SCCM that causes the VMM agent to stop. You can uninstall the SCCM agent using this command:

    C:\Windows\ccmsetup\ccmsetup.exe /uninstall

     
  • Friday, February 01, 2013 12:44 AM
     
     
    Sign In to Vote
    0

    Just found this information that may be what I am looking for as we do run SCCM 2012 (non SP1)

    SCCM 2012 (pre SP1) is not supported for use with WS2012, if you run unsupported configurations in production you may well get unpleasant results.
     
  • Thursday, February 28, 2013 10:20 PM
     
     
    Sign In to Vote
    0
    Still seeing this problem on a daily basis. Machines will not restart in an RDS config so my pool runs out of machines as the broker can not restart them. I now have a failover cluster setup, seeing the problem on both nodes, but also machines will not migrate between nodes until I have restarted the vmm service. It has lead me here though, and I'll be investigating tomorrow http://social.technet.microsoft.com/Forums/en-US/winserverhyperv/thread/37d354db-76c3-40e2-be28-7dd8b300f09c/ And then here http://support.microsoft.com/kb/2779204
     
  • Tuesday, March 05, 2013 12:38 PM
     
     
    Sign In to Vote
    0

    Looks like this may well be down to NT Virtual Machine\Virtual Machines not having the ability to Log on as a Service

    See this article KB/2779204

    When the VM in the RDS will not restart, check the Log on as a service, NT Virtual Machine\Virtual Machines will be missing.

    Run a gpupdate /force and recheck, NT Virtual Machine\Virtual Machines will now have the right to Log on as a service.

    VMs should then restart with no problems and without having to restart the VMM service