Hi portent,

can you try creating a new package and try deploying it using migration and deployment wizard( once package is created , save it, in migration and deployment wizard, select existing package option)

find unmanged computer option does not give reason for why it failed, migration and deployment will let us know the cause.
most of the times, it will be authentication...check these steps and let me know

Greetings portent,

We have an internal document on getting this deployed to Windows 7, I believe UAC is preventing the deploying from going through. I would suggest either temporarily disabling UAC or giving us a call and we can provide you with a registry key that will circumvent UAC and allow the install to go through.

then it should be this key.

look for any other log file starting with  a number .log

Try deploying to Win XP or Win 2003 and update the status

You said the deployment status was failed
That means the package never reached the client hence there wont be any logs getting created on the client side.
You will need to make sure that the on the client the windows firewall is turned OFF & the simple file sharing is disabled.
if still its not working then try to install the client locally.

Ok, sorry it took a while for any feedback here.

Have now disabled the UAC without any luck using the "find unmanaged computers" tool.

Deployed throu the Migration and deployment wizard" and this works as it should. (deployed to a win 7 computer)

I have been using the "find unmanaged computers" tool since Symantec released their first Endpoint Protection and I have not encontered any problems until now, when trying to deploy from a new server 2008 R2 server.