[1809, ou] Windows 10 v1809 released

[free780]

I'm slowly readying 1809 due to the longer support life. If I can automate the image creation it doesn't matter when I release it.

[AJWhite1970]

Did the first 100 pc’s from 1709 to 1809 last night, all appears to have gone ok. Will run them for the last week of term and if they hold up I’ll do the rest of the site over Christmas

[AJWhite1970]

Have now finished upgrading the entire site to 1809 (and most of the servers to 2019...)

Monday will either be the quietest day in Helpdesk history while being carried shoulder high round the sports hall in assembly or carnage, but hey, can’t be worse than the nightmare we had running 1709 for three months....

[free780]

That's weird 1709 has been rock solid where as 1803 seems to have all sorts of issues.

[Jaan]

Have now finished upgrading the entire site to 1809 (and most of the servers to 2019...)

Monday will either be the quietest day in Helpdesk history while being carried shoulder high round the sports hall in assembly or carnage, but hey, can’t be worse than the nightmare we had running 1709 for three months....

 

We're finalising the clients, still the servers to do to 2019. (Have one 2019 for ADBA)

 

Will prob just do the DCs and Hyper-V hosts to be fair.

 

Touch wood and Good luck!

[mavhc]

How are you updating the servers to 2019, in place upgrade? scripted automatic install? manual recreation?

[Jaan]

How are you updating the servers to 2019, in place upgrade? scripted automatic install? manual recreation?

 

back up and inplace upgrade for us.

[Arthur]

New ADMX templates released for 1809...

 

www.microsoft.com/en-us/download/details.aspx?id=57576

[Jaan]

Any ideas how we can find out whats been added or removed with the new GPOs?

 

Thanks

[keyboards]

Upgraded most from 1803 to 1809 here, 98% went fine, one capitulated after update and two machines won't update, on the whole not too bad.

[ass17]

Upgraded most from 1803 to 1809 here, 98% went fine, one capitulated after update and two machines won't update, on the whole not too bad.

 

Bloody hell, we’re still on 1709, can’t get 1803/1809 to work as we have issues with Chrome not working now and again, must be a profile issue but can’t find issue

[mavhc]

Bloody hell, we’re still on 1709, can’t get 1803/1809 to work as we have issues with Chrome not working now and again, must be a profile issue but can’t find issue

 

Define "not working", and how are your profiles set up?

[ass17]

Define "not working", and how are your profiles set up?

 

New fresh profile as per official instructions. When we launch Chrome it fails with page cannot load, I suspect it’s to do with cryptography/windows certs. Sometimes it works when logged in, the another time logged in it stops working, IE/Edge/Chrome.

[Lee_West]

New fresh profile as per official instructions. When we launch Chrome it fails with page cannot load, I suspect it’s to do with cryptography/windows certs. Sometimes it works when logged in, the another time logged in it stops working, IE/Edge/Chrome.

 

Hi all,

 

That was exactly the issue we had. No amount of profiles changes would solve it, so we abandoned a network one and just use the default one on the PC. We've not had any reports of errors so far.

 

Just for the record, our image has been a series of upgrades. We went from fully patched Win 7 to 1709, then to 1803. Just starting with 1809 today. Looking at deploying it via WSUS if I can, especially now I've figured out how to remove the Windows.old folder remotely. Seemed to have a massive junction point in application data, so it ran over 260chrs, so takeown kept crashing out. Right pain.

 

Stumbled across this while looking for a way to remove Mixed Reality Portal. Thanks for the heads up

[Chuckster]

Hi all,

 

That was exactly the issue we had. No amount of profiles changes would solve it, so we abandoned a network one and just use the default one on the PC. We've not had any reports of errors so far.

 

Just for the record, our image has been a series of upgrades. We went from fully patched Win 7 to 1709, then to 1803. Just starting with 1809 today. Looking at deploying it via WSUS if I can, especially now I've figured out how to remove the Windows.old folder remotely. Seemed to have a massive junction point in application data, so it ran over 260chrs, so takeown kept crashing out. Right pain.

 

Stumbled across this while looking for a way to remove Mixed Reality Portal. Thanks for the heads up

@Lee_West, how do you remove the Windows.old folder?

[mavhc]

Hi all,

 

That was exactly the issue we had. No amount of profiles changes would solve it, so we abandoned a network one and just use the default one on the PC. We've not had any reports of errors so far.

 

Just for the record, our image has been a series of upgrades. We went from fully patched Win 7 to 1709, then to 1803. Just starting with 1809 today. Looking at deploying it via WSUS if I can, especially now I've figured out how to remove the Windows.old folder remotely. Seemed to have a massive junction point in application data, so it ran over 260chrs, so takeown kept crashing out. Right pain.

 

Stumbled across this while looking for a way to remove Mixed Reality Portal. Thanks for the heads up

 

Ah, roaming profiles? Yeah, they seem a bit dead/untested, stop using them if you can.

 

Yikes, my image is almost just the wim extracted from the esd off the iso. Use DISM++ to remove/alter a few things, then as it deploys a few scripts to fix a bit more, then all software installed via msi/scripts

[Lee_West]

@Chuckster

 

I use PDQ to deploy it, but it uses a a sysinternals tool called Junction to scan windows.old for junction points then outputs them to a text file. I then found a Powershell script that looks at that text file and deletes the junction. That bypasses the 260chr error. I then use takeown, Icacls and RD to delete it.

 
#Run in CMD
c:\tools\junction64.exe -accepteula -s -q C:\windows.old > %temp%\junc.txt -force

#Save below as a PS Script

foreach ($line in [system.IO.File]::ReadLines("$env:temp\junc.txt")) {     if ($line -match "^\\")     {         $file = $line -replace "(: JUNCTION)|(: SYMBOLIC LINK)",""         & c:\tools\junction64.exe -d "$file"     } }

#Run the next three parts in CMD

takeown /F C:\windows.old /R /D Y
echo y| cacls C:\windows.old /T /Grant Everyone:F
rd /s /q C:\windows.old

What had happened was a junction had been created in Application Data that made about 40 levels of the same folders underneath, so steps 3-5 on their own would fail every time.

Edited January 17, 2019 by Lee_West

[Lee_West]

Ah, roaming profiles? Yeah, they seem a bit dead/untested, stop using them if you can.

 

Yikes, my image is almost just the wim extracted from the esd off the iso. Use DISM++ to remove/alter a few things, then as it deploys a few scripts to fix a bit more, then all software installed via msi/scripts

This was a mandatory profile on the network. Roamers didn;t have the issue, but we're swapping them to using UE-V at the moment, as we use Deep Freeze, so everything gets lost at reboot.

 

Problem is we have tonnes of software to reinstall, a chunk of which works, but the installers might not as it's old Win98 stuff.

[ass17]

@Lee_West, how do you remove the Windows.old folder?

 

Obviously the manual way is with disk cleanup but would be interested if it’s a different way too

[Lee_West]

@ass17

 

Two posts up . You can't use disk cleanup remotely, as you need to click 'Yes' when removing old Windows installations. I've not been able to find a way to do that with out actually being either at or TS'd to the PC

[mavhc]

This was a mandatory profile on the network. Roamers didn;t have the issue, but we're swapping them to using UE-V at the moment, as we use Deep Freeze, so everything gets lost at reboot.

 

Problem is we have tonnes of software to reinstall, a chunk of which works, but the installers might not as it's old Win98 stuff.

 

Well, if people actually still use it, when I monitored what was actually used and scrapped anything that was annoying to install

[Lee_West]

That'll be the next thing. If we hit any major issues or if we want to scale the image down. Pushing nearly 60gb at the moment.

[JATSO]

@ass17

 

Two posts up . You can't use disk cleanup remotely, as you need to click 'Yes' when removing old Windows installations. I've not been able to find a way to do that with out actually being either at or TS'd to the PC

 

Just read your post is this any good, not tested.

 

https://qtechbabble.wordpress.com/2016/11/16/use-a-batch-script-to-remotely-delete-windows-old-folder/

[Lee_West]

Just read your post is this any good, not tested.

 

https://qtechbabble.wordpress.com/2016/11/16/use-a-batch-script-to-remotely-delete-windows-old-folder/

 

That's parts 3-5 of what I use, so yes in theory, it should do.

 

The problem I had was the 40 folder deep nesting of Application Data. The structure ended up being something like C:\Windows.old\username\AppData\Local\Applicat... Data\Application Data\Application Data\Application Data\ for about 40 levels. It maxed out the 260chr limit, even with NTFS long names enabled in GPO.

[Jaan]

Anybody seen a new excel sheet that shows the changes from the older 1809 gpos templates to the new current ones please?