Win7PRO to Win10PRO Upgrade
-
@iroal said:
I'm in the same situation, 17 Dell Desktops with W7
I upgraded one machine using Windows Update, no error in all the process, looking the license appear as correctly activated.
Now I'm going to create a image to clone the computers, using this tutorial you can activate W10 licence before install it
Interesting. If this works, this will be the first way to use cloning/imaging that appears (without reading the EULA) to be legal to deploy images without using VL media.
I'm wondering, does running gatherosstate.exe do the process that actually registers your machine with MS? Or is that not handled until the associated GenuineTicket.xml file is run under the Windows 10 install?
I have to assume the latter, otherwise why bother doing the latter?
I would be interested to know - if after doing this and verifying that it's activated, if you wipe the machine again, and install Win10 from scratch again, will it auto activate without the need to save this file?
-
@ryanblahnik said:
The 7 years old point is accurate for sure and worthwhile in more ways than one, but a little disingenuous in another respect too while 7's still being updated.
Windows 7 still is supported with patches, it is not getting updated. Not the same thing. Only necessary fixes are still applied. The code base continuous to age in general.
-
@scottalanmiller said:
@ryanblahnik said:
The 7 years old point is accurate for sure and worthwhile in more ways than one, but a little disingenuous in another respect too while 7's still being updated.
Windows 7 still is supported with patches, it is not getting updated. Not the same thing. Only necessary fixes are still applied. The code base continuous to age in general.
it's in extended support now, so sure, but for the first 5 years it was "" more than just updates/patches.
-
@ryanblahnik said:
The standard best practices sysadmin approach just has these couple inconsistencies to me in this case. I know there are a ton of limits to my knowledge that would probably explain some of this.
I don't see any inconsistencies. Staying updated is important and a best practice but nothing in a panacea.
-
@Dashrender said:
@scottalanmiller said:
@ryanblahnik said:
The 7 years old point is accurate for sure and worthwhile in more ways than one, but a little disingenuous in another respect too while 7's still being updated.
Windows 7 still is supported with patches, it is not getting updated. Not the same thing. Only necessary fixes are still applied. The code base continuous to age in general.
it's in extended support now, so sure, but for the first 5 years it was "" more than just updates/patches.
Not in a general sense. What important updates to security structure, functionality, refactoring, kernel performance, etc. were added?
-
@scottalanmiller said:
@Dashrender said:
@scottalanmiller said:
@ryanblahnik said:
The 7 years old point is accurate for sure and worthwhile in more ways than one, but a little disingenuous in another respect too while 7's still being updated.
Windows 7 still is supported with patches, it is not getting updated. Not the same thing. Only necessary fixes are still applied. The code base continuous to age in general.
it's in extended support now, so sure, but for the first 5 years it was "" more than just updates/patches.
Not in a general sense. What important updates to security structure, functionality, refactoring, kernel performance, etc. were added?
I'm pretty sure there were some changes/updates with SP1, but beyond that, not sure any did really happen... but that is why I said "" to mean that MS claims they can/do release these types of updates, but often doesn't and leaves them for the new versions.
-
@Dashrender These are more good points. I'll continue to play devil's advocate a little here but I know splitting from best practices on this wouldn't be a sustainable thing either.
A lot of people are barely coming to accept that regular updates are best for them, and would rather continue to work around the annoying notifications because the risk of something changing in a bad way seems higher than the chance of anything improving + considering unknown security-type stuff. When something like last summer's iOS update opens the possibility they can end up with a fairly disabled phone until another fix comes out, it's hard to say they're not justified.
I did the upgrade on an older laptop out of curiosity, and after moving files off didn't ask the upgrade to try to keep any data or any other programs along. The Windows store is where I saw most of my issues. Out of curiosity I think at some point I'll give it another fresh shot from scratch.
Whether most people would have any interest in putting that much time into it or giving it those chances is irrelevant though, because it's our job to handle all that and present them with usable systems.
I really don't mean to take this down a paranoid/security/move to a cave track and you make good points there too. Before I continue more months of studying I always feel like I'm mostly talking out of my ass about security anyway, or at least missing complexities. So I'll try not to hit too much more on this part here.
They are admitting/telling some things, but some updates are more opaque too.
The Samsung example is obscene for sure. If our focus is on trusting and staying patched, the baseline for that stuff can continue to shift even a lot further. Bigger companies have more to lose and that's a fair point too, and they also have a lot of people dependent on their products who might not like the idea of some of this stuff but only have inconvenient alternatives.
-
@scottalanmiller said:
I don't see any inconsistencies. Staying updated is important and a best practice but nothing in a panacea.
I'd describe the first one as, they're hounding people, talking about improvements. Follow the process they offer you, and end up running into these issues.
Now even throw that out, because it's our job to keep learning and find independently of MS that we can use a workaround that's more of a hassle than we were promised. But how do you like this so far? If you consider if it weren't MS who you've been working with for decades, would you see it any differently? (Also curious for reference, did a fresh reinstall after your upgrade resolve the issues you've been having?)
The second one follows, and is there a strong base here to have faith in what we're being offered?
I'm thinking of the other thread discussing people following vendor advice. Here, we can't even really "trust, but verify".
If there aren't a lot of good alternatives to trusting, that still doesn't seem to make trusting so black and white.
-
I hear ya on updates can sometimes break things situation, so we have to ask ourselves. Do we want to leave ourselves vulnerable to hackers and just skip the updates? It's a double edged sword.
Speaking of what we're told are in the updates, the masses don't care. I suppose we as IT personal do/should, but then again who has time to? In the SMB I don't have the resources that large companies do to test everything before rolling it out (patch wise). I'd definitely spend a significant amount of additional time testing patches then I do fixing a problem when a patch breaks something. I weigh the likeliness of a problem with a patch versus my users becoming infected by a virus and find it's much more likely they will be infected, so I want to patch security holes ASAP.
I also agree that people don't want to be bothered with update notices all the time. My boss was recently lamenting to me about how she just updated last week, when in fact it was approx 4 weeks ago, during the last patch Tuesday event. Windows 8 (or was it 8.1?) for non corporate users just installs the updates and if you don't reboot on your own in three days, reboots for you. I really like this method for those users.
You mentioned your store experience - what was the issue. And - I don't use the store, at least not with any regularity yet. They don't have x86 x64 apps yet, and I'm not an APP buyer anyway.. so...
-
@Dashrender said:
You mentioned your store experience - what was the issue.
I've got to run for now but can hit on this quick.
Fox Sports has an app that works well on Android for streaming. They offer it on Windows too, through a browser on 7. I was trying to run it to a TV with HDMI, but after logging in, it worked until the point where you start the stream, and then sat there indefinitely. Tried in 3 different browsers ranging from add-ons to completely stock. So I broke out the old computer, and in 10 you can't do it through a browser and need to install an app.
That 10 minutes was pretty goofy. One or two big half-screen dialog boxes with no text and an OK button, just from opening and starting to navigate.
I'm trying to think exactly what the weirdest part was regarding. After I made it to the app page, it had a couple preinstall checkboxes, maybe they were for automatic updates, or location services. And I remember if I picked one option, the page would just refuse to load, and show me an empty apparent error. After trying the other option, it loaded normally now that it had forced me to that opposite option.
Then there was one more similar round of that, where the option I chose just loaded to a blank page, until trying the option I didn't want let it start to work like it was supposed to. I couldn't have made it up. It would have been a stretch for the normal range of Android glitches and seemed senseless on a desktop.
A lot of this is just the app developers, and when I opened the app it failed at the same point it had on Windows 7. But the store was weird before I made it that far too.
-
In 10 you can't do it through a browser? Why not? If you installed Chrome or FF on Windows 10, it wouldn't run? WTF? Are you saying the website knew it was Windows 10 and refused to run outside of their what appears to be a crappy app?
You should be able to solve that by changing the browser string in Chrome or FF (though if the site is doing IP stack scanning to check Windows version, you'll need an IP stack proxy program (that I only just learned about last week - thanks Steve Gibson) that will obfuscate your IP stack.
-
@Dashrender said:
In 10 you can't do it through a browser? Why not? If you installed Chrome or FF on Windows 10, it wouldn't run? WTF? Are you saying the website knew it was Windows 10 and refused to run outside of their what appears to be a crappy app?
You should be able to solve that by changing the browser string in Chrome or FF (though if the site is doing IP stack scanning to check Windows version, you'll need an IP stack proxy program (that I only just learned about last week - thanks Steve Gibson) that will obfuscate your IP stack.
Because he only tried Edge obviously. Edge has no plugin infrastructure yet. This is a huge failing on MS' part.
-
@Dashrender said:
@iroal said:
I'm in the same situation, 17 Dell Desktops with W7
I upgraded one machine using Windows Update, no error in all the process, looking the license appear as correctly activated.
Now I'm going to create a image to clone the computers, using this tutorial you can activate W10 licence before install it
Interesting. If this works, this will be the first way to use cloning/imaging that appears (without reading the EULA) to be legal to deploy images without using VL media.
I'm wondering, does running gatherosstate.exe do the process that actually registers your machine with MS? Or is that not handled until the associated GenuineTicket.xml file is run under the Windows 10 install?
I have to assume the latter, otherwise why bother doing the latter?
I would be interested to know - if after doing this and verifying that it's activated, if you wipe the machine again, and install Win10 from scratch again, will it auto activate without the need to save this file?
I will be testing this out. And regarding your last question, yes. Because a clean install of Windows 10 does not have this file.
https://i.imgur.com/NfMtcST.jpg -
@JaredBusch said:
@Dashrender said:
@iroal said:
I'm in the same situation, 17 Dell Desktops with W7
I upgraded one machine using Windows Update, no error in all the process, looking the license appear as correctly activated.
Now I'm going to create a image to clone the computers, using this tutorial you can activate W10 licence before install it
Interesting. If this works, this will be the first way to use cloning/imaging that appears (without reading the EULA) to be legal to deploy images without using VL media.
I'm wondering, does running gatherosstate.exe do the process that actually registers your machine with MS? Or is that not handled until the associated GenuineTicket.xml file is run under the Windows 10 install?
I have to assume the latter, otherwise why bother doing the latter?
I would be interested to know - if after doing this and verifying that it's activated, if you wipe the machine again, and install Win10 from scratch again, will it auto activate without the need to save this file?
I will be testing this out. And regarding your last question, yes. Because a clean install of Windows 10 does not have this file.
https://i.imgur.com/NfMtcST.jpgLOL of course a clean install doesn't have that file.
I'm just trying to work out the process and timing when MS puts information about your hardware on their servers to authenticate you?
It would be awesome if it happened when gatherosstate.exe runs. If that was the long and the short of it, and we didn't need that XML file, life would be awesome, we run that, it registers the Windows 7/8/8.1 machine with MS and bam Bob's your uncle. Now you upgrade to Windows 10 whenever you want, be that today, or 2 years from now.
-
@Dashrender said:
@JaredBusch said:
@Dashrender said:
@iroal said:
I'm in the same situation, 17 Dell Desktops with W7
I upgraded one machine using Windows Update, no error in all the process, looking the license appear as correctly activated.
Now I'm going to create a image to clone the computers, using this tutorial you can activate W10 licence before install it
Interesting. If this works, this will be the first way to use cloning/imaging that appears (without reading the EULA) to be legal to deploy images without using VL media.
I'm wondering, does running gatherosstate.exe do the process that actually registers your machine with MS? Or is that not handled until the associated GenuineTicket.xml file is run under the Windows 10 install?
I have to assume the latter, otherwise why bother doing the latter?
I would be interested to know - if after doing this and verifying that it's activated, if you wipe the machine again, and install Win10 from scratch again, will it auto activate without the need to save this file?
I will be testing this out. And regarding your last question, yes. Because a clean install of Windows 10 does not have this file.
https://i.imgur.com/NfMtcST.jpgLOL of course a clean install doesn't have that file.
I'm just trying to work out the process and timing when MS puts information about your hardware on their servers to authenticate you?
It would be awesome if it happened when gatherosstate.exe runs. If that was the long and the short of it, and we didn't need that XML file, life would be awesome, we run that, it registers the Windows 7/8/8.1 machine with MS and bam Bob's your uncle. Now you upgrade to Windows 10 whenever you want, be that today, or 2 years from now.
It cannot activate then.
The system is in the wrong state. It would make a system hash against your current OS not Windows 10.
-
@JaredBusch said:
@Dashrender said:
@JaredBusch said:
@Dashrender said:
@iroal said:
I'm in the same situation, 17 Dell Desktops with W7
I upgraded one machine using Windows Update, no error in all the process, looking the license appear as correctly activated.
Now I'm going to create a image to clone the computers, using this tutorial you can activate W10 licence before install it
Interesting. If this works, this will be the first way to use cloning/imaging that appears (without reading the EULA) to be legal to deploy images without using VL media.
I'm wondering, does running gatherosstate.exe do the process that actually registers your machine with MS? Or is that not handled until the associated GenuineTicket.xml file is run under the Windows 10 install?
I have to assume the latter, otherwise why bother doing the latter?
I would be interested to know - if after doing this and verifying that it's activated, if you wipe the machine again, and install Win10 from scratch again, will it auto activate without the need to save this file?
I will be testing this out. And regarding your last question, yes. Because a clean install of Windows 10 does not have this file.
https://i.imgur.com/NfMtcST.jpgLOL of course a clean install doesn't have that file.
I'm just trying to work out the process and timing when MS puts information about your hardware on their servers to authenticate you?
It would be awesome if it happened when gatherosstate.exe runs. If that was the long and the short of it, and we didn't need that XML file, life would be awesome, we run that, it registers the Windows 7/8/8.1 machine with MS and bam Bob's your uncle. Now you upgrade to Windows 10 whenever you want, be that today, or 2 years from now.
It cannot activate then.
The system is in the wrong state. It would make a system hash against your current OS not Windows 10.
eh? I suppose if it needs to include something specific from Win10 in the hash, OK fine, but that seems completely unnecessary. The hash only needs to be tied to the hardware. Are you telling the the hardware hashes would be different under Win10 vs anything else?
-
and now I have another question - can the same XML file be used to authorize more than one machine? or is the old Install key used?
I would guess that the old key could be used, but OEM machine were all installed using the same key until the OEMs started putting the install key into the BIOS. There are (or were) millions of machines with Windows 7 installed that came with a generic OEM install key.
-
@Dashrender said:
In 10 you can't do it through a browser? Why not? If you installed Chrome or FF on Windows 10, it wouldn't run? WTF? Are you saying the website knew it was Windows 10 and refused to run outside of their what appears to be a crappy app?
You should be able to solve that by changing the browser string in Chrome or FF (though if the site is doing IP stack scanning to check Windows version, you'll need an IP stack proxy program (that I only just learned about last week - thanks Steve Gibson) that will obfuscate your IP stack.
Yes, the page ends up on a message forcing you to the app.
Interesting idea for a workaround.
@JaredBusch said:
Because he only tried Edge obviously. Edge has no plugin infrastructure yet. This is a huge failing on MS' part.
IE and Edge. I'll leave the tone alone.
-
before working around it, I'd try Chrome or FF.
-
@scottalanmiller, curious if 10 has been more solid for you lately? It seems like within the last few weeks had been seeing reports of multiple restarts daily.
