New
#131
I doubt you notice the difference. GPEDIT is still there, Remote desktop too. I have a link to the feature list someplace. Will have look for it.
Compare Windows 10 Editions
I doubt you notice the difference. GPEDIT is still there, Remote desktop too. I have a link to the feature list someplace. Will have look for it.
Compare Windows 10 Editions
Hi Alpha,
Its not a question of whose's right or wrong
Its about sharing our knowledge, we each have our own speciality.
Im no IT Pro, learnt over on 7 watching and learning from Noeldp.
Roy
As posted elsewhere, Win 10S and Win 10 Pro licences are interchangeable.
To test this I installed Win 10S and not having a product key, it was naturally not activated.
Proceeded to change the key to Win 10 Pro and the edition changed to that with a digital licence linked to MSA.
Then changed the key again to a generic Win 10S key and after it temporarily lost activation during the edition switch, it then activated as Win 10S.
I had suspected that. I also had done an install without entering a key, mine activated though. That PC already had a DL for Pro. It was assumed it used that to activate. No easy way to prove it, not for me anyway. Not without using a VM or something. All my PC's now have multiple DL's for just about every Edition of W 10. Most from doing test installs like you just did.
Makes one wonder why you would use 10 S, unless forced too? Or really really had a need too. And what's to stop Joe Student upgrading to Pro the first time they get a chance? Block it via GPO I guess?
I've been checking the licensing logs that gets produced with licensingdiag, but there does not seem to be much interesting in the event logs - prolly b'cos I've not had activation issues (I still have to force de-activation on VM's to see if anything juicy pops up - may have to go to the 'dark side' for that... but this is a meatier script we did with the BSOD guys recently.
Just putting it out there in case it comes in handy...
Thanks!
Shows all relevant info, in a nicely formatted text file and I find it very useful. But of course I had to comment out the lines that hides my keys. (great that the script does hide those by default though)
Yup, thanx... was thinking of adding a param to display the key - however this is for diagnostics and we rather not at his stage.
With the upgrade to 17133.1 additional data gets extracted under Clip
Not sure what the purpose is though, I mean last bios key? as if there are others? Odd.Code:+Registry: SYSTEM\CurrentControlSet\Services\ClipSVC\Parameters LastBiosKey: ***** - ***** - ***** - ***** - KD782 ProcessBiosKey: 1
PS: Running the latest script added to the OP will give this info.