Skip to main content
The Managed Service Accounts (MSA) was introduced in Windows Server 2008 R2 to automatically manage (change) passwords of service accounts. Using MSA, you can considerably reduce the risk of system accounts running system services being compromised. MSA has one major problem which is the usage of such service account only on one computer. It means that MSA Service Accounts cannot work with cluster or NLB services, which operate simultaneously on multiple servers and use the same account and password. To fix this, Microsoft added the feature of Group Managed Service Accounts (gMSA) to Windows Server 2012.
To create a gMSA, we should follow the steps given below −
Step 1 − Create the KDS Root Key. This is used by the KDS service on DC to generate passwords.
KDS Service
To use the key immediately in the test environment, you can run the PowerShell command −
Add-KdsRootKey –EffectiveTime ((get-date).addhours(-10)) 
To check whether it creates successfully or not, we run the PowerShell command −
Get-KdsRootKey 
Step 2 − To create and configure gMSA → Open the Powershell terminal and type −
New – ADServiceAccount – name gmsa1 – DNSHostNamedc1.example.com – PrincipalsAllowedToRetrieveManagedPassword "gmsa1Group"
In which,
  • gmsa1 is the name of the gMSA account to be created.
  • dc1.example.com is the DNS server Name.
  • gmsa1Group is the active directory group which includes all systems that have to be used. This group should be created before in the Groups.
To check it, Go to → Server Manager → Tools → Active Directory Users and Computers → Managed Service Accounts.
Managed Service Accounts
Step 3 − To install gMAs on a server → open PowerShell terminal and type in the following commands −
  • Install − ADServiceAccount – Identity gmsa1
  • Test − ADServiceAccount gmsa1
The result should come “True” after running the second command, as shown in the screenshot given below.
True
Step 4 − Go to service properties, specify that the service will be run with a gMSA account. In the This account box in the Log on tab type the name of the service account. At the end of the name use symbol $, the password need not to be specified. After the changes are saved, the service has to be restarted.
Log On
The account will get the “Log On as a Service” and the password will be retrieved automatically.

Comments

Popular posts from this blog

HaydarOrac

Windows Server 2012 codenamed Windows Server 8 is the most recent version of the operating system from Microsoft regarding server management. But it is not the last one, as the last one is Windows Server 2016. Officially it was released on August 1st, 2012 and is being sold as a commercial version only. Improvements in Windows Server 2012 The major Improvements on this version are as follows − It is ready to be integrated with cloud systems and it still can maintain the classic features of local datacenters as a result  Hyper-V Virtualization  has new features  Hyper-v replicas , it allows you to create virtual machines replications between clusters and storage systems. The  Storage migration  virtual disks can be moved to different physical storages, Virtual machine snapshots, virtual machines can be deleted from the Hyper-v and also from the virtual disks and it can be used directly without the need to shut down the virtual machine. The  Cor...
To manage DNS, we have to create a primary Zone because by default, there are no zones in order to manage the records. Step 1  − To manage DNS, go to Server Manager → Tools → DNS → Right click on “Forward Lookup Zone” → New Zone. Step 2  − Select “Primary Zone” and then click Next. Step 3  − Enter the name of the primary Zone for which you want to manage the records. Step 4  − Select “Create a new file with this filename” option. Step 5  − If you want to update the record of this zone manually, you have to select “Do not allow dynamic Updates”, as shown in the following screenshot. Step 6  − Click the Finish button.