locked
SCCM 2012 cannot deploy client on HyperV server RRS feed

  • Question

  • Hi all,

    I cannot install SCCM2012 clients on my HyperV servers. After pushing installation I see that ccmsetup service is created and started in ccm.log.

    In Configuration Manager Console I see these servers with client type "none". Site code is proper.

    When I connected to HyperV services I see ccmsetup in stopping state. In eventviewer of HyperV servers there are no errors or warnings.

    Clients on all other servers are deployed normally. All servers including HyperV servers are in the same OU in AD with same AD policies. SCCM 2012 version is 5.0.7711.0.

    What can cause this problem with deploying on Hyper V servers?



    Thursday, May 17, 2012 1:44 PM

Answers

  • The release notes say that Server core R2 (no SP) is not supported for .Net 4 and the web says that Server Core R2 SP1 is supported.  That seems to indicate that support was added later to SP1 of R2 after the .Net 4 release notes. 

    However it looks like installing 3.5 will do the trick according to this so .Net 4 support is not needed in your case.

    http://technet.microsoft.com/en-us/library/gg682042.aspx

    Microsoft .NET Framework 4 Client Profile

    Client computers require the .NET Framework to support client operations. If a client computer does not have one of the following supported versions, the Microsoft .NET Framework 4 Client Profile is installed automatically:

    • Microsoft .NET Framework version 3.0.
    • Microsoft .NET Framework version 3.5.
    • Microsoft .NET Framework version 4.0.


    Stan

    Thursday, May 17, 2012 4:32 PM

All replies

  • Hi,

    I have never had any problems with installing the sccm client on a hyper-v server. If you look in C:\windows\ccmsetup\ccmsetup.log file, you can see the reason why it fails to install.
    that is where I would start.

    Regards,
    Jörgen


    -- My System Center blog ccmexec.com -- Twitter @ccmexec

    Thursday, May 17, 2012 1:50 PM
  • Thanks for quick reply. I see following errors in ccmsetup.log:

    <![LOG[Installing file 'C:\Windows\ccmsetup\dotNetFx40_Client_x86_x64.exe' with options '/q /norestart /log dotNetFx4_Client_Setup.log'.]LOG]!><time="17:51:47.435-240" date="05-17-2012" component="ccmsetup" context="" type="1" thread="5192" file="manifest.cpp:1923">
    <![LOG[File 'C:\Windows\ccmsetup\dotNetFx40_Client_x86_x64.exe' returned failure exit code 5100. Fail the installation.]LOG]!><time="17:52:00.992-240" date="05-17-2012" component="ccmsetup" context="" type="3" thread="5192" file="manifest.cpp:1972">

    Regarding following article server does not meet system requirements:

    http://msdn.microsoft.com/en-us/library/ee942965.aspx


    Thursday, May 17, 2012 1:57 PM
  • Strange thing. Windows Server 2008R2 server core with SP1 is supported for .Net4 as I see from following article: http://msdn.microsoft.com/en-us/library/ee390831

    When I run dotNetFx40_Client_x86_x64.exe manually it says that OS is "6.1.7601, Platform 2, Service Pack 1" and  it's unsupported and sends me to http://go.microsoft.com/fwlink/?LinkId=164156. In that document I see that .Net4 not supported on Server Core Role.

    Who is lying? :-)

    Thursday, May 17, 2012 3:08 PM
  • The release notes say that Server core R2 (no SP) is not supported for .Net 4 and the web says that Server Core R2 SP1 is supported.  That seems to indicate that support was added later to SP1 of R2 after the .Net 4 release notes. 

    However it looks like installing 3.5 will do the trick according to this so .Net 4 support is not needed in your case.

    http://technet.microsoft.com/en-us/library/gg682042.aspx

    Microsoft .NET Framework 4 Client Profile

    Client computers require the .NET Framework to support client operations. If a client computer does not have one of the following supported versions, the Microsoft .NET Framework 4 Client Profile is installed automatically:

    • Microsoft .NET Framework version 3.0.
    • Microsoft .NET Framework version 3.5.
    • Microsoft .NET Framework version 4.0.


    Stan

    Thursday, May 17, 2012 4:32 PM
  • Many thanks, that did the trick!

    I've allready had  NetFx2-ServerCore feature enabled, so I enable features for x32/x64 .Net3.5 support:

    Start /w ocsetup NetFx3-ServerCore
    Start /w ocsetup ServerCore-WOW64
    Start /w ocsetup NetFx2-ServerCore-WOW64
    Start /w ocsetup NetFx3-ServerCore-WOW64

    Clients are deployed successfully.

    Friday, May 18, 2012 5:30 AM
  • Just FYI

    I had the same problem and installed the .NET Framework Version 4.0 for Server Core (http://www.microsoft.com/en-us/download/details.aspx?id=22833). Using that version did it aswell.

    Ralf

    Sunday, August 5, 2012 2:29 PM