Microsoft Dynamics GP 2018 RTM has now been released. In this series of posts, I will be stepping through the installation of Microsoft Dynamics GP and additional products and then will move on to taking a look at the new functionality which has been introduced.
The series index for this series of posts is here and will automatically update as posts go live.
Whenever I install the web components, or any application or component, the next thing I do is run a test to ensure that the installation, and any configuration, was successful.
To test the Microsoft Dynamics GP web client, open the browser of your choice (from Dynamics GP 2016 onwards, the GP web client has been in HTML5 and therefore cross-browser compatible) and navigate to the web client page, which will be the server name followed by /GP. I installed the web client using a self-signed certificate which was created using the fully qualified domain name of the server.
However, when I did my test, I used only the server name and so got a security certificate warning:
To test the web client, you need to log in using a Domain account which was added to the Web Client users Domain group; I am working on a demo environment so have just used the built in administrator account, but for a live system I would always recommend using a named account:
If all goes well, the next page you’ll be present with is the company selection dialog (if you only have one company available, you will not see this step). Select a company and click Next:
If you have the sample company deployed and log into it, you will be presented with the sample company warning:
Clicking OK will deposit you to the home page:
After login, I typically step through a few actions, change a vendor, raise and post an invoice, to ensure functions work correctly. To ensure these tests are valid, they should be done when logged in with a normal user account rather than sa or DYNSA.