
Contents
As a follow-up to my world-renown Web browser telemetry article, which I will update soon, I promise, I decided to do a similar test to see which Windows edition and version performs the most network connections (and where to) after a default install.
Methodology
The test hardware is an Apple (yeah, I know) MacBook Air 2012 (CPU: i7 @ 2.0GHz, RAM: 8GB, SSD: 512GB), running macOS Catalina (yeah, I know) and Parallels Desktop (so all the installs are done inside separate virtual machines). Network filtering and logging is done using Little Snitch and application-level whitelisting, basically I get a trigger for each connection and I can choose to block or allow it: all connections are allowed and logged. Also, the install is done in a default way, manual (not unattended), I’m not modifying the default options in any way (for example, you have the option to alter some privacy options, but by default the toggles are on and they will stay on). I’m not creating or logging into a Microsoft account (not like I have one), so the default user is local (yeah, you know).
On the Parallels side, all VMs are created with 4GB of assigned RAM, isolated from the host system. Network connection are logged from the first boot to desktop after the installation (not during setup) and all network traffic is routed through a VPN in Sweden.
Not all network connections should be considered spyware or telemetry, some are legitimate (for example, Windows Update), though personally I consider all default connections as spyware/telemetry, unless I press a big red button that says “Connect to Microsoft”.
I installed the Consumer and Business editions of Windows 11 and 10 (General Availability Channel, GAC for short), as well as IoT Enterprise (Long-Term Servicing Channel, LTSC for short) edition of both Windows 11 and 10, which is a favorite among privacy enthusiasts that have to use Windows for some reason (mostly retro gaming), but keep in mind that telemetry options for LTSC are the same as GAC Enterprise.
If you’re into Windows Server, I got it covered too by testing Windows Server 2025 (based on Windows 11 codebase), Windows Server 2019 (based on Windows 10), Windows Server 2012 R2 (based on Windows 8.1) and Windows Server 2008 R2 (based on Windows 7 codebase).

All ISOs are official, legitimate, genuine downloads from the Microsoft website and you can compare the hashes if you’re inclined to do so. If you’re wondering what’s the difference between Consumer and Business editions, it’s very simple: the Consumer ISOs includes all editions such as Home, Pro, and Education, but excludes the Enterprise edition; in contrast, the Business ISOs contains all editions except for the Home-level editions, and these ISO files come with a KMS key pre-installed, but not activated, by default. I guess I should have installed the Home editions too, but I guess the difference between Home and Pro (regarding network connections) would be minimal.
Additionally, LTSC (Long-Term Servicing Channel) editions are designed for devices where functionality and features must remain constant over time, such as medical systems, industrial controllers, and air traffic control devices. Maximum support is 10 years for the IoT LTSC edition, which means that Windows 10 IoT Enterprise LTSC is supported until 2032.
Last but not least, I’m doing the same test with several legacy Windows virtual machines, not like I recommend anyone to use those for daily activities unless you know what you’re doing. Just for fun, I guess.
There are no direct links to the official ISOs here, but you can always check our trusted friends.
Some observations are in order:
- Windows 11 IoT Enterprise LTSC 2024 and Windows 11 Enterprise are the only tested versions that open network connections to Google servers. I didn’t bother to check why, feel free to dig deeper.
- Be absolutely sure Microsoft knows at what time each day your IP goes online and at which time it goes offline.
- Long gone are the days of Windows 7.
- As the Spanish say, “Cría cuervos y te sacarán los ojos”, raise ravens and they will gouge your eyes out.
- I’m surprised by Windows 7 to be honest, but I guess the telemetry comes after you update the system. Still it’s a long way to the level of telemetry in modern Windows versions. Strange that Windows Update didn’t kick in.
- Windows 10 IoT Enterprise LTSC is a clear winner. Unfortunately, there are no winners here, only losers (or loosers, for my “American”-speaking friends).
- Somebody probably could make some charts regarding which of the hostnames is the most active in every edition of Windows, and other similar goodies, but that somebody ain’t me.
Charts
Windows 11 is the latest major release of Microsoft’s Windows NT operating system, released on October 5, 2021. It succeeded Windows 10 (2015).

Windows 11 Consumer 24H2
- Build: 26100.1742 (RTM)
- Edition: Windows 11 Pro
- Arch: x64
- ISO:
Win11_24H2_EnglishInternational_x64.iso - Hashes: here
- Network connections: 68
click here for the list of network connections
www.msftconnecttest.com on TCP port 80
login.live.com on TCP port 443
v10.events.data.microsoft.com on TCP port 443
watson.events.data.microsoft.com on TCP port 443
settings-win.data.microsoft.com on TCP port 443
v20.events.data.microsoft.com on TCP port 443
ctldl.windowsupdate.com on TCP port 80
config.edge.skype.com on TCP port 443
msedge.api.cdp.microsoft.com on TCP port 443
wdcp.microsoft.com on TCP port 443
www.bing.com on TCP port 443
officeclient.microsoft.com on TCP port 443
fp.msedge.net on TCP port 443
g.live.com on TCP port 443
oneclient.sfx.ms on TCP port 443
client.wns.windows.com on TCP port 443
fd.api.iris.microsoft.com on TCP port 443
storeedgefd.dsx.mp.microsoft.com on TCP port 443
ocsp.digicert.com on TCP port 80
crl3.digicert.com on TCP port 80
to-do.microsoft.com on TCP port 443
slscr.update.microsoft.com on TCP port 443
config.teams.microsoft.com on TCP port 443
oneocsp.microsoft.com on TCP port 80
www.microsoft.com on TCP port 80
graph.microsoft.com on TCP port 443
logincdn.msauth.net on TCP port 443
geo.prod.do.dsp.mp.microsoft.com on TCP port 443
lgincdnvzeuno.azureedge.net on TCP port 443
go.microsoft.com on TCP port 443
res.cdn.office.net on TCP port 443
tse1.mm.bing.net on TCP port 443
res.public.onecdn.static.microsoft on TCP port 443
to-do.office.com on TCP port 443
kv601.prod.do.dsp.mp.microsoft.com on TCP port 443
teams.microsoft.com on TCP port 443
arc.msn.com on TCP port 443
windows.msn.com on TCP port 443
assets.msn.com on TCP port 443
staticview.msn.com on TCP port 443
edge.microsoft.com on TCP port 443
browser.events.data.msn.com on TCP port 443
ecs.office.com on TCP port 443
msedge.b.tlu.dl.delivery.mp.microsoft.com on TCP port 80
displaycatalog.mp.microsoft.com on TCP port 443
fe3cr.delivery.mp.microsoft.com on TCP port 443
geover.prod.do.dsp.mp.microsoft.com on TCP port 443
cp601.prod.do.dsp.mp.microsoft.com on TCP port 443
outlook.office.com on TCP port 443
login.microsoftonline.com on TCP port 443
dl.delivery.mp.microsoft.com on TCP port 80
tlu.dl.delivery.mp.microsoft.com on TCP port 80
outlook-sdf.office.com on TCP port 443
nav-edge.smartscreen.microsoft.com on TCP port 443
fs.microsoft.com on TCP port 443
data-edge.smartscreen.microsoft.com on TCP port 443
assets.msn.com on UDP port 443
api.msn.com on TCP port 443
srtb.msn.com on TCP port 443
img-s-msn-com.akamaized.net on TCP port 443
th.bing.com on TCP port 443
cdn.storeedgefd.dsx.mp.microsoft.com on TCP port 443
ev2-ring.msedge.net on TCP port 443
wac-ring.msedge.net on TCP port 443
t-ring.msedge.net on TCP port 443
odinvzc.azureedge.net on TCP port 443
download.windowsupdate.com on TCP port 80
au.download.windowsupdate.com on TCP port 80

Windows 11 Business 24H2
- Build: 26100.1742 (RTM)
- Edition: Windows 11 Enterprise
- Arch: x64
- ISO:
en-us_windows_11_business_editions_version_24h2_x64_dvd_59a1851e.iso - Hashes: here
- Network connections: 60
click here for the list of network connections
www.msftconnecttest.com on TCP port 80
login.live.com on TCP port 443
officeclient.microsoft.com on TCP port 443
config.edge.skype.com on TCP port 443
edge.microsoft.com on TCP port 443
edge-mobile-static.azureedge.net on TCP port 443
clients2.google.com on TCP port 443
settings-win.data.microsoft.com on TCP port 443
clients2.googleusercontent.com on TCP port 443
to-do.microsoft.com on TCP port 443
ctldl.windowsupdate.com on TCP port 80
msedgeextensions.sf.tlu.dl.delivery.mp.microsoft.com on TCP port 443
www.googleapis.com on TCP port 443
g.live.com on TCP port 443
ocsp.digicert.com on TCP port 80
config.edge.skype.com on UDP port 443
crl3.digicert.com on TCP port 80
slscr.update.microsoft.com on TCP port 443
fs.microsoft.com on TCP port 443
www.microsoft.com on TCP port 80
graph.microsoft.com on TCP port 443
msedge.b.tlu.dl.delivery.mp.microsoft.com on TCP port 80
config.teams.microsoft.com on TCP port 443
clientconfig.passport.net on TCP port 443
events.data.microsoft.com on TCP port 443
logincdn.msauth.net on TCP port 443
to-do.office.com on TCP port 443
fe2cr.update.microsoft.com on TCP port 443
oneclient.sfx.ms on TCP port 443
www.bing.com on TCP port 443
fd.api.iris.microsoft.com on TCP port 443
client.wns.windows.com on TCP port 443
assets.msn.com on TCP port 443
windows.msn.com on TCP port 443
licensing.mp.microsoft.com on TCP port 443
staticview.msn.com on TCP port 443
browser.events.data.msn.com on TCP port 443
assets.msn.com on UDP port 443
deff.nelreports.net on TCP port 443
chromewebstore.googleapis.com on TCP port 443
api.msn.com on TCP port 443
srtb.msn.com on TCP port 443
img-s-msn-com.akamaized.net on TCP port 443
download.windowsupdate.com on TCP port 80
th.bing.com on TCP port 443
data-edge.smartscreen.microsoft.com on TCP port 443
oneocsp.microsoft.com on TCP port 443
fe3cr.delivery.mp.microsoft.com on TCP port 443
geo.prod.do.dsp.mp.microsoft.com on TCP port 443
kv601.prod.do.dsp.mp.microsoft.com on TCP port 443
au.download.windowsupdate.com on TCP port 80
edgeassetservice.azureedge.net on TCP port 443
go.microsoft.com on TCP port 443
cp601.prod.do.dsp.mp.microsoft.com on TCP port 443
dl.delivery.mp.microsoft.com on TCP port 80
tlu.dl.delivery.mp.microsoft.com on TCP port 80
r.bing.com on TCP port 443
weathermapdata.blob.core.windows.net on TCP port 443
arc.msn.com on TCP port 443
geover.prod.do.dsp.mp.microsoft.com on TCP port 443

Windows 11 IoT Enterprise LTSC 2024
- Build: 26100.1742
- Edition: Windows 11 IoT Enterprise LTSC
- Arch: x64
- ISO:
en-us_windows_11_iot_enterprise_ltsc_2024_x64_dvd_f6b14814.iso - Hashes: here
- Network connections: 41
click here for the list of network connections
www.msftconnecttest.com on TCP port 80
settings-win.data.microsoft.com on TCP port 443
officeclient.microsoft.com on TCP port 443
login.live.com on TCP port 443
slscr.update.microsoft.com on TCP port 443
edge.microsoft.com on TCP port 443
config.edge.skype.com on TCP port 443
clients2.google.com on TCP port 443
edge-consumer-static.azureedge.net on TCP port 443
ctldl.windowsupdate.com on TCP port 80
msedge.api.cdp.microsoft.com on TCP port 443
ocsp.digicert.com on TCP port 80
msedgeextensions.sf.tlu.dl.delivery.mp.microsoft.com on TCP port 443
fs.microsoft.com on TCP port 443
crl3.digicert.com on TCP port 80
clients2.googleusercontent.com on TCP port 443
msedge.b.tlu.dl.delivery.mp.microsoft.com on TCP port 80
www.googleapis.com on TCP port 443
geo.prod.do.dsp.mp.microsoft.com on TCP port 443
kv601.prod.do.dsp.mp.microsoft.com on TCP port 443
client.wns.windows.com on TCP port 443
cp601.prod.do.dsp.mp.microsoft.com on TCP port 443
fd.api.iris.microsoft.com on TCP port 443
licensing.mp.microsoft.com on TCP port 443
dl.delivery.mp.microsoft.com on TCP port 80
fe2cr.update.microsoft.com on TCP port 443
edgeassetservice.azureedge.net on TCP port 443
v10.events.data.microsoft.com on TCP port 443
v20.events.data.microsoft.com on TCP port 443
download.windowsupdate.com on TCP port 80
prod.client.wosc.services.microsoft.com on TCP port 443
www.bing.com on TCP port 443
geover.prod.do.dsp.mp.microsoft.com on TCP port 443
fe3cr.delivery.mp.microsoft.com on TCP port 443
au.download.windowsupdate.com on TCP port 80
go.microsoft.com on TCP port 443
tlu.dl.delivery.mp.microsoft.com on TCP port 80
arc.msn.com on TCP port 443
chromewebstore.googleapis.com on TCP port 443
cacerts.digicert.com on TCP port 80
wdcp.microsoft.com on TCP port 443
Windows 10
Windows 10 is a major release of Microsoft’s Windows NT operating system. The successor to Windows 8.1, it was released to manufacturing on July 15, 2015, and later to retail on July 29, 2015.

Windows 10 Consumer 22H2
- Build: 19045.5131
- Edition: Windows 10 Pro
- Arch: x64
- ISO:
en-us_windows_10_consumer_editions_version_22h2_updated_nov_2024_x64_dvd_3eeacab9.iso - Hashes: here
- Network connections: 47
click here for the list of network connections
www.msftconnecttest.com on TCP port 80
slscr.update.microsoft.com on TCP port 443
time.windows.com on UDP port 123
ctldl.windowsupdate.com on TCP port 80
config.edge.skype.com on TCP port 443
displaycatalog.mp.microsoft.com on TCP port 443
v10.events.data.microsoft.com on TCP port 443
v20.events.data.microsoft.com on TCP port 443
fe3cr.delivery.mp.microsoft.com on TCP port 443
watson.events.data.microsoft.com on TCP port 443
fp.msedge.net on TCP port 443
www.bing.com on TCP port 443
ocsp.digicert.com on TCP port 80
g.live.com on TCP port 443
inference.location.live.net on TCP port 443
oneclient.sfx.ms on TCP port 443
settings-win.data.microsoft.com on TCP port 443
login.live.com on TCP port 443
config.teams.microsoft.com on TCP port 443
logincdn.msauth.net on TCP port 443
cxcs.microsoft.net on TCP port 443
fe2cr.update.microsoft.com on TCP port 443
lgincdnvzeuno.azureedge.net on TCP port 443
download.windowsupdate.com on TCP port 80
crl3.digicert.com on TCP port 80
tsfe.trafficshaping.dsp.mp.microsoft.com on TCP port 443
geo-prod.do.dsp.mp.microsoft.com on TCP port 443
3.au.download.windowsupdate.com on TCP port 80
kv601.prod.do.dsp.mp.microsoft.com on TCP port 443
cp601.prod.do.dsp.mp.microsoft.com on TCP port 443
geover.prod.do.dsp.mp.microsoft.com on TCP port 443
9.au.download.windowsupdate.com on TCP port 80
2.au.download.windowsupdate.com on TCP port 80
dl.delivery.mp.microsoft.com on TCP port 80
3.tlu.dl.delivery.mp.microsoft.com on TCP port 80
msedge.api.cdp.microsoft.com on TCP port 443
msedge.b.tlu.dl.delivery.mp.microsoft.com on TCP port 80
9.tlu.dl.delivery.mp.microsoft.com on TCP port 80
msedge.f.dl.delivery.mp.microsoft.com on TCP port 80
fs.microsoft.com on TCP port 443
go.microsoft.com on TCP port 443
fd.api.iris.microsoft.com on TCP port 443
clientconfig.passport.net on TCP port 443
client.wns.windows.com on TCP port 443
licensing.mp.microsoft.com on TCP port 443
arc.msn.com on TCP port 443
prod.client.wosc.services.microsoft.com on TCP port 443
ris.api.iris.microsoft.com on TCP port 443

Windows 10 Business 22H2
- Build: 19045.5131
- Edition: Windows 10 Enterprise
- Arch: x64
- ISO:
en-us_windows_10_business_editions_version_22h2_updated_nov_2024_x64_dvd_60ca6446.iso - Hashes: here
- Network connections: 51
click here for the list of network connections
www.msftconnecttest.com on TCP port 80
api.msn.com on TCP port 443
slscr.update.microsoft.com on TCP port 443
settings-win.data.microsoft.com on TCP port 443
login.live.com on TCP port 443
www.bing.com on TCP port 443
g.live.com on TCP port 443
ctldl.windowsupdate.com on TCP port 80
ocsp.digicert.com on TCP port 80
v20.events.data.microsoft.com on TCP port 443
msedge.api.cdp.microsoft.com on TCP port 443
crl3.digicert.com on TCP port 80
cdn.onenote.net on TCP port 443
crl4.digicert.com on TCP port 80
msedge.b.tlu.dl.delivery.mp.microsoft.com on TCP port 80
maps.windows.com on TCP port 443
fe2cr.update.microsoft.com on TCP port 443
go.microsoft.com on TCP port 443
v10.events.data.microsoft.com on TCP port 443
clientconfig.passport.net on TCP port 443
download.windowsupdate.com on TCP port 80
displaycatalog.mp.microsoft.com on TCP port 443
client.wns.windows.com on TCP port 443
licensing.mp.microsoft.com on TCP port 443
checkappexec.microsoft.com on TCP port 443
oneocsp.microsoft.com on TCP port 80
apprep.smartscreen.microsoft.com on TCP port 443
prod.client.wosc.services.microsoft.com on TCP port 443
fp.msedge.net on TCP port 443
inference.location.live.net on TCP port 443
self.events.data.microsoft.com on TCP port 443
nav.smartscreen.microsoft.com on TCP port 443
oneclient.sfx.ms on TCP port 443
data-edge.smartscreen.microsoft.com on TCP port 443
fd.api.iris.microsoft.com on TCP port 443
config.edge.skype.com on TCP port 443
cxcs.microsoft.net on TCP port 443
config.teams.microsoft.com on TCP port 443
geo-prod.do.dsp.mp.microsoft.com on TCP port 443
arc.msn.com on TCP port 443
ris.api.iris.microsoft.com on TCP port 443
logincdn.msauth.net on TCP port 443
lgincdnvzeuno.azureedge.net on TCP port 443
fe3cr.delivery.mp.microsoft.com on TCP port 443
windows.msn.com on TCP port 443
assets.msn.com on TCP port 443
kv601.prod.do.dsp.mp.microsoft.com on TCP port 443
cp601.prod.do.dsp.mp.microsoft.com on TCP port 443
geover.prod.do.dsp.mp.microsoft.com on TCP port 443
dl.delivery.mp.microsoft.com on TCP port 80
fs.microsoft.com on TCP port 443

Windows 10 IoT Enterprise LTSC 2021
- Build: 19044.1288
- Edition: Windows 10 IoT Enterprise LTSC
- Arch: x64
- ISO:
en-us_windows_10_iot_enterprise_ltsc_2021_x64_dvd_257ad90f.iso - Hashes: here
- Network connections: 20
click here for the list of network connections
www.msftconnecttest.com on TCP port 80
slscr.update.microsoft.com on TCP port 443
v10.events.data.microsoft.com on TCP port 443
ctldl.windowsupdate.com on TCP port 80
msedge.api.cdp.microsoft.com on TCP port 443
login.live.com on TCP port 443
ocsp.digicert.com on TCP port 80
msedge.b.tlu.dl.delivery.mp.microsoft.com on TCP port 80
fe2cr.update.microsoft.com on TCP port 443
fs.microsoft.com on TCP port 443
settings-win.data.microsoft.com on TCP port 443
go.microsoft.com on TCP port 443
v20.events.data.microsoft.com on TCP port 443
clientconfig.passport.net on TCP port 443
client.wns.windows.com on TCP port 443
download.windowsupdate.com on TCP port 80
cxcs.microsoft.net on TCP port 443
www.bing.com on TCP port 443
config.edge.skype.com on TCP port 443
go.microsoft.com on TCP port 80
Windows 8.1
Windows 8.1 is a release of the Windows NT operating system developed by Microsoft. It was released to manufacturing on August 27, 2013, and broadly released for retail sale on October 17, 2013, about a year after the retail release of its predecessor, and succeeded by Windows 10 on July 29, 2015.

Windows 8.1 Pro
- Build: 9600.17415
- Edition: Windows 8.1 Pro
- Arch: x64
- ISO:
Win8.1_EnglishInternational_x64.iso - Hashes: here
- Network connections: 26
click here for the list of network connections
www.msftncsi.com on TCP port 80
time.windows.com on UDP port 123
login.live.com on TCP port 80
go.microsoft.com on TCP port 80
clientconfig.passport.net on TCP port 443
cacerts.digicert.com on TCP port 80
ctldl.windowsupdate.com on TCP port 80
login.live.com on TCP port 443
ocsp.digicert.com on TCP port 80
sls.update.microsoft.com on TCP port 443
crl3.digicert.com on TCP port 80
crl4.digicert.com on TCP port 80
logincdn.msauth.net on TCP port 443
fe2.update.microsoft.com on TCP port 443
lgincdnvzeuno.azureedge.net on TCP port 443
download.windowsupdate.com on TCP port 80
sqm.telemetry.microsoft.com on TCP port 443
activation-v2.sls.microsoft.com on TCP port 443
watson.telemetry.microsoft.com on TCP port 443
cdf-anon.xboxlive.com on TCP port 80
finance.services.appex.bing.com on TCP port 80
en-gb.appex-rf.msn.com on TCP port 80
update.microsoft.com on TCP port 443
weather.microsoft.com on TCP port 80
www.windowssearch.com on TCP port 443
inference.location.live.net on TCP port 443
Windows 8
Windows 8 is a major release of the Windows NT operating system developed by Microsoft. It was released to manufacturing on August 1, 2012, made available for download via MSDN and TechNet on August 15, 2012, and generally released for retail on October 26, 2012.

Windows 8 Pro
- Build: 9200.16384
- Edition: Windows 8 Pro
- Arch: x64
- ISO:
en_windows_8_x64_dvd_915440.iso - Hashes: here
- Network connections: 14
click here for the list of network connections
www.msftncsi.com on TCP port 80
activation.sls.microsoft.com on TCP port 443
validation.sls.microsoft.com on TCP port 443
go.microsoft.com on TCP port 80
login.live.com on TCP port 443
ds.download.windowsupdate.com on TCP port 80
ssw.live.com on TCP port 80
en-us.appex-rf.msn.com on TCP port 80
www.bing.com on TCP port 80
fe2.update.microsoft.com on TCP port 443
update.microsoft.com on TCP port 443
watson.telemetry.microsoft.com on TCP port 443
sqm.telemetry.microsoft.com on TCP port 443
go.microsoft.com on TCP port 443
Windows 7
Windows 7 is a major release of the Windows NT operating system developed by Microsoft. It was released to manufacturing on July 22, 2009, and became generally available on October 22, 2009. It is the successor to Windows Vista, released nearly three years earlier. It was succeeded by Windows 8 in October 2012.

Windows 7 Professional
- Build: 7601.17514
- Edition: Windows 7 Pro SP1
- Arch: x64
- ISO:
en_windows_7_professional_with_sp1_x64_dvd_u_676939.iso - Hashes: here
- Network connections: 1
click here for the list of network connections
www.msftncsi.com on TCP port 80

Windows 7 Embedded POSReady
- Build: 7601.17514
- Edition: Windows 7 Embedded POSReady
- Arch: x64
- ISO:
en_windows_embedded_posready_7_eval_x64_dvd_698169.iso - Hashes: here
- Network connections: 4
click here for the list of network connections
www.msftncsi.com on TCP port 80
download.windowsupdate.com on TCP port 80
www.update.microsoft.com on TCP port 443
watson.microsoft.com on TCP port 80
Windows Server 2025
Windows Server 2025 is the fourteenth and current major version of the Windows NT operating system produced by Microsoft to be released under the Windows Server brand name. It was released on November 1, 2024.

- Build: 26100.1742
- Edition: Windows Server 2025 Standard (Desktop Experience)
- Arch: x64
- ISO:
en-us_windows_server_2025_x64_dvd_b7ec10f3.iso - Hashes: here
- Network connections: 26
click here for the list of network connections
www.msftconnecttest.com on TCP port 80
time.windows.com on UDP port 123
login.live.com on TCP port 443
slscr.update.microsoft.com on TCP port 443
ctldl.windowsupdate.com on TCP port 80
v10.events.data.microsoft.com on TCP port 443
ocsp.digicert.com on TCP port 80
crl3.digicert.com on TCP port 80
fe2cr.update.microsoft.com on TCP port 443
v20.events.data.microsoft.com on TCP port 443
settings-win.data.microsoft.com on TCP port 443
fd.api.iris.microsoft.com on TCP port 443
download.windowsupdate.com on TCP port 80
fe3cr.delivery.mp.microsoft.com on TCP port 443
go.microsoft.com on TCP port 443
tsfe.trafficshaping.dsp.mp.microsoft.com on TCP port 443
geo.prod.do.dsp.mp.microsoft.com on TCP port 443
kv801.prod.do.dsp.mp.microsoft.com on TCP port 443
cp801.prod.do.dsp.mp.microsoft.com on TCP port 443
2.au.download.windowsupdate.com on TCP port 80
9.au.download.windowsupdate.com on TCP port 80
3.au.download.windowsupdate.com on TCP port 80
geover.prod.do.dsp.mp.microsoft.com on TCP port 443
dl.delivery.mp.microsoft.com on TCP port 80
client.wns.windows.com on TCP port 443
www.bing.com on TCP port 443
Windows Server 2019
Windows Server 2019 is the twelfth major version of the Windows NT operating system produced by Microsoft to be released under the Windows Server brand name. It is the second version of the server operating system based on the Windows 10 platform, after Windows Server 2016. It was announced on March 20, 2018 for the first Windows Insider preview release, and was released internationally on October 2, 2018, the same release date of Windows 10 version 1809. It was succeeded by Windows Server 2022 on August 18, 2021.

- Build: 17763.3650
- Edition: Windows Server 2019 Standard (Desktop Experience)
- Arch: x64
- ISO:
en-us_windows_server_2019_x64_dvd_f9475476.iso - Hashes: here
- Network connections: 32
click here for the list of network connections
www.msftconnecttest.com on TCP port 80
time.windows.com on UDP port 123
sls.update.microsoft.com on TCP port 443
settings-win.data.microsoft.com on TCP port 443
ctldl.windowsupdate.com on TCP port 80
login.live.com on TCP port 443
wdcp.microsoft.com on TCP port 443
ocsp.digicert.com on TCP port 80
wdcpalt.microsoft.com on TCP port 443
crl3.digicert.com on TCP port 80
v10.events.data.microsoft.com on TCP port 443
fe2.update.microsoft.com on TCP port 443
go.microsoft.com on TCP port 443
clientconfig.passport.net on TCP port 443
www.microsoft.com on TCP port 80
checkappexec.microsoft.com on TCP port 443
oneocsp.microsoft.com on TCP port 80
v20.events.data.microsoft.com on TCP port 443
licensing.mp.microsoft.com on TCP port 443
apprep.smartscreen.microsoft.com on TCP port 443
download.windowsupdate.com on TCP port 80
update.microsoft.com on TCP port 443
www.bing.com on TCP port 443
fe3.delivery.mp.microsoft.com on TCP port 443
geo-prod.do.dsp.mp.microsoft.com on TCP port 443
au.download.windowsupdate.com on TCP port 80
kv801.prod.do.dsp.mp.microsoft.com on TCP port 443
cp801.prod.do.dsp.mp.microsoft.com on TCP port 443
go.microsoft.com on TCP port 80
geover.prod.do.dsp.mp.microsoft.com on TCP port 443
dl.delivery.mp.microsoft.com on TCP port 80
tlu.dl.delivery.mp.microsoft.com on TCP port 80
Windows Server 2012 R2
WWindows Server 2012 R2, codenamed “Windows Server Blue”, is the tenth major version of the Windows NT operating system produced by Microsoft to be released under the Windows Server brand name. It was unveiled on June 3, 2013, at TechEd North America, and released on October 18 of the same year. It is the successor to Windows Server 2012, and is based on the Windows 8.1 codebase.

- Build: 9600.17415
- Edition: Windows Server 2012 R2 Standard (Server with a GUI)
- Arch: x64
- ISO:
en_windows_server_2012_r2_vl_with_update_x64_dvd_6052766.iso - Hashes: here
- Network connections: 2
click here for the list of network connections
www.msftncsi.com on TCP port 80
time.windows.com on UDP port 123
Windows Server 2008 R2
Windows Server 2008 R2, codenamed “Windows Server 7”, is the eighth major version of the Windows NT operating system produced by Microsoft to be released under the Windows Server brand name. It was released to manufacturing on July 22, 2009, and became generally available on October 22, 2009, the same respective release dates of Windows 7.

- Build: 7601.17514
- Edition: Windows Server 2008 R2 Standard SP1
- Arch: x64
- ISO:
en_windows_server_2008_r2_with_sp1_vl_build_x64_dvd_617403.iso - Hashes: here
- Network connections: 1
click here for the list of network connections
www.msftncsi.com on TCP port 80
Legend
If you’re wondering what some of those domains/hostnames are assigned to, here is a “small” legend:
config.edge.skype.com- Microsoft Skypectldl.windowsupdate.com- Windows Updatewww.msftconnecttest.com- Network Connectivity test(NCSI)www.msftncsi.com- Network Connectivity test (NCSI)settings-win.data.microsoft.com- Used for Windows apps to dynamically update their configurationmsedge.api.cdp.microsoft.com- Microsoft Edgemsedge.f.tlu.dl.delivery.mp.microsoft.com- Microsoft Storefs.microsoft.com- Used to download fonts on demandcacerts.digicert.com- CRL and OCSP checks to the issuing certificate authoritieslogin.live.com- Microsoft Accountnav.smartscreen.microsoft.com- Windows Defender Smartscreensmartscreen-prod.microsoft.com- Windows Defenderslscr.update.microsoft.com- Windows Update, Microsoft Update, and the online services of Microsoft Storeocsp.digicert.com- CRL and OCSP checks to the issuing certificate authoritiescrl3.digicert.com- CRL and OCSP checks to the issuing certificate authoritiescrl4.digicert.com- CRL and OCSP checks to the issuing certificate authoritiesfe2cr.update.microsoft.com- Windows Update, Microsoft Update, and the online services of Microsoft Storegeo.prod.do.dsp.mp.microsoft.com- Windows Updatego.microsoft.com- Windows Defenderstatics.teams.cdn.office.net- Microsoft Teamsdownload.windowsupdate.com- Windows Updatekv501.prod.do.dsp.mp.microsoft.com- Windows Updatefe3cr.delivery.mp.microsoft.com- Microsoft Storecp501.prod.do.dsp.mp.microsoft.com- Windows Updatego.microsoft.com- Windows Defendergeover.prod.do.dsp.mp.microsoft.com- Windows Updatelicensing.mp.microsoft.com- Used for online activation and some app licensingclient.wns.windows.com- Used for the Windows Push Notification Services (WNS)dmd.metaservices.microsoft.com- Used to retrieve device metadataconfig.teams.microsoft.com- Microsoft Teamsteams.events.data.microsoft.com- Microsoft Teamsstatics.teams.cdn.live.net- Microsoft Teamsedge-conumer-static.azureedge.net- Microsoft Edgedl.delivery.mp.microsoft.com- Microsoft Storemsedge.b.tlu.dl.delivery.mp.microsoft.com- Microsoft Storeedge.microsoft.com- Microsoft Edgeaccount.live.com- Microsoft Live accountacctcdn.msauth.net- Microsoft Live accountbrowser.events.data.microsoft.com- Telemetrylogin.live.com- Microsoft Accountlogincdn.msftauth.net- Microsoft OneDrivev10.events.data.microsoft.com- Diagnostic Datainference.location.live.net- Used for location datav20.events.data.microsoft.com- Telemetrywww.bing.com- Cortana, apps, and Live Tilesonedscolprduks05.uksouth.cloudapp.azure.com- Azurer.bing.com- Cortana, apps, and Live Tilesth.bing.com- Cortana, apps, and Live Tilesteams.live.com- Microsoft Teamsassets.msn.com- Windows Spotlightedgeassetservice.azureedge.netarc.msn.com- Windows Spotlightg.live.com- Microsoft OneDriveofficeclient.microsoft.com- Microsoft Officeoneclient.sfx.ms- Used by OneDrive for Business to download and verify app updatesmaps.windows.com- Maps applicationwatson.events.data.microsoft.com- Diagnostic Dataself.events.data.microsoft.com- Microsoft Officegraph.microsoft.com- Telemetryris.api.iris.microsoft.com- Used to retrieve Windows Spotlight metadatafp.msedge.net- Microsoft OfficeHubwindows.msn.com- Windows Spotlightnav-edge.smartscreen.microsoft.com- Microsoft Edge
Conclusions? None whatsoever, it is what it is.