• State Not Answered
  • Locked Locked
  • Replies 11 replies
  • Subscribers 28 subscribers
  • Views 11337 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Another Shut down a Core post

Emte
over 7 years ago

Is this even a topic of discussion in the product for any version? This has been a huge topic of discussion and anger since version 5 came out and zero progress has been made

And now in V6, it seems to be getting WORSE. 

1) It seems like the changes to the repository in v6, cause the checks that runs after a dirty shutdown to take longer (just a guess)

2) The unsupported powershell script that was provided by DELL for v5 does not work for 6 and Support just told me there is no script for 6 and never will be.

3) Long running jobs. With the introduction of cloud archives, exports etc, we are seeing massive jobs that run (and block other jobs like backups but that is another issue) for days, meaning scheduling a restart becomes even harder.

I am not even asking for the Core to be able to cleanly shutdown during an OS shutdown (something that every other application in the world seems to manage) But how is this not a single button(s) on the GUI "Prepare for Shutdown" and "Core has been restarted" (to un-pause jobs)

Or at the very least, a single supported powershell script to perform this basic function?

We have dozens of Cores in various geographic locations and managing simple shutdowns is such a massive problem for us.

Parents
  • 0 over 7 years ago
    We all know what the powershell approach is. I mentioned the issues with powershell in my original post. So when you respond with powershell as the answer, it makes me worry that no one at Quest is listening to our feedback or understands what our issues are

    - This post is from 2014 ... and nothing has changed.

    en.community.dell.com/.../

    - Powershell is un-supported. So your suggested method to power down your product is to use unsupported commands and scripting.

    - You want every single customer to build their own script to power down your product.

    - When a change is made that breaks our script, you want every one of us individually to spend our time to fix the script that powers down your product.

    - Just look at the amount of work above. Name one other product that takes this much individual work, all on the customers shoulders to build and manage, to simply power down.

    - Look at the debacle with Windows 2012 and the "hidden" windows key to shut down the OS. The process to shut down Windows was a bit harder but no where near this and yet MS changed it after the feedback in the next release, R2.

    - "The issue with shutting down a core graciously arouse from the jobs that are running at that time"

    I know what the issue is, but why is this our problem? Why cant you guys write some code that handles shutting down your product. Pause jobs, wait till jobs are done and then send a message to the terminal that the Core is ready.

    Lastly, I would like to say that the fact we are still talking about basic things like a supported method to reliably and easily power down your product takes away time and energy that we could use to talk about real issues with the product.
Reply
  • 0 over 7 years ago
    We all know what the powershell approach is. I mentioned the issues with powershell in my original post. So when you respond with powershell as the answer, it makes me worry that no one at Quest is listening to our feedback or understands what our issues are

    - This post is from 2014 ... and nothing has changed.

    en.community.dell.com/.../

    - Powershell is un-supported. So your suggested method to power down your product is to use unsupported commands and scripting.

    - You want every single customer to build their own script to power down your product.

    - When a change is made that breaks our script, you want every one of us individually to spend our time to fix the script that powers down your product.

    - Just look at the amount of work above. Name one other product that takes this much individual work, all on the customers shoulders to build and manage, to simply power down.

    - Look at the debacle with Windows 2012 and the "hidden" windows key to shut down the OS. The process to shut down Windows was a bit harder but no where near this and yet MS changed it after the feedback in the next release, R2.

    - "The issue with shutting down a core graciously arouse from the jobs that are running at that time"

    I know what the issue is, but why is this our problem? Why cant you guys write some code that handles shutting down your product. Pause jobs, wait till jobs are done and then send a message to the terminal that the Core is ready.

    Lastly, I would like to say that the fact we are still talking about basic things like a supported method to reliably and easily power down your product takes away time and energy that we could use to talk about real issues with the product.
Children
No Data