Endpoint Protection

 View Only
  • 1.  SEPM - install unmanaged client problem

    Posted Nov 12, 2009 08:48 AM
    After upgrade SEPM to RU5, when I install client using console and find unmanaged client SEPM scripts instead of copy files to C:\Temp folder, it create on C drive Temp file (wihtout extension) includes contents of all files, that are ususally in C:\Temp\CLi-inst folder! This is a SEPM RU5 bug?


  • 2.  RE: SEPM - install unmanaged client problem

    Posted Nov 12, 2009 09:01 AM
    on which OS you are trying to push?


  • 3.  RE: SEPM - install unmanaged client problem

    Posted Nov 12, 2009 09:01 AM
    on which OS you are trying to push?


  • 4.  RE: SEPM - install unmanaged client problem

    Posted Nov 12, 2009 09:01 AM
    on which OS you are trying to push?


  • 5.  RE: SEPM - install unmanaged client problem

    Posted Nov 12, 2009 09:22 AM
    SEPM on Windows Server 2003 and clients are on XP. I must add, that this happen on comupter where SEP is already installed but not managed (i have problem with upgrade from MR4 to RU5 and now client cannot conect to SEPM  - I added old domain etc but it didnt work, and I used psexec and sylinkdrop etc)


  • 6.  RE: SEPM - install unmanaged client problem

    Posted Nov 12, 2009 09:30 AM
    can you try replacing the sylink file. see if that works.

    How to change a Symantec Endpoint Protection client from unmanaged to managed in MR1 and MR2.


    http://service1.symantec.com/support/ent-security.nsf/docid/2007082009543848


  • 7.  RE: SEPM - install unmanaged client problem



  • 8.  RE: SEPM - install unmanaged client problem

    Posted Nov 13, 2009 02:02 AM
    I do it using psexec and it work, but when I using SEPM and finding unmanaged computers and at the same time I want  upgrade client to newest version this happen I  wrote in first comment. At this time I'm using SEPM to find unmanaged computer with installed SEP11 older version, and using psexec scripts I'm changing client from unmanaged to managed.


  • 9.  RE: SEPM - install unmanaged client problem

    Posted Nov 13, 2009 02:15 AM
    Hi prohol,

    It is a "feature" when you push out client packages from SEPM.  When the package installs, it uses the directory you mentioned. 

    See my idea to get get rid of this.

    https://www-secure.symantec.com/connect/idea/cleanup-after-client-install

     


  • 10.  RE: SEPM - install unmanaged client problem

    Posted Nov 13, 2009 05:41 AM
    thanks all. I use 3 solution from second link writen by sandip_sali using psexec. But my question is, why, when I'm using SEPM find unmanaged computers function, and install new version of SEP on computer with older version of SEP, it create temp file on C: (not folder Temp!) and installation failed? And after this when im using psexec to copy sylinkdrop.exe,sylink.xml and *.bat file (which execute smc -stop etc) to C:\Temp folder on client computer, script failed becouse  there are not c:\temp folder and cannot create Temp folder (couse file temp exist).