Missing Service Principal Name WSMAN? Do I need to worry for a hyper-v host which is running some mobile messaging VM's.

    일반 토론

  • Missing Service Principal Name WSMAN?  Both the netbios and fqdn versions of WSMAN are missing on the hyper-v host.  All other SPN's are available for this hyper-v host object in ADSI.

    Do I need to worry for a hyper-v host which is running some mobile messaging VM's.

    We have removed this hyper-v host from the domain and readded it.   I have also done an addportrange.vbs and this runs--error  Line 43 character 1 shows error that that that there are no more ports are available for endpoint mapper. (code: 8000706D9  source: null)   I believe this error means that there are no more ports to add for this mapping-all available ports are available.   The "self" entry for the server object has the correct "write" permission to create SPN's.  In fact all otherSPN's are in AD except WSMAN. This server is also patched with all available windows updates.  Other hyper-v host added to the domain have all SPN's visible in ADSI.  The below event occurs whenever the hyper-v host is rebooted.

    Log Name: Microsoft-Windows-Hyper-V-VMMS-Admin

    Source: Microsoft-Windows-Hyper-V-VMMS

    Date: 7/24/2013 12:19:20 PM

    Event ID: 14050

    Task Category: None

    Level: Error


    User: SYSTEM



    Failed to register service principal name.

    Event Xml:

    <Event xmlns="">


    <Provider Name="Microsoft-Windows-Hyper-V-VMMS" Guid="{6066F867-7CA1-4418-85FD-36E3F9C0600C}" />







    <TimeCreated SystemTime="2013-07-24T16:19:20.538494900Z" />


    <Correlation />

    <Execution ProcessID="1740" ThreadID="2416" />



    <Security UserID="S-1-5-18" />



    <VmlEventLog xmlns:auto-ns2="" xmlns="">





    2013년 7월 24일 수요일 오후 9:35

모든 응답