No Outlook Email via RDP

  • Thread starter Thread starter Eric
  • Start date Start date
E

Eric

Guest
Ok, being new to SBS 2003 and TS integration, I am having an issue with users
loggin into the Terminal Server and accessing Outlook 2003. I can RDP into
the TS Server via my Wyse S90 WinTerm with XPe but when I launch Outlook, it
ask for a username and password.

Since I have logged into the TS server via RDP with the same usrename and
password I found it very odd to ask for this. Naturally I tried putting in
the username and password again only for it to prompt me for it again. For
some reason, It will not let me login to my Outlook email.

I did test a few standard worksation conversions to this new network from
SBS2000 and I can access email just fine.

After going through the process of removing the workstation from the old
domain and adding it to my new domain blah blah blah, I can login with the
username and password of all AD users and access email without the need to
input another username or password. I only have this issue with the users on
the Wyse Win Terminals accessing email via RDP. Very WEIRD!

Can anybody point me in the direction to fix this please? I thank you all in
advance.
 
RE: No Outlook Email via RDP

Directions on how to deploy Office Applications on Terminal Server are here:

http://www.sessioncomputing.com/ppt/ManagedMicrosoftOfficeInstallation.ppt

--
Patrick C. Rouse
Microsoft MVP - Terminal Server
Provision Networks VIP
Citrix Technology Professional
President - Session Computing Solutions, LLC
http://www.sessioncomputing.com



"Eric" wrote:

> Ok, being new to SBS 2003 and TS integration, I am having an issue with users
> loggin into the Terminal Server and accessing Outlook 2003. I can RDP into
> the TS Server via my Wyse S90 WinTerm with XPe but when I launch Outlook, it
> ask for a username and password.
>
> Since I have logged into the TS server via RDP with the same usrename and
> password I found it very odd to ask for this. Naturally I tried putting in
> the username and password again only for it to prompt me for it again. For
> some reason, It will not let me login to my Outlook email.
>
> I did test a few standard worksation conversions to this new network from
> SBS2000 and I can access email just fine.
>
> After going through the process of removing the workstation from the old
> domain and adding it to my new domain blah blah blah, I can login with the
> username and password of all AD users and access email without the need to
> input another username or password. I only have this issue with the users on
> the Wyse Win Terminals accessing email via RDP. Very WEIRD!
>
> Can anybody point me in the direction to fix this please? I thank you all in
> advance.
 
RE: No Outlook Email via RDP

Patrick,

I did follow the office installation guide as I was implementing the system.
I was able to successfully open Outlook on all profiles as well as sending
and receiving all emails until I added the TS Group Policy as provided by the
best practices guide for implementing Group Policy on TS. Now I cannot even
access my profiles as it says that they are not found or access is denied.

"Patrick Rouse" wrote:

> Directions on how to deploy Office Applications on Terminal Server are here:
>
> http://www.sessioncomputing.com/ppt/ManagedMicrosoftOfficeInstallation.ppt
>
> --
> Patrick C. Rouse
> Microsoft MVP - Terminal Server
> Provision Networks VIP
> Citrix Technology Professional
> President - Session Computing Solutions, LLC
> http://www.sessioncomputing.com
>
>
>
> "Eric" wrote:
>
> > Ok, being new to SBS 2003 and TS integration, I am having an issue with users
> > loggin into the Terminal Server and accessing Outlook 2003. I can RDP into
> > the TS Server via my Wyse S90 WinTerm with XPe but when I launch Outlook, it
> > ask for a username and password.
> >
> > Since I have logged into the TS server via RDP with the same usrename and
> > password I found it very odd to ask for this. Naturally I tried putting in
> > the username and password again only for it to prompt me for it again. For
> > some reason, It will not let me login to my Outlook email.
> >
> > I did test a few standard worksation conversions to this new network from
> > SBS2000 and I can access email just fine.
> >
> > After going through the process of removing the workstation from the old
> > domain and adding it to my new domain blah blah blah, I can login with the
> > username and password of all AD users and access email without the need to
> > input another username or password. I only have this issue with the users on
> > the Wyse Win Terminals accessing email via RDP. Very WEIRD!
> >
> > Can anybody point me in the direction to fix this please? I thank you all in
> > advance.
 
RE: No Outlook Email via RDP

Best Practice for applying Settings to Users only when they log on to
Terminal Servers would be to:

1. Create an OU to contain a set of Terminal Servers

2. Block Policy Inheritance on the OU (Properties -> Group Policy). This
prevents settings from higher-up in AD from affecting your Terminal Servers.

3. Move the Terminal Server Computer Objects into the OU. Do NOT place User
Accounts in this OU.

4. Create an Active Directory Security Group called “Terminal Servers” (or
something similar that you’ll recognize) and add the Terminal Servers from
this OU to this group.

5. Create a GPO called “TS Machine Policy” linked to the OU

6. Check “Disable User Configuration settings” on the GPO

7. Enable Loopback Policy Processing in the GPO

8. Edit the Security of the Policy so Apply Policy is set for “Authenticated
Users” and the Security Group containing the Terminal Servers

9. Create additional GPOs linked to this OU for each user population, i.e.
“TS Users”, “TS Administrators”.

10. Check “Disable Computer Configuration settings” on these GPO

11. Edit the Security on these User Configuration GPOs so Apply Policy is
enabled for the target user population, and Deny Apply Policy is enabled for
user to which the policy should not apply.

With GPOs configured this way the Machine Policy applies to everyone that
logs on to the Terminal Server (only the Computer Configuration Settings of
the Machine Policy are processed) in addition to the appropriate User
Configuration GPO (only the User Configuration portion of the GPO is
processed) for the target user population.

--
Patrick C. Rouse
Microsoft MVP - Terminal Server
Provision Networks VIP
Citrix Technology Professional
President - Session Computing Solutions, LLC
http://www.sessioncomputing.com



"Eric" wrote:

> Patrick,
>
> I did follow the office installation guide as I was implementing the system.
> I was able to successfully open Outlook on all profiles as well as sending
> and receiving all emails until I added the TS Group Policy as provided by the
> best practices guide for implementing Group Policy on TS. Now I cannot even
> access my profiles as it says that they are not found or access is denied.
>
> "Patrick Rouse" wrote:
>
> > Directions on how to deploy Office Applications on Terminal Server are here:
> >
> > http://www.sessioncomputing.com/ppt/ManagedMicrosoftOfficeInstallation.ppt
> >
> > --
> > Patrick C. Rouse
> > Microsoft MVP - Terminal Server
> > Provision Networks VIP
> > Citrix Technology Professional
> > President - Session Computing Solutions, LLC
> > http://www.sessioncomputing.com
> >
> >
> >
> > "Eric" wrote:
> >
> > > Ok, being new to SBS 2003 and TS integration, I am having an issue with users
> > > loggin into the Terminal Server and accessing Outlook 2003. I can RDP into
> > > the TS Server via my Wyse S90 WinTerm with XPe but when I launch Outlook, it
> > > ask for a username and password.
> > >
> > > Since I have logged into the TS server via RDP with the same usrename and
> > > password I found it very odd to ask for this. Naturally I tried putting in
> > > the username and password again only for it to prompt me for it again. For
> > > some reason, It will not let me login to my Outlook email.
> > >
> > > I did test a few standard worksation conversions to this new network from
> > > SBS2000 and I can access email just fine.
> > >
> > > After going through the process of removing the workstation from the old
> > > domain and adding it to my new domain blah blah blah, I can login with the
> > > username and password of all AD users and access email without the need to
> > > input another username or password. I only have this issue with the users on
> > > the Wyse Win Terminals accessing email via RDP. Very WEIRD!
> > >
> > > Can anybody point me in the direction to fix this please? I thank you all in
> > > advance.
 
RE: No Outlook Email via RDP

Thank you Patrick I appreciate your help. This did not help to correct the
issue however. For whatever reason, those using TS could not login to Outlook.

"Patrick Rouse" wrote:

> Best Practice for applying Settings to Users only when they log on to
> Terminal Servers would be to:
>
> 1. Create an OU to contain a set of Terminal Servers
>
> 2. Block Policy Inheritance on the OU (Properties -> Group Policy). This
> prevents settings from higher-up in AD from affecting your Terminal Servers.
>
> 3. Move the Terminal Server Computer Objects into the OU. Do NOT place User
> Accounts in this OU.
>
> 4. Create an Active Directory Security Group called “Terminal Servers” (or
> something similar that you’ll recognize) and add the Terminal Servers from
> this OU to this group.
>
> 5. Create a GPO called “TS Machine Policy” linked to the OU
>
> 6. Check “Disable User Configuration settings” on the GPO
>
> 7. Enable Loopback Policy Processing in the GPO
>
> 8. Edit the Security of the Policy so Apply Policy is set for “Authenticated
> Users” and the Security Group containing the Terminal Servers
>
> 9. Create additional GPOs linked to this OU for each user population, i.e.
> “TS Users”, “TS Administrators”.
>
> 10. Check “Disable Computer Configuration settings” on these GPO
>
> 11. Edit the Security on these User Configuration GPOs so Apply Policy is
> enabled for the target user population, and Deny Apply Policy is enabled for
> user to which the policy should not apply.
>
> With GPOs configured this way the Machine Policy applies to everyone that
> logs on to the Terminal Server (only the Computer Configuration Settings of
> the Machine Policy are processed) in addition to the appropriate User
> Configuration GPO (only the User Configuration portion of the GPO is
> processed) for the target user population.
>
> --
> Patrick C. Rouse
> Microsoft MVP - Terminal Server
> Provision Networks VIP
> Citrix Technology Professional
> President - Session Computing Solutions, LLC
> http://www.sessioncomputing.com
>
>
>
> "Eric" wrote:
>
> > Patrick,
> >
> > I did follow the office installation guide as I was implementing the system.
> > I was able to successfully open Outlook on all profiles as well as sending
> > and receiving all emails until I added the TS Group Policy as provided by the
> > best practices guide for implementing Group Policy on TS. Now I cannot even
> > access my profiles as it says that they are not found or access is denied.
> >
> > "Patrick Rouse" wrote:
> >
> > > Directions on how to deploy Office Applications on Terminal Server are here:
> > >
> > > http://www.sessioncomputing.com/ppt/ManagedMicrosoftOfficeInstallation.ppt
> > >
> > > --
> > > Patrick C. Rouse
> > > Microsoft MVP - Terminal Server
> > > Provision Networks VIP
> > > Citrix Technology Professional
> > > President - Session Computing Solutions, LLC
> > > http://www.sessioncomputing.com
> > >
> > >
> > >
> > > "Eric" wrote:
> > >
> > > > Ok, being new to SBS 2003 and TS integration, I am having an issue with users
> > > > loggin into the Terminal Server and accessing Outlook 2003. I can RDP into
> > > > the TS Server via my Wyse S90 WinTerm with XPe but when I launch Outlook, it
> > > > ask for a username and password.
> > > >
> > > > Since I have logged into the TS server via RDP with the same usrename and
> > > > password I found it very odd to ask for this. Naturally I tried putting in
> > > > the username and password again only for it to prompt me for it again. For
> > > > some reason, It will not let me login to my Outlook email.
> > > >
> > > > I did test a few standard worksation conversions to this new network from
> > > > SBS2000 and I can access email just fine.
> > > >
> > > > After going through the process of removing the workstation from the old
> > > > domain and adding it to my new domain blah blah blah, I can login with the
> > > > username and password of all AD users and access email without the need to
> > > > input another username or password. I only have this issue with the users on
> > > > the Wyse Win Terminals accessing email via RDP. Very WEIRD!
> > > >
> > > > Can anybody point me in the direction to fix this please? I thank you all in
> > > > advance.
 
Back
Top