Jump to content

20H2 is out

caffrey

By caffrey
in Windows 10

 Share

Recommended Posts

supportman

supportman

Posted
Posted (edited)

Seems to work well for me, love the new explorer icons on the start menu.

 

One thing I noticed is I cant press the delete key on the keyboard on desktop items. Anyone else having the same issue? Right clicking and delete works.

 

One other thing, it was incredibly quick to apply the update, not sure if its just small or Microsoft have a new install method but it was great!

Edited by supportman
  • 2 weeks later...
thatley

thatley

Posted
Posted
Rolled out 20H2 fresh from WDS at a school last week (65 machines) and all working well. Only issue I had was the new embedded MS Edge Chromium adds Online Office Apps shortcuts to the start menu when you run it, which is typical MS and annoying. Created a GPO to delete those shortcuts for each user, so they never see them. Apart from that, all good!
supportman

supportman

Posted
Posted
Seems to work well for me, love the new explorer icons on the start menu.

 

One thing I noticed is I cant press the delete key on the keyboard on desktop items. Anyone else having the same issue? Right clicking and delete works.

 

One other thing, it was incredibly quick to apply the update, not sure if its just small or Microsoft have a new install method but it was great!

 

Cumulative update seems to have fixed delete key on desktop.

 

Great release!

  • 4 weeks later...
kennysarmy

kennysarmy

Posted
Posted

We've not even got all our site on 1903 Education yet :( many PC's still on 1607 LTSB - but we're getting there.

 

What's the easiest way to get from 1903 Edu to 20H2? Run the Windows 10 Update Assistant during school downtime?

caffrey

caffrey

Posted
  • Author
Posted
I'm not sure I'm doing it the right way, but from 1809 - 1909 I created an update task sequence with a modified WIM. I then have a special account that runs a batch file that runs that task sequence, so I just go round or remote in and log on and wait for a while (takes upto 2 hours...) and they magically update
  • Thanks 1
kennysarmy

kennysarmy

Posted
Posted
I'm not sure I'm doing it the right way, but from 1809 - 1909 I created an update task sequence with a modified WIM. I then have a special account that runs a batch file that runs that task sequence, so I just go round or remote in and log on and wait for a while (takes upto 2 hours...) and they magically update

 

Might look in to that, but why is that preferable to just running the Update Assistant?

 

I'm guessing because you don't have to go to the latest version?

caffrey

caffrey

Posted
  • Author
Posted

It's just the way I do it, not sure if it's the right way or the best way but it works for me :) I'm sure there are better ways. It's just a thin image just with appx packages removed

 

For some reason I like to stay a year behind, there's no real benefit in my eyes to the end user what version they are on - we just have to do it now.

 

Logon script is just

 

\\yourmdtserver\MDT$\Scripts\litetouch.vbs /skiptasksequence:yes /tasksequenceid:yourtasksequenceID /UserID:**** /UserPassword:****

 

Only annoying thing is a UAC prompt

  • Thanks 1
kennysarmy

kennysarmy

Posted
Posted

My upgrade task sequence was not happy :(

 

ut-fail.JPG

 

Logged on to PC as domain admin, mapped a drive to the deployment share and ran the litetouch.vbs - choose the upgrade task sequence, seemed to be successful but then PC rolls back and gives above error :(

kennysarmy

kennysarmy

Posted
Posted
I don't run it as domain admin, just as a user who has access to the MDT$ share - I don't mount any drives at all

 

It should be that easy right ;)

 

To rule things out I've taken the test PC off the domain, logged in locally and am trying again.

 

ut.JPG

 

It's currently doing the upgrade...

caffrey

caffrey

Posted
  • Author
Posted
Takes forever, to the point where I'm thinking it would be quicker to just not bother with upgrade sequences. It saves on the re installing of all those random bits of software though...
kennysarmy

kennysarmy

Posted
Posted
It should be that easy right ;)

 

To rule things out I've taken the test PC off the domain, logged in locally and am trying again.

 

[ATTACH=CONFIG]60082[/ATTACH]

 

It's currently doing the upgrade...

 

That worked.

 

I suspect the policy that caused the issue yesterday was one from our PowerMan settings which shutsdown PC's if no one is logged on for 10 minutes, I think once the script has done it's bit and the PC sits updating with no one logged on the policy kicked in and shutdown the PC :(

 

Bit more testing to do.

  • Thanks 1
kennysarmy

kennysarmy

Posted
Posted
That worked.

 

I suspect the policy that caused the issue yesterday was one from our PowerMan settings which shutsdown PC's if no one is logged on for 10 minutes, I think once the script has done it's bit and the PC sits updating with no one logged on the policy kicked in and shutdown the PC :(

 

Bit more testing to do.

 

Failed!

 

Was not to do with it shutting down - just removed the policy that does that and attempted to upgrade a PC on the domain.

 

I suspect now it might be to do with our local administrator name being changed by group policy, have renamed the local account back to "Administrator" and I'm trying again !!

gmonks

gmonks

Posted
Posted
Failed!

 

Was not to do with it shutting down - just removed the policy that does that and attempted to upgrade a PC on the domain.

 

I suspect now it might be to do with our local administrator name being changed by group policy, have renamed the local account back to "Administrator" and I'm trying again !!

 

I've had to take the device off the domain before and then login locally and retry...this has then worked.

  • Thanks 1
_techie_

_techie_

Posted
Posted

I'm having issues deploying 2004 out from WDS 2012 R2 - giving me an issue about joining the domain. 1909 works fine however. This is on old kit (9 years old).

 

Any ideas? Haven't really had time to look at it yet but 1909 works fine, joins the domain and does its job.

 

Not really fussed to be honest, as we have a working and stable Enterprise LTSC 2019 rollout.

Norphy

Norphy

Posted
Posted
With some of our PCs, there was something in a user’s profile that was preventing the upgrade from completing. In the end, I changed the task sequence to log the computer off and delete all cached profiles. That seemed to do the trick.
  • 4 weeks later...
2097

2097

Posted
Posted

I have been deploying via the ESD file and a batch , Took a while ( i think the esd was corrupt) but i got it working ok ( despite it taking a very long time to install ).

 

start /w WindowsUpdateBox /Update /PreDownload /quiet /noreboot

start /w WindowsUpdateBox /Update /Install /quiet /noreboot

start /w WindowsUpdateBox /Update /Finalize /quiet /noreboot

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing


×
×
  • Create New...