B
Bob Singer
I support 70+ users who are running Windows XP. I've been
working on an Office 2003 deployment and have run into a
big Outlook problem.
Here's the situation:
The users don't have access to their C: drive and can't
install software. They're configured as roaming users and
their 'My Documents' folder is redirected to their home
drive on the server. So, what I wanted to do was create
an install that would locate their PST file(s)in a folder
on their home drive. They would IMAP to our mail server.
The problem:
The IMAP PST is created by default in the users local
application data folder located at:
C:\Documents and Settings\%USERNAME%\Local
Settings\Application Data\Microsoft\Outlook.
So, it is not replicated with their roaming profile.
Relocating the IMAP PST file to the server drive doesn't
work. I've tried many experiments trying to get this to
work, without success, including a GPO redirecting PST
creation to the users home drive.
I've read a few places that there is a hack to fix this
and I've read that it can't be done. What's the truth?
If this is a real limitation, how are roaming users
supposed to use Outlook 2003?
The whole point of roaming is that it allows your users
to use any machine with their settings which follow them.
If this is a limitation of Outlook, why? I mean, the
other e-mail clients out their allow their data file to
exist where ever you want to put it. It doesn't make a
great deal of sense, technically or business-wise.
working on an Office 2003 deployment and have run into a
big Outlook problem.
Here's the situation:
The users don't have access to their C: drive and can't
install software. They're configured as roaming users and
their 'My Documents' folder is redirected to their home
drive on the server. So, what I wanted to do was create
an install that would locate their PST file(s)in a folder
on their home drive. They would IMAP to our mail server.
The problem:
The IMAP PST is created by default in the users local
application data folder located at:
C:\Documents and Settings\%USERNAME%\Local
Settings\Application Data\Microsoft\Outlook.
So, it is not replicated with their roaming profile.
Relocating the IMAP PST file to the server drive doesn't
work. I've tried many experiments trying to get this to
work, without success, including a GPO redirecting PST
creation to the users home drive.
I've read a few places that there is a hack to fix this
and I've read that it can't be done. What's the truth?
If this is a real limitation, how are roaming users
supposed to use Outlook 2003?
The whole point of roaming is that it allows your users
to use any machine with their settings which follow them.
If this is a limitation of Outlook, why? I mean, the
other e-mail clients out their allow their data file to
exist where ever you want to put it. It doesn't make a
great deal of sense, technically or business-wise.