johnran's community posts

This occured again when we updated our computers with windows update the update number was KB5011831
It was pretty big and after doing the update the host on all the machines failed to start up again, Luckaly we used the fix thats re-started the host every hour if not running..
Just a heads up which update did it this time.. It was for windows 10 machines..

Same here it had to be a manual start, that’s why this fix were using in the task scheduler is working so well..

Same thing here, Ive uninstalled and reinstalled in the past,   .. it made no difference,... I never deleted the key though. If i see it happen I will again but for now the fix that we are using i might not even notice if it does go offline because it would restart..

I know when my hosts went out, rebooting them would not start them up either, I had to physically click on the start host tab to get it to work. I beileve others must be having a similar problem, I doubt its just two of us.

The workaround Matthew came up with seems to be working very well so far...

Matthew Cooper wrote:

...I just re-read your post and realised you are not using the script. I am unsure if there will be any effect of running the start command when the service is already running. Probably not, but I guess you will know for sure after it runs for a few days.

Matthew, Thanks so much for all this help, this been going on for a while and at least now we might have a soultion. Thanks again for all the help.. I will try to update here in the future if it continues to work out..

I just created the task in the task scheduler  to run every hour gave it the highest privileges and then exported the task to the other computers and added it so they are all the same.. seems to work very well as a workaround to make sure it always runs..

there must be an error in your script because I added it as you said and they do  show it he task manager but fail to work. What I did instead was to just create a task to start the Host every hour to insure that it is working and that works.. Great Idea you had, not sure why the script isnt working but hay it gave me a idea that helped.  I just hope that the triggering to start the host does not create a problem if its already running?

This is Very awsome of you to do and appreciate it BUT when I run the install I get my antivirus blocking it saying its a Adware install virus.. Im sure it it not but Im not sure why it is doing this?

I just added it in a folder and ran it as admin, testing it out right now will leave update after litttle while..thanks

Matthew Cooper wrote:

I too am interested in the outcome here.

We have been forced to run dual remote access applications on all systems to account for when RU does not start the host. It is very frequent in my case, and it is not limited only to reboots after a windows update. Regular reboots where no updates take place [Such as on Server 2008 R2 machines] result in this behavior too.

We have a little shy of 500 hosts in our network, so it is common for us to not realise that a host has not started right after a reboot.

It seems that RU needs a watchdog service that can restart the host if it is not running. Although it is another moving part, maybe a simple service of this type would be able to keep the host online.

Matthew

That is exactly what is happening us too.. you are 100% correct , it needs a watchdog to insure it is running...You said it perfect..