Upgrading Domain Controller Questions

Hello, we currently have 2 domain controllers in our environment, both with Server 2003 R2. We are looking to upgrade them one at a time to 2008 R2 but I have some questions.
Here's the environment:
Server 1 (the one we are going to upgrade first):
Server 2003 R2
Domain Controller
DHCP Server
DNS Server
Server 2 (we will be upgrading this in the near future but not just yet):
Server 2003 R2
Domain Controller
DHCP Server
DNS Server
File Server with most of the company data
We also have DNS replication set up between the two servers.
My questions:
Will we run into any issues having two domain controllers with different Operating Systems?
We would like for the domain controllers to keep the same names and IP's. Any issues with that?
How will we stop, then re-setup DNS replication between the two servers?
Any other 'gotcha's' we should be aware of?
Dan Chandler-Klein

I don't see any reason why not keeping old name and IP.
Before upgrading make sure AD has no issues:
look at the event viewer, run DCDiag, replication runs clean (repadmin /showrepl) etc.
OS has no warning/errors.
Not must but I would move the FSMO roles to another DC before demote.
Make sure applications installed on the new DC's (AV\Backup agents etc.) support Windows 2008 R2 OS.
Make sure all your network applications in your environment support working with Windows 2008 R2 DC - I recommend test it in lab first.
Make sure that the DC you are about to demote not holding CA role.
Most important:
Make sure you successfully demote the old DC and no records left in DNS.
I'm not agree with evrimicelli about DC's naming and I wouldn't go for CNAME record - this can get you in many troubles in the future.
after demote the old DC, I would rename it or remove it from the domain, than you can rename the new server with old Dc name and promote it to DC with old DCs' IP address.
I didn't understand the question about DNS replication.
What kind of DNS zone do host? if its AD integrated (and thats what you should have), you don't need to configure any replication, AD integrated DNS zone replicate as part of AD replication between your two DC's.
Please take a moment to Vote as Helpful and/or Mark as Answer where applicable. Thanks.

Similar Messages

Upgrading domain controller from Server 2003 to Server 2012 R2, how will this affect Exchange 2010?

Hi All,
Below is an AD and Server related post that I had submitted last week. While I did receive valid responses for the post, I was advised to check with the Exchange forums for the Exchange related question in
bold. All responses are welcomed, thank you!
===========================================================
Hi All,
I am hoping that someone could perhaps provide some insight on this topic as I apparently can't seem to google the best answer.
I have recently acquired an AD domain that is running on a 2003 domain controller. I have been tasked with upgrading our existing domain structure with 2012 R2 domain controllers for our main office and remote offices.
The domain name is company.mynetwork.com, and it is the default first site name. We have multiple offices throughout the US with their own domain controllers (i.e. FL.mynetwork.com, NY.mynetwork.com, DC.mynetwork.com, etc.).
Our main office, and default first site has one domain controller (mynetdc1) running Server 2003 R2. It is also our only DNS server for the main office. It also has an additional domain controller called mynetmaster3 which is running Server 2003.
Both mynetdc1 & mynetmaster3 NTDS settings show them as global catalogs under AD Sites & Services. Both servers are also in the AD Domain Controllers OU, along with all of the other satellite office domain controllers.
Additionally, our main office is running Exchange 2010 with the latest service pack. My questions are:
Can we demote and retire mynetmaster3, then replace mynetdc1 with a newly promoted 2012 R2 global catalog domain controller without harming anything in the domain tree and interrupting connectivity to the other offices (this of course goes without saying
after a 4 hour maintenance window to get the task completed has passed)?
Should we upgrade the satellite offices first after raising the functional level for mynetdc1, or should we do the opposite (upgrade main office, then satellite offices)?
MS Exchange 2010 is heavily dependent on AD, what effect will this entire project have on our email server? What steps should we take beforehand to ensure email continuity?
Finally, is there any shame for a Net Admin to suggest that we hire an implementation specialist for this task? :)
Any advice would be greatly appreciated!

As long as the operating system on your Exchange servers isn't upgraded, and as long as you do the Active Directory domain and forest updates in the supported manner (the following link is a good example -
http://blogs.msmvps.com/mweber/2012/07/30/upgrading-an-active-directory-domain-from-windows-server-2003-or-windows-server-2003-r2-to-windows-server-2012/), Exchange will happily operate behind the scenes. Exchange 2010 is supported in the Windows
forests (domain controllers, domain functional level and forest functional level) mentioned in the following TechNet article, which includes both Windows 2003 and Windows 2012.
http://technet.microsoft.com/en-us/library/ff728623(v=exchg.150).aspx
Due to this, you should be good as long as you do the domain controller, domain, and forest upgrades carefully. Oh, and before you start each step, get a nice backup.

Windows Server Primary & Secondary Domain Controller Question

lulzchicken wrote:
Right now the DHCP is assigning 192.168.200.1 (DNS server) and 8.8.8.8 (Google's DNS) as DNS servers for each client. I don't necessarilly want to change these assignment settings,Yes, you do. This is absolutely the worst thing you can ever do with DNS. More details why here -> Ramblings of a Sysadmin: How to do DNS correctly
Primary and secondary DNS should ALWAYS be internal.
Your DNS Servers should use FORWARDERS go go out to google. That's the only place that should see google DNS servers in your environment.

Hi everyone, thank you for taking the time to listen.
I have successfully implemented an Active Directory setup using a Primary DC and a Secondary DC with Windows Server 2012 R2.
EL1 is my PDC and EL2 is my BDC.
Active Directory is in sync among the two Domain Controllers. Here is my question:
If I were to have a policy (Group Policy) that sets the wallpaper of each client machine to whatever is in the "\\EL1\Wallpaper\wp.jpg" - what would happen if I were to have that Domain Controller fail? That directory is no longer available due to the outage - even though the Backup Domain Controller will still be pushing out the policy (pointing to the down server).
My idea was to have that directory replicated on the Backup Domain Controller, "\\EL2\Wallpaper\wp.jpg" however - the policy will still be looking for the file in the Primary Domain...
This topic first appeared in the Spiceworks Community

How to upgrade Domain Controller 2008 to 2012 on New Server

Hi All,
We are planning to upgrade our domain controller and exchange server 2008 to 2012 R2, so can anyone please suggest what step should be taken first. we have new server machine we are planning to install Windows 2012 R2 and create a additional domain controller
of our existing domain 2008 then transfer the FSMO roles to this server to act as a primary. after successful migration we will upgrade our exchange 2008 to 2012. please advice is there any problem to do this way.
Thanks
Agha

I was just curious about the same thing. However, I am running 32bit version of server 2008 and want to move the server 2012 r2. This will be on a machine with new hardware and all. Am just curious though if it is possible to migrate some of the
domain as to not to have to replicate everything?
Directory Services doesn't really care what version of the OS you are using. You cannot do an in-place upgrade from a 32bit box to a 64bit box.
You'll need to make your new R2 server, install AD, move the FSMOs, and demote your 2008 32bit box.
What WOULDN'T you want to replicate? That's not how AD works. It's a multimaster enviroment where ALL DCs have the same information. You can't choose which objects replicate. To do that, you'll need to clean up your AD.
Good luck.
- Chris Ream -
**Remember, if you find a post that is helpful, or is the answer, please mark it appropriately.**

Decommissioning a domain controller - Possible Scenarios

Hello,
I am in the process of upgrading my window server 2003 to 2012 R2.
I have introduced a swing DC,installed 2012 on it,ensured that replication is occuring between the two and succesffully transfered the roles from the old DC to the new temporary 2012 DC.
Refer to this thread for the procedures in use
http://social.technet.microsoft.com/Forums/en-US/1c742612-ff44-4521-bb68-53b17b287fae/upgrade-domain-controller-from-windows-server-2003-sp2-to-windows-server-2008-or-2012?forum=winservergen
Now i intend to decommission the old 2003 server , and to a fresh reinstallation of 2012 in it,then once i ensure replication has occured, transfer back the roles and decommission the swing DC
Both server are global catalogs..
My question is this, Do i just do a fresh reinstallation of the 2012 on the old server 2003 without first demoting it? or do i demote it ,test and then install 2012 on it...
Since the servers are GC both,is there a possibility that when i demote the old DC the DNS,AD details that had replicated dissapears?
What any other cautions should i check?
Thanks

Hello,
demotion is ALWAYS required except you do in-place upgrades which is not recommended on DCs.
If you don't do a correct demotion, also removing it from AD UC after removing the server complete from the network, checking DNS zones and zone properties and Name server tabs and removing the DC from AD sites and services (not done during demotion),
you may run into trouble when installing a new DC with the same name and also have always replication errors as the AD database doesn't know that the DC is removed correct.
With a not correct demoted DC AD metadata cleanup is required.
BEFORE demoting the old OS machine ASSURE that the enw DC has also the NETLOGON and SYSVOL share available and they contain the same content as on the old DC.
Also the new DC MUST become DNS server if you don't have any domain member server that handles DNS zones.
Best regards
Meinolf Weber
MVP, MCP, MCTS
Microsoft MVP - Directory Services
My Blog: http://msmvps.com/blogs/mweber/
Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.

Upgrade a Domain Controller running Windows Server 2012 Datacenter Eval

Hello,
because I couldn't wait for Server 2012 to show up on Dreamspark Premium I installed the Datacenter evaluation version after I found this blog
post telling me, I could simply enter my key when I get it to upgrade to the full version.
After entering the command I get notified that "Changing this Windows edition is not supported online for a domain controller.".
The TechNet article for upgrading evaluation versions states the following:
"If the server is a domain controller, see http://technet.microsoft.com/library/hh472160.aspx for important steps to follow before proceeding."
and taking me to an article for installing/uninstalling ADDS without further comments.
Simply typing "slui 3" and entering my key states that I have to enter an eval key.
My question is: Is there a painless way to upgrade my 2012 DC without losing my AD config?
Regards,
Hans

Hi,
Please refer to the following Microsoft TechNet article to confirm if the steps of converting to full retail version are correct.
Evaluation Versions and Upgrade Options for Windows Server 2012
http://technet.microsoft.com/en-us/library/jj574204.aspx
If the warning persists, it means Windows Server 2012 Domain Controller does not support such convert. If so, please install another Windows Server 2012 full retail version or
convert to full retail version and then promote it to an additional Domain Controller for this domain. After that, transfer FSMOs to this new Domain Controller and demote the original Domain Controller.
Regards,
Arthur Li
TechNet Community Support

¿Is it possible to upgrade from SCCM 2012 a domain controller in Windows Server 2008 R2 TO 2012 R2?

Hi all.
I want to know if is it possible to upgrade a domain controller from Windows Server 2008 r2 to 2012 r2 installing from SCCM 2012.
Thanks.
Regards.

Hi all.
I want to know if is it possible to upgrade a domain controller from Windows Server 2008 r2 to 2012 r2 installing from SCCM 2012.
Thanks.
Regards.
Anything is possible if you can script it. You could create a task sequence to do the following (with scripts):
1. Demote 2008R2 DC to member server
2. Remove 2008R2 member server from domain
3. Build new 2012R2 member server and join to domain
4. Promote 2012R2 member server to DC
You can do this. However, why would you? Just because you can doesn't mean you should. In my opinion it's more trouble and testing than it's worth. How many times would you need to do this?
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

How to test domain controller on upgraded Win Server 2008 R2

The windows team recently upgraded the development environment for the domain controller from 2003 to Windows 2008 R2 and I am to test the Idm functionality on this upgraded version. Our current configuration is that the DC and Idm gateway runs on different machines. To test this new DC, i want to install the idm gateway on that server and run some onboarding and termination test cases just to make sure if the AD connection is working on the upgraded DC. But i am getting ’Input/output error’ when i try to install the service and from the documentation it says 'The most common cause of this is that you do not have rights to work with this service.'. The server admin tried installing the gateway with his id as well and it failed. He tested installing in on the 2003 version of DC and it worked, so its not a matter of permission (i think..)...
Does anyone have any better idea on how to test an upgrade of a DC from version 2003 to 2008 R2? Any help in this matter is appreciated. We are running Idm 8.1 on a Windows platform and an upgrade to OW 8.1.1. Patch 2 is also in the works..
Thanks in advance.

I may have found a workaround. Can you try to change the "compatibility mode" in 2008 R2 to "Windows XP SP3" and see if it will install?
Admittedly I have not done this myself so I'm not entirely sure where or how it's done, but I have confirmation it resolves the issue from others who have faced it.

A question and out CA 'domain controller' templates, and kerbros/KDC in general

Hello All
Can someone please help me with the following question. This may be two questions (so if you think I have to post separately please let me know).
I was reading an MS article called "Active Directory Domain Controllers and Certificate auto-enrolment" which was very helpful but through up some questions too.
for example the article talks about a 'template' called 'Directory E-mail Replication' what is this? in other words we have all heard of MS Exchange for corporate email, but the name of this template seems to suggest 'Domain Controllers' send e-mails to
reach other? (over and above their normal AD replication) or is this template used for sending AD replication data via SMTP rather than RPC (which is something I have never heard of). Can someone please explain the purpose of this template, thanks very much.
Also I want to understand the relationship (if any) between these Domain Controller PKI templates and Kerberos in general (can someone point me to a white paper of good blog article)
For example my understanding at the moment if Kerberos is basically a 'symmetric' key encryption system where by the KDC (Key Distribution Center) take care of administering all these symmetric key pairs, is this basic premise
correct?
I understand (at a very basic level) to concept of Kerberos TGT and TST (ticket granting ticket and ticket service ticket) and the fact the client cannot read the contents of either of these (rather the KDC is the trust anchor and deals with all the encryption
and description of the keys to provide/proof identity authentication, and the client simply presents these tickets)
Hopefully the above is correct (or on the right lines), what I do not understand is how this (Kerberos/KDC) relates to DC's and their 'Domain Controller' templates or how these Domain Controllers use the certificates generated from these templates for encryption
(I presume to encrypt the AD sync traffic, but isn't this done via Kerberos).
Also AD CA is optional component therefore my logic suggests there should be no relation to these Domain Controller templates and Kerberos
As you can see I have some fundermental gaps in my knowleague and would really appreciate someone helping me out here
Thanks very much
AAnotherUser__
AAnotherUser__

Re the template Directory E-mail Replication.
Yes, you are right - these are only used for (optional) AD replication via SMTP, and yes this is rather uncommon. I have only encountered this type of replication in a few environments with very specific - and historically grown - firewall and trust requirements.
Re Kerberos and certificates:
My favorite white paper is this:
Windows Vista Smart Card Infrastructure. See especially the details of how Kerberos is used with smart cards as depicted in Figure 16 and the text below.
When users use smartcards to logon to their computers they authenticate to DCs and DCs authenticate to them. So DCs also need certificates.
See
RFC 4556 for details of how public key cryptography is used to protect the Kerberos protocol.
So in summary certificates are used for authentication and encryption.
You are right that otherwise - if you don't use smart card logon for users - DC certificates are optional and not needed to do default Kerberos authentication.
Another reason DC certificates are often deployed is for allowing LDAP browsers and other management tools to connect to AD via LDAPs.
Elke

Domain Controller Upgrade 2008R2 to 2012R2

Hi
One of my customers has an environment with 3 domain controllers. Primary DC resides on premise as well as the secondary. One more Additional DC's resides on DR site and are all running Windows Server 2008 R2.
We have now decided to upgrade all of them to 2012R2 and therefore I would like to know what are the concerns we need to be aware of?What sort of problems we may face or experience?and also best practice methodologies to perform the upgrade?
Thanks

Hi,
Based on my experience, CA is not recommend to install on a DC. I recommend you to back up CA and then remove the CA role from the current DC, add the CA role
on a member server and restore the CA database on that member server.
In addition, I suggest adding a new Windows Server 2012 R2 into the domain and promote it to a DC instead of an in-place upgrade. Then you can transfer the FSMO and
DHCP services to the new server, deactivate the DHCP scope on the old DC and turn on DHCP on the new DC. After all the DHCP clients receive IP addresses from the new DHCP server, then you can demote the old DC.
For more detailed information, you can refer to the links below：
AD CS Migration: Migrating the Certification Authority
Migrating a 2003 Domain Controller with DCHP to 2012R2 (Similar for Windows Server
2008 R2)
Best regards,
Susie

Question about adding Windows 2012 R2 Domain Controller, into a native Windows 2008 R2 single forest domain

I current have a two server domain, both Windows 2008 R2 and fully updated. The two servers are on subnet 10.0.1.0 /24
- Windows 2008 R2 Server A: 10.0.1.1 (DC, GC, FSMO, DNS)
- Windows 2008 R2 Server B: 10.0.1.2 (DC, GC)
AD Domain: COMPANY.LOCAL
I have a second connected subnet, 192.168.1.0 /24) which is routed to the 10.0.1.0/24 subnet and I would like to install a Windows 2012 R2 server onto a server on that subnet and make it a domain controller with AD-Integrated DNS and DHCP for the 192.168.1.0
/24 subnet.
- Windows 2012 R2 Server C: 192.168.1.1
What are the proper progression steps, in order to bring up the Windows 2012 R2 server and then add it to my COMPANY.LOCAL domain and then promote it do a DC/GC/AD-Integrated DNS server? Are they anything like the following:
1. Install Windows 2012 R2 server (Server C)
2. Point Windows 2012 R2 server DNS servers at Server's A and B
3. Perform AD prep to extend AD schema to support Windows 2012 R2 domain controllers
4. Promote Windows 2012 R2 server to domain controller (install local DNS service on Server C, during this step)
* Question: Will Windows automatically create a DNS zone for the Windows 2012 R2 subnet (192.168.1.0/24) AND also include the DNS zone from the previous Windows 2008 R2 domain (10.0.1.0 /24)? Or will I need to add the 10.0.1.0 /24 zone to the DNS
server on Server C, even though the DNS from the Windows 2008 R2 domain is AD integrated?

Hi,
Regarding the issue here, please take a look into below articles:
System Requirements and Installation Information for Windows Server 2012 R2
http://technet.microsoft.com/en-us/library/dn303418.aspx
Release Notes: Important Issues in Windows Server 2012 R2
http://technet.microsoft.com/en-us/library/dn387077.aspx
Install a Replica Windows Server 2012 Domain Controller in an Existing Domain (Level 200)
http://technet.microsoft.com/en-us/library/jj574134.aspx
Here is an example for promoting Windows Server 2012 to a DC, see:
Step-by-Step Guide for Setting Up A Windows Server 2012 Domain Controller
http://social.technet.microsoft.com/wiki/contents/articles/12370.step-by-step-guide-for-setting-up-a-windows-server-2012-domain-controller.aspx
As the server is promoted to a DC, DNS Zones will be replicated and synchronized to it automatically whenever the new one is added to an AD DS domain, bascially there is no special need to add zones, for more information, please see:
Understanding Active Directory Domain Services Integration
http://technet.microsoft.com/en-us/library/cc726034.aspx
Hope this may help
Best regards
Michael
If you have any feedback on our support, please click
here.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Upgrading windows server 2003 domain controller to windows server 2008

Hello friedns :
We have a company with about 2000 users , and two windows server 2003 domain controllers , one of them acts as a primary domain controller , and the other acts as secondary domain controller , all the FSMO s are on the primary DC ,we have decided to upgrade all of our servers from windows server 2003 to windows server 2008 , the first step is to upgrade the domain controllers to windows server 2008 , our domain controllers are so sensitive and has to be active 24 hours a day , i have stress upgrading it to windows server 2008 , what is the best solution to upgrade it with no risk ?
( i have an opinion but i am not sure and i dont have any guide about it , i want to install a windows server 2008 and promote it as an additional domain controller to the windows server 2003 DC and the transfer all the FSMOs to it , and then promote the first domain controller !!! is that possible ? if yes , is there any guide about it? )
If there is a guide available for it please let me know . (Specially if there is a tip & trick)
thank you guys.
Network is my LOVE

Hi,
This TechNet online article might be helpful for you.
How to Upgrade Domain Controllers to Windows Server 2008 or Windows Server 2008 R2
http://technet.microsoft.com/en-us/library/ee522994(WS.10).aspx
For your convenience, I have list some general steps for your reference.
Since the following operation have potential damage to Active Directory database, it is highly suggested that you'd better perform a full backup of Active Directory (System State) firstly. Also it is better to test the following procedure in a similar lab environment first.
General Steps:
=============
1. Verify the new server's TCP/IP configuration has been pointed to the current DNS server.
2. Make the new server become a member server of the current Windows Server 2003 domain first.
3. Upgrade the Windows Server 2003 forest schema to Windows Server 2008 schema with the "adprep /forestprep" command on old server.
Please run the "adprep.exe /forestprep" command from the Windows Server 2008 installation disk on the schema master. To do this, insert the Windows Server 2008 installation disk, and then type the following command:
Drive:\sources\ADPREP\adprep.exe /forestprep
4. Upgrade the Windows 2003 domain schema with the "adprep /domainprep" command on old server.
Please run the "adprep.exe /domainprep" command from the Windows Server 2008 installation disk on the infrastructure master. To do this, insert the Windows Server 2008 installation disk, and then type the following command:
Drive:\sources\ADPREP \adprep.exe /domainprep
5. Insert Windows Server 2008 Installation Disc in the new server.
6. Run "dcpromo" on new server to promote it as an additional domain controller in existing Windows 2003 domain, afterwards you may verify the installation of Active Directory.
Please refer to:
How to Verify an Active Directory Installation in Windows Server 2003
http://support.microsoft.com/kb/816106
7. Verify the new server's TCP/IP configuration has been pointed to current DNS server.
8. Enable Global Catalog on new server and manually Check Replication Topology and afterwards manually trigger replication (Replicate Now) to synchronize Active Directory database between 2 replicas.
Please note: It will some time to replicate GC between DC, please wait some time with patience.
9. Disable Global Catalog on the old DC.
10. Transfer all the FSMO roles from the old DC to the new DC.
Please refer to:
How to view and transfer FSMO roles in Windows Server 2003
http://support.microsoft.com/kb/324801
11. Verify that the old DNS Server Zone type is Active Directory-Integrated. If not, please refer to:
How To: Convert DNS Primary Server to Active Directory Integrated
http://support.microsoft.com/kb/816101
Note: Active Directory Integrated-Zone is available only if DNS server is a domain controller.
12. Install DNS component on new server and configure it as a new DNS Server (Active Directory Integrated-Zone is preferred). All the DNS configuration should be replicated to the new DNS server with Active Directory Replication.
13. Make all the clients change TCP/IP configuration to point to new server as DNS.
14. You may configure TCP/IP on all the clients, or adjust DHCP scope settings to make them use the new DNS server.
Please note: It is a good practice to make the old DC offline for several days and check whether everything works normally with the new server online. If so, you may let the old DC online and run DCPROMO to demote it.
Hope it helps.
Regards,
Wilson Jia
This posting is provided "AS IS" with no warranties, and confers no rights.

Domain controller upgrade in Exchange Environment

We have an existing 2003 Server Environment and Exchange server 2003 coexistence with Exchange server 2010 with DAG setup. We have recently decided to move to a windows server 2012 standard Environment. How do I promote the new windows Server 2012 std
to DC and remove the 2003 Server from the Environment. My users are currently using the old 2003 DC to logon.
in brief
We have windows 2003 enterprise + sp2 Domain controller (holding DNS as well) and Exchange server 2003 Entp + Exchange server 2010 running in Coexistence with DAG.
We have decided to remove the 2003 Server from the Environment and go with Windows 2012 Standard OS. I would know to know the what will be the impact on Exchange server environment if any ?
please suggest right path with less downtime.Mailing service should not be affected.
TheAtulA

Simply migrate the remaining mailboxes to your Exchange Server 2010 and then you can decommission your Exchange Server 2003. More if you ask them here: https://social.technet.microsoft.com/Forums/exchange/en-US/home?forum=exchangesvrgenerallegacy
Once done, you can upgrade to ADDS 2012 and introduce your first DC running Windows Server 2012. Please note that your Exchange Servers should be SP2 or later to support your new DC. More details here: http://blogs.technet.com/b/rmilne/archive/2013/09/17/exchange-support-for-windows-server-2012-r2.aspx
This posting is provided AS IS with no warranties or guarantees , and confers no rights.
Ahmed MALEK
My Website Link
My Linkedin Profile
My MVP Profile

Upgrading from 2012 Standard Evaluation (Domain Controller) to 2012 R2 Standard Full

Hello,
My company recently wanted to move from a Linux domain controller to a Windows system. We downloaded and installed Server 2012 Standard evaluation, set up a domain, and made sure things were working well. Now, we want to purchase the full copy, but we see
that 2012 R2 is now out.
We would like to purchase R2, but somehow do an in-place upgrade. From what I can tell, we have a few hurdles:
*No upgrade path from 2012 Evaluation to 2012 R2 Full
*Cannot upgrade evaluation with DC role to full
What would be the recommended course of action to take here? We do have an unused machine here that could serve as a secondary domain controller that currently has no OS installed, but we don't want to buy 2 server licenses at this time if we can help it.
Thanks,
B
Braden

As far as i know you can't upgrade an eval to a full install on 2012.
you could build a new server using server 2012 R2 depends on how you normally purchase software you might be able to install without likening initially as you get a grace period. Build a new DC in the existing domain and then demote the current DC, then
rebuild it using 2012 R2, licence it and then install it back as a DC and demote the other one you created.
Regards,
Denis Cooper
MCITP EA - MCT
Help keep the forums tidy, if this has helped please mark it as an answer
My Blog
LinkedIn:
actually i believe you might be able to
http://technet.microsoft.com/en-us/library/dn303416.aspx
Upgrade means
moving from your existing operating system release to a more recent release, while staying on the same hardware. For example, if your server is running Windows Server 2012, you can upgrade it to Windows Server 2012 R2. You can upgrade from an evaluation version
of the operating system to a retail version, from an older retail version to a newer version, or, in some cases, from a volume-licensed edition of the operating system to an ordinary retail edition.
Regards,
Denis Cooper
MCITP EA - MCT
Help keep the forums tidy, if this has helped please mark it as an answer
My Blog
LinkedIn:

Domain Controller Authentication Fail Since Upgrade

When I boot my Mac Pro at the office, the network's domain controller prompts me for my domain login. Since upgrading to Yosemite, the domain controller rejects my credentials. However, I can go to "Connect To Server" and browser the entire network despite the domain controller not authenticating me as a user.
To summarize, since switching to Yosemite:
1. Can't login to the network when I submit my credentials
2. Can browse the network without my credentials
My theory is that the only reason #2 works is because #1 is working but Yosemite is just mistakenly telling me I wasn't authenticated.
So what's the problem you may ask if I can browse the network anyway? The problem is that I can't mount any of the network drives to my desktop because Yosemite doesn't think I'm authenticated to do such. If I can solve this authentication problem, then I should get my mounted network drives back.
Thanks in advance.

Hi,
TEST: Basic (Basc)
Warning: Adapter 00:0D:3A:00:0D:01 has dynamic IP address
(can be a misconfiguration)
Do you have any NIC conifgured to get dynamic IP on your DC which is having issue? If yes, please disable that NIC. Also, please provide me the result of the below
1) On your DC which is having issue, run "ipconfig /all"
2) Repadmin /showrepl
Thanks,
Umesh.S.K
Thanks, there is only 1 nic card. It is getting a dhcp address because this is an AZURE Hyper-v machine and I have set an IP reservation for it. I have no way to hardcode the IP because it gets shut off/on all the time
C:\Users\Administrator>repadmin /showrepl
Repadmin: running command /showrepl against full DC localhost
Default-First-Site-Name\GP2010-A
DSA Options: IS_GC
Site Options: (none)
DSA object GUID: 007c755c-f56c-4e51-a211-fd4431f63927
DSA invocationID: 007c755c-f56c-4e51-a211-fd4431f63927

Upgrading Domain Controller Questions

Similar Messages

Maybe you are looking for