We have XP clients with outlook 2000, a W2k DC, and use roaming profiles successfully. Only problems which arise are if the user's profile is set up on a pc with Outlook 2003, and they log on to an Outlook 2000 pc..and vice versa.
I'm setting this up this weekend. I really need some help. We have a couple of win2003 servers and 40 xp clients. Users need to be able to roam with outlook. I've been reading many articles saying that outlook doesn't roam with the user as the 'local settings' folder doesn't roam.
Does this definately work? Are any there any special requirements? Is it just a simple matter of setting roaming users as normal and outlook files will be available. I am not very experienced in this stuff but need to learn it somehow. I've just about managed to setup Active Directory. In the end I went with a .local domain instead of a .com domain, why? because I read it on forums. Can anyone confirm why this is considered the best way?
Do you have an Exchange server?
My company currently don't have a Exchange server. So, to achieve the goal that users can access their Outlook data from any workstation, I stored all users' PST file in the file server. When user open Outlook from a new location/workstation, roaming profile direct Outlook to connect to the PST file in the file server automatically. I hope this help.
We dont have an exchange server, just a normal pop3/smtp server where users get their mail.
We have all users pst & pab files saved onto a server, with each user using roaming xp profiles. I guess these could be saved within the roaming profile but I figured this would increase logon/logoff times ?
Their "outlook profile" follows them when they logon to different pc's, along with username / password etc.
Thanks for the reply. We have the same setup. I can see a solution for this. I am very grateful. No-where on thr microsoft website is this documented.
The confusing part for me I guess is:
"We have all users pst & pab files saved onto a server, with each user using roaming xp profiles"
The roaming profiles part is no problem. Storing all users pst and pab files is the problem. Do I have to myself log on with each user and re-direct those files to the server. i.e. log on with user1 and redirect files to <servername>/homedir/user1. then log on with user2 and redirect to <servername>/homed/user2 within each users login. Also how do you redirect these files within outlook.
Been doing a little more research today. On the Office 2003 resource kit, you can download .adm files. These can be imported into group policy. You can then use these policy templates to adjust where outlook stores it pst files i.e. by redirecting to users homedrive.
This I am hoping will avoid having to configure each user individually. I really want to do things properly the first time around.
Another thing that came to light when setting up my Active Directory Domain. I read that you should set up domains with as .local instead of .com. Do you know why this is?
your internal dns server would have difficulties in resolving the address.
There are also various security issues on having the same domain name, for both internal and external domains. Best to use .local or create a DNS namespace based on outlook2003.com eg uk.outlook2003.com, which is what we use here...
What do you think of importing the .adm files into grop policy to deploy re-directing the outlook store files. It should save on having to configure each version outlook individually
Thanks for your responses. I'm gonna give it a go on the weekend. Hopefully (fingers crossed) it will work. If worst comes to worst i'll do what you did. I will still create roaming users, but on each version of outlook installed manually redirect the store folder to a network location.
You should be able to create a default user profile by copying a standard profile to the netlogon folder on the server. When you first log in as the user the default profile will be copied from the netlogon folder. This could save hours of (very boring) configuration time.
I haven't tested it but if you configure the standard profile to use say \\server\outlook\%username%\outlook.pst this should create the pst file on the server with a different folder for each user. When you roam with your profile you will always see your Outlook folders as long as you have a connection to the server.
E-mail signatures and the like will roam as well because they are stored within the profile folders.
Thanks for the reply. I was thinking of just creating a new user through active directory and pointing the home directory to \\server\homedir\%username%. Then duplicating this user whenever creating a new one and changing login name.
Then deploying office to all the machines. Once done download the office reskit and import the .adm template for outlook 2003. This should allow me to use a group policy one the machines that have outlook installed. the group policy will direct the outlook files on all machines to \\server\homedir\%username%
This is what i figured will work. If you disagree please let me know.
To be completely honest with you your email has only made sense to me now. Thanks for the valuable tip. I didn't know much usre profiles until this experience and have a load more than I could have ever imagined. I didn't even know what the netlogon folder was and what it did. I am still in early learning stages. Please excuse me if my last reply made out ignore your advice.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.