Nothing about TOR is a boring topic for me, but it's off topic for this thread titled: "[DISCUSSION] Windows 10 Pro for Workstations" I've already diverged into Firefox keyword search -- for which I probably should find a better place to put that post.
Yeah I thought this was still the "Conversation" screen. That's what 48 hours at the office can do, heh.
Thank you. Please understand, I'm not trying to be difficult My current workstation is dual E5-2696v3, 64gb, NVMe boot and NVMe data, SSD data storage, nothing spinning, no hyperV, everything real-time. It is used for hi-res video and photo work, all specialized, large scale time and cpu power consuming (not photoshop work, all custom), which was what led me to Windows Server 2016 and it's inherent advantages in processor scheduling and distributed usage (which you say PfW now has). I have taken the time to read what you have posted (and the entire thread, after all I started it ). Everything you've mentioned so far (while great improvements over Windows 10) are all a part of or a subset of Windows Server 2016. What I am asking boils down to - "Are there any advantage(s) to using PfW over Windows Server 2016 as a workstation OS, other than cost". Since I already own Windows Server 2016, cost is not a factor. Are you familiar enough with Windows Server 2016? Have you encountered any improvements over what Windows Server 2016 offers? Thank you for your time.
I never thought you were being difficult, heh. There is a significant lack of any viable information about this flavor of Windows 10 in regards to actual performance differences. As for your question: I, too, have a sever that's quite stout, and between the two there is no question that I would continue to run Windows Server 2016. That said, I also use it as a sever, and it runs anything with internet access from virtual machines to isolate them from the actual physical server hardware entirely. Now here is where your decision would be a very easy one to make. I would personally have no issues using Server 2016 (or even 2012 R2) as a desktop OS on a device other than either of my workstation devices. I say that because in a workstation environment, PfW will blow Server 2016 out of the water. You must remember that workstations are designed for pure power output due to the multiple high-load processes the end-user will be generally running on them - from CAD/graphical design, audio and video editing and creation, high-density datamining to multiple script invocations with large overheads and processing requirements like debugging, unattended testing of functions, files, etc. On the other hand, a server is not designed for that type of environment and PfW has a very clear advantage over Server 2016 when it comes to running it on what it's designed for - a workstation. Lastly, from what you wrote, the fact you do high-resolution video and photo work on it and long and intensive processes that utilize your cores on a large scale, I would personally say switching should be a no-brainer and you will indeed notice a major difference. Workstation PCs do not play well with server OS' and are often suffocated by them.
That was the kind of info I was seeking, but couldn't find. I'm guessing 90% or more of the PfW installs are the same as the Datacenter installs - vanity. I'm going to give PfW a try once my current project list is finished in about 15-16 workdays. I have some interesting projects coming up that should give good time/scale comparisons. Thank you.
I visit this thread occasionally yet lost track of the post with the instructions to activate/upgrade to ProWS. Going to read the thread again. It would be nice if it could be listed in the OP.
16251 > 16288 can be activated by the non gVLK from the product.ini from the mentioned builds and next you can upgrade to newer builds or generate a genuineticket.xml and clean install a desired build.
Thank you! 16251, 16288 are Insider Preview builds right? I don't have any Insider Previews downloaded.
Yup, I did it because I could, and it is linked to my Microsoft Account. Pro for Workstations Insider Preview looks real nice in the bottom right-hand corner!
Thanks for the help. But I can't seem to find 16288 in the downloader. There is 16281.1000 and 16278.1000. Will any of these do?
Just to confirm with all you who has Windows 10 Pro for WS installed, you still aren't able to receive windows updates right? that's a long wait to have this fixed until RS4 arrives
There is no fault, so nothing to fix, it probably will be released officially when rs4 goes official.
Digital License for Pro for Workstations Do Method "A" and Method "B" work? Concrete example: Current OS Build: 10586 Pro (can be whatever) Activate as Pro for Workstations Build: 16278 (must be 16251 > 16288) Upgrade Build: 16299 (can be 16299 > 17083+) Method "A" - In place upgrade Current OS: 10586 Pro with lifetime digital license Use UUP to get CORE 16278 Convert 16278 CORE to 16278 Pro for Workstations In place upgrade 10586 Pro to 16278 Pro for Workstations Go to Final Steps Method "B" - license switch Current OS: 10586 Pro with lifetime digital license Use UUP to get Pro 16278 In place upgrade 10586 Pro to 16278 Pro Reactivate 16278 Pro as 16278 Pro for Workstations using the the Pro for Workstations key found in the product.ini Go to Final Steps Final Steps Check if you still have an active digital license Gather the State of new Pro for Workstations digital license (save this somewhere) Use UUP to get newest 16299 Convert 16299 to Pro for Workstations Do clean install of 16299 Pro for Workstations Inject your saved Gather the State of new Pro for Workstations lifetime digital license Done If Method B is correct, what are the recommended steps to: "Reactivate 16278 Pro as 16278 Pro for Workstations using the the Pro for Workstations key found in the product.ini"?
I really don't get what 10586 or any other non Pro-WS install has to do with it? Just install 16278 pro-ws, activate it by using the product.ini non gVLK pro-WS key and upgrade to a more current pro-ws and it will have a free hwid. gatherosstate.exe also generates a working genuineticket.xml.
My brain isn't/wasn't working ... I'm trying to incorporate the previous digital license that is tied to the PC hardware New Method Save the genuineticket.xml for the digitally licensed PC you're upgrading to Pro for Workstations Clean install 16278 Pro onto your PC Apply your previously saved genuineticket.xml You now have a digitally licensed copy of 16278 Pro Activate (upgrade?) 16278 Pro to 16278 Pro for Workstations using non gVLK pro-WS key ProfessionalWorkstation=XXXX-7YMDX 16278 Pro > 16278 Pro for Workstations Run gatherosstate.exe to generate a new genuineticket.xml for Pro for Workstations Clean install pre-converted 16299 Pro for Workstations Inject your newly made genuineticket.xml that is for Pro for Workstations Done Is this right?