A Windows Management Interface (WMI) policy creates messages
with the message type ForwardToVP.
A flexible management policy forwards messages that have the
message type ForwardToVP.
Another WMI policy forwards ownership changes and
acknowledgements.
Server-based flexible management offers several advantages:
You can keep messages up to date on all management servers by
forwarding more message operations, for example changes of
severity, changes to annotations, and action responses.
The object attribute of the forwarded message remains
unchanged. It is not overwritten with the originating node name, as
is the case with the ForwardToVP-based method.
You can forward messages, message operations, and action
responses to multiple management servers.
The message action server forwards the messages, so the load on
the management server's agent is much smaller.
Server-based flexible management is faster and more reliable,
especially if there is a high load on the management server.
You can forward all types of messages, not just messages of
with the message type ForwardToVP.
If you use ForwardToVP-based message forwarding, you can stay
with that solution or manually migrate to server-based flexible
management. Server-based flexible management is the recommended
message forwarding solution. ForwardToVP-based message forwarding
is only available for backward compatibility.
To migrate from ForwardToVP-based message forwarding to
server-based flexible management
Copy the content of the agent-based flexible management policy
that to forwards all messages of the type ForwardToVP to other
management servers. Use it to create a server-based flexible
management policy.
In the server-based flexible management policy, remove the
SECONDARYMANAGERS section. The section is not needed, because each
management server maintains an internal list of the other
management servers to which it has forwarded each message. The
management server forwards message operations and action responses
to only the management servers in this list.
In the policy, remove the ACTIONALLOWMANAGERS section. The
section is not needed for server-based flexible management.
In the MSGTARGETRULES section, remove the MSGTARGETRULE that
forwards all messages to the source server itself.
In the MSGTARGETRULES section, modify the MSGTARGETRULE that
forwards messages to destination servers. Replace MSGTARGETRULECOND
MSGTYPE "ForwardToVP" with the conditions (if any) from the WMI
policy that creates messages with the message type
ForwardToVP.
The keywords ACKNONLOCALMGR, MSGCONTROLLINGMGR, and NOTIFYMGR
are not supported for server-based flexible management policies. If
your existing policy contains these keywords, remove them.
Remove the WMI policy that creates messages with the message
type ForwardToVP, so that it is no longer deployed to the agent on
the management server.
Remove the agent-based flexible management policy that forwards
messages, so that it is no longer deployed to the agent on the
management server.
Remove the WMI policy that forwards ownership changes and
acknowledgements.
Configure any prerequisites for server-based flexible
management and then deploy the new server-based flexible management
policy to the management server.