Comments (0) The quick fix is “Set-NetConnectionProfile –Name “Unidentified network” -NetworkCategory Private” but it won’t sustain as it will change back to Public profile after reboot.
So the easiest way to trick Windows is to assign Unidentified network property to Private!
The solution is quite easy with PowerShell
New-SelfSignedCertificate -CertStoreLocation Cert:\LocalMachine\My -DnsName “stargate.domainname.com” -FriendlyName “Stargate” -NotAfter (Get-Date).AddYears(20)
Using certmgr, make sure copy it from Personal Certificates to the Trusted Root Certification Authorities, or it won’t appear in IIS Server Certification.
Simply add the following lines to VM options
tools.syncTime 0
time.synchronize.continue 0
time.synchronize.restore 0
time.synchronize.resume.disk 0
time.synchronize.shrink 0
time.synchronize.tools.startup 0
time.synchronize.tools.enable 0
time.synchronize.resume.host 0
Seems the old Windows Server 2003 is having trouble with recent SEP v12.1 virus definition updates.
Solution is simple by restarting the SEP service.
smc -stop
smc -start
Then manually update the definition will solve all the question marks.
As expected, the installation process is almost identical to Windows Server 2012 and 2016. The key is to use BIOS version SLIC 2.5.
Except I’ve encountered a tricky problem that the valid license key won’t activate, it returns with “windows server 2019 error -xc004f069″.
It turns out the the source ISO is an evaluation copy, so all you have to do is to convert the Eval copy to Retail version by:
DISM /Online /Set-Edition:ServerStandard /ProductKey:xxxxx-xxxxx-xxxxx-xxxxx-xxxxx /AcceptEula
To determine upgrade path and other available edition:
DISM /online /Get-TargetEditions
For the evaluation/retail version of Windows Server 2016 Standard, you can also convert to the retail version of Windows Server 2016 Data Center using the same command and the appropriate product key.
DISM /Online /Set-Edition:ServerDatacenter /ProductKey:xxxxx-xxxxx-xxxxx-xxxxx-xxxxx /AcceptEula
Update: Apr 11, 2021
It turns out VM will lost its customized CPUID parameter after Veeam backup restoration, BIOS SLIC 2.5 parameter holds though.
So you have to add it back again, or the VM will keep crashing every now and then.
However, if the VM is deployed via template, then there is no problem at all.
This is another powerful documentary besides An Inconvenient Truth (2006), and it’s the most shocking “witness statement” from Sir David Attenborough.
If we don’t take action, the collapse of our civilization and the extinction of much of the natural world is on the horizon. … The natural world is fading, the evidence is all around… (But) if we act now, we can yet put it right.
System drive is filling up with all the unncessary hotfix files and cannot be removed? Finally the most important piece of system cleanup tools shows up in Windows Server 2008 R2
All you need to do is to copy the following two files into corresponding locations!
Cleanmgr.exe should go in %systemroot%\System32.
Cleanmgr.exe.mui should go in %systemroot%\System32\en-US.
You can now launch the Disk cleanup tool by running Cleanmgr.exe from the command prompt.
