We have a system that we would like to protect against xcopy onto another machine. The system consists of MFC app, some .NET components and lots of configuration files. If we were able to make a strategically selected set of these configuration files unavailable for copying (or useless/encrypted when copied) then we would have effectively achieved this goal. Due to the nature of the system, it has local administrator rights when executing. The platform is windows. In this case it will probably be win7.
I realize that this has little chance of being waterproof as the persons copying the software will have access to the operating system as administrators. But they aren't computer savvy. I am merely talking about introducing friction so that the first person to try will think "oh, didn't work".