HQ Client Command-Line Options


Y

YidMo

We currently have 14 locations plus HQ, soon to be more on the order of 20+
and our HQ. The trouble we're having is that our closing employees aren't
all that tech-savvy and don't understand that they need to leave their
HQClient open all night so it'll process worksheets we have set to run
after-hours. Is there any way to use a command-line option to have HQClient
connect to HQ on startup, if so I'll be making a script for windows scheduled
event to run on the primary machines at the store level and starting HQClient
(possibly after killing an existing session if it's already running when the
event occurs) to force it to connect right then. Any ideas are welcomed,
I'm thinking that there must be SOME way to force a connection at startup,
either by a switch or a command-line option.
 
Ad

Advertisements

J

Jeff

YidMo,

I might be missing something, only had 3 hours sleep last night, but if you
create a shortcut to HQClient.exe and place it in the Startup folder of All
Users, HQ Client will connect according to the schedule you've setup, after
_anyone_ logs into Windows

If you're asking about running HQ Client as a Windows service, currently its
not supported, but sometimes works with an add-on Run As a Service program,
like SrvAny http://support.microsoft.com/kb/q137890/.



We currently have 14 locations plus HQ, soon to be more on the order of 20+
and our HQ. The trouble we're having is that our closing employees aren't
all that tech-savvy and don't understand that they need to leave their
HQClient open all night so it'll process worksheets we have set to run
after-hours. Is there any way to use a command-line option to have HQClient
connect to HQ on startup, if so I'll be making a script for windows
scheduled
event to run on the primary machines at the store level and starting
HQClient
(possibly after killing an existing session if it's already running when the
event occurs) to force it to connect right then. Any ideas are welcomed,
I'm thinking that there must be SOME way to force a connection at startup,
either by a switch or a command-line option.
 
Y

YidMo

Hey there Jeff, thanks for your reply... You're right about putting it in
the startup group and all, however the most relevent part of the enquiry I
think you might have missed; As we have a lot of locations, we have them
all set to connect 5 minutes apart from one another, so as not to weigh-down
our HQ server. As HQClient will only run at "x" minutes past the hour, this
won't work if I wanted them all to connect say right at midnight. The idea
here is to create a process that will FORCE all the HQ clients to both run
AND connect at one very specific moment of the evening. The reason for this,
in my case, is because we have an automated report that runs, which requires
ALL stores to have transmitted their sales/tender information. The report
needs to run at a designated time, and I need to ASSURE that all of the
stores have connected and updated accordingly, regardless of if someone at
the store has decided to close HQClient or not.

Hence, using the Event Scheduler in XP, I can create an event that'll
run/restart HQClient at a specific time, even if nobody is logged-in. This
ASSURES me that it'll be running. The catch becomes; how to make sure that
it connects at 11.55pm rather than say 12.20am at a store scheduled to
connect at 20-past every hour. If there was a switch to make HQClient
connect to HQServer on startup, I could have the event scheduler script kill
any running HQClients, start it with the switch, and voila it'd connect at
11.55pm when I need it to so I can have the reports run at midnight and I'm
certain every system has updated with their final sales info for the day.
 
J

Jeff

YidMo,

I don't see anything in Partner/CustomerSource about any switches, nor does
hqclient/? or /h reveal any.

How about some kind of macro program to do it? Run your Scheduled task to
start HQClient and then another task to run a macro that emulates a Connect
click on the HQ Client toolbar.

There really has to be a way to do this as when you right click the HQClient
icon in the system tray, Connect is an option.




Hey there Jeff, thanks for your reply... You're right about putting it in
the startup group and all, however the most relevent part of the enquiry I
think you might have missed; As we have a lot of locations, we have them
all set to connect 5 minutes apart from one another, so as not to weigh-down
our HQ server. As HQClient will only run at "x" minutes past the hour, this
won't work if I wanted them all to connect say right at midnight. The idea
here is to create a process that will FORCE all the HQ clients to both run
AND connect at one very specific moment of the evening. The reason for
this,
in my case, is because we have an automated report that runs, which requires
ALL stores to have transmitted their sales/tender information. The report
needs to run at a designated time, and I need to ASSURE that all of the
stores have connected and updated accordingly, regardless of if someone at
the store has decided to close HQClient or not.

Hence, using the Event Scheduler in XP, I can create an event that'll
run/restart HQClient at a specific time, even if nobody is logged-in. This
ASSURES me that it'll be running. The catch becomes; how to make sure that
it connects at 11.55pm rather than say 12.20am at a store scheduled to
connect at 20-past every hour. If there was a switch to make HQClient
connect to HQServer on startup, I could have the event scheduler script kill
any running HQClients, start it with the switch, and voila it'd connect at
11.55pm when I need it to so I can have the reports run at midnight and I'm
certain every system has updated with their final sales info for the day.
 
Y

YidMo

Great thinking Jeff - I downloaded a freeware application called MacroMaker
which had enough parameter flexibility to allow me to create a scheduled
script that's just what I needed.

Many thanks!

YidMo
 
M

Mihir Shah

YidMo,

Making all stores connect to the server at the same time will create
problems at HQ Server e.g. communication error for some stores.
Check and verify your 401s were processed correctly.
Best way it to stagger the store connections.

Best regards,

Mihir Shah
Diviasoft, Inc
www.diviasoft.com
(e-mail address removed)
 
Ad

Advertisements

O

ozzie

We have a hq client that runs as a service but I don't know if that is
because our supplier has custom written it or not. But try this: create a
shortcut to the client, and add " serviceinstall" at the end. eg c:\program
files\rms\hqclient serviceinstall"

If it is the same as how ours works, it should popup a message like "service
installation complete". It then becomes a bit easier to manage its start up
behaviour.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top