Zourous Posted May 23, 2017 Posted May 23, 2017 So new laptops went out to teachers last year just before the last summer with Windows 10 1511 on them. 1511 looks like it is due to expire some time in the next year. We call all the laptops in at the begining of summer for a PAT test and perform any updates we need to do. I won't see these laptops again for any reasonable amount of time in the next yeat I'm assuming I need to at least get them onto 1607? Also what is the easiest way of doing it? Is it by doing an in-place upgrade assuming you don't what to wipe out any data files in the meantime?
DalekSec Posted May 23, 2017 Posted May 23, 2017 In place upgrade will be the place to go, might be worth seeing if you can up them to 1703 instead of 1607, gives you more time before you have to do it again! 1
Zourous Posted May 23, 2017 Author Posted May 23, 2017 Yes, but I'm more of a tried and tested guy rather than the cutting edge, and I just don't trust windows 10 at the moment.
alfatec Posted May 23, 2017 Posted May 23, 2017 Careful doing the in-house upgrade. 1607 will put all the apps back on and 1703 seems to still have quite a few issues. We are still on 1511 but think we will do a slow upgrade with a new image once 1703 is sorted. But by then we will probably be on 1909.
3s-gtech Posted May 23, 2017 Posted May 23, 2017 If you do in place upgrade with your own custom rolled ISO you can remove the apps etc, but this will mean visitng each PC one-by-one. I have my custom ISO for 1703 on a memory stick - this allows me to install a fresh OC or in-place upgrade with worthless apps etc.
Geoff Posted May 23, 2017 Posted May 23, 2017 LTSB might work better for you if you don't have SCCM to control the in place upgrades properly.
garethEds Posted May 23, 2017 Posted May 23, 2017 Careful doing the in-house upgrade. 1607 will put all the apps back on and 1703 seems to still have quite a few issues. We are still on 1511 but think we will do a slow upgrade with a new image once 1703 is sorted. But by then we will probably be on 1909. Being ignorant here - but what are the issues with 1703? Gareth
mullet_man Posted May 23, 2017 Posted May 23, 2017 I've deployed a few 1703 machines and not noticed any issues at all really. The lock screen is still broke but not a major issue and would assume it will get fixed in an update.
FragglePete Posted May 23, 2017 Posted May 23, 2017 The only issue I noticed with 1703 was with the missing text..... but, this had Impero on, and not seen it since we've re-deployed it on the same machines without Impero. We're ditching Impero this year in favor of Senso so don't see it as in issue. I believe Impero may have indentified the issue, but that doesn't help us as I didn't renew the support. So far though, looks ok. Had to re-work the MDT sequence (additional pre-installed apps need to be removed along with some gone) - can't believe I'm planning Summer rebuild already; has come round very quick this year. Pete 1
Michael Posted May 23, 2017 Posted May 23, 2017 I was led to believe each version of Windows 10 would be valid for 5 years in terms of support.
sparkeh Posted May 23, 2017 Posted May 23, 2017 (edited) I was led to believe each version of Windows 10 would be valid for 5 years in terms of support. Don't think so. Here is an explanation: https://blog.juriba.com/windows-10-branching-timeline So, v1511 is expected to fall out of support in Sep 17 for CB and Jan 18 for CBB Edited May 23, 2017 by sparkeh
Michael Posted May 23, 2017 Posted May 23, 2017 So the question is, how are you guys performing upgrades? Last time I tried 1507 > 1511 it took nearly 2 hours for one device! It's actually quicker/cleaner to re-image the device in my experience, unless Microsoft have improved the process?
sparkeh Posted May 23, 2017 Posted May 23, 2017 So the question is, how are you guys performing upgrades? Last time I tried 1507 > 1511 it took nearly 2 hours for one device! It's actually quicker/cleaner to re-image the device in my experience, unless Microsoft have improved the process? My current thinking is to reimage. You're right, it quicker and less painful process. 1511 -> 1607 was a drag too.
mbedford Posted May 23, 2017 Posted May 23, 2017 (edited) My current thinking is to reimage. You're right, it quicker and less painful process. 1511 -> 1607 was a drag too. I second this, re-image. In place upgrade just causes more trouble than its worth. Also have to contend with the Windows.old folder residing on your HDD's until Windows decides it can go. If you have a WDS server in place then this shouldn't be a huge issue. We have 2500+ machines here and my team of 5 of us could do the entire estate in a week to 10 days if we had to rush it. Biggest slow down is the prep on the reference image IMO. I am just finalising our 1607 image to move us away from 1511. I know 1703 but I just find it a little more prudent to sit just behind the bleeding edge rather than on it. Microsoft is not having a good time with updates recently... Patch Tuesday: Security Update for Group Policy Breaks Group Policy | Patch Tuesday content from Windows IT Pro Patch Tuesday Windows security update rendered Outlook unusable for many | PCWorld Granted, the WannaCry attack of last week is more than enough reason to stay on top of security updates. But actual operating system upgrades, I think we can afford to be a little more cautious. Mike Edited May 23, 2017 by mbedford
free780 Posted May 24, 2017 Posted May 24, 2017 Well either you have SCCM and do a in place upgrade out of hours. For laptops you may need to configure them to go straight to Microsoft for updates if you want the control you have to setup a DP/MP in a DMZ to push out upgrades for internet clients. You could just push out 1607 via WSUS but would need a script to get rid of the apps. You can configure Windows Updates to only allow reboots after business hours. Basically unless your setup for zero touch with all software re-imaging is going to be a pain every 6-8 months even if done via SCCM client. Also user data will need to not be on client PC/laptops.
Blue_Cookeh Posted May 24, 2017 Posted May 24, 2017 I opted to just push the 1703 update out via SCCM as a software (feature) upgrade. At the end of the day I'm not going to be going around and reimaging all our machines every time whatever build we're on leaves support, and really it makes my life easier since I can just build a machine and forget about the software side of it for the life of the hardware. I use GPOs and SCCM Compliance settings to pull the machines back into a state we like after the upgrade.
sparkeh Posted May 24, 2017 Posted May 24, 2017 Well either you have SCCM and do a in place upgrade out of hours. For laptops you may need to configure them to go straight to Microsoft for updates if you want the control you have to setup a DP/MP in a DMZ to push out upgrades for internet clients. You could just push out 1607 via WSUS but would need a script to get rid of the apps. You can configure Windows Updates to only allow reboots after business hours. Basically unless your setup for zero touch with all software re-imaging is going to be a pain every 6-8 months even if done via SCCM client. Also user data will need to not be on client PC/laptops. I opted to just push the 1703 update out via SCCM as a software (feature) upgrade. At the end of the day I'm not going to be going around and reimaging all our machines every time whatever build we're on leaves support, and really it makes my life easier since I can just build a machine and forget about the software side of it for the life of the hardware. I use GPOs and SCCM Compliance settings to pull the machines back into a state we like after the upgrade. So if you do an in place upgrade with sccm, do you get all the cruft like start menu apps coming back?
SHimmer45 Posted May 24, 2017 Posted May 24, 2017 so essentially if you havent got SCCM in place its a pita i know 10 have brought improvements but the whole "upgrade" process is broken.
Michael Posted May 24, 2017 Posted May 24, 2017 It's too long winded, and Microsoft's upgrade policy is just too narrow. Unfortunately releasing a whole new OS every time to get a new feature is just poorly thought out. It's just ironic that Windows 7 is still being supported after the first edition of Windows 10... makes absolutely no sense at all!
Arthur Posted May 24, 2017 Posted May 24, 2017 It's just ironic that Windows 7 is still being supported after the first edition of Windows 10... makes absolutely no sense at all! Support for Windows 7 RTM ended on 9 April 2013. Only Windows 7 with SP1 will be supported until 14 January 2020. It makes sense to me.
Michael Posted May 24, 2017 Posted May 24, 2017 I'm afraid it doesn't - Windows 10 (any version) is infinitely better than Windows 7 SP1.
Arthur Posted May 24, 2017 Posted May 24, 2017 Windows 10 (any version) is infinitely better than Windows 7 SP1. I agree, but you have completely missed the point I was trying to make. Windows 10 v1507 and v1511 are like Windows 7 RTM in the sense that they are, or soon will be, no longer supported. Windows 10 v1607 and v1703 are like Windows 7 SP1. i.e. still supported by Microsoft.
Michael Posted May 24, 2017 Posted May 24, 2017 But it's not a good comparative Arthur. That means Windows 7 will be supported for 11 years and Windows 10 only 2/3 years at a time. Microsoft need a bit of a reality check I'm afraid. There's no chance big corporations are going to upgrade every 2/3 years. I know that's what LTSB is for, but realistically this should be the scope for all versions regardless.
Duke5A Posted May 25, 2017 Posted May 25, 2017 But it's not a good comparative Arthur. That means Windows 7 will be supported for 11 years and Windows 10 only 2/3 years at a time. Microsoft need a bit of a reality check I'm afraid. There's no chance big corporations are going to upgrade every 2/3 years. I know that's what LTSB is for, but realistically this should be the scope for all versions regardless. They probably did it this way on purpose. After what MS went through trying to get people to give up older versions of Windows I can see why they're doing this.
Blue_Cookeh Posted May 25, 2017 Posted May 25, 2017 (edited) IMO you guys are looking at it all wrong. IT is moving on and everything is becoming a service, Windows being no exception. If you properly manage your upgrades then you won't be reimaging machines to install new feature upgrades. Windows 10 will be set and forget in that you'll image a machine (using a continuously serviced image, which SCCM does in the background) and then it becomes part of your Windows 10 servicing plans. Yes, SCCM seems to be the only real product out there at the moment than can manage this lifecycle properly, but honestly if you embrace it I believe it'll be a lot less work in the long run for a lot of gain. In a certain part of the NHS we're moving onto Windows 10 CBB full steam ahead and are planning a 3,000 device roll out over the next year. So if you do an in place upgrade with sccm, do you get all the cruft like start menu apps coming back? Yes they do, but I'm using Compliance settings in SCCM to check for the apps, then remediate with another PowerShell script to remove them. Edited May 25, 2017 by Blue_Cookeh 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