locked
Use same captured image on 2 different servers, MP should change. RRS feed

  • Question

  • Hi,

    We have a 2nd SCCM UAT server on which we use the same captured image (in which an SCCM client is included with MP etc). We deploy this on the UAT and DO change during this install the MP (in step "Setup Windows and ConfigMgr") but the MP stays targetted to the original MP (in the capture).
    How can we force this in a correct way during a task sequence (change regkey?), repair of client?

    J.


    Jan Hoedt

    Thursday, May 7, 2015 8:49 AM

Answers

All replies

  • but the MP stays targetted to the original MP (in the capture).


    Where? How did you determine that?

    Torsten Meringer | http://www.mssccmfaq.de

    Thursday, May 7, 2015 9:13 AM
  • When we deploy an OS with the different/UAT SCCM-server and we look in the client, the sitecode is the one of the production sccm server, not the UAT one.

    Jan Hoedt

    Thursday, May 7, 2015 9:15 AM
  • That should not happen. Examine ccmsetup.log.

    Torsten Meringer | http://www.mssccmfaq.de

    • Proposed as answer by Joyce L Wednesday, May 20, 2015 8:36 AM
    • Marked as answer by Joyce L Friday, May 22, 2015 2:45 AM
    Thursday, May 7, 2015 9:37 AM
  • Queried the log, you are right:

    In the beginning of the log I can see indeed the old config of our main server is there:

    Lookup MP:    ourmainsccmserver.domain.com    ccmsetup    24/04/2015 9:48:11    684 (0x02AC)
    FSP:    ourmainsccmserver.domain.com    ccmsetup    24/04/2015 9:48:11    684 (0x02AC)
    CCMFIRSTCERT:    1    ccmsetup    24/04/2015 9:48:11    684 (0x02AC)
    Config file:      C:\Windows\ccmsetup\MobileClientUnicode.tcf    ccmsetup    24/04/2015 9:48:12    684 (0x02AC)
    Retry time:       10 minute(s)    ccmsetup    24/04/2015 9:48:12    684 (0x02AC)
    MSI log file:     C:\Windows\ccmsetup\Logs\client.msi.log    ccmsetup    24/04/2015 9:48:12    684 (0x02AC)
    MSI properties:    INSTALL="ALL SMSMP="ourmainsccmserver.domain.com" FSP="ourmainsccmserver.domain.com" SMSPROVISIONINGMODE="1" SMSSITECODE="FLS" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="224" SMSSLP="ourmainsccmserver.domain.com" CCMFIRSTCERT="1"    ccmsetup    24/04/2015 9:48:12    684 (0x02AC)
    Source List:    ccmsetup    24/04/2015 9:48:12    684 (0x02AC)
                      C:\_SMSTaskSequence\OSD\PRD00075    ccmsetup    24/04/2015 9:48:12    684 (0x02AC)


    Then it tries to install the new config (UAT) but fails and does a rollback, probably due to the fact it doen't find the MP, but why(?):


    Couldn't determine site version for site 'UAT'. Let client deployment continue.    ccmsetup    7/05/2015 11:59:48    1884 (0x075C)
    Failed to load mdmregistration.dll with error 0x8007007e    ccmsetup    7/05/2015 11:59:48    1884 (0x075C)
    Failed to load mdmregistration.dll. Continue deployment.    ccmsetup    7/05/2015 11:59:48    1884 (0x075C)
    C:\Windows\ccmsetup\SCEPInstall.exe is Microsoft trusted.    ccmsetup    7/05/2015 11:59:48    1884 (0x075C)
    An MP does not exist on this machine.    ccmsetup    7/05/2015 11:59:49    1884 (0x075C)
    Running installation package
      Package:     C:\Windows\ccmsetup\{181D79D7-1115-4D96-8E9B-5833DF92FBB4}\client.msi
      Log:         C:\Windows\ccmsetup\Logs\client.msi.log
      Properties:   REINSTALL=ALL REINSTALLMODE=vmous  INSTALL="ALL" SMSCACHESIZE="8000" SMSMP="ouruatsccmserver.domain.com" FSP="ouruatsccmserver.domain.com" CCMLOGMAXSIZE="104857600" SMSPROVISIONINGMODE="1" SMSSITECODE="FLK" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="224" SMSSLP="ourmainsccmserver.domain.com" CCMFIRSTCERT="1" SMSPUBLICROOTKEY=0602000000A4000052126485734131000804580001000100F1A5B0413BD149F0312A83C446C91393A4D5C99987A8CA44ADE84119B0A9379D05166A872ABA0F45753A0C902EB6DFD2E5DA50CFE5157A4C715F40A3F1DAFEA61770A7890DB330F995BB24AF438A76770B28A5A5C57C0A8A79FB1F922D4909B874E53D670ADBA5E026F7DD2896A33FB2F984F30DAD1D2B8E467262E5EB2B1C2007C8ED7855C6D72E83547E5AEB2D8CF83E73371C8374B720DE226FA1A0C21198DF60389690D6C21171496392B89538E6B33D81E252609E830A330F01E27F4AE2D6F35A471D49A52C4F65E9E9064A72A1818805E4BF2E9041401B308C4649B626453162A280EDFBDE07AEE063D385C254D055CE0BF1A21F6CA42732EDA43C15CAD    ccmsetup    7/05/2015 11:59:49    1884 (0x075C)
    MSI: Action 11:59:59: CcmTypelibRollback. In the event of install failing, this event rolls back the type libraries to the state before install started.    ccmsetup    7/05/2015 11:59:59    1884 (0x075C)

    Jan Hoedt



    • Edited by janhoedt Thursday, May 7, 2015 2:24 PM UPdate
    Thursday, May 7, 2015 2:22 PM
  • Please advise on this.

    Jan Hoedt

    Tuesday, May 12, 2015 9:03 AM
  • Examine the log, find the cause of the failure and fix it. That snippet above cannot be used to tell what went wrong. 

    Torsten Meringer | http://www.mssccmfaq.de

    • Proposed as answer by Joyce L Wednesday, May 20, 2015 8:35 AM
    Tuesday, May 12, 2015 9:13 AM