Replies

guys, anyone having issues installing KB5023765 on Server 2012 r2?

what I see is some of the vms take a really long time to apply this update. often takes a few attempts. not all of them.

DirectAccess is fixed. I am patching abt 10-20 test users with the issue and is resolved.

some of them downgraded from ENT to PRO… I am guessing because they cannot or could not talk to the KMS server

KB5019959 broke DA.
Can someone verify if direct Access is fixed by the latest updates?

One of my test users got  this message: do you trust this printer?

He was able to print to the printserver yesterday w/o issues > after the patch he got this… Anyone else?

I am unable to replicate the issue in my test machines

Great tool!
now I can have a nice visual stats for my co-workers (users) when they say is the computer and it turns out is their local ISP having issues.

https://twitter.com/msft365status?lang=en

We’re not observing an increase in successful connections after rolling back a recent change

hopefully is resolved by the AM

1 user thanked author for this post.

woody

i installed kb4530684 on my test domain PCs and the network drive mappings are working (vbs script and AD mapping)

he states: ” Co-management is a destination, and you can get started today by connecting ConfigMgr”

SCCM is not dead, not every site has the $$$ to afford the cloud services, other places refuse to put their stuff on the cloud due to privacy issues… we all know big brother is always watching (IMO)

[EP]

EP wrote:

check this out woody:

NEW out-of-band updates on MS Update Catalog:
https://www.catalog.update.microsoft.com/Search.aspx?q=2019-10

KB4524135 IE update for IE9/IE10/IE11
KB4524147 CU for 1903 (build 18362.388)
KB4524148 CU for 1809 (build 17763.775)
KB4524149 CU for 1803 (build 17134.1040)
KB4524150 CU for 1709
KB4524151 CU for 1703
KB4524152 CU for 1607

edit: these updates will also be available thru WU and WSUS

ooooh information overload 4 me on these new updates 🙁

• This reply was modified 5 years, 7 months ago by EP.
• This reply was modified 5 years, 7 months ago by EP.

They just  came down via WSUS…

I am a bit torn abt this… to deploy or not deploy to my org (prior testing of course)?

Also in the notes: “mitigation and corrects a recent printing issue some users have experienced.

Note This update does not replace the upcoming October 2019 monthly update, which is scheduled to release on October 8, 2019.”

 

me neither.

1 user thanked author for this post.

woody

ltorres wrote:

win32kfull.sys that comes with KB4487026 is 10.0.14393.2791 dell optiplex 9020m w/o issues have 10.0.143932665 At this point I had to uninstall the patch as it is for one of my Customer Service agents. I setup another 9020M with the latest patches and runing Prime95… I am not sure if this will trigger a blue screen

I donno if this matters anymore but I did not deploying KB4487026. I deployed March updates and win32kfull.sys changed to 10.0.14393.2848 and my user has yet to blue screen so I am confident I am ok for march updates… I did not end up finding out what caused the bsod

win32kfull.sys that comes with KB4487026 is 10.0.14393.2791

dell optiplex 9020m w/o issues have 10.0.143932665

At this point I had to uninstall the patch as it is for one of my Customer Service agents. I setup another 9020M with the latest patches and runing Prime95… I am not sure if this will trigger a blue screen

I am dealing with BSOD for Dells 9020M (1607 and 1709)

Dumps point to the win32kfull.sys… I have updated BIOS and video drivers so far but still BSOD. next on my list is chipset and sound.

No other Dell chassis is having this issues (we only have dells)

¯\_(ツ)_/¯

 

1 user thanked author for this post.

woody

KB4487026 via sccm timed out (max run time 360 min) granted Dev and Test environments are on slow drives.

I gotta feeling patching night will take a couple more hours for prod

 

What I have done in this occasions is to approve them in batches.

I like to go by year, in that way you can see what you are approving (don’t want to deploy .net 4.7 to web servers if that is not your intention)

Also you can monitor what systems are running low in space in that way you don’t stop exchange from working due to lack of space.

take this time to go as far back as you can to see if patches from 2015 are applicable (u might have 2 systems)

When I do catch-up on clients I do it one batch a week (200 servers and 3000 WKS on average) aprox… that way is easier to troubleshoot if things happen.