Solved Hyper-V 2016 Server free file server included ?
-
So when I was playing with Hyper-V and remote managing it. I noticed I can install additional roles.
While the Remote Desktop Services included an licensing feature (you need to configure), where you can configure the licensing. The File Server does not have this. Thus if I used Windows Hyper-V standalone 2016 + File Server role, and not use the Hyper-V and use it for File Server is that okay ? and legit ?
This way I can get the get the benefit of Windows File services instead of using linux Samba, my question is did anybody noticed this or running this, and Do i get the full experience on SMB 3.1.1 like full server 2016 installation, any limitations ?
Thanks
-
@dbeato said in Hyper-V 2016 Server free file server included ?:
This will answer this:
https://www.starwindsoftware.com/blog/part-1-smb-3-0-file-server-on-free-microsoft-hyper-v-server-2012-r2thanks, very resourceful. Solved then. I thought I found a hidden Easter egg.
However, this process is a violation of license agreement, so StarWind urges the readers not to repeat it. As to the reason the process is at all possible, the answer is quite simple: SMB3 is a crucial part of the free Microsoft Hyper-V Server R2 and the latter won’t work if the protocol support is cut out. In any case, a fact that you can do something doesn’t mean you should. Violating Microsoft’s user license agreement is some serious business you don’t want to get involved in.
-
Not legal. You can't legally use Windows Server for production purposes without it being licensed.
-
@dustinb3403 said in Windows 2016 Server free file server ?:
Not legal. You can't legally use Windows Server for production purposes without it being licensed.
Even if it was the Hyper-V free one ?
-
@emad-r Why would you want to have a FIle Server in a Hyperv 2016 Server? Will this be for sharing files?
-
@emad-r said in Windows 2016 Server free file server ?:
@dustinb3403 said in Windows 2016 Server free file server ?:
Not legal. You can't legally use Windows Server for production purposes without it being licensed.
Even if it was the Hyper-V free one ?
Not even the hyper-v one. Because there is no such thing as 'the hyper-v one'.
Hyper-v and Windows Server 2016 are two completely different solutions.
The first is a hypervisor and the second is a Server operating system.
-
@dbeato said in Windows 2016 Server free file server ?:
@emad-r Why would you want to have a FIle Server in a Hyperv 2016 Server? Will this be for sharing files?
Alot of people stated that Windows handles file locking and sharing of excel files much better than Linux Samba, which is an issue i am having with my users. Excel Files in NAS that are run by SAMBA.
I dont blame SAMBA ofcourse.
-
@emad-r said in Windows 2016 Server free file server ?:
@dbeato said in Windows 2016 Server free file server ?:
@emad-r Why would you want to have a FIle Server in a Hyperv 2016 Server? Will this be for sharing files?
Alot of people stated that Windows handles file locking and sharing of excel files much better than Linux Samba, which is an issue i am having with my users. Excel Files in NAS that are run by SAMBA.
I dont blame SAMBA ofcourse.
Right, don't blame SAMBA, blame your NAS.
-
@dbeato said in Windows 2016 Server free file server ?:
@emad-r Why would you want to have a FIle Server in a Hyperv 2016 Server? Will this be for sharing files?
In a real, business oriented, production environment, one would never use their hypervisor for anything except as a hypervisor. The only reason the role for file services is available at all is to allow DAS to be available to other Hypervisors, as with a vSAN or cluster.
-
@dustinb3403 said in Windows 2016 Server free file server ?:
Not legal. You can't legally use Windows Server for production purposes without it being licensed.
Also I dont see any licensing options for file server role, FYI.
-
@emad-r said in Windows 2016 Server free file server ?:
@dustinb3403 said in Windows 2016 Server free file server ?:
Not legal. You can't legally use Windows Server for production purposes without it being licensed.
Also I dont see any licensing options for file server role, FYI.
Either your title is incorrect (you aren't using Windows Server 2016) or you're using Hyper-V 2016.
So which is it?
-
@dustinb3403 said in Windows 2016 Server free file server ?:
@emad-r said in Windows 2016 Server free file server ?:
@dustinb3403 said in Windows 2016 Server free file server ?:
Not legal. You can't legally use Windows Server for production purposes without it being licensed.
Also I dont see any licensing options for file server role, FYI.
Either your title is incorrect (you aren't using Windows Server 2016) or you're using Hyper-V 2016.
So which is it?
Ops using Hyper-V 2016, fixed title.
-
In this case (using Hyper-V 216) see @Grey response.
-
-
@dbeato said in Hyper-V 2016 Server free file server included ?:
This will answer this:
https://www.starwindsoftware.com/blog/part-1-smb-3-0-file-server-on-free-microsoft-hyper-v-server-2012-r2thanks, very resourceful. Solved then. I thought I found a hidden Easter egg.
However, this process is a violation of license agreement, so StarWind urges the readers not to repeat it. As to the reason the process is at all possible, the answer is quite simple: SMB3 is a crucial part of the free Microsoft Hyper-V Server R2 and the latter won’t work if the protocol support is cut out. In any case, a fact that you can do something doesn’t mean you should. Violating Microsoft’s user license agreement is some serious business you don’t want to get involved in.
-
On seperate note, I cannot select your latest reply as the correct answer for some reason, however if I quote it first then I can... Need to raise this with site admins I guess
-
@emad-r yeah, something weird about the permissions with the plugin.
-
@emad-r said in Hyper-V 2016 Server free file server included ?:
@dustinb3403 said in Windows 2016 Server free file server ?:
Not legal. You can't legally use Windows Server for production purposes without it being licensed.
Also I dont see any licensing options for file server role, FYI.
It's not a role. To license the use of any non-hypervisor functionality the license is a full Windows Server license.
