Thank you for writing this article. I wrote all my own Powershell code to install VMs, but on the free Hypervisor-only platform. IMO, it is pointless to host VMs on a GUI based server. The command line based server has far less bloat and better security.
If you’re creating complex PowerShell scripts like this, you should already be aware that setting the AllowTelemetry key in the registry, will have the same effect as using the Local Group Policy Editor to set one on of the 4 allowed levels of Data Reporting. You should also be aware that setting it to Zero is only possible on Windows Enterprise and if you choose to do it anyway…. for example, if you set this key to 0 on a Windows Pro copy…. the system will revert to the level of Diagnostic Data that Microsoft sees fit, and this effect will be invisible. You can verify what I’m telling you by simply visiting the relevant Group Policy, setting it to 4 then refresh Regedit (press F5) and watch as the AllowTelemetry key changes to 4. If you’re not on Enterprise then then 1 is the lowest setting you can use.
Basically, if you don’t know what you’re doing by poking around in the registry, you may very well be enabling more Telemetry while you think you’re turning it off.
Local Group Policy: Computer ConfigurationAdministrative TemplatesWindows ComponentsData Collection and Preview BuildsAllow Telemetry (it tells you that you can only set 0 if you’re running Enterprise.)
*I’d never recommend that anybody run a script that automatically makes a bunch of changes to their Windows in the hopes of tuning it for privacy reasons. The best thing to do is do the research yourself and understand what it is that you’ll be changing.
Hi, I installed Windows Server 2016 on my computer, and when I installed it, it asked me which Windows to select. I also selected Windows Server Dasta Center, and after installing Windows on my computer, it asks me I need the administrator password. I do not know, but I do not know what the password. Please help me, thank you
1. Navigate to C:windowssystem32 and search for the Sysprep folder, go to properties and change the ownership of the folder to the local admin by changing the permissions in the Advance menu. 2. After you take the ownership of the folder you can open sysprepactionfiles and edit the Generalize.xml and remove the following entry from there:
3. Save as the Generalize.xml on any desired location and then rename the existing Generalize.xml to old and replace it with the new one. 4. Run sysprep Generalize and see if that works for you.
Sometimes unexpected changes can have beneficial effects.
I run a Server 2019 VM on my daily driver Win10 laptop, which allows me to use WSUS for my home domain by collecting updates where data is cheaper.
I have been progressively increasing the VM’s RAM allocation to get better performance, but adding a third virtual processor improved things enormously, to the point where I could reduce its RAM by half a gigabyte.
That might not seem a lot, but don’t forget that the VM is competing with the “normal” tasks on that laptop.
I have to conclude that the extra “processor” allows the VM to shift its workload more easily, avoiding having to queue things up in memory awaiting the resource.
The laptop does not seem to suffer much from allocating more CPU time to the VM.
In fact, I’ll also be using it for a code to extract the value of InterfaceIndex (thru Get-Netadapter). But how do I get the value/s of the property/ies (like InterfaceIndex and InterfaceAlias) of Get-Netadapter and use it/them, say move the value/s to a variable/s?