Modify Host Firmware Policies http://developer.cisco.com/c/message_boards/find_category?p_l_id=2049005&mbCategoryId=0 2013-06-20T12:05:59Z 2013-06-20T12:05:59Z Sean McCune http://developer.cisco.com/c/message_boards/find_message?p_l_id=2049005&messageId=3988138 2011-06-02T01:59:07Z 2011-06-02T01:59:07Z

Awesome! Figured it might be something that would leverage the profile to quickly apply to package and then unassociate. I'll get to work trying to modify this as necessary to our environment but excellent foundation to build on. Thanks guys!

Sean McCune 2011-06-02T01:59:07Z Sean McCune http://developer.cisco.com/c/message_boards/find_message?p_l_id=2049005&messageId=3988133 2011-06-02T01:56:19Z 2011-06-02T01:56:19Z

Great to hear! My SCOM guru is anxiously awaiting this. It is one of our last blind spots in our environment.

Sean McCune 2011-06-02T01:56:19Z Sean McCune http://developer.cisco.com/c/message_boards/find_message?p_l_id=2049005&messageId=3987624 2011-06-01T20:12:51Z 2011-06-01T20:12:51Z

Hey Kevin, Normally, we would push the firmware updates through a host package when the profile is created and associated with a blade. We have been doing it this way for a year now. The catalyst for the change is that we have an open TAC case regarding a critical thermal fault on one of our chassis. This chassis is populated with B200 M1 blades but none of them are associated with profiles. One of the troubleshooting steps TAC has requested is to match our blade firmware to the rest of the infrastructure (unassociated blades on 1.3.1m; UCSM on 1.4.2b). Doubtful that it will make any difference in the fault but I'm willing to try it. In addition, it might save us a few crucial minutes when we bring up a new profile.

Sean McCune 2011-06-01T20:12:51Z Sean McCune http://developer.cisco.com/c/message_boards/find_message?p_l_id=2049005&messageId=3987525 2011-06-01T19:41:16Z 2011-06-01T19:41:16Z

Any news or updates on the pending release of the new SCOM management pack?  We currenly have a TAC case regarding the v1.2 release that has been open since January in Bug/Defect Required status.  This is related to the targeting of systems in the management pack and the lack of robust documentation around the product.

Sean McCune 2011-06-01T19:41:16Z Sean McCune http://developer.cisco.com/c/message_boards/find_message?p_l_id=2049005&messageId=3987503 2011-06-01T19:35:37Z 2011-06-01T19:35:37Z

Hey Josh!  Great to see the Powershell cmdlets evolve and its nice to have a space to post questions to the community regarding Microsoft-specific products and environments.   First off, is there a set command to modify firmware policies to apply firmware updates to a subset of servers or profiles via Powershell?  Also, a way to update and activate firmware on blades that are not associated with profiles.   This is one of the more time-consuming tasks through the GUI and it would be great to get it automated.

Sean McCune 2011-06-01T19:35:37Z