Re: NT4 BDC to Win2k3 server
From: Don Wilwol (donwilwol_at_yahoo.com)
Date: 03/18/05
- Next message: Joel Kaminsky: "Taking Exchange and Moving into Active Directory as a Member Server Question:"
- Previous message: Mike Culver: "Re: NT4 BDC to Win2k3 server"
- In reply to: Mike Culver: "Re: NT4 BDC to Win2k3 server"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 18 Mar 2005 11:11:10 -0500
Well, if i now understand correctly, you are saying you want to upgrade your
BDC to a w2k3. As long as you still have a PDC, the domain local groups will
remain in the domain. The domain local groups are kept on all domain
controllers.
If this is the case you have a couple of options, the easiest would be to
take it off line (it will need to be connected to its own hub, windows 2003
likes to see a network) run the upgrade, it will install AD. Then run
dcpromo again and delete all references to it. Add it to the domain as a
memeber server.
-- Hope it helps........... dw Don Wilwol Blog - http://spaces.msn.com/members/wilwol/ Web - http://capital.net/~wilwol/dw.htm DonWilwol(REMOVE)@yahoo.com "Mike Culver" <MikeCulver@discussions.microsoft.com> wrote in message news:C25A29D3-7C22-48FB-B83A-1E820A7D4CB0@microsoft.com... > hmmmm..... > Thanks but that article didn't really answer anything for me. > > To be clear - I do not have AD now and I do not want to have AD after I > upgrade the BDC from NT4 svr to Win2k3 svr. I simply want to have the new > Win2k3 server be a member server in the NT4 domain. When this happens I'm > wondering what happens to all of the domain local groups that were used to > secure the file system when it was an NT4 BDC. I know the local groups > will > still be int eh NT4 domain but when the server is a standalone server they > can't be used to secure the file system any longer. > > Once I can get my main file servers to be win2k3 standalone servers in my > NT4 domain I can then concentrate on implementing AD. > > Thanks, > MIKEC > > "Don Wilwol" wrote: > >> had me thinkin there for a minute......they say the mind is the first >> thing >> to go!! :-) >> So I looked it up, Upgrade Windows NT 4.0 BDCs, >> http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/deployguide/en-us/Default.asp?url=/resources/documentation/windowsserv/2003/all/deployguide/en-us/dssbe_upnt_huxa.asp. >> During the operating system upgrade the computer will restart three >> times. >> After the computer restarts for the last time, the Welcome to the Active >> Directory Installation Wizard appears. >> >> I don't think there is any way to back out of this. >> >> You can use admt to tranlate these groups. I think you will have to >> translate then to domain local groups, but you can verify this. >> >> >> -- >> Hope it helps........... >> >> dw >> >> Don Wilwol >> Blog - http://spaces.msn.com/members/wilwol/ >> Web - http://capital.net/~wilwol/dw.htm >> DonWilwol(REMOVE)@yahoo.com >> >> "Mike Culver" <MikeCulver@discussions.microsoft.com> wrote in message >> news:CE8E6D46-09E3-4A8D-BC5E-5C4CBD679B15@microsoft.com... >> > hmmm....I attended a Microsoft TechNet presentation on Upgrading NT4 >> > Domains >> > to AD. I asked the presenter (offline) what would happen when I do >> > this >> > and >> > he said DCPROMO would not run automatically. He also said there is a >> > way >> > to >> > keep the local groups intact for the standalone server. Frankly I >> > think >> > he >> > was wrong on the local group issue and now I'm wondering about the >> > DCPROMO >> > issue. I guess a test environment is my only option to find out for >> > sure. >> > >> > "Don Wilwol" wrote: >> > >> >> The domain local groups will remain domain local groups. You can't >> >> upgrade a >> >> BDC until the PDC is upgraded, then the BDC will become another domain >> >> controller. The only way to make this a member server is upgrade it, >> >> dcpromo >> >> will run automatically and become a DC, then you can run dcpromo again >> >> to >> >> demote it. >> >> >> >> Your only other option is a reg hack (you'll have to google it) to >> >> make >> >> the >> >> upgrade think its already a member server. I'm pretty sure you will >> >> loose >> >> the groups if you try this. >> >> >> >> -- >> >> Hope it helps........... >> >> >> >> dw >> >> >> >> Don Wilwol >> >> Blog - http://spaces.msn.com/members/wilwol/ >> >> Web - http://capital.net/~wilwol/dw.htm >> >> DonWilwol(REMOVE)@yahoo.com >> >> >> >> "MIKEC" <MIKEC@discussions.microsoft.com> wrote in message >> >> news:4203A18F-068F-4F0A-9D36-FADEE30B8A5D@microsoft.com... >> >> >I have an NT4 BDC file server that has extensive use of domain local >> >> >groups >> >> > to secure the file system. When I upgrade this server to Win2k3, >> >> > what >> >> > happens to the file system security that was secured with domain >> >> > local >> >> > groups >> >> > since the new win2k3 server is only a member server? I'm basing >> >> > this >> >> > question on my experience with NT4 member servers inability to >> >> > utilize >> >> > domain >> >> > local groups. >> >> > >> >> > If I can get passed this issue I can upgrade some of my servers.... >> >> >> >> >> >> >> >> >>
- Next message: Joel Kaminsky: "Taking Exchange and Moving into Active Directory as a Member Server Question:"
- Previous message: Mike Culver: "Re: NT4 BDC to Win2k3 server"
- In reply to: Mike Culver: "Re: NT4 BDC to Win2k3 server"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
