|
|
|
Question : Remote desktop
|
|
Hello! to all Expert,
I am running at work a windows server 2003 entreprise with 120 users. I am trying to configurate Remote desktop/ terminal services on my techsupport computer running windows XP pro, so I can logon to any computer on the network and be able to observe the users action for security purpose. I try to install and configure it but I was unsuccessful, I looked up many ressources for help, however, each of them say something different.
Please, I need help. Is anybody can lead me through that process step by step.
I also have some windows 2000 pro machine as well.
Thank you in advance.
Tye.
|
Answer : Remote desktop
|
|
A better option (as your using 2003 server) is to install RCONAD on the domain.
Rcontrolad.exe: Active Directory Remote Control Add-On
Active Directory Remote Control Add-On (RControlAD) is a tool that opens a Remote Desktop connection from Active Directory MMC snap-ins to computers running Windows 2003 Server or Windows XP Professional. A connection can also be opened to a Terminal Server running on Windows 2003 Server or Windows 2000 Server. RControlAD makes it easier for administrators to remotely administer servers.
File Required
Rcontrolad.exe
Files included in the 2K3 Resource Kit
http://www.microsoft.com/downloads/details.aspx?FamilyID=9d467a69-57ff-4ae7-96ee-b18c4790cffd&DisplayLang=en
Download and run rktools.exe then extract it to a folder.
http://www.microsoft.com/downloads/details.aspx?FamilyID=0a91d2e7-7594-4abb-8239-7a7eca6a6cb1&DisplayLang=en
HOw to deploy it (this is a five minute job :)
Active Directory Remote Control Add-On (RControlAD) is a tool that opens a Remote Desktop connection from Active Directory MMC snap-ins to computers running Windows 2003 Server or Windows XP Professional. A connection can also be opened to a Terminal Server running on Windows 2003 Server or Windows 2000 Server. RControlAD makes it easier for administrators to remotely administer servers
http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/techref/en-us/Default.asp?url=/Resources/Documentation/windowsserv/2003/all/techref/en-us/rcontrolad.asp
once its installed run adminpak.msi on the client PC to install the active directory users and computers snap in on your tech support PC, copy the file you need locally to the system32 directory
Now your only problem will be if your clients have XP SP2 installed and the firewall is on - as we/I dont believe in hard work turn it off through group policy
Disable XP SP2 Firewall through Group Policy
1. Open Active directory users and computers.
2. Right click the domain name and select properties (note you can also apply this .policy on an OU if you wish).
3. Select the Group policy tab.
4. Select either the default domain policy (of the policy you wish to edit).
5. Click Edit.
6. Navigate to Computer Configuration\Administrative Templates\Network\Network Connections\Windows Firewall.
Note Im only concerned with the domain profile here If you have mobile users you can configure different settings for the domain and standard (not on the domain) settings.
7. Select Domain Profile.
8. Set the policies as follows,
Windows Firewall: Protect all network connections set to disabled
Note this is all you need to do however if you have users that Fiddle you might want to configure a few more (note you can navigate through all the settings using the Next Setting buttons
Windows Firewall: Do not allow exceptions not configured
Windows Firewall: Define program exceptions not configured
Windows Firewall: Allow local program exceptions not configured
Windows Firewall: Allow remote administration exception enabled (put in your entire subnet i.e 172.16.0.0/16)
Windows Firewall: Allow file and printer sharing exception enabled (put in your entire subnet i.e 172.16.0.0/16)
Windows Firewall: Allow ICMP exceptions not configured
Windows Firewall: Allow Remote Desktop exception enabled (put in your entire subnet i.e 172.16.0.0/16)
Windows Firewall: Allow UPnP framework exception enabled (put in your entire subnet i.e 172.16.0.0/16)
Windows Firewall: Prohibit notifications enabled (notifications cause calls to IT :)
Windows Firewall: Allow logging - disabled
Windows Firewall: Prohibit unicast response to multicast or broadcast requests - disabled
Windows Firewall: Define port exceptions not configured
Windows Firewall: Allow local port exceptions not configured
NOTE give this some time to propagate round the network (NOTE start > run > gpupdate will enforce it immediately on an XP client if you want to test it)
Once thats done all you need to do on your tech support PC is launch AD users and computers, open the computers OU and right click the
PC you want to control and select remote control.
--------------------------------------------------------------------------------
If all thats too much hassle use Dameware (you get a Looooong trial if you want to try it out and its cheap as chips anyway :)
I've trialed A LOT of remote control software and to be honest this beats everything, you don't need
to install anything on the "Target" PC (if its 2K or XP)
Mini Remote Control
www.dameware.com/
------------------------------------------------------------------------------
heres some more options
Remote Control
To Remote Control another PC/Server over a network you need some dedicated software
The most popular (because its free) is VNC (Virtual Network Computing) you can download it here
http://www.uk.research.att.com/vnc/ or Consider http://www.tightvnc.com/
Shareware
RemoteControl from DataSet http://www.dataset.fr/eng/rc.html
HueyPC From GID Software http://www.grassheap.com/software.php?ID=2405
Commercial Software
PC Anywhere http://www.symantec.com/pcanywhere/
NetOP From CrossTec http://www.crossteccorp.com/
RADMIN from Sunbelt http://www.sunbelt-software.com/product.cfm?id=470 (cheap on small networks)
NOTE: If you intend to remotely control a Windows 2000 server use Terminal Services (add it as a
windows component and select remote ADMINISTRATION MODE) This gives you up to 2 concurrent connections
On your client install adminpak.msi from the W2K server disk. This RARELY works for Win XP, to fix
download this patch.
http://www.microsoft.com/downloads/details.aspx?familyid=6E5DA79C-5C38-4445-B039-E3F3AA5E5B25&displaylang=en
If your using Windows XP consider "Remote assistance"
http://www.microsoft.com/windowsxp/pro/techinfo/deployment/remoteguide/default.asp
http://www.microsoft.com/windowsxp/pro/using/howto/gethelp/remoteassist/default.asp
If you need to connect to XP using OLDER operating systems look here
http://www.microsoft.com/windowsxp/pro/downloads/rdclientdl.asp
Windows Netmeeting supports "remote desktop sharing"
http://www.microsoft.com/windows/NetMeeting/Features/RDS/default.ASP
Bear in mind if you need to go through a router at home, you will need to enable port forwarding.
Or If you are going through a firewall you may need to open some ports, see the product documentation
for more details.
ADD Right click remote control to Active directory users and computers snap-in
http://www.microsoft.com/downloads/details.aspx?FamilyID=0a91d2e7-7594-4abb-8239-7a7eca6a6cb1&DisplayLang=en
Of course if you lucky enough to have Novell you can use ZenWorks for Desktops as well!
|
|
|
|
|
|
|
