KB956358 and problems with networked startup locations

[Rohan Salt]

KB956358 alters Word startup behaviour for Startup location on network drives.

A dotm in Word's default startup location which on a network location will
no longer be trusted by default (and hence vba code is disabled) even when
Trust Center's "Allow Trusted Location on my network" is set .

Prior to this, this the startup location was always trusted!

The work around for this is to:
* deploy the template on each workstation or
* digitally sign the template, change security to "Disable all macros except
digitally signed macros", and add the owner of the certificate to the list of
trusted publishers.

Which is great except for smaller organisations that write their own
templates and don't have a code signing certificate or want to streamline the
rollout of new versions of the startup template by keeping a single copy
centrally.

Does anyone know if this is a permanent change or an oversight likely to be
reversed out in a couple of days?

 

[Hamish Blunck]

KB956358alters Word startup behaviour for Startup location on network drives.

A dotm in Word's default startup location which on a network location will
no longer be trusted by default (and hence vba code is disabled) even when
Trust Center's "Allow Trusted Location on my network" is set .

Prior to this, this the startup location was always trusted!

The work around for this is to:
* deploy the template on each workstation or
* digitally sign the template, change security to "Disable all macros except
digitally signed macros", and add the owner of the certificate to the list of
trusted publishers.  

Which is great except for smaller organisations that write their own
templates and don't have a code signing certificate or want to streamlinethe
rollout of new versions of the startup template by keeping a single copy
centrally.

Does anyone know if this is a permanent change or an oversight likely to be
reversed out in a couple of days?

I too am hoping this was an oversight or will be reversed. Or at least
an easy workaround/fix made.

I am using Author-it (content authoring system) that uses Word
templates stored on a network drive, and it fails now after applying
the
KB956358 update.

Does anyone know of any way of getting around this apart from the
solutions offered by Rohan above?

Thanks
Hamish