Shamelessly stolen from the stanford forum.
It works.
Will see how well it fares on the machines at work. And I can keep an eye on the clients using fahmon and fix any problems with vnc.
Don't know if it's 100% Kosher, but one of my teammates found a way to run the Windows SMP client as a service & claims to have been doing so for over a month now without a lick of trouble. I just tried it out on my own Athlon X2 4400 system & it seems to be working just fine for me as well. To test it, I created a new user account, logged off my account, logged into the new account in which the WinSMP Client continued to run, I then rebooted the PC from the new account. Upon restarting, the WinSMP client started up just like the non SMP clients in service mode.
Key points:
1> .net 2.0 & Windows SMP Client must be installed from the same account with full administrator privelages.
2> using the -configonly flag, say "yes" to services question & configure everything else as you normaly would.
3> Open the services control pannel, go to the new FAH WinSMP service & open the properties for it & click the log on tab. Select Log On As: This Account (instead of Local System Account), put the user name for the account under which .net 2.0 & WinSMP client were installed & enter the password.
4> Reboot & WinSMP client will automaticly start in service mode.
It works.
Will see how well it fares on the machines at work. And I can keep an eye on the clients using fahmon and fix any problems with vnc.