Posts Tagged ‘Windows Server 2012’

How to: Windows 2012 Server deploy remote domain controllers using Server Manager – part II of II

A few weeks ago I’ve posted an article about how to remotely Install a domain controller within Windows 2012 Server using the Server Manager.

How to: Windows 2012 Server Deploy remote domain controllers using Server Manager – Part I of II

Since Windows 2012 Server, creating a new domain controller is much eassier then ever before. There is another option to create a new domain controller….Yes, using Windows PowerShell!!

As you can see in part I of the post, there are two domain controllers. I have installed a clean Windows 2012 Server within my labenvironment, called Server2.

1.) Logon to Server1 with the Administrator account
2.) Open Windows PowerShell
3.) Type the following command:
Install-WindowsFeature -Name AD-Domain-Services -ComputerName Server2
4.) After the Windows feature is installed succesfully, type the following command:
Invoke-Command –ComputerName Server2 –ScriptBlock {Import-Module ADDSDeployment;Install-ADDSDomainController –NoGlobalCatalog:$False –CreateDNSDelegation:$False –Credential (Get-Credential) –CriticalReplicationOnly:$False –DatabasePath “C:\Windows\NTDS” –DomainName “” –InstallDNS:$True –LogPath “C:\Windows\NTDS” –NoRebootOnCompletion:$False –SiteName “Default-First-Site-Name” –SysVolPath “C:\Windows\SysVol” }
When prompted for credentials, enter the username and password of your domain administrator account!

In my labenvironment, I have used the following parameters:
-ComputerName, this is the name of the new domain controller
-NoGlobalCatalog:$False, the new domain controller becomes also an Global Catalog Server
-CreateNDSDelegation:$False, there are no ohter DNS servers available for DNS delegation
-Creadential(Get-Credential), before executing the command, there will be an popup asking your admin crerdentials
-CriticalReplicationOnly:$False, this entry specifies whether the installation operation performs only important replication before a restart and then skips the noncritical and potentially lengthy part of replication. The noncritical replication occurs after the role installation is complete, and the computer restarts
-Databasepath, the location of the ADDS database (NTDS.DIT)
-DomainName, specifies the fully qualified domain name of your domain
-InstallDNS:$True, the new domain controllers becomes also an DNS server
-LogPath, this is the path of the fully qualified, non-UNC directory on a hard disk on the local computer that will  host the AD DS log files.
-NoRebootOnCompletion:$False, there will be no reboot at the end of the installation
-SiteName, this is the name of your Active Directory site where the new domain controller becomes a member of
-SysVolPath, this folder contains all content replicated to the other domain controller (NETLOGON and SYSVOL directories)
5.) After executing the commands above, and the installation has finished, the new domain controller becomes vissible in your Active Directory environment
6.) All you have to do now is waiting for the next Active Directory replication, so all your domain controllers are synchronized





How to: Windows 2012 Server deploy remote domain controllers using Server Manager – part I of II

A great new feature whitin Windows 2012 Server is the possibility to manage servers remote through the Windows Server Manager. In part one of this blogpost, I’m going to deploy a new domain controller to my existing domain in my lab environment through the GUI. In part two of the blogpost, I’m going to deploy again a new domain controller. But now I’m going to use Microsoft Powershell.

I already installed two clean Windows 2012 Servers with the right IP configuration. The servers are added to the Windows Server Manager within my first domain controller, so we’ve the possibility to manage this servers! As you can see, in the begin there’s only one domain controller available.

1.) Login to the existing domain controller of your domain
2.) Open the Server Manager
3.) Navigate to All Servers
4.) Select server SERVER1
5.) Select Manager – Add Roles and Features
6.) Click Next
7.) Select Role-based or feature-based installation
8.) Select server SERVER1
9.) Select server role Active Directory Domain Services and click Next
10.) Click Add Features to install the right Windows features to manage your Active Directory environment
11.) In the confirmation screen, click Install
This will install the server role and features only, not configuring!
12.) After the installation succeeded succesfully, click the red flag on top of the screen
13.) Navigate to Post-deployment Configuration and click Promote this server to a domain controller
14.) Supply the right credentials and click Next
15.) Type the Directory Service Restore Mode (DSRM) password and click Next
16.) In the review screen, you can save the Powershell script to perform this actions automatically the next time.
17.) After the configuration is finished, you’ll see the new domain controller within:
Active Directory Users and Computers
Active Directory Sites and Services








How to: Windows 2012 switch from GUI to Core and from Core to GUI

When you install Windows 2012 Server, you’ve two options to install. The first one is the Core version, the second one is the graphical version (GUI). In the previous version, Windows Server 2008, it was also possible! There is one mayer difference in Windows 2012 Server. You’ve the possibility to change between the Core edition and graphical interface and back without installing the whole server again!

In a few steps you can transform your fully graphical version of Windows 2012 Server to only a black command line box! 😉 Let’s have a look.

1.) Install a Windows 2012 Server with the GUI version
2.) Open Powershell
3.) Type the following command:
Get-WindowsFeature *gui*. As you can see, there’re two Windows feature.
Graphical Management Tools and Infrastructure (Server-Gui-Mgmt-Infra)
Server Graphical Shell (Server-Gui-Shell)
4.) Type the following command to uninstall the GUI:
Get-WindowsFeature *gui* | Remove-WindowsFeature
5.) After restarting the server, you don’t have the GUI anymore
6.) Open Powershell
7.) Type the following command to install the GUI:
Get-WindowsFeature *gui* | Install-WindowsFeature
8.) After restarting the server, the GUI is back again.






Big, bigger, biggest…with Windows Server 2012

During launch of Windows Server 2012, Microsoft has doubled the number of VM’s per cluster: going up from 4000 to 8000 since the last announcement at RTM. Windows Server 2012 cluster scalability goes up to 8000 VMs!! 🙂

Updated eBook Introducing Windows Server 2012 RTM Edition

Mitch Tulloch and the Windows Server team have released a new updated version of the FREE e-Book for IT professionals: Introducing Windows Server 2012 RTM Edition. This book is a great way to get quickly skilled up on all the new improvements in this latest Windows Server – one of the most ambitious releases of Windows Server for IT Pros since Active Directory was released in Windows Server 2000! In this 256-page eBook, you’ll find 5 chapters of detailed technical content covering the following key improvements to building a Private Cloud at your shop with Windows Server 2012:

All you have to do is tweet about this free eBook.

Altaro Hyper-V Backup v3.5 Launched with Full Support for Windows Server 2012

Altaro just launched Altaro Hyper-V Backup v3.5! The first backup solution with full support for Windows Server 2012!!

Full details below:

  • Windows Server 2012 Support, including support for VHDX files.
  • Windows 2012: support for backup and restore of VMs located on network paths.
  • Windows 2012: support for Volume Shadow Copies of SMB3.0 network paths.
  • Windows 2012: support for CSV3.0 and scale-out CSV file shares.
  • New and improved Metro-Style User Interface.

Download the PDF with full details about Altaro Backup v3.5. Also read the productreview written a copple of weeks ago.

Windows Server 2012 Hyper-V Component Architecture Poster

Yesterday Microsoft has published a new version of the Hyper-V Component Architecture Poster. You can download the poster here.

An update is available for Windows 7 and Windows Server 2008 R2 KMS hosts to support Windows 8 and Windows Server 2012

This update extends the Key Management Service (KMS) for Windows 7 and Windows Server 2008 R2 to allow enterprise licensing of Windows 8 and of Windows Server 2012. KMS provides support for the following KMS client activations:

  • Windows Server 2008 R2 and Windows Server 2008 R2 Service Pack 1 (SP1)
  • Windows Server 2008 and Windows Server 2008 Service Pack 2 (SP2)
  • Windows 8
  • Windows Server 2012
  • Windows 7 and Windows 7 Service Pack 1 (SP1)
  • Windows Vista and Windows Vista Service Pack 2 (SP2)

Key Management Service (KMS) uses a KMS host key to activate KMS on a KMS host, and to establish a local activation service in your environment. This update extends support for KMS to provide activation for Windows 8 and for Windows Server 2012.

Download the hotfix here.