[1703, cu] 1703 Updates

[gshaw]

Windows 10 as a quick summarisation is going down the sh*tter in terms of corporate and education use. Every major release introduces more fluffy cr*p that no-one really wants and makes unnecessary changes like pushing more things from control panel into the new interactive settings app which is awful.

Windows server 2016 isn't much better either, the extra cpu overhead that it uses in comparison to 2012 r2 is a piss take and the Remote Desktop / Remote App solution while a lot easier to setup and manage is unstable as hell in comparison too.

 

As Michael said, never upgrade! It's asking for a world of hurt. I am re-imaging fully every other year however redoing my base image every major release and using it for rebuilds where needed.

 

And don't get me started about Office 2016 and it's cr*p patching hierarchy... Why MS can't just release CU patches for office or the apps is beyond me, instead a new office build has a ton of patches to install...

What's up with your RDS 2016 farm? Ours has been stable so far but be interested if there's anything to watch out for.

 

Patching Office really irritates me, for Windows I can shrink right down to a base WIM and a couple of Cumulative Updates, fairly nice to deploy.

 

Office then comes along with 100+ updates on top of Office 2013 SP1 and even 2016 has about 30-50 and takes way too long in comparison. Agree patching for Office should follow the Windows model.

 

Win10 1607 seems the most stable of the bunch so will skip 1703 and wait for the Fall Creators Update which has the long awaited OneDrive Files on Demand feature we've craved for so long.

[Tefters]

What's up with your RDS 2016 farm? Ours has been stable so far but be interested if there's anything to watch out for.

 

Patching Office really irritates me, for Windows I can shrink right down to a base WIM and a couple of Cumulative Updates, fairly nice to deploy.

 

Office then comes along with 100+ updates on top of Office 2013 SP1 and even 2016 has about 30-50 and takes way too long in comparison. Agree patching for Office should follow the Windows model.

 

Win10 1607 seems the most stable of the bunch so will skip 1703 and wait for the Fall Creators Update which has the long awaited OneDrive Files on Demand feature we've craved for so long.

I find that CPU utilization from users can spiral out of control when using IE, constantly seeing 20/30% usage on some IE instances.

 

Another one is that the RDCB everyone once in a while (6 to 8 weeks) will throw a hissy fit and not allow connections through and a simple reboot just resolves it?!?! Nothing in the logs or event viewer whatsoever.

 

The session hosts love to crash explorer a lot and I end up having to have the users save all the work as the apps are still open and then have them either log off via ctrl + Alt + Insert which is alien to them or I just log off the session from the RDWEB console. I've seen explorer crash on logon too which is even funnier. Easily resolved just a pain.

Also had session hosts just hang completely, cant log on to them (black screen) via RDP or console however still ping and end up having to hard reboot them.

 

I end up rebuilding my session hosts every 4 months now just for a fresh start, thankfully I have image and task sequences setup in SCCM so rebuilding is as quick and simple as a normal PC however just another Microsoft PITFA to deal with...

Also look back at the drive redirection issue and how long it took them to sort that mess out!

[gshaw]

Luckily we don't use Drive Redirection, deliberately turned off so files don't leave the network (or we is now bad stuff doesn't come in from home machines)

 

Will have to keep an eye on the CPU, not had the login or RDWeb issues yet so fingers crossed it stays that way!

[Sheridan]

Our base image is 1607 build 1198, or the 1703 more recently. Neither will download updates from WSUS on our Server 2012, the usual 0% downloading at the client and missing/failed updates showing in WSUS.

 

At this point I think reimaging every year is more realistic than fixing the updates, I haven't got the time to waste on fixing the ever growing list of bugs on this crappy OS.

[Sheridan]

And my 1703 personal PC just gets the error 0x8024401c every time I try to check for updates - not even using WSUS!

[v01d]

And my 1703 personal PC just gets the error 0x8024401c every time I try to check for updates - not even using WSUS!

 

This is how I picture you when reading your nightmare dealings with Win 10 and the prospect of more nightmares to come with every new build

 

http://2.bp.blogspot.com/-1cOmrnB2bDo/UF9P0q1yZvI/AAAAAAAADIw/4jwAmABdj6g/s320/Vince-McMahon-distraught.gif

 

Having to finally delve into Win 10 deployment myself. Fingers crossed I don't end up the same!

[speckytecky]

That's odd. When I had 1605 on a number of clients I was getting that exact same error. Doing an in- place upgrade to 1703 so far the updates are rolling out fine. I'd also found that with 1605 Central Sophos wasn't automatically starting; even when logged on as an Admin. I needed to tell the system to trust the publisher - each time on a fresh logon. With 1703 that's not happened.

 

And my 1703 personal PC just gets the error 0x8024401c every time I try to check for updates - not even using WSUS!

[Sheridan]

Maybe I should just wait for Windows 11!

[LemonEntry]

I understand I'm necro'ing a post, but is there a resolution to this issue? So far I have one instance of this error, but my entire fleet is 1703 Edu. I was planning on holding off until the Summer to reimage the lot... I don't fancy doing it during term time.