none
SCCM neue secondary site puplic key probleme RRS feed

 > 

  • Frage

  • Question
    Anmelden
    0
    Anmelden

    Hi, vielleicht kann mir einer von euch helfen. Ich habe einen Distribution Point neu installiert. (Aus SCCM deleted, OS neu installiert und SCCM wieder drauf installiert), weil wenn ich immer einen PXE servive Point dort installiert habe, die Svhost.exe mit 100 % Auslastung gelaufen ist. Die Installation ist gelaufen, jedoch steht die Site seit Tagen auf Pending. Bei der durchsicht der Logfiles ist mir aufgefallen dass noch das alte pkc file des Distribution Points ist und ich bekomme folgende Fehler im Logfile.

    ~Waiting for ready instruction file.... $$<SMS_DESPOOLER><Fri Oct 01 17:15:21.129 2010 W. Europe Daylight Time><thread=384 (0x180)>
~Verifying signature for instruction D:\SMS\inboxes\despoolr.box\receive\ds_71gpd.ist of type MICROSOFT|SMS|MINIJOBINSTRUCTION|REPORTING $$<SMS_DESPOOLER><Fri Oct 01 17:15:21.129 2010 W. Europe Daylight Time><thread=16864 (0x41E0)>
CPublicKeyLookup::CPublicKeyLookup("YOR")~ $$<SMS_DESPOOLER><Fri Oct 01 17:15:21.129 2010 W. Europe Daylight Time><thread=16864 (0x41E0)>
CPublicKeyLookup::CPublicKeyLookup("YOR") Initializing to file: D:\SMS\inboxes\hman.box\pubkey\YOR.pkc~ $$<SMS_DESPOOLER><Fri Oct 01 17:15:21.129 2010 W. Europe Daylight Time><thread=16864 (0x41E0)>
CPublicKeyLookup::GetNextKey() Getting Iteration: 2~ $$<SMS_DESPOOLER><Fri Oct 01 17:15:21.144 2010 W. Europe Daylight Time><thread=16864 (0x41E0)>
CPublicKeyLookup::GetNextKey() Checking D:\SMS\inboxes\hman.box\pubkey\YOR.pkc for Key0~ $$<SMS_DESPOOLER><Fri Oct 01 17:15:21.144 2010 W. Europe Daylight Time><thread=16864 (0x41E0)>
CPublicKeyLookup::GetNextKey() Found Key: 0602000000A40000525341310004000001000100D37B863C612F67DEDAF591405DFB6E8483E944B8F45E578D89F735E48C1B6F22D6D58574CFC108C6170C9A114A28C240BCCA8411A9E744D354310F9B8449C64AD381800549B35FC0F197D67FB1E1A6E4AF84AFEAABC4097DA4B53C28D6EA0DE620866A4F65EE6549385B8C27D65B5A4F8E6C0F701E5828D93EDD04574F94DACE $$<SMS_DESPOOLER><Fri Oct 01 17:15:21.160 2010 W. Europe Daylight Time><thread=16864 (0x41E0)>
~Begin to calculate signature on D:\SMS\inboxes\despoolr.box\receive\ds_71gpd.pkg using hash algorithm ID 0x800C $$<SMS_DESPOOLER><Fri Oct 01 17:15:21.160 2010 W. Europe Daylight Time><thread=16864 (0x41E0)>
~Cannot use public key 0602000000A40000525341310004000001000100D37B863C612F67DEDAF591405DFB6E8483E944B8F45E578D89F735E48C1B6F22D6D58574CFC108C6170C9A114A28C240BCCA8411A9E744D354310F9B8449C64AD381800549B35FC0F197D67FB1E1A6E4AF84AFEAABC4097DA4B53C28D6EA0DE620866A4F65EE6549385B8C27D65B5A4F8E6C0F701E5828D93EDD04574F94DACE to verify package signature from site YOR (Win32 error = 2148073478) $$<SMS_DESPOOLER><Fri Oct 01 17:15:21.160 2010 W. Europe Daylight Time><thread=16864 (0x41E0)>
CPublicKeyLookup::GetNextKey() Getting Iteration: 3~ $$<SMS_DESPOOLER><Fri Oct 01 17:15:21.160 2010 W. Europe Daylight Time><thread=16864 (0x41E0)>
CPublicKeyLookup::GetNextKey() Checking D:\SMS\inboxes\hman.box\pubkey\YOR.pkc for Key1~ $$<SMS_DESPOOLER><Fri Oct 01 17:15:21.160 2010 W. Europe Daylight Time><thread=16864 (0x41E0)>
CPublicKeyLookup::GetNextKey() Found Key: 0602000000A40000525341310004000001000100452006ADFDFECEC7B5E3DBBCA3033DEFFC749B011039945B395619BB38250F656DCB200958BBF1E687BA866ED5D661AA65BEC8DA2991BDB356AD0364BF5B3F9B8D5B1449A17047187E8C2ACBB597EA8EC6C337350E7795E610F5477E53FEA8C9499EC9D7070BF787C5E791885951480B9A90312C8AE5F71A5886E983B0FC5190 $$<SMS_DESPOOLER><Fri Oct 01 17:15:21.160 2010 W. Europe Daylight Time><thread=16864 (0x41E0)>
~Cannot use public key 0602000000A40000525341310004000001000100452006ADFDFECEC7B5E3DBBCA3033DEFFC749B011039945B395619BB38250F656DCB200958BBF1E687BA866ED5D661AA65BEC8DA2991BDB356AD0364BF5B3F9B8D5B1449A17047187E8C2ACBB597EA8EC6C337350E7795E610F5477E53FEA8C9499EC9D7070BF787C5E791885951480B9A90312C8AE5F71A5886E983B0FC5190 to verify package signature from site YOR (Win32 error = 2148073478) $$<SMS_DESPOOLER><Fri Oct 01 17:15:21.160 2010 W. Europe Daylight Time><thread=16864 (0x41E0)>
CPublicKeyLookup::GetNextKey() Getting Iteration: 4~ $$<SMS_DESPOOLER><Fri Oct 01 17:15:21.160 2010 W. Europe Daylight Time><thread=16864 (0x41E0)>
CPublicKeyLookup::GetNextKey() Checking D:\SMS\inboxes\hman.box\pubkey\YOR.pkc for Key2~ $$<SMS_DESPOOLER><Fri Oct 01 17:15:21.160 2010 W. Europe Daylight Time><thread=16864 (0x41E0)>
CPublicKeyLookup::GetNextKey() Found Key:  $$<SMS_DESPOOLER><Fri Oct 01 17:15:21.160 2010 W. Europe Daylight Time><thread=16864 (0x41E0)>
~Cannot use public key 0602000000A40000525341310004000001000100D37B863C612F67DEDAF591405DFB6E8483E944B8F45E578D89F735E48C1B6F22D6D58574CFC108C6170C9A114A28C240BCCA8411A9E744D354310F9B8449C64AD381800549B35FC0F197D67FB1E1A6E4AF84AFEAABC4097DA4B53C28D6EA0DE620866A4F65EE6549385B8C27D65B5A4F8E6C0F701E5828D93EDD04574F94DACE to verify package signature from site YOR (Win32 error = 2148073478) $$<SMS_DESPOOLER><Fri Oct 01 17:15:21.191 2010 W. Europe Daylight Time><thread=16864 (0x41E0)>
CPublicKeyLookup::GetNextKey() Getting Iteration: 9999~ $$<SMS_DESPOOLER><Fri Oct 01 17:15:21.191 2010 W. Europe Daylight Time><thread=16864 (0x41E0)>
CPublicKeyLookup::CPublicKeyLookup("YOR")~ $$<SMS_DESPOOLER><Fri Oct 01 17:15:21.191 2010 W. Europe Daylight Time><thread=16864 (0x41E0)>
~Delete the instruction (D:\SMS\inboxes\despoolr.box\receive\ds_71gpd.ist) from site YOR, the signature is bad. $$<SMS_DESPOOLER><Fri Oct 01 17:15:21.191 2010 W. Europe Daylight Time><thread=16864 (0x41E0)>
STATMSG: ID=4406 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DESPOOLER" SYS=DEEDCMFS01 SITE=TDE PID=3464 TID=16864 GMTDATE=Fri Oct 01 15:15:21.191 2010 ISTR0="YOR" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 $$<SMS_DESPOOLER><Fri Oct 01 17:15:21.191 2010 W. Europe Daylight Time><thread=16864 (0x41E0)>

     

    Daraufhin habe ich nach folgender Anleiung die Zertifikate ausgetauscht

    To manually transfer the child site public key to the parent site 

1. While logged on to the child site, open a command prompt and navigate to the location of Preinst.exe. 

2. Run the following command to export the child site’s public key: Preinst /keyforparent 

3. The Preinst /keyforparent command places the public key of the child site in the <site code>.CT4 file located at the root of the system drive. 

4. Move the <site code>.CT4 file to the parent site’s <install directory>\inboxes\hman.box directory. 

To manually transfer the parent site public key to the child site 

1. While logged on to the parent site, open a command prompt and navigate to the location of Preinst.exe. 

2. Run the following command to export the parent site’s public key: Preinst /keyforchild. 

3. The Preinst /keyforchild command places the public key of the parent site in the <site code>.CT5 file located at the root of the system drive. 

4. Move the <site code>.CT5 file to the <install directory>\inboxes\hman.box directory on the child site. 

However I found this procedure to work in my setup (see inverted child<->parent wording in point 4): 

To manually transfer the child site public key to the parent site 

1.While logged on to the child site, open a command prompt and navigate to the location of Preinst.exe. 
2.Run the following command to export the child site’s public key: Preinst /keyforparent 
3.The Preinst /keyforparent command places the public key of the child site in the <site code>.CT4 file located at the root of the system drive. 
4.Move the <site code>.CT4 file to this child site’s <install directory>\inboxes\hman.box directory.
To manually transfer the parent site public key to the child site 

1.While logged on to the parent site, open a command prompt and navigate to the location of Preinst.exe. 
2.Run the following command to export the parent site’s public key: Preinst /keyforchild. 
3.The Preinst /keyforchild command places the public key of the parent site in the <site code>.CT5 file located at the root of the system drive. 
4.Move the <site code>.CT5 file to this parent site’s <install directory>\inboxes\hman.box directory.

    Leider hat das nicht funktioniert, die Fehlermeldung bleibt. Was mich aber wundert, die cert Dateien auf dem primary sind keine CT4 dateien sondern pkc. Umbenennen half jedoch dabei nicht.

    Hat einer von euch eine Idee, wie ich das Problem lösen könnte?

    Gruß

    newibo

     

     

    Freitag, 1. Oktober 2010 16:32
    |

Alle Antworten

  • Question
    Anmelden
    0
    Anmelden
    Ich habe einen Distribution Point neu installiert ... Die Installation ist gelaufen, jedoch steht die Site seit Tagen auf Pending.
    Also was wurde neu installiert? Einen DP oder die gesamte Site? Was steht/stand denn im hman.log zum Zeitpunkt des manuellen Austausches der Keys laut oben stehender Anleitung?
    Montag, 4. Oktober 2010 06:41
    |
    Beantworter
  • Question
    Anmelden
    0
    Anmelden

    Hi Torsten,

    es geht um eine secondary site.

    hier die log

    SMS-Site-YOR successfully updated.~ $$<SMS_HIERARCHY_MANAGER><Mon Oct 04 05:00:53.567 2010 W. Europe Daylight Time><thread=2576 (0xA10)>
  Time to verify that the public key of current site server in the site control file is still valid. $$<SMS_HIERARCHY_MANAGER><Mon Oct 04 05:00:53.567 2010 W. Europe Daylight Time><thread=2576 (0xA10)>
~Wait for site control changes for maximum 3600 seconds... $$<SMS_HIERARCHY_MANAGER><Mon Oct 04 05:00:53.587 2010 W. Europe Daylight Time><thread=2576 (0xA10)>
Active Directory DS Root:DC=emea,DC=worldwide,DC=com~ $$<SMS_HIERARCHY_MANAGER><Mon Oct 04 06:00:59.335 2010 W. Europe Daylight Time><thread=2576 (0xA10)>
Searching for the System Management Container.~ $$<SMS_HIERARCHY_MANAGER><Mon Oct 04 06:00:59.355 2010 W. Europe Daylight Time><thread=2576 (0xA10)>
System Management container exists.~ $$<SMS_HIERARCHY_MANAGER><Mon Oct 04 06:00:59.365 2010 W. Europe Daylight Time><thread=2576 (0xA10)>
  Searching for SMS-Site-YOR Site Object.~ $$<SMS_HIERARCHY_MANAGER><Mon Oct 04 06:00:59.365 2010 W. Europe Daylight Time><thread=2576 (0xA10)>
  SMS-Site-YOR exists, updating.~ $$<SMS_HIERARCHY_MANAGER><Mon Oct 04 06:00:59.365 2010 W. Europe Daylight Time><thread=2576 (0xA10)>
SMS-Site-YOR successfully updated.~ $$<SMS_HIERARCHY_MANAGER><Mon Oct 04 06:00:59.395 2010 W. Europe Daylight Time><thread=2576 (0xA10)>
  Time to verify that the public key of current site server in the site control file is still valid. $$<SMS_HIERARCHY_MANAGER><Mon Oct 04 06:00:59.405 2010 W. Europe Daylight Time><thread=2576 (0xA10)>
~Wait for site control changes for maximum 3600 seconds... $$<SMS_HIERARCHY_MANAGER><Mon Oct 04 06:00:59.405 2010 W. Europe Daylight Time><thread=2576 (0xA10)>
Active Directory DS Root:DC=emea,DC=worldwide,DC=com~ $$<SMS_HIERARCHY_MANAGER><Mon Oct 04 07:01:05.223 2010 W. Europe Daylight Time><thread=2576 (0xA10)>
Searching for the System Management Container.~ $$<SMS_HIERARCHY_MANAGER><Mon Oct 04 07:01:05.253 2010 W. Europe Daylight Time><thread=2576 (0xA10)>
System Management container exists.~ $$<SMS_HIERARCHY_MANAGER><Mon Oct 04 07:01:05.253 2010 W. Europe Daylight Time><thread=2576 (0xA10)>
  Searching for SMS-Site-YOR Site Object.~ $$<SMS_HIERARCHY_MANAGER><Mon Oct 04 07:01:05.253 2010 W. Europe Daylight Time><thread=2576 (0xA10)>
  SMS-Site-YOR exists, updating.~ $$<SMS_HIERARCHY_MANAGER><Mon Oct 04 07:01:05.263 2010 W. Europe Daylight Time><thread=2576 (0xA10)>
SMS-Site-YOR successfully updated.~ $$<SMS_HIERARCHY_MANAGER><Mon Oct 04 07:01:05.284 2010 W. Europe Daylight Time><thread=2576 (0xA10)>
  Time to verify that the public key of current site server in the site control file is still valid. $$<SMS_HIERARCHY_MANAGER><Mon Oct 04 07:01:05.284 2010 W. Europe Daylight Time><thread=2576 (0xA10)>
~Wait for site control changes for maximum 3600 seconds... $$<SMS_HIERARCHY_MANAGER><Mon Oct 04 07:01:05.294 2010 W. Europe Daylight Time><thread=2576 (0xA10)>
Active Directory DS Root:DC=emea,DC=worldwide,DC=com~ $$<SMS_HIERARCHY_MANAGER><Mon Oct 04 08:01:11.052 2010 W. Europe Daylight Time><thread=2576 (0xA10)>
Searching for the System Management Container.~ $$<SMS_HIERARCHY_MANAGER><Mon Oct 04 08:01:11.092 2010 W. Europe Daylight Time><thread=2576 (0xA10)>
System Management container exists.~ $$<SMS_HIERARCHY_MANAGER><Mon Oct 04 08:01:11.102 2010 W. Europe Daylight Time><thread=2576 (0xA10)>
  Searching for SMS-Site-YOR Site Object.~ $$<SMS_HIERARCHY_MANAGER><Mon Oct 04 08:01:11.102 2010 W. Europe Daylight Time><thread=2576 (0xA10)>
  SMS-Site-YOR exists, updating.~ $$<SMS_HIERARCHY_MANAGER><Mon Oct 04 08:01:11.102 2010 W. Europe Daylight Time><thread=2576 (0xA10)>
SMS-Site-YOR successfully updated.~ $$<SMS_HIERARCHY_MANAGER><Mon Oct 04 08:01:11.122 2010 W. Europe Daylight Time><thread=2576 (0xA10)>
  Time to verify that the public key of current site server in the site control file is still valid. $$<SMS_HIERARCHY_MANAGER><Mon Oct 04 08:01:11.122 2010 W. Europe Daylight Time><thread=2576 (0xA10)>
~Wait for site control changes for maximum 3600 seconds... $$<SMS_HIERARCHY_MANAGER><Mon Oct 04 08:01:11.142 2010 W. Europe Daylight Time><thread=2576 (0xA10)>
Active Directory DS Root:DC=emea,DC=worldwide,DC=com~ $$<SMS_HIERARCHY_MANAGER><Mon Oct 04 09:01:16.950 2010 W. Europe Daylight Time><thread=2576 (0xA10)>
Searching for the System Management Container.~ $$<SMS_HIERARCHY_MANAGER><Mon Oct 04 09:01:16.980 2010 W. Europe Daylight Time><thread=2576 (0xA10)>
System Management container exists.~ $$<SMS_HIERARCHY_MANAGER><Mon Oct 04 09:01:16.980 2010 W. Europe Daylight Time><thread=2576 (0xA10)>
  Searching for SMS-Site-YOR Site Object.~ $$<SMS_HIERARCHY_MANAGER><Mon Oct 04 09:01:16.990 2010 W. Europe Daylight Time><thread=2576 (0xA10)>
  SMS-Site-YOR exists, updating.~ $$<SMS_HIERARCHY_MANAGER><Mon Oct 04 09:01:17.000 2010 W. Europe Daylight Time><thread=2576 (0xA10)>
SMS-Site-YOR successfully updated.~ $$<SMS_HIERARCHY_MANAGER><Mon Oct 04 09:01:17.020 2010 W. Europe Daylight Time><thread=2576 (0xA10)>
  Time to verify that the public key of current site server in the site control file is still valid. $$<SMS_HIERARCHY_MANAGER><Mon Oct 04 09:01:17.020 2010 W. Europe Daylight Time><thread=2576 (0xA10)>
~Wait for site control changes for maximum 3600 seconds... $$<SMS_HIERARCHY_MANAGER><Mon Oct 04 09:01:17.040 2010 W. Europe Daylight Time><thread=2576 (0xA10)>
Active Directory DS Root:DC=emea,DC=worldwide,DC=com~ $$<SMS_HIERARCHY_MANAGER><Mon Oct 04 10:01:23.049 2010 W. Europe Daylight Time><thread=2576 (0xA10)>
Searching for the System Management Container.~ $$<SMS_HIERARCHY_MANAGER><Mon Oct 04 10:01:23.079 2010 W. Europe Daylight Time><thread=2576 (0xA10)>
System Management container exists.~ $$<SMS_HIERARCHY_MANAGER><Mon Oct 04 10:01:23.079 2010 W. Europe Daylight Time><thread=2576 (0xA10)>
  Searching for SMS-Site-YOR Site Object.~ $$<SMS_HIERARCHY_MANAGER><Mon Oct 04 10:01:23.099 2010 W. Europe Daylight Time><thread=2576 (0xA10)>
  SMS-Site-YOR exists, updating.~ $$<SMS_HIERARCHY_MANAGER><Mon Oct 04 10:01:23.109 2010 W. Europe Daylight Time><thread=2576 (0xA10)>
SMS-Site-YOR successfully updated.~ $$<SMS_HIERARCHY_MANAGER><Mon Oct 04 10:01:23.149 2010 W. Europe Daylight Time><thread=2576 (0xA10)>
  Time to verify that the public key of current site server in the site control file is still valid. $$<SMS_HIERARCHY_MANAGER><Mon Oct 04 10:01:23.159 2010 W. Europe Daylight Time><thread=2576 (0xA10)>
~Wait for site control changes for maximum 3600 seconds... $$<SMS_HIERARCHY_MANAGER><Mon Oct 04 10:01:23.199 2010 W. Europe Daylight Time><thread=2576 (0xA10)>
    Montag, 4. Oktober 2010 11:58
    |
  • Question
    Anmelden
    0
    Anmelden
    hman.log zum Zeitpunkt des manuellen Austausches der Keys
    Du hast doch sicher nicht heute früh um 05:00 die Keys exportiert/kopiert/importiert (außerdem ist die Frage ja schon von Freitag).
    Außerdem sollte man im Falle eine Neuinstallation einer Secondary Site niemals den gleichen Sitecode verwenden, da dies zu diversen Problemen führen kann.
    Montag, 4. Oktober 2010 12:30
    |
    Beantworter
  • Question
    Anmelden
    0
    Anmelden

    Sorry hier die logs der Installation

     

    SMS_EXECUTIVE started SMS_HIERARCHY_MANAGER as thread ID 3416 (0xD58).  $$<SMS_HIERARCHY_MANAGER><Thu Sep 30 10:52:36.238 2010 W. Europe Daylight Time><thread=1528 (0x5F8)>
    ~Hierarchy Manager (build 6487) is starting...  $$<SMS_HIERARCHY_MANAGER><Thu Sep 30 10:52:36.238 2010 W. Europe Daylight Time><thread=3416 (0xD58)>
    ~Created inbox def 27, Hierarchy Manager (Site Public Keys)  $$<SMS_HIERARCHY_MANAGER><Thu Sep 30 10:52:36.248 2010 W. Europe Daylight Time><thread=3416 (0xD58)>
    ~Waiting for the inbox manager to create the inboxes, retry in 10 seconds.  $$<SMS_HIERARCHY_MANAGER><Thu Sep 30 10:52:36.258 2010 W. Europe Daylight Time><thread=3416 (0xD58)>
    ~Waiting for the inbox manager to create the inboxes, retry in 10 seconds.  $$<SMS_HIERARCHY_MANAGER><Thu Sep 30 10:52:46.257 2010 W. Europe Daylight Time><thread=3416 (0xD58)>
    CPublicKeyLookup::Initialize("D:\SMS\inboxes\hman.box\pubkey")  $$<SMS_HIERARCHY_MANAGER><Thu Sep 30 10:52:56.286 2010 W. Europe Daylight Time><thread=3416 (0xD58)>
    CPublicKeyLookup::Initialize()  Initializing the Public Key Store Path to D:\SMS\inboxes\hman.box\pubkey~  $$<SMS_HIERARCHY_MANAGER><Thu Sep 30 10:52:56.286 2010 W. Europe Daylight Time><thread=3416 (0xD58)>
    ~Successfully created the file D:\SMS\inboxes\hman.box\pubkey\YOR.CT4  $$<SMS_HIERARCHY_MANAGER><Thu Sep 30 10:52:56.306 2010 W. Europe Daylight Time><thread=3416 (0xD58)>
    Writing out maintenance task default schedule to site control file.  $$<SMS_HIERARCHY_MANAGER><Thu Sep 30 10:52:56.356 2010 W. Europe Daylight Time><thread=3416 (0xD58)>
    Active Directory DS Root:DC=emea,DC=worldwide,DC=com~  $$<SMS_HIERARCHY_MANAGER><Thu Sep 30 10:52:56.416 2010 W. Europe Daylight Time><thread=3416 (0xD58)>
    Searching for the System Management Container.~  $$<SMS_HIERARCHY_MANAGER><Thu Sep 30 10:52:56.416 2010 W. Europe Daylight Time><thread=3416 (0xD58)>
    System Management container exists.~  $$<SMS_HIERARCHY_MANAGER><Thu Sep 30 10:52:56.426 2010 W. Europe Daylight Time><thread=3416 (0xD58)>
       Searching for SMS-Site-YOR Site Object.~  $$<SMS_HIERARCHY_MANAGER><Thu Sep 30 10:52:56.426 2010 W. Europe Daylight Time><thread=3416 (0xD58)>
       SMS-Site-YOR exists, updating.~  $$<SMS_HIERARCHY_MANAGER><Thu Sep 30 10:52:56.426 2010 W. Europe Daylight Time><thread=3416 (0xD58)>
    SMS-Site-YOR could not be updated, error code = 5.~  $$<SMS_HIERARCHY_MANAGER><Thu Sep 30 10:52:56.456 2010 W. Europe Daylight Time><thread=3416 (0xD58)>
    STATMSG: ID=4912 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_HIERARCHY_MANAGER" SYS=UKYORVMFS04 SITE=YOR PID=2664 TID=3416 GMTDATE=Thu Sep 30 08:52:56.456 2010 ISTR0="SMS-Site-YOR" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_HIERARCHY_MANAGER><Thu Sep 30 10:52:56.456 2010 W. Europe Daylight Time><thread=3416 (0xD58)>
    ~Wait for site control changes for maximum 3600 seconds...  $$<SMS_HIERARCHY_MANAGER><Thu Sep 30 10:52:56.466 2010 W. Europe Daylight Time><thread=3416 (0xD58)>
    ~Sent the actual site control image to site TDE  $$<SMS_HIERARCHY_MANAGER><Thu Sep 30 10:53:19.146 2010 W. Europe Daylight Time><thread=3416 (0xD58)>
    ~Sent the actual site control image to site TDE  $$<SMS_HIERARCHY_MANAGER><Thu Sep 30 10:53:19.186 2010 W. Europe Daylight Time><thread=3416 (0xD58)>
    ~Sent the actual site control image to site TDE  $$<SMS_HIERARCHY_MANAGER><Thu Sep 30 10:53:19.216 2010 W. Europe Daylight Time><thread=3416 (0xD58)>
    ~Sent the actual site control image to site TDE  $$<SMS_HIERARCHY_MANAGER><Thu Sep 30 10:53:19.266 2010 W. Europe Daylight Time><thread=3416 (0xD58)>
    ~Sent the actual site control image to site TDE  $$<SMS_HIERARCHY_MANAGER><Thu Sep 30 10:53:19.296 2010 W. Europe Daylight Time><thread=3416 (0xD58)>
    ~Sent the actual site control image to site TDE  $$<SMS_HIERARCHY_MANAGER><Thu Sep 30 10:53:19.336 2010 W. Europe Daylight Time><thread=3416 (0xD58)>
    ~Sent the actual site control image to site TDE  $$<SMS_HIERARCHY_MANAGER><Thu Sep 30 10:53:19.366 2010 W. Europe Daylight Time><thread=3416 (0xD58)>
    Active Directory DS Root:DC=emea,DC=worldwide,DC=com~  $$<SMS_HIERARCHY_MANAGER><Thu Sep 30 10:53:19.386 2010 W. Europe Daylight Time><thread=3416 (0xD58)>
    Searching for the System Management Container.~  $$<SMS_HIERARCHY_MANAGER><Thu Sep 30 10:53:19.396 2010 W. Europe Daylight Time><thread=3416 (0xD58)>
    System Management container exists.~  $$<SMS_HIERARCHY_MANAGER><Thu Sep 30 10:53:19.396 2010 W. Europe Daylight Time><thread=3416 (0xD58)>
       Searching for SMS-Site-YOR Site Object.~  $$<SMS_HIERARCHY_MANAGER><Thu Sep 30 10:53:19.396 2010 W. Europe Daylight Time><thread=3416 (0xD58)>
       SMS-Site-YOR exists, updating.~  $$<SMS_HIERARCHY_MANAGER><Thu Sep 30 10:53:19.396 2010 W. Europe Daylight Time><thread=3416 (0xD58)>
    SMS-Site-YOR could not be updated, error code = 5.~  $$<SMS_HIERARCHY_MANAGER><Thu Sep 30 10:53:19.396 2010 W. Europe Daylight Time><thread=3416 (0xD58)>
    STATMSG: ID=4912 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_HIERARCHY_MANAGER" SYS=UKYORVMFS04 SITE=YOR PID=2664 TID=3416 GMTDATE=Thu Sep 30 08:53:19.396 2010 ISTR0="SMS-Site-YOR" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_HIERARCHY_MANAGER><Thu Sep 30 10:53:19.396 2010 W. Europe Daylight Time><thread=3416 (0xD58)>
       Time to verify that the public key of current site server in the site control file is still valid.  $$<SMS_HIERARCHY_MANAGER><Thu Sep 30 10:53:19.396 2010 W. Europe Daylight Time><thread=3416 (0xD58)>
    ~Wait for site control changes for maximum 3600 seconds...  $$<SMS_HIERARCHY_MANAGER><Thu Sep 30 10:53:19.406 2010 W. Europe Daylight Time><thread=3416 (0xD58)>
    Active Directory DS Root:DC=emea,DC=worldwide,DC=com~  $$<SMS_HIERARCHY_MANAGER><Thu Sep 30 10:53:24.421 2010 W. Europe Daylight Time><thread=3416 (0xD58)>
    Searching for the System Management Container.~  $$<SMS_HIERARCHY_MANAGER><Thu Sep 30 10:53:24.421 2010 W. Europe Daylight Time><thread=3416 (0xD58)>
    System Management container exists.~  $$<SMS_HIERARCHY_MANAGER><Thu Sep 30 10:53:24.421 2010 W. Europe Daylight Time><thread=3416 (0xD58)>
       Searching for SMS-Site-YOR Site Object.~  $$<SMS_HIERARCHY_MANAGER><Thu Sep 30 10:53:24.421 2010 W. Europe Daylight Time><thread=3416 (0xD58)>
       SMS-Site-YOR exists, updating.~  $$<SMS_HIERARCHY_MANAGER><Thu Sep 30 10:53:24.431 2010 W. Europe Daylight Time><thread=3416 (0xD58)>
    SMS-Site-YOR could not be updated, error code = 5.~  $$<SMS_HIERARCHY_MANAGER><Thu Sep 30 10:53:24.431 2010 W. Europe Daylight Time><thread=3416 (0xD58)>
    STATMSG: ID=4912 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_HIERARCHY_MANAGER" SYS=UKYORVMFS04 SITE=YOR PID=2664 TID=3416 GMTDATE=Thu Sep 30 08:53:24.431 2010 ISTR0="SMS-Site-YOR" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_HIERARCHY_MANAGER><Thu Sep 30 10:53:24.431 2010 W. Europe Daylight Time><thread=3416 (0xD58)>
    ~Wait for site control changes for maximum 3600 seconds...  $$<SMS_HIERARCHY_MANAGER><Thu Sep 30 10:53:24.431 2010 W. Europe Daylight Time><thread=3416 (0xD58)>
    Active Directory DS Root:DC=emea,DC=worldwide,DC=com~  $$<SMS_HIERARCHY_MANAGER><Thu Sep 30 10:53:29.455 2010 W. Europe Daylight Time><thread=3416 (0xD58)>
    Searching for the System Management Container.~  $$<SMS_HIERARCHY_MANAGER><Thu Sep 30 10:53:29.465 2010 W. Europe Daylight Time><thread=3416 (0xD58)>
    System Management container exists.~  $$<SMS_HIERARCHY_MANAGER><Thu Sep 30 10:53:29.465 2010 W. Europe Daylight Time><thread=3416 (0xD58)>
       Searching for SMS-Site-YOR Site Object.~  $$<SMS_HIERARCHY_MANAGER><Thu Sep 30 10:53:29.465 2010 W. Europe Daylight Time><thread=3416 (0xD58)>
       SMS-Site-YOR exists, updating.~  $$<SMS_HIERARCHY_MANAGER><Thu Sep 30 10:53:29.475 2010 W. Europe Daylight Time><thread=3416 (0xD58)>

    Montag, 4. Oktober 2010 12:51
    |
  • Question
    Anmelden
    0
    Anmelden
    Ich fragte nach dem Zeitpunkt, an dem Du das File kopiert hast (nach dem preinst.exe; beim Kopieren des .ct4 bzw .ct5 Files in die hman.box der entsprechenden Site), nicht nach dem Installationszeitpunkt ... Wobei oben erkennt man, dass Permissions auf dem System Management gefehlt haben. Du kannst http://technet.microsoft.com/en-us/library/bb693690.aspx nochmal durchführen und dann das Log beobachten (auf der Primary und Secondary). Weiterhin ist sender.log auf beiden Sites interessant, um festzustellen, dass sie miteinander kommunizieren können.
    Montag, 4. Oktober 2010 13:42
    |
    Beantworter
  • Question
    Anmelden
    0
    Anmelden

    Die Rechte haben gefehlt, weil sie nicht durchgeerbt wurden. Das habe ich dann behoben.

    Das CT4 file haben ich direkt in den folder der primary kopiert \inboxes\hman.box\pubkey

    und das CT5 file in inboxes\hman.box\pubkey der secondary kopiert

    Habe ich da was falsch verstanden?

     

    Ich kann leider hier nicht die ganze log posten da sie zu groß ist. Nach was soll ich suchen?

    Die sender logs sehen eigentlich gut aus. die habe ich schon geprüft.

    Montag, 4. Oktober 2010 15:48
    |
  • Question
    Anmelden
    0
    Anmelden
    Ich stelle mal morgen die logs rein 
    Montag, 4. Oktober 2010 15:59
    |
  • Question
    Anmelden
    0
    Anmelden
    Das CT4 file haben ich direkt in den folder der primary kopiert \inboxes\hman.box\pubkey

    und das CT5 file in inboxes\hman.box\pubkey der secondary kopiert

    Habe ich da was falsch verstanden?

    Vermutlich, siehe: http://technet.microsoft.com/en-us/library/bb693690.aspx. Da ist nirgends die Rede von \pubkey. Einfach planlos Logfiles posten macht keinen Sinn. trace32.exe ist Dir bekannt (Logfile-Viewer aus dem ConfigMgr Toolkit)? Einfach mal der Anleitung genau folgen und dabei das Log beobachten. Dann siehst Du sofort Erfolg oder Fehler.
    Montag, 4. Oktober 2010 18:13
    |
    Beantworter