Outlook .pst folder redirection possible?
-
@iroal said:
Where I work nobody delete e-mails.
I try to explain the problem with the size in Exchange but they just don't care.Only way I found to reduce the Exchange Database was use Pst, we have a lot, and many are really big.
I put all of them in an old server, 12 years old, It works perfect, no problems since I use this system.
Yeah no, that's a horrible process. If users are storing emails into PST files that are hosted on a network share, you might as well kiss that email goodbye.
PST are not designed to work over a network share. Period, never have been and likely never will be.
If you need an infinite amount of past email saved switch everyone over to OWA or a different platform.
-
@iroal said:
Where I work nobody delete e-mails.
I try to explain the problem with the size in Exchange but they just don't care.Only way I found to reduce the Exchange Database was use Pst, we have a lot, and many are really big.
I put all of them in an old server, 12 years old, It works perfect, no problems since I use this system.
Why not just let Exchange get bigger? How much are we talking per user? Average and worst case?
-
Policy is really the issue here. Set a mailbox limit and stick with it. Force users to clean out their old garbage. Chances are there is a ton of emails that can be deleted. Exchange is not meant to hold attachments, so all those emails should be deleted and their content should be stored on a user's network share.
-
@IRJ said:
Policy is really the issue here. Set a mailbox limit and stick with it.
If management wants large mailboxes and is the one paying for them, what's the concern?
-
@scottalanmiller said:
@IRJ said:
Policy is really the issue here. Set a mailbox limit and stick with it.
If management wants large mailboxes and is the one paying for them, what's the concern?
Then everything should be hosted on Exchange like you previously said. PST(s) are a sloppy way to archive especially if you are archiving for everyone and trying to move to network shares.
-
That's what we do. We have 50GB mailboxes (thank you Office 365) and everything goes on Exchange. That way you can use OWA. If you use PSTs you start to lose functionality or options.
-
@scottalanmiller said:
That's what we do. We have 50GB mailboxes (thank you Office 365) and everything goes on Exchange. That way you can use OWA. If you use PSTs you start to lose functionality or options.
One thing I'm finding is that the OWA search function is so much faster than even using a cached exchange connection in Outlook. What keeps me in Outlook proper is being able to select messages and drive it mostly from the keyboard. I cannot do this in OWA.
-
@dafyre said:
@scottalanmiller said:
That's what we do. We have 50GB mailboxes (thank you Office 365) and everything goes on Exchange. That way you can use OWA. If you use PSTs you start to lose functionality or options.
One thing I'm finding is that the OWA search function is so much faster than even using a cached exchange connection in Outlook. What keeps me in Outlook proper is being able to select messages and drive it mostly from the keyboard. I cannot do this in OWA.
OWA is better than Outlook, but users swear they need outlook. Even though most of our users don't even use a calendar...lol
-
@dafyre said:
@scottalanmiller said:
That's what we do. We have 50GB mailboxes (thank you Office 365) and everything goes on Exchange. That way you can use OWA. If you use PSTs you start to lose functionality or options.
One thing I'm finding is that the OWA search function is so much faster than even using a cached exchange connection in Outlook. What keeps me in Outlook proper is being able to select messages and drive it mostly from the keyboard. I cannot do this in OWA.
Searching is one of those things that tend to be way better server-side than client-side.
-
@IRJ said:
@dafyre said:
@scottalanmiller said:
That's what we do. We have 50GB mailboxes (thank you Office 365) and everything goes on Exchange. That way you can use OWA. If you use PSTs you start to lose functionality or options.
One thing I'm finding is that the OWA search function is so much faster than even using a cached exchange connection in Outlook. What keeps me in Outlook proper is being able to select messages and drive it mostly from the keyboard. I cannot do this in OWA.
OWA is better than Outlook, but users swear they need outlook. Even though most of our users don't even use a calendar...lol
And OWA Calendaring works decently, too.
-
I have been so accustomed to using the keyboard for my email, thanks largely in part to GMail, lol. I can tag and mark messages and all of that in GMail with my keyboard. I'd love to be able to do that in OWA / Office365. I really could ditch outlook then.
-
Can you not do that with OWA? I've definitely not tried, just wondering.
-
@scottalanmiller said:
@iroal said:
Where I work nobody delete e-mails.
I try to explain the problem with the size in Exchange but they just don't care.Only way I found to reduce the Exchange Database was use Pst, we have a lot, and many are really big.
I put all of them in an old server, 12 years old, It works perfect, no problems since I use this system.
Why not just let Exchange get bigger? How much are we talking per user? Average and worst case?
We still use Exchange 2003 , actual database size is near to 200Gb, It's complicate recover backups with this size.
I hope in 2016 we move to Exchange Online and I can forget Pst and Exchange Backups with Backup Exec.
-
@iroal said:
@scottalanmiller said:
@iroal said:
Where I work nobody delete e-mails.
I try to explain the problem with the size in Exchange but they just don't care.Only way I found to reduce the Exchange Database was use Pst, we have a lot, and many are really big.
I put all of them in an old server, 12 years old, It works perfect, no problems since I use this system.
Why not just let Exchange get bigger? How much are we talking per user? Average and worst case?
We still use Exchange 2003 , actual database size is near to 200Gb, It's complicate recover backups with this size.
I hope in 2016 we move to Exchange Online and I can forget Pst and Exchange Backups with Backup Exec.
OMG 2003!! Exchange was so bad back then. It wasn't really usable until 2010. 2013 was a huge leap forward. 200GB is not that large for a single mailbox in 2013, but for a 2003 system that is problematic.
-
@scottalanmiller said:
@iroal said:
@scottalanmiller said:
@iroal said:
Where I work nobody delete e-mails.
I try to explain the problem with the size in Exchange but they just don't care.Only way I found to reduce the Exchange Database was use Pst, we have a lot, and many are really big.
I put all of them in an old server, 12 years old, It works perfect, no problems since I use this system.
Why not just let Exchange get bigger? How much are we talking per user? Average and worst case?
We still use Exchange 2003 , actual database size is near to 200Gb, It's complicate recover backups with this size.
I hope in 2016 we move to Exchange Online and I can forget Pst and Exchange Backups with Backup Exec.
OMG 2003!! Exchange was so bad back then. It wasn't really usable until 2010. 2013 was a huge leap forward. 200GB is not that large for a single mailbox in 2013, but for a 2003 system that is problematic.
200GB Exchange database, not mailbox.
-
Oh right, ha ha.
-
@scottalanmiller said:
@iroal said:
@scottalanmiller said:
@iroal said:
Where I work nobody delete e-mails.
I try to explain the problem with the size in Exchange but they just don't care.Only way I found to reduce the Exchange Database was use Pst, we have a lot, and many are really big.
I put all of them in an old server, 12 years old, It works perfect, no problems since I use this system.
Why not just let Exchange get bigger? How much are we talking per user? Average and worst case?
We still use Exchange 2003 , actual database size is near to 200Gb, It's complicate recover backups with this size.
I hope in 2016 we move to Exchange Online and I can forget Pst and Exchange Backups with Backup Exec.
OMG 2003!! Exchange was so bad back then. It wasn't really usable until 2010. 2013 was a huge leap forward. 200GB is not that large for a single mailbox in 2013, but for a 2003 system that is problematic.
It's not so bad for a SMB, just one little problem in the 5 years I'm working here.
Now thanks to Outlook 2013 and 2016, they are not compatible with Exchange 2003, they are thinking in move the mail to Exchange Online.
-
It was the disaster of Exchange 2003 that drove us to Zimbra back in that era
-
@scottalanmiller said:
@iroal said:
@scottalanmiller said:
@iroal said:
Where I work nobody delete e-mails.
I try to explain the problem with the size in Exchange but they just don't care.Only way I found to reduce the Exchange Database was use Pst, we have a lot, and many are really big.
I put all of them in an old server, 12 years old, It works perfect, no problems since I use this system.
Why not just let Exchange get bigger? How much are we talking per user? Average and worst case?
We still use Exchange 2003 , actual database size is near to 200Gb, It's complicate recover backups with this size.
I hope in 2016 we move to Exchange Online and I can forget Pst and Exchange Backups with Backup Exec.
OMG 2003!! Exchange was so bad back then. It wasn't really usable until 2010. 2013 was a huge leap forward. 200GB is not that large for a single mailbox in 2013, but for a 2003 system that is problematic.
Amazed you don't have all kinds of problems with a mail store that large on 2003.
MS improved disk performance and a million other things with new versions of Exchange - damn you really want to move ASAP
-
For an entire store, 200GB isn't all that big. That's four mailboxes in the Hosted Exchange world
