2010-07-28 07:44:21 UTC
connect to a RPC Service on a remote machine.
By default, the client installs itself with a dependency to the same
machine RPC service. It will (or SCM will) start the RPC server
service if not already started.
The new options:
wcclient -install -server:mach_name
adds a switch to the binary to tell it which RPC server to bind and
My question is what sort of techniques I can explore, if there is not
already a Windows method for this, in particular during restart
(reboot) times to synchronize it. i.e. the RPC Server must be started
first before any RPC client can connect to it.
Currently, when the RPC client is started as a desktop, we use a
STARTUP tool to synchronize dependences, like wait for a remote RPC
server to load by basically trying to connect to it in a loop. When
its local, we use a named kernel object to wait on before starting
When starting as NT Services, I don't see a way to do this naturally,
other than maybe adding the "connection wait" looping logic to the
clients themselves, but that cause NT service startup timeout issues.
What ideas or methods do you suggest it to synchronize multiple