No, those hats arent old since much hasn't changed between SMS 2.0 and 2003 for the remote tools.
The Kb article states the same thing that I am firing off in the HTA:
remote.exe 2 <computername> \\smsserver
OR
this is actually faster
remote.exe 2 computername /SMS:noSQL <-- doesn't check the computer or use the SMS SQL Server DB to check information
Here is what happens when you launch either command above
a window pops up of remote.exe. Remote.exe is a collection of tools, when you click the Remote Control button a terminal services connection is established, and launches WUser2.exe on the client end.
Or you can do other tools within remote.exe
Such as:
Reboot the targeted computer Chat with the current logged in user Remote Execute applications, etc. Check system resources etc.
As you can see the purpose of this application is for our QA department to just monitor a user, so there is no need for the other tools. This also would be a security issue.
So I need to initiate the Remote Control application without having the users having access to the other tools