Enable nt 4.0 drivers upgrade#
So the machines have to be joined to a domain (requiring a license upgrade worth half the machines buy price), then to use 365 with our own password policy we’d need to deploy ADFS and do SSO with it, etc. It turns out Microsoft accounts and Office 365 are accounts are completely different things – ie the Windows team didn’t bother talking to the cloud services team. So great I thought, we could run them like Chromebooks – provision a bunch of Office 365 accounts and they can just sign in to Windows with them – ie, no infrastructure required in the school. The Windows machines are now coming down to Chromebook pricing (ie the HP Stream 11). Microsoft is also taking a bit of a gamble with the Windows for Bing licenses. Here in Australia, Woolworths has recently made a big deal about dumping Windows for the Chromebook too – so I don’t think it’s reasonable for people to assume that this situation will be confined to EDU. Its a lot of infrastructure, and then you need someone to set it all up and maintain it.
Enable nt 4.0 drivers software#
Windows just isn’t something you can easily deploy in a school you need Active Directory, a way of imaging the machines (these days its SCCM), a way of deploying software and updates to it (again SCCM or WSUS), etc. The reason for it really is price, and ease of deployment. I work in education, and we have a huge deployment of Chromebooks. I can’t imagine using the Windows desktop on a 7″ screen with my finger! Its barely usable on my 11″ tablet.Ĭhromebooks are potentially larger threat. I think the $99 tablets will fail – there is no compelling use case, and you can’t use Windows on a tablet without using the desktop at some point (even if its MS Office). PS C:\WINDOWS\system32> Get-VMProcessor NT40 | fl CompatibilityForOlderOperatingSystemsEnabledĬompatibilityForOlderOperatingSystemsEnabled : True PS C:\WINDOWS\system32> Set-VMProcessor NT40 -CompatibilityForOlderOperatingSystemsEnabled $true PS C:\WINDOWS\system32> Get-VMProcessor NT40 | fl CompatibilityForOlderOperatingSystemsEnabledĬompatibilityForOlderOperatingSystemsEnabled : FalseĪs you can see it’s disabled. Now it’s hidden from the user, so you need to enable this in Power Shell. Restricting the CPU capabilities was the checkbox to enable in the first version of Hyper-V.
![enable nt 4.0 drivers enable nt 4.0 drivers](https://i.ytimg.com/vi/JN3h1eFqayA/mqdefault.jpg)
Make sure the VMs are powered off before trying to do this. It’s weird to me how they are “Operating normally’ since they aren’t running but I guess that’s a feature.
![enable nt 4.0 drivers enable nt 4.0 drivers](https://s3.manualzz.com/store/data/021437389_1-98d7cfcdc79843a165b5b21569aad648.png)
Both of them are ‘off’ since there is no memory assigned, nor is there any uptime. Windows 2000(wks) Off 0 0 00:00:00 Operating normallyĪs you can see here I have two virtual machines. Name State CPUUsage(%) MemoryAssigned(M) Uptime Status Old versions of Windows are not supported, but with a little bit of fun from PowerShell you can get them to work.įirst make sure you run PowerShell as Administrator!
Enable nt 4.0 drivers windows 10#
This holds true for 2008r2, and 2012 along with the Windows 10 preview. In this attempt to get NT 4.0 running on my machine, here is what I did.