sultanofsin's dashboard

sultanofsin replied on September 22, 2008 15:54 to the question "How to wait for 5... 4... 3... 2... 1... seconds?" in Bozteck:

Steve, you rock! Thanks.

sultanofsin marked one of Steve Bostedor's replies in Bozteck as useful. Steve Bostedor replied to the question "How to wait for 5... 4... 3... 2... 1... seconds?".

sultanofsin asked a question in Bozteck on September 20, 2008 01:02:

How to wait for 5... 4... 3... 2... 1... seconds?

Hey Boz, quick question... What is the command or tool that you use in your scripts to "wait for 5... 4... 3... 2... 1... seconds" and then continue? For example, it shows up in the VNC Scan script right after starting/stopping vnc services when you push or remove UVNC to/from a client. I've been looking for something like this forever. I hope you'll share that with me. Thanks.

sultanofsin replied on July 25, 2008 19:16 to the question "Remote scripting problems" in Bozteck:

Poopdog, that is a good solution and it will probably work. However, as I mentioned before, your domain admin password is sent unencrypted over the network in plain text. This is not an option. At a command prompt, type psexec /? Then read the second-to-last paragraph.

I do thank you for the suggestion of using psexec though. I have found a few other uses that make my job a little easier.

sultanofsin replied on July 24, 2008 19:18 to the question "RDP settings don't allow direct RDP login." in Bozteck:

None of the Global RDP settings are overridden at a lower level (I already checked that just in case). However, the problem may lie in the "Always prompt for password setting" This is checked and greyed out. So this may be the problem. It has probably been set through group poilicy. Bummer. But that doesn't explain how this works when we use RoyalTS. Hmmm...

On a second point, is it possible to force the /console (/admin) switch when connecting via RDP through VENM? Thanks.

sultanofsin replied on July 24, 2008 19:06 to the question "Remote scripting problems" in Bozteck:

Instead of having the client connect to the remote share, I wrote a script that copies the file (on the share) directly to that client PC (from MY PC). It then executes the file on the client. That then creates new files in a specific folder on the client. The script then copies the data back to the server. All of this works though MY credentials from MY computer. Thus, the direct connection by the client to the server is eliminated.

More simply:

Computer A copies file to computer B. Computer B executes file (psexec). Files (exported by the executable) are then copied to Server C (from computer A). So Computer B and Server C no longer communicate directly.

Again, this was pretty complex. This solution will most certainly NOT work in other scenarios. The executable just happened to be coded conveniently to make this possible in accordance with our needs and I was able to take advantage of it with the batch script. Sorry, but this really doesn't solve the original problem.

sultanofsin replied on July 24, 2008 18:47 to the question "Remote scripting problems" in Bozteck:

Understood. I've also tried that unsuccessfully. Additionally, that requires manual adjustment on 500+ computers. I have created a script that works around this problem the HARD way. It took a week to code and I was VERY lucky that the executable was cooperative, but it works. Hopefully someone will come up with a solution (better workaround) before I need to tackle a similar task. Again, thanks for your help.

sultanofsin replied on July 24, 2008 18:40 to the question "RDP settings don't allow direct RDP login." in Bozteck:

Unless I missed the setting you're refering to, this "Automatic Login" feature you mentioned provides for only one user. I'm not the only user connecting to this server. I was under the impression that VENM console will log me in with the credentials specified in the global settings. Is this not the case? I know there are other programs that do this (RoyalTS) without this "Automatic Login" feature you mentioned. Am I missing something?

sultanofsin replied on July 24, 2008 18:25 to the question "Remote scripting problems" in Bozteck:

yes, thank you. However, passwords are thus sent over the network in clear text. Can't have that. Thanks for the extra effort.

sultanofsin asked a question in Bozteck on July 24, 2008 18:18:

RDP settings don't allow direct RDP login.

In the global options screen, under terminal Services (RDP), I have my domain account specified under the "Login Settings" area. However, when I log onto any 2003 server machines, I am still presented with the log on dialog box on the remote server. Is this setting supposed to allow me to log directly into the RDP session, or just allow me to connect to the computer? If the former, this doesn't seem to work correctly. Please clarify. Thanks.

I tried searching for an answer, but this new format has me a little confused on how to search as well.

sultanofsin replied on June 21, 2008 04:04 to the question "Remote scripting problems" in Bozteck:

I just typed out a nice long explanation of what I'm trying to do. When I clicked on "Post Reply", got page not found. Back button took me back to a blank reply page, Dammit!

So here's the long story short:

I'm on computer A. I'm trying to run a script on Computer B. The script executes a file from a share on Server C. (The file cannot be copied and executed from Computer B. It must be run from the share on Server C)

See the problem? The local system account on Computer B has no credentials on Server C or the Domain. Thus, every attempt results in access denied.

The script is simple:

start \\server\file.exe

I'll try using a batch file with the runas command on monday, but I doubt it will work. Anyone got any other suggestions? Thanks.

sultanofsin replied on June 20, 2008 23:32 to the question "Remote scripting problems" in Bozteck:

Thanks P00PDOG, and thanks again Steve. However, both scripting methods seem to be using the System account so they will not execute files over the network. This is helpful for other things though.

sultanofsin marked one of Steve Bostedor's replies in Bozteck as useful. Steve Bostedor replied to the question "Remote scripting problems".

sultanofsin replied on June 20, 2008 00:10 to the question "Remote scripting problems" in Bozteck:

Thanks for the reply. That is a great explanation and that info helps quite a bit.

"The script runs under the context of the local system account and that account doesn't have access to the network."

I think that explains just about every problem I was having. I can't wait for a workaround for that limitation.

I also tried running a script that copies over a batch file and runs the command from the batch file. That didn't work either. This must still be under the controll of the local system account. In my case, the executable cannot be copied to the remote machine. It must be run from the network location. I may be able to work around this, but I'd still need the remote computer to access the network resources so I doubt it will work.

P.S.- I just recommended VNCScan to my class at school. Hopefully, you'll get a few new clients soon. I love your program and your online support. Keep it up!

sultanofsin replied on June 19, 2008 20:33 to the question "Remote scripting problems" in Bozteck:

Sorry, I forgot to mention that I'm using ver 6.11.218

sultanofsin asked a question in Bozteck on June 19, 2008 20:27:

Remote scripting problems

Why don't most remote scripts work? I want to run a command on the remote machine. I type it into the remote script field, save the script, and run the script on a computer through VNCScan. Nothing. Black CMD window pops up and goes away. Nothing happened. Some scripts work (e.g. the shutdown command), others do nothing. What am I doing wrong?

I want to tell the remote computer to run an executable on the network. It works flawlessly if it is typed into the "Run" dialog box, or from a command prompt. No matter what I try, it will nut run through VNCScan's Remote script tool.