Non-authoritative SYSVOL restore (FRS)

 

When you are working in Active Directory environment you may fall into this problem, especially in case where you have many Domain Controllers. Sometimes you may figure out that one or more Domain Controllers are out of date with SYSVOL replication.

Each Domain Controller has its own folder where GPOs and scripts are saved. This folder is located under %WINDIR%SYSVOLdomain (by default, if you changed that location during DC promotion, you need to refer to your own location).

There are 2 folders:

  • Policies where Group Policies are saved (%WINDIR%SYSVOLdomainPolicies)
  • Scripts where logon scripts or other files are saved (%WINDIR%SYSVOLdomainScripts shared as NETLOGON)

If a DC does not replicate SYSVOL you can see that some Group Policies (GPOs) or scripts are not available on DC(s) in SYSVOLdomain folder on particular DC. Another symptom may be that all GPOs are in place but they are not updated.

When you notice one of these behaviors, you would need to do non-authoritative SYSVOL restore which re-deploys SYSVOL data from working Domain Controller (holding PDC Emulator operations master role).

How to be sure if you need non-authoritative SYSVOL restore? There is no simple answer because that depends on the size of your Active Directory and number of Domain Controllers.

When we can decide to start this kind of retore ?

  • one DC out of couple does not replicate SYSVOL
  • a few DCs out of many do not replicate SYSVOL
  • more than few but less than 50% of them do not replicate SYSVOL

above examples are typical scenarios for non-authoritative SYSVOL restore.

Let’s see how you to do that.

First of all, you need to find out which DC or DCs does/do not replicate SYSVOL. Then you have to start SYSVOL restore.

When you see an empty SYSVOL, this may suggest that Domain Controller initialization where not finished after server was promoted. Active Directory database was replicated but SYSVOL was not. In this case, you can simply perform non-authoritative restore and SYSVOL should be replicated.

Empty SYSVOL folder

Empty SYSVOL folder

Another case is when DC, is not up to date with SYSVOL. Some policies are missing and non-authoritative SYSVOL restore would be helpful.

Missing Group Policies under SYSVOL

Missing Group Policies under SYSVOL

When you log on to Domain Controller with PDC Emulator operation master role, you should see that there are more policies than on those faulty Domain Controllers

All Group Policies on DC with PDC Emulator role

So, you can see that those Domain Controllers need SYSVOL restore to have all data up-to-date.

Now, it’s time to play with non-authoritative SYSVOL restore. Log on to the DC which is out of replication with SYSVOL and stop File Replication Service (NtFRS) from command-line/elevated command-line. Type

net stop ntfrs
Stopping File Replication Service

Stopping File Replication Service

Now, you need to change some setting in Windows registry.

Warning! Be careful, do not change other entries than showed in this artcile, you may destroy your server!

You need to open registry editor from run box

Executing registry editor

Executing registry editor

Now, you need to find below key:

HKEY_LOCAL_MACHINESystemCurrentControlSetServicesNtFrsParametersBackup/RestoreProcess at Startup
BurFlags value location

BurFlags value location

and change BurFlags value from 0 to D2 (hexadecimal) by editing it

Changing BurFlags value

Changing BurFlags value

Before you will start FRS service, I would suggest to remove all content from those 2 folders

  • %WINDIR%SYSVOLdomainPolicies
  • %WINDIR%SYSVOLdomainScripts

Note! (by default, if you changed SYSVOL location during DC promotion, you need to refer to your own location)

Warning! When you set up D2 BurFlags value, you need to know that during restoration time, your DC is prevent to be a Domain Controller! So, you need to be careful in locations/Sites where you have only single DC or you are going for authentication over WAN-link!

Now, it’s time to start File Replication Service. Type in command-line

net start ntfrs
Running File Replication Service

Running File Replication Service

When you refresh (F5 key) registry editor, you should see that BurFlgs values has changed back to 0

BurFlags value reset

BurFlags value reset

and you should also check “File Replication Service” event log. Please check if event id 13565 appeared. That means, server has initiated SYSVOL replication and you need to wait a while. You have to refresh event log from time to time and check if these event IDs appeared:

  • 13553
  • 13516

when you can see them, SYSVOL replication is over and your Domain Controller is up-to-date.

SYSVOL re-initialized

SYSVOL re-initialized

SYSVOL re-initialized

SYSVOL re-initialized

Verify if SYSVOL share is available on your Domain Controller, type in command-line

net share
SYSVOL share verification

SYSVOL share verification

go to %WINDIR%SYSVOLdomainPolicies and check if data is replicated

SYSVOL content verification

SYSVOL content verification

That’s all! Everything you need to do is to repeat all those steps on each Domain Controller which does not replicate SYSVOL volume.

Done!

Next part >>>

Author: Krzysztof Pytko

Advertising new time server in domain environment

 

I can see on different forums that people are asking what happens when they transfer PDC Emulator Operation Master role to another Domain Controller. This is really important question as PDC Emulator is responsible for time management in domain environment. When you do not advertise new time server you might notice some time differences between your domain controllers and domain member servers.

This article shows the procedure on Windows Server 2012 R2 how to accomplish that properly but is also suitable for all earlier operating systems.

All the time when you transfer PDC Emulator role to another Domain Controller, you need to change configuration on both servers:

  • on previous PDC Emulator role holder
  • on the new PDC Emulator role holder

this will advertise new time server in your domain environment and you will prevent future issues because of that. The most often scenario of transferring PDC Emulator FSMO role to another DC is when you are promoting new Domain Controller based on newer operating system i.e:

  • promoting new Windows Server 2008/2008R2 DC in Windows Server 2003/2008 DC environment
  • promoting new Windows Server 2012/2012R2 DC in Windows Server 2003/2008/2008R2/2012 environment

in this particular case you need to do following things:

Log on directly or over Remote Desktop connection to the new PDC Emulator FSMO role holder and run elevated command prompt

Running elevated command prompt

Running elevated command prompt

Now, you need to configure external time server source from which you will synchronize time settings. This may be another device in your network (like Cisco ACS server) or any reliable external NTP server. The list of reliable NTP servers you may find on NTP Pool website

In this example I will use external NTP pool server for my region (Poland)

You need to use IP address or DNS name of NTP server during Domain Controller configuration, so if you want to use IP address then the first step is to ping DNS name and write down an IP address of the server

  • 95.158.95.123

this is the IP address resolved from pl.pool.ntp.org

Important! Before you start reconfiguring servers, please ensure if UDP/123 port is allowed on your router/firewall because NTP is using this particular port to synchronize time settings!

Now, in elevated command-line you need to run this command

w32tm.exe /config /manualpeerlist:95.158.95.123 /syncfromflags:manual /reliable:yes /update
Configuring NTP source on new PDC Emulator FSMO role holder

Configuring NTP source on new PDC Emulator FSMO role holder

or

w32tm.exe /config /manualpeerlist:pl.pool.ntp.org /syncfromflags:manual /reliable:yes /update
Configuring NTP source on new PDC Emulator FSMO role holder

Configuring NTP source on new PDC Emulator FSMO role holder

where /manualpeerlist:IPAddress or /manualpeerlist:DNSServerName is an NTP server to use in your environment

and restart Windows Time service

net stop w32time
net start w32time
Restarting Windows Time service

Restarting Windows Time service

Now, your new PDC Emulator FSMO role holder will synchronize time with specified NTP time source.

The last step is to reconfigure the old PDC Emulator Operation Master role holder to not advertise it as time server and pull time information from new PDC Emulator. To do that log on directly or over Remote Desktop connection to the server and type in command prompt (2003)/elevated command prompt (all newer OSes)

w32tm.exe /config /syncfromflags:domhier /reliable:no /update
Reconfiguring old PDC Emulator FSMO role holder

Reconfiguring old PDC Emulator FSMO role holder

and you need to also restart Windows Time service to complete whole operation

net stop w32time
net start w32time
Restarting Windows Time service

Restarting Windows Time service

That’s all! You have reconfigured your environment and advertised new time server in a domain.

Author: Krzysztof Pytko

How to re-register time services on a server

 

This time, I would like to show you, how you can simply fix an issue with time services on your server. That method helps in 90% of cases with time issues.

Sometimes, you may notice a server is out of time in your domain environment. The first method you should follow is re-registering time services on that server. When it fails then much more deep investigation might be needed.

So, let’s check how we can re-register time services on a server.

Windows Server 2003

Log on to the server directly or over Remote Desktop connection and run command prompt by typing in run box

cmd.exe
Running command promt

Running command promt

and provide a command to stop “Windows Time services” by entering

net stop w32time
Stopping Windows Time services

Stopping Windows Time services

or stop the service from GUI console

services.msc
Running "Services" console

Running “Services” console

Now, search for “Windows Time” service which should be started

Searching "Windows Time" service

Searching “Windows Time” service

Double click on it and you’ll see its details, like:

  • service name (w32time)
  • display name (Windows Time)
  • description
  • Path to executable file
  • Startup type (Automatic by default)
  • service status (Started)
Service details

Service details

To stop the service, simply click on “Stop” button and wait a while

Stopping service

Stopping service

Service is stopping

Service is stopping

you should see that service is stopped

Service is stopped

Service is stopped

Now, you can start time services re-registering procedure. The command you need to use is called

w32tm.exe

It is responsible for time management in a domain or on a single server in a workgroup.

First of all, you have to unregister time service by typing

w32tm.exe /unregister
Unregistering time service

Unregistering time service

and now, register service using /register parameter

w32tm.exe /register
Registering time service

Registering time service

and the last, final step requires to start Windows Time service in command prompt

net start w32time
Starting Windows Time service

Starting Windows Time service

or you may do that using GUI console as well. Just click on “Start” button and wait a while for service startup

Starting Windows Time service from GUI console

Starting Windows Time service from GUI console

Service is starting

Service is starting

That’s all. Re-registration procedure has been done. From now, you should see that time is accurate on the server. It comes from your Domain Controller or from other NTP server (depends on network configuration).

If not then you’ll need to deeply investigate the case.

But this is not a part of this article. I’ll try to post another article on troubleshooting services.

Windows Server 2008/2008R2

The procedure required for Windows Time service re-registration is EXACTLY the same as for Windows Server 2003. The only one difference is that you need to execute command prompt in elevated mode as administrator. The rest steps are the same.

Log on to the server directly or over Remote Desktop connection and run elevated command prompt from “Start” menu. Go to “All Programs -> Accessories” and click right mouse button on “Command prompt“. Select “Run as administrator” from the context menu

Running elevated command prompt

Running elevated command prompt

provide a command to stop “Windows Time” service by entering

net stop w32time
Stopping Windows Time service in command-line

Stopping Windows Time service in command-line

or use the same GUI console for that, as it was for Windows Server 2003

services.msc
Running services GUI console

Running services GUI console

and search for “Windows Time” service on the list

Searching for Windows Time service on the list

Searching for Windows Time service on the list

Double click on it and you’ll see its details, like:

  • service name (w32time)
  • display name (Windows Time)
  • description
  • path to executable file
  • startup type (Manual by default) -> startup type is changed in comparison to Windows Server 2003
  • service status (Started)
Service details

Service details

To stop the service, simply click on “Stop” button and wait a while

Stopping Windows Time service from GUI console

Stopping Windows Time service from GUI console

Service is stopping

Service is stopping

after a while, you should see that service is stopped

Service is stopped

Service is stopped

Now, you can start time services re-registering procedure. The command you need to use is called

w32tm.exe

It is responsible for time management in a domain or on a single server in a workgroup.

First of all, you have to unregister time service by typing

w32tm.exe /unregister
Unregistering time service

Unregistering time service

and now, register service using /register parameter

w32tm.exe /register
Registering time service

Registering time service

and the last, final step requires to start Windows Time service in command prompt

net start w32time
Starting Windows Time service from command prompt

Starting Windows Time service from command prompt

or you may do that using GUI console as well. Just click on “Start” button and wait a while for service startup

Starting Windows Time service from GUI console

Starting Windows Time service from GUI console

Service is starting

Service is starting

That’s all. Re-registration procedure has been done. From now, you should see that time is accurate on the server. It comes from your Domain Controller or from other NTP server (depends on network configuration).

If not then you’ll need to deeply investigate the case.

But this is not a part of this article. I’ll try to post another article on troubleshooting services.

Windows Server 2012/2012R2

The procedure required for Windows Time service re-registration is EXACTLY the same as for Windows Server 2003 and Windows Server 2008/2008R2. The only one difference is that you need to execute command prompt in elevated mode as administrator. The rest steps are the same.

Log on to the server directly or over Remote Desktop connection and run elevated command prompt from “Start” tile. Move mouse cursor to the left bottom corner and wait until “Start” tile appears (Windows Server 2012) or do it directly on it (Windows Server 2012 R2). Click on it right mouse buttond and select “Command Prompt (Admin)

Running elevated command prompt

Running elevated command prompt

provide a command to stop “Windows Time” service by entering

net stop w32time
Stopping Windows Time service from command prompt

Stopping Windows Time service from command prompt

or use the same GUI console for that, as it was for Windows Server 2003/2008/2008R2

services.msc
Running services GUI console

Running services GUI console

and search for “Windows Time” service on the list

Searching Windows Time service on the list

Searching Windows Time service on the list

Double click on it and you’ll see its details, like:

  • service name (w32time)
  • display name (Windows Time)
  • description
  • path to executable file
  • startup type (Manual Trigger Start by default) -> startup type is changed in comparison to Windows Server 2003/2008/2008R2
  • service status (Running)
Service details

Service details

To stop the service, simply click on “Stop” button and wait a while

Stopping Windows Time service from GUI console

Stopping Windows Time service from GUI console

Service is stopping

Service is stopping

after a while, you should see that service is stopped

Service is stopped

Service is stopped

Now, you can start time services re-registering procedure. The command you need to use is called

w32tm.exe

It is responsible for time management in a domain or on a single server in a workgroup.

First of all, you have to unregister time service by typing

w32tm.exe /unregister
Unregistering Windows Time service

Unregistering Windows Time service

and now, register service using /register parameter

w32tm.exe /register
Registering time service

Registering time service

and the last, final step requires to start Windows Time service in command prompt

net start w32time
Starting Windows Time service from command prompt

Starting Windows Time service from command prompt

or you may do that using GUI console as well. Just click on “Start” button and wait a while for service startup

Starting service from GUI console

Starting service from GUI console

Service is starting

Service is starting

That’s all. Re-registration procedure has been done. From now, you should see that time is accurate on the server. It comes from your Domain Controller or from other NTP server (depends on network configuration).

If not then you’ll need to deeply investigate the case.

But this is not a part of this article. I’ll try to post another article on troubleshooting services.

Author: Krzysztof Pytko

Windows Server 2012/2012R2 education resources

 

When you plan to take some Windows Server 2012/2012 R2 education, you may check following resources which may help you in gaining an experience in those technologies. This is probably only part of available resources but might be helpful on your education road.

First of all, you could download evaluation versions from official Microsoft web site

There is also full free version of Microsoft Hyper-V Server. You may use it without any restrictions or limitations for test purposes and in production environment(s):

More information about new features implemented in those Microsoft products are available at Technet:

There are a lot of great Windows Server 2012/2012R2 courses at Microsoft Virtual Academy, i.e

and many, many more at Microsoft Virtual Academy

You have also possibility to learn using free Microsoft Virtual Labs for Windows Server 2012 where you are able to test case studies prepared by them.

I hope this short extract of free education resources will help you in gaining knowledge and preparing to Microsoft official exams.

Author: Krzysztof Pytko

Windows Server 2008R2 in-place upgrade to Windows Server 2012/2012R2

 

Previous article showed that in-place upgrade from Windows Server 2008 to Windows Server 2012 is possible only if it has Hyper-V role configured and it is impossible to do that on Windows Server 2012 R2.

Situation looks much better when you plan to do in-place upgrade of Windows Server 2008 R2 into Windows Server 2012/2012R2. This is supported but requires some administrator’s attention before server will be upgraded.

Below you can find some hints for that process.

First of all, you need to evaluate if software installed on your Windows Server 2008 R2 is compatible and supported on Windows Server 2012/2012R2. When you find any incompaticle software you need to

  • upgrade it to supported version before OS upgrade (recommended action)
  • uninstall it from the server before OS upgrade
  • leave it as is but remember that Windows Server after in-place upgrade may not function properly

Important! Some applications may be compatible with Windows Server 2012/2012R2 but their version might not be sufficient to support full application features. You need to evaluate it also before OS in-place upgrade.

When all appropriate steps were taken, are able to start in-place upgrade. To do that follow procedure listed below

Start Windows Server 2012/2012R2 setup wizard from DVD media

Windows setup wizard

Windows Server 2012 setup wizard

Windows Server 2012 R2 setup wizard

Windows Server 2012 R2 setup wizard

Wait for Windows to copy necessary files to the server

Setup is copying necessary files

Setup is copying necessary files

Setup is starting

Setup is starting

When those files were copied to local hard drive, you should go on-line and install all new Windows Server 2008 R2 updates (recommended)

Note! The Internet connection will be required!

Updating Windows Server 2008 before in-place ugrade

Updating Windows Server 2008 R2 before in-place ugrade

Wait for system update to finish the process

Windows Server 2008 R2 on-line update

Windows Server 2008 R2 on-line update

At this moment you have to provide valid Windows Server 2012/2012R2 product key to start installation

Provide valid Windows Server 2012/2012R2 product key

Provide valid Windows Server 2012/2012R2 product key

When system is updated, you’ll see a screen where you need to choose appropriate Windows Server 2012 edition to which you want to upgrade Windows Server 2008 R2

Select Windows Server 2012 edition to install

Select Windows Server 2012 edition to install

Accept license terms and go to the next step

License terms

License terms

Now, everything is ready to start in-place upgrade. Click on “Upgrade: Install Windows and keep files, settings, and applications

In-place upgrade initiation

In-place upgrade initiation

Review applications compatibility report and if there are no errors, continue the installation

Compatibility report

Compatibility report

Compatibility report

Compatibility report

Windows Server upgrade will start

Windows Server 2012 upgrade progress

Windows Server 2012 upgrade progress

During the upgrade process, several actions will be executed like:

  • collecting files
  • collecting settings
  • collecting applications
Windows Server 2012 upgrade progress

Windows Server 2012 upgrade progress

In the next step, Windows Server will install its own files

Windows Server 2012 upgrade progress

Windows Server 2012 upgrade progress

Your server will be restarted when all files were extracted. During system restart, you have short time to decide if you wish to continue in-place upgrade or you want to roll back to the previous Windows Server 2008 R2 OS

Windows Server 2012 upgrade progress

Windows Server 2012 upgrade progress

Windows Server 2012 starts preparing itself for devices configuration

Windows Server 2012 upgrade progress

Windows Server 2012 upgrade progress

Windows Server 2012 upgrade progress

Windows Server 2012 upgrade progress

The server will be restarted to finalize settings

Windows Server 2012 upgrade progress

Windows Server 2012 upgrade progress

and finally, logon screen will appear. That means the in-place upgrade process has been finished.

Windows Server 2012/2012R2 logon screen

Windows Server 2012/2012R2 logon screen

That’s all!

<<< Previous part

Author: Krzysztof Pytko

Windows Server 2008 in-place upgrade to Windows Server 2012/2012R2

 

This topic is about Windows Server 2008 in-place upgrade to Windows Server 2012/2012R2. Article will be really short because there is no possibility to do in-place upgrade of Windows Server 2008 to Windows Server 2012/2012R2 when it has no Hyper-V role configured.

The only one supported in-place upgarde is possible when your Windows Server 2008 has Hyper-V role configured.

Windows Server 2008 in-place upgrade to Windows Server 2012

When you insert Windows Server 2012 installation media on Windows Server 2008 and you’ll run setup.exe or autostart will do that, you will be able to start in-place installation process

Windows setup wizard

Windows setup wizard

Click on “Install now” button to initiate setup. Wizard will copy necessary files to start in-place upgrade process

Setup is copying necessary files

Setup is copying necessary files

Setup is starting

Setup is starting

Now, you should go on-line and install the lates Windows Server 2008 updates before you will continu in-place upgrade

Note! The Internet connection is required!

Updating Windows Server 2008 before in-place ugrade

Updating Windows Server 2008 before in-place ugrade

When all updates are applied you need to provide product key for this installation

Provide valid Windows Server 2012/2012R2 product key

Provide valid Windows Server 2012 product key

after that choose Windows Server 2012 edition to which you want to upgrade current Windows Server 2008

Select Windows Server 2012 edition to install

Select Windows Server 2012 edition to install

Accept license terms and go to the next step

License terms

License terms

Now, you can initiate in-place upgrade installation. Choose “Upgrade: Install Windows and keep files,settings, and applications

In-place upgrade initiation

In-place upgrade initiation

When you click to start in-place upgrade, setup wizard starts to check if there is any incompatible software on Windows Server 2008. In this case that process is skipped because of unsupported scenario. You will notice an error stating that you cannot do in-place upgrade to Windows Server 2012 (GUI or non-GUI installation) if no Hyper-V role is configured on the current server.

No in-place upgrade support for GUI edition of Windows Server 2012

No in-place upgrade support for GUI edition of Windows Server 2012

No in-place upgrade support for non-GUI edition of Windows Server 2012

No in-place upgrade support for non-GUI edition of Windows Server 2012

and that’s all in this case. Unfortunatelly, you need to do clean Windows Server 2012 installation.

Windows Server 2008 in-place upgrade to Windows Server 2012 R2

In this scenario, in-place upgrade path is shorter because when you start Windows Server 2012 R2 setup wizard, you get an error that this is not possible at all. Does not matter if current Windows Server 2008 has Hyper-V role configured or not. In-place upgrade to Windows Server 2012 R2 is not supported at all.
When you try to do that, you see an error similar to that below

Windows Server 2012 R2 setup wizard error

Windows Server 2012 R2 setup wizard error

That’s all, you need to use workaround in this case. First of all you have to perform in-place upgrade from Windows Server 2008 to Windows Server 2008 R2 and then to Windows Server 2012

Next part >>>

Author: Krzysztof Pytko

Microsoft Technology Questions – Question 1

 

Finally, I found some time to start something new on my blog 🙂

This time, I’ve decided to start a serie of Microsoft Technology Questions (MTQ).  Its form may be familiar for many of you who did take a Microsoft official exam. This form is only one common thing with official Microsoft exam. I will defintively NOT publish official questions from the real exams here. So, those people who are looking for exact questions for Microsoft exams will be disappointed!

I’ll try to publish in a monthly basis one Microsoft technology related question invented by me. The question will be prepared by me, based on my experience and you won’t find it anywhere before it will be published here 🙂 So, do not search the Internet to find an answer 😉

After two weeks, I will update particular post with an answer, containing detailed explanation. I would like to start sharing knowledge with you using this form.

I hope you would love this idea and we will meet here regularly to learn something new! 🙂

Please feel free to discuss this idea and comment the question. I would love to hear if the idea is worth developing or not.

So, let’s start with the first question. The answer will be provided in two weeks from now.

QUESTION

You are working in TESTENV company as Domain Administrator. There is a single forest, single domain environment.
All Domain Controllers are running on Windows Server 2003 R2 Enterprise x64 and they are physical machines.
FSMO roles are split. Both, forest and domain functional levels are set up to Windows Server 2003.

You need to promote two new Domain Controllers using the least administrative effort. One based on Windows Server 2008R2 and one based on Windows Server 2012.

How would you do that?
More than one answer is appropriate, choose the most suitable to the above requirements.

ANSWERS

A)
– Run adprep from Windows Server 2008R2 media
– Promote new Windows Server 2008R2 Domain Controller
– Run adprep from Windows Server 2012 media
– Promote new Windows Server 2012 Domain Controller
B)
– Run adprep from Windows Server 2012 media
– Promote Windows Server 2012 Domain Controller
– Run adprep from Windows Server 2008R2 media
– Promote Windows Server 2008R2 Domain Controller
C)
– Promote Windows Server 2012 Domain Controller
– Promote Windows Server 2008R2 Domain Controller
D)
– Run adprep from Windows Server 2008R2 media
– Promote Windows Server 2008R2 Domain Controller
– Decommission all Windows Server 2003R2 Domain Controllers
– Run adprep from Windows Server 2012 media
– Promote Windows Server 2012 Domain Controller
E)
– Run adprep from Windows Server 2008R2 media
– Promote Windows Server 2008R2 Domain Controller
– Promote Windows Server 2012 Domain Controller

Author: Krzysztof Pytko

Decommissioning Windows Server 2012 R2 Domain Controller

 

When you wish to do this action, please be informed that nothing has changed from the previous (Windows Server 2012) operating system release. That means, all those steps from Windows Server 2012 are still valid for Windows Server 2012 R2.

I would not rewrite that article again, and if you are interested please read the article about Decommissioning Windows Server 2012 Domain Controller on my blog.

I hope you would find it useful.

Author: Krzysztof Pytko

Adding additional Domain Controller (Windows Server 2012 R2)

 

When you wish to do this action, please be informed that nothing has changed from the previous (Windows Server 2012) operating system release. That means, all those steps from Windows Server 2012 are still valid for Windows Server 2012 R2.

I would not rewrite that article again, and if you are interested please read the article about Adding additional Domain Controller (Windows Server 2012) on my blog.

I hope you would find it useful.

Author: Krzysztof Pytko

Adding first Windows Server 2012 R2 Domain Controller within Windows 2003/2008/2008R2/2012 network

 

When you wish to do this action, please be informed that nothing has changed from the previous (Windows Server 2012) operating system release. That means, all those steps from Windows Server 2012 are still valid for Windows Server 2012 R2.

I would not rewrite that article again, and if you are interested please read the article about Adding first Windows Server 2012 Domain Controller within Windows 2003/2008/2008R2 network on my blog.

I hope you would find it useful.

Author: Krzysztof Pytko