Anyone Applied DST KB926666 Yet?

We are runnning W2K3 SP2 and I am reading the articles regarding the DST
patch. Article KB912918 (mobile devices or shared mailboxes) has caught my
attention.
It appears that the new version of Store.exe that will be upgraded in the
DST patch will change the way that permissions work. No longer is it enough
to have
full mailbox priviledges but you must also set a Send As permission too on
accounts that open additional mailboxes. I am worried that this will blow
up our BlackBerry
Enterprise Server and our numerous people that open additional mailboxes.

Has anyone updated their E2K3 servers with the new DST patch? If so, how
did it affect your environment?


Thanks,
Fred

Andy
Tue Feb 06 14:42:41 CST 2007

On Tue, 6 Feb 2007 14:33:52 -0600, "Fred Yarbrough"
<fcyarbrough@yahoo.com> wrote:

>We are runnning W2K3 SP2 and I am reading the articles regarding the DST
>patch. Article KB912918 (mobile devices or shared mailboxes) has caught my
>attention.
>It appears that the new version of Store.exe that will be upgraded in the
>DST patch will change the way that permissions work. No longer is it enough
>to have
>full mailbox priviledges but you must also set a Send As permission too on
>accounts that open additional mailboxes. I am worried that this will blow
>up our BlackBerry
>Enterprise Server and our numerous people that open additional mailboxes.
>
>Has anyone updated their E2K3 servers with the new DST patch? If so, how
>did it affect your environment?
>
>
>Thanks,
>Fred
>


The updated store has been around for about a year since
http://support.microsoft.com/kb/895949

and is incorporated into every post Sp2 store.exe hotfix.

Betelgeuse
Tue Feb 06 14:44:28 CST 2007

I am in the process of applying it across 11 servers. It did blow up one of
our BES servers pretty badly.

RIM is a better source of support on this, but here is the thumbnail sketch.

Log on to a desktop machine as the BES account. Then open a mailbox for a
user that the BES account has access to.
Open an email, address it to yourself, and make sure you SEND IT AS THE BES
ACCOUNT.

If your perms are in order, the message will go.
If your perms are not in order, you will need to adjust the SEND AS
permission.

ONe way to do that is open ADUC, View | Show Advanced.

Then, highlight the top node in your domain, (company.local, or whatever it
is) and right click | properties. Security tab click ADvanced, and then
add...add in the BES accnt IN the box that appears, change the Applies To:
to User objects, and then check SEND AS.

OK out.....once this bakes through your AD and exchange environment, you
should be able to apply the patch with no issues.
I have noticed that rebooting both the BES and EXchange servers is
mandantory...











"Fred Yarbrough" <fcyarbrough@yahoo.com> wrote in message
news:%23eXVe4iSHHA.496@TK2MSFTNGP06.phx.gbl...
> We are runnning W2K3 SP2 and I am reading the articles regarding the DST
> patch. Article KB912918 (mobile devices or shared mailboxes) has caught
> my attention.
> It appears that the new version of Store.exe that will be upgraded in the
> DST patch will change the way that permissions work. No longer is it
> enough to have
> full mailbox priviledges but you must also set a Send As permission too on
> accounts that open additional mailboxes. I am worried that this will blow
> up our BlackBerry
> Enterprise Server and our numerous people that open additional mailboxes.
>
> Has anyone updated their E2K3 servers with the new DST patch? If so, how
> did it affect your environment?
>
>
> Thanks,
> Fred
>

WILDPACKET
Tue Feb 06 14:46:01 CST 2007


Hold on do not apply 926666 yet. Here is what Microsoft says .....

We are seeing some edge cases where under certain circumstances applying KB
926666 (â??Update for daylight saving time changes in 2007 for Exchange 2003,â??
this is the CDO update for Exchange server) will cause the Exchange store not
to mount. It doesnâ??t apply to all servers and is still under investigation.
Currently the two possible causes are:

1. If a built-in group (such as Administrators, for example) was delegated
permissions at the Org and Admin Group levels.
2. If a regular user/group had the same MSEXCHMASTERACCOUNTSID or SIDHISTORY
value as another user/group.

A fix is currently being tested. So the best advice at this point is not to
deploy 926666 until we get an update.

For BES read this ....KB-04707

http://www.blackberry.com/btsc/search.do?cmd=displayKC&docType=kc&externalId=KB04707&sliceId=SAL_Public&dialogID=2960015&stateId=0%200%202958237






"Fred Yarbrough" wrote:

> We are runnning W2K3 SP2 and I am reading the articles regarding the DST
> patch. Article KB912918 (mobile devices or shared mailboxes) has caught my
> attention.
> It appears that the new version of Store.exe that will be upgraded in the
> DST patch will change the way that permissions work. No longer is it enough
> to have
> full mailbox priviledges but you must also set a Send As permission too on
> accounts that open additional mailboxes. I am worried that this will blow
> up our BlackBerry
> Enterprise Server and our numerous people that open additional mailboxes.
>
> Has anyone updated their E2K3 servers with the new DST patch? If so, how
> did it affect your environment?
>
>
> Thanks,
> Fred
>
>
>

Andy
Tue Feb 06 14:52:39 CST 2007

On Tue, 6 Feb 2007 15:44:28 -0500, "Betelgeuse"
<betelgeuse@news.postalias> wrote:

>I am in the process of applying it across 11 servers. It did blow up one of
>our BES servers pretty badly.
>
>RIM is a better source of support on this, but here is the thumbnail sketch.
>
>Log on to a desktop machine as the BES account. Then open a mailbox for a
>user that the BES account has access to.
>Open an email, address it to yourself, and make sure you SEND IT AS THE BES
>ACCOUNT.
>
>If your perms are in order, the message will go.
>If your perms are not in order, you will need to adjust the SEND AS
>permission.
>
>ONe way to do that is open ADUC, View | Show Advanced.
>
>Then, highlight the top node in your domain, (company.local, or whatever it
>is) and right click | properties. Security tab click ADvanced, and then
>add...add in the BES accnt IN the box that appears, change the Applies To:
>to User objects, and then check SEND AS.
>
>OK out.....once this bakes through your AD and exchange environment, you
>should be able to apply the patch with no issues.
>I have noticed that rebooting both the BES and EXchange servers is
>mandantory...

It should be noted that the DST patch itself is not the cause, but
rather the updated store.exe that is part of the update.
If the BES problem is biting you now, it just means you havent been
applying any hotfixes to your server lately :)


>
>
>
>
>
>
>
>
>
>
>
>"Fred Yarbrough" <fcyarbrough@yahoo.com> wrote in message
>news:%23eXVe4iSHHA.496@TK2MSFTNGP06.phx.gbl...
>> We are runnning W2K3 SP2 and I am reading the articles regarding the DST
>> patch. Article KB912918 (mobile devices or shared mailboxes) has caught
>> my attention.
>> It appears that the new version of Store.exe that will be upgraded in the
>> DST patch will change the way that permissions work. No longer is it
>> enough to have
>> full mailbox priviledges but you must also set a Send As permission too on
>> accounts that open additional mailboxes. I am worried that this will blow
>> up our BlackBerry
>> Enterprise Server and our numerous people that open additional mailboxes.
>>
>> Has anyone updated their E2K3 servers with the new DST patch? If so, how
>> did it affect your environment?
>>
>>
>> Thanks,
>> Fred
>>
>

Jim
Tue Feb 06 14:56:52 CST 2007

I am recommending that you wait on applying the Exchange patch for a few
more weeks. Certainly you need to be doing your homework and planning for
it, but avoid it for now. A lot of the problems that are popping up,
though, are people that have not applied any of the post SP2 fixes for
Exhange, such as the Blackberry fix.
http://mostlyexchange.blogspot.com/2006/05/exchange-fix-breaks-blackberry-and.html

When you apply the DST fix, you need to be prepared for a few things like
this. We are seeing more information popping up about the best ways to
apply this fix and I think Microsoft will be improving their documentation
very shortly. The folks that have gotten burned seems to be the early
adopters of this fix.

Just my opinion.

--
Jim McBee
Blog - http://mostlyexchange.blogspot.com
Directory Update - http://www.directory-update.com



"Fred Yarbrough" <fcyarbrough@yahoo.com> wrote in message
news:%23eXVe4iSHHA.496@TK2MSFTNGP06.phx.gbl...
> We are runnning W2K3 SP2 and I am reading the articles regarding the DST
> patch. Article KB912918 (mobile devices or shared mailboxes) has caught
> my attention.
> It appears that the new version of Store.exe that will be upgraded in the
> DST patch will change the way that permissions work. No longer is it
> enough to have
> full mailbox priviledges but you must also set a Send As permission too on
> accounts that open additional mailboxes. I am worried that this will blow
> up our BlackBerry
> Enterprise Server and our numerous people that open additional mailboxes.
>
> Has anyone updated their E2K3 servers with the new DST patch? If so, how
> did it affect your environment?
>
>
> Thanks,
> Fred
>

Jim
Tue Feb 06 15:11:05 CST 2007

But, have their been any *public* hotfixes that changed the store
permissions? :-)

From the KB article: "A supported hotfix is now available from Microsoft,
but it is only intended to correct the problem that this article describes.
Apply it only to systems that are experiencing this specific problem."

--
Jim McBee
Blog - http://mostlyexchange.blogspot.com
Directory Update - http://www.directory-update.com


>>OK out.....once this bakes through your AD and exchange environment, you
>>should be able to apply the patch with no issues.
>>I have noticed that rebooting both the BES and EXchange servers is
>>mandantory...
>
> It should be noted that the DST patch itself is not the cause, but
> rather the updated store.exe that is part of the update.
> If the BES problem is biting you now, it just means you havent been
> applying any hotfixes to your server lately :)
>
>

RealDeal1
Tue Feb 06 15:15:14 CST 2007

It is inevitable that this update will be applied to your Exchange server
since it is part of the Store.exe revision and any revisions of store.exe
will include it anyway. We got complains the first time we applied the patch
because no longer did simply having complete mailbox rights allow the users
to Send As. Fortunately we did not have many users utalizing this feature.
After you get used to it and understand how it works, it should get easier.

Blackberry and Goodlink are definate issues with this patch.


"Fred Yarbrough" <fcyarbrough@yahoo.com> wrote in message
news:%23eXVe4iSHHA.496@TK2MSFTNGP06.phx.gbl...
> We are runnning W2K3 SP2 and I am reading the articles regarding the DST
> patch. Article KB912918 (mobile devices or shared mailboxes) has caught
> my attention.
> It appears that the new version of Store.exe that will be upgraded in the
> DST patch will change the way that permissions work. No longer is it
> enough to have
> full mailbox priviledges but you must also set a Send As permission too on
> accounts that open additional mailboxes. I am worried that this will blow
> up our BlackBerry
> Enterprise Server and our numerous people that open additional mailboxes.
>
> Has anyone updated their E2K3 servers with the new DST patch? If so, how
> did it affect your environment?
>
>
> Thanks,
> Fred
>

Andy
Tue Feb 06 15:17:21 CST 2007

On Tue, 6 Feb 2007 11:11:05 -1000, "Jim McBee \(MVP - Exchange\)"
<jmcbee@cta.spambegone.net> wrote:

>But, have their been any *public* hotfixes that changed the store
>permissions? :-)



>
>From the KB article: "A supported hotfix is now available from Microsoft,
>but it is only intended to correct the problem that this article describes.
>Apply it only to systems that are experiencing this specific problem."


http://www.microsoft.com/technet/security/Bulletin/MS06-019.mspx
http://www.microsoft.com/technet/security/Bulletin/MS06-029.mspx

I'm pretty sure they incorporated the new store :P

Fred
Tue Feb 06 16:56:28 CST 2007

Thanks guys.

I normally don't go around and patch servers with hotfixes unless I am
experiencing the problem it resolves.

The fact that this new store.exe is being bundled with the DST patch really
stinks. This is now just one more issue for me to worry about.

Thanks,
Fred





<RealDeal1@nospam.nospam> wrote in message
news:eEhArPjSHHA.4028@TK2MSFTNGP03.phx.gbl...
> It is inevitable that this update will be applied to your Exchange server
> since it is part of the Store.exe revision and any revisions of store.exe
> will include it anyway. We got complains the first time we applied the
> patch because no longer did simply having complete mailbox rights allow
> the users to Send As. Fortunately we did not have many users utalizing
> this feature. After you get used to it and understand how it works, it
> should get easier.
>
> Blackberry and Goodlink are definate issues with this patch.
>
>
> "Fred Yarbrough" <fcyarbrough@yahoo.com> wrote in message
> news:%23eXVe4iSHHA.496@TK2MSFTNGP06.phx.gbl...
>> We are runnning W2K3 SP2 and I am reading the articles regarding the DST
>> patch. Article KB912918 (mobile devices or shared mailboxes) has caught
>> my attention.
>> It appears that the new version of Store.exe that will be upgraded in the
>> DST patch will change the way that permissions work. No longer is it
>> enough to have
>> full mailbox priviledges but you must also set a Send As permission too
>> on accounts that open additional mailboxes. I am worried that this will
>> blow up our BlackBerry
>> Enterprise Server and our numerous people that open additional mailboxes.
>>
>> Has anyone updated their E2K3 servers with the new DST patch? If so, how
>> did it affect your environment?
>>
>>
>> Thanks,
>> Fred
>>
>
>

WoodyAnderson
Tue Feb 06 17:30:02 CST 2007

We are looking to install this patch tonight (as well as the other DST
fixes).

We're at: SBS2K3 SP1 w/ Exchange 2003 SP2

Besides installing Exchange SP2 & regular windows updates, we haven't
installed any other hot fixes. I am concerned about the changes to the
store, but it sounds like it is inevitable and waiting another two weeks may
not make a difference since these changes have already been implemented in
other hotfixes.

We don't have a BES or Goodlink, but do use Exchange Activesync.

I have searched high and low for any other issues with this patch and there
are not many. Maybe the patch is too new and many of the issues haven't been
documented. I'm hoping not to become a bad statistic. We plan to follow the
path laid out by MS. Servers-Workstations-Exchange-Outlook Tool.
-Woody

"Fred Yarbrough" wrote:

> We are runnning W2K3 SP2 and I am reading the articles regarding the DST
> patch. Article KB912918 (mobile devices or shared mailboxes) has caught my
> attention.
> It appears that the new version of Store.exe that will be upgraded in the
> DST patch will change the way that permissions work. No longer is it enough
> to have
> full mailbox priviledges but you must also set a Send As permission too on
> accounts that open additional mailboxes. I am worried that this will blow
> up our BlackBerry
> Enterprise Server and our numerous people that open additional mailboxes.
>
> Has anyone updated their E2K3 servers with the new DST patch? If so, how
> did it affect your environment?
>
>
> Thanks,
> Fred
>
>
>

Andy
Tue Feb 06 17:43:02 CST 2007

On Tue, 6 Feb 2007 16:56:28 -0600, "Fred Yarbrough"
<fcyarbrough@yahoo.com> wrote:

>Thanks guys.
>
>I normally don't go around and patch servers with hotfixes unless I am
>experiencing the problem it resolves.

Not even security fixes?

>
>The fact that this new store.exe is being bundled with the DST patch really
>stinks. This is now just one more issue for me to worry about.

The fix is easy enough. The only bump is if you attempt to apply the
SEND AS perms to accounts that hold the adminSDHolder role.
Documented in:
http://support.microsoft.com/kb/912918


>
>Thanks,
>Fred
>
>
>
>
>
><RealDeal1@nospam.nospam> wrote in message
>news:eEhArPjSHHA.4028@TK2MSFTNGP03.phx.gbl...
>> It is inevitable that this update will be applied to your Exchange server
>> since it is part of the Store.exe revision and any revisions of store.exe
>> will include it anyway. We got complains the first time we applied the
>> patch because no longer did simply having complete mailbox rights allow
>> the users to Send As. Fortunately we did not have many users utalizing
>> this feature. After you get used to it and understand how it works, it
>> should get easier.
>>
>> Blackberry and Goodlink are definate issues with this patch.
>>
>>
>> "Fred Yarbrough" <fcyarbrough@yahoo.com> wrote in message
>> news:%23eXVe4iSHHA.496@TK2MSFTNGP06.phx.gbl...
>>> We are runnning W2K3 SP2 and I am reading the articles regarding the DST
>>> patch. Article KB912918 (mobile devices or shared mailboxes) has caught
>>> my attention.
>>> It appears that the new version of Store.exe that will be upgraded in the
>>> DST patch will change the way that permissions work. No longer is it
>>> enough to have
>>> full mailbox priviledges but you must also set a Send As permission too
>>> on accounts that open additional mailboxes. I am worried that this will
>>> blow up our BlackBerry
>>> Enterprise Server and our numerous people that open additional mailboxes.
>>>
>>> Has anyone updated their E2K3 servers with the new DST patch? If so, how
>>> did it affect your environment?
>>>
>>>
>>> Thanks,
>>> Fred
>>>
>>
>>
>

Rich
Tue Feb 06 22:20:08 CST 2007

Andy David {MVP} <adavid@pleasekeepinngcheesebucket.com> wrote:

[ snip ]

>The fix is easy enough. The only bump is if you attempt to apply the
>SEND AS perms to accounts that hold the adminSDHolder role.
>Documented in:
>http://support.microsoft.com/kb/912918

The "only bump" too me over two man-weeks to prepare for! Ferreting
out all the potential problems required making changes to the supplied
VBS script to separate the accounts that had Send As but never needed
it, but had it applied through inheritance. There were a couple of
other twists in there, too. After 9 years of operation, acquisitions,
mergers, divestitures, different admins doing some rather odd things,
etc. it was an "interesting" exercise.

--
Rich Matheisen
MCSE+I, Exchange MVP
MS Exchange FAQ at http://www.swinc.com/resource/exch_faq.htm
Don't send mail to this address mailto:h.pott@getronics.com
Or to these, either: mailto:h.pott@pinkroccade.com mailto:melvin.mcphucknuckle@getronics.com mailto:melvin.mcphucknuckle@pinkroccade.com

Andy
Wed Feb 07 06:33:49 CST 2007

On Tue, 06 Feb 2007 23:20:08 -0500, "Rich Matheisen [MVP]"
<richnews@rmcons.com.NOSPAM.COM> wrote:

>Andy David {MVP} <adavid@pleasekeepinngcheesebucket.com> wrote:
>
> [ snip ]
>
>>The fix is easy enough. The only bump is if you attempt to apply the
>>SEND AS perms to accounts that hold the adminSDHolder role.
>>Documented in:
>>http://support.microsoft.com/kb/912918
>
>The "only bump" too me over two man-weeks to prepare for! Ferreting
>out all the potential problems required making changes to the supplied
>VBS script to separate the accounts that had Send As but never needed
>it, but had it applied through inheritance. There were a couple of
>other twists in there, too. After 9 years of operation, acquisitions,
>mergers, divestitures, different admins doing some rather odd things,
>etc. it was an "interesting" exercise.

Ah yes, there are always those intangibles. :P

Betelgeuse
Wed Feb 07 08:13:39 CST 2007

Actually, all BES'es are up to date, and all exchange servers are SP2.....
This version of store.exe initially would not mount stores in our
environment. I opened a PSS ticket on that, and got a work-around, but not
a fix.....

"Andy David {MVP}" <adavid@pleasekeepinngcheesebucket.com> wrote in message
news:ahqhs2hetdiqndus4tjrnkccmm6ev15age@4ax.com...
> On Tue, 6 Feb 2007 15:44:28 -0500, "Betelgeuse"
> <betelgeuse@news.postalias> wrote:
>
>>I am in the process of applying it across 11 servers. It did blow up one
>>of
>>our BES servers pretty badly.
>>
>>RIM is a better source of support on this, but here is the thumbnail
>>sketch.
>>
>>Log on to a desktop machine as the BES account. Then open a mailbox for a
>>user that the BES account has access to.
>>Open an email, address it to yourself, and make sure you SEND IT AS THE
>>BES
>>ACCOUNT.
>>
>>If your perms are in order, the message will go.
>>If your perms are not in order, you will need to adjust the SEND AS
>>permission.
>>
>>ONe way to do that is open ADUC, View | Show Advanced.
>>
>>Then, highlight the top node in your domain, (company.local, or whatever
>>it
>>is) and right click | properties. Security tab click ADvanced, and then
>>add...add in the BES accnt IN the box that appears, change the Applies
>>To:
>>to User objects, and then check SEND AS.
>>
>>OK out.....once this bakes through your AD and exchange environment, you
>>should be able to apply the patch with no issues.
>>I have noticed that rebooting both the BES and EXchange servers is
>>mandantory...
>
> It should be noted that the DST patch itself is not the cause, but
> rather the updated store.exe that is part of the update.
> If the BES problem is biting you now, it just means you havent been
> applying any hotfixes to your server lately :)
>
>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>"Fred Yarbrough" <fcyarbrough@yahoo.com> wrote in message
>>news:%23eXVe4iSHHA.496@TK2MSFTNGP06.phx.gbl...
>>> We are runnning W2K3 SP2 and I am reading the articles regarding the DST
>>> patch. Article KB912918 (mobile devices or shared mailboxes) has caught
>>> my attention.
>>> It appears that the new version of Store.exe that will be upgraded in
>>> the
>>> DST patch will change the way that permissions work. No longer is it
>>> enough to have
>>> full mailbox priviledges but you must also set a Send As permission too
>>> on
>>> accounts that open additional mailboxes. I am worried that this will
>>> blow
>>> up our BlackBerry
>>> Enterprise Server and our numerous people that open additional
>>> mailboxes.
>>>
>>> Has anyone updated their E2K3 servers with the new DST patch? If so,
>>> how
>>> did it affect your environment?
>>>
>>>
>>> Thanks,
>>> Fred
>>>
>>

WoodyAnderson
Wed Feb 07 08:58:00 CST 2007

We held off applying this and the other DST fixes last night. It seemed
unnecessary to rush into this if there are known issues. We'll shoot for
applying it in two weeks after we see how this shakes out with MS.

"WoodyAnderson" wrote:

> We are looking to install this patch tonight (as well as the other DST
> fixes).
>
> We're at: SBS2K3 SP1 w/ Exchange 2003 SP2
>
> Besides installing Exchange SP2 & regular windows updates, we haven't
> installed any other hot fixes. I am concerned about the changes to the
> store, but it sounds like it is inevitable and waiting another two weeks may
> not make a difference since these changes have already been implemented in
> other hotfixes.
>
> We don't have a BES or Goodlink, but do use Exchange Activesync.
>
> I have searched high and low for any other issues with this patch and there
> are not many. Maybe the patch is too new and many of the issues haven't been
> documented. I'm hoping not to become a bad statistic. We plan to follow the
> path laid out by MS. Servers-Workstations-Exchange-Outlook Tool.
> -Woody
>
> "Fred Yarbrough" wrote:
>
> > We are runnning W2K3 SP2 and I am reading the articles regarding the DST
> > patch. Article KB912918 (mobile devices or shared mailboxes) has caught my
> > attention.
> > It appears that the new version of Store.exe that will be upgraded in the
> > DST patch will change the way that permissions work. No longer is it enough
> > to have
> > full mailbox priviledges but you must also set a Send As permission too on
> > accounts that open additional mailboxes. I am worried that this will blow
> > up our BlackBerry
> > Enterprise Server and our numerous people that open additional mailboxes.
> >
> > Has anyone updated their E2K3 servers with the new DST patch? If so, how
> > did it affect your environment?
> >
> >
> > Thanks,
> > Fred
> >
> >
> >

WoodyAnderson
Wed Feb 07 12:05:02 CST 2007

It seems like others have had success in removing the 926666 fix if the store
would not mount. Is that going to mess things up if the Windows DST fix is
installed on all servers and workstations, but 926666 is not...nor has the
Outlook tool been run?
It seems MS recommends rapid succession of installs, so stopping short of
installing 926666 would present problems??

"WoodyAnderson" wrote:

> We held off applying this and the other DST fixes last night. It seemed
> unnecessary to rush into this if there are known issues. We'll shoot for
> applying it in two weeks after we see how this shakes out with MS.
>
> "WoodyAnderson" wrote:
>
> > We are looking to install this patch tonight (as well as the other DST
> > fixes).
> >
> > We're at: SBS2K3 SP1 w/ Exchange 2003 SP2
> >
> > Besides installing Exchange SP2 & regular windows updates, we haven't
> > installed any other hot fixes. I am concerned about the changes to the
> > store, but it sounds like it is inevitable and waiting another two weeks may
> > not make a difference since these changes have already been implemented in
> > other hotfixes.
> >
> > We don't have a BES or Goodlink, but do use Exchange Activesync.
> >
> > I have searched high and low for any other issues with this patch and there
> > are not many. Maybe the patch is too new and many of the issues haven't been
> > documented. I'm hoping not to become a bad statistic. We plan to follow the
> > path laid out by MS. Servers-Workstations-Exchange-Outlook Tool.
> > -Woody
> >
> > "Fred Yarbrough" wrote:
> >
> > > We are runnning W2K3 SP2 and I am reading the articles regarding the DST
> > > patch. Article KB912918 (mobile devices or shared mailboxes) has caught my
> > > attention.
> > > It appears that the new version of Store.exe that will be upgraded in the
> > > DST patch will change the way that permissions work. No longer is it enough
> > > to have
> > > full mailbox priviledges but you must also set a Send As permission too on
> > > accounts that open additional mailboxes. I am worried that this will blow
> > > up our BlackBerry
> > > Enterprise Server and our numerous people that open additional mailboxes.
> > >
> > > Has anyone updated their E2K3 servers with the new DST patch? If so, how
> > > did it affect your environment?
> > >
> > >
> > > Thanks,
> > > Fred
> > >
> > >
> > >

Andy
Wed Feb 07 12:17:34 CST 2007

On Wed, 7 Feb 2007 10:05:02 -0800, WoodyAnderson
<WoodyAnderson@discussions.microsoft.com> wrote:

>It seems like others have had success in removing the 926666 fix if the store
>would not mount. Is that going to mess things up if the Windows DST fix is
>installed on all servers and workstations, but 926666 is not...nor has the
>Outlook tool been run?
>It seems MS recommends rapid succession of installs, so stopping short of
>installing 926666 would present problems??
>

I would not run any tool until the server/OS and Exch patches are all
applied.


>"WoodyAnderson" wrote:
>
>> We held off applying this and the other DST fixes last night. It seemed
>> unnecessary to rush into this if there are known issues. We'll shoot for
>> applying it in two weeks after we see how this shakes out with MS.
>>
>> "WoodyAnderson" wrote:
>>
>> > We are looking to install this patch tonight (as well as the other DST
>> > fixes).
>> >
>> > We're at: SBS2K3 SP1 w/ Exchange 2003 SP2
>> >
>> > Besides installing Exchange SP2 & regular windows updates, we haven't
>> > installed any other hot fixes. I am concerned about the changes to the
>> > store, but it sounds like it is inevitable and waiting another two weeks may
>> > not make a difference since these changes have already been implemented in
>> > other hotfixes.
>> >
>> > We don't have a BES or Goodlink, but do use Exchange Activesync.
>> >
>> > I have searched high and low for any other issues with this patch and there
>> > are not many. Maybe the patch is too new and many of the issues haven't been
>> > documented. I'm hoping not to become a bad statistic. We plan to follow the
>> > path laid out by MS. Servers-Workstations-Exchange-Outlook Tool.
>> > -Woody
>> >
>> > "Fred Yarbrough" wrote:
>> >
>> > > We are runnning W2K3 SP2 and I am reading the articles regarding the DST
>> > > patch. Article KB912918 (mobile devices or shared mailboxes) has caught my
>> > > attention.
>> > > It appears that the new version of Store.exe that will be upgraded in the
>> > > DST patch will change the way that permissions work. No longer is it enough
>> > > to have
>> > > full mailbox priviledges but you must also set a Send As permission too on
>> > > accounts that open additional mailboxes. I am worried that this will blow
>> > > up our BlackBerry
>> > > Enterprise Server and our numerous people that open additional mailboxes.
>> > >
>> > > Has anyone updated their E2K3 servers with the new DST patch? If so, how
>> > > did it affect your environment?
>> > >
>> > >
>> > > Thanks,
>> > > Fred
>> > >
>> > >
>> > >

hagemanoh
Fri Mar 02 11:03:38 CST 2007

Hi Fred,

Yes. I applied it last night and it broke the heck out of our BES
server. Haven't had any issues, yet, with others opening other mailboxes.
In fact I'm waiting to speak with RIM now on this issue. From what I have
read thus far, I'm lucky, it appears in a lot of case the update causes the
mail stores to not want to mount. My Blackberry users keep getting a red X
when trying to send e-miails. They are able to receive without problems. I
have followed everything in Microsoft article 912918 but it still does not
work. Good Luck!



"Fred Yarbrough" wrote:

> We are runnning W2K3 SP2 and I am reading the articles regarding the DST
> patch. Article KB912918 (mobile devices or shared mailboxes) has caught my
> attention.
> It appears that the new version of Store.exe that will be upgraded in the
> DST patch will change the way that permissions work. No longer is it enough
> to have
> full mailbox priviledges but you must also set a Send As permission too on
> accounts that open additional mailboxes. I am worried that this will blow
> up our BlackBerry
> Enterprise Server and our numerous people that open additional mailboxes.
>
> Has anyone updated their E2K3 servers with the new DST patch? If so, how
> did it affect your environment?
>
>
> Thanks,
> Fred
>
>
>