Re: Upgrade Schema to R2.



If i have sufficients permissions, can i run the schema update from the DC
at our branch office OR it has to be updated from the

Schema Master physically by inserting the CD2 there ?


You have to be a member of the schema admin group and you must run adprep on
the schema master for your domain.

If i upgrade the Schema from any of the DC, will it create any problems
from
the rest of our DCs at different sites ?

You can't update the schema from "any DC" it must be done on the schema
master for your domain. That information is then replicated to the rest of
the DCs in your domain. Since the updated schema is replicated to the rest
of the DCs in the domain this has the potential to cause major problems.
Have I heard of users having problems when the schema update is replicated
to the rest of the DCs? No.

You should always have a current backup and of course test before doing it
in production. This test could be as simple as installing Win 2k3 SP1 on two
"boxes" (they really don't need to be servers) in a separate domain. Update
the schema master using adprep from the second disk of the R2 set and let it
replicate and see what happens.


hth
DDS

"abckid" <abckid@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6F5B709F-F1EF-4CD9-9BE4-2C6454877F59@xxxxxxxxxxxxxxxx
Hi,

We have Windows Server 2003 Standard SP1 domain. All the domain
controllers
are same. The schema version of the Schema Master and all

DCs is 30.

Now we have installed a Windows Server 2003 R2 as a member server to the
domain. It holds the File and Print server roles. I am

trying to use the Deploy Printer with GPO from the Printer Management in
the
R2 server.
As per link -
http://www.windowsnetworking.com/articles_tutorials/Deploying-Printers-Group-Policy-Windows-R2.html
But i get the below error when i click to apply it.

Deploying printer connection '\\server\Printer' to per machine GPO 'Deploy
Printers' failed. The specified directory service

attribute or value does not exist

I think i would have to upgrade the schema to R2 (Version 31).

If i have to upgrade it to R2, it should be done from CD2 on the Schema
Master.

Now the Schema Master is physically at our Central Office. We have
installed
the new R2 server at one of our branch office. I

would like to clear my doubts as

If i have sufficients permissions, can i run the schema update from the DC
at our branch office OR it has to be updated from the

Schema Master physically by inserting the CD2 there ?

If i upgrade the Schema from any of the DC, will it create any problems
from
the rest of our DCs at different sites ?

Please guide.

Thanks,

abc.


.



Relevant Pages

  • Re: replacing a sms server
    ... to keep from the previous SMS server. ... domain computers that have the sms client installed. ... this is the safest way of extending your schema. ... Locate the server that is the schema master ...
    (microsoft.public.sms.setup)
  • Re: adprep /forestprep failure
    ... Find out if the existing Win 2000 DC is the schema master. ... We raised the functional level to Windows ... we ran DCPROMO and it reverted to a member server with no errors. ...
    (microsoft.public.windows.server.active_directory)
  • Re: adprep /forestprep failure
    ... so there is no other server for spserver01 to replicate to. ... When I run the Active Directory Schema ... > promote it to be a DC, transfer the Schema master role to it, and then> try ... >>> The schema master did not complete a replication cycle after the ...
    (microsoft.public.windows.server.active_directory)
  • RE: replacing a sms server
    ... server and then for some reason I promoted it to a domain controller, ... It is advised to follow the procedure below, before any schema modifications ... not just sms 2003 schema extentions. ... Locate the server that is the schema master ...
    (microsoft.public.sms.setup)
  • RE: 2000 to 2003 domain controller upgrade
    ... The ADPREP /FORESTPREP must be executed on the Schema Master. ... |Subject: RE: 2000 to 2003 domain controller upgrade ... Produced By Microsoft MimeOLE V5.50.4910.0300 ...
    (microsoft.public.windows.server.migration)