Am rapidly approaching the end of my tether with MS's new invention of evil so am hoping that someone here can save me from having a complete strop and merrily flinging my entire test network out of my 3rd floor office window. I have a new network to bring online before Christmas - 35 roaming users that need locking down as much as possible, and that Office installs happily from an admin install point, they can just logon with their login, double-click their neat new Outlook icon on the desktop and they get straight into their email. 2003 server, xp pro sp1 workstations and Office 2003 sp1 - linking up to an exchange server 2000 sp3 at the main site.
My office deployment is working fine except for one most vexing aspect. Outlook 2003.
What I need to be able to achieve is this:
1) A user logs on - all the outlook settings are in place so things neatly open up into shiny new clean mailbox. I need to run Outlook in cached mode for exchange (I think) as 35 users on top of the rest are going to eat the bandwidth into the main site. The users have to have roaming profiles (or redirected folders at least) as they can logon to any pc - they're shift working outreach support workers, so there will be a bank of pc's available to them. So out of the 18000 various options or so in the Office 2003 custom installation wizard, what do I need to set so Outlook will roam with these users in cached exchange mode, or can't I? Do I need pst's to network shares or not?
This question is worth about 20000 points to me because I'm running out of time on this with all the other stuff I need to do. I know I can't post that many points, but will give as many as I can get away with if someone can help me out with this. Please ask any questions you need, but don't post general links as I can find them myself. Specific links or direct pointers based on experience would be hugely welcome. Thanks in advance,
I have asked this one before in a more general way, but as yet haven't had much joy with definite answers,