IT/Programming Help

Hey guys. I’m working on a project where I am trying to set up a remote controller using a linux program that will run behind the windows OS.

Basically, here is the story. We give out a laptop. We want to be able to shut down the laptop in the event a customer falls behind on a payment.

I am not looking for code as much as i’m looking for logic to start with.

We would like to start out by having the PC check in with the host server. This is as far as I have got. I can easily track the laptop but im having trouble coming up with a way to control the features such as on/off since im working with Linux behind windows. I think this is where the problem is coming from.

The only real idea I have jotted down so far is to look into the possibility of canceling the product code on the PC so that the OS stops working. Once the payment has been made I can go ahead and restart the product code. The only problem im thinking will happen is that Microsoft dosen’t like one product code being used to many times so I think i’ve already shut that idea down. Any help appreciated…

I don’t know much about the subject, but anyone with a working knowledge of computers, namely simply reformatting, should be able to wipe whatever you do off the laptop easily.

toss a remote kill switch so to speak on the power supply and have it be controlled remotely like a gps or onstar can kill your engine of u fall behind on ur payments

Is there any way to control the cooling fan?

You could program something that disables the fan so it only runs for a few minutes before it goes into thermal overload protection and shuts down.

I think that would void warranties and is most likely not very cost effective.

very true

I think I came up with the solution:

What-ever checks when it fails rewrite the boot.ini with garbage and reboot the machine

Won’t be able to boot into windows.

Schedule a task at a daily interval which downloads a file from the host server.

Logic:

Reads the file is deactivate, is in the file run script to break boot.ini and reboot, if not, do nothing.

You might want to look at and even possibly disassemble code from something like Lojack for Laptops… since you are looking for the same functionality. AFAIK it runs custom code in the bios which checks in with a server on the internet from time to time and a remote “kill” can be performed if needed.

What is this “linux behind windows” thing you talk about? Where is your code located, on the disk?

Basically, we will have to download a program or application that is linux/unix based onto each computer. The program is what will contain the code for execution.

Look into a program called Safeboot, my work’s laptops use it for encryption. But on every reboot you have to enter a username and password, then when you log into windows, safeboot will sync with the server and check to make sure the local user/password list is acurate. If you remove the user they can’t get past the safeboot login during a reboot. From what I hear from the IT guys onsite, in order to reformat the drive you have to disable safeboot and/or it just takes a stupid amount of time.

well if its linux or unix behind windows then there has to be a unix or linux partition of some sort correct? if thats the case bypass win-blows all together and just code it to contact the server download a boot file to force it to bypass or overwrite windows boot.ini and just force it to loop or shut down or maybe boot linux or unix os that automatically scripted to log in by itself and connect to the server and once it finds a payment has been made another file is downloaded to reverse the boot options and presto win-blows now has control again? probly sounds easier then it is… if its even possible but i would think this day in age there has to be a way to do it.

Yea I came up with something that seems to be working. I am still tweaking it but it works.

What you’d have to do is make some kind of user lockout policy. You really cant do much to disable the machine, if you did and it wouldnt boot to windows… how would you revert back once the customer pays?

The client we are developing this for is a rent to own company. Basically they want software from us that will disable a pc and basically force the customer to bring in the computer to have it “fixed” and make a payment or it dosent get fixed.

Basically, we throw a garbage value into boot.ini so the pc won’t boot the OS.
The customer then brings the pc in for repair and to make a payment. At which time we use a startup fix utility to repair the damaged boot.ini file.

Wow man that’s great. I need to get a real job. :rofl

You are assuming that the users are idiots. What’s to stop them from blowing away the hard drive and reinstalling the OS? You need something that runs in hardware i.e. the bios.

A BIOS and a hard drive password.

The company were doing this for technically owns the PC’s until they are done being rented, or payed for. As a precaution we already put Passwords on the BIOS and the Hard Drives. Only the store and us have the passwords and they are not shared with the customer.

Of course if you know what you are doing there are always going to be ways around anything you do. BIOS can be reset. Hard Drives can be replaced. Etc, etc. 98% of the clientel for rent to own do not have the knowledge to reset BIOS and replace hard drives. The store is looking to cut down on loss, not eliminate it. That is impossible in that industry.

Yeah like said before. That can be worked around. You can install an OS without needing the bios password as long as the optical drive is set to a boot device prior to the hard drive.

What would be sweet is a hard drive encryption program such as true crypt or something like that set to encrypt the drive at your command, only making it accessable to them if they bring it in to have the decrypted… but… then again you would only have to re-install OS over the encrypted drive if it doesn’t have CMOS security.

Tough one to do on a non large programming project scale. Let me know how it turns out!

Yea you def. have a good point. I did some additional logic last night and came up with another idea on top of the passwords.

The software we are developing is also going to be able to track the customer PC’s. Basically, the PC will be scheduled to call into the host server at least once a day, or whenever it is hooked up to the internet. If the PC does not call in it goes into a report which will be viewed at the end of each week. If there is a PC that has not called in within a given time period then the client takes over from there and does whatever they have to do to find out what their customers are up to.

Damn Ricky didn’t know you were a computer geek