HQ Server not a Windows Service

Thanks for the reply. I got this directly from Microsoft--their "RMS Headquarters Best Practices Quick Reference":

Rule #5: Headquarters Client and Headquarters Server are NOT Windows® Services (page 102). . Place shortcuts in the Windows Start Up directory so they automatically start when a user logs on. . Logging off the machine while running these applications WILL CLOSE the application and stop communications. . Some partners make use of 3rd party tools that allow you to run any Windows application as a service.

Do you have your schedule set up to process HQ worksheets "after hours"? Or did you setup the HQ Client and HQ Server apps to run as services? During testing, we found when we logged off the computer running HQ Server, the Client could not connect.

thanks, randy

BTW: Microsoft's "solution" for this shortcoming is to place a shortcut to the HQ Server app in the Startup folder for All Users. Unfortunately, this still requires a user to log into Windows before the HQ Server app is started.

Like I said earlier--I was really surprised that Microsoft allows such a kludge like this to continue in a product that costs as much as RMS does. [Sorry for the rant.]

thanks, randy

hi Randy as you said you can use tools to make the Hq Server runs as a service.

you can run it as a service using SrvAny and it's installer "Instsrv.exe". Which is a Microsoft application found in "Windows Server 2003 Resource Kit Tools" and you can download it from this link:

Hi!

Thanks for the reply. Yes, I was considering using the SrvAny tools and I looked at some 3rd party tools. The 3rd party tools look nice, but the price is right for the SrvAny solution--free. I'll let you know what happens.

thanks, randy

I have gotten several replies to this issue and here's what I've decided:

• Microsoft's solution to put a shortcut to the HQ Server in the Windows Startup folder won't work for us. If you've got a dedicated computer running HQ Server and can afford to keep a user logged on all the time, then this might work for you.

• Jeff @ Check Point Software suggested creating a scheduled task which runs whenever Windows starts: System Tools | Scheduled Tasks | Add Scheduled Tasks. In the Scheduled Task Wizard, select (or browse to) Headquarters Server (HQServer.exe) and select Perform this task - When my computer starts. Then enter a user id/password to be used to run the application. You can modify the properties of the task if you wish. (I didn't test this completely, but I would expect you would need to uncheck "Stop the task if it runs for xx hours xx minutes" as I expect you want it to run continuously.) This method has the advantage of not requiring any special tools or need to edit the registry. If you're looking for a solution that is simple and effective, this would be your option. (Thanks Jeff!)

• I decided to go ahead and run the HQ Server as a service because I manage this system remotely and need to be assured the HQ Server is restarted should it stop and I'm not around to restart it. It also lets me run this service using the Local System userid. You can get the InstSrv and SrvAny tools from the Windows Server 2003 Resource Kit Tools at
  formatting link
  467a69-57ff-4ae7-96ee-b18c4790cffd&DisplayLang=en and details on how to use them at
  formatting link
  Note that the instructions are for Windows NT/2000 so the path to the Resource Kit Tools are not where they are installed for Windows Server 2003. Also, while it is tempting to check "Allow service to interact with desktop" on the Service properties, when I did that there were errors when I logged off. I have NOT attempted to use this solution on a Windows XP Pro system. That's about it. Hope this helps. If you have any questions, I'd be happy to try and answer them.

randy

You can indeed install HQ Server or HQ Client as a service. Contact your RMS reseller for instructions. A step by step article is available from Microsoft.

Most HQ users leave HQ Server/Client running 24/7 and schedule connections to run as often as every 15 minutes during business hours.

You'll want this communication running on a daily schedule to support the transfer of products between store locations. This ensures transfers from sending locations are ready to be processed at receiving locations as soon as the stock arrives.

Thanks for the reply and info. Yes, I found that article and have HQ Server running as a service on our main Server.

It might be nice for RMS 3.0 to have this process setup from the start as a service so folks won't have to set it up themselves. Just my $0.02.

thanks, randy