| Subject | Possible NT Service issue with Registration module? |
| Version | 6.x |
| Date | 07/22/2007 |
| Message | Melvin, I just set up the new registration number for Automize on my system and was about to send information on setting up this number to others using Automize here at *******. However, I stopped myself. I have a question... Will there be any problems if the registration is set up with my username (i.e.. ***) and the NT service is set up to utilize a service account (i.e.. AutomizeService) ? I ask because this sort of arrangement is very common at our site. |
| Reply1 |
Thanks for pointing out this possible issue with the service account name
and new registration system. I just finished testing 6.06 with a service
account name different from my username. Yes, the tasks would not run in 6.05-6.06 when the service account name is different than the username. In your case, the tasks may still be running under service account since 6.05-6.06 get new 30 day trial period. We will fix this issue in 6.07, which will be released next week. Basically, during registration key entry in the register dialog, the 'registered_username' will be written to file. When running in service mode, if service account name is different from the stored 'registered_username', the stored 'registered_username' will be used to verify registration. -- Sincerely, Melvin Desilva Hitek Software |
| Reply2 | |
| Reply3 | |
| Reply4 | |
| Reply5 |