asked on

Windows Server 2008RC

I have a client that wants to have their file server converted to a domain controller. It has been in use for a year now and has substantial data accumulated on it. Minimal users were ever setup on it...what's the best procedure at this point to implement the DC and AD for the new platform? It won't be handling DHCP or Exchange. Thanks in advance...

R--R

You can run dcpromo and promote it as a DC. If you have alreay have a DC at site then this will be a backup DC.

But will it be able to share load of File server as well as DC?

PCWoes

ASKER

Is this where you define the domain with an existing forest? If so how do I define the new DC alongside the existing DC (file server) and log all workstations into the newly established domain vs. workgroup? I tried that yesterday and the domain wasn't accessible...so I reverted all my changes to be back to file server without AD! Quite annoying... :(

ASKER CERTIFIED SOLUTION

Lee W, MVP

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

PCWoes

ASKER

Out of the box it was setup as a file server. No domain setup! So I attempted the dcpromo thinking a simple task as I've read considerably but then found it was identifying the file sever (Server1) as a domain? I then said OK to myself and went to configuration to activate the AD. That's when the problem arose as it it now implies no DC running? So I confused my self with this and told the setup to use existing domain with existing forest (including DNS) and typed in a domain name per config requirement. Then after all the necessary configuration the domain wasn't accessible via workstation request to join? I do have plenty experience on workstation side and file servers so I felt confident enough to make these changes. In existing networks I manage AD and group policies (small scale) for multiple clients. It just confused me yesterday and they had work to get done so as not to hold them back any longer I opted to do what I did and am going back in tomorrow with no one working. I will join their workstations to the domain if I get this setup and there's really only few options to follow. I'm just still puzzled why it implies domain but there isn't one? The AD proved that...

PCWoes

ASKER

After a good nights sleep and pondering my thoughts about this small office configuration I can now maybe be a bit more clear as to what I'm asking for assistance with...

The office is managed by a T1 config with their DHCP and no access to device...only tech support call !
My setup process:

1. Create the "new" DC
2. Use DNS
3. Static IP for Server: 192.168.1.150
4. Gateway IP: 192.168.1.5 (T1 ISP DHCP)
5. Primary DNS server: 192.168.1.150
6. Secondary DNS sever: 8.8.8.8.8 (or ISP DNS) <~~ This is question mark for me
7. Client workstation change Primary DNS to 192.168.1.150
8. Client workstation: Join domain with admin credentials

That's it in a nutshell really...my question is will I have DNS for www access with Secondary DNS config to Public or ISP servers while using Primary DNS server to be Server IP (192.168.1.150). If I have to DHCP enabled on server then I need client support from the T1 ISP to deactivate their's...

leew...I do appreciate your comments at experience level offered in regards to client network but I'm just dealing with one hurdle that's new to me...the actual DC setup of the server. Just one thing I've not done !! I've been fortunate enough to be quick learner for most office server environments that had been previously configured DC. SO AD and Group policies haven't been an issue. Nice learning process actually!