T
TJ
Looking for insight ... Let me know if you see anything wrong with this
approach.
When I bring new hires in and load their Outlook data, I do the following:
1) Give myself Full Control access of the user's mailbox.
2) I will then add the user's mailbox to my profile as an additional
mailbox.
3) Import the pst file from my workstation while logged into Outlook under
my profile.
4) Revoke access to the user's mailbox
I've not experienced any problems but wanted to make sure I'm covering my
bases.
Do I stand the risk of losing or not importing any data by working in this
manner?
Is it preferable to import on the user's machine? If so, why?
My concerns are private entries, auditing information and object ownership.
I wouldn't think ownership would be an issues as the data would be going
into a new environment but please let me know your thoughts or best
practices. We are on an Exchange 2000/Outlook Xp platform.
approach.
When I bring new hires in and load their Outlook data, I do the following:
1) Give myself Full Control access of the user's mailbox.
2) I will then add the user's mailbox to my profile as an additional
mailbox.
3) Import the pst file from my workstation while logged into Outlook under
my profile.
4) Revoke access to the user's mailbox
I've not experienced any problems but wanted to make sure I'm covering my
bases.
Do I stand the risk of losing or not importing any data by working in this
manner?
Is it preferable to import on the user's machine? If so, why?
My concerns are private entries, auditing information and object ownership.
I wouldn't think ownership would be an issues as the data would be going
into a new environment but please let me know your thoughts or best
practices. We are on an Exchange 2000/Outlook Xp platform.