Christopher Greer's community posts

That works Thanks!

In the help file it is confusing since only NAME and PASSWORD specify you can use a : .

Is there any other parameters that use : ?

Also... I have another problem...

If The Name specified already exists in the viewer program and the Internet ID has changed I would assume the Viewer would overwrite the Internet ID or IP if I specify it with the /HOST parameter.  But it does not.  It just tries to open it with the previous ID/IP.  

I can get around this by creating a new name... but then I am left with a junk profile left behind that I would manually need to delete.

Is there some way possible for me to use a parameter to delete the old profile?  Or a way to force an overwrite of the old profile?

Thanks again!

I'm trying to use the Viewer Command Line to launch a batch file with the Internet ID... but I can't figure out how to do it.

Can you give me an example?

I want to start with nothing in my viewer. I want to have it automatically create the name and launch the viewer with the Internet ID.

I tried:

/name:123-456-789 /FULLCONTROL /CREATE /HOST

But it is not working.  I thought this would create the name 123-456-789 and connect to 123-456-789. But it does not ins ert the Internet ID in to the profile.

I created an Agent.exe and I input Username / Passwords for Tech logins.  So I don't have a need for the customer to read a password to us.  We just need them to give us the ID.  Is there a way to remove the password box under the ID?  I'd feel better with it removed... since I think it would be a security issue if someone walks by their computer and uses the ID and password to log in.  So if the password box is hidden I have nothing to worry about. ;)  

Thanks!!  RU is awesome software!!

I'm currently creating my own internet portal for Remote Tech Support at my company that utilizes RU. :)  Kind of like  [censored] has.

I understand that it is for one time use.  But sometimes a restart is needed during one time use.  It would be a pain to install remote service on someone's computer when doing a virus cleanup and having to remember to uninstall it once the cleanup is finished.  Not that it would be difficult to do... but sometimes it can be easily forgotten.  Then the customer is stuck with a remote access tool being left behind.  Not that it should be a big deal either... but what if later the customers computer is acting up and they blame the previous tech saying they had remote access and could have messed with their computer.  I personally like the idea of the Agent.

The Agent does show the option to restart the computer. But it does not work the way I figured it would.  I am able to initiate the restart into normal mode or safemode. But then I am not able to get back onto the system to finish unless I call my customer and ask them to re-launch the agent. Again... not a big deal... but it would be much easier to do if it were built in. ;)

Either way... your software is great!!   :D

It would also be nice if there was an option to select a specific amount of restarts that the Agent would autolaunch.  For instance... If I am running some scripts that will end up restarting the computer automatically it would be great if I could input 2 auto launch restarts into the options.  Then no matter what I could get access later if the computer restarted.

Just a recommendation of a feature you could possibly add that gives us something different than other remote access utilities. ;)

If I try to Remote Restart the Agent software it fails because the Agent does not auto launch during boot up.  I am thinking for this to work properly either the Agent would need to be run as a service for the next boot... so that the Agent will be running at boot up and not need a user to log in.  Or we would need the ability to input a verified windows user/pass and the Agent would need to be put in the RunOnce section of the registry (with autologon credentials).  This way the computer would auto login and launch the Agent software.

An added benefit would be if the viewer would continue to attempt to reconnect periodically until it can.

Is this possible from the Agent already and I am skipping a step?

I was testing this feature by remotely connecting to a Windows 2008 R2 server.