Login to participate
Endpoint Management & Virtualization BlogsRSS

Applying SP2 for v7 breaks out-of-band manageability functionality

Terry Cutler's picture
Terry Cutler
August 18th, 2009
Filed under: , ,

Looking to confirm what I'm experiencing.

In working with Altiris 7 (Symantec Management Platform) - I upgraded to SP2 which was released in recent weeks.   This included the hotfix (SP2 HF1) released within the past week.
 

In my environment, I’m running the following versions:
  • Symantec Platform Solutions (SIM) 7.0.420
  • Symantec Management Platform 7.0.5202
  • Altiris Client Management Suite 7.0.9
  • Altiris Client Management Suite Portal Page 7.0.1037
  • Altiris Pluggable Protocol Architecture  7.0.6455
  • Altiris Real-Time System Manager 7.0.1299
  • Altiris Real-Time Console Infrastructure 7.0.1299
  • Altiris Out-of-Band Management 7.0.1213 

The default computer collection is empty after the upgrade  (select "Manage" followed by "Computers").   The computer objects are still in the database and can be accessed via other means – yet the default list is missing.   Newly created computer objects (via Altiris agent) do not appear at first, yet after running a “Resource Membership Update” they will appear.   (Correction: after restarting the system - the previous computer objects suddenly appeared)

When I accessed a Resource Manager page, navigating into the Real-Time System Manager, power-on and redirection functions were disabled.

Was able to fix the redirection via “Amtredirectionservice.exe /Service” - apparently the service got unregistered and needed to be re-registered.  

From a base remote power control perspective, I’m still not getting “power on” option to appear.   Thus if system is off, unable to power-on via Intel vPro\AMT… yet am able to via inventory, AMT event logs, set\clear network filters, etc.  

Attempted a TaskServer based AMT sequence of events (apply filter, power-on, deploy software, remove filter).   TaskServer page generates critical error and points to Altiris log (haven't looked at that yet).   I am able to refresh\access TaskServer jobs previously created, yet attempts to run sequence failed… couldn’t get past first step of applying filter.  Upon rebooting system and retrying - network filter was applied yet status\details did not reflect in subsequent steps didn't happen.   As noted above – applying filter worked via RTSM.

Does this reflect what others might be experiencing?

Any ideas\insights on getting this fixed?  Something similar to the "amtredirection.exe /service" workaround\fix noted above?

+1 (1 vote)