I don't think Luke733 has anything to worry about although he probably did violate something in the license agreement. Some of the users don't work here anymore and most of the hostnames are long gone, no idea what they actually were. I just pulled up an audit trail and it shows users and machines going back 14 years. I can have dozens of PC's in my organization sharing the same licenses. It does record a history (audit trail) of who created the file and and the machine hostname but that does not mean much as most companies have floating licenses and the hostname is not the license server name. Creo does not 'phone home' to check if PTC supplied the license. It has no way of knowing if PTC generated that license code or some cracker did. If Creo sees a license file on startup with a valid license code it runs, if not it exits. Before they started doing that you could fix a file (re)naming problem with a text editor, now you can't. The check codes are just there to stop people from using non PTC software from altering the files. Really? I don't think the software has any idea whether or not the license is legal or not. That is how they detect illegal files since the check strings do not match.'

Looslib 'I doubt the license file put anything malicious in the files beyond some check string that PTC writes to legal files.

Ptc creo 5.0 license file download