Here is a <a href=”http://www.msexchange.org/tutorials/Migrating_Exchange_5_5_to_2003.html”>comprehensive guide</a> for migrating from exchange 5.5 to exchange 2003.
<a href=”http://technet.microsoft.com/en-us/library/aa998691(EXCHG.65).aspx”>Here is a step by step guide</a>.
Try running outlook.exe /cleanfreebusy switch next time and see if the issue clears. Close outlook, go to start, run, type this in the “open” field.
Read <a href=”http://msmvps.com/blogs/ehlo/archive/2008/02/21/1520820.aspx”>this article</a> for a solution.
Try closing outlook, go to start, run, and in the “open” field type “outlook.exe /cleanfreebusy” (without the quotes obviously.) See if that clears it up.
When a meeting request arrives in the inbox, the outlook “sniffer” is responsible for putting it on the calendar as tentative. Try closing outlook and running the outlook.exe /cleanfreebusy switch first. (Type this in the “open” field when you go to start,run) If this does not resolve it close outlook again and try outlook.exe /sniff.
Do you have more than one mailbox server? Do you have more than one public folder store? If yes to both they need to be replicating to each other. A useful tool for working with Public Folders is PFDAVAdmin. Download and install version 2.8 to your pc, not the exchange server.
There is no way to do this from the servers side. You would have to use a third party tool to acheive this and it may or may not be cost effective to do so.One third party tool which looks promising is <a href=”http://www.exchangegroupcalendar.com/”>this.</a>
Do you have your BB set up to synchronize with all folders? The empty one may not be set to sync.
<a href=”http://www.tek-tips.com/viewthread.cfm?qid=694486″>Here is a thread</a> explaining the same issue, perhaps one of the solutions there may help you.
If you have given others access to your calendar with editor rights you will not be able to tell who put an appt there, no. If this was a sent meeting obviously you can see who the organizer is.
You did not mention whether this was a new development and it has worked in the past or not. If it has never worked did you create an SMTP connector for all outbound email which sends to a smarthost (typically your ISP)? If you have not, create one and put * for the addresses. Restart [...]
You could either open your firewall to allow communication with your CAS or publish it to an ISA server instead.
I can’t tell you why this is doing this, but I can recommend some troubleshooting steps to try. It would be helpful if you had included more details. You did not say whether you are connecting to an exchange server, but if you are please tell us what version and patch level. If not, are [...]
You can have more than one CAS, we have two in our environment, but that may not be what you need to configure.
About two weeks ago we migrated our mail from an external Exchange hosting company named MailStreet to our own internal Exchange 2007 server. Most of the migration went extremely smoothly, however our poor Creative team has had to use Outlook Web Access (OWA) the entire time because Entourage 2004 wasn’t playing nicely with Exchange 2007. [...]
Hi, I have checked the Application and Event logs and i have already installed and all the patches and latest updates but still the problem continues. Is this is related to the hardware performence or any false SMTP connector issues?
Because you’re saying that this is an issue when sending to more than one person or sending more than one file, it sounds like it could possibly be a restriction on how much information that your Outlook client is configured to send. I think that they use to limit it to 2MB by default, see [...]
<b><i>I don’t think</i></b> you need to run ADPREP unless you are upgrading to a newer version of Windows Server. <b><i>I think</i></b> you should be able to add the second domain controller running DCPROMO without any preparation to the forest or domain. The only special thing to take into consideration when promoting the second DC is [...]
Not a problem. There can be different internal names and external names. This is a good practice.





