ptcis
asked on
PST on Network Share
Hi All!
I recently upgraded our Exchange 2007 server running on Server 2003 to Exchange 2013 running on a VM 2012 server. I have several users that have always had PST's that reside on share (previously on 2003 server, now on 2012.) The users have never had any issues until I moved everyone to the new servers. Now the users are receiving errors when they try to access there pst on those shares. They can still access the PST but every once in a while they get an error and usually have to restart Outlook several times. Attached is a picture of the error they are receiving.
I have tried using mapped drives and unc, but still receiving the error. I have also made users the "owner" with full permissions on the share but still get the errors. I have read that Microsoft does not support PST's on network shares, but we've been doing it for almost 10 years with no issues. Does anyone have any suggestions because I am at a lost.
pst-error.jpg
I recently upgraded our Exchange 2007 server running on Server 2003 to Exchange 2013 running on a VM 2012 server. I have several users that have always had PST's that reside on share (previously on 2003 server, now on 2012.) The users have never had any issues until I moved everyone to the new servers. Now the users are receiving errors when they try to access there pst on those shares. They can still access the PST but every once in a while they get an error and usually have to restart Outlook several times. Attached is a picture of the error they are receiving.
I have tried using mapped drives and unc, but still receiving the error. I have also made users the "owner" with full permissions on the share but still get the errors. I have read that Microsoft does not support PST's on network shares, but we've been doing it for almost 10 years with no issues. Does anyone have any suggestions because I am at a lost.
pst-error.jpg
Haresh Nikumbh
run below command from command line with administrator right and check if this solve this issue
Can you see what's locking the .pst on the server when the message come up for the users?
AV? Backup software?
Agree with you about Microsoft's views and what happens in the real world, haven't seen a problem - ever! Inluding users who have their accounts linked permanently to multiple .pst files when they start up Outlook!
AV? Backup software?
Agree with you about Microsoft's views and what happens in the real world, haven't seen a problem - ever! Inluding users who have their accounts linked permanently to multiple .pst files when they start up Outlook!
ASKER
I will give the command a try. Next time someone get the error.
@MASQUERAID I have disabled AV and backup's o a machine and still get the error. And it does not show any locking on the file. That's what is driving me nuts right now.
@MASQUERAID I have disabled AV and backup's o a machine and still get the error. And it does not show any locking on the file. That's what is driving me nuts right now.
PST files on a network share are not supported and what you are seeing are one of the main reasons why not.
http://support.microsoft.com/default.aspx?kbid=297019
More on the same subject:
http://blogs.technet.com/askperf/archive/2007/01/21/network-stored-pst-files-don-t-do-it.aspx
The fact that you have been doing it for ten years isn't really a valid reason to continue doing it - I call that the drink driver's excuse. If you have had no problems with a PST file on a network share then you have been lucky, and that is all. Most people do have problems and I have seen a single PST file cause an entire file server to crash.
Simon.
http://support.microsoft.com/default.aspx?kbid=297019
More on the same subject:
http://blogs.technet.com/askperf/archive/2007/01/21/network-stored-pst-files-don-t-do-it.aspx
The fact that you have been doing it for ten years isn't really a valid reason to continue doing it - I call that the drink driver's excuse. If you have had no problems with a PST file on a network share then you have been lucky, and that is all. Most people do have problems and I have seen a single PST file cause an entire file server to crash.
Simon.
agree with simon
put your pst files locally or implement personal archives (as mentioned in the kb article)
the smallest thing like this where the connection to the file is broken over the network could cause the file to become corrupt (seen this happen before)
put your pst files locally or implement personal archives (as mentioned in the kb article)
the smallest thing like this where the connection to the file is broken over the network could cause the file to become corrupt (seen this happen before)
ASKER
The reason the PST's are on a share is because they get backed up. I use shadowprotect to take snapshots of the file server, which the PST's are on. If I move them locally, I will have to find another way to get those backed up.
That is the common reason why people put them on to a network share.
The simple answer is to eliminate PST files. I tell clients there is no difference between deleting the content and storing it in PST files - you will lose the content eventually.
Even though you are backing up the PST files, the corruption in the files can go unnoticed for months, even years and then you have no chance of getting the content back.
If you are using Exchange 2013, import the content back in to Exchange, where it belongs. Not only will it be easier to backup, it is a lot more efficient than PST files. PST files can be up to THREE times bigger than the content in Exchange (so 100mb of content in Exchange could mean 300mb in a PST file).
I only use PST files for migrations, and that is only after eliminating all other options. Otherwise they have no place in a business environment.
Simon.
The simple answer is to eliminate PST files. I tell clients there is no difference between deleting the content and storing it in PST files - you will lose the content eventually.
Even though you are backing up the PST files, the corruption in the files can go unnoticed for months, even years and then you have no chance of getting the content back.
If you are using Exchange 2013, import the content back in to Exchange, where it belongs. Not only will it be easier to backup, it is a lot more efficient than PST files. PST files can be up to THREE times bigger than the content in Exchange (so 100mb of content in Exchange could mean 300mb in a PST file).
I only use PST files for migrations, and that is only after eliminating all other options. Otherwise they have no place in a business environment.
Simon.
I also have used network server storage for PSTs for archiving for many years without problems, although I've always had a slightly queasy feeling about it because of all the horror stories I've heard. With Exchange 2013, you really don't have any excuse, though. Set up a separate archive database for your users, enable archiving on their mailboxes, and then import the old content if they need to have on-line access to it. It's cleaner, safer, and faster in all respects.
ASKER
Wow....so it is nice that In-Place archiving doesn't work with our Office Standard Volume License. I cannot believe that Microsoft would only make that available to certain versions of Outlook, especially with both exchange 2013 and office standard 2013. Has anyone ran into this?
Oh, you do need an Enterprise CAL for some features, but I thought you didn't need it for archiving. I have Exchange 2010 at one of my clients, and as far as I know they don't have Enterprise CALs, but it works fine. I wonder if they changed this in 2013...
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Yeah I saw that. We have office 2013 standard on volume, not Pro Plus. Just bought the volume licensce for it about 8 months ago. FML!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.