Can not import OOB patch into WSUS; "Trusted Sites" grayed out
55 views
Skip to first unread message
Michael Leone
Jan 20, 2022, 10:20:02 AM1/20/22
to ntsysadmin, patchma...@googlegroups.com
I run a WSUS server on Win 2016. I am trying to import the new OOB
patches. However, when I click "Import Updates", which opens IE. But
it says I need to enable Active X and active scripting, and to import
the updates sites as "Trusted Sites". Yet, when I click on the Sites
button in "Trusted Sites", it is grayed out, and I can't click on
anything. And therefore I can't import anything.
I realize that's probably due to our IE settings pushed by GPO, but do
I really need to use IE, and not something modern to do the import?? I
have the files downloaded, can't I import them that way? It's a real
pain, to have to reconfigure my GPOs to allow just this one computer
access to the trusted sites ....
patches. However, when I click "Import Updates", which opens IE. But
it says I need to enable Active X and active scripting, and to import
the updates sites as "Trusted Sites". Yet, when I click on the Sites
button in "Trusted Sites", it is grayed out, and I can't click on
anything. And therefore I can't import anything.
I realize that's probably due to our IE settings pushed by GPO, but do
I really need to use IE, and not something modern to do the import?? I
have the files downloaded, can't I import them that way? It's a real
pain, to have to reconfigure my GPOs to allow just this one computer
access to the trusted sites ....
Mike Leone
Jan 20, 2022, 10:49:11 AM1/20/22
to ntsys...@googlegroups.com, patchma...@googlegroups.com
AH HA! Powershell to the rescue ...
A bit aggravating, but not too bad ...
$wsus.ImportUpdateFromCatalogSite('cc80b5f2-fdae-4643-b546-c6d0b172c0a7', 'E:\Temp\windows10.0-kb5010791-x64_466ad2172d2cc77b2125420c26b7f9ac00e197f4.msu')
--
You received this message because you are subscribed to the Google Groups "ntsysadmin" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ntsysadmin+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ntsysadmin/CA%2BZrOWxJWf52%3D5hA%2B4OfKpZBgeL3Uie%3DcQs3Gtv-RPH99%2Bu7gg%40mail.gmail.com.
Mike. Leone, <mailto:tur...@mike-leone.com>
PGP Fingerprint: 0AA8 DC47 CB63 AE3F C739 6BF9 9AB4 1EF6 5AA5 BCDF
Photo Gallery: <http://www.flickr.com/photos/mikeleonephotos>
This space reserved for future witticisms ...
Markus Klocker
Jan 21, 2022, 4:22:23 AM1/21/22
to ntsys...@googlegroups.com
recently had the problem myself:
using strong crypto and you should be able to do the import through
catalog again:
https://docs.microsoft.com/en-us/mem/configmgr/core/plan-design/security/enable-tls-1-2-server#configure-for-strong-cryptography
Additionaly I think you have to change the protocol version on the
catalog site when opened from 1.20 to 1.80
hth
Markus
using strong crypto and you should be able to do the import through
catalog again:
https://docs.microsoft.com/en-us/mem/configmgr/core/plan-design/security/enable-tls-1-2-server#configure-for-strong-cryptography
Additionaly I think you have to change the protocol version on the
catalog site when opened from 1.20 to 1.80
hth
Markus
Reply all
Reply to author
Forward
0 new messages