Jump to content


dani3l

Established Members
  • Posts

    19
  • Joined

  • Last visited

Posts posted by dani3l

  1. Hi Guys,

     

    i have another special problem with our OSD Tasksequencens. In my test environment i have 2 Clients (1 physical, 1 virtual) and there in the sccm console (with Client = Yes).

     

    If i try to reinstall the Client, the client get his old name from the sccm but then the client starts a second request and didnt get the old name. Here is the part of the logfile

     

    
    CLibSMSMessageWinHttpTransport::Send: URL: SCCM-SERVER.TE.ST1:80 CCM_POST /ccm_system/request TSMBootstrap 21.06.2012 09:20:11 1268 (0x04F4)
    Request was succesful. TSMBootstrap 21.06.2012 09:20:11 1268 (0x04F4)
    Decompressing reply body. TSMBootstrap 21.06.2012 09:20:11 1268 (0x04F4)
    ::DecompressBuffer(65536) TSMBootstrap 21.06.2012 09:20:11 1268 (0x04F4)
    Decompression (zlib) succeeded: original size 509, uncompressed size 2732. TSMBootstrap 21.06.2012 09:20:11 1268 (0x04F4)
    -60 -60 TSMBootstrap 21.06.2012 09:20:11 1268 (0x04F4)
    Server time zone info: -60, , [0 10 0 5 3 0 0 0], 0, , [0 3 0 5 2 0 0 0], -60 TSMBootstrap 21.06.2012 09:20:11 1268 (0x04F4)
    Client Identity: GUID:5db8d8df-546f-1234-XXXX-41ed589d5e90 TSMBootstrap 21.06.2012 09:20:11 1268 (0x04F4)
    Netbios name: SCCM-TEST2 TSMBootstrap 21.06.2012 09:20:11 1268 (0x04F4)
    Client GUID = GUID:5db8d8df-546f-1234-XXXX-41ed589d5e90, Netbios name = SCCM-TEST2, State = Known TSMBootstrap 21.06.2012 09:20:11 1268 (0x04F4)
    Set media certificate in transport TSMBootstrap 21.06.2012 09:20:11 1268 (0x04F4)
    Set authenticator in transport TSMBootstrap 21.06.2012 09:20:11 1268 (0x04F4)
    CLibSMSMessageWinHttpTransport::Send: URL: SCCM-SERVER.TE.ST1:80 GET /SMS_MP/.sms_aut?MPKEYINFORMATION TSMBootstrap 21.06.2012 09:20:11 1268 (0x04F4)
    Request was succesful. TSMBootstrap 21.06.2012 09:20:11 1268 (0x04F4)
    New settings: TSMBootstrap 21.06.2012 09:20:11 1268 (0x04F4)
    site=ABC,ABC, MP=http://SCCM-SERVER.TE.ST1, ports: http=80,https=443 TSMBootstrap 21.06.2012 09:20:11 1268 (0x04F4)
    certificates are received from MP. TSMBootstrap 21.06.2012 09:20:11 1268 (0x04F4)
    MP specific X86 unknown machine GUID is received at run time TSMBootstrap 21.06.2012 09:20:11 1268 (0x04F4)
    MP specific X64 unknown machine GUID is received at run time TSMBootstrap 21.06.2012 09:20:11 1268 (0x04F4)
    Getting MP time information TSMBootstrap 21.06.2012 09:20:11 1268 (0x04F4)
    Set authenticator in transport TSMBootstrap 21.06.2012 09:20:11 1268 (0x04F4)
    Requesting client identity TSMBootstrap 21.06.2012 09:20:11 1268 (0x04F4)
    Setting message signatures. TSMBootstrap 21.06.2012 09:20:11 1268 (0x04F4)
    Setting the authenticator. TSMBootstrap 21.06.2012 09:20:11 1268 (0x04F4)
    CLibSMSMessageWinHttpTransport::Send: URL: SCCM-SERVER.TE.ST1:80 CCM_POST /ccm_system/request TSMBootstrap 21.06.2012 09:20:11 1268 (0x04F4)
    Request was succesful. TSMBootstrap 21.06.2012 09:20:11 1268 (0x04F4)
    Decompressing reply body. TSMBootstrap 21.06.2012 09:20:11 1268 (0x04F4)
    ::DecompressBuffer(65536) TSMBootstrap 21.06.2012 09:20:11 1268 (0x04F4)
    Decompression (zlib) succeeded: original size 418, uncompressed size 2500. TSMBootstrap 21.06.2012 09:20:11 1268 (0x04F4)
    -60 -60 TSMBootstrap 21.06.2012 09:20:11 1268 (0x04F4)
    Server time zone info: -60, , [0 10 0 5 3 0 0 0], 0, , [0 3 0 5 2 0 0 0], -60 TSMBootstrap 21.06.2012 09:20:11 1268 (0x04F4)
    Client Identity: TSMBootstrap 21.06.2012 09:20:11 1268 (0x04F4)
    Netbios name: TSMBootstrap 21.06.2012 09:20:11 1268 (0x04F4)
    Current time: 2012-06-21 08:20:11.843 TZ:Mitteleuropäische Zeit Bias:-060 TSMBootstrap 21.06.2012 09:20:11 1268 (0x04F4)
    
    

     

    Have someone a idea or a hint?

     

    Regards,

    dani3l

  2. This logs says nothing, but last friday i found an error message on the server, which says that the sccm cant connect to the machine wmi.

    I checked this and i only connect to the machine wmi with the hostname and not with the ip adresse. I removed the SCCM Client from the Tasksequence and installed the machine againagaint... and then i can connect to the machine wmi with the ip. I think this isn't normal because when i install the sccm after the task sequence, it works fine and the client appears in the sccm console.

     

    Have someone a solution for this problem?

  3. Hi,

     

    i have installed the SCCM Client to our test machines (with the sccm console) and the installation works fine (ccmsetup.log shows no error). But i got the problem that the sccm console says that von this machine the sccm client isnt installed (waited about 12 Hours) and i dont know why. In Addition the problem appears too when i install the sccm client with a osd tasksequence.

     

    In both cases the SCCM Client is installed on the machine, but i only have 2 actions availabe (machine & user policy retrieval...) and i have no idea why this happend. Have someone an idea?

     

    Regards,

    dani3l

  4. Hi everyone,

     

    i try the sccm 2012 rc and have a problem with the software updates. I have selected do discover (i hope its the right word) new updates for office 2007/2012 and windows 7 and in the end i only want to have updates for office 2010 and windows 7. So i tryed to delete the office 2007 updates but there is no delete button in the sccm console. I found the updates in WIM under Root\SMS\site_XXX -> SMS_SoftwareUpdate but i dont know how i can delete them. Have you a idea?

     

    Regards,

    dani3l

  5. I had the same Problem with a script and i solve it by changeing the tasksequencve like this.

     

    Before the change: OSD Step -> Conifg Mgr Client -> Script with Domain Acc

    With the solution: OSD Step -> Restart -> Config Mgr Client -> Script with Domain Acc

     

    The Restart Step solved the problem for me... maybe this helps you ;)

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.