/build/static/layout/Breadcrumb_cap_w.png

Run Now script - Shutdown - Powering off Windows Server 2008 VM's

I have a script that essentially does a prompt asking the user if they want to power off their machine. If they don't do anything, it will auto-power off after 5 minutes. A simple batch file - nothing fancy. We use this for winter breaks, holiday weeks, etc., since we have over 4,000 desktops in our environment and we want to save power.

However, today I noticed all of my VM servers with the KACE agent on them were down. They are Server 2003 and Server 2008 R2 VM's. The script is only set to deploy to select OS - XP, Windows 7. Server isn't selected on them, yet they went down. It shows them under the "successful", so it pushed the script out to them when it shouldn't have.

KACE shows the OS correctly. Any ideas?

 

OS Name: Microsoft Windows Server 2008 R2 Standard x64

0 Comments   [ + ] Show comments

Answers (1)

Posted by: dugullett 12 years ago
Red Belt
0

Is your script checking the OS, or do you have smart labels checking it?


Comments:
  • I told it to deploy to labels - which are basically subnets (10.17.X.X is a label, say "Franklin School). I tell it to deploy to Franklin School, which is any machine on 10.17.X.X IP scheme. However, the script is supposed to only run on XP SP3, Windows 7 Pro x86, and Windows 7 Pro x64. But it seems to have run on the Windows Server VM's as well.

    Am I doing this wrong? I thought that regardless of what label I deploy it to, the script should follow the OS restrictions. - sfigg 12 years ago
    • I would think that would work, but never tested it. I have smart labels for my servers to avoid something like that. Sorry I couldn't be more help. - dugullett 12 years ago
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ