RE: Samba

No question the M$ stuff is entrenched since everyone is really happy to
spend way more money than they need to.

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Richard Schoen
Sent: Monday, March 30, 2015 10:22 AM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: Samba

On our recent survey and in every real world customer I talk with Windows is
firmly entrenched in the environment. AD, Exchange, Many Business Apps,
VMware, on and on.

Are you seeing differently in the customers you visit ?

Regards,

Richard Schoen | Director of Document Management Technologies, HelpSystems
T: + 1 952-486-6802
RJS Software Systems | A Division of HelpSystems
richard.schoen@xxxxxxxxxxxxxxx www.rjssoftware.com

-----Original Message-----

message: 1
date: Mon, 30 Mar 2015 08:46:11 -0500
from: "Jim Oberholtzer" <midrangel@xxxxxxxxxxxxxxxxx>
subject: RE: Samba

The biggest knock on SAMBA is related to security in my view. Netserver
follows IBM i security exactly. SAMBA has its own model that in my view is
not as robust as Netserver.

That having been said, having SAMBA on the platform is a great addition to
the already strong toolkit administrators have to utilize the resources of
the POWER platform, and the SAMBA admin needs to know SAMBA not IBM i. Add
in SWAT and/or WEBMIN, PHP, pick your WEB content management tools and
you've about clobbered any reason for an Intel network. Remember IBM i
already does LDAP so you don't even need Active Directory really. (Yea, I
know AD has more than just LDAP but those tools are all on IBM i as well)

Also since the 80GB restriction on the load source for a virtualized V7R2
partition has been lifted you can virtualize servers some much easier to the
size you need, and with NFS in the tool kit, now you can really lock down
data if you want to. (To counter my earlier point about security)

Would I pick SAMBA over Netserver, maybe, maybe not? It depends on the
customer requirements.

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


Confidentiality Notice: This email, including attachments, may include
confidential and/or proprietary information, and may be used only by the
person or entity to which it is addressed. If the reader of this email is
not the intended recipient or his or her authorized agent, the reader is
hereby notified that any dissemination, distribution or copying of this
email is prohibited. If you have received this email in error, please notify
the sender by replying to this message and delete this email immediately.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.