Re: Terminal Server Roaming Profiles and Outlook 2007

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

What exactly are you setting up in Outlook that can't wait until the actual user logs in? Most companies especially large ones want the profile to be correct for each user, not showing someone else on splash screens, etc, especially when it comes to the use credentials when office shows who has a particular file open. The same goes for any office app, what exactly needs to be setup ahead of time?

Jeff Pitsch
Microsoft MVP - Terminal Server
Citrix Technology Professional
Provision Networks VIP

Forums not enough?
Get support from the experts at your business
http://jeffpitschconsulting.com

Jer wrote:
I have Terminal Server 2003 R2 SP2 servers. I've read a ton on creating roaming profiles and have been pretty successful over the years at making them work. Basically, I'm trying to find the best way for me to create a "default user" that will work with Outlook 2007. What I currently do is go thru everything as an admin user and get every application and Windows layout as I want. Then I log out and copy this profile. Then I call it "Default User". Previously, the only problem with this was that some splash screens and certain other settings maintained the Admin's credentials. So, the Outlook 2000 splash screen stated Admin as the user, but once in it, it was the actual user's email and personal folders. This, in combination with some registry modifications, the Office Profile Wizard, and some scripting, resulted in an environment that worked (although I had to change the ntuser.dat to ntuser.man). Now, with Outlook 2007, the same approach results in the user trying to actually open the Admin's email instead of their own. If I go into Control Panel -> Mail and change it for the user, then all is fine. After 90 minutes with a Microsoft tech, I have found that they were zero help. Their answer is to have me have a very generic Default User, and then have each user set up their environment. It may have been the language barrier, but that seems messed up for a large environment. Is it possible to create a roaming profile (Default User) that has everything already setup for the new user upon their first login? Meaning, if they go into Outlook, it will try to open their mailbox? It sure seems that is should be easy enough, but I keep hitting roadblocks. I do see several registry changes that I could try in HKCU, but it seems a bit daunting.

Please advise.

Thank you,

Jer
.

Relevant Pages

  • Re: How do I Recover the emails in an old Outlook .OST file?
    ... can covert it to a PST file for recover or reconnect to that old OST file. ... If the original Microsoft Exchange profile existed and was not modified, ... The instruction to recover OST file when the original Outlook Profile ...
    (microsoft.public.windows.server.sbs)
  • RE: SBS2003 plus OL plus Business Contact Manager
    ... To check if your Outlook 2003 profile is configured to use "Cached Exchange ... once it is completed, you will see "Business Tools" ... Business Contact Manager for Outlook 2003 Update: ...
    (microsoft.public.windows.server.sbs)
  • Re: Change mail servers by scripting it
    ... apply changes with a .prf file. ... Sue Mosher, Outlook MVP ... > it to "modify" the Outlook profile it creates a new profile (not tested on ... > "migrate user settings". ...
    (microsoft.public.outlook.installation)
  • Re: Not All Outlook 2003 Email Attachments Go Out
    ... Outlook and are getting a winmail.dat attachment that they cannot open. ... I'd really try to not use Spamarrest for a while altogether. ... I could configure a second email account using my Google ... Where do I check to verify that my old profile is using ...
    (microsoft.public.outlook)
  • RE: Exchange Problems on One User
    ... > cannot receive email in the trial SBS 2003 Standard Server. ... > places (User Properties, Exchange General; Outlook rules). ... > appropriate user account and then select Properties, ... > re-create a new Outlook profile and then check if the issue can be ...
    (microsoft.public.windows.server.sbs)