I've got the following issue:
I'm the administrator of an Exchange Account.
There is a PST saved in a network directory that is used to save every email that I receive in this account, manually. When there are many emails there, I save them in diferrent folders in this PST.
My problem:
I don't have enough time to do that alone, so i would like to duplicate the access to this account AND the PST to more 10 people. Then, all of us would see one inbox, one PST and edit it.
Is there any way of doing that?
No, a PST file cannot be shared between multiple machines. Why not create a dedicated mailbox on the Exchange server that can be accessed from multiple machines?
Related
We have an In-house executable which creates Outlook Meetings and Appointments in shared calendars.
One user is having a problem creating appointments in a shared calendar using this code. This code's been running fine for years now.
WHAT HAS BEEN TRIED:
I had the user access the Calendar directly through Outlook. She was able to create meetings in the Shared Calendar without a problem.
EXCEPTION THROWN:
"The operation failed because of a registry or installation problem. Restart Outlook and try again. If the problem persists, reinstall."
Re-installing Outlook would be a major inconvenience for the user.
I'm wondering.
What area in the Registry would I look at?
Would recreating the .PST file be a reasonable alternative?
Can I use Outlook Redemption to troubleshoot the user's account?
It seems your Outlook profile (or Outlook installation itself) is corrupted. You can take a look at the Windows event log what else Outlook states about the error incident. At this stage, it is not clear whether it is related to the profile corruption (to re-create a pst) or Outlook itself.
Redemption is a wrapper around Extended MAPI (a low-level API on which Outlook is built on). But it doesn't provide any self-diagnostic services, only convenient access to the low-level functions. However, you can use Redemption for getting your job done without Outlook involved.
I'd suggest opening a support case with Microsoft if you need to continue working with OOM.
It turns out that it was a data issue.
I asked the user to create Appointments for other shared calendars using our custom executable. She was able to do so without a problem.
The exception message that I posted came from the call to GetSharedDefaultFolder
The Recipient parameter was created using an email address that doesn't exist on our Exchange server. That bad email address came from our database.
Apologies for the basic question; we're having a spring clean of the office Active Directory and plan to remove a large number of legacy users. Saying good-bye to their email is not a problem, but we have an on-premise Dynamics CRM we occasionally refer to. My question is, will there be any implications for that if I delete a user who might have entered a case?
There is no direct link between CRM on-premise 2011 & Active Directory to pull all users overnight & sync. When you create a new user in CRM by giving domain name, it will verify in AD & pull the details to store in CRM. This will happen on tab out.
So when you delete/disable an AD user it won't flow down in Dynamics. But you have to disable them manually (no delete option available). Before doing that make sure to read these best practices.
Best Practices
Make sure to Re-assign any associated records/activities to another
User or Team before disabling User. If you don’t Re-assign the records
they will still be available, but they will still be assigned to the
disabled user.
It is very important to ensure that there are no Workflows owned by
the User to be disabled. All Published Workflows need to be owned by
an administrative account, not an employee’s account.
There are situations where a User’s account only needs to be disabled
for a short period of time, so records don’t necessarily need to be
Re-assigned. (Example: the User went on vacation for a month). Take
into consideration the User’s privileges for those records. If only
the User can modify that record, then no one will be able to modify
the record, if the owner is disabled.
Read this community thread as well.
Some users are having issues with their mailboxes not updating automatically, they need to click update folder every couple of minutes, send and receive doesn't work either for their mailboxes. The users are Personal Assistants to 3 different senior managers and have access to those mailboxes and another generic rarely used contact-us mailbox. We are using outlook 2010 with exchange cached mode. They also need to click update folder to get one of the managers calendar to update the contents. All 3 managers mailboxes and the other 2 calendars update without issue.
One of the senior managers has a 5GB mailbox, the others are 1GB or less. The issue only happens when we add the 5GB mailbox is added. The user receives emails immediately for 3 of the managers mailboxes(including the 5GB one) but not her own mailbox
The issue is obviously with the 5GB mailbox as when it's removed everything works fine.
-Why would the users own mailbox and one managers calendar not update as opposed to the 5gb or other mailboxes/calendars?
-Is there a way to prioritise which mailbox updates?
-Is there a way to re-synchronise outlook so everything works?
-Is there anything I can do to get the users working with all mailboxes/calendars etc?
-Do I need to get the 5GB mailbox reduced somehow, she's a finance person and is very concerned about losing emails?
Disabling Exchange Cached mode for the shared mailboxes resolved this issue.
We have a requirement to show persons location/work location in the last week and show him on the website when webpage is opened. We have a process mandate that every employee should visit this website and mark the attendance of last week. To get this information, can we pull the last synchronisation date time and location/IP Address or an individual from exchange server or Lync server?
It depends how your users are actually connecting if they are using Outlook Anywhere or OWA then you should be able to use the Logs on Exchange to grab the Client IpAddress being used which you should then be able to derive their location. I would start by looking at the Log Parser Studio which has a lot of precanned reports http://blogs.technet.com/b/exchange/archive/2012/03/07/introducing-log-parser-studio.aspx and then look at customising your own solution.
Another alternative method that would rely on them having sent a messages in the last week is you could use EWS to derive it from their sent email eg http://gsexdev.blogspot.com.au/2012/10/geolocating-users-last-send-location.html
Cheers
Glen
I'm wondering what the best practice is for "archiving" old disabled accounts in exchange. I work for a small health exchange company and the upper management wants any mailbox over 60 days old, backed up and off our network. So basically a .pst created for the mailbox, put on the network for a short time for it to be backed up to tape, then it is deleted (the mailbox and .pst).
I'm assuming most companies just disable the account and mailbox so that the mailbox goes into the "inactive" storage and leave it there.
Thanks for any input.
I don't think there is a one size fits all strategy.
Some of the clients I work with do one or some of the following.
Disable the mailbox for 30-90 days, then archive it to PST and delete the mailbox.
Set an autoforward to the appropriate individual replacing the user in question, and give the user full mailbox access.
Archive and delete the mailbox and assign the old email address to a catch all mailbox, or as a duplicate address to the new user.
Alternatively you could always disable the account and hide it from the GAL if you wanted to keep it readily available for longer than 60 days.