P2V from Lenovo Laptop to Recover PST
-
@thanksajdotcom said:
@scottalanmiller said:
@thanksajdotcom said:
Issue is the email was pulled from an ISP email, which uses POP3, not IMAP/
POP3, while silly, is not the issue. It is a setting from the end user to delete the files on download. POP3 can keep the files on the server. It's not a protocol issue, it is end user decisions.
The setting is set that way by default. I can't really blame a home user for not knowing.
There is no one to blame. It's not about "blame." Every decision here was the end user's and the end user's alone. That doesn't make them a bad person. But it does NOT make the issue yours, Staples or Microsofts. Walk away, NOW. This is exactly the kind of overstepping that has gotten you in trouble time and time again. Quite literally, if I was a manager and knew you were considering this, I'd walk you out the door right this second. This is a completely justifiable firing offense. No warning needed. There is no condition under which you should continue given what you have explained to us.
-
@scottalanmiller said:
@thanksajdotcom said:
Because of the way the network is setup. It's annoying. I have no control over the backend either.
Well, easy peasy then. It isn't your issue and legally you have no right to continue. Explain to the customer that Staples does not provide the tooling required to recover files and give the box back to the customer. Tell him that any corner computer store can recover his files in minutes and send him on his way.
If Staples is blocking you from doing this, why are you looking at putting them in line for a Microsoft licensing violation? Don't even EVER think of going down this path.
You have to remember that Staples is a retail store. They really don't want you to handle projects that take you hours for very little payoff. You gotta do what is best for your company because they are the ones that pay your bill.
People don't go to Staples because they are looking for the best techs in the industry, they go there because they are cheap.
-
Here is the status right now:
- Customer did the dumbest chain of things, it's their data, whatever. No one is to "blame." But this is the customer's issue and theirs alone.
- Staples explicitly does not allow (technically perhaps) data recovery in this way.
- The only path you believe that you have is to violate MS licensing and make Staples culpable for intentional violations.
Those are the three things we have to work with. Stop. Think. No amount of clear thinking should lead you to keep working on that box unless you come up with an alternative approach. It is totally clear what you need to do next.
-
@brrabill shudders quietly in his chair
-
@IRJ said:
You have to remember that Staples is a retail store. They really don't want you to handle projects that take you hours for very little payoff. You gotta do what is best for your company because they are the ones that pay your bill.
And no matter how board you are and how much free time you might have.... violating MS licensing as a support practice puts Staples at risk unnecessarily. There is zero reason for them to be at risk in that way.
-
@IRJ said:
People don't go to Staples because they are looking for the best techs in the industry, they go there because they are cheap.
Going to Staples for this kind of data recovery is just another "the customer made this decision" component. They decided to go to someone that is not a recovery shop and lacks the tools to do this properly. Again... their decision. Nothing wrong with that but you can't live in a world where you and Staples assume all costs and responsibility and shield end users from their own decisions.
-
On a PERSONAL level I help people like this all the time. Not breaking licensing but try to recover data from their drives.
But of course a company should not get involved in any illicit activity.
-
Nothing wrong with him trying to recover the data, as long as that is allowed (sounds like it is not.) He has means by which he can legally do that. It's only company policy stating that he cannot.
-
Clone the drive (as a backup), then stick it into a desktop. Run windows repair(s) until it boots into safe mode, do the needful, bill the customer. Unsure what requires P2V etc etc
-
@BRRABill said:
On a PERSONAL level I help people like this all the time. Not breaking licensing but try to recover data from their drives.
But of course a company should not get involved in any illicit activity.
Refusing to do personal work on anyone's computers has been the best decision I ever made.
-
@IRJ said:
@BRRABill said:
On a PERSONAL level I help people like this all the time. Not breaking licensing but try to recover data from their drives.
But of course a company should not get involved in any illicit activity.
Refusing to do personal work on anyone's computers has been the best decision I ever made.
Preach it!
-
@IRJ said:
Refusing to do personal work on anyone's computers has been the best decision I ever made.
Yeah not sure I can do it.
-
@MattSpeller said:
Clone the drive (as a backup), then stick it into a desktop. Run windows repair(s) until it boots into safe mode, do the needful, bill the customer. Unsure what requires P2V etc etc
Can you legally boot a copy of Machine1 on Machine2 like this?
-
-
@BRRABill said:
@MattSpeller said:
Clone the drive (as a backup), then stick it into a desktop. Run windows repair(s) until it boots into safe mode, do the needful, bill the customer. Unsure what requires P2V etc etc
Can you legally boot a copy of Machine1 on Machine2 like this?
If it is FPP, yes. If it is OEM, no.
-
@scottalanmiller said:
@BRRABill said:
@MattSpeller said:
Clone the drive (as a backup), then stick it into a desktop. Run windows repair(s) until it boots into safe mode, do the needful, bill the customer. Unsure what requires P2V etc etc
Can you legally boot a copy of Machine1 on Machine2 like this?
If it is FPP, yes. If it is OEM, no.
I'd love to get some feedback from a MS rep for this. It seems insane to screw a customer for such a minor thing.
-
@MattSpeller said:
@scottalanmiller said:
@BRRABill said:
@MattSpeller said:
Clone the drive (as a backup), then stick it into a desktop. Run windows repair(s) until it boots into safe mode, do the needful, bill the customer. Unsure what requires P2V etc etc
Can you legally boot a copy of Machine1 on Machine2 like this?
If it is FPP, yes. If it is OEM, no.
I'd love to get some feedback from a MS rep for this. It seems insane to screw a customer for such a minor thing.
You and I both know nothing would ever come of it, but I am pretty sure a MS rep is going to state the legalities and leave it at that.
-
@MattSpeller said:
@scottalanmiller said:
@BRRABill said:
@MattSpeller said:
Clone the drive (as a backup), then stick it into a desktop. Run windows repair(s) until it boots into safe mode, do the needful, bill the customer. Unsure what requires P2V etc etc
Can you legally boot a copy of Machine1 on Machine2 like this?
If it is FPP, yes. If it is OEM, no.
I'd love to get some feedback from a MS rep for this. It seems insane to screw a customer for such a minor thing.
They've commented before. Nothing new here. OEM restores are extremely clear. And it is not MS screwing anyone, it is...
- The wrong way to do a restore.
- The customer's option to have used OEM rather than FPP, they already saved money giving up this feature
- Not MS' fault that the customer didn't take a backup of any sort, anywhere.
-
@IRJ said:
You and I both know nothing would ever come of it, but I am pretty sure a MS rep is going to state the legalities and leave it at that.
What else is there to state. Customer made decisions, had tons of ways to not have this happened and now that they have not been proactive are hoping that MS will cover their butts for them.
There ARE options here, even now the reasons that we can't do a restore are a Staples' decision. In no way is MS blocking any recovery.
-
@scottalanmiller said:
I stopped years ago. I don't work on family machines, friends' machines... nothing. There is nothing good that can come from that.
I don't have the chutzpah.