Next I want to create a new VM - My Domain Controller.

First, I want to change Hyper-V settings so my VM's go into D:\

1. How do I partition the D drive on my host - when i formatted windows I created one partition for (80GB) and left 1.9TB spare (which I want to be my D drive) - How do I bring the D drive online on the host and have it accessible?

Thanks

UPDATE: I have run Updates on the host and after a reboot I think i can now connect. It did throw another error about WinRM firewall but it connected - i'll report back after a bit more tetsing
THANKS so far

Its just the connecting via hyper-v manager 'Operation not supported' - So how can I allow remote management on the HV01 host or get my host to support Hyper-V Manager?

Enter-PSSession -ComputerName HV01 -Credential HV01\Administrator does work - yes this does work!

@obsolesce haha yes. HV01\Administrator

sadly no joy - same result even with hostname\administrator

I found online to run this command on the host - I'm not sure what that is so dont feel comfortable running it. Any ideas?

Run “MOFCOMP %SYSTEMROOT%\System32\WindowsVirtualization.V2.mof”

https://community.spiceworks.com/how_to/122307-fix-error-managing-hyper-v-server-2012-r2-from-windows-10

I'm connecting as the local admin. Ie on my host there is a default 'Administrator' user account.

Within HyperV-Manager I choose 'Connect to server' and Set User as:
Workgroup\administrator and then enter my password

I'm getting this error now!

I have just run:
netsh advfirewall firewall set rule group = "XXX" new enable =yes

Where XXX = Remote Event Log Management
Remote Service Management
File and Printer Sharing
Remote Scheduled Tasks
Performance Logs and Alerts
Remote Volume Management
Windows Firewall Remote Management

@joel said in HyperVServer Build:

@nashbrydges said in HyperVServer Build:

These are the steps I follow when setting up a Hyper-V server with a Windows 10 machine to manage in a Workgroup environment. Works perfectly every time.

From Hyper-V Server:

Enable Remote Management

• Select 4 on the menu
• Then select 1 for Enable Remote Management
• Go back to previous menu

Enable Remote Desktop

• Select 7 on the menu
• Then select "e" for enable
• Select 2 on the next screen for Allow clients running ANY version of remote desktop

Run Powershell Commands

• Type powershell in command window and press Enter
• Type "Enable-PSRemoting" and press ENTER
• Type "Enable-WSManCredSSP -Role Server" and press ENTER
• Select "y" when prompted to confirm and press ENTER
• Exit Powershell by typing "exit" and press ENTER
• In command prompt, type "net start winrm" and press ENTER <-- Use this is can't connect later to server

From Windows 10 Machine

• Control Panel -> Programs & Features -> Turn Windows Features On Or Off
• Enable Hyper-V role and press OK
• Launch Powershell as Admin
• Type "Set-Item WSMan:\localhost\Client\TrustedHosts -Value "IP_OF_HYPER-V_SERVER" and press ENTER
• Type "y" when prompted and press ENTER
• Type "Enable-WSManCredSSP -Role client -DelegateComputer "IP_OF_HYPER-V_SERVER" and press ENTER
• Type "y" when prompted and press ENTER

Edit Group Policy

• Click Windows icon and type "gpedit" and open Group Policy program
• Local Computer-> Computer Configuration -> Administrative Templates -> System -> Credential Delegation
• Edit the "Allow delegating fresh credentials with NTLM-Only server authentication"
• Click "Show" button to add items
• Add value "WSMAN/*" to servers list and click OK

Manage Via Hyper-V Manager

• Start Hyper-V Manager and click Connect To Server and add IP address of server
• Select "Connect as another user" and click "Set User"
• Enter user login details with username in format of "WSMAN\Username"
• Create Virtual Switch as needed

MY HERO - I'm in process of re-installing so will follow these steps - Thanks

So I followed this to the letter and no luck this time!!!
Last time i did run some PS for firewalls - do I need to do this also on the host?

@nashbrydges said in HyperVServer Build:

These are the steps I follow when setting up a Hyper-V server with a Windows 10 machine to manage in a Workgroup environment. Works perfectly every time.

From Hyper-V Server:

Enable Remote Management

• Select 4 on the menu
• Then select 1 for Enable Remote Management
• Go back to previous menu

Enable Remote Desktop

• Select 7 on the menu
• Then select "e" for enable
• Select 2 on the next screen for Allow clients running ANY version of remote desktop

Run Powershell Commands

• Type powershell in command window and press Enter
• Type "Enable-PSRemoting" and press ENTER
• Type "Enable-WSManCredSSP -Role Server" and press ENTER
• Select "y" when prompted to confirm and press ENTER
• Exit Powershell by typing "exit" and press ENTER
• In command prompt, type "net start winrm" and press ENTER <-- Use this is can't connect later to server

From Windows 10 Machine

• Control Panel -> Programs & Features -> Turn Windows Features On Or Off
• Enable Hyper-V role and press OK
• Launch Powershell as Admin
• Type "Set-Item WSMan:\localhost\Client\TrustedHosts -Value "IP_OF_HYPER-V_SERVER" and press ENTER
• Type "y" when prompted and press ENTER
• Type "Enable-WSManCredSSP -Role client -DelegateComputer "IP_OF_HYPER-V_SERVER" and press ENTER
• Type "y" when prompted and press ENTER

Edit Group Policy

• Click Windows icon and type "gpedit" and open Group Policy program
• Local Computer-> Computer Configuration -> Administrative Templates -> System -> Credential Delegation
• Edit the "Allow delegating fresh credentials with NTLM-Only server authentication"
• Click "Show" button to add items
• Add value "WSMAN/*" to servers list and click OK

Manage Via Hyper-V Manager

• Start Hyper-V Manager and click Connect To Server and add IP address of server
• Select "Connect as another user" and click "Set User"
• Enter user login details with username in format of "WSMAN\Username"
• Create Virtual Switch as needed

MY HERO - I'm in process of re-installing so will follow these steps - Thanks

Post can be closed. I found our GPO's are not tied to the OU's so was fine to simply re-create new OUs. Cheers.

@black3dynamite said in HyperVServer Build:

https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/manage/remotely-manage-hyper-v-hosts

I saw this earlier but skimmed over it. Having just re-read it, this was key to do on my Windows 10 client.

Computer Configuration > Administrative Templates > System > Credentials Delegation > Allow delegating fresh credentials with NTLM-only server authentication
Click Enable and add wsman/fqdn-of-hyper-v-host.

I'm going to format and start from scratch as previously I had enabled so many firewall rules and bits so want to start clean and see what I need to enable exactly.

Thanks I'll report back

Update:
I just ran Hyper-V Manager as an admin and this time when I tried to connect to HV01, I chose the option to Use another account and entered the HV01 local admin account and got message:

'Enable delegation of user credentials?
This computer is not configured to allow delegation of user credentials. Do you want to allow delgation of user credentials to HV01?'

I clicked YES and got the error:

Delegation of credentials to HV01 could not be enabled.
CredSSP authentication is currently disabled on the local client. You must be running with administrator privileges in order to enable CredSSP

Double help!

I've installed HyperVServer 2016 for the first time (HV01)
I have gone through sconfig and renamed the computer, given it a static ip, enabled remote desktop and remote management but now hit a brick wall.

I want to install 2x VM's on there so have a Windows 10 laptop which I installed the Hyper-V manager on but when i try to connect to my HyperV host (HV01) it says:

"An error occured whilst attempting to connect to server "HV01" check that the Virtual Machine Management Service service is running and that you are authorised to connect to the server.

The computer HV01 could not be resolved. Make sure you typed the machine name correctly and that you have network access.

HELP

We have all of our Active Directory users under the default 'Users' OU - all in one container.
I'd like to split this up into different branches, ie. Back Office, Marketing, Managers etc etc

However if I create new OU's and move users, will that break our group policies if applied to the original OU's?
Is there a way I can export all Group Policies so I can view what policies are in place (assuming i'll need to re-create them)?

Thanks
Jason

@scottalanmiller said in OBR10 - Server Setup:

@joel said in OBR10 - Server Setup:

Then, I can provision DomainController
Add Virtual Hard Drive - C:\OS (130GB) - (Location: D:\VM\DomainController)
Add Virtual Hard Drive - D:\Logs (20GB) - (Location: D:\VM\DomainController)

Why would you make a domain controller like this? Of all workloads, should not be this way.

• I recall reading a MS article stating should have the OS installed but then a second drive should be used as SysVOL/Logs

@scottalanmiller said in OBR10 - Server Setup:

@joel said in OBR10 - Server Setup:

My HyperV server will be in Raid10 with 2 partitions - C:\OS (100GB) - D:\Data (1.9TB)
(on D drive, create folder called VM\DomainController)
(on D drive, create another folder called VM\FileServer)

Don't make folders. This is all much simpler than you are making it out to be. All of this is stuff you can ignore.

Cool cool - thanks SAM