So now that I'm more/less starting from scratch I thought it would be a great time to try an in-place upgrade of server 2016 to 2019! HOW EXCITING! I do have some software I will running on my C: including SQL server so it will be interesting to see what still works after the upgrade. Now that I have some new drives and I can now setup a backup solution for some of my dev work!
Following the guide from microsoft. https://docs.microsoft.com/en-us/windows-server/upgrade/upgrade-2016-to-2019
I saved the info they requested to a network drive and a flash drive.
open the cmd prompt and cd to
c:\Windows\system32, and then type systeminfo.exe.
Results from running systeminfo.exe.
Host Name: "MY WORKSTATION"
OS Name: Microsoft Windows Server 2016 Standard
OS Version: 10.0.14393 N/A Build 14393
OS Manufacturer: Microsoft Corporation
OS Configuration: Standalone Server
OS Build Type: Multiprocessor Free
Registered Owner: Windows User
Product ID: xxxxx-xxxxx-xxxxx-xxxxx
Original Install Date: 2018-06-18, 6:36:57 AM
System Boot Time: 2020-02-26, 9:58:13 AM
System Manufacturer: COMPUTER INC.
System Model: WORKSTATION
System Type: x64-based PC
Processor(s): 2 Processor(s) Installed.
: ~1200 Mhz
: ~1200 Mhz
BIOS Version: American Megatrends Inc.
Windows Directory: C:\Windows
System Directory: C:\Windows\system32
Boot Device: \Device\HarddiskVolume4
System Locale: en-ca;English (Canada)
Input Locale: en-us;English (United States)
Time Zone: (UTC-07:00) Mountain Time (US & Canada)
Total Physical Memory: 130,958 MB
Available Physical Memory: 115,100 MB
Virtual Memory: Max Size: 150,414 MB
Virtual Memory: Available: 132,449 MB
Virtual Memory: In Use: 17,965 MB
Page File Location(s): C:\pagefile.sys
Domain: "MY DOMAIN"
Logon Server: \\LoginServer
Hotfix(s): 14 Hotfix(s) Installed.
NETWORK INFORMATION Gets listed with all details about your networks connected, such as VLAN Tags, IPs, etc
Hyper-V Requirements: A hypervisor has been detected. Features required for Hyper-V will not be displayed.
Run and save the information from ipconfig /all
RESULTS FROM IPCONFIG
Windows IP Configuration
Host Name . . . . . . . . . . . . : "My Workstation"
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : Domain1
All you networking information gets listed here starting with your default NETWORK and it lists all vlan tags, mac addresses, much as you would expect from the
"ipconfig /all" command.
Record 2 registry key entries. BuildLabEx (version) and EditionID (edition)
I did a Registry Keys Export for a Backup and a screen shot for reference
I saved the upgrade info to a text file on the flash drive along with a screen shot of the registry and an export of the current version key.
I create upgrade media using rufus, then ran the installer as an administrator
NOTE: You will need your server key when you upgrade
First it will check for updates, if there are none it will move on
then it will check and see if your ready to install, checking for enough disk space etc. Here is where you will be asked for your product key
Then you will need to select your version of server in this case I'm picking (Desktop Experience)
Accept the notices and license terms
Then it will ask you to install windows
So to fix this problem; you need to edit a registry entry "AllowInsecureGuestAuth"
located here (you can copy and paste the path into regedit):
The update change the REG_DWORD to 0
|AllowInsecureGuestAuth Value after upgrade|
You need to change the value to 1 if you want to be able to access unauthenticated shares.
|Change the REG_DWORD to 1 to allow access to unauthenticated shares|
you can read the reference link below with the details.
Microsoft is defaulting on the side of security which I completely applaud them for; however I do have to re-enable unauthenticated access.
It was also shortly after fixing my network share issue I noticed some issues with most of my virtual networks with most of my networks showing an error.
|Most networks no longer work after upgrade.|
After doing a clean install of Server 2019, setting up the dual port nic into a teamed interface I still lost network connectivity after installing the Hyper-V roll. This happened after I reinstalled another 2 times. What I didn't realize even looking though forums this issue was hard to find a resolution to. The only solution that worked for me was to follow this process I found on Microsoft Technet
- I had to remove Hyper-V role
- Run netcfg -d in a privileged powershell console
- I made sure I setup all my teamed networks after this
- Install Hyper-v role