![]() In the event that an older SEPM is managing a newer client, new client features will not be configurable from the SEPM, the client will not be able to take advantage of newer features or policy options and the SEPM may be unable to deliver definition content to the clients. In the event that an older client is managed by a newer SEPM, the client will only adhere to policy features that the client has. (For 14.3 RU5 and newer, see: SEP client builds and SEPM compatibility.) Managing newer SEP clients with an older SEPM release, however, is not. It is supported to have newer SEPMs managing older SEP clients. ![]() However, maintaining a consistent release version across all SEPMs in an organization is not a requirement for support. SEP Infrastructure Functionality with Different Releases For specific information on upgrading to the latest release, please see Upgrading and Migrating to the Latest Release of Symantec Endpoint Protection (SEP). This ensures that management components and endpoints can take advantage of the most recent enhancements and improvements, addresses potential vulnerabilities and fixes noted defects. Per best practice, all SEPMs and SEP clients in an organization should be upgraded to the latest available software release as soon as it becomes available. Best Practice Calls for the Latest Version ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |