Endpoint Protection

 View Only
  • 1.  Import centralized exceptions on unmanaged sep clients

    Posted Mar 14, 2011 03:20 PM

    Hy I need to import centralized exceptions on various unmanaged sep.

    How do I do?

    Thanks



  • 2.  RE: Import centralized exceptions on unmanaged sep clients

    Posted Mar 14, 2011 03:28 PM

    you have symantec endpoint protection manager installed?

    if yes then create the necessary centralized exception , export this policy with unmanged package and then install it

    or eles

    create 1 CEPolicy on one client, export it and import the policy.xml file.

    https://www-secure.symantec.com/connect/forums/manually-alter-policies-managedunmanaged-computer#comment-3214121



  • 3.  RE: Import centralized exceptions on unmanaged sep clients

    Posted Mar 15, 2011 10:05 AM

    First I have only no managed clients.

    Second, I have already done but nothing occur.

    The steps were: I create CE on sep, then export to a policy.xml file and import on a new sep installation!!

    Any idea?



  • 4.  RE: Import centralized exceptions on unmanaged sep clients

    Posted Mar 15, 2011 10:12 AM

    u can install a manager on any machine, use it to create CE and export the client package as unmanaged clients and then install. then remove manager,

    which exporting check all the policies like Liveupdate allow  users to liveudpate ,schedule, CE,etc.

    once exported u can then unisntall it.



  • 5.  RE: Import centralized exceptions on unmanaged sep clients

    Trusted Advisor
    Posted Mar 15, 2011 10:19 AM

    Hello,

    Question: Are you trying to Import the Centralized Exception Policy created in the SEPM and want the same to be imported to Unmanaged Clients?

    Solution

    Steps to export a policy:
     

    1. Logon to the Symantec Endpoint Protection Manager console.
    2. In the left hand pane, click Policies.
    3. On the Policies page, under View Policies, click the <type of policy> that you want to export. (e.g. LiveUpdate)
    4. On the <type of policy> Policies page in the right hand pane, click the policy that you want to export. (e.g. LiveUpdate Settings policy)
    5. On the same page, under Tasks, click Export the Policy.
    6. In the Export Policy dialog box, locate the folder where you want to export the policy file to, and then click the Export button.


    Steps to import policy on the Managed Client:
     

    1. Logon to the Symantec Endpoint Protection Manager console.
    2. In the left hand pane, click Policies.
    3. On the Policies page, under View Policies, click the <type of policy> that you want to import (e.g. LiveUpdate).
    4. On the same page, under Tasks, click Import a <type of policy> Policy.
    5. In the Import Policy dialog box, browse to the policy file that you want to import (policy files are .dat format), and then click the Import button.

    Steps to import policy on the UnManaged Client:

    1) Open your unmanged clients interface
    2) Click on help and trouble shooting
    3) Click on troubleshooting
    4) Under the policy profile click on import
    5) This will ask for .dat file, select the one you exported in the management console as per the symantec document.
     



  • 6.  RE: Import centralized exceptions on unmanaged sep clients

    Posted Mar 15, 2011 01:50 PM

    Hy, when I exported the Centralized Exception Policy the extension of output file is .DAT

    But when I want to import on sep unmanaged  clients the import process ask me for an .XML file and then nothing occur...

    What can be happening?

    Thanks



  • 7.  RE: Import centralized exceptions on unmanaged sep clients

    Posted Mar 15, 2011 02:02 PM

    when u export it will be ce.dat

    rename to .zip

    extract it

    u wil find one xml file

    try replacing that..



  • 8.  RE: Import centralized exceptions on unmanaged sep clients
    Best Answer

    Trusted Advisor
    Posted Mar 15, 2011 02:03 PM

    Hello,

    I agree with Rafeeq as well.

    OH! Here is what you need to Do.

     

    How to manually apply a group policy from the Symantec Endpoint Protection Manager (SEPM) to an Symantec Endpoint Protection (SEP) client?

    Solution


    To manually apply a policy from the Symantec Endpoint Protection Manager to a client, follow the steps below:

    1. First determine which policy file you would like to apply.
    2. Login to the Symantec Endpoint Protection Manager and click Clients.
    3. Click the group who's policy you would like to apply.
    4. Click the Details tab.
    5. Take note of the alpha-numeric code at the beginning of the Policy Serial Number (For example 553E-12/18/2025 14:01:36 474)
    6. Navigate to the outbound policy folder on the Manager, the default location is:
      C:\Program Files\Symantec\Symantec Endpoint Protection Manager\data\outbox\agent\
    7. Go to the file folder that starts with the same alpha numeric code as the policy you would like to apply (For example 553E862D0A003D2F019FD541B9A58BE3).
    8. Copy the "LSProfile.xml" file in this folder to the desired client.
    9. Open the Symantec Endpoint Protection Client interface
    10. Click Help and Support > Troubleshooting > Import.
    11. Navigate to the "LSProfile.xml" file copied above. Click the LSProfile.xml, then click Open.


    The Policy serial number listed should change to match the one seen in step 2.

    * This will change the Group reported in the Symantec Endpoint Protection Client interface to match the Group related to this policy.
    However, the client will still heartbeat to the group specified in the "Sylink.xml."
    Once the heartbeat is complete the group and the policy used will change to reflect the one specified by the "Sylink.xml."



  • 9.  RE: Import centralized exceptions on unmanaged sep clients

    Posted Mar 15, 2011 03:41 PM

    Lamentably, any way is succesful to me

    I also probed to do the following on one unmanaged client.

    First:

        - Add manually one Centralized Exception about folder on client. Then I ran smc -exportconfig c:\testeo.xml

    Second

         -Remove the manual entry on centralized Exception. Restart the server and the I ran smc -importconfig c:\testeo.xml to renew the first configuration but any change is applied.