Testing /forestprep and /domainprep

Is there any way to test to effect of expanding the Active Directory
schema before actually doing so.

I have a heterogeneous network, consisting of Windows and Linux boxes,
all of which belong to our Windows 2003 AD domain. For the Linux boxes,
all RedHat 4 & 5 of various sub-versions, both 32- and 64-bit, I used
Winbind and Samba to add the computer to the domain, with PAM modules
configured to allow our users to use their Active Directory usernames to
log into these Linux boxes.
At this point, I'm thinking about upgrading the network, as the first
step of our eventual upgrade from 2003/XP to 2008/7, but I'm scared that
by messing with the schema, I'll ruin the Single-sign-on with the Linux
boxes that makes things so convenient.
I've tried recreating things in a virtual environment, but the schema
obviously is not going to be the same as my real production environment.
Is there any way I can test, or run some sort of analyzer that will
point out the possible pitfalls of expanding my schema before actually
doing so?

Max

"Atomax" wrote:

> Is there any way to test to effect of expanding the Active Directory
> schema before actually doing so.
>
> I have a heterogeneous network, consisting of Windows and Linux boxes,
> all of which belong to our Windows 2003 AD domain. For the Linux boxes,
> all RedHat 4 & 5 of various sub-versions, both 32- and 64-bit, I used
> Winbind and Samba to add the computer to the domain, with PAM modules
> configured to allow our users to use their Active Directory usernames to
> log into these Linux boxes.
> At this point, I'm thinking about upgrading the network, as the first
> step of our eventual upgrade from 2003/XP to 2008/7, but I'm scared that
> by messing with the schema, I'll ruin the Single-sign-on with the Linux
> boxes that makes things so convenient.
> I've tried recreating things in a virtual environment, but the schema
> obviously is not going to be the same as my real production environment.
> Is there any way I can test, or run some sort of analyzer that will
> point out the possible pitfalls of expanding my schema before actually
> doing so?
>
> Max
> .
>

"Atomax" wrote:

> Is there any way to test to effect of expanding the Active Directory
> schema before actually doing so.
>
> I have a heterogeneous network, consisting of Windows and Linux boxes,
> all of which belong to our Windows 2003 AD domain. For the Linux boxes,
> all RedHat 4 & 5 of various sub-versions, both 32- and 64-bit, I used
> Winbind and Samba to add the computer to the domain, with PAM modules
> configured to allow our users to use their Active Directory usernames to
> log into these Linux boxes.
> At this point, I'm thinking about upgrading the network, as the first
> step of our eventual upgrade from 2003/XP to 2008/7, but I'm scared that
> by messing with the schema, I'll ruin the Single-sign-on with the Linux
> boxes that makes things so convenient.
> I've tried recreating things in a virtual environment, but the schema
> obviously is not going to be the same as my real production environment.
> Is there any way I can test, or run some sort of analyzer that will
> point out the possible pitfalls of expanding my schema before actually
> doing so?
>
> Max
> .
>

Hello Atomax,

The schema upgrade is an irreversable step. Normally it works or not with
an error message, never have seen a crash during the upgrade. You can create
a test network from your production according to the following articles,
for testing:
http://www.pbbergs.com/windows/articles/TestDomain.html

http://blogs.dirteam.com/blogs/jorge...11/19/107.aspx

http://blogs.dirteam.com/blogs/jorge...11/19/105.aspx

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Is there any way to test to effect of expanding the Active Directory
> schema before actually doing so.
>
> I have a heterogeneous network, consisting of Windows and Linux boxes,
> all of which belong to our Windows 2003 AD domain. For the Linux
> boxes,
> all RedHat 4 & 5 of various sub-versions, both 32- and 64-bit, I used
> Winbind and Samba to add the computer to the domain, with PAM modules
> configured to allow our users to use their Active Directory usernames
> to
> log into these Linux boxes.
> At this point, I'm thinking about upgrading the network, as the first
> step of our eventual upgrade from 2003/XP to 2008/7, but I'm scared
> that
> by messing with the schema, I'll ruin the Single-sign-on with the
> Linux
> boxes that makes things so convenient.
> I've tried recreating things in a virtual environment, but the schema
> obviously is not going to be the same as my real production
> environment.
> Is there any way I can test, or run some sort of analyzer that will
> point out the possible pitfalls of expanding my schema before actually
> doing so?
> Max
>

Extending the Schema is irreverisible but I would be shocked if it impacted
your Linux connection. I don't think they will care, but just test it prior
to the upgrade and it sounds like you have or are in the process already.

--
Paul Bergson
MVP - Directory Services
MCITP - Enterprise Administrator
MCTS, MCT, MCSE, MCSA, MCP, Security +, BS CSci
2008, Vista, 2003, 2000 (Early Achiever), NT4
Microsoft's Thrive IT Pro of the Month - June 2009

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewGroups. This
posting is provided "AS IS" with no warranties and confers no rights.
"Atomax" <atomax@nospam> wrote in message
news:...
> Is there any way to test to effect of expanding the Active Directory
> schema before actually doing so.
>
> I have a heterogeneous network, consisting of Windows and Linux boxes, all
> of which belong to our Windows 2003 AD domain. For the Linux boxes, all
> RedHat 4 & 5 of various sub-versions, both 32- and 64-bit, I used Winbind
> and Samba to add the computer to the domain, with PAM modules configured
> to allow our users to use their Active Directory usernames to log into
> these Linux boxes.
> At this point, I'm thinking about upgrading the network, as the first step
> of our eventual upgrade from 2003/XP to 2008/7, but I'm scared that by
> messing with the schema, I'll ruin the Single-sign-on with the Linux boxes
> that makes things so convenient.
> I've tried recreating things in a virtual environment, but the schema
> obviously is not going to be the same as my real production environment.
> Is there any way I can test, or run some sort of analyzer that will point
> out the possible pitfalls of expanding my schema before actually doing so?
>
> Max

Services for Unix installed?

You could stand up an isolated DC from your production enviroment using one
of several means to get a more complete test enviroment using the exact
schema.



Paul Bergson [MVP-DS] wrote:
> Extending the Schema is irreverisible but I would be shocked if it
> impacted your Linux connection. I don't think they will care, but
> just test it prior to the upgrade and it sounds like you have or are
> in the process already.
>
> Please no e-mails, any questions should be posted in the NewGroups. This
> posting is provided "AS IS" with no warranties and confers no
> rights. "Atomax" <atomax@nospam> wrote in message
> news:...
>> Is there any way to test to effect of expanding the Active Directory
>> schema before actually doing so.
>>
>> I have a heterogeneous network, consisting of Windows and Linux
>> boxes, all of which belong to our Windows 2003 AD domain. For the
>> Linux boxes, all RedHat 4 & 5 of various sub-versions, both 32- and
>> 64-bit, I used Winbind and Samba to add the computer to the domain,
>> with PAM modules configured to allow our users to use their Active
>> Directory usernames to log into these Linux boxes.
>> At this point, I'm thinking about upgrading the network, as the
>> first step of our eventual upgrade from 2003/XP to 2008/7, but I'm
>> scared that by messing with the schema, I'll ruin the Single-sign-on
>> with the Linux boxes that makes things so convenient.
>> I've tried recreating things in a virtual environment, but the schema
>> obviously is not going to be the same as my real production
>> environment. Is there any way I can test, or run some sort of
>> analyzer that will point out the possible pitfalls of expanding my
>> schema before actually doing so? Max

--
/kj