Re: Feasability
From: Travis Sweat \(MSFT\) (travsw_at_microsoft.com)
Date: 03/13/04
- Next message: Adam Welker [MSFT]: "Re: MBSA 1.2 for SMS 2.0 sp4"
- Previous message: NoDoubt: "SMS 2003:standard site reporting to advanced site"
- In reply to: MSGuru: "Feasability"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 13 Mar 2004 10:33:38 -0800
Ok, putting aside if its overkill or not here's a short list of something's
to know. I HIGHLY encourage you to read the Concepts and Planning Guide. I
know people hate it when us Microsoft people say to read the manuals, but
seriously we put in a lot of work to try and make deployments as easy as
possible. (End soap box stand)
Ok roll up yer sleeves and lets get a check list going.
1) Understand which security model you are going to use. Advanced or
Standard. If you are using Standard you will have to create service accounts
that have admin level privileges. Please see the guide about this topic for
further instructions. For Advanced Security you will be using the Machine
accounts. A quick tip: you add machine accounts to groups in windows 2000 by
typing "Net localgroup <groupname> /add Machinename$"
2) Once you know the security model you need to know if you will be
extending your AD schema. Are you going to have an AD aware environment or
not. If so you will need to extend the schema and allow the service or
machine accounts rights to publish in AD. If you are not AD aware you will
need to make special entries on the WINS servers. All this can again be
found in the manuals. Also you will need to set the a property on the DC so
that the AD schema can be updated. On the DC run the following command:
"regsvr32 c:\winnt\system32\schmmgmt.dll" once that registers run from start
run: mmc.exe. You will have an MMC console open now. Choose console\add
remove snap-in. Choose add, then Add "Active Directory Schema", hit ok. Now
in the console root right click on Active Directory Schema. Now choose
Operations Master. In that property page there is an option which says
something like "allow the schema to be updated on this DC" choose that
option and close out.
3) Which client will you be using? Advanced or Legacy client? Each have
their own special considerations.
4) If you will be planning on creating Server Locator Points or Management
Points you will need to have IIS enabled.(On the site server or a remote
server that will hold site rolls.)
I think that will keep you busy for a bit. Its a short list but those should
save you some initial headaches.
-- Travis Sweat [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights "MSGuru" <MSGuru79@hotmail.com> wrote in message news:esb6OnrBEHA.688@tk2msftngp13.phx.gbl... > Hey guys, > > I am a sys admin for a 25 person organization we run a windows 2000 network > with a few windows 2003 server ( they are not DC's). I wasnt to obviously > play around with new technology and was wondering how feasable SMS 2003 is > for my orgainzation. I want to get ready for the new windows XP service pack > etc and was planning to install SMS 2003 on a windows 2000 network. Please > let me know of things I should or shouldnt do. > > thanks for your help > -Z > >
- Next message: Adam Welker [MSFT]: "Re: MBSA 1.2 for SMS 2.0 sp4"
- Previous message: NoDoubt: "SMS 2003:standard site reporting to advanced site"
- In reply to: MSGuru: "Feasability"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
