Make sure you have Enterprise Admin account/permission to run this command and run the PowerShell as Admin.
If you run into error that you can’t bring up a new Domain Controller due to Operating System is not in the suitable forest functional level, this solution could help you out. RODC is not accepted to run these commands.
I am not sure whether does this require FSMO roles to make the changes towards these functional levels. Hence, I run these commands on the Primary domain controller.
Login to your existing domain controller using an enterprise admin account
Run the Windows PowerShell as Admin
Type in the following command to change the forest functional level
#Get Forest level Info
#To Set the forest level
Set-ADForestMode -ForestMode <Operating System Name>
#Example: Set-ADForestMode -ForestMode Windows2012R2Forest
Type the following command to change the domain level
#Get Domain level Info
#To Set the forest level
Set-ADDomainMode -DomainMode <Operating System Name>
#Example: Set-ADDomainMode -DomainMode Windows2012R2Forest
Would recommend that you study on the difference between Forest Functional Level and Domain level. I would write a blog post about it soon!
To those that wants to perform Live backup or export (to a local drive or external drive) of your virtual machines via Hyper-V, before you jump into that there are few things that you need to take concern of;
Where is your virtual machines located on what server operating system?
Does the server support live backup or export?
What is live backup or export?
A live backup or export is where you could run your backup without having to shut down the virtual machines. This require minimal to zero impact or downtime.
If your virtual machines are hosted on a legacy server, such as Windows Server 2012 below, you are require to shut down the virtual machines and perform the backup or export. If the virtual machine is not shut down the export button will not be shown to you to perform the backup. However, please do take note that if you were to migrate virtual machines from legacy server to non-legacy server, is best to not use the export feature in the legacy server, please refer the reference below for full explanation and proper way to migrate.
If your virtual machines are hosted on a non-legacy server, such as Windows server 2012 and above, then you can perform live backup or export without the need to experiences total downtime. As technology getting more advance this is the benefit to IT admins to perform their tasks without the need to perform after hours, and end users will not experience total downtime.
Do also read up and understand when to use checkpoints and when not to use checkpoints. Is basically means snapshots.
This is my first time doing VM migration or import/export of VM from server 2008 R2 to server 2012 R2. At first, I used the export function from the Hyper-V in server 2008 R2 and I notice the export result was different from the server 2012 R2. Thus, when I try to import the VM from server 2008 R2 to server 2012 R2, it was unable to recognize.
Always make a backup copy! Don’t modify the original!
This is because 2008 or 2008 R2 are legacy servers, and choosing the export feature to export the VM will result of export EXPfile instead of XMLfile. In server 2012 R2, VM that is exported has XMLfile.
The best way to import VM from legacy server is to copy the entire VM folder to server 2012 R2. When I mean entire VM folder, means its VHDand etc..
This VM that I am importing does not have any checkpoints or snapshot, so I am unsure that do you required to delete the copied snapshots before you import.
So what I did was,
At server 2008 R2, shut down the VM
Locate the entire Data folder of the VM in File Explorer
Right click the folder > Properties > Share > Advanced Sharing > Add the specific user account (server 2012 R2) and the computer (server 2012 R2) > Full Control
Is up to your choice on how you want your destination server to retrieve the source information (VM), it could be via a Network Share, a USB, or an external Hard Disk
At server 2012 R2, open file explorer
At the top bar, type “\\<2008 R2 server name/IP address>\<vm folder name>\”
Copy the entire folder and paste it into server 2012 R2 (your comfortably location/driver/directory)
Remember to remove the share permission of the folder in server 2008 R2, after you finish copying the folder from server 2008 R2 to server 2012 R2
Create a new folder in server 2012 R2 and rename it as your actual/original VM’s folder naming in server 2008 R2, this folder will be the new location of your VM
Go to Hyper-V in server 2012 R2 > select the Import Virtual Machine at the right side bar
Browse and locate the VM folder that you just copied
Select the import type “Copy the virtual machine“, this allows you to create a new unique ID of the virtual machine and also allows you to choose your new location to store this VM in sever 2012 R2
Make sure the new location are browse to the new folder that you just created in server 2012 R2
Then you click next > finish and wait for the importing to complete
Make sure the VM in server 2008 R2 is Shut down
Start or Boot up the VM in server 2012 R2 (If required to change IP address of the VM then change)
Everything is fine and monitor for 48 hours, then only decide to remove the VM in server 2008 R2
After import the VM, Hyper-V do not start the VM automatically. You have to start the VM manually, after import completed.
Happy Chinese New Year to my Chinese friends and Happy holiday to the non-Chinese friends!
There are cases where you have to apply the license later due to you have to wait for the license key. So you had to proceed deploying and running your tasks. However, the GUI of activate the Windows Server license doesn’t prompt to allow you to key in the product key and there is no error shown. (After you have promoted the server as Domain Controller)
The solution is to activate the license key through command prompt or Windows PowerShell and run as administrator.
If you have forgotten the command, is “slmgr” and to see the list of the command’s option just type “slmgr /help“, it will prompt the list.
Here is an example;
Below is the command to activate your license key;
slmgr /ipk <your product key>
If you wish to view expiration of your license key, then you could use this command;
When your environment migrates from legacy or lower version of Windows Server to a newer version. Example, from Windows Server 2008 to Windows Server 2016. You will experience this. This is why I am writing this post.
I notice when I launch the Group Policy Management and direct to one of the Group Policy Object > Settings Tab > Show all and saw a part says “Extra Registry Settings“. I open up the Edit, trying to locate that part but failed to do so. What I did is I research on the browser, checking whether has anyone experience it and what are the solutions to it.
There is a message display inside the “Extra Registry Settings” but not helpful in getting any information in the browser. The message is “Display names for some settings cannot be found. You might be able to resolve this issue by updating the .ADM files used by Group Policy Management.”
Thank god that PowerShell can remove this registry using the Remove-GPRegistryValue Command. You may refer to the reference below too.
First I run the GET command just to make sure the registry value is valid;
#This command retrieve information of an extra registry of the
Get-GPRegistryValue -Name "<GPO Name>" -Key "HKLM\Software\Policies\Microsoft\Windows\CurrentVersion\Internet Settings\"
#If result is valid then move on to REMOVE command, note that sensitivity on the Key Path Value "\" at the end must not be included
Remove-GPRegistryValue -Name "<GPO Name>" -Key "HKLM\Software\Policies\Microsoft\Windows\CurrentVersion\Internet Settings\" -ValueName "<Registry Value Name>"
#A result will be shown after the REMOVE command executed, result contain GPO Name, Owner, creation time and modification time
Yes, is Windows Server 2008 and Windows Server 2016. ISCSI Storage located at the Windows Server 2008 and the ISCSI Initiator is Windows Server 2016. This short video will explain how you could create ISCSI storage properly. Hope you enjoy it! Sorry, I sound slightly nervous.