Re: Schema and "first" System Management Container
From: Kim Oppalfens (kim_at_computacenter.nospam)
Date: 09/29/04
- Next message: Tobias Svensson: "SMS_SQL_monitor fails to install"
- Previous message: Kim Oppalfens: "Re: SQL Permissions"
- In reply to: Jason: "Schema and "first" System Management Container"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 29 Sep 2004 17:11:11 +0200
Although I haven't verified this, this doesn't really seem to make
sense. The system management container is created in the domain
partition, so I couldn't see how it would influence other domains at
all.
If it would be created in Configuration partition it might have an
impact, but now it doesn't.
Kim Oppalfens
In article <Og6X9iOpEHA.3392@TK2MSFTNGP15.phx.gbl>, jasons@hotmail.com
says...
> Hi, Our Active Directory have an "empty " root DC domain at the top level
> with 6 child domains. Total of 30K users. Now that the schema will be
> extended shortly for our SMS 2003 deployment.
> But I heard that since our root domain is an " empty" root with DC and no
> other member server , and therefore will not have any System Management
> Container created for SMS 2003 . At a result, whichever child domain, after
> schema extension, created their "first" System managment container , will
> have control right to other System Management container that will be created
> later on at each different child domain.
>
> Is this really true ? Is there any support MS article / info that I could
> refer to ?
>
> Any help appreciated.
>
> Jason
>
>
>
-- Check out the SMS Technical FAQ: http://www.microsoft.com/technet/prodtechnol/sms/sms2003/techfaq/default .mspx
- Next message: Tobias Svensson: "SMS_SQL_monitor fails to install"
- Previous message: Kim Oppalfens: "Re: SQL Permissions"
- In reply to: Jason: "Schema and "first" System Management Container"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
