Me and my colleague found an incredibly weird behavior on ESXi, while experimenting with APC PowerChute Network Shutdown and this neat little script – If you want to do a scripted shutdown of a free version of ESX(i), try it out.
Once you initiate the host shutdown through SSH or SOAP API, it won’t shutdown or suspend virtual machines unless they are in “Automatic Startup” list. Ticking the “Allow virtual machines to start and stop automatically with the system.” and adjusting the shutdown delay is not enough. Machines you want shut down when the host is sent the shutdown command need to be part of automatic startup list, ordered or not.
Later, I looked through ESXi documentation and found this to be working as intended, machines that are in “Manual Startup” list can’t be automatically shut down. I think this is unnecessary limitation, that could have been easily avoided.
We do actually have VM’s that are not required to auto start, but still want them to have a graceful shutdown in case of power failure. It would be nice if VMware redesigned this feature…
My company is using Microsoft Exchange 2010 SP1, there we have a few mailboxes that have permanent out of office assistant set for the purpose of informing people that their message has been received and that we’ll process it ASAP. And that’s fulfilling its purpose, but at some point we realized that the notification is sent only once to each email sender. It doesn’t matter how much time has passed between two sent emails, you would always get out of office reply only for the first message.
This is actually all by design, hard-coded, without the possibility to change or modify this behavior. The Microsoft’s intended purpose for OOF is to notify senders that the recipient is out of office, usually on vacation for some period of time. For that objective, usually there is no need for auto reply with OOF info to be sent out more than once. But for our intents and purposes, this will not do. Those accounts have permanent Auto Reply, and we want our server to respond more than once.
But not too often 🙂 Microsoft left out the possibility to modify OOF settings out of the box for a good reason. If an email server would respond with OOF each time it received an email on that particular mailbox, it could be really easy to either purposely or not cause an email loop. Two mail servers would bounce (auto reply) emails until one of them dies or reaches the mailbox limit. Hence, you should be really careful when meddling with OOF auto reply.
One way I found to make OOF respond more than once is to reset the Auto Reply configuration. Basically, disable it, and enable it right away. The OOF will be sent to each sender again on the first email, at least until the configuration is changed again.
So, one would schedule a PowerShell script to disable/enable OOF on speciefic mailboxes that fit aforementioned intent. Do not reset OOF too often, set the scheduler for an interval of one day at least.
set-MailboxAutoReplyConfiguration -id user.name -AutoReplyState Disabled
set-MailboxAutoReplyConfiguration -id user.name -AutoReplyState Enabled