This is a followup to my previous question.

Question

This is a followup to my previous question.
The following code works:
MyRec.List[1].AdminObject:=createoleobject('NovellGroupwareAdmi n');
MyRec.List[1].AdminObject.ConnectByDN('SOMEDOMAIN.GROUPWISEOU.S OMEORG','SOME
-TREE' );
MyRec.List[2].AdminObject:=createoleobject('NovellGroupwareAdmi n');
MyRec.List[2].AdminObject.ConnectByDN('SOMEOTHERDOMAIN.GROUPWIS EOU.SOMEOU.SO
MEORG','SOME-TREE');
MyRec.List[1].Domains:=MyRec.List[1].AdminObject.Domains;
MyRec.List[2].Domains:=MyRec.List[2].AdminObject.Domains;
Having said that I'm getting iffy results when I try to do operations on one
domain then the other and back ... The Groupwise Admin Object api doesn't
seem to want to be connected to multiple groupwise systems, even with
multiple instantiations of 'NovellGroupwareAdmin'
Question 1:
1) Is there a way I can tell one instantiation ("You've got the football")
and have it work reliably, then do the same for the other when I need to
operate on it?
2) Is there a natural limit or restriction to this library that I'm
colliding with?
3) Has anyone had any success operating on multiple groupwise systems at the
same time?
Any help appreciated.

Answer 1

That should work in theory... however the problem I'm running into is that the job will report a "fail" everytime no matter what because it loses connection with the remote host while it's updating the network drivers. However, on the server, all network
drivers are in fact updated. The only results I get from the receive-job is a timeout, but if I redirect the actual results from the command to a text file on the server, then just wait 15 seconds for the drivers to complete their install I can read what actually
happened. I'm not sure why the job is timing out. It waits for a good 30-45 seconds before timing out when the host is only blipping for about 10 seconds, but it never tries to establish a connection back. 
Reading through, if our servers were updated with powershell 4.0 I could use the InDisconnectedSession
parameter I think... Hmmmm I'm gonna look into upgrading our powershell versions anyways.