Storage Informer
Storage Informer

BKM for optimising SMS Addon operations – how would you like 100% success rates?

by on Sep.03, 2009, under Storage

BKM for optimising SMS Addon operations – how would you like 100% success rates?

For those of you out there that areĀ  using the SMS Addon the following might be of interest, if seeing close to 100% success rates is your thing…

If you&aposve been using the SMS Addon together with Microsoft SMS as your vPro enabled management console of choice then you might have experienced less than 100% success rates when you&aposre trying to perform AMT operations on collections of machines. The following details I will be providing have been devised specifically in the context of using the AMT wake-up feature for a Power Management Use Case, however you can extrapolate the essence and apply elsewhere if you&aposre using some of the other features in the SMS Addon…Ok enough of an introduction.If you&aposre implementing the power management use case, then before you&aposll be using the AMT wake-up feature, you&aposll be putting machines to sleep according to a certain policy you&aposve put together (user initiated, SMS job executed shutdown.exe or some other shutdown scripts). However, you want to be sure that the machines you have put to sleep can be woken up on demand – mandatory advertisement triggered wake-up, scheduled wake-up or console initiated wake-up. Finding out you can&apost wake some machines up that you&aposve put to sleep is far from being ideal – effectively you&aposre reducing the success rate of your use case and you&aposre putting machines in a state where you&aposre benefiting from power savings, but you&aposve compromised on your ability to get access to that machine from remote.What might interest you then is a deterministic way to ensure that every machine you put to sleep as part of your power management use case, you can wake up. Well… we&aposve done just that.Here is the trick – you create your SMS collection for machines that you want to put to sleep and then wake-up, with a simple SQL statement of:&apos Select * where iAMTStatus = 1&aposiAMTStatus = 1 which is a return value that confirms the SMS Addon can communicate successfully with the vPro machine. Therefore you now have a deterministic way of knowing that a machine that you&aposve put to sleep can be woken up using SMS Addon and the AMT wake-up feature. An improvement on that is to run an AMT discovery daily (or some other frequency) to dynamically update the collection based on the ability of the SMS Addon to get to machines successfully. This will cater for if there are any changes in your environment, which there might or might not be. Currently the only way to run an AMT Discovery repeatedly on machines that have already been discovered in the past is to manually right click on a collection in the SMS Console and select AMT Discovery. We might have a more automated way of doing this soon… so watch this space.Hopefully you find this useful.- a caveat/disclaimer I should perhaps mention is that his method does not mean you will have 100% success rate for ALL your machines. Undoubtedly you will have some machines that do not have iAMTStatus = 1. Effectively what you&aposre doing here is defining the scope.

URL: http://feedproxy.google.com/~r/IntelBlogs/~3/GMBo9p6WgbE/bkm-for-optimising-sms-addon-operations–how-would-you-like-100-success-rates

:, , , , ,

Leave a Reply

Powered by WP Hashcash

Looking for something?

Use the form below to search the site:

Still not finding what you're looking for? Drop a comment on a post or contact us so we can take care of it!

Visit our friends!

A few highly recommended friends...