Endpoint Protection

When deploying to a remote computer (Windows XP, Windows Vista, Windows 7) the remote install creates the C:\temp\clt-inst folders and places two files in it: vpremote.dat and vpremote.exe  the console comes back with deployment status of failed and no logs are created on the computer that was client was being deployed to.  I am at a loss as to the cause, it was working prior to two weeks ago and nothing has changed in my enviroment (that I know of).

Are you deploying it using Migration and Deployment wizard or Find Unmanaged computers ?
Try exporting the package and then deploy using Migration and Deployment wiz.
If it fails it will also give you the reason for the faillure.
On vista and Windows 7 its mainly becuase of the UAC.
for Xp make sure  in the folder options "Use Simple file sharing" is disabled/Unchecked.

We are deploying via the Find Unmanaged computers.

I should have mentioned that UAC and Simple File Sharing is off by group policy already. 

Deploying the client via the Migration and Deployment wiz works w/o any issues, any ideas as to why the Find Unmanaged computers is failing?

Thanks,
Alex

It sounds like the installation files are being copied over. The SEP installer (setup.exe) usually gets automatically deleted on failed or successful installation.

If you have access to a computer that you are trying to deploy to. Try login go into the c:\temp\clt-inst folder(if already exist) do a push from the SEPM console and continuously refresh the folder on the client machine to see if all the files are being copied.

I know that you mention no logs are created, I am going to assume that you meant the Symantec log files in the temp folder.  Have you checked the Application event logs on the client machine, They'll show MsiInstaller events to confirm if the install is being attempted or not.

Hope that helps,

Hi Robert,

Already did that, watching the directory, only the two files (Vpremote.*) are copied over, nothing is in the Eventlogs other than in the security logs showing a remote login for the admin account used.  Thanks for the input though :)

Alex

Make sure that there have not been any changes on the account that you are using to push out the client (AD - expired password, etc).

I went through something similar with MR4 and a specific XP client, but it went away after rebooting the client. The client was on domain, firewall disabled, etc. I still do not know what the cause was, no logs - just like this case.

Be sure to post a solution when you find one, I haven't upgraded to RU5 yet.

Thanks

I just opened a support case with Symantec, will let you know the outcome.

Alex

I spent an hour on the phone last night with Symantec support.  The tech tried telling me the issue was that the install for SEPM database was corrupt and that the only way to correct the issue was to do a complete reinstall.  As a work around, he said that we could just use the deployment wizard.  When I asked if it were possible to send them the SQL database to have them look at and possibly repair I got the reply "We don't have any utilities to do that".  He then asked me if I was satisfied with the solution...

So long story short, I did a complete uninstall of SEPM, deleted the remote SQL database, reloaded Windows 2008 OS for the SEPM server and then reinstalled SEPM.  I then tried to do a Find unmanaged client install from SEPM (note at this point I have not even started customizing SEPM for our enviroment, just using the canned setup) the install fails just like before. 

I updated my case online and told the tech that what he thought the issue was was not correct.  I will continue to update this until a solution is found for the issue.

Alex


 

Hello Alex,

Navigage to

<os>:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat\bin\remote_troubleshooting.html

open the remote troubleshooting.html

check if you  have necessary permissions and made the settings are that doc

Hi Rafeeq,

Those are all in place already.

Thanks,
Alex

We gonna do a small test here , well a simple one
open a note pad , save it as setup.exe
now use the migration and deployment wizard
select this setup.exe
push it to one client
check if hat setup.exe is present in the temp folder
if it is then the push install it working..
the problem is at the client end..security may be blocking exe files.

Hi Rafeeq,

That's not it either, the migration and deployment wizard has worked since day one w/o any issues.  And when the find unmanaged clients is used, vpremote.exe is copied over to the the remote pc.

Thanks,
Alex