S
Scott Boettcher
Anyone from MS care to reply?
I¹ve installed it on my test Macs, and they ³appear² OK, but...
Scott
I¹ve installed it on my test Macs, and they ³appear² OK, but...
Scott
for Mac
We¹ve seen some questions from customers about some security updates that
posted for a while today for Office for Mac that they didn¹t see any security
bulletins for.
I wanted to let you know that these weren¹t security updates related to this
month¹s release or the two Word issues we¹ve written about in Security
Advisory 929433 and on our weblog: those investigations are still underway and
we¹ll release updates for those issues once we¹ve met the appropriate quality
bar. The updates posted in error were pre-release binaries that had been
staged internally as part of our testing for an upcoming release. Due to
human error, they were accidentally published to the public websites before
our full testing release process was complete.
As soon as we discovered the error, we moved quickly to address it and remove
the pre-release binaries from our public sites.
Once our investigation into this issue is complete and we have security
updates that meet our quality bar for release, we¹ll release those final
security updates for all products affected along with a security bulletin.
We¹re also taking steps to ensure a mistake like this doesn¹t happen again.
We recommend that anyone who may have installed these pre-release updates to
uninstall them.
I¹m sorry for any confusion this might have caused.
Thanks.
Mike
*This posting is provided "AS IS" with no warranties, and confers no rights.
<http://blogs.technet.com/msrc/archive/2006/12/13/information-on-accidental-
posting-of-pre-release-security-updates-for-office-for-mac.aspx>
Anyone from MS care to reply?
I¹ve installed it on my test Macs, and they ³appear² OK, but...
Scott
Mike, I used Office 2004's built-in auto-update application rather than
downloading anything posted at versiontracker. Does that make a difference?
If not, what's the least time-consuming to fix it?
So, yes, is there a way to back off this update without recreating the
world? Should I try to remove the update if it does not appear to be
broken? Does anyone know about the dynamics of the bad effects people have
seen -- do they show up right away?
Well, I'm not sure if Mike checks these newsgroups. I only quoted his blog
entry.
Too soon to tell. The blog entry says that this update was not meant to be
released to the wider public, as it is still in some kind of beta state.
This can mean that some things are broken, or will break at some point. It
can also mean that the beta is stable enough for the everyday use. If I were
you, I'd keep using it if there are no apparent problems. Of course, it is
not known whether the real update, when it comes out, will simply fix the
update or whether you'll be forced to remove and re-install Office at that
point.
Michael Bintener:
Thanks for your post on this thread:
Ummmmm, so the situation is clear ... as mud.
Would you pass on to your colleagues "inside" the suggestion that the
company issue a definitive advisory on this subject, so people who depend on
their products --and trusted the MS auto-update process-- might be
reassured. Or advised how to repair defect(s) introduced by this mishap?
Soon would be best. Today would work great.
Thanks,
Henry
Ummmmm, so the situation is clear ... as mud.
Would you pass on to your colleagues "inside" the suggestion that the
company issue a definitive advisory on this subject, so people who depend on
their products --and trusted the MS auto-update process-- might be
reassured. Or advised how to repair defect(s) introduced by this mishap?
Soon would be best. Today would work great.