Re: replacing a sms server

I don't see a system management container in AD, where can I see that?


"Kim Oppalfens [MVP]" <""Kim dot Oppalfen" wrote:



Domain computers that have an sms 2003 client installed can have it
upgraded to sccm 2007 clients without you needing to manually uninstall
the clients, so you should be fine there.

Deactivating the server can be as simple as uninstalling it, make sure
the objects are removed from the system management container in AD.

So far sccm hasn't let me down in anything I tried with it, so
definitely looks like a winner. The only thing I struggle with a little
is admin console performance.




--
"Everyone is an expert at something"
Kim Oppalfens - Sms Expert for lack of any other expertise
Windows Server System MVP - SMS
http://www.blogcastrepository.com/blogs/kim_oppalfenss_systems_management_ideas/default.aspx

cuadmin wrote:
Kim,
I am going to move up to SCCM 2007, I really don't have any data that I need
to keep from the previous SMS server. Will there be any problem for the
domain computers that have the sms client installed. What's the best way to
deactivate the sms server? How have you found SCCM - is it as good as
microsoft claims?
I am very interested in using it to deploy winxp images in hopes that it
works better than ghost which always required a visit to the workstation.

thanks
Neil



"Kim Oppalfens [MVP]" <""Kim dot Oppalfen" wrote:

Kim is right, this is the safest way of extending your schema.

cuadmin wrote:
thanks, I will give it a try. Originally I had installed sms on a member
server and then for some reason I promoted it to a domain controller, but I'm
not sure why I did that now. What about extending the schema, I see on the
web
http://www.blogcastrepository.com/blogs/kim_oppalfenss_systems_management_ideas/default.aspx
that Kim says to do this:

It is advised to follow the procedure below, before any schema modifications
are made, not just sms 2003 schema extentions. There are no known issues in
making the SMS 2003 schema extensions.

This being said, keep in mind that

1) Every forest only has 1 Schema partition.

2) There is no such thing as an AUTHORITATIVE RESTORE for the schema
partition.

These 2 things combined spell disaster if something did go wrong. If
something does go wrong with the schema extension process and the schema gets
replicated to all dc's.

If this happens you have two options

1) Hire a Microsoft PSS consoltant to help clean up your Active Directory
Schema mess

2) Restore a backup of the Active Directory on All domain controllers in the
Forest. All domain controllers have to be disconnected from the network
during this recovery.

Neither of these seem to really appealing to me.



Proper Procedure

Locate the server that is the schema master
In a command prompt type regsvr32 schmmgmt.dll (You should get a message
that the dll was registered succesfully)
Type mmc, and add the Active Directory Schema snap-in
Right Click Active Directory Schema and select Operations Masters
Take note of the current Schema master
Back up the schema master.
Disconnect the schema master from the network and do not reestablish the
connection until the end of this procedure. (This means fysically removing
the cable, do not just disable the network interface since some of the tools
used later in the procedure require a functional tcp/ip stack.
On the schema master, insert the SMS 2003 SP2 Setup CD in the CD-ROM drive.
Open a command prompt, change to the CD-ROM drive, and change to the
\SMSSETUP\BIN\I386 folder on the CD.
On the schema master, at the command prompt, type Extadsch.exe
After the preceding command has finished on the schema master, confirm that
the preparation of the forest was successful. Review
%SystemDrive%\ExtAdSch.log
Evaluate the information you gathered in the previous step and choose
accordingly:
If extadsch.exe ran without errors, reconnect the schema master to the
network and continue with the next step of this procedure.
If extadsch.exe ran but error messages provided instructions for additional
steps to take, follow the instructions and then return to the confirmation
process described in the previous step.
If extadsch.exe did not run successfully, restore the schema master from
backup and investigate the corrective steps necessary so that extadsch.exe
can be run successfully.
Important Note: Extending the Schema will trigger a FULL Global Catalog
Synchronization between Windows 2000 Global catalog servers. Windows 2003
Global Catalog servers will use delta replication.

Enjoy.

"Everyone is an expert at something"
Kim Oppalfens - Sms Expert for lack of any other expertise
Windows Server System MVP - SMS

Posted: Monday, May 14, 2007 2:13 PM by kimoppalfens | 2 Comments
Filed under: SCCM 2007, Sms 2003

How can I tell if my schema is already extended?



"Matthew Hudson" wrote:

SMS should be installed on just a member server.
It would be best to keep the same site code server name can change. Since
all the information is published in the AD the clients will contact the AD
and find the new server name. I did the very same thing. It took about 3
days before all the computers came back to the fold. I did have several
client that just refused to change over. I was forced to uninstall and
re-install the client. I just watched for computers that weren't assinged
and weren't moving over.

Does this make sense?

--
-----------------------
http://sms-hints-tricks.blogspot.com/


"cuadmin" wrote:

I need to replace our current sms server (an AD domain controller, also
running WSUS 3.0 and deployment services) with a new server. The current ad
schema is 2003 R2:
Should the new server be a domain controller or a just a member server?
Can the site name remain the same?
Will the domain computers need to have sms client re-installed?
Should I also install MOM on this server?


.

Relevant Pages

  • Re: After reinstallation
    ... If you manually install the client and open the system manager in control ... See Ccm.log on site server ... SMS Active Directory System Group Discovery Agent reported errors for 3 ... The MP installation was succesful, ...
    (microsoft.public.sms.setup)
  • Re: Adv Client with Workgroup Computers
    ... I was trying to use the SMS tools from the SMS server to initiate harware ... Inv for example the account is a domain account but the Client PC is in a ... Is there a procedure for installing the ADV client localy on a workgroup ... I have manually added to the WINS server. ...
    (microsoft.public.sms.admin)
  • Re: Schema Update Problem
    ... rebooting the SMS server and re-running extadsch.exe from the sms server. ... I have confirmed the Schema Master is also my Master AD Server. ... Error code = 8245. ...
    (microsoft.public.sms.setup)
  • Re: replacing a sms server
    ... Domain computers that have an sms 2003 client installed can have it upgraded to sccm 2007 clients without you needing to manually uninstall the clients, so you should be fine there. ... Deactivating the server can be as simple as uninstalling it, make sure the objects are removed from the system management container in AD. ... It is advised to follow the procedure below, before any schema modifications are made, not just sms 2003 schema extentions. ...
    (microsoft.public.sms.setup)
  • Re: replacing a sms server
    ... to keep from the previous SMS server. ... domain computers that have the sms client installed. ... this is the safest way of extending your schema. ... Locate the server that is the schema master ...
    (microsoft.public.sms.setup)