OOO issue at one of my Sites

2011-08-01 Thread phil levine
I am getting the error where it says exchange server is unavailable at 1 of my sites when trying to set an Out of Office. The users are working fine otherwise and here is the output when I do a test-outlookwebservices for the user: [PS] C:\Windows\system32Test-OutlookWebServices -Identity

RE: Android Exchange Client - WAS: SOLVED: EAS problems Exchange 2003

2011-08-01 Thread Sean Rector
Carl, Try TouchDown for Exchange. I think you'll really like that as an Exchange client on your tablet. Sean Rector, MCSE From: Carl Houseman [mailto:c.house...@gmail.com] Sent: Saturday, July 30, 2011 1:19 PM To: MS-Exchange Admin Issues Subject: SOLVED: EAS problems Exchange 2003

RE: Outlook Social Connector/GAL Photos

2011-08-01 Thread Peter Johnson
IIRC correctly it's listed as the People pane and is a component of that. It's found on the view tab. Regards [cid:image001.jpg@01CC5076.48BEF960] Peter Johnson I.T Architect United Kingdom: +44 1285 658542 South Africa: +27 11 252 1100 Swaziland: +268 2442 7000 Fax:+27 11 974 7130 Mobile:

RE: Android Exchange Client - WAS: SOLVED: EAS problems Exchange 2003

2011-08-01 Thread Carl Houseman
I'd heard of Touchdown, but this isn't my tablet, and TD isn't free, so the choice to upgrade or not will be left to the user. If it was mine, I'd be looking for something that can sync public folder contacts, calendars, and messages, the same as Outlook. Doesn't appear that Touchdown handles

RE: Android Exchange Client - WAS: SOLVED: EAS problems Exchange 2003

2011-08-01 Thread Kennedy, Jim
http://www.codetwo.com/exchange-folder-sync/?sts=962 From: Carl Houseman [mailto:c.house...@gmail.com] Sent: Monday, August 01, 2011 12:30 PM To: MS-Exchange Admin Issues Subject: RE: Android Exchange Client - WAS: SOLVED: EAS problems Exchange 2003 I'd heard of Touchdown, but this isn't my

RE: Android Exchange Client - WAS: SOLVED: EAS problems Exchange 2003

2011-08-01 Thread Kennedy, Jim
And this one: https://market.android.com/details?id=net.northrivertechnologies.publicfoldercontactsync From: Kennedy, Jim [mailto:kennedy...@elyriaschools.org] Sent: Monday, August 01, 2011 12:31 PM To: MS-Exchange Admin Issues Subject: RE: Android Exchange Client - WAS: SOLVED: EAS problems

RE: Android Exchange Client - WAS: SOLVED: EAS problems Exchange 2003

2011-08-01 Thread Peter Johnson
This is an issue with the ActiveSync protocol. Not everyone implements it the same way and MS don't seem to enforce any standards. I've seen some weird behaviour with iOS clients where they don't honor folder view settings. Regards [cid:image001.jpg@01CC507A.A3FCFD00] Peter Johnson I.T

RE: Outlook Social Connector/GAL Photos

2011-08-01 Thread Paul Hutchings
Thanks Peter, that's what I was expecting but it just point blank doesn't appear to be present. From: Peter Johnson [peter.john...@peterstow.com] Sent: 01 August 2011 5:03 PM To: MS-Exchange Admin Issues Subject: RE: Outlook Social Connector/GAL Photos IIRC

RE: Android Exchange Client - WAS: SOLVED: EAS problems Exchange 2003

2011-08-01 Thread Carl Houseman
It is issue or omission? Incomplete or faulty implementation is one thing, the protocol not allowing it is something else entirely. You seem to be talking about folder view settings, but my question would be, what about public folders in general. If there is no defined way that public folders

RE: Android Exchange Client - WAS: SOLVED: EAS problems Exchange 2003

2011-08-01 Thread Carl Houseman
Thanks, will keep those in mind when the need arises. From: Kennedy, Jim [mailto:kennedy...@elyriaschools.org] Sent: Monday, August 01, 2011 12:33 PM To: MS-Exchange Admin Issues Subject: RE: Android Exchange Client - WAS: SOLVED: EAS problems Exchange 2003 And this one:

RE: Unexpected error DOC_TOO_HUGE with Exchange 2010 SP1?

2011-08-01 Thread Leedy, Andy
I installed the office filter pack update and rebooted... but no luck. Still getting the following error: Log Name: Application Source:MSExchangeIS Mailbox Store Date: 8/1/2011 1:04:33 PM Event ID: 9875 Task Category: Content Indexing Level: Error Description:

RE: Unexpected error DOC_TOO_HUGE with Exchange 2010 SP1?

2011-08-01 Thread Michael B. Smith
Now, rebuild the indexes. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Leedy, Andy [mailto:ale...@butlerschein.com] Sent: Monday, August 01, 2011 2:51 PM To: MS-Exchange Admin Issues Subject: RE: Unexpected error DOC_TOO_HUGE with Exchange 2010

RE: Unexpected error DOC_TOO_HUGE with Exchange 2010 SP1?

2011-08-01 Thread Leedy, Andy
Like this? cd C:\Program Files\Microsoft\Exchange Server\V14\Scripts .\ResetSearchIndex.ps1 -Force Inside Sales A to F Thanks, Andy From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Monday, August 01, 2011 3:07 PM To: MS-Exchange Admin Issues Subject: RE: Unexpected error

Changing 2003 to 2010 RGC Bridgehead?

2011-08-01 Thread Paul Hutchings
I'm just about to move my last mailbox from 2003 to 2010 at which point I'll want to start decommissioning my 2003 servers - the bit I'm not looking forward to! I have two 2003 boxes.  One is the BE mailbox server, the other is a FE server. The FE server is specified as the bridgehead server

RE: Unexpected error DOC_TOO_HUGE with Exchange 2010 SP1?

2011-08-01 Thread Leedy, Andy
Or should I just... 1) Stop the MSExchangeSearch service. 2) Delete the whole CatalogData folder in the affected database folder (there is only CatalogData folder in the db folder). 3) Start the MSExchangeSearch service. I assume this what you mean by rebuilding the indexes.

RE: Unexpected error DOC_TOO_HUGE with Exchange 2010 SP1?

2011-08-01 Thread Michael B. Smith
I would do something similar, but just slightly different: cd $exscripts .\ResetSearchIndex -all -force Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Leedy, Andy [mailto:ale...@butlerschein.com] Sent: Monday, August

RE: Changing 2003 to 2010 RGC Bridgehead?

2011-08-01 Thread Michael B. Smith
Update the routing group connector? AFTER MAKING SURE that you have updated any necessary firewall translations (such as where the default incoming port 25 goes...). Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com -Original Message- From: Paul