Title: Windows 2003 AD
Guido,
He can do what ever he wants. All I
am saying is that his is going to be modifying the schema on the parent, as
well as, the sub-domain. Why put all that effort into a child domain
where you are not going to get the benefits to the parent domain? Yes,
th
I had a like problem in several situation
I am in Ent Adm and Dom adm and some application doesn't worked.
Applications that worked in folder, that was raising DLL or other
components.
I found that in specific situation WIn2k protect by the 'less permissions'
concept when it look at a multiple p
:o)
Come on Rick think damn you! I need the laugh!
I have a laugh for you though.
Imagine a product that works in a cross realm (cross domain) manner fine for
say modifying distribution lists via the most common client used for it. Now
say you upgrade that product and now, you can no longer do t
glad you fixed it, but this was certainly not the reason... If your account
was in those groups, then you should not have had any issues.
-Original Message-
From: Salandra, Justin A. [mailto:[EMAIL PROTECTED]
Sent: Freitag, 26. September 2003 19:50
To: '[EMAIL PROTECTED]'
Subject: RE: [
Title: Windows 2003 AD
It is neither illogical nor un-safe to add a 2003 domain to
a 2000 forest. As was said, you'll have to prep the schema - but you'll
have to do that anyways to update the existing domains at some point in time. So
read up on the potential schema conflicts and fixes requ
