SEPM - install unmanaged client problem
Updated: 23 May 2010 | 9 comments
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?
discussion Filed Under:
Comments
Hi
on which OS you are trying to push?
Please don't forget to mark your thread solved with whatever answer helped you : ) Rafeeq
Hi
on which OS you are trying to push?
Please don't forget to mark your thread solved with whatever answer helped you : ) Rafeeq
Hi
on which OS you are trying to push?
Please don't forget to mark your thread solved with whatever answer helped you : ) Rafeeq
SEPM on Windows Server 2003
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)
can you try replacing the sylink
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
Please don't forget to mark your thread solved with whatever answer helped you : ) Rafeeq
I do it using psexec and it
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.
Sylink
Check these links.
http://service1.symantec.com/SUPPORT/ent-security....
http://service1.symantec.com/SUPPORT/ent-security....
Thanks & Regards Sandip C Sali
Hi prohol, It is a "feature"
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
thanks all. I use 3 solution
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).
Would you like to reply?
Login or Register to post your comment.