Suggestion for a spawning a remote process
From: andrew_webby at hotmail (andrew_webby_at_hotmail.com)
Date: 03/31/04
- Next message: tinman: "Enums: Good or Bad ?"
- Previous message: MadCrazyNewbie: "Re: Dos Command in VB"
- Next in thread: andrew_webby at hotmail: "Re: Suggestion for a spawning a remote process"
- Reply: andrew_webby at hotmail: "Re: Suggestion for a spawning a remote process"
- Messages sorted by: [ date ] [ thread ]
Date: 31 Mar 2004 02:00:52 -0800
Hi
I'm working on an app that I will use to target and install patches
remotely for testing purposes (and also to get a bit more experience
of VB.Net). Given that MS supply their patches as .EXE's, it doesn't
look like I can use Win32_Product to install them (MSI only
apparently).
Am wondering what the best way to go about the spawning and monitoring
of this installation might be?
Thoughts I'd had so far include:
Schedule the job remotely, then keep checking the process list to see
when it's finished. (Untidy)
Schedule remotely, monitor the event log for information (won't work -
can't monitor events remotely, can only keep reading them..)
Was hoping the Process component would help (Start, onExited), but it
won't spawn remotely either.
Any suggestions for a decent way to go about kicking off an EXE
remotely (of course, I have all access permissions needed as domain
admin) and monitoring to see when it finishes?
I've a feeling this is one of those questions whose answer is
blindingly obvious, so I'm expecting a flash of inspiration seconds
after I hit "post".. :)
TIA
AW
- Next message: tinman: "Enums: Good or Bad ?"
- Previous message: MadCrazyNewbie: "Re: Dos Command in VB"
- Next in thread: andrew_webby at hotmail: "Re: Suggestion for a spawning a remote process"
- Reply: andrew_webby at hotmail: "Re: Suggestion for a spawning a remote process"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|