Anonymous_User Absent Member.
Absent Member.
1849 views

Linux full download and Window clients

Greetings, testing out a GW installation on a SLES10SP2/OES2SP1 box, I
downloaded gw800hp2_full_linux_multi.tar.gz on my SLES server and expanded
it, and successfully installed an MTA and POA connecting to my GW system
🙂

However in the subdir structure for the resulting SDD on the SLES server,
under CLIENTS I don't see the Windows client install subdir. So I'm
thinking normally on my NetWare servers I would have the SDD which I install
the MTA/POA's off of, and I would give my Windows users access to the
CLIENTS subdir and bump the software update out, but how do I do this once I
make the move off of NetWare to OES2/Linux? The SDD won't have the Windows
client. Is there some manual way to integrate it in the SDD I expanded from
the Linux download?

Thanks for your comments
James


Labels (2)
0 Likes
5 Replies
jmarton2 Absent Member.
Absent Member.

Re: Linux full download and Window clients

On Tue, 10 Nov 2009 21:51:54 +0000, JJB wrote:

> Is there some manual way to integrate it in
> the SDD I expanded from the Linux download?


Just use the Windows/NetWare full download and extract the client from
that. Note that there's a separate GW client standalone download, but it
now automatically runs the install of the client. You might be able to
use 7-zip to manually extract it. If not, the full download is the only
option. Either way, once you have the client, stick it in your SDD just
as you had it with your SDD on NetWare.



--
Joe Marton
Novell Knowledge Partner

Joe Marton Emeritus Knowledge Partner
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Linux full download and Window clients

OK so using the NetWare/Windows SDD that I created as the source and the
Linux SDD as the destination, I just have to copy from NWSDD\CLIENT the
entire WIN32 subdir, to the LINUXSDD\CLIENT subdir?

Or do I need to copy the entire NWSDD\CLIENT directory and subdirs to the
LINUXSDD\CLIENT subdir? I don't see any conflicts, and there are some DLL's
and software.inf at the root of this structure.

Is this what every SLES/OES2 GW admin is doing?

I wonder what we will do once they stop making the NetWare/Windows download
available (once they pull NetWare support in March), or if the NW/WIN
download is delayed each SP or HP...??

Thanks
James

"Joseph Marton" <jmarton@no-mx.forums.novell.com> wrote in message
news:bOlKm.1856$K62.1715@kovat.provo.novell.com...
> On Tue, 10 Nov 2009 21:51:54 +0000, JJB wrote:
>
>> Is there some manual way to integrate it in
>> the SDD I expanded from the Linux download?

>
> Just use the Windows/NetWare full download and extract the client from
> that. Note that there's a separate GW client standalone download, but it
> now automatically runs the install of the client. You might be able to
> use 7-zip to manually extract it. If not, the full download is the only
> option. Either way, once you have the client, stick it in your SDD just
> as you had it with your SDD on NetWare.
>
>
>
> --
> Joe Marton
> Novell Knowledge Partner



0 Likes
jmarton2 Absent Member.
Absent Member.

Re: Linux full download and Window clients

On Wed, 11 Nov 2009 19:05:00 +0000, JJB wrote:

> OK so using the NetWare/Windows SDD that I created as the source and the
> Linux SDD as the destination, I just have to copy from NWSDD\CLIENT the
> entire WIN32 subdir, to the LINUXSDD\CLIENT subdir?


Correct.

> Is this what every SLES/OES2 GW admin is doing?


It's what I'm doing at least. 🙂

> I wonder what we will do once they stop making the NetWare/Windows
> download available (once they pull NetWare support in March), or if the
> NW/WIN download is delayed each SP or HP...??


Since GW8 is supported on NetWare, and Microsoft isn't doing away with
Windows, I would assume that the GW NetWare/Windows downloads won't be
removed.


--
Joe Marton
Novell Knowledge Partner

Joe Marton Emeritus Knowledge Partner
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Linux full download and Window clients


"Joseph Marton" <jmarton@no-mx.forums.novell.com> wrote in message
news:B3UKm.2257$K62.46@kovat.provo.novell.com...
> On Wed, 11 Nov 2009 19:05:00 +0000, JJB wrote:
>
>> OK so using the NetWare/Windows SDD that I created as the source and the
>> Linux SDD as the destination, I just have to copy from NWSDD\CLIENT the
>> entire WIN32 subdir, to the LINUXSDD\CLIENT subdir?

>
> Correct.


What about the NWSDD\CLIENT\software.inf file, I normally do the auto update
thing to my Windows users, do I need to copy this file as well to the
LINUXSDD\CLIENT subdir (and give my Windows users RF access at the
LINUXSDD\CLIENT subdir as I would do for the NWSDD one)?

What about the other files at the root of NWSDD\CLIENT? There's a bunch of
DLL's in there, a SETUP.CFG (which I copy to the WIN32 subdir when I want to
deploy), and an update.exe - are all these needed to be copied too if I plan
to use the auto update (build and bump #) feature?

Or is there a better way?

>
>> Is this what every SLES/OES2 GW admin is doing?

>
> It's what I'm doing at least. 🙂


OK, just wanted to be sure I wasn't forcing the round peg into the square
hole... 😉

>
>> I wonder what we will do once they stop making the NetWare/Windows
>> download available (once they pull NetWare support in March), or if the
>> NW/WIN download is delayed each SP or HP...??

>
> Since GW8 is supported on NetWare, and Microsoft isn't doing away with
> Windows, I would assume that the GW NetWare/Windows downloads won't be
> removed.


Right... the NW/WIN download also includes the programs to install the back
ends on a Windows server, not just the client, so I guess at the very least
this will continue to be available..

>
>
> --
> Joe Marton
> Novell Knowledge Partner


Cheers
James


0 Likes
jmarton2 Absent Member.
Absent Member.

Re: Linux full download and Window clients

On Thu, 12 Nov 2009 14:24:23 +0000, JJB wrote:

> What about the NWSDD\CLIENT\software.inf file, I normally do the auto
> update thing to my Windows users, do I need to copy this file as well to
> the LINUXSDD\CLIENT subdir (and give my Windows users RF access at the
> LINUXSDD\CLIENT subdir as I would do for the NWSDD one)?


Honestly I'm not sure as I haven't tested that yet. I don't use auto
update here.

> What about the other files at the root of NWSDD\CLIENT? There's a bunch
> of DLL's in there, a SETUP.CFG (which I copy to the WIN32 subdir when I
> want to deploy), and an update.exe - are all these needed to be copied
> too if I plan to use the auto update (build and bump #) feature?


The setup.cfg there is only a "template" for your use. The one that
matters and is used by setup.exe is located in win32. I don't believe
you'll need the other files, either.

> Right... the NW/WIN download also includes the programs to install the
> back ends on a Windows server, not just the client, so I guess at the
> very least this will continue to be available..


Even if NetWare support is eventually removed from future versions of GW,
you'll still have the Windows Server downloads which presumably will have
the Windows client.

Or if there's enough customer complaints about the client download now
being a self-install, maybe we can get Novell to release it as a
standalone zip again. 🙂



--
Joe Marton
Novell Knowledge Partner

Joe Marton Emeritus Knowledge Partner
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.