[itsallgoode9]

So I have 6 computers in my network and wondering if there is some way, via command line in windows to start or close a program on a different computer than the one i'm working on?
something roughly like this: Computer 192.168.1.5 run maxwell.exe

I specifically want to do this to make resetting maxwell rendernodes easier. Currently, if a node crashes, or if I have to shut down the entire network, I have to login to each computer via remote desktop and manually start the program. As my renderfarm expands, I'm really dreading the thought of having to manually go into 12 or 18 computers and manually launch programs on each one, so hopefully there is some way to do this!

[feynman]

Yes, our render notworks ;)

I know what you mean. Don't you find Remote Desktop or a KVM switch easy enough? Or what about Teamviewer? If you really like command line style working, then maybe http://technet.microsoft.com/en-us/sysi ... s/bb897553 is for you?

[itsallgoode9]

I currently use teamviewer to do it manually, but it wastes so much time manually doing it...especially if I have a file that's causing issues and causes the rendernodes to hang at merging or something. I ran into this today and had to manually restart the nodes on all six computers, four renders in a row before I figured out what the issue with the file was. I mean, think if you had a renderfarm with 100 computers in it...that would be a nightmare.

So i'd like to basically have a command line script where I could just double click on a desktop icon and it would run through each computer and start the rendernode. So that way, it's a one click solution to start all rendernodes on a network. I'll checkout PsExec, it looks like that could be what i need.

[itsallgoode9]

thanks, looks like this will do the job, although I am having problems setting up the default Admin$ share on my computer. argh.

[Fernando Tella]

It would be great if you could do it right from Maxwell Monitor.

[itsallgoode9]

It would be great if you could do it right from Maxwell Monitor.

Is "Reset Network" actually supposed to close then reopen all the nodes on the network? Because right now all it does is close down all nodes...not sure if it's broken or that's how it's intended.

[simmsimaging]

It would be great if you could do it right from Maxwell Monitor.

+1

[joaomourao]

It would be great if you could do it right from Maxwell Monitor.

+1!

[itsallgoode9]

It would be great if you could do it right from Maxwell Monitor.

+1!

I agree ten thousand percent...but even before this I think we need to figure out the "reset nodes" button...whether it is a "reset" button or a "kill" button regarding nodes. Maybe it has been addressed but for the past couple years, at least for me, it's a "kill" switch for my render nodes. It shuts everything down perfectly but it does not reopen anything...which I assume a "reset" button would close down then open up. It might be a sharing/permissions thing I overlooked but for me it's not working.


On a note about the original question...as sad as it is, remotely opening programs on the network via command line is not as easy as it should be, sadly. As much as I love windows, this is one of many areas where it makes things not easy. Feynman gave a link to a program that DOES work, although you might have to go into registry to make it work. For me it hasn't fully worked...I've been researching this an some people it's worked off the bat and for many people the solutions don't work. It might be a stupid thing i've overlooked but once i figure this out i'll let you know

[Fernando Tella]

but even before this I think we need to figure out the "reset nodes" button...whether it is a "reset" button or a "kill" button regarding nodes. Maybe it has been addressed but for the past couple years, at least for me, it's a "kill" switch for my render nodes. It shuts everything down perfectly but it does not reopen anything...which I assume a "reset" button would close down then open up. It might be a sharing/permissions thing I overlooked but for me it's not working.

That's what it does here too.

[numerobis]

I agree ten thousand percent...but even before this I think we need to figure out the "reset nodes" button...whether it is a "reset" button or a "kill" button regarding nodes. Maybe it has been addressed but for the past couple years, at least for me, it's a "kill" switch for my render nodes. It shuts everything down perfectly but it does not reopen anything...which I assume a "reset" button would close down then open up.

yes, it would be really helpful if the "reset" function would work as expected...

And concerning the remote thing... i'm starting the render node using the windows autostart but i'm always logged in on all network machines using remote desktop, because almost every time i start a job there is at least one (mostly two) nodes that doesn't start immediately.
So the possibility to "reinitialize" a node would be nice.

[Fernando Tella]

What program do you use for remote desktop? Windows'?

[numerobis]

yes the normal windows Remote Desktop.
I startet with UltraVNC, but i think the performance is better now with windows RD.
Sometimes i still have to use VNC because RD doesn't work for the logon screen after a reboot...

I would like to know if linux would be better to control for headless render nodes and if there is a difference in the render time.
I really would like to set up a linux installation optimized for rendering. But i'm a complete noob in linux distributions.
Maybe someone who is already using linux could share his knowlegde how to set up linux for rendering...

[Fernando Tella]

I would like to know if linux would be better to control for headless render nodes and if there is a difference in the render time.
I really would like to set up a linux installation optimized for rendering. But i'm a complete noob in linux distributions.
Maybe someone who is already using linux could share his knowlegde how to set up linux for rendering...

I'm fearing the same jump.

[l1407]

http://www.splashtop.com/home

my be using this