Getting on towards two years ago, I did a post where I mentioned that AD Groups used as approvers need to have a display name set; I don’t seem to have mentioned that ordinary domain user accounts set as approvers also need to have a display name set.
I’ve recently been reminded about this on a test system where the admin account I was logging in as did not have a display name.
Where there is no display name, you can set the approver, but when you click OK, the name disappears.
Depending on your selected options when installing the Microsoft Dynamics GP web client, there are between three and four service accounts required.
The three which are always required are:
- Web Application User
- Session Service
- Session Central Service
The one which is optional dependent on installation options is:
- Management Console Application User
This last is only required if the Management COnsole is installed to a different web site to the web client.
To create the service accounts, you need to be logged onto the Domain Control (in my case DC1 which is running Windows Server 2008 R2) and open Active Directory Users and Computers.
Continue reading “Microsoft Dynamics GP 2013 SP2 Web Client Scale-Out Deployment: Creating Required Service Accounts”
There are two security groups required for the Microsoft Dynamics GP web client:
- A group for users who can access the web client
- A group for users who can access the web client’s management console.
To create these groups we need to be logged onto the domain controller which on my test system is AZC-DC1.
On the domain controller, open Active Directory Users and Computers.
I decided to create a business unit called Microsoft Dynamics GP but you could create the required groups anywhere. To create the web console user’s group click the Create Group button on the toolbar:
Continue reading “Microsoft Dynamics GP 2013 SP2 Web Client Scale-Out Deployment: Creating Security Groups In AD For The Web Client”