Roaming profiles XP SP3

Hello !!
i'm using roaming profiles in a windows 2003 with my XP sp3.
is there any problems related to syunchronizing the outlook *.pst files from
the local application data to the shared roaming location ?
if there's no problem .. may any one tell me why it doesn't synchronize ?

Thanks
Ahmad

Ahmad Sabry <(E-Mail Removed)> wrote:
> Hello !!
> i'm using roaming profiles in a windows 2003 with my XP sp3.
> is there any problems related to syunchronizing the outlook *.pst
> files from the local application data to the shared roaming location ?
> if there's no problem .. may any one tell me why it doesn't
> synchronize ?
> Thanks
> Ahmad

Hi - ...a few notes:

If you want them to work, PST files *must* reside on a local drive - it is
not supported to access them across a LAN or WAN connection. You will face
performance and data corruption issues otherwise. PST files are rather
unsuitable in a corporate environment for many reasons....I suggest you look
into Exchange server, either locally or remotely hosted. I don't recommend
PST files even for archiving,

See
http://support.microsoft.com/?id=297019
and
http://www.exchangefaq.org/faq/Excha.../qid/1209Ifyou want to use PST files on the network anyway, you should put them intheusers' home directories. Nothing in "local settings" will roam,ofcourse....and you really want to keep your profiles miniscule if you wanttokeep them working at all.Here's my boilerplate on roaming profiles.Generaltips:1. Set up a share on the server. For example - d:\profiles, sharedasprofiles$ to make it hidden from browsing. Make sure this share is *not*setto allow offline files/caching! (that's on by default - disable it)2.Make sure the share permissions on profiles$ indicate everyone=fullcontrol.Set the NTFS security to administrators, system, and users=fullcontrol.3. Inthe users' ADUC properties, specify \\server\profiles$\%username% intheprofiles field4. Have each user log into the domain once from their usualworkstation(where their existing profile lives) and log out. The profile isnowroaming.5. If you want the administrators group to automatically havepermissions tothe profiles folders, you'll need to make the appropriatechange in grouppolicy. Look in computer configuration/administrativetemplates/system/userprofiles - there's an option to add administratorsgroup to the roamingprofiles permissions.Notes:* Make sure users understandthat they should not log into multiplecomputers at the same time when theyhave roaming profiles (unless you makethe profiles mandatory by renamingntuser.dat to ntuser.man so they can'tchange them). Explain that thelast oneout wins, when it comes to uploading the final, changed copy of theprofile.* Keep your profiles TINY. Via group policy, redirect My Documentsat thevery least - to a subfolder of the user's home directory or userfolder.Also consider redirecting Desktop & Application Data similarly.....so theuser will have:\\server\home$\%username%\MyDocuments,\\serve r\home$\%username%\Desktop,\\server\home$\%usernam e%\Application Data.Alternatively, just manually re-target My Documentsto\\server\home$\%username% (this is not optimal, however!)If you aren'tgoing to also redirect the desktop using policies, tell usersthatthey arenot to store any files on the desktop or you will beat them with astick. Bigprofile=slow login/logout, and possible profile corruption.* Note that userprofiles are not compatible between different OS versions,even betweenW2k/XP. Keep all your computers. Keep your workstations asidentical aspossible - meaning, OS version is the same, SP level is thesame, app load is(as much as possible) the same.* Do not let people store any data locally -all data belongs on the server.* The User Profile Hive Cleanup Utilityshould be running on all yourcomputers. You can download ithere:http://www.microsoft.com/downloads/d...lang=enRoaming profile & folder redirectionarticle -http://www.windowsnetworking.com/articles_tutorials/Profile-Folder-Redirection-Windows-Server-2003.html