Jump to content

Terminal Services Web Access - Registration


Recommended Posts

Posted

I have obviously done something worng or incompletely, judging by all the

reports of how easy TSWA is to set up. Any help is appreciated...

 

I have a TS Gateway which also is to serve as TSWA front-end. I have a TS

NLB farm of two nodes running 2008 EE TSwhich have an identical list (1

application now, for simplicity/troubleshooting sake) of RemoteApp

Applications. They are set to use the TS GW. The GW is added to the TS Web

Access Computers security group on both nodes of the NLB TS Farm. When I go

to the TSWA Administration pages and try to set the "Terminal Server Name" in

the web part editor zone, I get the following error:

 

"TS Web Access was not able to access the specified terminal server. Verify

that the computer account of the TS Web Access server is added to the TS Web

Access Computers security group on the terminal server."

 

This error is the same if I use the FQDN of the farm or either server or the

individual NetBIOS names of either server. I'm not finding anything terribly

interesting in any logs. COnsidering how easy everyone says this is, I have

to believe I have missed something teribly fundamental. Any takers?

 

Thanks in advance.

--

MCSE, MCSA + Messaging

Guest Munindra Das [MSFT]
Posted

Re: Terminal Services Web Access - Registration

 

I think you do not need to add to the TSWA computer’s security group. Also,

what is the Terminal Services resource authorization policy (TS RAP) in TSG

set to – does it include both the farm machines with their IP addresses

added to the resource groups? Can you allow any resource in the TSG RAP

policy?

 

You can refer to "Make RemoteApp programs available from the Internet"

section of

http://technet2.microsoft.com/windowsserver2008/en/library/61d24255-dad1-4fd2-b4a3-a91a22973def1033.mspx?mfr=true.

 

--

 

Thanks!

 

This posting is provided "AS IS" with no warranties, and confers no rights.

 

"Jay" <Jay@discussions.microsoft.com> wrote in message

news:9832A062-9D79-448C-BC51-D6846DCA046D@microsoft.com...

>I have obviously done something worng or incompletely, judging by all the

> reports of how easy TSWA is to set up. Any help is appreciated...

>

> I have a TS Gateway which also is to serve as TSWA front-end. I have a TS

> NLB farm of two nodes running 2008 EE TSwhich have an identical list (1

> application now, for simplicity/troubleshooting sake) of RemoteApp

> Applications. They are set to use the TS GW. The GW is added to the TS Web

> Access Computers security group on both nodes of the NLB TS Farm. When I

> go

> to the TSWA Administration pages and try to set the "Terminal Server Name"

> in

> the web part editor zone, I get the following error:

>

> "TS Web Access was not able to access the specified terminal server.

> Verify

> that the computer account of the TS Web Access server is added to the TS

> Web

> Access Computers security group on the terminal server."

>

> This error is the same if I use the FQDN of the farm or either server or

> the

> individual NetBIOS names of either server. I'm not finding anything

> terribly

> interesting in any logs. COnsidering how easy everyone says this is, I

> have

> to believe I have missed something teribly fundamental. Any takers?

>

> Thanks in advance.

> --

> MCSE, MCSA + Messaging

Posted

Re: Terminal Services Web Access - Registration

 

Munindra:

 

You misread what I said. What I meant to convey is the TSWA computer account

is added to the "Terminal Services Web Access Computers" security group on

the RemoteApp servers. And you *do* need to add the TSWA Server to the

security group on the RemoteApp servers. See task #4 under "About deploying

RemoteApp programs through TS Web Access" in the document you posted:

 

4. Add the computer account of the TS Web Access server to the TS Web Access

Computers group on the terminal server.

 

The RAP currently is "allow all" (no restriction).

 

Thank you.

 

--

MCSE, MCSA + Messaging

 

 

"Munindra Das [MSFT]" wrote:

> I think you do not need to add to the TSWA computer’s security group. Also,

> what is the Terminal Services resource authorization policy (TS RAP) in TSG

> set to – does it include both the farm machines with their IP addresses

> added to the resource groups? Can you allow any resource in the TSG RAP

> policy?

>

> You can refer to "Make RemoteApp programs available from the Internet"

> section of

> http://technet2.microsoft.com/windowsserver2008/en/library/61d24255-dad1-4fd2-b4a3-a91a22973def1033.mspx?mfr=true.

>

> --

>

> Thanks!

>

> This posting is provided "AS IS" with no warranties, and confers no rights.

>

> "Jay" <Jay@discussions.microsoft.com> wrote in message

> news:9832A062-9D79-448C-BC51-D6846DCA046D@microsoft.com...

> >I have obviously done something worng or incompletely, judging by all the

> > reports of how easy TSWA is to set up. Any help is appreciated...

> >

> > I have a TS Gateway which also is to serve as TSWA front-end. I have a TS

> > NLB farm of two nodes running 2008 EE TSwhich have an identical list (1

> > application now, for simplicity/troubleshooting sake) of RemoteApp

> > Applications. They are set to use the TS GW. The GW is added to the TS Web

> > Access Computers security group on both nodes of the NLB TS Farm. When I

> > go

> > to the TSWA Administration pages and try to set the "Terminal Server Name"

> > in

> > the web part editor zone, I get the following error:

> >

> > "TS Web Access was not able to access the specified terminal server.

> > Verify

> > that the computer account of the TS Web Access server is added to the TS

> > Web

> > Access Computers security group on the terminal server."

> >

> > This error is the same if I use the FQDN of the farm or either server or

> > the

> > individual NetBIOS names of either server. I'm not finding anything

> > terribly

> > interesting in any logs. COnsidering how easy everyone says this is, I

> > have

> > to believe I have missed something teribly fundamental. Any takers?

> >

> > Thanks in advance.

> > --

> > MCSE, MCSA + Messaging

>

>

  • 3 weeks later...
Posted

Re: Terminal Services Web Access - Registration

 

I still can't get this registration to work. Any help?

--

MCSE, MCSA + Messaging

 

 

"Jay" wrote:

> Munindra:

>

> You misread what I said. What I meant to convey is the TSWA computer account

> is added to the "Terminal Services Web Access Computers" security group on

> the RemoteApp servers. And you *do* need to add the TSWA Server to the

> security group on the RemoteApp servers. See task #4 under "About deploying

> RemoteApp programs through TS Web Access" in the document you posted:

>

> 4. Add the computer account of the TS Web Access server to the TS Web Access

> Computers group on the terminal server.

>

> The RAP currently is "allow all" (no restriction).

>

> Thank you.

>

> --

> MCSE, MCSA + Messaging

>

>

> "Munindra Das [MSFT]" wrote:

>

> > I think you do not need to add to the TSWA computer’s security group. Also,

> > what is the Terminal Services resource authorization policy (TS RAP) in TSG

> > set to – does it include both the farm machines with their IP addresses

> > added to the resource groups? Can you allow any resource in the TSG RAP

> > policy?

> >

> > You can refer to "Make RemoteApp programs available from the Internet"

> > section of

> > http://technet2.microsoft.com/windowsserver2008/en/library/61d24255-dad1-4fd2-b4a3-a91a22973def1033.mspx?mfr=true.

> >

> > --

> >

> > Thanks!

> >

> > This posting is provided "AS IS" with no warranties, and confers no rights.

> >

> > "Jay" <Jay@discussions.microsoft.com> wrote in message

> > news:9832A062-9D79-448C-BC51-D6846DCA046D@microsoft.com...

> > >I have obviously done something worng or incompletely, judging by all the

> > > reports of how easy TSWA is to set up. Any help is appreciated...

> > >

> > > I have a TS Gateway which also is to serve as TSWA front-end. I have a TS

> > > NLB farm of two nodes running 2008 EE TSwhich have an identical list (1

> > > application now, for simplicity/troubleshooting sake) of RemoteApp

> > > Applications. They are set to use the TS GW. The GW is added to the TS Web

> > > Access Computers security group on both nodes of the NLB TS Farm. When I

> > > go

> > > to the TSWA Administration pages and try to set the "Terminal Server Name"

> > > in

> > > the web part editor zone, I get the following error:

> > >

> > > "TS Web Access was not able to access the specified terminal server.

> > > Verify

> > > that the computer account of the TS Web Access server is added to the TS

> > > Web

> > > Access Computers security group on the terminal server."

> > >

> > > This error is the same if I use the FQDN of the farm or either server or

> > > the

> > > individual NetBIOS names of either server. I'm not finding anything

> > > terribly

> > > interesting in any logs. COnsidering how easy everyone says this is, I

> > > have

> > > to believe I have missed something teribly fundamental. Any takers?

> > >

> > > Thanks in advance.

> > > --

> > > MCSE, MCSA + Messaging

> >

> >

  • 2 weeks later...
Posted

Re: Terminal Services Web Access - Registration

 

I still have this problem and I'm having trouble figuring out the right place

to look for debug options. I've tried to configure it as simply as possible.

--

MCSE, MCSA + Messaging

 

 

"Munindra Das [MSFT]" wrote:

> I think you do not need to add to the TSWA computer’s security group. Also,

> what is the Terminal Services resource authorization policy (TS RAP) in TSG

> set to – does it include both the farm machines with their IP addresses

> added to the resource groups? Can you allow any resource in the TSG RAP

> policy?

>

> You can refer to "Make RemoteApp programs available from the Internet"

> section of

> http://technet2.microsoft.com/windowsserver2008/en/library/61d24255-dad1-4fd2-b4a3-a91a22973def1033.mspx?mfr=true.

>

> --

>

> Thanks!

>

> This posting is provided "AS IS" with no warranties, and confers no rights.

>

> "Jay" <Jay@discussions.microsoft.com> wrote in message

> news:9832A062-9D79-448C-BC51-D6846DCA046D@microsoft.com...

> >I have obviously done something worng or incompletely, judging by all the

> > reports of how easy TSWA is to set up. Any help is appreciated...

> >

> > I have a TS Gateway which also is to serve as TSWA front-end. I have a TS

> > NLB farm of two nodes running 2008 EE TSwhich have an identical list (1

> > application now, for simplicity/troubleshooting sake) of RemoteApp

> > Applications. They are set to use the TS GW. The GW is added to the TS Web

> > Access Computers security group on both nodes of the NLB TS Farm. When I

> > go

> > to the TSWA Administration pages and try to set the "Terminal Server Name"

> > in

> > the web part editor zone, I get the following error:

> >

> > "TS Web Access was not able to access the specified terminal server.

> > Verify

> > that the computer account of the TS Web Access server is added to the TS

> > Web

> > Access Computers security group on the terminal server."

> >

> > This error is the same if I use the FQDN of the farm or either server or

> > the

> > individual NetBIOS names of either server. I'm not finding anything

> > terribly

> > interesting in any logs. COnsidering how easy everyone says this is, I

> > have

> > to believe I have missed something teribly fundamental. Any takers?

> >

> > Thanks in advance.

> > --

> > MCSE, MCSA + Messaging

>

>

×
×
  • Create New...