Microsoft Knowledge Base Email Alertz

(830017) - After you upgrade a server that is running Microsoft Systems Management Server 2.0 to Microsoft Systems Management Server 2003, you notice that the following two collections do not appear in the Collections container: All Windows Workstation or...

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 830017 - Last Review: October 27, 2006 - Revision: 2.2

Two Systems Management Server 2003 collections do not appear after you upgrade from Systems Management Server 2.0

SYMPTOMS

After you upgrade a server that is running Microsoft Systems Management Server 2.0 to Microsoft Systems Management Server 2003, you notice that the following two collections do not appear in the Collections container:
All Windows Workstation or Professional Systems
All Windows Server Systems
Instead, the following two collections are listed in the Collections container:
All Windows NT Workstation Systems
All Windows NT Server Systems
However, if you perform a new installation of Systems Management Server 2003, these collections do appear. You expect the same collections to appear when you upgrade to Systems Management Server 2003 as when you perform a fresh installation of Systems Management Server 2003.

CAUSE

This problem occurs because the existing Systems Management Server 2.0 collection names are retained when you upgrade to Systems Management Server 2003.

WORKAROUND

To work around this problem, rename each collections to the correct SMS 2003 collection name. To do this, follow these steps:
  1. Click Start, point to All Programs, point to Systems Management Server, and then click SMS Administrator Console.
  2. Locate and expand the Collections subtree.
  3. Right-click the All Windows NT Workstation Systems collection, and then click Properties.
  4. In the Name text box, change All Windows NT Workstation Systems to All Windows Workstation or Professional Systems, and then click OK.
  5. Right-click the All Windows NT Server Systems collection, and then click Properties.
  6. In the Name text box, change All Windows NT Server Systems to All Windows Server Systems, and then click OK.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.

MORE INFORMATION

When you upgrade from Systems Management Server 2.0 to Systems Management Server 2003, the Setup program does not rename these Systems Management Server 2.0 collections to the same names as those that appear when you perform a fresh Systems Management Server 2003 installation. However, the collection identifiers (IDs) remain the same for both an upgrade installation and a fresh installation.

Also, when you install Systems Management Server 2003, additional collections are created to provide the same information as the All Windows Workstation or Professional Systems collection and the All Windows Server Systems collection.

APPLIES TO
  • Microsoft Systems Management Server 2003
Keywords: 
kbnofix kbbug KB830017
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate