I've been reading about Windows Server 2016 and I'd like to try it in a workstation. I have already grabbed my copy and bought a brand new SSD for the task. The problem is, I'm a total newbie when the subject is "servers". I'm not lazy and I'm already googling the subject and trying to learn the most I can even before installing it. This site* is a starting point, although it was written for the 2012 version. But, at the same time, it would be very nice if a knowledgeable member of this forum could share some tips: you know, only the essential steps needed for the proper use of Windows Server as a workstation. It would help a lot of people. Thanks. * win2012workstation.com
A new website regarding Windows Server 2016 Workstation is in works. But you need to be careful, each Windows Server edition has specific features. I have discovered this from using WS 2016 since first preview. Already using it as a workstation. For me, it is fairly easy to set it up. You can join the Windows Server Workstation boards and discuss all the issues there.
2016 is just easier to use as workstation than previous servers. You can still use the MSC2012 converter to easily set some minor annoyances (IE security, shutdown tacker, password complexity and so on...). The only glitch is the missing msmpeg2adec.dll in the final version, but that looks more like a bug rather than an intended omission (tp4/5 had it and the video codec is there), hence just take it from W10 and you're fine.
I do not advice using the converter, manual configuration is less risky. WS 2016 is already halfway transformed into a workstation, if you install the Desktop Experience option. But still some work has to be done.
The converter is just an UI that does what you would do manually using gpedit, regedit, poledit and whatever. The old sections dedicated to something that isn't needed anymore (say, enable desktop experience, install wifi stack will just fail if called)
This is exactly what we need, a good discssion of the current issues with the process with pointers to refrences not really, Win7Ult/Ws2012Datacenter ; upgraded from XP/Win7Ult. now looking at Win10EntLTSB with this as an alternative, to see if I can stand the aggro. I'm never at the bleeding edge of change, except for KMS, that was fun. ...T
These are great news. I finally read most of the site I mentioned in the OP and now I will adventure a Windows Server 2016 install. Not in my main machine, though. It will be installed in an HTPC. Yeah, I know this is a bit odd, but life is odd sometimes. I'll be back to this topic to ask for your help if needed. Cheers!
Sever 2016 is my main driver on all client machines since july. No problems so far, just advantages. Funnily enough I'm still on 2012 R2 on my server/htpc machine, because a tiny dll from the IR receiver that is incompatible with W10/Srv2016
Yep, the same i use-it as my main OS, WS 2016, is a really good alternative to all W10 editions (Ltsb included) and prior OS, fast, granular settings, almost compatible with all software and drivers, i just have a bug with my intel lan 82579V, unable to install-it, and Windows Update try to insall it but it failed, and each time i re-check for update, each time it failed, i have to modify some *.inf files in the latest 21.1 package and run the following command to install : Bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS Bcdedit -set TESTSIGNING ON Driver successfully installed.
Yepp, I had to do the same on my vga (intel as well) just an obvious single byte to change, but enough to break the signature.
Forget to mention to don't forget to disable Sending KMS activation to M$, disable almost communication (Windows Firewall Control in public mode work like a charm), and disable Completly WD and MRST,using dism command for disable IE and WMP, i just added MBAE and SSP for real-time security, but no AV anymore. And "in memories for W7", classic shell start menu is really useful.
I tried todo without classiic shell on w7, 7 didnt need it once i got used to 7. 1st looks at 10, eek. If i can get used to it or fiddle with it without using 3rd party tools, i will. I use 3rd party tools if 100% neccessary.
I have a silly question, but what about using TV-Cards in Windows Server 2016? Is all the BDA stuff already there or is it a similar situation to Windows Server 2008 R2 where you would have had to patch the missing files into the OS? Greetings TEN
CAn you upload your modified intel lan 82579v driver? Edit: Nevermind windsman modified driver myself and works great. Thanks for the info to start me on the path to getting this done.