| We currently have all of our clients connecting in three-tier
| thin mode, however we do have some client machines that are
| massively overspec'd and would like to run Axapta in 3-tier
| fat on them. I have three concerns in this case:
| - SQL client licensing: what are the licensing implications
| on sequel for having clients connecting directly to it?
You need a SQL-Client-Acces-License (CAL) for each Axapta-User no matter if
you are using 2- or 3-tier. So there will be no difference.
| - Application and Bin folders: up until now, our client
| configurations have, incorrectly, been pointing to shared
| application and bin folders on the file server (the folders
| containing the non-standard applications). This posed a
| security risk, as that folder needed to be shared to all
| axapta users! We recently discovered that this is not
| necessary and want to alter our configs to use their local
| installations, can we expect any side effects?
I recommend you install the client files on the users machines. In 2-tier
mode, let them use the same Application-Folder the AOS uses. Try using
Windows-Tools to see what rights your users (Normal user, Developer) need on
the axapta-files (readonly, write).
| - To avoid the problem of future installations being
| performed incorrectly, we would like these installs (from the
| deployment page) to be silent, or at least to NOT offer the
| users the ability to choose installation paths, how do we
| achieve this?
|
| Regards,
|
| Matt Benic
| Axapta Developer
| UTi Sun Couriers Division
HTH
Herbert
| Yahoo! Groups Sponsor | |
|
|
Yahoo! Groups Links
- To visit your group on the web, go to:
http://groups.yahoo.com/group/development-axapta/
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
