Weird Problem - Casper Client NOT installing

I was going home - so didn't have time for more info

That machine came from a consultant - it previously had Casper installed - was then removed and now trying to reinstall casper for a different Casper server... Also the 501 account was deleted, it currently has a 502 admin acount - maybe other odderties too...

So I was trying to find if there were particular things I should look out for... To resolve this...
-- Other then wiping it and rebuilding the image myself.

I think the command to remove the jamf binaries off the machine is jamf -removeFramework

You can then do a recon to add it to the correct jss

Since the CPU was on my desk - I was using a QuickAdd package - the one that we normally use… But it's coming up with a 'postflight script' error…

Humm… The QuickAdd is failing… But I CAN get it into Casper Via Recon…

So, is the problem solved? If not, try rebuilding the QuickAdd pkg and run again. If that errors out, you may have something wrong with the end user machine and could be related to the admin account missing and re-adding a different one.

PeterClarke ,

I had the same exact same issue, rebuilt the quick add .pkg, same issue. tried same quick add .pkg on a different Mac quick worked. I guess that it was an issue with the Mac i was using and moved on. sorry no solid answer..

C

I have this with a Mac on 10.7.4 also. Did a removeframework yada yada yada. Only solution was reimaging the machine.

Well the QuickAdd DOES Work with EVERY other sets of machines…

– But these were using an image supplied to us - for a custom project…
– The Recon solution worked, but the QuickAdd didn't
– There was possibly something odd about the original image…

Looks like there was something wrong with THAT copy of the QuickAdd package…

– Just thought I would share that info…
– someone may find it helpful…