Tag: Microsoft Dynamics GP 2013

In this series of posts I’m going to take a look at the Config AD product from Fastpath which adds single sign-on to the Dynamics GP desktop client; you can find my series index here.

With the service installed, the next stage is to configure the service. This is done by accessing Config AD and then opening the Config AD Options (File » Options) and then select the Service tab:

On this tab there are several options which can be enabled/disabled:

1. Disable/Delete Feature Enabled – When this option is enabled a choice can be made as to the interval the process cycles at and whether Dynamics GP users should be disabled or deleted when the AD account is deleted.
2. Auto Logout Feature – This option will logout users after the specified number of minutes inactivity.
3. AD Group Security – This option will provision new users and assign/revoke access to GP users based upon AD Group membership of AD Groups that are setup in Config AD for GP access

As well as the above options, you also need to specify the Login name that should be used to access SQL Server.

In this series of posts I’m going to take a look at the Config AD product from Fastpath which adds single sign-on to the Dynamics GP desktop client; you can find my series index here.

Config AD includes a service which can run on any machine within the network; the service can automatically log users out after a period of inactivity and will also disable/delete GP user accounts when the AD user is deleted.

A service account is needed to run the Config AD service; this account needs to be a Domain User account and also needs to be either a Domain Admin or have the following permissions:

1. Read Property and List Contents permission to the Deleted Objects container in Active Directory (non-admin users will not have these permissions by default, but they can be granted: further details available from Microsoft Support).
2. Read All Properties permission to the container(s) where your users are located.
3. Log on as a service permission.
4. A SQL Login on the SQL Server for the domain user.

With a suitable service account, find the Fastpath.ADServiceSetup.msi in the /FPConfigAD 5.4.0.0/Config AD Service 3.3.0 folder.

Continue reading “Implementing Fastpath’s Config AD: Installing The Service”

In this series of posts I’m going to take a look at the Config AD product from Fastpath which adds single sign-on to the Dynamics GP desktop client; you can find my series index here.

Once a user has been created or associated, the first time that user logs into GP they will need to link the GP and Windows passwords. When Dynamics GP is started, the user ID will default in; enter the password (if the user was created from Config AD the password will be set to the Config AD Options) and click OK:

Continue reading “Implementing Fastpath’s Config AD: First Login With Single Sign-On”

In this series of posts I’m going to take a look at the Config AD product from Fastpath which adds single sign-on to the Dynamics GP desktop client; you can find my series index here.

The point of Fastpath’s Config AD is to make life easier by removing the number of usernames and passwords a user needs to be entered to access Dynamics GP. In the previous posts in this series I have associated an exiting AD user with an existing Dynamics GP user and then created a new GP user from an AD one.

For the user to benefit from this integration we need to install some code into Dynamics GP. This is done by installing the Fastpath Single Sign-On. In the FPSSO folder double click the setup.exe. On the security warning click on Run:

Continue reading “Implementing Fastpath’s Config AD: Install Single Sign-On”

In this series of posts I’m going to take a look at the Config AD product from Fastpath which adds single sign-on to the Dynamics GP desktop client; you can find my series index here.

In the last post, I took a look at associating an AD user with an existing Dynamics GP user; in this one I’ll be taking a look at creating a new Dynamics GP user from an AD one.

To do this, create an AD User in Active Directory Users and Groups and then right click and select Create Dynamics User. This will launch the Config AD logon with the first window show being ther Connect To Database one:

Continue reading “Implementing Fastpath’s Config AD: Create GP User For AD User”

In this series of posts I’m going to take a look at the Config AD product from Fastpath which adds single sign-on to the Dynamics GP desktop client; you can find my series index here.

Over the last couple of posts, Config AD has been installed and configured and it is time to get started linking AD users to Dynamcis GP ones. This can be done in one of two ways:

1. Associate AD users to existing Dynamics GP users
2. Create new Dynamics GP users from the AD users

In this post I’m going to associate my iang AD user with my ian.grieve Dynamics GP user; in the next post I’ll take a look at creating a new GP user from an AD one.

To assign a user, open Active Directories Users and Groups, right click on a user, which in this post is my iang one, and then click on Configure Dynamics User.

Before the Config AD window itself opens, you’ll be prompted to supply the database connection details. Ensure the correct Server and authentication method is selected: if using SQL Server Authentication enter the login and password:

Continue reading “Implementing Fastpath’s Config AD: Associate AD User With GP User”

In this series of posts I’m going to take a look at the Config AD product from Fastpath which adds single sign-on to the Dynamics GP desktop client; you can find my series index here.

With Config AD installed on the domain controller, we now need to configure it to connect to the required Microsoft Dynamics GP installation. To do this open the Active Directory Users and Groups, right click on a user and then click on Configure Dynamics User:

Continue reading “Implementing Fastpath’s Config AD: Configuration”

In this series of posts I’m going to take a look at the Config AD product from Fastpath which adds single sign-on to the Dynamics GP desktop client; you can find my series index here.

Once you have the Config AD installer extract the files and run the setup.exe on your Domain Controller server. Depending on your security setup you may see the following warning to which you should click Run:

Continue reading “Implementing Fastpath’s Config AD: Installation”

In this series of posts I’m going to take a look at the Config AD product from Fastpath which adds single sign-on to the Dynamics GP desktop client; you can find my series index here.

The prerequisites for Config AD are fairly simple:

• Windows Active Directory
• Microsoft Dynamics GP configured with companies and security roles
• If Dynamics GP has already been implemented the Advanced SQL Server options on all users in Dynamics GP needs to be disabled

When I was configuring Config AD the last of the prerequisites caught me out as it was mentioned only in the Troubleshooting section of the documentation. It would have been helpful if this had been mentioned in the instructions or a prerequisites section. It was fairly easy to resolve once I knew what the problem was (I’ll cover this in a later post).

In this series of posts I’m going to take a look at the Config AD product from Fastpath which adds single sign-on to the Dynamics GP desktop client; you can find my series index here.

The single sign-on is done by integrating Microsoft Dynamics GP with Active Directory. This can allow for all user provisioning to be done by the IT Helpdesk without requiring them to log into Dynamics GP itself which IT teams are not usually familiar with. Config AD installs onto the Domain Controller and provides a right click interface in the Users and Groups applet.

As it is unlikely that all maintenance will be done on the Domain Controller, Config AD also has a Config AD Desktop which can be installed on any client and allow users to be created and maintained.

Both the Users and Groups applet and Config AD allow a Microsoft Dynamics user can be created in seconds without the need to use the sa account within Dynamics GP or even to give the security and access roles in SQL Server to a user.

Continue reading “Implementing Fastpath’s Config AD: Overview”