Running Outlook 2003 on Windows 2003 Terminal Services server...

This is a reply to an old thread. I started a new message because I
couldn't reply to the old thread from Google. A gentleman that was
having the same problem outlined below, contacted me recently to ask
me whether or not we were using roaming profiles, which we are. He
discovered that the cause of the problem was in the profile. I
confirmed this by creating a new user in our domain with a clean
profile. That user was able to run Outlook 2003 on our 2003 Terminal
Server without needing to be a member of the administrators group.

I'd like to give credit where credit is due, and thank Tom at Infinity
Network Solutions for persevering and finding the solution to this. I
hope others can benefit from this solution to this rare problem.

Thanks,

Mike

googlegro...@xxxxxxxxxxx
View profile
I'm trying to set up a new 2003 terminal server here and am having
some issues getting Outlook 2003 to run properly. If I login with my
administrator account, Outlook runs fine. If I login as any other
typical user and try to run Outlook, I get a "Cannot Start Microsoft
Office Outlook" dialog box. I realize this is a permissions issue, but
have been unable to find any specific directions for setting
permissions for files and registry keys for Outlook in this situation.
I started using FileMon and RegMon to try to solve this, but figured
that there had to be a quicker way out there that has already been
documented. Can anyone point me to some solid deirections on how to
configure Outlook on a terminal server? Thanks, Mike
googlegro...@xxxxxxxxxxx
More options Oct 23 2006, 1:32 pm
Newsgroups: microsoft.public.windows.terminal_services
From: googlegro...@xxxxxxxxxxx
Date: 23 Oct 2006 10:32:05 -0700
Local: Mon, Oct 23 2006 1:32 pm
Subject: Running Outlook 2003 on Windows 2003 Terminal Services
server...
Reply to author | Forward | Print | Individual message | Show original
| Remove | Report this message | Find messages by this author
I'm trying to set up a new 2003 terminal server here and am having
some
issues getting Outlook 2003 to run properly. If I login with my
administrator account, Outlook runs fine. If I login as any other
typical user and try to run Outlook, I get a "Cannot Start Microsoft
Office Outlook" dialog box. I realize this is a permissions issue, but
have been unable to find any specific directions for setting
permissions for files and registry keys for Outlook in this situation.
I started using FileMon and RegMon to try to solve this, but figured
that there had to be a quicker way out there that has already been
documented. Can anyone point me to some solid deirections on how to
configure Outlook on a terminal server?

Thanks,

Mike
googlegro...@xxxxxxxxxxx

Reply Reply to author Forward
Cancel


Send Discard


From:
googlegroups@xxxxxxxxxxx
To:
Cc:
Followup To:

Add Cc | Add Followup-to | Edit Subject
Subject:
Send Discard






OscarSotoCL
View profile
More options Oct 23 2006, 7:53 pm
Newsgroups: microsoft.public.windows.terminal_services
From: "OscarSotoCL" <oscar.s...@xxxxxxxxxxxxxxxx>
Date: Mon, 23 Oct 2006 20:53:24 -0300
Local: Mon, Oct 23 2006 7:53 pm
Subject: Re: Running Outlook 2003 on Windows 2003 Terminal Services
server...
Reply to author | Forward | Print | Individual message | Show original
| Report this message | Find messages by this author
Mike:

Normally there's no reason for outlook 2003 not to run in terminal
services.
I have two enterprises running TS, with office 2003 and other tools,
like
Adobe Reader. Dou you have installed Office Before or After
installing
Terminal Services. Microsoft suggests installing First Terminal
Services
and then the rest of the applications. When you install the
application you
must take care of the "Terminal Services Application Setup Message" (A
square dialog box that appears every time you setup a new application
in
TS).

Hope this helps you

Oscar Soto Casali
MVP Directory Services

<googlegro...@xxxxxxxxxxx> escribió en el mensaje de
noticias:1161624724.930173.301...@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

- Hide quoted text -
- Show quoted text -
I'm trying to set up a new 2003 terminal server here and am having some
issues getting Outlook 2003 to run properly. If I login with my
administrator account, Outlook runs fine. If I login as any other
typical user and try to run Outlook, I get a "Cannot Start Microsoft
Office Outlook" dialog box. I realize this is a permissions issue, but
have been unable to find any specific directions for setting
permissions for files and registry keys for Outlook in this situation.
I started using FileMon and RegMon to try to solve this, but figured
that there had to be a quicker way out there that has already been
documented. Can anyone point me to some solid deirections on how to
configure Outlook on a terminal server?

Thanks,

Mike
googlegro...@xxxxxxxxxxx


Reply Reply to author Forward Rate this post: Text for clearing
space





googlegro...@xxxxxxxxxxx
View profile
More options Oct 24 2006, 1:02 am
Newsgroups: microsoft.public.windows.terminal_services
From: googlegro...@xxxxxxxxxxx
Date: 23 Oct 2006 22:02:51 -0700
Local: Tues, Oct 24 2006 1:02 am
Subject: Re: Running Outlook 2003 on Windows 2003 Terminal Services
server...
Reply to author | Forward | Print | Individual message | Show original
| Remove | Report this message | Find messages by this author
Oscar,

Thanks for your quick reply. I did install TS before I installed
Office. I then installed Office from the "Add/Remove Programs" which
should have put TS into "install mode" while the installation ran. I
did not press the "Next" and "Finish" buttons until the Office
installation was complete. I set up a test server today with 2003
Server and Office 2003 to see if something went wrong the first time.
My exact order of installation was this:

1. Installed Windows 2003 Standard
2. Added TS option from Windows Components, left in "Full Security"
mode
3. Installed SP1 for 2003 Server
4. Installed Office 2003
5. Joined server to domain

The result was the same. The user can run Outlook as long as he is a
member of the Administrators group, otherwise Outlook produces the
error I mentioned previously. Can you see anything wrong with my
installation process? Do you have any other suggestions?

Thanks,

Mike

- Hide quoted text -
- Show quoted text -
OscarSotoCL wrote:
Mike:

Normally there's no reason for outlook 2003 not to run in terminal services.
I have two enterprises running TS, with office 2003 and other tools, like
Adobe Reader. Dou you have installed Office Before or After installing
Terminal Services. Microsoft suggests installing First Terminal Services
and then the rest of the applications. When you install the application you
must take care of the "Terminal Services Application Setup Message" (A
square dialog box that appears every time you setup a new application in
TS).

Hope this helps you

Oscar Soto Casali
MVP Directory Services

<googlegro...@xxxxxxxxxxx> escribió en el mensaje de
noticias:1161624724.930173.301...@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I'm trying to set up a new 2003 terminal server here and am having some
issues getting Outlook 2003 to run properly. If I login with my
administrator account, Outlook runs fine. If I login as any other
typical user and try to run Outlook, I get a "Cannot Start Microsoft
Office Outlook" dialog box. I realize this is a permissions issue, but
have been unable to find any specific directions for setting
permissions for files and registry keys for Outlook in this situation.
I started using FileMon and RegMon to try to solve this, but figured
that there had to be a quicker way out there that has already been
documented. Can anyone point me to some solid deirections on how to
configure Outlook on a terminal server?

Thanks,

Mike
googlegro...@xxxxxxxxxxx


Reply Reply to author Forward





Vera Noest [MVP]
View profile
More options Oct 24 2006, 3:43 pm
Newsgroups: microsoft.public.windows.terminal_services
From: "Vera Noest [MVP]" <vera.no...@xxxxxxxxxxxxxxxxxxxxxxxxx>
Date: Tue, 24 Oct 2006 12:43:24 -0700
Local: Tues, Oct 24 2006 3:43 pm
Subject: Re: Running Outlook 2003 on Windows 2003 Terminal Services
server...
Reply to author | Forward | Print | Individual message | Show original
| Report this message | Find messages by this author
Anything in the EventLog?
Can the users start other Office applications?

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

googlegro...@xxxxxxxxxxx wrote on 24 okt 2006 in
microsoft.public.windows.terminal_services:

- Hide quoted text -
- Show quoted text -
Oscar,

Thanks for your quick reply. I did install TS before I installed
Office. I then installed Office from the "Add/Remove Programs"
which should have put TS into "install mode" while the
installation ran. I did not press the "Next" and "Finish"
buttons until the Office installation was complete. I set up a
test server today with 2003 Server and Office 2003 to see if
something went wrong the first time. My exact order of
installation was this:

1. Installed Windows 2003 Standard
2. Added TS option from Windows Components, left in "Full
Security" mode
3. Installed SP1 for 2003 Server
4. Installed Office 2003
5. Joined server to domain

The result was the same. The user can run Outlook as long as he
is a member of the Administrators group, otherwise Outlook
produces the error I mentioned previously. Can you see anything
wrong with my installation process? Do you have any other
suggestions?

Thanks,

Mike

OscarSotoCL wrote:
Mike:

Normally there's no reason for outlook 2003 not to run in
terminal servic
es.
I have two enterprises running TS, with office 2003 and other
tools, like Adobe Reader. Dou you have installed Office Before
or After installing Terminal Services. Microsoft suggests
installing First Terminal Services and then the rest of the
applications. When you install the application
you
must take care of the "Terminal Services Application Setup
Message" (A square dialog box that appears every time you setup
a new application in TS).

Hope this helps you

Oscar Soto Casali
MVP Directory Services

<googlegro...@xxxxxxxxxxx> escribió en el mensaje de
noticias:1161624724.930173.301...@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I'm trying to set up a new 2003 terminal server here and am
having some issues getting Outlook 2003 to run properly. If I
login with my administrator account, Outlook runs fine. If I
login as any other typical user and try to run Outlook, I get
a "Cannot Start Microsoft Office Outlook" dialog box. I
realize this is a permissions issue, but have been unable to
find any specific directions for setting permissions for
files and registry keys for Outlook in this situation. I
started using FileMon and RegMon to try to solve this, but
figured that there had to be a quicker way out there that has
already been documented. Can anyone point me to some solid
deirections on how to configure Outlook on a terminal server?

Thanks,

Mike
googlegro...@xxxxxxxxxxx


Reply Reply to author Forward Rate this post: Text for clearing
space





googlegro...@xxxxxxxxxxx
View profile
More options Oct 27 2006, 1:40 pm
Newsgroups: microsoft.public.windows.terminal_services
From: googlegro...@xxxxxxxxxxx
Date: 27 Oct 2006 10:40:41 -0700
Local: Fri, Oct 27 2006 1:40 pm
Subject: Re: Running Outlook 2003 on Windows 2003 Terminal Services
server...
Reply to author | Forward | Print | Individual message | Show original
| Remove | Report this message | Find messages by this author
Yes, all other Office apps appear to work fine. Oddly, there doesn't
seem to be any entries in the app log regarding the Outlook problem. I
do see some stating that the Folder Redirection policy failed to
execute.

For some unexplained reason, we are now seeing different behavior on
the TS. Outlook will now run, but the user's Outlook profile is not
loading properly, i.e. they don't get any of their Exchange
configuration. We are wondering if this is related to some AD
corruption that we experienced in the past. As a test, I set up a
completely separate domain on a test server and configured a TS for
that domain. Outlook can be run without any problems when logged on as
a normal user on that test TS. This does not make me very happy... Is
there a way to check for and correct any abnormalities in AD?

Giving the user local admin rights seems to completely alleviate the
problem. We are locking this TS down pretty tightly via GP, even using
software restriction policies (that GPO is not applied right now, as
we
were trying to determine the cause of the Outlook issue). Would it be
too dangerous to allow users to be local admins on the TS if we have
all these other protections in place via GP?

Thanks,

Mike

On Oct 24, 3:43 pm, "Vera Noest [MVP]"

- Hide quoted text -
- Show quoted text -
<vera.no...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Anything in the EventLog?
Can the users start other Office applications?

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

googlegro...@xxxxxxxxxxx wrote on 24 okt 2006 in
microsoft.public.windows.terminal_services:

Oscar,

Thanks for your quick reply. I did install TS before I installed
Office. I then installed Office from the "Add/Remove Programs"
which should have put TS into "install mode" while the
installation ran. I did not press the "Next" and "Finish"
buttons until the Office installation was complete. I set up a
test server today with 2003 Server and Office 2003 to see if
something went wrong the first time. My exact order of
installation was this:

1. Installed Windows 2003 Standard
2. Added TS option from Windows Components, left in "Full
Security" mode
3. Installed SP1 for 2003 Server
4. Installed Office 2003
5. Joined server to domain

The result was the same. The user can runOutlookas long as he
is a member of the Administrators group, otherwiseOutlook
produces the error I mentioned previously. Can you see anything
wrong with my installation process? Do you have any other
suggestions?

Thanks,

Mike

OscarSotoCL wrote:
Mike:

Normally there's no reason foroutlook2003 not to run in
terminal servic
es.
I have two enterprises running TS, with office 2003 and other
tools, like Adobe Reader. Dou you have installed Office Before
or After installing Terminal Services. Microsoft suggests
installing First Terminal Services and then the rest of the
applications. When you install the application
you
must take care of the "Terminal Services Application Setup
Message" (A square dialog box that appears every time you setup
a new application in TS).

Hope this helps you

Oscar Soto Casali
MVP Directory Services

<googlegro...@xxxxxxxxxxx> escribió en el mensaje de
noticias:1161624724.930173.301...@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I'm trying to set up a new 2003 terminal server here and am
having some issues gettingOutlook2003 to run properly. If I
login with my administrator account,Outlookruns fine. If I
login as any other typical user and try to runOutlook, I get
a "Cannot Start Microsoft OfficeOutlook" dialog box. I
realize this is a permissions issue, but have been unable to
find any specific directions for setting permissions for
files and registry keys forOutlookin this situation. I
started using FileMon and RegMon to try to solve this, but
figured that there had to be a quicker way out there that has
already been documented. Can anyone point me to some solid
deirections on how to configureOutlookon a terminal server?

Thanks,

Mike
googlegro...@xxxxxxxxxxx


Reply Reply to author Forward
Cancel


Send Discard


From:
googlegroups@xxxxxxxxxxx
To:
Cc:
Followup To:

Add Cc | Add Followup-to | Edit Subject
Subject:
Send Discard

.