Highlighted
Contributor.
Contributor.
1694 views

Launch executable command line parameters ignored

We have created a bundle to install and launch GroupWise client (2012). This "online" version uses a Launch Executable action with no command line parameters in the launch phase and works fine to launch the client in online mode after install has completed.

We have another bundle, "caching mode" version, which uses a Launch Executable action to launch GW Client in caching mode by passing command line parameters:

/ipa-127.0.0.1 /ipp-1677 /pc-C:\Novell\Groupwise

This also works, except in a certain situation. The situation is this... we have a remote access solution that provides a way, using a laptop while offsite connected to any wifi, to launch the locally installed GW Client in caching mode but using different command line parameters than those noted above, we'll call this the "offsite" version. For argument sake let's say these are the parameters used for the "offsite" version:

/ipa-gw.company.com /ipp-1677 /pc-C:\Novell\Groupwise

Once back onsite, and connected to our wired network, both the "online" and "caching mode" bundles fail to launch the client correctly. The "online" version presents the Novell GroupWise Startup window which shows that the "Address:" field still contains the setting from the "offsite" version (gw.company.com). The "caching mode" version launches but is unable to connect for the same reason, and the "Updating Mailbox" window shows that it is attempting to connect to the same address used by the "offsite" version (gw.company.com).

Ignoring the "online" version, my real question is this, why is the "caching mode" version bundle ignoring the command line parameters assigned to it at launch? Shouldn't it be passing it's own parameters at launch time, effectively forgetting those parameters passed to the client by the "offsite" version?

I suppose the "online" version could be configured to pass command line parameters telling the client to launch in online mode with the correct address, but I suspect it may have the same problem as the "caching mode" bundle in the situation described.
Labels (2)
0 Likes
5 Replies
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: Launch executable command line parameters ignored

Hi,

Perhaps you could explain what it is exactly that you are trying to achieve having two different "launches" of the client? This might give us insight into how best to assist you.

Looking forward to hearing back from you.

Cheers,
Laura Buckley

Views/comments expressed here are entirely my own.
If you find this post helpful, please show your appreciation and click on "Like" below...
0 Likes
Highlighted
Outstanding Contributor.
Outstanding Contributor.

Re: Launch executable command line parameters ignored

Quick thought.
If any part of GroupWise is already running (possibly notify runs at startup?) then all client parameters will be ignored because you have already connected to the GroupWise system with whatever switches may be present on notify.

Mark.
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Launch executable command line parameters ignored

MarkDissington wrote on 15.09.2016 12:16:
> (possibly notify runs at
> startup?)


Three possible culprits to look for, in this case:
grpwise.exe
notify.exe
addrbook.exe

Uwe

--
Micro Focus Knowledge Associate
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: Launch executable command line parameters ignored

Am 15.09.2016 um 12:38 schrieb Uwe Buckesfeld:
> MarkDissington wrote on 15.09.2016 12:16:
>> (possibly notify runs at
>> startup?)

>
> Three possible culprits to look for, in this case:
> grpwise.exe
> notify.exe
> addrbook.exe


gwsync.exe

But seriously, that whole process IMHO is unnecessary. Caching mode when
properly configured simply works, and I fail to understand why to use
online mode when inhouse if you already have caching enabled.

CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: Launch executable command line parameters ignored

In article <janthenat.7m1h3c@no-mx.forums.microfocus.com>, Janthenat
wrote:
> /ipa-127.0.0.1 /ipp-1677


how about just taking advantage of the discovery mechanisms within
GroupWise. The GroupWise client will look for ngwnameserver, so just
have at least your internal DNS point that A record to your POA
Once the client connects to the POA, it finds out the exact address if
you have multiple POAs and the client switches to the correct one if
needed. Within the POA config, you put both the internal and external
address/host name and any setup caching mode will remember where to go.


Andy of
http://KonecnyConsulting.ca in Toronto
Knowledge Partner
http://forums.novell.com/member.php/75037-konecnya
If you find a post helpful and are logged in the Web interface, please
show your appreciation by clicking on the star below. Thanks!

___
“i’ve sworn an oath of solitude til the blight is purged from these lands”
Andy of Konecny Consulting in Toronto
Knowledge Partner Profile
If you find a post helpful, click the Like button below. Thanks!
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.