3s-gtech Posted October 25, 2017 Posted October 25, 2017 That's understandable - we had some Asus T100s that had the same issue (annoying as the CPU supported 32 bit instructions). They never made it into the production environment and were quickly binned here.
gshaw Posted October 25, 2017 Posted October 25, 2017 If given the choice, for either LTSB or Edu, would you deploy x86 or x64? We're currently undecided as all of our software is compatible with both (bar Paint.net!) and none of our devices have any more than 8gb RAM. Previously we've only pushed out x86 Win 7 for the small image size. x64 every time, all of ours have been for some time now
kennysarmy Posted October 25, 2017 Posted October 25, 2017 I originally tested LTSB - then talked myself in to trying the EDU version, but seriously all the crap that you have to remove, that may come back, a perception that logon times were much better under LTSB means I'm going to build up an image for further user testing based on that. As an aside was also using classic shell/start menu but have ditched that due to a few test users experiencing lockups! 1
Katy Posted October 25, 2017 Posted October 25, 2017 We had a split of x86 and x64 win7 (two schools merged, one was x86 the other x64). We rebuilt everything with the "new school image" as x64. Now we're on Win 10 Enterprise x64, the only 32bit stuff we have left is the digital signage PCs - they will run the 64bit OS but the graphics driver will only do 1920x1080 resolution if it's running on a 32bit system (and it doesn't work on anything newer than Win 7). They're ancient and only have 2GB RAM so no big deal having a separate win7x86 image for them. We used to be on the LTSB Win 10 branch but the crap with the start menu pushed me onto the enterprise 1609 build (where it was slightly less broke), and then moved onto 1703 (where it's a little bit better again). I've never looked at the Education version though. We remove all the crap with a powershell script near the end of the MDT task sequence, although doing so breaks calculator (we have installed "Old Calculator" and just pointed the shortcuts at that instead). 1
gshaw Posted October 25, 2017 Posted October 25, 2017 We had a split of x86 and x64 win7 (two schools merged, one was x86 the other x64). We rebuilt everything with the "new school image" as x64. Now we're on Win 10 Enterprise x64, the only 32bit stuff we have left is the digital signage PCs - they will run the 64bit OS but the graphics driver will only do 1920x1080 resolution if it's running on a 32bit system (and it doesn't work on anything newer than Win 7). They're ancient and only have 2GB RAM so no big deal having a separate win7x86 image for them. We used to be on the LTSB Win 10 branch but the crap with the start menu pushed me onto the enterprise 1609 build (where it was slightly less broke), and then moved onto 1703 (where it's a little bit better again). I've never looked at the Education version though. We remove all the crap with a powershell script near the end of the MDT task sequence, although doing so breaks calculator (we have installed "Old Calculator" and just pointed the shortcuts at that instead). Education and Enterprise are pretty identical, indeed when you import the WIM it used to identify as Enterpise
kennysarmy Posted October 25, 2017 Posted October 25, 2017 We had a split of x86 and x64 win7 (two schools merged, one was x86 the other x64). We rebuilt everything with the "new school image" as x64. Now we're on Win 10 Enterprise x64, the only 32bit stuff we have left is the digital signage PCs - they will run the 64bit OS but the graphics driver will only do 1920x1080 resolution if it's running on a 32bit system (and it doesn't work on anything newer than Win 7). They're ancient and only have 2GB RAM so no big deal having a separate win7x86 image for them. We used to be on the LTSB Win 10 branch but the crap with the start menu pushed me onto the enterprise 1609 build (where it was slightly less broke), and then moved onto 1703 (where it's a little bit better again). I've never looked at the Education version though. We remove all the crap with a powershell script near the end of the MDT task sequence, although doing so breaks calculator (we have installed "Old Calculator" and just pointed the shortcuts at that instead). Crap with the Start Menu on LTSB being? It just does n't work?
mavhc Posted October 25, 2017 Posted October 25, 2017 Pro. 64 bit. Installing 1709 today. I use dism to remove some apps from the image, own own applications are all done via gpo.
Katy Posted October 25, 2017 Posted October 25, 2017 Crap with the Start Menu on LTSB being? It just does n't work? Yeah, at least on the 1511 LTSB people were randomly just getting a plain black area instead of the actual start layout, fix being to delete their profile. 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now