We currently have SMS 2.0 running
in production. The SMS server provides every role except for the logon points,
which is handled by our 3 domain controllers. I am curious if I could bring up a
SMS 2003 server on the same domain and use the same domain controller as long as
the site name was different.
The logon folder created should have different names. The reason I would like to
do this is to see how SMS 2003 will operate on the domain, so we would bring a
few test machines on with the SMS2003 client but leave all our other existing
clients on the SMS 2.0 server. This may be a far-fetched idea, but I figured I
would see what others thought about it.
Thanks much.
Contributed By: Rick Butler
on
the SMS
2003 Forum
If it were my domain, I'd probably not even chance it. I'd build it up in a
test network. SMS 2003 integrates with AD. Even though the Schema Mod is a
separate step, SMS doesn't work right without it.
You might set up a test LAN, roll 2.0 out and then see the upgrade path. That
would be something I'd like to talk about in due course.
There are two things you need to do to get ready for upgrade
You need to do a
upgrade test on your site database. Backup your site database, restore it to a
test SQL box (no need to install SMS) and Test Upgrade the DB. It's a
destructive process, so DO THIS IN LAB!
After that, run the
Deployment Readiness Wizard against your 2.0 environment.
That should point out the major bends
in the road.
Contributed By:
Cliff Hobbs [MVP SMS]
on
the SMS
2003 Forum
Rick has
hit the nail on the head.
This is definitely something for the lab. Although I've heard good reports about
people using SMS 2003 in production without too many hitches I'd be a bit wary about putting
any software near a production
network without either having tried it in the lab before or having done some
research such as checking out the Microsoft SMS web site:
http://www.microsoft.com/smserver
|
 |
To see other SMS 2003 Design and Planning related FAQs click
here. |
|