You don't need a special command for policies because any policy change will be transferred anyway--either nearly immediately (push mode) or after the next heartbeat interval (pull mode). That applies to console commands, too.

See this enlightening thread:

https://www-secure.symantec.com/connect/forums/sepm-console-and-client-communication

Hi,

We can give the policy update from the console..select the client or group and if you click update na the policy will gets immediately updated

Policy does not immediately update when using Client > Run Command on Computer, if communication mode is Pull.

This will only be the action is communication mode is Push.

And it will not in fact, be immediate. It can take from several seconds to over a minute for SEPM to send the command to check in, after which the client policy will update.

This is true for any action available from the Run Command on Computer menu.

With communication mode set to Pull, and the default 5 minute heartbeat interval, the policy will get updated within 5 minutes of being changed. So this may not be a great concern.

However, this is not so useful for customers with larger client deployments which require an extended heartbeat interval of 1 hour or more.

Regards,

JC

An option to force policy updates would be good. In an ideal world, policy changes go out like was mentioned above. However, we don't live in a perfect world, so the ability to force a policy update would be great.

Thanks for your suggestion.  We will consider this for a future release.

Sooner rather than later would be good. I moved a computer into another group yesterday, and as of this morning, that computer still hasn't updated its policy - at least in SEPM it hasn't. So in my view, this is a critical change that needs to happen soon. Someone is going to have to make a deskside visit now because the policy hasn't updated, and I can't push it from the console.