Windows 7 Auto Start / IP Binding

[WoodburyMan]

Steve lists a way to have CumulusMX load without admin privledges on the main page. (Running net sh command as a admin to allow CumulusMX to bind to any local IP on that port).
I had issues with this, it did not work for me unless I manually specified the IP, wildcard using * and + did not work. Not sure why. Rather than binding to specific IP's, which I found another problem with (see 2nd part), I decided to just find a shortcut for launching the program on startup with admin privileges.

I followed this guide to make a task.
http://www.sevenforums.com/tutorials/11 ... reate.html
However in the "Edit Action" field, I had it start the following programs"
Program/Script:

Code: Select all

%windir%\System32\cmd.exe 

Add an argument:

Code: Select all

/c start "CumulusMX" "/c start "CumulusMX" "C:\CumulusMXDist\CumulusMX.exe""

Start In:

Code: Select all

C:\CumulusMXDist

Also, under "Triggers" I had it start at login. I already have my system set to auto login to my user account, so it all works. You can set it to start even if the user isn't logged on I suppose to start anyway.



Now the 2nd part.
It seems CumulusMX decides what IP/Interface to bind to on it's own. For example it bind to my local LAN 10.0.0.87 IP. When I access it in a browser, via http://10.0.0.87:8998/ it loads fine. However, it does not load when I type http://127.0.0.1:8998/ as the URL. This may be a issue for several reasons. Example 1: It may choose the wrong interface on Multi-Interface systems. 2. IP changes. My system boots up faster than the switches I have it plugged into (Cisco SG300). In the event of a power outage, that adapter would show disconnected. In this case, Cumulus binds to 127.0.0.1, and is inaccessible remotely from my LAN IP.
A possible Fix would be a setting perhaps to tell it what IP's to bind to. A list, perhaps where you specify the IP's, ex. 127.0.0.1, 10.0.0.87, and a "all" and "auto" setting somewhere in the config file. Just me $.02.

[gluepack]

Well, everything was working fine until I ran the netsh and setup the logon task, as described above, which all seemed to go well (I used my user name instead of u$er).
Then I logged off and logged on but CumulusMX didn't start, which was obvious from my website not being updated and also the timeout error when attempting to access it through the browser.
Now, having started it manually, I am getting a 503, service unavailable, in the browser when attempting to access it.

One thing I am not quite clear on. I have three other systems on the network and they are all accessible from each other but I can't access the cumulus server 192.1.etc. through a browser from any of them, just the local system. I must be missing something. It seems as if it should be the same as other servers, e.g. FTP. I have set up and my webcam so not sure about it.

Never mind, it's late, I'll have a look in the morning. I've started it manually and I just hope that the system doesn't restart during the night.

Oh, perhaps it did start. I just checked Task Scheduler and it shows as running and started at 21.47 and my manual start was at 21.56. Strange.

[gluepack]

ok, with everything resolved as far as local access is concerned, as far as auto start is concerned, until I can improve on it, I have an Admin Command Prompt and TeamViewer starting at login so at least, if I am away and the system restarts, I can use TeamViewer to run MX. It also enables me to see the MX control panel on the server, wherever I am, without having to worry about how I access the MX server remotely.

Update: Duh! Better still, along with TeamViewer, I have an Admin batch file to start at login that runs MX.
I guess I could also start my browser with the server IP address at login as well, to save having to do that with TeamViewer, when I want to see it remotely.

Update: That requires a response to the admin request, so I have setup a shortcut of a runas.../savecred to run the batch file that, in turn, invokes CumulusMX.
So, havng set up Administrator with a password, the shortcut, that gets run at login, is...
runas /user:system\Administrator /savecred "C:\CumulusMX\CumulusMX.bat"
...where system is the server system name
(you have to run it once, in order for the password to be requested and saved)
...and the bat file cd's to CumulusMX and runs CumulusMX.exe
(I did try running the exe from the runas but it fails)

[empezza]

I am trying to get CumulusMX to auto start when the PC boots up - running Windows 8.1.
I've tried all sorts of combinations as suggested above but nothing works.
Does anyone have the full details of how to set this up? Please post details for dummies!

I have Cumulus running on a "headless" PC - no monitor/mouse/keyboard - unless needed. No password at boot.

[gluepack]

OK, well five systems, only one went via 8.1 so I don't remember everything. They are now all on 10, except the Cumulus machine, which is on 7 Pro. So, forgive me if it isn't exactly like this...

I assume by "no password at boot" that you mean it automatically logs in to Win 8.1.

Well, it depends whether you are automatically logging on as Administrator or as someone who has Administrator privileges.
If the former, you only need to setup a batch file to run at startup. If the latter, you need the additional step of setting up a shortcut and run that at startup instead of the batch file.
The batch file will be something like this...

Code: Select all

echo off
cd\CumulusMX
CumulusMX.exe

...obviously changing the cd... command to specify the directory where you have installed CumulusMX.

The shortcut will be to...

Code: Select all

runas /user:system\Administrator /savecred "C:\CumulusMX\CumulusMX.bat"

So, you create a batch file, using Notepad, copy the above block of code into it, change the directory name if necessary and save it as, for example, CumulusMX.bat
Save it somewhere appropriate.
Then, if you are automatically logging in as Administrator (not just Fred with Administrator privileges), using File Explorer, copy it to the Startup folder which should be at Windows/Start Menu/Programs/Startup by dragging it there from wherever you saved it.

If you are not logging on as Administrator, first you have to ensure that Administrator has a password and that you know what it is.
Then, having created the batch file, as above, on the desktop, right-click and create a new shortcut adding the above "runas" statement as the location, changing the piece in quotes to the location of your batch file.
Open File Explorer, navigate to the Startup folder, as above, and drag your shortcut to it.
When it runs the first time, it will ask for the password. After that it should run without doing so.

[empezza]

Thank you so much for your detailed reply!
I login as Administrator (the only user) and creating the batch file as you described works perfectly.

Cheers,
Max

[ajcm]

Hello:

I woluld like know how I can open cumulus MX with StartWatch and Windows 10. StartWatch says that It can´t open Cumulus.exe

I use StartWatch and this opens Virtualvp and weather display, cumulus, etc.

Thanks.

[gluepack]

Have you spoken to SoftWx, connecting to weather software is their business. Hopefully they know how to accomplish this.

[mcrossley]

The exe filename is no longer Cumulus.exe it is CumulusMX.exe, do you have to change it StartWatch?

[ajcm]

If I have changed.

[laulau]

Is the requirement to run (CumuluMX) as root/administrator removed ?

[ajcm]

I've tried this:

runas / user: administrator "CumulursMX C: \ CumulusMX \ CumulusMX.exe"

It does not work and do not know the commands of Windows 10.

Thanks.

[ajcm]

StartWatch can not open programs as Administrator on Windows 10, CumulusMX opens in normal mode but does not work the socket localhost: 8998.

Thanks.

[jdc]

I may be missing something here but I run MX on a 'headless' Acer Revo on Win10 accessed by Team Viewer. On startup I log on automatically with Admin priviledges and have put a shortcut to CumulusMX in:

C:\Users\'Username'\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup

This works fine for me. Ironically whilst typing this we had a power cut and the Acer with Cumulus was the first back up.

[steve]

StartWatch can not open programs as Administrator on Windows 10, CumulusMX opens in normal mode but does not work the socket localhost: 8998.

Then as laulau suggested, try removing the requirement to run as administrator (as in the instructions).