We choose to integrate with Active Directory.
And we let the Ax. application MSI install the appropriate schema in the AD
which was successfull after we temprarily granted Schema Rights to the installing user.
Starting the AOS in the "use AD integration" mode you can find ugly error messages in the event log. After granting domain admin rights to the AOS account everything works fine.
My question #1: which specific right does the AOS need to successfully register itself in the AD on startup or is there any other reason?
Please let me continue.
This time (not in production) we run the AOS with domain admin rights to make further tests with AD.
The client uses "connect using AD information" and "by name - find a specficic AOS" and we enter AXAPTATEST there. This is the service name of our 2 AOS.
This works fine but:
When server and client are running in AD mode we see a
reproducable client crash if a "normal" Citrix user runs it. If we test
to grant domain admin right to that user again everything works fine.
Is there again any need for an AD-specific right needed to browse the AD
for the AXAPTATEST service?
We run a Citrix conecpt. All user connect to that server having the Ax clinet
installed. This client should connect to one of the 2 AOS.
Looking forward to your help - we need it urgently!
Thanx a lot and best regards,
Arthur.
[Non-text portions of this message have been removed]
| 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.
