Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1056
  • Last Modified:

RemoteApp Server 2008 R2

Hello,

When we deploy RemoteApp in Server 2008 R2. Upon clicking on the app:

1) Is the application opened using port 80/443  or still uses 3389?
2) Is there anyway to just move RemoteApp data on 80/443 and block 3389?
3) Is there a way to disable RDP and only enable RemoteApp. My understanding of RemoteApp is that it still uses RDP to open the Apps, but not exactly sure..

Thanks
0
masdf123
Asked:
masdf123
3 Solutions
 
rhinocerosCommented:
0
 
jjjosefCommented:
Have a look at the article published on Expert-Exchange itself

It might be helpful for You

Expert Exchange Article

For your Third Query follow the bellow procedure
      
Go to the RDP properties in Terminal Services Configuration Console
In environment tab, select the option "Start the following program when the user....”
Path: c:\windows\system32\logoff.exe
 Start in: c:\windows\system32
0
 
masdf123Author Commented:
Can someone please answer my questions specifically?
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
Rob WilliamsCommented:
I think a general answer, will answer all 3 questions.
If you enable the TS Gateway service, when you connect to the server you use only port 443 to access the server.  You are authenticated, and then the TS Gateway server uses port 3389 internally to connect to the Terminal Server (now called Remote Desktop Services (RDS)  server, which can be but does not need to be the same server.  In this case external access to port 3389 is not needed at all, no router/firewall opening or port forwarding for port 3389 is required.  Port 3389 is only needed internally, but is needed.  Without the TS Gateway service port 3389 is required externally.  RDP is always needed, even with RemotApps, as it is the protocol/service used for accessing and communicating with the server or PC to which you are connecting.  It is possible to change the the RDP listening port to something other than 3389.

These days due to a virus that spreads via RDP and port 3389, the TS Gateway service, which uses SSL, should always be used instead of direct connections using 3389.
0
 
SteveCommented:
1) Is the application opened using port 80/443  or still uses 3389?

3389

2) Is there anyway to just move RemoteApp data on 80/443 and block 3389?

Kindof. You can set RDP port to anything you like but you will find issues if it conflicts with another used port, like 443. This doesnt change how it connects, it just changes the port number.
You should try the Web Access feature of Remoteapp, as that uses port 443 (https) and may do what you want.


3) Is there a way to disable RDP and only enable RemoteApp. My understanding of RemoteApp is that it still uses RDP to open the Apps, but not exactly sure..

Again, it's a yes & no. You can use remote web apps and block port 3389 completely, or just set the TS to log users straight off if they log in directly (using login script or group policy etc.)
0
 
Rob WilliamsCommented:
As mentioned, if TS Gateway is used there is no need for 3389 or any other redirected port. Handshaking and Internet to server RDP traffic all uses SSL/443.
0

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now