- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi, we use the newest Powershell Module for IntelvPro (SDK has 3.2.6, module has 3.2.2) and new systems with AMT Firmware 11.8.55 and above.
When i set an alarm clock via the set-amtalarmclock Method it always overwrites existing alarm clocks. According to the Source file the script should support multiple alarm clock timers.
With MeshCommander in wsman browser I can see that the powershell module writes the alarm clock to "AMT_AlarmClockService" while MeshCommander writes to "IPS_AlarmClockOccurrence" and can set multiple.
Is there a way to set multiple alarm clock timers via Powershell, either via the module or using a WsmanConnection object?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
There is a bug in the powershell module. The local AMT version is compared using string comparison which results in version "11" being less than "8" and therefore the old approach is used which allows only one alarm clock timer.
Find and replace
if($temp[0] -lt "8")
with
if ([int]($temp[0]) -lt 8)
in the ps1 files of the module. Of course this will void the signature and you cannot use it as a module anymore. But you can import the files as includes in your scripts and set/clear/get the new types of alarm clocks.
Hopefully a next version will fix the error.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Sergio
Set-AMTAlarmClock always overwrites the existing alarm clock timer. Even if I use different names. That's why I was asking the question of how else to do it with PowerShell. Can you create multiple alarms with this commandlet?
I looked at the Intel Managability Commander but it doesn't seem helpful to script creating alarm clocks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
There is a bug in the powershell module. The local AMT version is compared using string comparison which results in version "11" being less than "8" and therefore the old approach is used which allows only one alarm clock timer.
Find and replace
if($temp[0] -lt "8")
with
if ([int]($temp[0]) -lt 8)
in the ps1 files of the module. Of course this will void the signature and you cannot use it as a module anymore. But you can import the files as includes in your scripts and set/clear/get the new types of alarm clocks.
Hopefully a next version will fix the error.

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page