Project ''Install Windows 10''

[RJohnson91]

Hi all,

 

We are embarking on our journey to install Windows 10 around the school both physically and virtually.

 

I am currently in the stage of finding guineapigs before I push it out fully.

 

 

So I call all techies that have completed this project already, what problems did you face?

 

 

What software compatibility caused you a headache?

 

 

Did you find running a mixed environment of Windows 7 and Windows 10 screwed GPOs...

 

 

I'm trying to do as much research as possible before taking the leap :nerd:

[FN-GM]

So I call all techies that have completed this project already, what problems did you face?

 

Sorting the start menu tiles was fiddly, but got it sorted in the end.

Also turn off the automatic driver installs from Windows Update. That used to kick in during SCCM OSD and make it fail. I turned it off on the image before I captured it.

 

What software compatibility caused you a headache?

 

Everything worked in all our schools (to my surprise!)

 

Did you find running a mixed environment of Windows 7 and Windows 10 screwed GPOs...

 

Nope, we had completely separate group policies one for Windows 7 and One for Windows 10. We then used WMI filters so the machines knew what policy to apply.

Edited April 27, 2017 by FN-GM

[GuyJD]

I don't think I've had major update to Windows 10 that hasn't broken something so my advice would be to thoroughly test updates well in advance of allowing the rest of the school to get them.

 

First update killed the drivers on all my DVD drives,

second update made the computers crash when the visualiser was used,

Not found what's broken in the latest update hence it's still only installed on my PC

[RJohnson91]

Sorting the start menu tiles was fiddly, but got it sorted in the end.

Also turn off the automatic driver installs from Windows Update. That used to kick in during SCCM OSD and make it fail. I turned it off on the image before I captured it.

 

 

 

Everything worked in all our schools (to my surprise!)

 

 

 

Nope, we had completely separate group policies one for Windows 7 and One for Windows 10. We then used WMI filters so the machines knew what policy to apply.

 

I don't think I've had major update to Windows 10 that hasn't broken something so my advice would be to thoroughly test updates well in advance of allowing the rest of the school to get them.

 

First update killed the drivers on all my DVD drives,

second update made the computers crash when the visualiser was used,

Not found what's broken in the latest update hence it's still only installed on my PC

 

 

Cheers guys,

 

I sense a trend that Automatic updates should be turned off at all costs

 

Separating group policies I think is the only way to go.

 

I'm shocked that all your software worked off the bat, our curriculum software is virtualized so no worries there, I'm more worried about Solus updates and Call Parent applications ...

 

Ryan

[GuyJD]

I'm more worried about Solus updates and Call Parent applications ...

 

Ryan

Solus works fine here

[FN-GM]

First update killed the drivers on all my DVD drives,

second update made the computers crash when the visualiser was used,

Not found what's broken in the latest update hence it's still only installed on my PC

 

This is why we use LTSB. Made things much more stable.

[Passat1983ICTech]

hi there we are doing lot testing her software is a pain with some software is a big pain to install

other thing is to look out for is windows 10 running 100% on the disk ssd don't do this normal hdd have work rounds just a lot of googling when you have time at work AV software ware i would recommend is get some as defender dose not pick up on malware i have just found out don't not witch bois you are pc make sure they are up to date as well

 

witch windows 10 are you going with make it all the same

[GuyJD]

This is why we use LTSB. Made things much more stable.

lol this is LTSB

[synaesthesia]

Be sure all your machines are new enough to run it. We forgot how many older AMD X2's and Pentium Dual Core's we had around the place which won't run 64bit Win10

[NB9457]

We have issues with black screens and not being able to click the start menu, still trying to get this sorted here

[mdrabble]

Using Enterprise LTSB 2016 - didn't want to uninstall the "extra" features that come with the EDU edition.

 

I have pulled a machine of each make/model in for testing - happy to say no issues at the moment.

 

Having issues with pinning items to the start menu - so but this on a back burner while I look at software deployments.

 

Using SCCM to deploy things and for some reason the software is being fussy about the deployment order!

 

Tested deployments with individuals apps and they deploy fine - soon as I build the TS to deploy other apps, some refuse to deploy!

[unixman_again]

We've had a lot of problems with old peripherals, which used to work just under W7 but refuse to work under W10. Included are Vidifox i3130 visualisers, Fujitsu ScanSnap s500, some Smartboards (can't remember models) and the Fluke PAT tester. It looks as though it's going to be an expensive summer if they want to replace all of these devices, with new versions which can be made to work. Some will have to be replaced.

 

We started off with Education, but we've moved to LTSB.

[kennysarmy]

We've had a lot of problems with old peripherals, which used to work just under W7 but refuse to work under W10. Included are Vidifox i3130 visualisers, Fujitsu ScanSnap s500, some Smartboards (can't remember models) and the Fluke PAT tester. It looks as though it's going to be an expensive summer if they want to replace all of these devices, with new versions which can be made to work. Some will have to be replaced.

 

We started off with Education, but we've moved to LTSB.

 

Ha - I started off with LTSB then moved to Education on my test rig !!

[mavhc]

Minecraft didn't work on old hardware with new java. Put old java on network, wrote a bat file, didn't bother installing java on the computers.

 

We don't have much hardware so not a problem.

 

I converted my installs to be all MSI based ages ago, so I just put the new WIM on the WDS server and test it out every 8 months, no need to recreate an image each time.

[disk]

We have issues with black screens and not being able to click the start menu, still trying to get this sorted here

 

How did you make your Windows 10 image? What are you using to deploy the image? What make/models are you using? Is it happening on many models or just specific ones?

[NB9457]

How did you make your Windows 10 image? What are you using to deploy the image? What make/models are you using? Is it happening on many models or just specific ones?

It's happening on a mix of machines apparenlty on 2015 and 2016 LTSB, not had a real chance to delve into it though, first thing to check is Impero and make sure that isn't causing issues.

[Simcfc73]

We are on 2016 LTSB but tempted to go back to Edu as the creator edition seems to have fixed loads of stuff for me and Edge is nice and stable for me now (IE was doing my head in on 1607 for some reason)

 

We do use classic shell though.

[ITGURU]

We've had a lot of problems with old peripherals, which used to work just under W7 but refuse to work under W10. Included are Vidifox i3130 visualisers, Fujitsu ScanSnap s500, some Smartboards (can't remember models) and the Fluke PAT tester. It looks as though it's going to be an expensive summer if they want to replace all of these devices, with new versions which can be made to work. Some will have to be replaced.

 

We started off with Education, but we've moved to LTSB.

 

Depending on your smartboard models, there is a newer driver on the smart website that we had to download to get them interacting with windows 10