Hello,
there is a way to protec a windows services exe?
windows service
Re: windows service
Do you mean prevent windows services exe from stop, pause, terminator or remove ? 
If you mean those, that is a good question, I'm wondering how to do that too.
If you mean those, that is a good question, I'm wondering how to do that too.
Re: windows service
No,
I want to apply the registration to the windows services executables. I can protect it, but since windows vista, the windows services can not have interaction with GUI, and in this case I can register the exe.
I want to apply the registration to the windows services executables. I can protect it, but since windows vista, the windows services can not have interaction with GUI, and in this case I can register the exe.
Re: windows service
No problems, you can make the registration through the key file.
So your customers will place the key file in some folder to register, instead of entering the key in the GUI (which is impossible for the service).
This way, you should take a look where you are storing registration information at Registration Features - Registration Data Storing panel, and ask user to place the file to necessary folder (if file system is used) or run a key file to add registration information to the registry (if registry is used).
Also, you can make an additional activation program to the service and protect it with registration dialog (and same project file as a service). So users will run activation program, then register through the interface, and then run protected service that will be already registered.
So your customers will place the key file in some folder to register, instead of entering the key in the GUI (which is impossible for the service).
This way, you should take a look where you are storing registration information at Registration Features - Registration Data Storing panel, and ask user to place the file to necessary folder (if file system is used) or run a key file to add registration information to the registry (if registry is used).
Also, you can make an additional activation program to the service and protect it with registration dialog (and same project file as a service). So users will run activation program, then register through the interface, and then run protected service that will be already registered.
Re: windows service
Hello,
sorry, it's not clear for me. I need the hardware id to generate the key file, how I can generated it without any interface dialog?
sorry, it's not clear for me. I need the hardware id to generate the key file, how I can generated it without any interface dialog?
Re: windows service
If you need the Hardware ID, then the second way I suggested is the best for you.
Take just any exe file, and protect it with the same project file as your service. But for this exe, enable the option Registration Features - Registration Dialog. So once you run this protected exe, it will ask you to enter registration information and register.
After you successfully register it, you may run the service, and service will be registered and will be working well.
So in your case, you will have additional exe file, that will do registration.
Does it make sense?
Also, for protecting services, you have to store registration information in HKEY_LOCAL_MACHINE in registry, and/or in some AllUsers folder for file system. This will prove protection will be able to load registration information with no matter under which user account the service or registration program are executed.
Take just any exe file, and protect it with the same project file as your service. But for this exe, enable the option Registration Features - Registration Dialog. So once you run this protected exe, it will ask you to enter registration information and register.
After you successfully register it, you may run the service, and service will be registered and will be working well.
So in your case, you will have additional exe file, that will do registration.
Does it make sense?
Also, for protecting services, you have to store registration information in HKEY_LOCAL_MACHINE in registry, and/or in some AllUsers folder for file system. This will prove protection will be able to load registration information with no matter under which user account the service or registration program are executed.
Re: windows service
It make sense, but i'm quite sure that if i choose Windows user name in hardware lock the hardware ID generate by the executable will not be valable for the windows services. Have you made this test before? (since windows vista the service run in a specific windows session and I don't know the user)
Re: windows service
Yes sure, you are right. This is also the option that is not compatible with the Windows service.
There is also one, that may not work. It is the debugging tool that allows to reset local trial information inside Enigma Protector. It won't also reset the trial, as Enigma Protector and the service are working under different user accounts.
So you should be aware of these limitations.
There is also one, that may not work. It is the debugging tool that allows to reset local trial information inside Enigma Protector. It won't also reset the trial, as Enigma Protector and the service are working under different user accounts.
So you should be aware of these limitations.