I manage the network for a small office. The office has 1 server and 5 client machines in a Windows domain. The old server is running Windows Server 2012 Standard and the client machines are running Windows 8.1. I've purchased a new server and installed Windows Server 2012 R2 on it and joined it to the domain, although I haven't defined a role for it yet.
The environment is this: windows 7 client (UAC at max) , server 2012 R2 (UAC at default) file server in an AD domain environment.
Created shares with the usual settings (everyone access on the share but control via NTFS to specific AD groups...).
The scenario is this: logged onto the client as a standard user, want to install an application so try to connect to an installation share \server\instal
Since Windows 8.1 has Hyper-V Platform and Hyper-V Manager built in to it, if I just enable the Hyper-V Manager on my Windows 8.1 client machine I should be able to access the standalone Hyper-V Server 2012 R2 (which I'm planning to install on my 2nd machine) right?
Then why every article I found on this suggests to install RSAT on my client machine?
Server running Windows Hyper-V Server 2012 R2 Core "Adama", up to
Core is accessible via RDP Running VM with Windows Server
Essentials 2012 "Apollo", also up to date and accessible via RDP
Apollo functions as a File server, AD Services haven't been activated
yet, so there is a domain, but unused, everything goes via WORKGROUP
Client running Windows 8.1 Pro, up to date