Solved

SMS 2.0 and SCCM 2007

Posted on 2010-09-01
3
835 Views
Last Modified: 2013-11-21
We had SMS 2.0 and hardly used it since it was just terrible to use.  Several months back we decommissioned the server but still have the computer object in the computers container in AD with domain and forest level 2003.  The IT person who is doing the install of SCCM 2007 version found about the SMS 2.0 version and the server it was installed.  He is informing me that he don't need to extend the schema for sccm 2007 since he sees SMS 2,0 has the schema extended already for this.  He wants to run the schema extension wizard to allow him to change the Site Name and Management Point.
I want to confirm if his statement is correct which I don't think it is since SMS 2.0 and SCCM 2007 will have to have different attributes.  Also, will this cause a problem installing SCCM 2007 since the SMS 2.0 server is no longer around.
0
Comment
Question by:hbpub
3 Comments
 
LVL 3

Accepted Solution

by:
socrates2012 earned 500 total points
ID: 33582037
Here is a link to a Technet article on running SCCM 2007 on a SMS 2003 extended schema.

http://technet.microsoft.com/en-us/library/bb694066.aspx

"It is supported to deploy Configuration Manager 2007 sites using SMS 2003 Active Directory schema extensions. There are important considerations when deciding whether or not to extend the Active Directory schema for Configuration Manager 2007. Even if the Configuration Manager 2007 site is publishing site data to Active Directory Domain Services, the required Active Directory schema attributes to store the published data will not exist in some cases if the Active Directory schema has only been extended for SMS 2003.

If the Active Directory schema has been extended for SMS 2003, but not for Configuration Manager, the following limitations apply:

A Configuration Manager 2007 server locator point must be used to allow clients to verify assigned site compatibility to complete client assignment. Clients can automatically locate a server locator point through Active Directory Domain Services if the schema is extended for SMS 2003.

Because Network Access Protection for Configuration Manager requires Configuration Manager 2007 Active Directory schema extensions, this feature is unsupported for sites using SMS 2003 Active Directory schema extensions.

Site mode changes require manual workarounds on clients.

Client communication port changes require manual workarounds.

The management point dNSHostName attribute is no longer published to Active Directory Domain Services."
0
 

Author Closing Comment

by:hbpub
ID: 33582188
Thanks for the info. I will show this to my fellow IT person.  This is very helpful.  
0
 

Expert Comment

by:Bigby
ID: 33638453
Actually, I am the one doing the SCCM install.  The original problem as outlined is not entirely correct.  I have completed the SCCM install on a server named NYSCCM and all modules are working except for software distribution.  The client handshakes with the MP and stops with the message that it is waiting to download the package.  When I look at the logs the client is waiting to pick up the software from a server NYSMS01 which is the old decommissioned server.  Since the schema was updated for the SMS 2.0 rollout (which never happened) the attribute 'MS-SMS-Default-MP' contains the old server value 'NYSMS01' so the clients are waiting on that server which does not exist.  If I add a an entry in the HOSTS file that points NYSMS01 to the IP address of NYSCCM on EACH client workstation then software installation works just fine.  The Operations group wants to modify the AD value 'MS-SMS-Default-MP' manually which is a bad idea for two reasons:

- Microsoft always recommends that you use a configuration tool to modify such values.
- I don't know what other values need to be updated and that in turn can cause other failures down the line.

Without running the schema extension tools my options are:

- Remove the attributes created by the SMS 2.0 Schema Extension tool (really, really bad idea).
- Add entries to the HOSTS file for all the clients and pray that no other incorrectly configured attributes cause the clients to break (really bad idea).

Prior to SCCM one could run the SMS Installation wizard and change the attributes but now the method is to run the schema extension tool (extadsch.exe) which installs the schema extension if they don't exist OR updates them if they do exist.  In addition to allowing me to update the necessary information in a Microsoft-approved manner it will add the following new attributes:

-      mS-SMS-Health-State
-      mS-SMS-Source-Forest
-      mS-SMS-Version
-      mS-SMS-Capabilities

I think that is the best way to go.

Thanks,

--Brian
0

Featured Post

How to run any project with ease

Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
- Combine task lists, docs, spreadsheets, and chat in one
- View and edit from mobile/offline
- Cut down on emails

Join & Write a Comment

Remote Desktop Protocol or RDP has become an essential tool in many offices. This article will show you how to set up an external IP to point directly to an RDP session. There are many reasons why this is beneficial but perhaps the top reason is con…
Some time ago I faced the need to use a uniform folder structure that spanned across numerous sites of an enterprise to be used as a common repository for the Software packages of the Configuration Manager 2007 infrastructure. Because the procedu…
This video gives you a great overview about bandwidth monitoring with SNMP and WMI with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're looking for how to monitor bandwidth using netflow or packet s…
This video shows how to remove a single email address from the Outlook 2010 Auto Suggestion memory. NOTE: For Outlook 2016 and 2013 perform the exact same steps. Open a new email: Click the New email button in Outlook. Start typing the address: …

707 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

16 Experts available now in Live!

Get 1:1 Help Now