locked
Secondary Site Issues RRS feed

  • Question

    Secondary Site shows fully installed and operational in the console.

    1. I can not prestage content (Even though console shows DP installed and Prestaged content enabled)   -----  Log states -  Failed to open local registry key software\microsoft\SMS\DP\Identity (80070002) ----- FYI - ...DP\Identity Registry does not exist.
    2. Program files\sms_CCM does not exist (even though console shows MP installed)
    3. Finally, should I be able to open the console for the secondary site, or is all managment of the seconday site through the primary site? (No CAS)

    • Edited by TE2011 Sunday, August 19, 2012 11:19 PM
    Sunday, August 19, 2012 11:19 PM

Answers

    1. I can not prestage content (Even though console shows DP installed and Prestaged content enabled)   -----  Log states -  Failed to open local registry key software\microsoft\SMS\DP\Identity (80070002) ----- FYI - ...DP\Identity Registry does not exist.

    There's a known issue with extractcontent.exe on sites without a DP. It will be fixed with SP1. That might not be applicable in your situation though ;-)

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

    Friday, August 24, 2012 7:16 AM

All replies

  • 1. Which log file? What procedure are you following to pre-stage content?

    2. The MP can be installed in another location. Was the ConfigMgr client agent intalled on the system? If so, then the MP gets installed into the agent's directory.

    3. No. There's nothing to really manage on a secondary site -- think of a secondary as just an extension of the primary.


    Jason | http://blog.configmgrftw.com

    Monday, August 20, 2012 12:27 AM
  • Hi Jason,

    Thanks for the response.

    1.  The log file reference is the PrestagedContent.log on the secondary site.  On the secondary site it put the log in the user\...\appdata\local\temp\1\, when I did this on my functioning DP it put the log in the SMS_DP$\sms\logs directory.  I assume since the sms_DP$ directory does not exist it puts in the appdata directory.  but why doesn't the SMS_DP$ directory exist, the primary site says there is a DP on the secondary.

    The procedure I am using is creating the prestaged content on the primary site, copy the files to the secondary site and running ExtractContent /P:"D:\Prestaged content" /S (is there another?)

    2.  The client is installed on the secodary site.  How can I confirm the MP is installed operational on the secondary site (Reg keys, directory structure, etc)?

    3.  Gotcha.  Thanks I have been racking my brain trying to figure out why I could not connect to the secondary "SITE"  :).

    Thanks again for your assistance.




    • Edited by TE2011 Monday, August 20, 2012 2:39 AM
    Monday, August 20, 2012 2:35 AM
  • Is the DP enabled for pre-staged content?

    For the MP, look in the client install directory (should be c:\windows\ccm) and all of the MP log files will be in the logs directory. It's status is also listed in the console in the Moniroting workspace under site status.


    Jason | http://blog.configmgrftw.com

    Monday, August 20, 2012 5:54 PM
  • Yes, there is a check in the box "Enable this distribution point for prestaged content"

    Monday, August 20, 2012 7:10 PM
  • Update - In the Configuration Manager Console, I removed the distribution point from the secondary site sever.  I gave it a day to ensure the DP had time to be removed.  I then readded the DP (ensuring the "Enable this distribution point for prestaged content" was checked).

    I waited a day to ensure the DP had time to install (even though the console said it was installed I wanted to make sure it was actually installed and not just reporting it was installed).  I then ran the extractcontent again and experienced the same issue.

    Please help.

    Thanks

    Thursday, August 23, 2012 8:18 PM
    1. I can not prestage content (Even though console shows DP installed and Prestaged content enabled)   -----  Log states -  Failed to open local registry key software\microsoft\SMS\DP\Identity (80070002) ----- FYI - ...DP\Identity Registry does not exist.

    There's a known issue with extractcontent.exe on sites without a DP. It will be fixed with SP1. That might not be applicable in your situation though ;-)

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

    Friday, August 24, 2012 7:16 AM
  • Hi,

    Please could you update me ? did you solve this issue? i have the same issue.

    Friday, January 10, 2020 1:04 PM
  • Given that this thread is 7+ years old, you really need to start a new thread and provide actual technical details of what you are experiencing.

    Jason | https://home.configmgrftw.com | @jasonsandys

    Friday, January 10, 2020 3:53 PM