The second of the wizards which pops up after the web client has been installed is the Web Components Help.
On the Welcome step click on Install to begin the installation:
Continue reading “Hands On With Microsoft Dynamics GP 2016 R1: Install Web Components Help”
Once the installation of the web client is complete, two wizards will be started. The first of these is the Microsoft Dynamics GP Web Components Configuration Wizard.
On the Welcome step click on Next:
Continue reading “Hands On With Microsoft Dynamics GP 2016 R1: Web Client Configuration”
In this post, we’re going to cover the installation of the Microsoft Dynamics GP Web Client as a single-machine deployment.
To install the web client, launch the setup utility from the downloaded installation media. Under Additional Products click on Web Client:
Continue reading “Hands On With Microsoft Dynamics GP 2016 R1: Installing the Web Client”
Todays post is a bit of a diversion from the Hands on With Microsoft Dynamics GP 2016 R1 series of posts I am currently working through. I was away on site last week and didn’t get a chance to write many posts and am now trying to catch up.
So something a little funny (I hope) to distract you while I get the next posts written:
The pet store was selling them for 50¢ a piece. I thought that odd since they were normally a couple thousand each. I decided not to look a gift horse in the mouth.
I bought 200. I like monkeys.
I took my 200 monkeys home. I have a big car. I let one drive. His name was Sigmund. He was retarded. In fact, none of them were really bright. They kept punching themselves in their genitals. I laughed. Then they punched my genitals. I stopped laughing.
I herded them into my room. They didn’t adapt very well to their new environment. They would screech, hurl themselves off of the couch at high speeds and slam into the wall. Although humorous at first, the spectacle lost its novelty halfway into its third hour.
Two hours later I found out why all the monkeys were so inexpensive: they all died. No apparent reason. They all just sorta’ dropped dead. Kinda’ like when you buy a goldfish and it dies five hours later. Damn cheap monkeys.
I didn’t know what to do. There were 200 dead monkeys lying all over my room, on the bed, in the dresser, hanging from my bookcase. It looked like I had 200 throw rugs.
I tried to flush one down the toilet. It didn’t work. It got stuck. Then I had one dead, wet monkey and 199 dead, dry monkeys.
I tried pretending that they were just stuffed animals. That worked for a while, that is until they began to decompose. It started to smell real bad.
I had to pee but there was a dead monkey in the toilet and I didn’t want to call the plumber. I was embarrassed.
I tried to slow down the decomposition by freezing them. Unfortunately there was only enough room for two monkeys at a time so I had to change them every 30 seconds. I also had to eat all the food in the freezer so it didn’t all go bad.
I tried burning them. Little did I know my bed was flammable. I had to extinguish the fire.
Then I had one dead, wet monkey in my toilet, two dead, frozen monkeys in my freezer, and 197 dead, charred monkeys in a pile on my bed. The odor wasn’t improving.
I became agitated at my inability to dispose of my monkeys and to use the bathroom. I severely beat one of my monkeys. I felt better.
I tried throwing them way but the garbage man said that the city wasn’t allowed to dispose of charred primates. I told him that I had a wet one. He couldn’t take that one either. I didn’t bother asking about the frozen ones.
I finally arrived at a solution. I gave them out as Christmas gifts. My friends didn’t know quite what to say. They pretended that they like them but I could tell they were lying. Ingrates. So I punched them in the genitals.
I like monkeys.
Typically for a production environment, an installation of the web client would be done as a scale-out deployment whereby the different components are installed on different servers.
As I am working on a small number of servers in my demo environment (a Domain Controller, a SQL Server and a Web Client Server) I will be doing a single-machine deployment with the sessions central and session host services on a single machine.
To do this I have the Microsoft Dynamics GP desktop client installed on the Web Client: this is the only machine with a client installed.
To do this, I need to add the Web Client Runtime feature to the installation of the desktop client. To do this open the Programs and Features applet in Control Panel, select Microsoft Dynamics GP 2016 and click the Change button:.
Continue reading “Hands On With Microsoft Dynamics GP 2016 R1: Install the Web Client Runtime”
One of the new features introduced in Microsoft Dynamics GP 2016 R1 was an OData service which provides a new way to report off Microsoft Dynamics GP. Before OData can be used, the service ust be installed from the Dynamics GP installation media.
Load the setup utility from the installation media and, under Additional Products, click on :
Continue reading “Hands On With Microsoft Dynamics GP 2016 R1: Install The OData Service”
Microsoft Dynamics GP PowerShell has a number of cmdlets which can be used to administer Microsoft Dynamics GP. Before you can use them GP PowerShell needs to be installed.
The following command can be used to return all available cmdlets for Dynamics GP PowerShell:
Get-Command -module GP2016
The following example shows how GP PowerShell can be used to create a new company:
Add-CompanyDatabase -GPClientDirectory "C:\Program Files (x86)\Microsoft Dynamics\GP2016" -SqlAdmin "sa" -SqlAdminPassword "password" -SqlServerName "2016R1-SQL\GP" -CompanyName "azurecurve Publishing" -CompanyDbName "A16R1"-SqlMdfFilePath "C:\SQL Server\Data\" -SqlMdfFileName "GPSA16R1Dat.mdf" -SqlLdfFilePath "C:\SQL Server\Data\" -SqlLdfFileName "GPSA16R1Dat.ldf"
The supplied parameters and their values are:
You would replace the text between the quotation marks with the values you want to use to create the company.
Enter the cmdlet and parameters into GP PowerShell and hit return and the cmdlet will launch GP Utilities and create the new company; if you have any missing parameters or errors the launch will fail (usually with a less than helpful message).
Microsoft Dynamics GP 2015 RTM introduced PowerShell which can be used for a number of administrative purposes. To use the supplied cmdlets, Microsoft Dynamics GP PowerShell needs to be installed from the downloaded media.
Once you have the media downloaded, run the setup utility and, under Additional Tools, select GP PowerShell:
Microsoft Dynamics GP supports the use of cross-platform companion applications (such as the Business Analyzer app).
Run the Microsoft Dynamics GP setup utility and, under Additional Tools select Companion Application Services:
Once the Web Services have been installed and configured, it is recommend that they be verified to ensure everything is working as it should. There are four items which need to be checked.
The first check, is to make sure that the Windows service is running; check this by opening the Services Control Panel applet (easiest to do by hitting Win+R and typing services.msc; scroll down and find Microsoft Dynamics GP Service Host. Ensure it is running and set to Automatic:
Continue reading “Hands On With Microsoft Dynamics GP 2016 R1: Web Services Verification”