Microsoft KB Archive/841923

= Files are not copied to new client access points, and existing client access points do not receive updated files in Systems Management Server 2.0 =

Article ID: 841923

Article Last Modified on 10/27/2006

-

APPLIES TO


 * Microsoft Systems Management Server 2.0 Standard Edition

-



Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry



SYMPTOMS
The Microsoft Systems Management Server (SMS) 2.0 Inbox Manager component cannot update files on the client access point (CAP). No errors are logged in the SMS component logs or the Windows event logs. If you remove and then re-create the CAP, not all the files are copied to the CAP. The folder structure is created on the CAP, but some or many of the files are not copied to the folders. Many files in the CAP folders have older dates, while some files have more recent dates.

After you upgrade to an SMS service pack, some clients do not complete the upgrade. Some client components are not upgraded to the service pack level.



CAUSE
This problem may occur if the following registry subkey on the site server is corrupted:

For example, some subkeys may repeat the key name or sections of the path in the values.

The Inbox Instances key defines the location of the component folders on the site server. By default, the component folders are in the SMS\Inbox folder on the site server. When SMS creates a CAP, new keys are written under the Inbox Instances key to define the network abstraction layer (NAL) path of the CAP server and share.

Original source keys have a defined Universal Naming Convention (UNC) entry that points to the site server. The CAP registry subkeys include a NAL Path value. The subkeys may appear in a different order on different CAP servers. SMS creates and deletes the CAP subkeys when a CAP is added or removed from the hierarchy.

Note The subkeys are created only when you install the SMS site server. SMS does not rebuild the subkeys after the initial installation of the site. The subkeys are not rebuilt by site resets or by re-application of a service pack. The subkeys cannot be rebuilt by an automatic process.



RESOLUTION
To resolve this problem, use one of the following methods:
 * Method 1: Remove and then restore the SMS site.
 * Method 2: Import the Inbox Instances key from another SMS site that is working correctly.

Method 1: Remove and then restore the SMS site
Back up the site server database, and then remove the SMS site. To re-create the Inbox Instances keys, reinstall the SMS site, and then restore the database.

You can use the Systems Management Server Recovery Expert to help you prepare and restore your SMS site. For additional information, visit the following Microsoft Web site:

http://www.microsoft.com/SMServer/techinfo/administration/20/recovery/

For additional information about how to remove an SMS 2.0 primary site, click the following article number to view the article in the Microsoft Knowledge Base:

840676 How to remove a primary site in Systems Management Server 2.0

Method 2: Import the Inbox Instances key from another site server that is working correctly
Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

Note You must import the keys from a site server that is working correctly. If another site server is not available, you must use Method 1 to remove and to restore your SMS 2.0 site server.  On the site that is working correctly, click Start, click Run, type regedit, and then click OK. Locate and then click the following registry subkey:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Inbox Source\Inbox Instances

 On the Registry menu, click Export Registry File. Select a save location, type Goodregistry as the registry file name, and then click Save. Copy the file to the SMS site server that has the corrupted registry. On the SMS site server that is experiencing the problem, remove all the CAPs. To do this, follow these steps: <ol style="list-style-type: lower-alpha;"> Start the SMS Administrator console.</li> Expand the Site Database\Site Hierarchy\ \Site Settings tree, and then click Site Systems, where  is the site that is experiencing the problem.</li> Double-click a site system to view the Site System Properties.</li> On the Client Access Point tab, click to clear the Use this site system as a client access point check box, and then click OK.</li> Repeat step d for each site system that is listed.</li> Monitor each CAP to make sure that the CAP_ folder and share is removed, where   is the site code of the SMS site. After all the CAPs are removed, go to step 7.</li></ol> </li> On the site server that is experiencing the problem, click Start, click Run, type regedit, and then click OK.</li> Locate and then click the following registry subkey:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Inbox Source\Inbox Instances

</li> On the Registry menu, click Export Registry File.</li> Select a save location, type Oldregistry as the registry file name, and then click Save.</li> Delete the Inbox Instances key.</li> Start Notepad, and then open the Goodregistry.reg file that you copied from the site server that is working correctly.</li>  Delete the CAP sections from the .reg file. In the CAP sections, the &quot;NAL Path&quot; entry has a value. The &quot;UNC Path&quot; entry has a null value. For example, a CAP section is similar to the following: <pre class="fixed_text">[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Inbox Source\Inbox Instances\14] &quot;Inbox Name&quot;=&quot;Package Info CAP&quot; &quot;NAL Path&quot;=&quot;MSWNET:[\&quot;SMS_SITE=xxx\&quot;]\\\\server name\\CAP_xxx\\&quot; &quot;Relative Path&quot;=&quot;pkginfo.box&quot; &quot;UNC Path&quot;=&quot;&quot; &quot;Location Type&quot;=dword:00000003 &quot;Assistant Flags&quot;=dword:00000000 The following example shows an original source section that has a value for the &quot;UNC Path&quot; entry and a null value for the &quot;NAL Path&quot; entry. <pre class="fixed_text">[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Inbox Source\Inbox Instances\13] &quot;Inbox Name&quot;=&quot;Package Master Info&quot; &quot;NAL Path&quot;=&quot;&quot; &quot;Relative Path&quot;=&quot;inboxes\\pkginfo.box&quot; &quot;UNC Path&quot;=&quot;\\\\server name\\SMS_xxx\\inboxes\\pkginfo.box&quot; &quot;Location Type&quot;=dword:00000001 &quot;Assistant Flags&quot;=dword:00000000 </li> In each remaining source section, change the name and share of the site server in the &quot;UNC Path&quot; entry to the name and share of the site server that is experiencing the problem. For example, change the site server name and share in the following source section:

&quot;UNC Path&quot;=&quot;\\\\ \SMS_ \\inboxes\ &quot;

Important The additional backslash characters are required.</li> After you modify the &quot;UNC Path&quot; entry in each section, save the .reg file, and then exit Notepad.</li> Import the .reg file on the site server that is experiencing the problem. To do this, follow these steps: <ol style="list-style-type: lower-alpha;"> <li>Locate the Goodregistry.reg file that you saved in step 4.</li> <li>Right-click the Goodregistry.reg file, and then click Merge.</li> <li>Click Yes to merge the information.</li> <li>Start Registry Editor.</li> <li>Locate and then click the following registry subkey:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Inbox Source\Inbox Instances

</li> <li>Make sure that each Inbox Instances key correctly references the site server.</li> <li>If any Inbox Instances keys are empty, delete those keys.</li></ol> </li> <li>Make sure that the correct permissions are restored to the Inbox Source keys. To do this, follow these steps: <ol style="list-style-type: lower-alpha;"> <li>Click Start, click Run, type regedt32, and then click OK.</li> <li>Locate and then click the following registry subkey:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Inbox Source

</li> <li>On the Security menu, click Permissions. The Inbox Source, Inbox Definitions, Inbox Instances, and Inbox Rules keys must have the following permissions: <ul> <li>Administrators = Full Control</li> <li>SMSServer_ = Full Control</li> <li>Everyone = Read</li></ul>

The numeric keys under the Inbox keys must have the following permissions: <ul> <li>Administrators = Full Control</li> <li>SMSServer_ = Full Control</li></ul> </li></ol> </li> <li>Re-create the CAP.</li></ol>

If the CAP folders are still not created correctly after you complete these steps, use Method 1.

<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.

Keywords: kbcap kbserver kbregistry kbinboxmgr kbtshoot kbupgrade kbprb KB841923

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.