does somebody know if wfw is supporting windows10 enterprise GPO-settings? like gpo-settings to send ZERO telemetry-data to MS? They are ignored on any professional install! I could not imagine, MS is releasing a workstation version without supporting it. also, wfw is calling smb-direct (with rdma-support) as a feature only for this version, and I am wondering, why its available as an installable feature on every professional install as well. there may be a difference on the client/server-role implementation. can a workstation act as an rdma-enabled server? MS didn't release any info to these questions as far as my knowledge goes. Can you shed some light on to this?
------------------------------------------- - Basic OEM Information For This Computer - ------------------------------------------- OS Version {WMIC} - Microsoft Windows 10 Pro for Workstations x64 OS Edition {Registry} - ProfessionalWorkstation OS Edition {CBS} - ProfessionalWorkstation OS Build Number - 16299 OS Update Build Revision - 15 {Baseline Release} OS Language Name/Code - en-US / Dec:1033 {Hex:409} =======================================[ Basic OEM Information For This Computer ]======================================= OS Version {SKU} - Windows 10 Pro for Workstations {161} OS Edition {Registry} - ProfessionalWorkstation {161} OS Edition {CBS} - Professional OS Architecture - 64 Bit OS Build/Update Revision - 17133 {rs4_release} / 1 OS Installation Type - Client OS Language Name/Code - en-US / Dec:1033 {Hex:409} Why the difference?
Get-CimInstance -Class Win32_OperatingSystem + Get-WmiObject Win32_ComputerSystem $OSClass = Get-CimInstance -Class Win32_OperatingSystem $Computer = Get-WmiObject Win32_ComputerSystem Code: $OSClass.BootDevice $OSClass.BuildNumber $OSClass.Caption $OSClass.CSName $OSClass.Description $OSClass.Encryption $OSClass.NumberOfUsers $OSClass.Name $OSClass.Manufacturer $OSClass.Organization $OSClass.OSArchitecture $OSClass.OperatingSystemSKU $OSClass.ServicePackMajorVersion $OSClass.ServicePackMinorVersion Code: $Computer.AdminPasswordStatus $Computer.Caption $Computer.Domain $Computer.InstallDate $Computer.Manufacturer $Computer.Name $Computer.NumberOfLogicalProcessors $Computer.NumberOfProcessors etc. etc. etc. Instead of cluttering your PC with dopey executables that give subpar information.
Hi, Could anyone please advise - 1) has "Windows 10 Pro for Worstations" been released yet? if not, what is the release date? 2) how could I upgrade my Windows 10 Pro to it? Does it cost extra?? (I have digital license on my 1950x workstation) 3) I have threadripper 1950x (16-core) workstation with 32GB RAM and 1TB NVMe Drive. Do you think it's better to have workstation version on it? Thanks!
It is a virtual edition, on rs4 you can simply enter the non gVLK from product.ini on the running windows (home, pro, etcetc) and it will switch to Pro-WS. We''ll know if it finally gets official support as soon as the first RS4 updates are released. If you take the effort and read this thread you can find that 16251 <> 16288 can be retail activated by the non gVLK from their product.ini files and when upgraded to, or by generating a genuineticket and clean install, a more current build and you will get it for free.
Get-CimInstance -Class Win32_OperatingSystem + Get-WmiObject Win32_ComputerSystem versus MRP Windows PowerShell Copyright (C) Microsoft Corporation. All rights reserved. PS C:\Windows\system32> Get-CimInstance -Class Win32_OperatingSystem SystemDirectory Organization BuildNumber RegisteredUser SerialNumber Version --------------- ------------ ----------- -------------- ------------ ------- C:\Windows\system32 16299 Windows User 00391-70000-00000-AA208 10.0.16299 PS C:\Windows\system32> Get-WmiObject Win32_ComputerSystem Domain : WORKGROUP Manufacturer : Dell Inc. Model : Latitude E7240 Name : DESKTOP-994Q8BS PrimaryOwnerName : Windows User TotalPhysicalMemory : 8490696704 ............................................................................................................................................................................................................................................... Basic OEM Information For This Computer - ------------------------------------------- OS Name - Windows 10 Pro for Workstations x64 OS Edition {Registry} - ProfessionalWorkstation OS Edition {WMIC} - ProfessionalWorkstation OS Build Number - 16299 OS Update Build Revision - 15 {Baseline Release} OS Language Name/Code - en-US / Dec:1033 {Hex:409} OS Locale - en-US OS Language Value - ENU OS Installation Date - 27/03/2018 08:03:39 CPU Name - Intel{R} Core{TM} i5-4310U CPU @ 2.00GHz CPU Description - Intel64 Family 6 Model 69 Stepping 1 CPU Architecture - 32/64 Bit Instruction Set CPU Cores/Threads - [2] / [4] HDD Mode/Partition - [Undefined, possible customized chipset.] / [MBR] Bios Version - [A25, 02/01/2018] Total Physical Memory - [8097 Mb] Available Memory - [6305 Mb] GPU Primary Adaptor Name - [Intel{R} HD Graphics Family] -------------------- - Scanned DMI/BIOS - -------------------- #01 CSProduct Name - Latitude E7240 #09 SLIC Version - 2.1 #02 CSModel Name - Latitude E7240 #10 Product Key - Not Shown On Saved Report #03 CSBaseboard Prod - 0R6F3F #11 MSDM Key - Not Shown On Saved Report #04 CSProduct Vendor - Dell Inc. #11 MSDM Edition - Win 8.1 Professional #05 CSManufacturer - Dell Inc. #11 MSDM Brand Name - Dell #06 Baseboard MFR - Dell Inc. #12 BIOS/Boot Mode - Legacy/MBR #07 Serial/Service Tag - Not Shown On Saved Report #13 Certificate - XXXXXXXXXXXXX #08 BIOS or SLIC ID - DELL #14 License Status - Licensed {Retail/Digital License} ----------- - Summary - ----------- OEM Theme/Branding - Dell [id: #04] OEM Activation Vista/7 - Dell [id: #08] Valid OEM Consumer OS - Vista/Win7/Win8.x/Win10 Valid OEM Server OS - Server 2008/Server 2008R2 MSDM Check Method Used - {M1} .Net Versions Detected - v1.1.4322 v2.0.50727 v3.5 v4.0.30319 v4.7.02556 Powershell Version{s} - 1.0, 2.0, 3.0, 4.0, 5.0, 5.1 License Status Reason - 4004F401: The activation server reported that the computer has a valid Digital License. ** End of Query Tool report. ** Care to explain GodHand,which is dopey and subpar.We come at different levels.
Hello, I currently have a digital license for my motherboard by upgrading from Windows 7 Ultimate to Windows 10 Pro. Meaning I can clean install Windows 10 Pro and get activated online. Now, How I can have the same for Windows 10 Pro for Workstation? I tried using gatherosstate.exe on a KMS-activated installed copy of Pro for Workstation and it did not worked, although I got GenuineTicket.xml. Meaning I clean installed Pro for Workstation, activated it using abbodi's KMS activator, ran gatherosstate.exe, got the GenuineTicket.xml file, reinstalled Pro for Workstation and before going online, copied GenuineTicket.xml to C:\ProgramData\Microsoft\Windows\ClipSVC\GenuineTicket. I prefer to have digital license and not use the KMS method. So what should be done to get a digital license for Pro Workstation? Maybe it's not possible at all and I'm just wasting time? Thanks.
All 17133.xxx non Home installs will show CBS Enterprise (let me recheck this statement ). And now with 17133.1 Pro-WS accepts the updates
Correction: Code: =======================================[ Basic OEM Information For This Computer ]======================================= OS Version {SKU} - Windows 10 Pro for Workstations N - x64 {162} OS Edition {Registry} - ProfessionalWorkstationN {162} OS Edition {CBS} - ProfessionalN OS Build Information - 17133 {rs4_release} / UBR: 73 / OSType: Client OS Language Name/Code - nl-NL / Dec:1043 {Hex:413} OS Locale/Language Value - nl-NL / NLD OS Installation Date - 10-4-2018 21:07:47 {Localized Date Format} CPU Name - Intel{R} Core{TM} i7-3770 CPU @ 3.40GHz { } CPU Description - Intel64 Family 6 Model 58 Stepping 9 CPU Architecture/ID Code - 32/64 Bit / [1F8BFBFF000306A9] CPU Cores/Threads/Skts/VT - [2] / [2] / [1] / Virtualization: [Disabled] Meltdown/Spectre Results - This system is vulnerable to Spectre only. {See Saved Report} Boot Drive Information - BusType: SAS, Mode: SAS/SCSI{S}, Partition: MBR, DriveType: HDD, FS: NTFS Boot Drive Model Name - VMware Virtual S BIOS Information - Type: Phoenix Technologies LTD , Version: 6.00 , Date: 05/19/2017 MEMORY Total/Available - [4095 Mb] / [2613 Mb] GPU Primary Adaptor Name - VMware SVGA 3D GPU Primary Adaptor Info - Resolution: 1024x768 , Driver Date: 02/03/2017 , Driver Vers: 8.15.1.60 ==================================================[ Scanned DMI/BIOS ]================================================== #01 CSProduct Name - VMware Virtual Platform #09 SLIC Information - No SLIC Table Detected #02 CSModel Name - VMware Virtual Platform #10 Product Key - Not shown by choice #03 CSBaseboard Prod - 440BX Desktop Reference Platfo #11 MSDM Key - No MSDM Table Detected #04 CSProduct Vendor - VMware, Inc. #11 MSDM Edition - Undefined #05 CSManufacturer - VMware, Inc. #11 MSDM Brand Name - Undefined #06 Baseboard MFR - Intel Corporation #12 BIOS/Boot Mode - Legacy/MBR #07 Serial/Service Tag - VMware-56 #13 Certificate - Not Present #08 BIOS or SLIC ID - INTEL - 6040000 #14 License Status - Licensed {0x4004F401} =======================================================[ Summary ]======================================================= OEM Theme/Branding - VMWARE [id: VMware] OEM Activation {V/7} - Un-Listed Valid OEM Consumer OS - Un-Listed Detected .Net Versions - v1.1.4322 / v2.0.50727 / v3.5 / v4.0.30319 / v4.7.03056 Powershell Version{s} - 1.0, 2.0, 3.0, 4.0, 5.0, 5.1 License Status Text - This computer has a valid Digital/Store License. > Save 'QTv54.0_Report.txt' before closing? {NOTE: Does not show keys in saved report}, Type {Y/N} then press ENTER: