Ability to set machine Boot Order

Comments

5 comments

  • Avatar
    Peter Franks

    Thanks Brian, interesting idea.  

    How are they not working correctly and what do you do to get them back in order?  Is it a networking / configuration issue that's out of place?  The first thing that jumps to mind is checking to make sure your snapshots are current but looking at your environment it seems that they are.  

    0
    Comment actions Permalink
  • Avatar
    Peter Franks

    Hi Brian, 

    A couple quick little tweaks to try: 

    • Decrease the RAM & disk allocation of the machine you need to start first and increase the RAM & disk of the ones you want to start later.  As we need to ship those resources to you, the VM with the fewer resources will resume the fastest.  

    • If there is a specific service that is starting that is starting too quickly on either a client or server machine, you can delay that service from starting.  Here's a quick guide.  

    0
    Comment actions Permalink
  • Avatar
    Brian Mehlman

    Scott,

    As far as I can tell - it is my domain controller that is causing issues. It really needs to be brought up before other machines connect to the domain. My company develops software that relies heavily on active directory and if the domain controller is not ready to service AD requests then the rest of our system fails. I believe if I can put a fixed delay between the starting of the DC and the other servers that the issues should (I hope) go away. Right now to remedy I reboot the DC, wait about 10 minutes then reboot the rest of the machines in my environment. Unfortunately this takes me close to 45 minutes to setup for any demo. I'm not quite sure exactly what happens when I resume an existing VM, although I am told that folks that use VMware to setup demo environments for our software see a similar issue.

    I think the delays would have to occur at either (1) reboot time of each server or (2) resume time of each server.

    0
    Comment actions Permalink
  • Avatar
    Peter Franks

    Hi Brian, 

    A 45 minute up and running time is definitely not something we want you to be going through.  

    I noticed your ADDC has a lot of RAM allocated to it.  Is that required for your company's software?  If not, I would definitely suggest dropping this down to 1GB (maybe even lower!) and you should see it resume well before the other VMs in your environment.  Have a look at our blog post on a recent update to the granularity of RAM allocation for extra details.  

    Our thinking is, as an Active Directory box does not need to do much, might as well limit its resources and put them to better use elsewhere.  

    Thanks! 

    0
    Comment actions Permalink
  • Avatar
    Brian Lalancette

    Brian, you should be able to configure a startup delay yourself for the VMs you want to start later, using the "Time to display list of operating systems" option in Control Panel --> System --> Advanced System Settings --> Startup and Recovery --> Settings (see attached). That way your VMs would sit waiting at the boot OS selection screen until the given timeout expired.

    Not sure if this would require you to actually have alternate boot OS settings configured, but this would be easy enough to set up anyhow - just make a dummy copy of the existing OS boot entry using BCDEdit.exe.

    Might be worth a try,

    (another) Brian

    0
    Comment actions Permalink

Please sign in to leave a comment.