Publicating a TS Farm in TS Web Access 2008

  • Thread starter Thread starter Ralph
  • Start date Start date
R

Ralph

Guest
Hello,

Can we configure a TS Web Access to populate the Remote Apps of several TS ?

We did not want to setup IIS on the TS and installed the TS Web App on a
dedicated server.

We published remote apps that point to a TS Farm but as it seems we cannot
enter a TS Farm name in the TS Web App configuration I had to enter a
specific TS in the configuration. When this specific is down no remote apps
are listed in the TS Web Apps. So how can we manage to publish remote app
that point to a TS Farm with the TS Web Access on a dedicated server ?

Thank you, Ralph
 
Re: Publicating a TS Farm in TS Web Access 2008

Configure the data source for TS Web Access
You can configure TS Web Access to populate the list of RemoteApp programs
that appear in the Web Part from a specific terminal server or terminal
server farm.

Specify the data source for TS Web Access
By default, TS Web Access populates its list of RemoteApp programs from a
single terminal server, and points to the local host. The Web Part is
populated by all RemoteApp programs that are enabled for TS Web Access on
that terminal server's RemoteApp Programs list.

To complete this procedure, you must log on to the TS Web Access server by
using the local Administrator account or an account that is a member of the
TS Web Access Administrators group on the TS Web Access server.

To specify which terminal server to use as the data source
1. Connect to the TS Web Access Web site. To do this, use either of the
following methods:
. On the TS Web Access server, click Start, point to Administrative Tools,
point to Terminal Services, and then click TS Web Access Administration.
. Use Internet Explorer to connect to the TS Web Access Web site. By
default, the Web site is located at the following address, where server_name
is the name of the TS Web Access server:
http://server_name/ts
2. Log on to the site by using either the local Administrator account, or
an account that is a member of the local TS Web Access Administrators group.
(If you are already logged on to the computer as one of these accounts, you
are not prompted for credentials.)
3. On the title bar, click the Configuration tab.
Note: If you access the TS Web Access Web site by using the TS Web Access
Administration option, the page automatically opens to the Configuration
tab.
4. In the Editor Zone area, in the Terminal server name box, enter the name
of the terminal server that you want to use as the data source.
5. Click Apply to apply the changes.


For more info check following link
http://technet2.microsoft.com/windo...dad1-4fd2-b4a3-a91a22973def1033.mspx?mfr=true

Ratnesh


"Ralph" <ralph@nospam.net> wrote in message
news:uRIljHNmIHA.5080@TK2MSFTNGP02.phx.gbl...
> Hello,
>
> Can we configure a TS Web Access to populate the Remote Apps of several TS
> ?
>
> We did not want to setup IIS on the TS and installed the TS Web App on a
> dedicated server.
>
> We published remote apps that point to a TS Farm but as it seems we cannot
> enter a TS Farm name in the TS Web App configuration I had to enter a
> specific TS in the configuration. When this specific is down no remote
> apps are listed in the TS Web Apps. So how can we manage to publish remote
> app that point to a TS Farm with the TS Web Access on a dedicated server ?
>
> Thank you, Ralph
>
>
 
Re: Publicating a TS Farm in TS Web Access 2008

Ratnesh,

Your answer doesn't address the question. I too am having the same issue
where TSweb will not list applications published for a farm. TSweb seems to
only publish applications from an individual terminal server. Microsoft's
documentation explains that you can either point the TSweb Access Properties
to a individual server or single farm. Point to a single farm doesn't seem to
work. The only other documentation that i have seen that kind of addresses
the issue is to customize TS web access using share point services to creat a
single web access point.

Could you clarify your explaination with regards to pointing TSweb to a farm?

Gabriel



"Ratnesh Yadav [MSFT]" wrote:

> Configure the data source for TS Web Access
> You can configure TS Web Access to populate the list of RemoteApp programs
> that appear in the Web Part from a specific terminal server or terminal
> server farm.
>
> Specify the data source for TS Web Access
> By default, TS Web Access populates its list of RemoteApp programs from a
> single terminal server, and points to the local host. The Web Part is
> populated by all RemoteApp programs that are enabled for TS Web Access on
> that terminal server's RemoteApp Programs list.
>
> To complete this procedure, you must log on to the TS Web Access server by
> using the local Administrator account or an account that is a member of the
> TS Web Access Administrators group on the TS Web Access server.
>
> To specify which terminal server to use as the data source
> 1. Connect to the TS Web Access Web site. To do this, use either of the
> following methods:
> . On the TS Web Access server, click Start, point to Administrative Tools,
> point to Terminal Services, and then click TS Web Access Administration.
> . Use Internet Explorer to connect to the TS Web Access Web site. By
> default, the Web site is located at the following address, where server_name
> is the name of the TS Web Access server:
> http://server_name/ts
> 2. Log on to the site by using either the local Administrator account, or
> an account that is a member of the local TS Web Access Administrators group.
> (If you are already logged on to the computer as one of these accounts, you
> are not prompted for credentials.)
> 3. On the title bar, click the Configuration tab.
> Note: If you access the TS Web Access Web site by using the TS Web Access
> Administration option, the page automatically opens to the Configuration
> tab.
> 4. In the Editor Zone area, in the Terminal server name box, enter the name
> of the terminal server that you want to use as the data source.
> 5. Click Apply to apply the changes.
>
>
> For more info check following link
> http://technet2.microsoft.com/windo...dad1-4fd2-b4a3-a91a22973def1033.mspx?mfr=true
>
> Ratnesh
>
>
> "Ralph" <ralph@nospam.net> wrote in message
> news:uRIljHNmIHA.5080@TK2MSFTNGP02.phx.gbl...
> > Hello,
> >
> > Can we configure a TS Web Access to populate the Remote Apps of several TS
> > ?
> >
> > We did not want to setup IIS on the TS and installed the TS Web App on a
> > dedicated server.
> >
> > We published remote apps that point to a TS Farm but as it seems we cannot
> > enter a TS Farm name in the TS Web App configuration I had to enter a
> > specific TS in the configuration. When this specific is down no remote
> > apps are listed in the TS Web Apps. So how can we manage to publish remote
> > app that point to a TS Farm with the TS Web Access on a dedicated server ?
> >
> > Thank you, Ralph
> >
> >

>
 
Re: Publicating a TS Farm in TS Web Access 2008

If you point to a farm name, there must be a DNS entry for that farm name,
and WMI traffic to the farm name must reach one of the TSs in the farm. In
addition, all farm members must be identically configured.

Rob

"gabriel miller" <gabrielmiller@discussions.microsoft.com> wrote in message
news:92BD7096-B5A4-4496-8D0A-BDF26AA74514@microsoft.com...
> Ratnesh,
>
> Your answer doesn't address the question. I too am having the same issue
> where TSweb will not list applications published for a farm. TSweb seems
> to
> only publish applications from an individual terminal server. Microsoft's
> documentation explains that you can either point the TSweb Access
> Properties
> to a individual server or single farm. Point to a single farm doesn't seem
> to
> work. The only other documentation that i have seen that kind of addresses
> the issue is to customize TS web access using share point services to
> creat a
> single web access point.
>
> Could you clarify your explaination with regards to pointing TSweb to a
> farm?
>
> Gabriel
>
>
>
> "Ratnesh Yadav [MSFT]" wrote:
>
>> Configure the data source for TS Web Access
>> You can configure TS Web Access to populate the list of RemoteApp
>> programs
>> that appear in the Web Part from a specific terminal server or terminal
>> server farm.
>>
>> Specify the data source for TS Web Access
>> By default, TS Web Access populates its list of RemoteApp programs from a
>> single terminal server, and points to the local host. The Web Part is
>> populated by all RemoteApp programs that are enabled for TS Web Access on
>> that terminal server's RemoteApp Programs list.
>>
>> To complete this procedure, you must log on to the TS Web Access server
>> by
>> using the local Administrator account or an account that is a member of
>> the
>> TS Web Access Administrators group on the TS Web Access server.
>>
>> To specify which terminal server to use as the data source
>> 1. Connect to the TS Web Access Web site. To do this, use either of the
>> following methods:
>> . On the TS Web Access server, click Start, point to Administrative
>> Tools,
>> point to Terminal Services, and then click TS Web Access Administration.
>> . Use Internet Explorer to connect to the TS Web Access Web site. By
>> default, the Web site is located at the following address, where
>> server_name
>> is the name of the TS Web Access server:
>> http://server_name/ts
>> 2. Log on to the site by using either the local Administrator account,
>> or
>> an account that is a member of the local TS Web Access Administrators
>> group.
>> (If you are already logged on to the computer as one of these accounts,
>> you
>> are not prompted for credentials.)
>> 3. On the title bar, click the Configuration tab.
>> Note: If you access the TS Web Access Web site by using the TS Web
>> Access
>> Administration option, the page automatically opens to the Configuration
>> tab.
>> 4. In the Editor Zone area, in the Terminal server name box, enter the
>> name
>> of the terminal server that you want to use as the data source.
>> 5. Click Apply to apply the changes.
>>
>>
>> For more info check following link
>> http://technet2.microsoft.com/windo...dad1-4fd2-b4a3-a91a22973def1033.mspx?mfr=true
>>
>> Ratnesh
>>
>>
>> "Ralph" <ralph@nospam.net> wrote in message
>> news:uRIljHNmIHA.5080@TK2MSFTNGP02.phx.gbl...
>> > Hello,
>> >
>> > Can we configure a TS Web Access to populate the Remote Apps of several
>> > TS
>> > ?
>> >
>> > We did not want to setup IIS on the TS and installed the TS Web App on
>> > a
>> > dedicated server.
>> >
>> > We published remote apps that point to a TS Farm but as it seems we
>> > cannot
>> > enter a TS Farm name in the TS Web App configuration I had to enter a
>> > specific TS in the configuration. When this specific is down no remote
>> > apps are listed in the TS Web Apps. So how can we manage to publish
>> > remote
>> > app that point to a TS Farm with the TS Web Access on a dedicated
>> > server ?
>> >
>> > Thank you, Ralph
>> >
>> >

>>
 
Re: Publicating a TS Farm in TS Web Access 2008

DNS A and ptr records exist, all machines are on the same ip network/switch,
WMI appears to be working because my NMS platform uses WMI to pull
performance counters, and the servers in the farm should be identical because
one configuration was made on one server and exported to the other. What else
is there to check? Is there a log file or something?

"Rob Leitman [MS]" wrote:

> If you point to a farm name, there must be a DNS entry for that farm name,
> and WMI traffic to the farm name must reach one of the TSs in the farm. In
> addition, all farm members must be identically configured.
>
> Rob
>
> "gabriel miller" <gabrielmiller@discussions.microsoft.com> wrote in message
> news:92BD7096-B5A4-4496-8D0A-BDF26AA74514@microsoft.com...
> > Ratnesh,
> >
> > Your answer doesn't address the question. I too am having the same issue
> > where TSweb will not list applications published for a farm. TSweb seems
> > to
> > only publish applications from an individual terminal server. Microsoft's
> > documentation explains that you can either point the TSweb Access
> > Properties
> > to a individual server or single farm. Point to a single farm doesn't seem
> > to
> > work. The only other documentation that i have seen that kind of addresses
> > the issue is to customize TS web access using share point services to
> > creat a
> > single web access point.
> >
> > Could you clarify your explaination with regards to pointing TSweb to a
> > farm?
> >
> > Gabriel
> >
> >
> >
> > "Ratnesh Yadav [MSFT]" wrote:
> >
> >> Configure the data source for TS Web Access
> >> You can configure TS Web Access to populate the list of RemoteApp
> >> programs
> >> that appear in the Web Part from a specific terminal server or terminal
> >> server farm.
> >>
> >> Specify the data source for TS Web Access
> >> By default, TS Web Access populates its list of RemoteApp programs from a
> >> single terminal server, and points to the local host. The Web Part is
> >> populated by all RemoteApp programs that are enabled for TS Web Access on
> >> that terminal server's RemoteApp Programs list.
> >>
> >> To complete this procedure, you must log on to the TS Web Access server
> >> by
> >> using the local Administrator account or an account that is a member of
> >> the
> >> TS Web Access Administrators group on the TS Web Access server.
> >>
> >> To specify which terminal server to use as the data source
> >> 1. Connect to the TS Web Access Web site. To do this, use either of the
> >> following methods:
> >> . On the TS Web Access server, click Start, point to Administrative
> >> Tools,
> >> point to Terminal Services, and then click TS Web Access Administration.
> >> . Use Internet Explorer to connect to the TS Web Access Web site. By
> >> default, the Web site is located at the following address, where
> >> server_name
> >> is the name of the TS Web Access server:
> >> http://server_name/ts
> >> 2. Log on to the site by using either the local Administrator account,
> >> or
> >> an account that is a member of the local TS Web Access Administrators
> >> group.
> >> (If you are already logged on to the computer as one of these accounts,
> >> you
> >> are not prompted for credentials.)
> >> 3. On the title bar, click the Configuration tab.
> >> Note: If you access the TS Web Access Web site by using the TS Web
> >> Access
> >> Administration option, the page automatically opens to the Configuration
> >> tab.
> >> 4. In the Editor Zone area, in the Terminal server name box, enter the
> >> name
> >> of the terminal server that you want to use as the data source.
> >> 5. Click Apply to apply the changes.
> >>
> >>
> >> For more info check following link
> >> http://technet2.microsoft.com/windo...dad1-4fd2-b4a3-a91a22973def1033.mspx?mfr=true
> >>
> >> Ratnesh
> >>
> >>
> >> "Ralph" <ralph@nospam.net> wrote in message
> >> news:uRIljHNmIHA.5080@TK2MSFTNGP02.phx.gbl...
> >> > Hello,
> >> >
> >> > Can we configure a TS Web Access to populate the Remote Apps of several
> >> > TS
> >> > ?
> >> >
> >> > We did not want to setup IIS on the TS and installed the TS Web App on
> >> > a
> >> > dedicated server.
> >> >
> >> > We published remote apps that point to a TS Farm but as it seems we
> >> > cannot
> >> > enter a TS Farm name in the TS Web App configuration I had to enter a
> >> > specific TS in the configuration. When this specific is down no remote
> >> > apps are listed in the TS Web Apps. So how can we manage to publish
> >> > remote
> >> > app that point to a TS Farm with the TS Web Access on a dedicated
> >> > server ?
> >> >
> >> > Thank you, Ralph
> >> >
> >> >
> >>

>
>
 
Publicating a TS Farm in TS Web Access 2008

It is currently NOT possible to configure TS Web Access to point to a farm though documentation says it is.

This is because kerberos is used for non-local authentication instead of NTLM.
 
Re: Publicating a TS Farm in TS Web Access 2008

So your saying that all that beta testing was for nothing and this feature
just completely does not work? I'll have to let the companies know who have
it working that they dont' actually have it working :)

sorry, just having fun. Blanket statements like this on a big feature like
this are typically incorrect, just fyi.

Jeff Pitsch
Microsoft MVP - Terminal Services


<Don> wrote in message news:2008711102830dokoni@microsoft.com...
> It is currently NOT possible to configure TS Web Access to point to a farm
> though documentation says it is.
>
> This is because kerberos is used for non-local authentication instead of
> NTLM.
>
>
 
Re: Publicating a TS Farm in TS Web Access 2008

Actually Don is 100% correct. I opened a case w/ Microsoft and here is the
status. In summary this configuration will not work as documemted.

"Gabriel,

Our Windows Sustained Engineering and Development team are still working on
this issue. When we use farm name in TS Web Client Configuration page, TS
web client makes a WMI call to the Terminal Server. To authenticate the
server the TS Web client uses Kerberos which will fail as there is no SRV
record for the TS farm name.

Currently Development team is working on two fixes in Windows 7 (next
version of Windows). First fix is to allow negotiate in WMI and then fix the
TS web client to use negotiate when making a WMI call.

Once the fix is checked into Windows 7, our Sustained Engineering team will
analyze the fix and see if it can be safely back ported to Windows 2008.

Please let me know if you have any questions

Thanks and Regards,
name removed
Windows 2000/XP/2003/Vista Escalation Engineer"



"Jeff Pitsch" wrote:

> So your saying that all that beta testing was for nothing and this feature
> just completely does not work? I'll have to let the companies know who have
> it working that they dont' actually have it working :)
>
> sorry, just having fun. Blanket statements like this on a big feature like
> this are typically incorrect, just fyi.
>
> Jeff Pitsch
> Microsoft MVP - Terminal Services
>
>
> <Don> wrote in message news:2008711102830dokoni@microsoft.com...
> > It is currently NOT possible to configure TS Web Access to point to a farm
> > though documentation says it is.
> >
> > This is because kerberos is used for non-local authentication instead of
> > NTLM.
> >
> >

>
>
>
 
Re: Publicating a TS Farm in TS Web Access 2008

You can point TS Web Access to a farm member name and this will get you most
of the benefits, as long as you set the farm name in RemoteApp Manager.

The only thing this doesn't get you is high availability, if the individual
TS you entered goes down.

Rob

"gabriel miller" <gabrielmiller@discussions.microsoft.com> wrote in message
news:E27C1978-B411-4A34-845F-25A8DE7AC4ED@microsoft.com...
> Actually Don is 100% correct. I opened a case w/ Microsoft and here is the
> status. In summary this configuration will not work as documemted.
>
> "Gabriel,
>
> Our Windows Sustained Engineering and Development team are still working
> on
> this issue. When we use farm name in TS Web Client Configuration page, TS
> web client makes a WMI call to the Terminal Server. To authenticate the
> server the TS Web client uses Kerberos which will fail as there is no SRV
> record for the TS farm name.
>
> Currently Development team is working on two fixes in Windows 7 (next
> version of Windows). First fix is to allow negotiate in WMI and then fix
> the
> TS web client to use negotiate when making a WMI call.
>
> Once the fix is checked into Windows 7, our Sustained Engineering team
> will
> analyze the fix and see if it can be safely back ported to Windows 2008.
>
> Please let me know if you have any questions
>
> Thanks and Regards,
> name removed
> Windows 2000/XP/2003/Vista Escalation Engineer"
>
>
>
> "Jeff Pitsch" wrote:
>
>> So your saying that all that beta testing was for nothing and this
>> feature
>> just completely does not work? I'll have to let the companies know who
>> have
>> it working that they dont' actually have it working :)
>>
>> sorry, just having fun. Blanket statements like this on a big feature
>> like
>> this are typically incorrect, just fyi.
>>
>> Jeff Pitsch
>> Microsoft MVP - Terminal Services
>>
>>
>> <Don> wrote in message news:2008711102830dokoni@microsoft.com...
>> > It is currently NOT possible to configure TS Web Access to point to a
>> > farm
>> > though documentation says it is.
>> >
>> > This is because kerberos is used for non-local authentication instead
>> > of
>> > NTLM.
>> >
>> >

>>
>>
>>
 
Re: Publicating a TS Farm in TS Web Access 2008

Rob, sorry to say but you are wrong. If you would like the SR# to research it
internally, i will be more than happy to provide it.

You cannot point TSWeb Access web part to a farm tp populate The RemoteApp
page. You get an Event ID 3 (security-kerberose) and an 10009 (DCOM) error.

"Rob Leitman [MS]" wrote:

> You can point TS Web Access to a farm member name and this will get you most
> of the benefits, as long as you set the farm name in RemoteApp Manager.
>
> The only thing this doesn't get you is high availability, if the individual
> TS you entered goes down.
>
> Rob
>
> "gabriel miller" <gabrielmiller@discussions.microsoft.com> wrote in message
> news:E27C1978-B411-4A34-845F-25A8DE7AC4ED@microsoft.com...
> > Actually Don is 100% correct. I opened a case w/ Microsoft and here is the
> > status. In summary this configuration will not work as documemted.
> >
> > "Gabriel,
> >
> > Our Windows Sustained Engineering and Development team are still working
> > on
> > this issue. When we use farm name in TS Web Client Configuration page, TS
> > web client makes a WMI call to the Terminal Server. To authenticate the
> > server the TS Web client uses Kerberos which will fail as there is no SRV
> > record for the TS farm name.
> >
> > Currently Development team is working on two fixes in Windows 7 (next
> > version of Windows). First fix is to allow negotiate in WMI and then fix
> > the
> > TS web client to use negotiate when making a WMI call.
> >
> > Once the fix is checked into Windows 7, our Sustained Engineering team
> > will
> > analyze the fix and see if it can be safely back ported to Windows 2008.
> >
> > Please let me know if you have any questions
> >
> > Thanks and Regards,
> > name removed
> > Windows 2000/XP/2003/Vista Escalation Engineer"
> >
> >
> >
> > "Jeff Pitsch" wrote:
> >
> >> So your saying that all that beta testing was for nothing and this
> >> feature
> >> just completely does not work? I'll have to let the companies know who
> >> have
> >> it working that they dont' actually have it working :)
> >>
> >> sorry, just having fun. Blanket statements like this on a big feature
> >> like
> >> this are typically incorrect, just fyi.
> >>
> >> Jeff Pitsch
> >> Microsoft MVP - Terminal Services
> >>
> >>
> >> <Don> wrote in message news:2008711102830dokoni@microsoft.com...
> >> > It is currently NOT possible to configure TS Web Access to point to a
> >> > farm
> >> > though documentation says it is.
> >> >
> >> > This is because kerberos is used for non-local authentication instead
> >> > of
> >> > NTLM.
> >> >
> >> >
> >>
> >>
> >>

>
>
 
Re: Publicating a TS Farm in TS Web Access 2008

Sorry Rob. I miss read your post. Yes, you can point to a single member of a
farm...

"gabriel miller" wrote:

> Rob, sorry to say but you are wrong. If you would like the SR# to research it
> internally, i will be more than happy to provide it.
>
> You cannot point TSWeb Access web part to a farm tp populate The RemoteApp
> page. You get an Event ID 3 (security-kerberose) and an 10009 (DCOM) error.
>
> "Rob Leitman [MS]" wrote:
>
> > You can point TS Web Access to a farm member name and this will get you most
> > of the benefits, as long as you set the farm name in RemoteApp Manager.
> >
> > The only thing this doesn't get you is high availability, if the individual
> > TS you entered goes down.
> >
> > Rob
> >
> > "gabriel miller" <gabrielmiller@discussions.microsoft.com> wrote in message
> > news:E27C1978-B411-4A34-845F-25A8DE7AC4ED@microsoft.com...
> > > Actually Don is 100% correct. I opened a case w/ Microsoft and here is the
> > > status. In summary this configuration will not work as documemted.
> > >
> > > "Gabriel,
> > >
> > > Our Windows Sustained Engineering and Development team are still working
> > > on
> > > this issue. When we use farm name in TS Web Client Configuration page, TS
> > > web client makes a WMI call to the Terminal Server. To authenticate the
> > > server the TS Web client uses Kerberos which will fail as there is no SRV
> > > record for the TS farm name.
> > >
> > > Currently Development team is working on two fixes in Windows 7 (next
> > > version of Windows). First fix is to allow negotiate in WMI and then fix
> > > the
> > > TS web client to use negotiate when making a WMI call.
> > >
> > > Once the fix is checked into Windows 7, our Sustained Engineering team
> > > will
> > > analyze the fix and see if it can be safely back ported to Windows 2008.
> > >
> > > Please let me know if you have any questions
> > >
> > > Thanks and Regards,
> > > name removed
> > > Windows 2000/XP/2003/Vista Escalation Engineer"
> > >
> > >
> > >
> > > "Jeff Pitsch" wrote:
> > >
> > >> So your saying that all that beta testing was for nothing and this
> > >> feature
> > >> just completely does not work? I'll have to let the companies know who
> > >> have
> > >> it working that they dont' actually have it working :)
> > >>
> > >> sorry, just having fun. Blanket statements like this on a big feature
> > >> like
> > >> this are typically incorrect, just fyi.
> > >>
> > >> Jeff Pitsch
> > >> Microsoft MVP - Terminal Services
> > >>
> > >>
> > >> <Don> wrote in message news:2008711102830dokoni@microsoft.com...
> > >> > It is currently NOT possible to configure TS Web Access to point to a
> > >> > farm
> > >> > though documentation says it is.
> > >> >
> > >> > This is because kerberos is used for non-local authentication instead
> > >> > of
> > >> > NTLM.
> > >> >
> > >> >
> > >>
> > >>
> > >>

> >
> >
 
Back
Top