UPDATE! The community will be go into read-only on April 19, 8am Pacific in preparation for migration on April 21. Read more.
UPDATE! The community will be go into read-only on April 19, 8am Pacific in preparation for migration on April 21.Read more.
Absent Member.
Absent Member.
845 views

Platform decision OES2SP3 or SLES11SP1 - what would you do?

I have to replace a NW6.5SP8 server, which does (now) only Groupwise
GWIA (and an empty MTA just for this GWIA), DNS-server and DHCP server.

I could migrate all that to OES2SP3 (there are 3 OES2SP3 servers in the
tree of the NW server already in place), but I could run all those
services on plain SLES as well.

What would you do/recommend?

Thanks for any inputs.

I tend to install it on OES2SP3, because of the already existing edir
integration of the NW server - but there are good reasons for SLES, too
- e.g. it is absolutely not needed for these services.

--
W. Prindl

W. Prindl
Labels (2)
0 Likes
3 Replies
Knowledge Partner Knowledge Partner
Knowledge Partner

I prefer OES2 only because I'm more familiar with it (meaning NSS, iManager/eDir for DNS/DHCP) vs. nasty old SAMBA, and native DNS/DHCP on SLES

So I guess if you want/need NSS, or eDir-enabled DNS/DHCP then that answers your question

If you don't mind SAMBA and native SLES DNS/DHCP then go with SLES.

(SAMBA because if you have a domain on that server or need to rebuild it, etc. via consoleone, you'll need "good" file access since NFS has no concept of file locking or doesn't care about it anyway).
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

Hi,

On 15.07.2011 14:47, W_ Prindl wrote:
> I have to replace a NW6.5SP8 server, which does (now) only Groupwise
> GWIA (and an empty MTA just for this GWIA), DNS-server and DHCP server.
>
> I could migrate all that to OES2SP3 (there are 3 OES2SP3 servers in the
> tree of the NW server already in place), but I could run all those
> services on plain SLES as well.
>
> What would you do/recommend?


Actually, there's no really good reason to use plain SLES, if you
already own OES licenses. The only one possibly being SELS11 vs. SLES10
for now, but in most cases that makes no real world difference.

NSS/NCP vs. EXT3/SAMBA for Groupwise however makes a huge difference, as
does the eDir integration of DNS.

CU,
--
Massimo Rosen
Novell 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
Absent Member.
Absent Member.

Thanks for your inputs!

Yes, that's what I think, too. And the configuration of GW on NSS/NCP
is really simpler than via plain SAMBA and further the migration is of
course much easier, too.

--
W. Prindl


Massimo Rosen wrote:

>Hi,
>
>On 15.07.2011 14:47, W_ Prindl wrote:
>>I have to replace a NW6.5SP8 server, which does (now) only Groupwise
>>GWIA (and an empty MTA just for this GWIA), DNS-server and DHCP
>>server.
>>
>>I could migrate all that to OES2SP3 (there are 3 OES2SP3 servers in
>>the tree of the NW server already in place), but I could run all
>>those services on plain SLES as well.
>>
>>What would you do/recommend?

>
>Actually, there's no really good reason to use plain SLES, if you
>already own OES licenses. The only one possibly being SELS11 vs.
>SLES10 for now, but in most cases that makes no real world difference.
>
>NSS/NCP vs. EXT3/SAMBA for Groupwise however makes a huge difference,
>as does the eDir integration of DNS.
>
>CU,


W. Prindl
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.