crwdns2933423:0crwdne2933423:0
crwdns2947577:0crwdnd2947577:0crwdne2947577:0

Getting Computace to respond to removal?

crwdns2915344:0crwdne2915344:0

This machine was acquired used and I am having the hardest time with Absolute Persistence. I already called Absolute and they cleared it out. However this generation of Persistence is a proper pain. I put a fresh copy of Windows on it and then wiped it today intentionally disabling ALL of the firewalls and keeping it on public to prevent network hazards. I also put it on an Asus router and it is not responding in the times older Persistence 1.0 machines do :-(. I even tried HP BCU to force it off, it did not take the /set: command or directly - it is nasty on these. What can I do to force it to check in, even via CLI?

If anyone is seeing this and thinks you shouldn't buy a Persistence affected PC, don't let it put you off - 1.0/2.0 are easy, the PKI versions are a bit picky - I knew this when I got it and Absolute cleared it. You just can't use it for a few days due to the security issues you need to create -- but KNOW what you are doing.

crwdns2934081:0crwdne2934081:0 crwdns2934083:0crwdne2934083:0 crwdns2934093:0crwdne2934093:0

crwdns2934109:0crwdne2934109:0

crwdns2889612:0crwdne2889612:0 0
crwdns2934285:0crwdne2934285:0

crwdns2933313:01crwdne2933313:0

crwdns2934051:0crwdne2934051:0

Had to pull the CMOS battery to get it to take for good 🙃 -- well, it's done lol I can wipe it since this didn’t clear the agent properly because of the BIOS hang. Like if anyone gets one use the image for the unlock and throw it out.

crwdns2934105:0crwdne2934105:0

crwdns2889612:0crwdne2889612:0 0
crwdns2934285:0crwdne2934285:0

crwdns2934229:0crwdne2934229:0

Nick crwdns2934231:0crwdne2934231:0
crwdns2936625:0crwdne2936625:0:

crwdns2936751:024crwdne2936751:0 13

crwdns2936753:07crwdne2936753:0 40

crwdns2936753:030crwdne2936753:0 40

crwdns2942667:0crwdne2942667:0 40