Hello - I was asked by a school to create a VDI environment that students can access through thin clients. I haven't done a lot of research yet and wanted to check if anyone can point me to a good reference or even a little walk through how this should be done,

The school wanted to setup the lab entirely in Azure, however the monthly reoccurring cost are to high in the long run. So I suggested an on-premise setup with the option to provision clients to Azure if needed. From what I was reading about Windows Server 2016, it's seems to be designed to work closely with Azure.

What hardware specs would you recommend to provision, manage and run those 50 VMs? I was thinking about getting a lower end server for AZURE ADS connector and the Systems Center suite which I assume is needed to manage and provision VMs.

For the Hyper-V server running the VM I am a trying to find out what the minimum specs should be to accommodate all machines at the same time. Or would it be better to get two servers and setup a cluster?

As for licensing, I wanted to go with the Server 2016 standard or is there any feature in the Datacenter edition that I would need? I am also unclear on the licensing? Do I need a user or device CAL for every connection? The machines are supposed to run Windows 10 with Office installed and some other free software. How would that be billed (education licensing) ?

Hope I was able to give an idea what I am trying to do here. I am looking forward to your …

I have 2 HYPERV host servers.

HYPERV1 is hosting APPSERVER
HYPERV2 is hosting  SBS2011 server and TERMINAL server.

(besides I have another domain controller and  approx 20 workstations)

I had hardware issues with the HYPERV2 host server and had to rebuild it with MS Server 2016 standard (It was MS Server 2012 R2 before)
I use Altaro for backup of the virtual machines.

I restored (or rather imported from backup) my main server Sbs2011 (Small Business Server 2011)

Now after the restore I have issues with connectivity to this server.

The server seemed to be restored correctly, but when I want to connect to shared folder on the Sbs2011 from another server I get following message:

"\\sbs2011\share is not accessible. You might not have permission to use this network resource. Contact the administrator of the server to find out if you have access permission.
Logon Failure: The target account name is incorrect"

I thought that possibly rejoining the domain will fix the issue, but when I try to do that I get:

"The following error occurred attempting to join the domain "domain":
Logon Failure: The target account name is incorrect."

It looks like I have no issues connecting to the SBS2011 by IP address.
I also noticed that after the reboot the SBS2011 netlogon service is paused and time service is not started.
They start manually without issues.

Well I am stuck - please help.

I am setting up a site in an Azure VM Windows 2012 server. The DNS is pointing to the external IP of that machine.
Yet, when I go to IIS to bind the site to that IP the IP is not displayed in the drop down menu and the site does not come up.
I checked the traceroute and the domain is correctly pointing to that IP, I am not familiar with what other configuration needs to take place in order to bind the external IP to the site so that it comes up.
Any guidance would be helpful.

I have a question regarding deploying templates.

when we deploy a template with SCVMM 2016 we receive error.

Error (2906)
The specified path //XXX-XXX-XXX.jict.local/MSSCVMMLibrary/Templates_xxx/XXX-TS-XXX-2/XXX-TS-XXX.vhdx is not valid on the XXX-CLA-XXX.jict.local server.

Recommended Action
Ensure that you have specified a valid path, and then try the operation again.

Select all Open in new window

you can see in the error above. that the slashes are the wrong way.... is there a way i can change this path?

Pls advise.

Hi,

I have 2 Windows Server 2012 R2 with hyper-v installed, in a workgroup. I currently have 1 vm that replication is enabled with certificate-based authentication 443 HTTPS, and it is working fine.

When i try to make a second vm to be replicated, I have this error :
Any idea ?

Thanks !

I have a Lenovo System x x3250 M6 3633K3U 1U Rack-mountable Server - 1 x Intel Xeon E3-1230 v5 Quad-core (4 Core) 3.40 GHz 16GB of Ram and 3 2TB Hard Drives in a Raid 1 with Hotspare.

This is a new install running in Server core mode and i installed all updates, changed Hostname, and set a static ip. When i run the following command in powershell i get an error. i checked the event logs but dont see any errors. Not sure if there is a different log to check.

PS C:\Users\administrator> Install-WindowsFeature -name Hyper-V -IncludeManagementTools -Restart
Install-WindowsFeature : The request to add or remove features on the specified server failed.
Installation of one or more roles, role services, or features failed. Error: 0x800f0831
At line:1 char:1
+ Install-WindowsFeature -name Hyper-V -IncludeManagementTools -Restart
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (@{Vhd=; Credent...Name=localhost}:PSObject) [Install-WindowsFeature],
Exception
+ FullyQualifiedErrorId : DISMAPI_Error__Failed_To_Enable_Updates,Microsoft. Windows.ServerManager.Commands.AddWind
owsFeatureCommand
Success Restart Needed Exit Code Feature Result
------- -------------- --------- --------------
False No Failed {}

Hi, I am trying to set up VMM in my domain and I am struggling a bit with creating a cluster via VMM. I have used clusters before but never through VMM.

I have a blade chassis with 16 blades in and I am trying to standardise the machines. Each blade has 2x 10GB connections across 2 switches and 4x 1gb connections across 2 switches (ports 1+3 switch 1 and 2+4 on switch 2).

Now I think I am doing my setup correct, but some advice on what is wrong would be great.

I am trying to create 4 different connections. Management, cluster, storage and Hyper-v. To do this I have created 3 logical switches. 10GB, Client and Management. I have then created 4 logical networks.


Storage - 192.168.10.0/24
Client - 192.168.20.0/24
Management - 192.168.12.0/24
Cluster - 192.168.14.0/24

On 3 blades for now while I test this I have gone in to the virtual switches tab. On here I have created the following

Client Switch - No virtual adapter and assign physical adapter 1GB port 1 and 2. - I then assign this to the VM's and set the IP's and they can communicate fine.

Management Switch - Physical 1GB adapters port 3+4 with a virtual adapter on the Host management VM network I created and corresponding IP pool / static address

10GB Switch - Physical 10GB adapters port 1+2 with 2 virtual adapters, one for storage and one for cluster. I have a separate VM/Logical network for each of these and I have set them to the corresponding IP pools with static IP addresses.

So I think …

I'm using my home PC as a lab for virtual machines, and I do some media sharing from one of my VMs that I previously created in Workstation that I keep encrypted.  I don't need the VMs to be on 24/7; rather, just when I want to do more lab work or do media sharing to my TV.

Which environment do you recommend I go with?  It's been tricky getting both platforms working at the same time.  And is there a way to encrypt the contents of HyperV?

I am trying to create a clone of a Virtual Machine (VHDX) in Windows Server 2012 r2 so as to be able to use it as a base image to deploy on other Servers. I have read of different ways to do it but am not sure which is the preferred way for my scenario.

Some say to run sysprep on the Virtual Machine and then after it shuts down just copy the Virtual Machine to another folder.
Others say to sysprep it and then use the export option to it to another folder.
Still others seem to indicate that the exporting alone strips our the needed ID's and it would not need to be sysprepped.

Which of these is correct, and if none  of them are, what would be the best way to accomplish it?

Hello Experts,

Can someone please let me know to activate the Hyper V platform? As you can see from the image, I'm unable to activate the Hyper V Hypervisor.


Thanks

I can see that drive letters start from B: onward, but there is no A:.
I have successfully attached a virtual FDD, but drive letters still start from B:
We use A: as a hidden drive for internal purposes.
Does this mean I will have to change our system to use B: as the hidden drive instead of A:?

Thanks for any guidance.