Jump to content


spitfire

Established Members
  • Posts

    19
  • Joined

  • Last visited

Posts posted by spitfire

  1. Hi,

     

    I have a problem with Windows (and Hyper-V) Server 2012 R2 OSD task sequence - the OS fails to boot after the "Install Operating System" group is done, and computer is rebooted - I'm getting error 0xc0000001.

    I've found out that bitlocker is the issue here - if I disable TPM on the machines I've got problem with it runs without any issue. Strange thing is - same TS works for Windows 8.1 Enterprise x64 (only thing I changed for that TS is porduct key, System OU, and of course system image).

     

    post-21469-0-54734800-1422816757_thumb.png

     

    Any ideas why that might be?

    post-21469-0-54734800-1422816757_thumb.png

    post-21469-0-56048600-1422834061_thumb.png

  2. Hi,

     

    I've just set up PKI insfrastructure on my AD/SCCM 2012 R2 server following:

    http://sccmguy.com/2013/11/26/pki-certificates-for-configuration-manager-2012-r2-part-1-of-4-web-server-certificate/

     

    Unfortunately Management Point complains about SMS_NOTIFICATION_SERVER nt being able to read my SSL cert from IIS - here's an excerpt from bgbserver.log found on my SCCM server:

     

    Beginning main thread SMS_NOTIFICATION_SERVER 2014-11-24 21:41:07 4104 (0x1008)
    Register a DB connection... SMS_NOTIFICATION_SERVER 2014-11-24 21:41:16 4156 (0x103C)
    Initializing the status message reporting system... SMS_NOTIFICATION_SERVER 2014-11-24 21:41:16 4156 (0x103C)
    The path to the "Status Manager" inbox is "C:\Program Files\Microsoft Configuration Manager\inboxes\statmgr.box\statmsgs". SMS_NOTIFICATION_SERVER 2014-11-24 21:41:16 4156 (0x103C)
    SMS_STATUS_MANAGER is not running as part of this process, the SMS_EXECUTIVE to SMS_STATUS_MANAGER in-memory status message queue will not be used. SMS_NOTIFICATION_SERVER 2014-11-24 21:41:16 4156 (0x103C)
    Registered this process as a source of "SMS Server" events. SMS_NOTIFICATION_SERVER 2014-11-24 21:41:17 4156 (0x103C)
    Registered this process as a source of "SMS Client" events. SMS_NOTIFICATION_SERVER 2014-11-24 21:41:17 4156 (0x103C)
    Registered this process as a source of "SMS Provider" events. SMS_NOTIFICATION_SERVER 2014-11-24 21:41:17 4156 (0x103C)
    Status message reporting system initialized successfully. SMS_NOTIFICATION_SERVER 2014-11-24 21:41:17 4156 (0x103C)
    BgbServerController COM wrapper object 22687807 is successfully initialized SMS_NOTIFICATION_SERVER 2014-11-24 21:41:17 4156 (0x103C)
    GetMPWebSite: MP is installed under web site <IIS://LocalHost/W3SVC/1> SMS_NOTIFICATION_SERVER 2014-11-24 21:41:17 4104 (0x1008)
    ERROR: GetIISWebServiceBinaryProperty failed (0x800cc801). SMS_NOTIFICATION_SERVER 2014-11-24 21:41:17 4104 (0x1008)
    Error: Failed to get IIS certificate check mode SMS_NOTIFICATION_SERVER 2014-11-24 21:41:17 4104 (0x1008)
    Error: Failed to refresh MP settings. SMS_NOTIFICATION_SERVER 2014-11-24 21:41:17 4104 (0x1008)
    STATMSG: ID=9800 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_NOTIFICATION_SERVER" SYS=CONFIGMGR-P01.mydomain.me SITE=P01 PID=2556 TID=4104 GMTDATE=Pn lis 24 20:41:17.330 2014 ISTR0="CONFIGMGR-P01.mydomain.me" ISTR1="-2146646015" ISTR2="CONFIGMGR-P01.mydomain.me" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_NOTIFICATION_SERVER 2014-11-24 21:41:17 4104 (0x1008)
    Failed to initialize BGB server. Wait 300 seconds to do initialization again SMS_NOTIFICATION_SERVER 2014-11-24 21:41:17 4104 (0x1008)
    Any ideas how to fix it?
  3. Even though http://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_SupConfigClientOS says, that "The Server Core installation of Windows Server 2008 (SP2)" "x86, x64" Even supports installation of cm client for:

    • System Center 2012 Configuration Manager with no service pack
    • System Center 2012 Configuration Manager with SP1

    I have the latter one, but I'm asking: how is it possible? I mean, .NET framework is NOT supported od Windows Server 2008 Core installations, and ccmclient requires .NET 4.0, right? Or am I getting something wrong?

     

    Anyway, I posted logs above, but really have no idea what is the case.

  4. from ccmsetup.log

     

     

    is dns working fine on this computer ? is the schema extended for configmgr in ad ?

     

    Yes I did. I have some Client computers that are working now. I'm also able to deploy Windows 8 and 2012R2 through Task sequence via PXE (and I've tried the same way of deployment with 2008 Core - but it doesn't install client = build &capture doesn't work).

     

     

    EDIT: All my clients get DNS settings from DHCP, and this server boots from PXE = it must be getting correct settings form DHCP.

  5. Hi,

     

    I'm having problems installing SCCM 2012 Client (I have SCCM 2012 SP1 CU3 to be exact) on my Windows 2008 (NOT R2) Server Core Systems (x86). According to http://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_SupConfigClientOS it is supported.I did update it to SP2, but still no luck.

     

    As far as I see (if I understool log correctly) the problem is with missing .NET Framework 2.0. It also seems that in is impossible to install .NET Fremework on Windows Server 2008 (NON-R2) Core installation.

     

    (I've attached logs as .zip, because they were 10MB big).

     

    Can anyone help?

     

    Regards,

    spitfire

    logs.zip

  6. Hi,

     

    I've set up WSUS on WIndows server 2012 on the same system, where most of of my SCCM (2012 SP1 CU2) site roles are residing. Standalone WSUS, offers products such as Windows 8/8.1/2012/2012R2, but when I want to setup Software Update point SCCM role, newest windows products, that are offered are Windows 7/2008R2.

     

    What do I need to fix, to be able to offer Windows 8/2012+ updates to my clients from SUP?

    post-21469-0-95951100-1379277756_thumb.png

×
×
  • Create New...