Applying Policies Configured for Windows Mobile Devices in Symantec Mobile Security 7.2

Article:TECH201752  |  Created: 2013-01-17  |  Updated: 2013-01-17  |  Article URL
Article Type
Technical Solution


When a Windows policy is customized and saved in the Symantec Management Console (SMC), the configuration may not be automatically applied to all the managed Symantec Mobile Security 7.2 (SMS 7.2) clients running Windows Mobile.  The devices are able to communicate with this management server and their logs are correctly received, but policy changes (configuring the Windows Mobile clients to retrieve their AntiVirus content updates from an internal LiveUpdate Administrator 2.x server, for example) do not go into effect.



The Mobile Agent indicates that there is a "Healthy Connection" to the Symantec Management Platform (SMP) server, and attempts to Update the policy appear to be successful.  No error is displayed though no policy updates are applied. 



Note: this article applies to Windows Mobile devices only.  SMS 7.2 Android clients are not affected. 



The policy is not applied to a resource group that contains the Windows Mobile devices.  Examining the Targeted Resources section at the bottom of the page shows a count of 0.



In order to be applied, the policy must be associated with the Resource Group that contains the Windows Mobile devices.

Click on Apply To, and create a Filtering Rule that excludes resources not in the Group named "Mobile."  



Save this rule, and then save the policy.  Note that the Count number should now reflect the number of mobiles devices in the organization. 

(This number will also include Android devices, but Android settings will remain unchanged.  The Windows Mobile policies cannot be applied to Androids.)

Article URL

Terms of use for this information are found in Legal Notices