This article will helps you to upgrade from Windows Server 2012 to Windows Server 2016. If you need to keep the same hardware & all the server roles you have already setup without flattening the server, you will want to do an in-place upgrade. In-place upgrades permit you to go from an older OS to a newer one while keeping your settings, server roles, & data intact.
To upgrade to Windows Server 2019, use this topic first to upgrade to Windows Server 2016, and then upgrade windows server 2016 to 2019.
Before you begin your in-place upgrade
Before you began upgrade Windows Server, we suggest that you collect some information from your server, for diagnostic and troubleshooting purposes. Through this intelligence is purpose for use only if your upgrade fails, please make sure that you have store the information somewhere that you can get to it off of your device.
To collect your info
1- Run a command prompt, go to c:\Windows\system32, and then type systeminfo.exe. Copy, paste & store the resulting system information somewhere off of your device.
2- Type ipconfig /all, and then copy & paste the resulting configuration information into the same location as above.
After you have collected all the Windows Server-related information, we highly recommend that you take backup of your operating system, apps, and virtual machines. You can’t have any VM (virtual machines) running during the in-place upgrade.
Upgrade Windows Server 2012 to Server 2016
1- Please make sure that you are running Windows Server 2012. Right click on my computer (This PC) and then properties
2- Enter Windows Server 2016 Setup media, and then double click to run.
3- It is always best practice to get the latest updates, in case any important security patches have been released, so I would recommend keep the default setting. Click next.
4- Checking the updates.
5- Enter your Server 2016 Product Key and then click next.
6- Here you can decide what type of operating system you want to upgrade, and click next.
7- Accept the license terms.
8- In this window, the Keep personal files and apps default option was chosen, so I cannot advise on the impact of choosing nothing. I would imagine that selecting this would delete everything, including any installed Server Roles. Proceed with this step at your own risk. Click next
9- Here you will get a rather lengthy Getting Updates window.
10- Finally, before starting the installation, you are prompted with an interesting warning, which you have to dismiss (confirm) before the installation will start.
11- The install check disk space.
12- Now the critical moment, review the settings that we have been specified and then select Install to start the process:
13- The full-screen setup will start, preventing you from doing anything else on the Server throughout the process.
14- This Server will restart several times after that. The whole process will take some time to complete the process.
15- After the upgrade, you will be greeted with the new Windows Server 2016 login screen.
In this guide, I will explain how to Backup Restore Reset Windows Server 2019. significant data can be lost, or the operating system can crash due to several reasons, for instance, an OS update, a virus, trogon attack careless dismissal of a file, system errors, human faults, Recycle Bin cleaning, formatting disk, etc. If we face any of these problems, don’t worry, this guide will help you restore/recover your server back to normal.
When some files are deleted from Windows Server OS, they don’t vanish from the hard disk. They can still be recovered from the Recycle Bin if they won’t remove without using the Recycle Bin. Even if the files were removed permanently from the Recycle Bin, there is still a chance to restore them. You can either restore the information or recover the operability & previous state of the operating system from a backup.
Backup Restore Reset Windows Server 2019
How to setup and configure backup for Windows Server.
Backing up Windows Server is a very important part of everyday server management. Windows Server backup copies enable recovery after crashes when data may be lost.
By default, the backup feature is not installed.
1- To enable it, select the search menu, type Server Manager, and then launch it.
2- In the Manager, select Add roles and features.
3- Click Next.
4- Click next.
5- In the server choosing tab, click next.
6- Click next.
7- Select Windows Server Backup feature from the list, and then click next.
8- Click Install.
9- Click Close.
The Windows Server Backup has been installed successfully.
You can access its backup features.
How to create a backup of Windows Server
1- In the interest of creating a backup or configure backup scheduled, From the Server Manager, select Tools and then Windows Server Backup.
2- For the quick launch, type Windows Server Backup in the search field.
The following features will be configured
“Backup Schedule” “Backup Once”, Recover and Configure Performance Settings.
Configure scheduled backup in Windows Server
1- To configure automatic backup on schedule, select Backup Schedule.
2- Click next.
3- Select backup configuration, backup type, “Full server (back up all server data, applications, and system state) or Custom (if you want to select a certain volume of files to be backed up). Click next
4- Choose a backup time and then click Next.
5- Select destination for backups, I am selecting the network shared folder. Click next.
6- After selecting this specific option, you can see a warning that you will only have one backup at a time. Click ok
7- Enter the network path and then click Next.
8- After that, it will be asked to type your account details to enable the scheduled backup.
3- If you want to choose a specific folder or files, choose custom and then click next.
4- Select Add items to be backed up.
5- Select items and then click ok.
6- Click next.
7- Specify destination type and then click Next.
8- Select the backup destination and then click next.
9- Select Backup to start.
10- Backup in progress
11- Click close
How to restore Windows Server from backup
Now our backup is ready, let’s examine the scenario when we want to restore Windows Server. In different cases with the operating system (OS) crashing, having a backup will save you a lot of time if compared with having to reinstall and reconfigure the whole thing.
1- To recover Windows Server to its previous state, Type Windows Server Backup in the search bar and then open it.
2- Select Recover.
3- Select the backup location:
This server or A backup is stored in another location. Click next
4- Specify the local disk or network folder where the backup is stored and then click next.
5- Select the backup location and click next.
6- Select the data from which server will be recovered and then click Next.
7- Select a backup available for recovery and click next.
8- Select what should be recovered and click next.
8- Select items to recover and click next.
9- Select browse to specify the folder for recovery.
10- Select WindowsImageBackup folder and then click ok.
11- Click next.
12- Select Recover to start the process.
13- The system will calculate how many files are to be restored, and the process will start. Restore done, click Close.
14- Restored items.
Restoring a crashed system
If you have a recovery drive, you can use it to bring your operating system back to normal.
1- If you have a recovery drive, you can use it to bring your operating system back to normal.
2- Click next.
3- In the Windows Setup, click on Repair your computer.
4- Select Troubleshoot.
5- Select System Image Recovery.
6- Select the operating system.
7- Select a system image backup and then click Next.
8- You can leave the box to Format and repartition disks checked or as it is, click advanced
9- Re-image your computer, click ok, and then next.
10- Click finish.
11- Click yes to confirm disk formatting.
12- Re-image your computer in progress.
After the restart, the server will be restored to the state restored in the last backup.
In this blog, we will see how to upgrade Windows Server 2008 R2 to Windows Server 2012. While selecting the Server edition makes sure you select the edition that fits your requirements. Before we start and deploy Windows Server 2012, let’s first have a look at the editions of Windows Server 2012.
Upgrade Windows Server 2008 R2
If I were to upgrade my existing windows server 2008 R2 Standard server to windows server 2012 I would first choose the edition and then I need to check the upgrade paths. I have created an upgrade table which shows whether you can upgrade to windows server 2012 with your present operating system.
Upgrade From
Windows Server 2012 Standard
Windows Server 2012 Datacenter
Server 2008 Standard SP2
Yes
Yes
Server 2008 Enterprise SP2
Yes
Yes
Server 2008 Datacenter SP2
No
Yes
Web Server 2008
Yes
No
Server 2008 R2 Standard SP1
Yes
Yes
Server 2008 R2 Enterprise SP1
Yes
Yes
Server 2008 R2 Datacenter SP1
No
Yes
Web Server 2008 R2
Yes
No
Let’s have a look at hardware requirements for upgrading Windows server to windows server 2012. Windows Server 2012 minimum requirement is 16 GB to 32 GB of disk space. It required 1.4 GHz 64-bit processor, Ram 512 MB, 32 GB Hard Disk space, CD/DVD Drive, Super VGA (800×600) or higher resolution monitor, keyboard, and mouse.
In this blog, I will show you how to upgrade a windows server 2008 R2 Standard to Windows Server 2012 Standard.
Note: my existing server 2008 is in workgroup; do not consider this post to upgrade your domain controller to windows server 2012.
2- Insert the Server 2012 Standard CD/DVD into the DVD-ROM and then open it.
3- Windows Setup screen, click on Install now.
4- If you need to get security updates and latest drivers for the operating system then choose Go online to install updates now. We will also do the windows updates after the upgrade will complete, so select No, Thanks.
5- Type your windows server 2012 product key and then click on Next.
6- Select the Windows Server 2012 Standard (Server with a GUI) and then click on Next.
7- Accept the license term checkbox and then click next.
8- First type “Upgrade: Install Windows and Keep files settings & applications”. This will keep all existing files, settings, applications and upgrade server to windows 2012.
9- Compatibility report, click next.
10- The upgrade will take some time.
11- Upgrading Windows.
12- Windows restarting.
13- Upgrading Windows.
14- Windows set
15- The upgrade from server 2008 R2 Standard to server 2012 Standard is complete.
In this article, I will show you how to fix the “Your Credentials Did Not Work” error while using (RDP) Remote Desktop Connection feature in Windows 10/8/7.
In Windows 10, we can use the remote desktop feature to connect systems remotely. This blog talks about an issue in which one is related to credentials used in Remote Desktop connectivity. Genuinely, while connecting systems remotely, recently I received the following error. Your credentials did not work The credential that was used to connect to did not work. Please enter the new credentials. The logon attempt failed.
In this issue, I was sure that the credentials were correct. Even it worked fine with other computers but one of my machines start throwing this error.
Using Security Policy Snap-in
1- Select Windows search bar, type local security policy and then select it.
3- Windows Local Security Policy, expand the Local Policies, choose Security Options. Search for policy setting named Network Security: LAN Manager Authentication level. This is set to Not Defined, by default. Double click on it.
4- Choose from the drop down list “Send LM & NTLM – use NTLMv2 session security if negotiated” and then click ok.
Using Group Policy Snap-in
1- Select Windows search bar and type gpedit.msc and then click on it.
I have written this blog, to help you migrate your existing Active Directory Domain Controller which is running on Windows Server 2012 R2 name (DC2k12) to Windows Server 2019 name (DC2K19). So, let’s get started.
This is straight forward process, but first make sure you have test it 1st in your Test Environment.
I am using two Servers & my previous domain Server (xpertstec.local).
First we need to install Additional domain controller
How to install Additional domain controller click here
Migrate Active Directory Server
Login to your additional domain controller (DC2K19)
Change the alternative DNS server.
netdom query fsmo
Open the command prompt and type netdom query fsmo to check the Master Operation role.
Migrating FSMO (Flexible Single Master Operation) roles to Windows Server 2019 (DC2K19).
1- Open active directory users and computers console. Right-click your local domain (xpertstec.local) and then click Operations Masters.
2- Select RID tab and then click Change.
3- When you are asked for confirmation, click yes.
4- Click OK.
5- Select PDC tab and then click Change.
6- When you are asked for confirmation, click Yes.
7- Click OK.
8- Select Infrastructure tab and then click Change.
9- When you are asked for confirmation, click Yes.
10- Click OK.
11- Select close.
Change Active Directory Domain Controller.
1- Still on our DC2K12.xpertstec.local server, open Active Directory Domain and Trusts console, right-click Active Directory Domain and Trusts, and then click Change Active Directory Domain Controller.
2- On the Change Directory Server interface, click This Domain Controller or AD LDS instance and then choose your new Windows Server 2019 which is DC2K19.xpertstec.local, and then click OK.
3- In the Active Directory Domains and Trusts interface, right-click Active Directory Domains and Trusts found in the folder tree and then select Operations Manager.
4- In the Operations Master interface, select Change to transfer the domain naming master role to the Windows Server 2019 (DC2K19).
5- Click Yes.
6- Click OK
7- In the Operation Master interface, verify that Domain naming operations master is now transferred to the DC2K19.xpertstec.local server.
In the DC2K19.xpertstec.local server, open Command Prompt and then type regsvr32 schmmgmt.dll to change the Schema Master.
Click OK.
How to Change Schema Master Role
Migrate Active Directory Server
1- Now we need to change Schema Master, on the DC2K19.xpertstec.local server. Type MMC and hit enter.
2- Select File and then click Add/Remove Snap-in.
3- Add or Remove Snap-ins interface, choose Active Directory Schema, select Add and then click OK.
4- In the Console, right-click Active Directory Schema and then click Change Active Directory Domain Controller.
5- In the Change Directory Server interface, click This Domain Controller or AD LDS instance, click DC2K19.xpertstec.local server and then click OK.
6- In the Active Directory Schema box just click OK to proceed.
7- In the Console, right click Active Directory Schema and select Operations Master.
8- Change the Schema Master interface, choose the Change button to transfer the schema master role to the Windows Server 2019 (DC2K19.xpertstec.local).
9- Click Yes.
10- Click OK to proceed.
11- Affirm the current schema master is now DC2K19.xpertstec.local, and then click Close.
Transfer FSMO roles
Open PowerShell, and then type netdom query fsmo command. Check if all the five FSMO roles have been transferred to Active Directory Domain Controller Windows Server 2019.
POWERSHELL (TRANSFER FSMO ROLES)
There are a lot of steps involved to accomplish fsmo transfer to a different Domain Controller. Note: that there is not only 1 way to accomplish this. Open Powershell as admin and type in netdom query fsmo or if you like PowerShell way Get-ADForest | choose schemamaster,domainnamingmaster –> For FOREST WIDE ROLES and Get-ADDomain | select ridmaster,pdcemulator,infrastructuremaster –> for Domain wide roles.
Change Global Catalog
Open Active Directory Sites and Services, expand Sites, expand Default-first-site-name, expand DC2K12. 1- Right-click on NTDS Settings and then select properties.
2- Untick Global Catalog checkbox and then click ok.
How to uninstall Active Directory Domain Services from Windows Server 2012 R2.
Log in to Windows Server 2012 R2 server with domain administrator credentials.
1- Open PowerShell and type below command then hit enter.
2- Insert local administrator password, confirm password and then press enter.
3- Type Y and press enter.
4- Be patient. It will complete in few minutes.
5- The server will be rebooted automatically.
DOMAIN / FOREST FUNCTIONAL LEVEL
What you want to know about DFL and FFL is that they epitomize advanced features. That is accessible with the newest software that can be used in the domain. Generally, when you administer a large AD environment we will notice that you have various Windows OS versions on your DCs. If you have DCs that are server 2008 R2, 2012 and you install server 2016 you will not be able to use the latest advanced features. That comes with server 2016 until we upgrade all our DC’s to server 2016 and raise the functional level. AD features are not backward compatible with AD domain controllers on the earliest versions of Windows Server so if you are running Server 2008 R2 and you install server 2016. You will be limited to those features that come with Server 2008 R2. Functional levels can be used to determine which DCs are allowed to run in our environmental. For example, if you raise the functional level to server 2016 we will not be able to install server 2012 R2 DC in our domain. You can’t set the DFL (domain functional level) to a value that is lower than the FFL (forest functional level), but we can set it to a value that is similar to or higher than the forest functional level.
How to check the DFL – FFL you can use GUI or Powershell.
1- GUI, Right-click on your domain and then select properties.
2- Now you can see domain and forest functional level.
RAISE DOMAIN AND FOREST FUNCTIONAL LEVEL
1- In ADUC right-click on the your domain and then select Raise DFL.
2- Select Windows Server 2016 so I am not able to raise it more than that but you comes here to raise domain functional level.
3- Click OK.
4- Click OK.
How to raise forest functional level.
1- Open domains and trusts, Right click on active directory domain and trust and choose raise FFL.
2- Select raise.
3- Click OK.
4- Click OK.
How to confirm the domain and forest functional levels.
CredSSP Encryption Oracle Remediation Credential Security Support Provider (CredSSP) Protocol is a security support operator that helps to securely representative user credentials from a client computer to a windows server by using Transport Layer Security (TLS) as an encrypted pipe.
Why the Windows update
The Windows update in May is made to correct how CredSSP validates demands throughout the authentication process. Microsoft updates have found a CredSSP error in RDP and found a fix for the vulnerability by mandatory requiring to update both the client and server computer to work properly.
Remote Desktop Connection
An authentication error has occurred. The function requested is not supported.
Remote computer: IP Address or Computer Name This could be due to CredSSP encryption oracle remediation. For more information, see the Link https://go.microsoft.com/fwlink/?linkid=866660
This error is because of the windows update not installed either on the server or on the client computer. How to fix CredSSP
To fix the issue, we want to uninstall the Windows update and roll back to an older version. But rolling back to an old version is not a best practice. We can fix this by modifying the group policy in the local computer to use the vulnerable setting
1- Press (Win Key + R) Go to Run Type gpedit.msc and then press Enter
2- Expand Computer Configuration and then select Administrative Template.
3- Expand Administrator templates and then select System
4- Expand System and then select Credentials Delegation
5- Double Click on Encryption Oracle Remediation to open.
6- Select Enable and change protection level to Vulnerable and then click Apply or OK.
7- Press (Win Key + R) Go to Run Type cmd and then press Enter
8- Type gpupdate /force command
9- Group policy successfully updated
Now your remote desktop connection will be working fine.
Install Web Server IIS, in this article I going to show you how to install the webserver (IIS) Internet Information Services in Microsoft Windows Server 2019 operating system. Install Web Server IIS, in this article I going to show you how to install the webserver (IIS) Internet Information Services in Microsoft Windows Server 2019 operating system.
Install Web Server IIS
1- Click on Windows start menu and then select Server Manager.
2- Server Manager, Dashboard select Add roles and features.
7- A new window will popup that additional features are required, simply click the Add Features button to install these as well.
8- Select server roles web server iis selected click next.
9- We will not be installing any additional features at this stage click next on the Select features window.
10- Click next
11- Enable webserver IIS Select role services, the window you can install additional services for IIS if required. then Click Next.
12- Confirm installation selections, review the items that are to be installed and then click Install when you are ready to proceed with installing the IIS web server.
13- No reboot required, the installation has succeeded, then click the close button.
Enable IIS Web Server With PowerShell
1- Use the Windows PowerShell command line interface (CLI) instead, follow these steps. Open the PowerShell with admin rights and then run the Install-WindowsFeature cmdlet as shown below. Install-WindowsFeature –name Web-Server -IncludeManagementTools
2- IIS Web Server start installation
3- Web Server feature successfully enabled
Its include the management tools so that we can manage IIS on this server
System Center Virtual Machine, in the article I will guide you on how to install Microsoft’s System Center Virtual Machine Manager 2019 (SCVMM). If you run Microsoft’s Hyper-V as your virtualization platform then you probably want a way to manage your Hyper-V hosts as well as the virtual machines that reside on this.
4- Virtual Machine Libraries Configuration click here
Install System Center Virtual Machine Manager
I am using a trial version of SCVMM which we can download if from the Microsoft Website
1- Browse the windows explorer to install SCVMM. Double click on SCVMM_2019.exe to start the installation.
2- The SCVMM install welcome screen, click next.
3- Accept the SCVMM license agreement and then click on next.
4- The SCVMM installer needs to extract the downloaded files. Please select a destination folder location and make sure you have enough free disks space (approximately 28GB) then click on next.
5- Confirm the settings and folder where you want to extract then click on Extract.
6- The installation files start extracting. This will take a few minutes to complete the extraction process.
7- Now the extraction of SCVMM is complete. Click on finish button.
Open your Hyper-V manager console and connect to your SCVMM host. Now we need to build a new VM for the System Center Virtual Machine Manager server.
8- Right click on host then click new and then Virtual Machine.
9- New Virtual Machine Wizard, click the next button to proceed.
10- Type your VM name (SCVMM) and select where to store the VM files. Click Next.
11- Choose Generation 1 and then click next.
12- The minimum memory recommended 4GB so as this is just a test lab, click on next.
13- Select a virtual switch you want to deploy this VM to then click next.
14- This is one of the most important parts of the System Center Virtual Machine install process, make sure to change the virtual hard disk to Use an existing virtual hard disk and browse to the extracted location of the SCVMM download. Select SCVMM_2019 VM and then click next.
15- Review the Summary of System Center virtual machine and then click on Finish.
Configure System Center Virtual Machine Manager
16- Hyper-V manager console and browse through your virtual machines the one we newly deployed System center virtual machine. Right-click on SCVMM and then click connect.
17- Virtual Machine window opens click the start button.
18- System center virtual machine starting Services.
19- Now we have run through the Windows 2019 server installation. Select your country/region and then click next.
20- Click Accept.
21- Type a local administrator password and then click the finish button.
22- Windows 2019 server successfully installed, log in to the server with the local administrator credentials.
Now we need to join the System center virtual machine to a domain. Click Here
In the next article, we need to start the installation of the SQL Database. On the desktop of Server 2019 VM, we can see Microsoft has placed two icons for me to use to start the SCVMM installation.
In this article, I am going to explore how to Add MX Record in DNS Manager Server. MX themselves stands for Mail Exchange and is a necessity when configuring the email server
1- Expand Forward Lookup Zones right-click on your external domain (xpertstec.com) and then select New Mail Exchange (MX).
2- So, click browse.
3- Select your DNS server > Forward lookup zones > your external domain (xpertstec.com) > select mail and click ok.
Alias CNAME Record, In this post, I can use this method to add an Alias canonical name (CNAME) reserve record for your Web server to a zone in Domain Name Server on your domain controller.
Add Alias CNAME Record
1- Expand Forward Lookup Zones and right-click on your external domain (xpertstec.com) and then select New Alias (CNAME).
2- within the Name, field Aname (autodiscover) for your certificate and then click on browse.
3- Select your DNS server > Forward lookup zones > your external domain (xpertstec.com) > so select mail and click ok.
A forward lookup zone is a critical component of DNS (Domain Name System) that helps to match domain names with the appropriate IP addresses. When you type a domain name into your web browser, DNS is responsible for finding the correct IP address so that you can load the website.
Without DNS, you would have to remember the IP address of every website you wanted to visit, which would be nearly impossible.
Forward lookup zones use a series of DNS records to store information about a domain and its associated IP address. The most common DNS record is the A record, which maps a domain name to an IP address.
There are also CNAME records, which can be used to redirect one domain to another, and MX records, which route email messages to the correct server. Creating and maintaining a lookup zone is critical for any administrator.
In this article, I’m going to discuss How to Create a Forward look-up zone is a Domain Name System zone in which hostname to IP address and IP address to hostname relations is saved.
1- On your active directory DNS server, open DNS Manager Right click on forward lookup zone and select New Zone.
2- Click Next.
3- Default settings click next.
4- Default settings so click next.
5- In the Forward Lookup Zone Name field enter your external domain name (my external domain is xpertstec.com).
6- We will manually create all the records in this zone so select do not allow dynamic updates click next.