From: Ace Fekay [MVP-DS, MCT] on

"Jim" <jim(a)dontwantspam.com> wrote in message news:hqbspv$11g7$1(a)energise.enta.net...
> Hi Ace,
>
> The user has a mailbox of around 4000 items and can search their own mailbox
> OK.
>
> The MailArchive is an additional ActiveDirectory user/mailbox which the user
> in question has full access to grated within the ESM.
>
> MailArchive mailbox contains over 60,000 items in the single Inbox folder, I
> know it's a lot but it worked absolutely fine before on SBS 2003 with
> Exchange 2003, it's only become a problem since the upgrade to SBS 2008.
>
> I've installed WDS 4.0 and set the local GPO to allow indexing of online
> delegate mailboxes, makes no difference at all.
>
> I've now found quite a few posts which appear to suggest that I should
> consider disabling Exchange Search Indexer on the server itself and this
> will return performance back to Exchange 2003 levels which from an Outlook
> 2003 client on a PC should be much better, but apparently this would cause
> searches from OWA and mobile activesync devices and Windows Live to suffer
> as they make user of the new Exchange Search Indexer service.
>
> Uhh...like which do you think I would prefer working better ?....
>
> http://technet.microsoft.com/en-us/library/aa996416.aspx#Mbxserver
>
> Anyway, I've just disabled the Exchange Search Indexer as per the Technet
> article and am rebooting the server to see how it goes.
>
> To be honest I guess I could have gone with just disabling it on this
> particular MailArchive mailbox I guess but lets see how this pans out first.
>
> I know I really need to get the number of items in it sorted out, but the
> customer really wants to know why their new more powerful server seems to
> offer a much slower experience than their old one !
>
> BTW I don't think it's user related any more, it searches slowly using the
> Administrator account on the XP Pro PC as well from time to time.
>
> Jim.
>

Jim,

Don't disable it on the server. Don't make too many changes, leave it default.

As I've previously mentioned, it is due to being a delegate of the mailbox. THe settings are Outlook specific because of the delegated mailbox. Since the mailbox doesn't belong to the user, and the user is a delegate, it is an Outlook setting, not on the server side.

You can enable this in the Group Policy settings for Windows Search. The settings are:

Enable Indexing of online delegate Mailboxes (This is for non-cached mode Outlook profiles)
- Supported on: Any version of Microsoft Windows with Windows Search 4.0 or later.

Enable Indexing uncached Exchange Folders
- Supported on: Windows XP, Windows Server 2003 with Windows Search 3.01 or later.
- If enabled, mail items on a Microsoft Exchange Server are indexed when Microsoft Outlook is not running in cached mode.

You can read more about these settings in the following article:

Group Policy for Windows Search
http://technet.microsoft.com/en-us/library/cc732491(WS.10).aspx

There is more info at the following link explaining this (which I've previously posted):
http://blogs.technet.com/mikelag/archive/2009/05/04/windows-desktop-search-and-the-implications-on-wan-performance.aspx


Ace


From: Jim on
OK Ace,

I've read both articles again....still a bit confused..

What we have are predominantly Windows XP SP3 PC's with Outlook 2003 SP3

On their previous SBS 2003 setup Outlook 2003 was configured in the default
configuration , ie the users own mailbox was in cached mode and they had a
number of
other users mailboxes in their folders lists including the MailArchive
mailbox which obviously with Outlook 2003 were uncached.

When the users wanted to search for an item in the MailArchive mailbox Inbox
they selected the inbox typed in a search criteria and then clicked the
'Find
Now' button, the little magnifying glass then started to animate indicating
search progress.

Outlook 2003 then started to return results almost immediately until the
search was complete.

Now what is happening since they have upgraded to SBS 2008 is that when they
select the MailArchive mailbox Inbox folder in their Outlook 2003 program
first of
all it often takes a very long time to even display the initial content of
the Inbox.
ie when they select the Inbox they get an hour glass for some considerable
time.

Previously they were not experiencing this behavior.

Once the initial content is displayed and they enter some search criteria
and then click on 'Find Now' button, again they get an hour glass cursor
which
can last up to ten minutes and the magnifying glass icon does not animate at
all.
Very shortly after starting the search a message comes up on the bottom left
hand corner of Outlook 2003 saying: "Microsoft Outlook is requesting data
from the server.."
It's as if the whole thing has hung.

If they click anything else in Outlook it then says Microsoft Outlook (Not
Responding) in the title bar.

Previously they were not experiencing this behavior.

It seems to make no difference if I'm in online mode or cached mode or if I
install and configure the WDS 4.0 ( though not convinced I have this setup
properly yet )

Now strangely....if I logon to the Windows 2008 Terminal Server which has
Outlook 2003 installed and configured in online mode and then search the
MailArchive Inbox then I do not get this behavior,
it all works really quickly, search completes in about 5 -10 seconds.

If I change Outlook 2003 to cached mode the magnifying glass still animates
but searches of the MailArchive Inbox are marginally slower, about 10 -20
seconds

I can't see any indexing service enabled on the Windows 2008 TS box ?

It is running IPV6 whereas all the XP PC's are not, could this be something
?

If I understand what's being said in the articles if I am using Windows XP
and Outlook 2003
with SBS 2008 with Exchange Search Indexer enabled then to start with I
should be configured in online mode and I should also install WDS 4.0 on all
XP PC's ?

And where should I be configuring the Search policies ? on the SBS 2008
server or on the local Windows XP PC ?

And what policy setting ought I be choosing if I'm using Outlook 2003 as
opposed to Outlook 2007 as most of the stuff is Outlook 2007 related as far
as I can make out ?

Something isn't right but I must agree with you I probably don't have the
right Windows XP, Outlook 2003 and WDS 4.0 environment configured properly
yet.

But I'm unsure as to exactly what to do.

Jim.



"Ace Fekay [MVP-DS, MCT]" <aceman(a)mvps.RemoveThisPart.org> wrote in message
news:eHLRIjk3KHA.5084(a)TK2MSFTNGP02.phx.gbl...
>
> "Jim" <jim(a)dontwantspam.com> wrote in message
> news:hqbspv$11g7$1(a)energise.enta.net...
>> Hi Ace,
>>
>> The user has a mailbox of around 4000 items and can search their own
>> mailbox
>> OK.
>>
>> The MailArchive is an additional ActiveDirectory user/mailbox which the
>> user
>> in question has full access to grated within the ESM.
>>
>> MailArchive mailbox contains over 60,000 items in the single Inbox
>> folder, I
>> know it's a lot but it worked absolutely fine before on SBS 2003 with
>> Exchange 2003, it's only become a problem since the upgrade to SBS 2008.
>>
>> I've installed WDS 4.0 and set the local GPO to allow indexing of online
>> delegate mailboxes, makes no difference at all.
>>
>> I've now found quite a few posts which appear to suggest that I should
>> consider disabling Exchange Search Indexer on the server itself and this
>> will return performance back to Exchange 2003 levels which from an
>> Outlook
>> 2003 client on a PC should be much better, but apparently this would
>> cause
>> searches from OWA and mobile activesync devices and Windows Live to
>> suffer
>> as they make user of the new Exchange Search Indexer service.
>>
>> Uhh...like which do you think I would prefer working better ?....
>>
>> http://technet.microsoft.com/en-us/library/aa996416.aspx#Mbxserver
>>
>> Anyway, I've just disabled the Exchange Search Indexer as per the Technet
>> article and am rebooting the server to see how it goes.
>>
>> To be honest I guess I could have gone with just disabling it on this
>> particular MailArchive mailbox I guess but lets see how this pans out
>> first.
>>
>> I know I really need to get the number of items in it sorted out, but the
>> customer really wants to know why their new more powerful server seems to
>> offer a much slower experience than their old one !
>>
>> BTW I don't think it's user related any more, it searches slowly using
>> the
>> Administrator account on the XP Pro PC as well from time to time.
>>
>> Jim.
>>
>
> Jim,
>
> Don't disable it on the server. Don't make too many changes, leave it
> default.
>
> As I've previously mentioned, it is due to being a delegate of the
> mailbox. THe settings are Outlook specific because of the delegated
> mailbox. Since the mailbox doesn't belong to the user, and the user is a
> delegate, it is an Outlook setting, not on the server side.
>
> You can enable this in the Group Policy settings for Windows Search. The
> settings are:
>
> Enable Indexing of online delegate Mailboxes (This is for non-cached mode
> Outlook profiles)
> - Supported on: Any version of Microsoft Windows with Windows Search 4.0
> or later.
>
> Enable Indexing uncached Exchange Folders
> - Supported on: Windows XP, Windows Server 2003 with Windows Search 3.01
> or later.
> - If enabled, mail items on a Microsoft Exchange Server are indexed when
> Microsoft Outlook is not running in cached mode.
>
> You can read more about these settings in the following article:
>
> Group Policy for Windows Search
> http://technet.microsoft.com/en-us/library/cc732491(WS.10).aspx
>
> There is more info at the following link explaining this (which I've
> previously posted):
> http://blogs.technet.com/mikelag/archive/2009/05/04/windows-desktop-search-and-the-implications-on-wan-performance.aspx
>
>
> Ace
>
>
From: Jim on
As a quick test and to rule out any network performance issues, I logged
onto my test Windows XP PC as the MailArchive user and accessed the mail box
in online mode and cached mode.

This *does* seem to work fine on the Windows XP PC.

So the only thing that seems not to be working is when you try and access
the large MailArchive mailbox as an additional mailbox in an Outlook 2003
profile from a Windows XP PC.

If you're on the Windows 2008 TS then it seem to work OK, need to check with
a Windows 7 PC at some stage...

So it seems that it is something to do with the indexing or accessing a
large additional mailbox from a Windows XP PC in Outlook 2003.

Also need to try a mailbox with a lesser number of items as this may be the
main culprit. Funny how it works OK from the Windows 2008 TS though, I'm
sure I'll get bashed over the head with that.. :-(

Jim.




"Jim" <jim(a)dontwantspam.com> wrote in message
news:hqd16p$2q9i$1(a)energise.enta.net...
> OK Ace,
>
> I've read both articles again....still a bit confused..
>
> What we have are predominantly Windows XP SP3 PC's with Outlook 2003 SP3
>
> On their previous SBS 2003 setup Outlook 2003 was configured in the
> default
> configuration , ie the users own mailbox was in cached mode and they had a
> number of
> other users mailboxes in their folders lists including the MailArchive
> mailbox which obviously with Outlook 2003 were uncached.
>
> When the users wanted to search for an item in the MailArchive mailbox
> Inbox
> they selected the inbox typed in a search criteria and then clicked the
> 'Find
> Now' button, the little magnifying glass then started to animate
> indicating search progress.
>
> Outlook 2003 then started to return results almost immediately until the
> search was complete.
>
> Now what is happening since they have upgraded to SBS 2008 is that when
> they
> select the MailArchive mailbox Inbox folder in their Outlook 2003 program
> first of
> all it often takes a very long time to even display the initial content of
> the Inbox.
> ie when they select the Inbox they get an hour glass for some considerable
> time.
>
> Previously they were not experiencing this behavior.
>
> Once the initial content is displayed and they enter some search criteria
> and then click on 'Find Now' button, again they get an hour glass cursor
> which
> can last up to ten minutes and the magnifying glass icon does not animate
> at all.
> Very shortly after starting the search a message comes up on the bottom
> left
> hand corner of Outlook 2003 saying: "Microsoft Outlook is requesting data
> from the server.."
> It's as if the whole thing has hung.
>
> If they click anything else in Outlook it then says Microsoft Outlook (Not
> Responding) in the title bar.
>
> Previously they were not experiencing this behavior.
>
> It seems to make no difference if I'm in online mode or cached mode or if
> I
> install and configure the WDS 4.0 ( though not convinced I have this setup
> properly yet )
>
> Now strangely....if I logon to the Windows 2008 Terminal Server which has
> Outlook 2003 installed and configured in online mode and then search the
> MailArchive Inbox then I do not get this behavior,
> it all works really quickly, search completes in about 5 -10 seconds.
>
> If I change Outlook 2003 to cached mode the magnifying glass still
> animates
> but searches of the MailArchive Inbox are marginally slower, about 10 -20
> seconds
>
> I can't see any indexing service enabled on the Windows 2008 TS box ?
>
> It is running IPV6 whereas all the XP PC's are not, could this be
> something ?
>
> If I understand what's being said in the articles if I am using Windows XP
> and Outlook 2003
> with SBS 2008 with Exchange Search Indexer enabled then to start with I
> should be configured in online mode and I should also install WDS 4.0 on
> all XP PC's ?
>
> And where should I be configuring the Search policies ? on the SBS 2008
> server or on the local Windows XP PC ?
>
> And what policy setting ought I be choosing if I'm using Outlook 2003 as
> opposed to Outlook 2007 as most of the stuff is Outlook 2007 related as
> far as I can make out ?
>
> Something isn't right but I must agree with you I probably don't have the
> right Windows XP, Outlook 2003 and WDS 4.0 environment configured properly
> yet.
>
> But I'm unsure as to exactly what to do.
>
> Jim.
>
>
>
> "Ace Fekay [MVP-DS, MCT]" <aceman(a)mvps.RemoveThisPart.org> wrote in
> message news:eHLRIjk3KHA.5084(a)TK2MSFTNGP02.phx.gbl...
>>
>> "Jim" <jim(a)dontwantspam.com> wrote in message
>> news:hqbspv$11g7$1(a)energise.enta.net...
>>> Hi Ace,
>>>
>>> The user has a mailbox of around 4000 items and can search their own
>>> mailbox
>>> OK.
>>>
>>> The MailArchive is an additional ActiveDirectory user/mailbox which the
>>> user
>>> in question has full access to grated within the ESM.
>>>
>>> MailArchive mailbox contains over 60,000 items in the single Inbox
>>> folder, I
>>> know it's a lot but it worked absolutely fine before on SBS 2003 with
>>> Exchange 2003, it's only become a problem since the upgrade to SBS 2008.
>>>
>>> I've installed WDS 4.0 and set the local GPO to allow indexing of online
>>> delegate mailboxes, makes no difference at all.
>>>
>>> I've now found quite a few posts which appear to suggest that I should
>>> consider disabling Exchange Search Indexer on the server itself and this
>>> will return performance back to Exchange 2003 levels which from an
>>> Outlook
>>> 2003 client on a PC should be much better, but apparently this would
>>> cause
>>> searches from OWA and mobile activesync devices and Windows Live to
>>> suffer
>>> as they make user of the new Exchange Search Indexer service.
>>>
>>> Uhh...like which do you think I would prefer working better ?....
>>>
>>> http://technet.microsoft.com/en-us/library/aa996416.aspx#Mbxserver
>>>
>>> Anyway, I've just disabled the Exchange Search Indexer as per the
>>> Technet
>>> article and am rebooting the server to see how it goes.
>>>
>>> To be honest I guess I could have gone with just disabling it on this
>>> particular MailArchive mailbox I guess but lets see how this pans out
>>> first.
>>>
>>> I know I really need to get the number of items in it sorted out, but
>>> the
>>> customer really wants to know why their new more powerful server seems
>>> to
>>> offer a much slower experience than their old one !
>>>
>>> BTW I don't think it's user related any more, it searches slowly using
>>> the
>>> Administrator account on the XP Pro PC as well from time to time.
>>>
>>> Jim.
>>>
>>
>> Jim,
>>
>> Don't disable it on the server. Don't make too many changes, leave it
>> default.
>>
>> As I've previously mentioned, it is due to being a delegate of the
>> mailbox. THe settings are Outlook specific because of the delegated
>> mailbox. Since the mailbox doesn't belong to the user, and the user is a
>> delegate, it is an Outlook setting, not on the server side.
>>
>> You can enable this in the Group Policy settings for Windows Search. The
>> settings are:
>>
>> Enable Indexing of online delegate Mailboxes (This is for non-cached mode
>> Outlook profiles)
>> - Supported on: Any version of Microsoft Windows with Windows Search 4.0
>> or later.
>>
>> Enable Indexing uncached Exchange Folders
>> - Supported on: Windows XP, Windows Server 2003 with Windows Search 3.01
>> or later.
>> - If enabled, mail items on a Microsoft Exchange Server are indexed when
>> Microsoft Outlook is not running in cached mode.
>>
>> You can read more about these settings in the following article:
>>
>> Group Policy for Windows Search
>> http://technet.microsoft.com/en-us/library/cc732491(WS.10).aspx
>>
>> There is more info at the following link explaining this (which I've
>> previously posted):
>> http://blogs.technet.com/mikelag/archive/2009/05/04/windows-desktop-search-and-the-implications-on-wan-performance.aspx
>>
>>
>> Ace
>>
>>
From: Jim on
If I setup another mailbox with just over 5000 items in it as per
Microsoft's recommendations regards maintaining a maximum number of items of
between 3500 - 5000 items in a single folder:

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

Then it does seem to work OK from a Windows XP PC with Outlook 2003.

So looks like it's down to the number of items in a single folder..

But it worked OK on Exchange 2003 and it still works OK from Outlook 2003 on
the Windows 2008 TS.

Seems that Windows XP and Outlook 2003 are not happy bedfellows for Exchange
2007 where large mailboxes are concerned ?

Hmm..



"Jim" <jim(a)dontwantspam.com> wrote in message
news:hqebtl$1puv$1(a)energise.enta.net...
> As a quick test and to rule out any network performance issues, I logged
> onto my test Windows XP PC as the MailArchive user and accessed the mail
> box in online mode and cached mode.
>
> This *does* seem to work fine on the Windows XP PC.
>
> So the only thing that seems not to be working is when you try and access
> the large MailArchive mailbox as an additional mailbox in an Outlook 2003
> profile from a Windows XP PC.
>
> If you're on the Windows 2008 TS then it seem to work OK, need to check
> with a Windows 7 PC at some stage...
>
> So it seems that it is something to do with the indexing or accessing a
> large additional mailbox from a Windows XP PC in Outlook 2003.
>
> Also need to try a mailbox with a lesser number of items as this may be
> the main culprit. Funny how it works OK from the Windows 2008 TS though,
> I'm sure I'll get bashed over the head with that.. :-(
>
> Jim.
>
>
>
>
> "Jim" <jim(a)dontwantspam.com> wrote in message
> news:hqd16p$2q9i$1(a)energise.enta.net...
>> OK Ace,
>>
>> I've read both articles again....still a bit confused..
>>
>> What we have are predominantly Windows XP SP3 PC's with Outlook 2003 SP3
>>
>> On their previous SBS 2003 setup Outlook 2003 was configured in the
>> default
>> configuration , ie the users own mailbox was in cached mode and they had
>> a number of
>> other users mailboxes in their folders lists including the MailArchive
>> mailbox which obviously with Outlook 2003 were uncached.
>>
>> When the users wanted to search for an item in the MailArchive mailbox
>> Inbox
>> they selected the inbox typed in a search criteria and then clicked the
>> 'Find
>> Now' button, the little magnifying glass then started to animate
>> indicating search progress.
>>
>> Outlook 2003 then started to return results almost immediately until the
>> search was complete.
>>
>> Now what is happening since they have upgraded to SBS 2008 is that when
>> they
>> select the MailArchive mailbox Inbox folder in their Outlook 2003 program
>> first of
>> all it often takes a very long time to even display the initial content
>> of the Inbox.
>> ie when they select the Inbox they get an hour glass for some
>> considerable
>> time.
>>
>> Previously they were not experiencing this behavior.
>>
>> Once the initial content is displayed and they enter some search criteria
>> and then click on 'Find Now' button, again they get an hour glass cursor
>> which
>> can last up to ten minutes and the magnifying glass icon does not animate
>> at all.
>> Very shortly after starting the search a message comes up on the bottom
>> left
>> hand corner of Outlook 2003 saying: "Microsoft Outlook is requesting data
>> from the server.."
>> It's as if the whole thing has hung.
>>
>> If they click anything else in Outlook it then says Microsoft Outlook
>> (Not Responding) in the title bar.
>>
>> Previously they were not experiencing this behavior.
>>
>> It seems to make no difference if I'm in online mode or cached mode or if
>> I
>> install and configure the WDS 4.0 ( though not convinced I have this
>> setup properly yet )
>>
>> Now strangely....if I logon to the Windows 2008 Terminal Server which has
>> Outlook 2003 installed and configured in online mode and then search the
>> MailArchive Inbox then I do not get this behavior,
>> it all works really quickly, search completes in about 5 -10 seconds.
>>
>> If I change Outlook 2003 to cached mode the magnifying glass still
>> animates
>> but searches of the MailArchive Inbox are marginally slower, about 10 -20
>> seconds
>>
>> I can't see any indexing service enabled on the Windows 2008 TS box ?
>>
>> It is running IPV6 whereas all the XP PC's are not, could this be
>> something ?
>>
>> If I understand what's being said in the articles if I am using Windows
>> XP and Outlook 2003
>> with SBS 2008 with Exchange Search Indexer enabled then to start with I
>> should be configured in online mode and I should also install WDS 4.0 on
>> all XP PC's ?
>>
>> And where should I be configuring the Search policies ? on the SBS 2008
>> server or on the local Windows XP PC ?
>>
>> And what policy setting ought I be choosing if I'm using Outlook 2003 as
>> opposed to Outlook 2007 as most of the stuff is Outlook 2007 related as
>> far as I can make out ?
>>
>> Something isn't right but I must agree with you I probably don't have the
>> right Windows XP, Outlook 2003 and WDS 4.0 environment configured
>> properly yet.
>>
>> But I'm unsure as to exactly what to do.
>>
>> Jim.
>>
>>
>>
>> "Ace Fekay [MVP-DS, MCT]" <aceman(a)mvps.RemoveThisPart.org> wrote in
>> message news:eHLRIjk3KHA.5084(a)TK2MSFTNGP02.phx.gbl...
>>>
>>> "Jim" <jim(a)dontwantspam.com> wrote in message
>>> news:hqbspv$11g7$1(a)energise.enta.net...
>>>> Hi Ace,
>>>>
>>>> The user has a mailbox of around 4000 items and can search their own
>>>> mailbox
>>>> OK.
>>>>
>>>> The MailArchive is an additional ActiveDirectory user/mailbox which the
>>>> user
>>>> in question has full access to grated within the ESM.
>>>>
>>>> MailArchive mailbox contains over 60,000 items in the single Inbox
>>>> folder, I
>>>> know it's a lot but it worked absolutely fine before on SBS 2003 with
>>>> Exchange 2003, it's only become a problem since the upgrade to SBS
>>>> 2008.
>>>>
>>>> I've installed WDS 4.0 and set the local GPO to allow indexing of
>>>> online
>>>> delegate mailboxes, makes no difference at all.
>>>>
>>>> I've now found quite a few posts which appear to suggest that I should
>>>> consider disabling Exchange Search Indexer on the server itself and
>>>> this
>>>> will return performance back to Exchange 2003 levels which from an
>>>> Outlook
>>>> 2003 client on a PC should be much better, but apparently this would
>>>> cause
>>>> searches from OWA and mobile activesync devices and Windows Live to
>>>> suffer
>>>> as they make user of the new Exchange Search Indexer service.
>>>>
>>>> Uhh...like which do you think I would prefer working better ?....
>>>>
>>>> http://technet.microsoft.com/en-us/library/aa996416.aspx#Mbxserver
>>>>
>>>> Anyway, I've just disabled the Exchange Search Indexer as per the
>>>> Technet
>>>> article and am rebooting the server to see how it goes.
>>>>
>>>> To be honest I guess I could have gone with just disabling it on this
>>>> particular MailArchive mailbox I guess but lets see how this pans out
>>>> first.
>>>>
>>>> I know I really need to get the number of items in it sorted out, but
>>>> the
>>>> customer really wants to know why their new more powerful server seems
>>>> to
>>>> offer a much slower experience than their old one !
>>>>
>>>> BTW I don't think it's user related any more, it searches slowly using
>>>> the
>>>> Administrator account on the XP Pro PC as well from time to time.
>>>>
>>>> Jim.
>>>>
>>>
>>> Jim,
>>>
>>> Don't disable it on the server. Don't make too many changes, leave it
>>> default.
>>>
>>> As I've previously mentioned, it is due to being a delegate of the
>>> mailbox. THe settings are Outlook specific because of the delegated
>>> mailbox. Since the mailbox doesn't belong to the user, and the user is a
>>> delegate, it is an Outlook setting, not on the server side.
>>>
>>> You can enable this in the Group Policy settings for Windows Search. The
>>> settings are:
>>>
>>> Enable Indexing of online delegate Mailboxes (This is for non-cached
>>> mode Outlook profiles)
>>> - Supported on: Any version of Microsoft Windows with Windows Search 4.0
>>> or later.
>>>
>>> Enable Indexing uncached Exchange Folders
>>> - Supported on: Windows XP, Windows Server 2003 with Windows Search 3.01
>>> or later.
>>> - If enabled, mail items on a Microsoft Exchange Server are indexed when
>>> Microsoft Outlook is not running in cached mode.
>>>
>>> You can read more about these settings in the following article:
>>>
>>> Group Policy for Windows Search
>>> http://technet.microsoft.com/en-us/library/cc732491(WS.10).aspx
>>>
>>> There is more info at the following link explaining this (which I've
>>> previously posted):
>>> http://blogs.technet.com/mikelag/archive/2009/05/04/windows-desktop-search-and-the-implications-on-wan-performance.aspx
>>>
>>>
>>> Ace
>>>
>>>
From: Ace Fekay [MVP - Directory Services] on
I see you've been busy. Unfortunate the articles didn't help you.

I understand your frustration that it "all worked before SBS 2008." As
the articles indicated, SBS 2008, which uses Exchange 2007, works
differently. I haven't used Terminal Services to test this, but I
assume since you are possibly using Termional Services on the 2008 box
itself, may be a factor since the policy settings may already be
default, which are the ones mentioned in that link I provided that
need to be set for the workstations.

Policies in this respect, are Group Policies, or known as Group Policy
Objects (GPOs). I apologize for the assumption you were aware of what
they are. They can be a little tricky to set if you are not familiar
with it or the first time seeing them. There is a Group Policy
Management Console (GPMC) that the settings can be made. However, as
implied, I do not recommend making these changes without some
familiarity. Do you have a qualified IT admin you can contract to take
care of this for you?

Curioua, how large is that mailbox? And I don't mean number of
messages, rather how many Gigabytes is it? You can right-click on the
Mailbox, choose properties, and look at the folder properties.

Ace



On Sun, 18 Apr 2010 09:16:37 +0100, "Jim" <jim(a)dontwantspam.com>
wrote:

>If I setup another mailbox with just over 5000 items in it as per
>Microsoft's recommendations regards maintaining a maximum number of items of
>between 3500 - 5000 items in a single folder:
>
>http://support.microsoft.com/kb/905803
>
>Then it does seem to work OK from a Windows XP PC with Outlook 2003.
>
>So looks like it's down to the number of items in a single folder..
>
>But it worked OK on Exchange 2003 and it still works OK from Outlook 2003 on
>the Windows 2008 TS.
>
>Seems that Windows XP and Outlook 2003 are not happy bedfellows for Exchange
>2007 where large mailboxes are concerned ?
>
>Hmm..
>
>
>
>"Jim" <jim(a)dontwantspam.com> wrote in message
>news:hqebtl$1puv$1(a)energise.enta.net...
>> As a quick test and to rule out any network performance issues, I logged
>> onto my test Windows XP PC as the MailArchive user and accessed the mail
>> box in online mode and cached mode.
>>
>> This *does* seem to work fine on the Windows XP PC.
>>
>> So the only thing that seems not to be working is when you try and access
>> the large MailArchive mailbox as an additional mailbox in an Outlook 2003
>> profile from a Windows XP PC.
>>
>> If you're on the Windows 2008 TS then it seem to work OK, need to check
>> with a Windows 7 PC at some stage...
>>
>> So it seems that it is something to do with the indexing or accessing a
>> large additional mailbox from a Windows XP PC in Outlook 2003.
>>
>> Also need to try a mailbox with a lesser number of items as this may be
>> the main culprit. Funny how it works OK from the Windows 2008 TS though,
>> I'm sure I'll get bashed over the head with that.. :-(
>>
>> Jim.
>>
>>
>>
>>
>> "Jim" <jim(a)dontwantspam.com> wrote in message
>> news:hqd16p$2q9i$1(a)energise.enta.net...
>>> OK Ace,
>>>
>>> I've read both articles again....still a bit confused..
>>>
>>> What we have are predominantly Windows XP SP3 PC's with Outlook 2003 SP3
>>>
>>> On their previous SBS 2003 setup Outlook 2003 was configured in the
>>> default
>>> configuration , ie the users own mailbox was in cached mode and they had
>>> a number of
>>> other users mailboxes in their folders lists including the MailArchive
>>> mailbox which obviously with Outlook 2003 were uncached.
>>>
>>> When the users wanted to search for an item in the MailArchive mailbox
>>> Inbox
>>> they selected the inbox typed in a search criteria and then clicked the
>>> 'Find
>>> Now' button, the little magnifying glass then started to animate
>>> indicating search progress.
>>>
>>> Outlook 2003 then started to return results almost immediately until the
>>> search was complete.
>>>
>>> Now what is happening since they have upgraded to SBS 2008 is that when
>>> they
>>> select the MailArchive mailbox Inbox folder in their Outlook 2003 program
>>> first of
>>> all it often takes a very long time to even display the initial content
>>> of the Inbox.
>>> ie when they select the Inbox they get an hour glass for some
>>> considerable
>>> time.
>>>
>>> Previously they were not experiencing this behavior.
>>>
>>> Once the initial content is displayed and they enter some search criteria
>>> and then click on 'Find Now' button, again they get an hour glass cursor
>>> which
>>> can last up to ten minutes and the magnifying glass icon does not animate
>>> at all.
>>> Very shortly after starting the search a message comes up on the bottom
>>> left
>>> hand corner of Outlook 2003 saying: "Microsoft Outlook is requesting data
>>> from the server.."
>>> It's as if the whole thing has hung.
>>>
>>> If they click anything else in Outlook it then says Microsoft Outlook
>>> (Not Responding) in the title bar.
>>>
>>> Previously they were not experiencing this behavior.
>>>
>>> It seems to make no difference if I'm in online mode or cached mode or if
>>> I
>>> install and configure the WDS 4.0 ( though not convinced I have this
>>> setup properly yet )
>>>
>>> Now strangely....if I logon to the Windows 2008 Terminal Server which has
>>> Outlook 2003 installed and configured in online mode and then search the
>>> MailArchive Inbox then I do not get this behavior,
>>> it all works really quickly, search completes in about 5 -10 seconds.
>>>
>>> If I change Outlook 2003 to cached mode the magnifying glass still
>>> animates
>>> but searches of the MailArchive Inbox are marginally slower, about 10 -20
>>> seconds
>>>
>>> I can't see any indexing service enabled on the Windows 2008 TS box ?
>>>
>>> It is running IPV6 whereas all the XP PC's are not, could this be
>>> something ?
>>>
>>> If I understand what's being said in the articles if I am using Windows
>>> XP and Outlook 2003
>>> with SBS 2008 with Exchange Search Indexer enabled then to start with I
>>> should be configured in online mode and I should also install WDS 4.0 on
>>> all XP PC's ?
>>>
>>> And where should I be configuring the Search policies ? on the SBS 2008
>>> server or on the local Windows XP PC ?
>>>
>>> And what policy setting ought I be choosing if I'm using Outlook 2003 as
>>> opposed to Outlook 2007 as most of the stuff is Outlook 2007 related as
>>> far as I can make out ?
>>>
>>> Something isn't right but I must agree with you I probably don't have the
>>> right Windows XP, Outlook 2003 and WDS 4.0 environment configured
>>> properly yet.
>>>
>>> But I'm unsure as to exactly what to do.
>>>
>>> Jim.
>>>
>>>
>>>
>>> "Ace Fekay [MVP-DS, MCT]" <aceman(a)mvps.RemoveThisPart.org> wrote in
>>> message news:eHLRIjk3KHA.5084(a)TK2MSFTNGP02.phx.gbl...
>>>>
>>>> "Jim" <jim(a)dontwantspam.com> wrote in message
>>>> news:hqbspv$11g7$1(a)energise.enta.net...
>>>>> Hi Ace,
>>>>>
>>>>> The user has a mailbox of around 4000 items and can search their own
>>>>> mailbox
>>>>> OK.
>>>>>
>>>>> The MailArchive is an additional ActiveDirectory user/mailbox which the
>>>>> user
>>>>> in question has full access to grated within the ESM.
>>>>>
>>>>> MailArchive mailbox contains over 60,000 items in the single Inbox
>>>>> folder, I
>>>>> know it's a lot but it worked absolutely fine before on SBS 2003 with
>>>>> Exchange 2003, it's only become a problem since the upgrade to SBS
>>>>> 2008.
>>>>>
>>>>> I've installed WDS 4.0 and set the local GPO to allow indexing of
>>>>> online
>>>>> delegate mailboxes, makes no difference at all.
>>>>>
>>>>> I've now found quite a few posts which appear to suggest that I should
>>>>> consider disabling Exchange Search Indexer on the server itself and
>>>>> this
>>>>> will return performance back to Exchange 2003 levels which from an
>>>>> Outlook
>>>>> 2003 client on a PC should be much better, but apparently this would
>>>>> cause
>>>>> searches from OWA and mobile activesync devices and Windows Live to
>>>>> suffer
>>>>> as they make user of the new Exchange Search Indexer service.
>>>>>
>>>>> Uhh...like which do you think I would prefer working better ?....
>>>>>
>>>>> http://technet.microsoft.com/en-us/library/aa996416.aspx#Mbxserver
>>>>>
>>>>> Anyway, I've just disabled the Exchange Search Indexer as per the
>>>>> Technet
>>>>> article and am rebooting the server to see how it goes.
>>>>>
>>>>> To be honest I guess I could have gone with just disabling it on this
>>>>> particular MailArchive mailbox I guess but lets see how this pans out
>>>>> first.
>>>>>
>>>>> I know I really need to get the number of items in it sorted out, but
>>>>> the
>>>>> customer really wants to know why their new more powerful server seems
>>>>> to
>>>>> offer a much slower experience than their old one !
>>>>>
>>>>> BTW I don't think it's user related any more, it searches slowly using
>>>>> the
>>>>> Administrator account on the XP Pro PC as well from time to time.
>>>>>
>>>>> Jim.
>>>>>
>>>>
>>>> Jim,
>>>>
>>>> Don't disable it on the server. Don't make too many changes, leave it
>>>> default.
>>>>
>>>> As I've previously mentioned, it is due to being a delegate of the
>>>> mailbox. THe settings are Outlook specific because of the delegated
>>>> mailbox. Since the mailbox doesn't belong to the user, and the user is a
>>>> delegate, it is an Outlook setting, not on the server side.
>>>>
>>>> You can enable this in the Group Policy settings for Windows Search. The
>>>> settings are:
>>>>
>>>> Enable Indexing of online delegate Mailboxes (This is for non-cached
>>>> mode Outlook profiles)
>>>> - Supported on: Any version of Microsoft Windows with Windows Search 4.0
>>>> or later.
>>>>
>>>> Enable Indexing uncached Exchange Folders
>>>> - Supported on: Windows XP, Windows Server 2003 with Windows Search 3.01
>>>> or later.
>>>> - If enabled, mail items on a Microsoft Exchange Server are indexed when
>>>> Microsoft Outlook is not running in cached mode.
>>>>
>>>> You can read more about these settings in the following article:
>>>>
>>>> Group Policy for Windows Search
>>>> http://technet.microsoft.com/en-us/library/cc732491(WS.10).aspx
>>>>
>>>> There is more info at the following link explaining this (which I've
>>>> previously posted):
>>>> http://blogs.technet.com/mikelag/archive/2009/05/04/windows-desktop-search-and-the-implications-on-wan-performance.aspx
>>>>
>>>>
>>>> Ace
>>>>
>>>>