Hi Justin

Why is your manager strongly opposed to placing it on a WIndows share ? I
don't really haven opinion either way, I am just curious about the
reasoning and whether there is some advantage to serving it from NetServer
I am unaware of.

On Sat, Feb 15, 2020 at 3:32 AM Justin Taylor <JUSTIN@xxxxxxxxxxxxx> wrote:

We keep iACS in an IFS dir and clients access it via a NetServer share.
It's incredibly convenient, and it works great for the majority of users.
A few users occasionally have tremendous difficulty getting iACS to
launch. IBM support reviewed network and process traces and showed the
issue was a Windows error, and IBM said we needed to contact Microsoft
support. Our Windows team will not do that. The Windows manager wants to
move iACS to one of their shares (assuming that will get around the
problem). My manager is strongly opposed to that.

I'm trying to find an acceptable solution. I looked into Samba, but
unfortunately it can't coexist with the NetServer. Samba has restrictions
that would be fine for iACS, but it will not work for all of our SMB share

Do anyone have any thoughts or suggestions?

This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].