Add a 2nd 2012 r2 server to a 2012 r2 domain

Hi All:
I have a new 2012 r2 server configured with AD & DNS.  This is our primary AD server.  I have a second 2012 r2 server that I want to join to this domain, but I do not want AD services on this device (it is a file and application server).

I am used to adding a machine using the "change settings" feature under the system properties and using the wizard.  It seems there is no wizard in the 2012 r2.  How do I go about adding this 2nd server (dataserver) to the established domain running under (adserver)?  I did go into change setting on the dataserver and change the domain to be the same as the adserver, but there are kerbos errors when I try to manage the dataserver from the adserver.  

Any suggestions or steps to configure this properly?

I have the AD server @ running AD & DNS
The data server is @ with a fixed DNS of
The admin names and passwords are the same on both
the 2012 r2 is licensed and activated on both

I would like the AD to be able to manage the dataserver via the server manager console and for them to be connected correctly.  
The dataserver will handle all the user files, data files and programs while the ADserver will authenticate, manage and provide permissions to the folders and shares on the data server.  

Help would be appreciated.

Thank you
Marshall KassOwnerAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Leroy LuffHead of IT & DIgitalCommented:
Very simple - Just add the server to the domain like a normal computer.
Cliff GaliherCommented:
Open server manager.  In the left pane, change to "local" (usually the second option down)

In the main pane is the computer name and workgroup/domain name. There are clickable links there to change these. When you change to a domain name, it will attempt to join the existing domain just like computer settings used to do. Same basic process, just a slightly different location. Same rules apply too. DNS needs to be working. Firewall rules need to allow it. You need to have AD admin privileges to create the new computer object in AD.  And of course the server will want to reboot.  If you did that and are still seeing errors, chances are you have some misconfiguration in group policy or in your firewall. Just as you could before, you can always switch back to workgroup, delete the computer object from AD,  and rejoin to rebuild the object and create a new trust.  2012  (and R2) are not that different in this regard. Just the UI has changed a little.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Marshall KassOwnerAuthor Commented:
It was too simple.  I had actually done what you suggested but I guess I did not give it the time to propagate.   Thank you

Leroy's solution was not exactly correct as I normally would add a pc or server using the wizard, which does not exist in 2012 r2.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.