So I'm a linux user; I was always curious if I could get W10 to run on KVM (linux native virtualization); i downloaded an ISO from MS and installed with no issues, indicating "activate later"
Did some web searching and MS had an article on how to activate using the command line with some keys documented right on the site. Did that, and it shows as activated. It indicated "volume licensing" keys which I have no idea what that is.
I'm not interested in using windows, this was an exercise and I also wanted to see the ProtonVPN client for windows (pretty slick); I occasionally use ProtonVPN for linux on the command line.
To see how many connections were being made in a native windows install, I opened a cmd and did a netstat -an; seems like a lot of 443 connections to various IPs.
I notice some connections going to an NN.x.x.x address when NN is a company I used to work for. The company owns a class A address allocated to them; I was like WT.....
Did a search and found that the company, in fact, had sold off parts or all of the address space or returned it to the allocating agency; did a whois on the address and it appears MS now controls it.
Makes sense.
End of story, no.....
Relayed this to one of my coworkers who used to work for the company also. He indicated he knew the company sold it off, because some people he worked with were busy re-iping their infrastructure because the company sold it off while lines of service in the company WERE STILL USING THE ADDRESS SPACE.
I don't work for them anymore; with blunders like that maybe I'm somewhat glad.....
-T
Did some web searching and MS had an article on how to activate using the command line with some keys documented right on the site. Did that, and it shows as activated. It indicated "volume licensing" keys which I have no idea what that is.
I'm not interested in using windows, this was an exercise and I also wanted to see the ProtonVPN client for windows (pretty slick); I occasionally use ProtonVPN for linux on the command line.
To see how many connections were being made in a native windows install, I opened a cmd and did a netstat -an; seems like a lot of 443 connections to various IPs.
I notice some connections going to an NN.x.x.x address when NN is a company I used to work for. The company owns a class A address allocated to them; I was like WT.....
Did a search and found that the company, in fact, had sold off parts or all of the address space or returned it to the allocating agency; did a whois on the address and it appears MS now controls it.
Makes sense.
End of story, no.....
Relayed this to one of my coworkers who used to work for the company also. He indicated he knew the company sold it off, because some people he worked with were busy re-iping their infrastructure because the company sold it off while lines of service in the company WERE STILL USING THE ADDRESS SPACE.
I don't work for them anymore; with blunders like that maybe I'm somewhat glad.....
-T