Search results for query: *

Windows backup is not enough - you also need to be doing Exchange aware backups. NTBackup can handle that. Use exmerge to export the mailboxes of users who are gone to PST files, then you can safely remove the account and mailboxes. Run the Exchange cleanup agent after removing old accounts...

Check this KB for a hotfix to the 9548 events: <http://support.microsoft.com/kb/555410/en-us> What is the date/time stamp on the first log? Is it before or after your last backup?

How about using distribution groups for the aliases and give the user account permission to send as the DG?

Did you follow KB 822931?

Do you have message tracking on? If so, what does the tracking log show for these messages? If not, turn it on and send a few test messages, then look at your tracking and see where the hold-up is.

Are you using "cached mode" in OL? If so, turn cached mode off and see if the problem persists. Have you tried creating a new Outlook profile? Also, try creating a profile for one of the additional mailboxes and see if it opens OK using that profile. It doesn't sound like a permissions issue...

Have you restarted Outlook?

Look at your tracking logs for more detailed information.

If you have the standard version of Exchange 5.5 your Public folder store can grow to 16GB. If you have the enterprise version, your only limitation to the PF size would be the time it needs to be backed up and disk space. If you are not using unicode PST files, your limit is 2GB (or somewhere...

Since you have Exchange, why not have them store the archive messages in a Public Folder?

You don't want to share a PST file unless you really don't care about the emails stored there. That said, there may be some 3rd party app to help with that - like Public Outlook ... Unfortunately, you cannot save sent items in the folder they were sent from vs. the logged on users sent items...

When was your last full backup?

Also look at the sending clients "nicknames" - unless they intentionally select the person from the updated address book, Outlook (by default) will use what's in its nicknames file - which may no longer work (in most cases, doesn't).

Look at the application generating the emails. We had this same issue several years ago and found the (Unix) application was the root of the problem.

If I'm not mistaken, the Export option doesn't move mail, it copies it - you would need to manually delete from the server what you have copied to the PST. Don't forget to empty your deleted items folder, and it helps to get rid of old Sent Items too. Do you really have 7Gb of mail or did you...

Why am I not surprised that someone else would also have this problem. Sorry for the late reply, but this was just reported to me today by a user, and it's happening internally. Trying to get more information about the senders interaction and setup now, but if you've resolved this since you...

Instant Messaging is enabled (Tools/Options/Other)? Disable it.

How do you know it's not updating the server? Is it stating (client only) in Rules Wiz? You might try a new OL profile for the user. You can definately forward email to an external account without having OL running with Ex5.5 - unless you route your mail to a .pst instead of leaving it on the...

Are only the Outlook 2003 clients affected? I don't have that version yet, but am guessing that, like 2002, it has Instant Messaging capability - if so, make sure it's not enabled (Tools/Options/Other in 2002).

&quot;quick&quot; depends on the size of priv.edb, but yes - you can do that. You should also copy your transaction logs and pub.edb if you use public folders. The copied files will only be of use if the server they are to be used on has the smae SP level, same org name and same site name as...