Prev: SQL 2005 KB970892 GDR 4053 & RWW, OWA, Performance report
Next: 2008 server unable to ping sbs 2003 box
From: Ace Fekay [MVP-DS, MCT] on 15 Apr 2010 16:48 "Jim" <jim(a)dontwantspam.com> wrote in message news:hq7ed3$ape$1(a)energise.enta.net... > Hi Ace, > > Thanks for the info, have installed it from Windows Update. > > It has this additional mailbox selected and have left it indexing overnight. > > Contacted the user this morning, he says it hasn't made any difference. > > Another thing done at the same time on the XP PC's was the addition of add > in Gigabit network cards. > > Guess it could be something to do with this, going to visit and investigate. > > Have already tried disabling network offload functions, made no difference. > > Also loading up a new clean PC with onboard gigabit network card with > Windows XP and office 2003 to do some tests as their PC's have quite old XP > installs. > > I'd rather be trying to prove or disprove issues with Outlook 2003 / > indexing with a cleaner OS base. > > Let you know how it goes > Ok, but strange the indexing didn't work. Ace
From: Jim on 16 Apr 2010 16:16 Gets more and more interesting.. :-( I've now got a clean freshly built fully patched PC with onboard GB NIC, 2GB RAM, P4 dual core, Windows XP Pro SP3 and Office 2003 SP3. I've setup two MAPI profiles, one cached, one not, in Outlook for each of two users. The first user, which is the SBS 2008 administrator works fine searching the large MailArchive mailbox on the XP Pro PC, the same as it does from the Windows 2008 TS. Doesn't matter whether it's cached mode or not it still works OK. If I logon as one of the other normal users and try and access the large secondary MailArchive mailbox then it's incredibly slow, ten minutes or so in either cached mode or no-cached mode on the same machine. "Microsoft Outlook is requesting data from the server.." I've waited for the users offline mailbox to finish caching when in cached mode and then tried again, still very very slow.. I log off and logon as the SBS 2008 administrator user ..now it's fast again..cached or non-cached mode, takes about 30-60 seconds to search through about 65000 items in the MailArchive mailbox Inbox. Quicker than this on subsequent searches. It seems to be user related, how can this be ? Previously on Exchange 2003 all the users could access this large MailArchive mailbox without any problems on what was actually a far lesser spec server than what they have now, that's what's so baffling. I've not yet installed Windows Desktop Search 4.0 onto this new XP Pro PC, I wanted to see what it was like without it first.. So I'll try installing WDS 4.0 next and see if this makes a difference. Jim. "Ace Fekay [MVP-DS, MCT]" <aceman(a)mvps.RemoveThisPart.org> wrote in message news:#jpyzzN3KHA.5588(a)TK2MSFTNGP06.phx.gbl... > "Jim" <jim(a)dontwantspam.com> wrote in message > news:hq7ed3$ape$1(a)energise.enta.net... >> Hi Ace, >> >> Thanks for the info, have installed it from Windows Update. >> >> It has this additional mailbox selected and have left it indexing >> overnight. >> >> Contacted the user this morning, he says it hasn't made any difference. >> >> Another thing done at the same time on the XP PC's was the addition of >> add >> in Gigabit network cards. >> >> Guess it could be something to do with this, going to visit and >> investigate. >> >> Have already tried disabling network offload functions, made no >> difference. >> >> Also loading up a new clean PC with onboard gigabit network card with >> Windows XP and office 2003 to do some tests as their PC's have quite old >> XP >> installs. >> >> I'd rather be trying to prove or disprove issues with Outlook 2003 / >> indexing with a cleaner OS base. >> >> Let you know how it goes >> > > Ok, but strange the indexing didn't work. > > Ace > >
From: Ace Fekay [MVP-DS, MCT] on 16 Apr 2010 23:53 "Jim" <jim(a)dontwantspam.com> wrote in message news:hqagjn$20ro$1(a)energise.enta.net... > Gets more and more interesting.. :-( > > I've now got a clean freshly built fully patched PC with onboard GB NIC, 2GB > RAM, P4 dual core, Windows XP Pro SP3 and Office 2003 SP3. > > I've setup two MAPI profiles, one cached, one not, in Outlook for each of > two users. > > The first user, which is the SBS 2008 administrator works fine searching the > large MailArchive mailbox on the XP Pro PC, the same as it does from the > Windows 2008 TS. > Doesn't matter whether it's cached mode or not it still works OK. > > If I logon as one of the other normal users and try and access the large > secondary MailArchive mailbox then it's incredibly slow, ten minutes or so > in either cached mode or no-cached mode on the same machine. > > "Microsoft Outlook is requesting data from the server.." > > I've waited for the users offline mailbox to finish caching when in cached > mode and then tried again, still very very slow.. > > I log off and logon as the SBS 2008 administrator user ..now it's fast > again..cached or non-cached mode, takes about 30-60 seconds to search > through about 65000 items in the MailArchive mailbox Inbox. > Quicker than this on subsequent searches. > > It seems to be user related, how can this be ? > > Previously on Exchange 2003 all the users could access this large > MailArchive mailbox without any problems on what was actually a far lesser > spec server than what they have now, that's what's so baffling. > > I've not yet installed Windows Desktop Search 4.0 onto this new XP Pro PC, I > wanted to see what it was like without it first.. > > So I'll try installing WDS 4.0 next and see if this makes a difference. > > Jim. > Ok, I'm getting a little confused, or maybe I didn't read into this whole thing correctly. So my question is, is MailboxArchive an actual AD/Exchange account, or something else? If it is an actual AD user with an Exchange mailbox, then you must have given the users permissions to access the mailbox, correct? For example, let's say you gave a user named Joe, full control to the User called "MailArchive," how did you give Joe permissions to the MailArchive mailbox? Then to continue on, they you added that Mailbox to the user's Outlook profile (account properties, Exchange, Change, More, Advanced, add mailbox)? And is that where the search issue is occuring on this added Exchange Mailbox, but NOT on the actual user's mailbox? Ace
From: Ace Fekay [MVP-DS, MCT] on 16 Apr 2010 23:56 "Jim" <jim(a)dontwantspam.com> wrote in message news:hqagjn$20ro$1(a)energise.enta.net... > Gets more and more interesting.. :-( > > I've now got a clean freshly built fully patched PC with onboard GB NIC, 2GB > RAM, P4 dual core, Windows XP Pro SP3 and Office 2003 SP3. > > I've setup two MAPI profiles, one cached, one not, in Outlook for each of > two users. > > The first user, which is the SBS 2008 administrator works fine searching the > large MailArchive mailbox on the XP Pro PC, the same as it does from the > Windows 2008 TS. > Doesn't matter whether it's cached mode or not it still works OK. > > If I logon as one of the other normal users and try and access the large > secondary MailArchive mailbox then it's incredibly slow, ten minutes or so > in either cached mode or no-cached mode on the same machine. > > "Microsoft Outlook is requesting data from the server.." > > I've waited for the users offline mailbox to finish caching when in cached > mode and then tried again, still very very slow.. > > I log off and logon as the SBS 2008 administrator user ..now it's fast > again..cached or non-cached mode, takes about 30-60 seconds to search > through about 65000 items in the MailArchive mailbox Inbox. > Quicker than this on subsequent searches. > > It seems to be user related, how can this be ? > > Previously on Exchange 2003 all the users could access this large > MailArchive mailbox without any problems on what was actually a far lesser > spec server than what they have now, that's what's so baffling. > > I've not yet installed Windows Desktop Search 4.0 onto this new XP Pro PC, I > wanted to see what it was like without it first.. > > So I'll try installing WDS 4.0 next and see if this makes a difference. > > Jim. > > Sorry, I meant to add to my previous post... If the scenario I mentioned is true, then you must add the ability for a delegated mailbox to allow the delegate to use the Search index. Read more about the setting, "Enable Indexing of online delegate Mailboxes" in the following link. Windows Desktop Search and the implications on WAN performance http://blogs.technet.com/mikelag/archive/2009/05/04/windows-desktop-search-and-the-implications-on-wan-performance.aspx Ace
From: Jim on 17 Apr 2010 04:50
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. "Ace Fekay [MVP-DS, MCT]" <aceman(a)mvps.RemoveThisPart.org> wrote in message news:#ByOCIe3KHA.4540(a)TK2MSFTNGP04.phx.gbl... > > "Jim" <jim(a)dontwantspam.com> wrote in message > news:hqagjn$20ro$1(a)energise.enta.net... >> Gets more and more interesting.. :-( >> >> I've now got a clean freshly built fully patched PC with onboard GB NIC, >> 2GB >> RAM, P4 dual core, Windows XP Pro SP3 and Office 2003 SP3. >> >> I've setup two MAPI profiles, one cached, one not, in Outlook for each of >> two users. >> >> The first user, which is the SBS 2008 administrator works fine searching >> the >> large MailArchive mailbox on the XP Pro PC, the same as it does from the >> Windows 2008 TS. >> Doesn't matter whether it's cached mode or not it still works OK. >> >> If I logon as one of the other normal users and try and access the large >> secondary MailArchive mailbox then it's incredibly slow, ten minutes or >> so >> in either cached mode or no-cached mode on the same machine. >> >> "Microsoft Outlook is requesting data from the server.." >> >> I've waited for the users offline mailbox to finish caching when in >> cached >> mode and then tried again, still very very slow.. >> >> I log off and logon as the SBS 2008 administrator user ..now it's fast >> again..cached or non-cached mode, takes about 30-60 seconds to search >> through about 65000 items in the MailArchive mailbox Inbox. >> Quicker than this on subsequent searches. >> >> It seems to be user related, how can this be ? >> >> Previously on Exchange 2003 all the users could access this large >> MailArchive mailbox without any problems on what was actually a far >> lesser >> spec server than what they have now, that's what's so baffling. >> >> I've not yet installed Windows Desktop Search 4.0 onto this new XP Pro >> PC, I >> wanted to see what it was like without it first.. >> >> So I'll try installing WDS 4.0 next and see if this makes a difference. >> >> Jim. >> >> > > Sorry, I meant to add to my previous post... > > If the scenario I mentioned is true, then you must add the ability for a > delegated mailbox to allow the delegate to use the Search index. Read more > about the setting, "Enable Indexing of online delegate Mailboxes" in the > following link. > > Windows Desktop Search and the implications on WAN performance > http://blogs.technet.com/mikelag/archive/2009/05/04/windows-desktop-search-and-the-implications-on-wan-performance.aspx > > Ace |