WHS Configuration issues (UPS and autoshutdowns)

WHS Configuration issues (UPS and autoshutdowns)

This question is answered
  • Hello all, I have been reading along all the posts and great information here. I have finally managed to get my custom built server done and have WHS up and running with many of the great add ons listed here. I'm at the point of wanting to start adding drives as well as data to the server but I have hit a major stumbling block that has prevented me from getting any farther. I've spent what seems like over a week now trying to figure it out. My issue that I'm having has to do with only having one UPS available for both the WHS server as well as my main computer. I want to be able to have both the server and pc on the UPS and both have them shutdown in a tidy fashion if the power drops.

    I understand the problem presented here is that the UPS can only signal one of the two, either the server or the PC. So logic tells me to hook it up to the server and then have the server tell the PC to shutdown when the server goes onto the battery backup. This all makes sense.

    My issue is that I have tried numerous different solutions for this with no luck. I am running the Grid Junction add-in and have read all the information in those couple of threads about how to enable the admin account in Win7 and allow WMI through the firewall as well as setting up the script. However I could not seem to make it work. Then I found an article-

    http://alexpummer.com/?p=463

    I tried this and set it up according to the steps listed. Unfortunately I ran into the exact same issue. I was lucky enough to get to chat with Alex Plummer and he told me that his method no longer worked because of some changes that Microsoft made as far as security goes with the new updates for WHS. He said he was pretty sure that is why the Grid Junction method had some of the same issues because it relied on the same scripting method to work as his own method.

    So at this point I am at an roadblock.  I do not want to put my data on the WHS server and configure everything while leaving open what I would consider to be a opening for data loss due to a power failure. My concern is that in the event the power were to drop at the time of a backup of my PC or during an automated backup using the WHS database backup add-in that I would lose data. I'm not sure of what happens when the WHS server shuts itself down. I don't know how it handles backups in progress and how it cancels and stops these backups midstream in the event in needs to shutdown. In my head the logical order in the event of power failure would be-

    Power fails

    Server and PC switch to battery power

    Server sends signal to PC to shutdown (somewhere in this process existing file transfers/backups have to stopped)

    Server shuts itself down

    Thats it!

     

    My issue is I have not figured out how to make this happen. I don't think the Autoexit add-in can do this and I seem to be unable to get the Grid Junction add-in to do it. Trying to use the power options on the server itself do not work as far as scripting goes so I really am stuck. I have seen from reading that maybe Alex Kent is working on something for this to try and solve this issue. I'm not sure what direction to go at this point. I have my shiny new server sitting there and a lot of data I want to get on it so I can set it up and let it automatically do what I intended it for but I'm struggling on this one.

    Any ideas, comments or otherwise would be greatly appreciated. I consider myself capable enough to usually pull off handling most issues or at least googling around to find answers but this one has stumped me.

     

    Info-

    WHS Homebuilt PP3

    Windows 7 Ultimate Main Computer

    Netgear WNDR3700 Router

    (Not sure what other info would help, can add whatever is needed though)

     

    Thanks!

     

Verified Answer
  • I have send you a PM with the download link. The Grid Junction Client is experimental but hopes to simplify the remote shutdown of clients from within the Grid Junction WHS add-in.

    The Grid Junction Client consists out of three main components:

    1. The GridJunctionClient which needs to be installed on any client PC (Windows XP, Windows Vista, Windows 7 etc) you wish to shutdown remotely. During installation it will attempt to auto-configure the Windows firewall - if you are using a different firewall such as McAfee or Norton etc please manually open TCP port 12345.
    2. The ShutdownClient.exe this executable must be copied to the WHS system partition not any UNC network path. For example c:\ShutdownClient.exe is OK but \\server\software\ShutdownClient.exe will not work correctly.
    3. The Grid Junction custom action script:

      Set objShell = WScript.CreateObject("WScript.Shell") 
      objShell.Run "c:\ShutdownClient.exe 10.0.0.10" 

      Note: 10.0.0.10 represents the IP address of the remote system you wish to shutdown and c:\ShutdownClient.exe represents tha path to the exe configured in step 2 on the WHS system.

    Microsoft MVP - Windows Home Server

    • Top 10 Contributor
    • Male
All Replies
  • Glancing at the link and the Alex Plummer method: Grid Junction does not piggyback on those services – in fact the native power options are disabled by GJ in an effort to avoid some potential issues.

    That being said the actual UPS and power management methodologies are not related to the client shutdown, instead the client shutdown issue(s) usually resolve around (a) transmitting shutdown instructions to the client and (b) permissions to shutdown the client

    One can use various technologies to communicate with a remote client (DCOM/RPC, WMI) and jump through hoops on the client (b) by creating/enabling admin accounts, assigning rights, mending the WMI and opening ports and more.

    To try and make it easier we’ve developed a quick helper tool. Here’s a video screencast of the Grid Junction Shutdown Client helper app

    It’s in Windows XP but works just fine in Windows 7 too. We’ve wrapped it into an MSI installer which *should* automatically configure the Windows firewall to allow the GJ helper exe and necessary ports to open- at the Grid Junction Software on the WHS side one merely sends a single line command with the IP address of the client to shutdown. The Grid Junction Shutdown Client helper application is still in beta and said to have helped a number of individuals who had issues with WMI and batch files.

    Let me know if you want to give it a spin to see if it helps.

    Microsoft MVP - Windows Home Server

    • Top 10 Contributor
    • Male
  • Hi Alexander,

    Thanks for the follow up and great info. I'm still trying to wrap my head around some of this stuff and don't seem to have a good enough understanding of it yet. I'm so thankful there are people like you out there willing to help.

    I'm definitely interested in trying the shutdown helper app that is currently in beta. Let me know what I need to do or how to get my hands on it and I will for sure give it a try and offer whatever feedback might be helpful for you with the beta.

    Thanks a lot!

    Mike

    • Top 100 Contributor
  • I have send you a PM with the download link. The Grid Junction Client is experimental but hopes to simplify the remote shutdown of clients from within the Grid Junction WHS add-in.

    The Grid Junction Client consists out of three main components:

    1. The GridJunctionClient which needs to be installed on any client PC (Windows XP, Windows Vista, Windows 7 etc) you wish to shutdown remotely. During installation it will attempt to auto-configure the Windows firewall - if you are using a different firewall such as McAfee or Norton etc please manually open TCP port 12345.
    2. The ShutdownClient.exe this executable must be copied to the WHS system partition not any UNC network path. For example c:\ShutdownClient.exe is OK but \\server\software\ShutdownClient.exe will not work correctly.
    3. The Grid Junction custom action script:

      Set objShell = WScript.CreateObject("WScript.Shell") 
      objShell.Run "c:\ShutdownClient.exe 10.0.0.10" 

      Note: 10.0.0.10 represents the IP address of the remote system you wish to shutdown and c:\ShutdownClient.exe represents tha path to the exe configured in step 2 on the WHS system.

    Microsoft MVP - Windows Home Server

    • Top 10 Contributor
    • Male
  • Awesome!

    I'm going to get on installing per your directions and I will let you know how it goes.  

    Thanks again for the help!

    Mike

    • Top 100 Contributor
  • It worked!

    I followed the instructions just as written and then went through and opened up port 12345 on Comodo firewall. After that I ran the test script and it worked perfectly.

    So then I went for a real life test and unplugged the UPS with both the server and main computer running. Everything went flawlessly and both the server and main pc shutdown in sequence in an orderly fashion.

    I can't thank you enough for all the help and the great application.

    Just let me know if there are any details or info about my setup or experience that you would like or that might help with the beta testing and I would be glad to help.

     

    Thanks again!

    Mike

    • Top 100 Contributor
  • Thanks I am happy to hear it.
     
    Would you be interested in helping test and beta out additional WHS related software and solutions?

    Microsoft MVP - Windows Home Server

    • Top 10 Contributor
    • Male
  • Sure, I would be glad to help test and offer feedback on other WHS related software and solutions. Just let me know what you may need I will be glad to help.

    Thanks

    Mike

    • Top 100 Contributor
  • How can I get a copy of the Grid Junction Shutdown Dlient helper app?

    Fred

    • Not Ranked
  • Please add me to the list...this would be a great addition to the software. I have a number of PC's sharing a UPS so it would be great to get them shutdown.

    Thanks

    Darren

    • Top 200 Contributor
  • Could I also get a hold of the Client sw?

     

    Thanks.

    • Top 500 Contributor
  • PM with download link sent. Thanks

    Microsoft MVP - Windows Home Server

    • Top 10 Contributor
    • Male
  • Thanks.  I've tried a few different installs and configs, but can't get this to work.  When I try to test the script, I keep getting the message, "The system cannot find the file specified".

    My script: (note: I changed the file it references from the above instructions as the program name is actually listed wrong... was that a test? :)   )

    Set objShell = WScript.CreateObject("WScript.Shell")

    objShell.Run "C:\GridJunctionClient\ClientShutdown.exe 192.168.1.8"

    WHS Specs:

    HP ex485, WHS2003

    APC ES750

    PC Specs:

    Dell, Win 7 Pro

    • Top 500 Contributor
  • I'm not sure if I can help at all. I know Alex is great at helping and helped me a ton getting my issue sorted out.

    I looked at the script that I have on my WHS that is based on the same thing and here is what I have-

    Set objShell = WScript.CreateObject("WScript.Shell") 
    objShell.Run "c:\ClientShutdown.exe 192.168.1.2"

    Seems slightly different then what you have in that the GridJunctionClient part is missing from my script. I'm not sure if that is by design though or new as opposed to what I have. The script I copied and pasted seems to work great for me. I guess you could try it out and see what happens.

    I'm sure Alex will pop in too and offer some help or guidance since at best I'm just a noob. lol

    • Top 100 Contributor
Page 1 of 1 (14 items)