Internet Explorer 11 Deployment

In the near future MSFT will begin to deploy IE11 via Windows/Microsoft
update as an important update for Windows 7 SP1 and higher for x64 and
x86 and Windows Server 2008 R2 SP1 and higher for x64.

If you don't wish to receive IE11 a tool kit is avaialble to block it

http://www.microsoft.com/en-us/downl....aspx?id=40722
"The Internet Explorer 11 Blocker Toolkit enables users to disable
automatic delivery of Internet Explorer 11 as an important class update
via Automatic Updates (AU) feature of Windows Update (WU)."

--
...winston
msft mvp consumer apps

"...winston" wrote in message
...
In the near future MSFT will begin to deploy IE11 via Windows/Microsoft
update as an important update for Windows 7 SP1 and higher for x64 and x86
and Windows Server 2008 R2 SP1 and higher for x64.

If you don't wish to receive IE11 a tool kit is avaialble to block it

http://www.microsoft.com/en-us/downl....aspx?id=40722
"The Internet Explorer 11 Blocker Toolkit enables users to disable
automatic delivery of Internet Explorer 11 as an important class update
via Automatic Updates (AU) feature of Windows Update (WU)."


If WAU is set to something other than "automatically receive", can't it just
be refused? There are a number of things I don't need (including Bing
Desktop and updates for programs I've never had installed), so I just
uncheck and hide them.

If IE11 is easily uninstalled, I may give it a try on one of my Win7
machines. My other one is still on IE9 since IE10 gave it fits. Or maybe
I'll try it on that one just to see if there are any improvements.
--
SC Tom

....winston wrote:

In the near future MSFT will begin to deploy IE11 via Windows/Microsoft
update as an important update for Windows 7 SP1 and higher for x64 and
x86 and Windows Server 2008 R2 SP1 and higher for x64.

If you don't wish to receive IE11 a tool kit is avaialble to block it

http://www.microsoft.com/en-us/downl....aspx?id=40722
"The Internet Explorer 11 Blocker Toolkit enables users to disable
automatic delivery of Internet Explorer 11 as an important class update
via Automatic Updates (AU) feature of Windows Update (WU)."

Don't need a toolkit. Just configure AU to *NOT* install updates
automatically. Let it notify only. Then when YOU visit the WU site YOU
will choose whether to install it or not or if YOU want to hide that
update so you're not nuisanced with it later.

VanguardLH wrote:
...winston wrote:

In the near future MSFT will begin to deploy IE11 via Windows/Microsoft
update as an important update for Windows 7 SP1 and higher for x64 and
x86 and Windows Server 2008 R2 SP1 and higher for x64.

If you don't wish to receive IE11 a tool kit is avaialble to block it

http://www.microsoft.com/en-us/downl....aspx?id=40722
"The Internet Explorer 11 Blocker Toolkit enables users to disable
automatic delivery of Internet Explorer 11 as an important class update
via Automatic Updates (AU) feature of Windows Update (WU)."

Don't need a toolkit. Just configure AU to *NOT* install updates
automatically. Let it notify only. Then when YOU visit the WU site YOU
will choose whether to install it or not or if YOU want to hide that
update so you're not nuisanced with it later.


That's a route to take (set AU to notify and hide) though with each
cumulative update it will be re-offered (since the KB# changes) locally
(not a site) in WU and most likely as a pre-checked item ready for
install..thus requiring one to re-hide the item.


--
...winston
msft mvp consumer apps

Bob Henson wrote:
...winston wrote:

In the near future MSFT will begin to deploy IE11 via Windows/Microsoft
update as an important update for Windows 7 SP1 and higher for x64 and
x86 and Windows Server 2008 R2 SP1 and higher for x64.

If you don't wish to receive IE11 a tool kit is avaialble to block it

http://www.microsoft.com/en-us/downl....aspx?id=40722
"The Internet Explorer 11 Blocker Toolkit enables users to disable
automatic delivery of Internet Explorer 11 as an important class update
via Automatic Updates (AU) feature of Windows Update (WU)."

Hmm, I'm not sure whether to use that. The beta version I tried was very
fast, but badly broken, so I'm hoping the release has been fixed. I think
I'll risk it - but thanks for telling us about the Blocker.


For Win7 I'm inclinded to wait a few weeks or more before installing a
new IE release preferring to periodically monitor MSFT's IE forums for
known issues.

For Win8 - IE11 or Sea Monkey have both been problem free for my usage.


--
...winston
msft mvp consumer apps

"...winston" wrote in message
...
VanguardLH wrote:
...winston wrote:

In the near future MSFT will begin to deploy IE11 via Windows/Microsoft
update as an important update for Windows 7 SP1 and higher for x64 and
x86 and Windows Server 2008 R2 SP1 and higher for x64.

If you don't wish to receive IE11 a tool kit is avaialble to block it

http://www.microsoft.com/en-us/downl....aspx?id=40722
"The Internet Explorer 11 Blocker Toolkit enables users to disable
automatic delivery of Internet Explorer 11 as an important class update
via Automatic Updates (AU) feature of Windows Update (WU)."

Don't need a toolkit. Just configure AU to *NOT* install updates
automatically. Let it notify only. Then when YOU visit the WU site YOU
will choose whether to install it or not or if YOU want to hide that
update so you're not nuisanced with it later.


That's a route to take (set AU to notify and hide) though with each
cumulative update it will be re-offered (since the KB# changes) locally
(not a site) in WU and most likely as a pre-checked item ready for
install..thus requiring one to re-hide the item.


Been doing that for years, and it hasn't been a problem for me. Any machine
that has Office 2003 (and possibly newer versions) installed continues to
try to install Outlook updates, even if Outlook was never installed as part
of the suite. Since it's a new definition, the KB# changes each time.

I'm sure there are others, but that one sticks out in my memory :-)
--
SC Tom

SC Tom wrote:


"...winston" wrote in message
...
VanguardLH wrote:
...winston wrote:

In the near future MSFT will begin to deploy IE11 via Windows/Microsoft
update as an important update for Windows 7 SP1 and higher for x64 and
x86 and Windows Server 2008 R2 SP1 and higher for x64.

If you don't wish to receive IE11 a tool kit is avaialble to block it

http://www.microsoft.com/en-us/downl....aspx?id=40722
"The Internet Explorer 11 Blocker Toolkit enables users to disable
automatic delivery of Internet Explorer 11 as an important class update
via Automatic Updates (AU) feature of Windows Update (WU)."

Don't need a toolkit. Just configure AU to *NOT* install updates
automatically. Let it notify only. Then when YOU visit the WU site YOU
will choose whether to install it or not or if YOU want to hide that
update so you're not nuisanced with it later.


That's a route to take (set AU to notify and hide) though with each
cumulative update it will be re-offered (since the KB# changes)
locally (not a site) in WU and most likely as a pre-checked item ready
for install..thus requiring one to re-hide the item.


Been doing that for years, and it hasn't been a problem for me. Any
machine that has Office 2003 (and possibly newer versions) installed
continues to try to install Outlook updates, even if Outlook was never
installed as part of the suite. Since it's a new definition, the KB#
changes each time.

I'm sure there are others, but that one sticks out in my memory :-)

Just because OL isn't installed doesn't mean that files OL uses or
shared across the other suite to ensure integration (e.g. OL uses Word
engine and has for some time)are not being identified during a system WU
deploy.

In the past users (both consumer and business) had a bit more control
over deployment. That MSFT model is changing with Win8/Server 8 though a
fair amount of back-and-forth reasoning is occuring amongst all parties
via the support and private feeback channels.

The majority of users will continue to run AU/WU in auto mode installing
anything that comes down the pipeline....and stuff will continue to show
up with the user asking (why is that being offered g)


Even though I prefer setting AU to notify on both Win7 and Win8 its been
years since anything coming down that pipeline has caused problems or
significant concern.
- Occasionally there a few udpates I take a longer wait/see approach.
e.g. a few updates (USB related KB 2868038 and 2862330) in this last
batch that I held off on installing due to a fair amount of problems
that have surfaced - not installing, interference with 3rd party AV/AM
software due to a possible 2X restart requirement, reoffered after a
logged successful install, etc. resetting audio driver)

--
...winston
msft mvp consumer apps

"...winston" wrote in message
...
SC Tom wrote:


"...winston" wrote in message
...
VanguardLH wrote:
...winston wrote:

In the near future MSFT will begin to deploy IE11 via
Windows/Microsoft
update as an important update for Windows 7 SP1 and higher for x64 and
x86 and Windows Server 2008 R2 SP1 and higher for x64.

If you don't wish to receive IE11 a tool kit is avaialble to block it

http://www.microsoft.com/en-us/downl....aspx?id=40722
"The Internet Explorer 11 Blocker Toolkit enables users to disable
automatic delivery of Internet Explorer 11 as an important class
update
via Automatic Updates (AU) feature of Windows Update (WU)."

Don't need a toolkit. Just configure AU to *NOT* install updates
automatically. Let it notify only. Then when YOU visit the WU site
YOU
will choose whether to install it or not or if YOU want to hide that
update so you're not nuisanced with it later.


That's a route to take (set AU to notify and hide) though with each
cumulative update it will be re-offered (since the KB# changes)
locally (not a site) in WU and most likely as a pre-checked item ready
for install..thus requiring one to re-hide the item.


Been doing that for years, and it hasn't been a problem for me. Any
machine that has Office 2003 (and possibly newer versions) installed
continues to try to install Outlook updates, even if Outlook was never
installed as part of the suite. Since it's a new definition, the KB#
changes each time.

I'm sure there are others, but that one sticks out in my memory :-)

Just because OL isn't installed doesn't mean that files OL uses or shared
across the other suite to ensure integration (e.g. OL uses Word engine and
has for some time)are not being identified during a system WU deploy.

In the past users (both consumer and business) had a bit more control over
deployment. That MSFT model is changing with Win8/Server 8 though a fair
amount of back-and-forth reasoning is occuring amongst all parties via the
support and private feeback channels.

The majority of users will continue to run AU/WU in auto mode installing
anything that comes down the pipeline....and stuff will continue to show
up with the user asking (why is that being offered g)


Even though I prefer setting AU to notify on both Win7 and Win8 its been
years since anything coming down that pipeline has caused problems or
significant concern.
- Occasionally there a few udpates I take a longer wait/see approach.
e.g. a few updates (USB related KB 2868038 and 2862330) in this last batch
that I held off on installing due to a fair amount of problems that have
surfaced - not installing, interference with 3rd party AV/AM software due
to a possible 2X restart requirement, reoffered after a logged successful
install, etc. resetting audio driver)

OL will use the Word engine if it is used as the default email editor. In
our environment (years ago), that had to be disabled- IIRC, it caused
considerable slowness on our NT Server and Exchange 5.0(?) setup when
sending or replying to emails.

And I believe that Word 2003 uses OL as the default for "Send by email", and
if OL isn't installed, the "Send. . ." option is grayed out (or at least it
is on my Win8 machine with Word 2003 installed). On my Win7 machine with OL
installed, the email options are available.

WU offers the "Update for Outlook 2003 Junk E-mail Filter (KBxxxxxxx)" each
month for both machines. I accept it on the one with OL installed, but
refuse it on the other. Word still works the same otherwise, word up! :-)
--
SC Tom

SC Tom wrote:


"...winston" wrote in message
...
SC Tom wrote:


"...winston" wrote in message
...
VanguardLH wrote:
...winston wrote:

In the near future MSFT will begin to deploy IE11 via
Windows/Microsoft
update as an important update for Windows 7 SP1 and higher for x64
and
x86 and Windows Server 2008 R2 SP1 and higher for x64.

If you don't wish to receive IE11 a tool kit is avaialble to block it

http://www.microsoft.com/en-us/downl....aspx?id=40722
"The Internet Explorer 11 Blocker Toolkit enables users to disable
automatic delivery of Internet Explorer 11 as an important class
update
via Automatic Updates (AU) feature of Windows Update (WU)."

Don't need a toolkit. Just configure AU to *NOT* install updates
automatically. Let it notify only. Then when YOU visit the WU
site YOU
will choose whether to install it or not or if YOU want to hide that
update so you're not nuisanced with it later.


That's a route to take (set AU to notify and hide) though with each
cumulative update it will be re-offered (since the KB# changes)
locally (not a site) in WU and most likely as a pre-checked item ready
for install..thus requiring one to re-hide the item.


Been doing that for years, and it hasn't been a problem for me. Any
machine that has Office 2003 (and possibly newer versions) installed
continues to try to install Outlook updates, even if Outlook was never
installed as part of the suite. Since it's a new definition, the KB#
changes each time.

I'm sure there are others, but that one sticks out in my memory :-)

Just because OL isn't installed doesn't mean that files OL uses or
shared across the other suite to ensure integration (e.g. OL uses Word
engine and has for some time)are not being identified during a system
WU deploy.

In the past users (both consumer and business) had a bit more control
over deployment. That MSFT model is changing with Win8/Server 8 though
a fair amount of back-and-forth reasoning is occuring amongst all
parties via the support and private feeback channels.

The majority of users will continue to run AU/WU in auto mode
installing anything that comes down the pipeline....and stuff will
continue to show up with the user asking (why is that being offered g)


Even though I prefer setting AU to notify on both Win7 and Win8 its
been years since anything coming down that pipeline has caused
problems or significant concern.
- Occasionally there a few udpates I take a longer wait/see approach.
e.g. a few updates (USB related KB 2868038 and 2862330) in this last
batch that I held off on installing due to a fair amount of problems
that have surfaced - not installing, interference with 3rd party AV/AM
software due to a possible 2X restart requirement, reoffered after a
logged successful install, etc. resetting audio driver)

OL will use the Word engine if it is used as the default email editor.
In our environment (years ago), that had to be disabled- IIRC, it caused
considerable slowness on our NT Server and Exchange 5.0(?) setup when
sending or replying to emails.

And I believe that Word 2003 uses OL as the default for "Send by email",
and if OL isn't installed, the "Send. . ." option is grayed out (or at
least it is on my Win8 machine with Word 2003 installed). On my Win7
machine with OL installed, the email options are available.

WU offers the "Update for Outlook 2003 Junk E-mail Filter (KBxxxxxxx)"
each month for both machines. I accept it on the one with OL installed,
but refuse it on the other. Word still works the same otherwise, word
up! :-)

It's been some time since I used Office 2003 (and OL03)

My recollection was that prior to OL03 the default editor was Outlook.
In OL03 Word was the default editor but could be turned off.

I certain that thereafter for OL07-10/13 the default editor is Word with
no ability to turn off.


--
...winston
msft mvp consumer apps

On Sat, 12 Oct 2013 23:00:36 -0400, "...winston"
wrote:

I certain that thereafter for OL07-10/13 the default editor is Word with
no ability to turn off.


I'm using Outlook 2013 and if the editor is Word I hadn't realized it.
How can I tell?

On 10/13/2013 10:09 AM, Ken Blake wrote:
On Sat, 12 Oct 2013 23:00:36 -0400, "...winston"
wrote:

I certain that thereafter for OL07-10/13 the default editor is Word with
no ability to turn off.


I'm using Outlook 2013 and if the editor is Word I hadn't realized it.
How can I tell?




Winword.exe shows up in Task Manager "Processes"

Ken Blake wrote:

"...winston" wrote:

I certain that thereafter for OL07-10/13 the default editor is Word with
no ability to turn off.

I'm using Outlook 2013 and if the editor is Word I hadn't realized it.
How can I tell?

Ever since Outlook 2007, and up, and even if you don't install MS Office
but just install a standalone copy of Outlook 2007+ or just pick Outlook
from the custom install of MS Office 2007+, Outlook uses Word. If Word
is present then it uses that. If Word is not present, Outlook comes
with a "stub" of Word to use that as its editor. So you're stuck using
Word with all its bloat and HTML-specific tags (that only Word
understands) when you compose in rich-text format (HTML or RTF).

http://support.microsoft.com/kb/933793

When I got MS Office 2010 Home & Student OEM included on an old computer
my buddy gave me (it was broke, I fixed it, I got to keep it), I really
didn't miss Outlook 2010 which is excluded from that edition. I just
installed only the Outlook component from my old MS Office 2003 retail
(that was no longer in use because that computer really died hard and my
buddy gave me his brother's broke one figuring that could be fixed). So
I have Office 2010 H&S (no Outlook) with Outlook 2003. That lets me use
the inbuilt editor in OL2003 instead of bloating my e-mails with Word-
specific HTML code if Word gets used as the editor.

As of Outlook 2007, and later, users no longer have a choice which
editor to use in the new-mail compose window. It'll be Word. Besides
not having to support to editors in Outlook, I suspect they also want to
reduce tech calls on why integration features didn't work because the
user had mixed versions of Word and Outlook. While you can have
multiple versions of other components of Office installed, you can have
only one version of Outlook installed at a time. So someone that kept
Outlook 2003 that installed Office 2010 would end up the later version
2010 or the earlier version 2003 but could not have both installed. I
didn't care that integration features between Outlook 2003 and Word 2010
were unavailable. Since I didn't want to use Word as the editor, I also
didn't need the integration features.

Ken Blake wrote:
On Sat, 12 Oct 2013 23:00:36 -0400, "...winston"
wrote:

I certain that thereafter for OL07-10/13 the default editor is Word with
no ability to turn off.


I'm using Outlook 2013 and if the editor is Word I hadn't realized it.
How can I tell?




If 2013 and 2010 and 2007 before you've been using Word in OL for
some time g

I recall looking for 'how' some time ago but didn't notice anything in
Task Manager that called or loaded Word. Most likely it's built into OL
in conjunction with shared files.


--
...winston
msft mvp consumer apps

On Sun, 13 Oct 2013 17:50:13 -0500, Bob I wrote:



On 10/13/2013 10:09 AM, Ken Blake wrote:
On Sat, 12 Oct 2013 23:00:36 -0400, "...winston"
wrote:

I certain that thereafter for OL07-10/13 the default editor is Word with
no ability to turn off.


I'm using Outlook 2013 and if the editor is Word I hadn't realized it.
How can I tell?




Winword.exe shows up in Task Manager "Processes"


I just checked. No it doesn't--not here.

Ken

On Sun, 13 Oct 2013 21:03:27 -0500, VanguardLH wrote:

Ken Blake wrote:

"...winston" wrote:

I certain that thereafter for OL07-10/13 the default editor is Word with
no ability to turn off.

I'm using Outlook 2013 and if the editor is Word I hadn't realized it.
How can I tell?

Ever since Outlook 2007, and up, and even if you don't install MS Office
but just install a standalone copy of Outlook 2007+ or just pick Outlook
from the custom install of MS Office 2007+, Outlook uses Word. If Word
is present then it uses that. If Word is not present, Outlook comes
with a "stub" of Word to use that as its editor. So you're stuck using
Word with all its bloat and HTML-specific tags (that only Word
understands) when you compose in rich-text format (HTML or RTF).


But I never compose in anything but plain text. Perhaps that's why I
don't see the Winword process in task manager.


http://support.microsoft.com/kb/933793


Thanks. That clearly says it's *always* Word. But perhaps it means
that it's always Word *if* you write html e-mail.