allow remote connections for remote desktop

[watts3000]

I'm setting up xp remote desktop for our company. I've
created a group that I've created an ad group that I've
added. Into the local remote desktop users group. The
problem is that I need to enable remote connections Im
trying to do this through group policy. I'm following this
article,
»www.microsoft.com/technet/treeview/def..[?]
url=/technet/prodtechnol/windowsserver2003/proddocs/entserv
er/ts_con_h_new_client_connections.asp
but the setting is not there. I'm in a 2000 server
environment but all workstations are xp pro. To my
knowlege I'm also using the most up to date .adm templates.

 

[mikecel79]

First of all do you want clients to run applications from this machine or are you doing this for remote administration? There's 2 different settings for this. Need to know which one you want to do first.

Edit: After reading your post again. Are you trying to setup all XP machines with RD or a Win2k server?

 

[watts3000]

I'm setting all workstations up with remote desktop.

 

[lowtech1]

RDP - Host setup

RDP - Client setup

RDP client for Win9.x/ME/NT4/2K

RdpClip file copy for terminal server that might work for Win2k client & XP host. - I haven't test it out.

Rdesktop - RDP client for Linux - Unix & Mac also have a version that is a derivative from Rdesktop.

How to change default RDP port (3389) on host computer - You must uses portforward for each host machine.

How to change default RDP port on client computer

RDP default port can be modify in .h file for Rdesktop.

You don't need to have portforward if all clients machine have VPN tunnel with the company network.

Since I have done most of the work for you I should get 1/2 of what you make 😉

 

[lowtech1]

The last post is for setting Windows XP boxes (Host) to be access from a Client box via Remote Desktop.

Setup Windows 2000 Terminal Services Server:

Control Panel > Add/Remove Programs > Add/Remove Windows Components > Terminal Services > Enable Terminal Services > Application Server > (Chose the appropriate permission compatible mode depending on the applications that you are running on the server) > Follow the rest of the Wizard to complete the install for TS Application services.

Control Panel > Add/Remove Programs > Add/Remove Windows Components > Terminal Services Licensing > Application server mode > follow the rest of the Wizard to complete the install for TS Licensing.

Goto the MMC & look for Terminal Services Licensing to install the licenses: Start > Programs > Administrative Tools > Terminal Services Licensing > Chose the appropriate server & right click to install the License (can be activate by the web or phone).

Uses CHANGE USER under the command promt instead of the Add & Remove Programs to install apps on the TS server, because I found Add & Remove Programs isn't stable under TS Server.

CHANGE USER /EXECUTE Enable execute mode (defaut).
CHANGE USER /INSTALL Enable install mode.
CHANGE USER /QUERY Display current settings.

Do not bother with the Client Creator, because it have several bugs in it, uses the better & bug fix RDP client that I provided in the above post.

Make sure that you read upon rights assignment & session control. It would bewise to get a book on Windows 2000 services administration or Terminal Services administration.

Good luck!

 

[watts3000]

Guys I understand all that stuff I'm trying to enable remote desktop through group policy. That way we will not all have to run around the building and enable this stuff by hand. I've posted the original article I was going by before.



To allow remote connections
Open Group Policy.
In Computer Configuration, Administrative Templates, Windows Components, Terminal Services, double-click the Allows users to connect remotely using Terminal Services setting.
Click Enabled, and then click OK.
Important

You should thoroughly test any changes you make to Group Policy settings before applying them to users or computers. For more information on testing policy settings, see Resultant Set of Policy.
Notes

To perform this procedure, you must be a member of the Administrators group on the local computer, or you must have been delegated delegated
An assignment of administrative responsibility to a user, computer, group, or organization.
For Active Directory, an assignment of responsibility that allows users without administrative credentials to complete specific administrative tasks or to manage specific directory objects. Responsibility is assigned through membership in a security group, the Delegation of Control Wizard, or Group Policy settings.

For DNS, an assignment of responsibility for a DNS zone. Delegation occurs when a name server (NS) resource record in a parent zone lists the DNS server that is authoritative for a child zone.
the appropriate authority. If the computer is joined to a domain, members of the Domain Admins group might be able to perform this procedure. As a security best practice, consider using Run as to perform this procedure.
Use the above procedure to configure the local Group Policy object. To change a policy for a domain or an organizational unit, you must log on to the primary domain controller as an Administrator. Then, you must invoke Group Policy through the Active Directory Users and Computers snap-in.

 

[lowtech1]

I'm not that familiar with Group Policy (the only thing that I do in there is create template & change Admin & Guest account name), but you can try editing your DC Group Policy: Right Click your Domain object in Active Directory Users & Computers > Properties > Group Policies > New > Edit > Computer Configuration > User Configuration > and add/edit the appropriate setting that you need.

You might want to read up on the help me guide or get a book on Win2k administration & security. Or, go to MS Technet forums for help.

Good luck!