Ivan,

 

I always just do it as a single command line via the ConfigMgr 2012
Application model. A simple batch script will handle sequencing the wusa.exe
commands, and then finally the Internet Explorer installer, together. Don't
overcomplicate it. :)

 

Cheers,

Trevor Sullivan
Microsoft PowerShell MVP 

 

From: [email protected] [mailto:[email protected]]
On Behalf Of Lindenfeld, Ivan
Sent: Tuesday, May 20, 2014 2:37 PM
To: [email protected]
Subject: [mssms] Internet Explorer 11: is it really such a PITA?

 

I need to deploy IE11 in a mode where it doesn't go to the internet during
installation.

 

Based on my work so far, IE11 needs multiple hotfixes prior to deployment
(or you're gonna have a bad time).

 

As I dug deep into this, all but 3 are either in Software Update or are .cab
files that can be imported with SCUP.

 

Those 3 are:.MSU.  No SCUP.  Traditional package.

 

As I see it here are my options:

 

1.       Package the updates that are not able to be deployed in SU as
traditional hotfixes;then separately deploy the hotfixes I can deploy with
SU; then deploy IE11

2.       Package all of the updates as traditional packages (or a package
script or task sequence) and deploy them; then deploy IE11

3.       Other?

 

Am I missing something?  This seems math hard.

 

Thank you.

 

Ivan Lindenfeld

Manager, Enterprise Deployment/SCCM

Fidelity National Financial | Jacksonville, Florida

 

  _____  

NOTICE: The information contained in this message is proprietary and/or
confidential and may be privileged. If you are not the intended recipient of
this communication, you are hereby notified to: (i) delete the message and
all copies; (ii) do not disclose, distribute or use the message in any
manner; and (iii) notify the sender immediately. 

 



Reply via email to