Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Deploy GP 10 with Group Policy Deployment GPO

Status
Not open for further replies.

andersonch

IS-IT--Management
May 14, 2004
8
US
I am trying to deploy Dynamics GP 10 using a Group Policies. I am down to
one issues. I cannot deploy the Microsoft Application Error Reporting 11.0.
I found what I thought was the MSI file in the \Bin\Watson\dw20shared.msi but
I keep getting the following error message.

Event Type: Error
Event Source: Application Management
Event Category: None
Event ID: 102
Date: 2/1/2008
Time: 4:00:59 PM
User: NT AUTHORITY\SYSTEM
Computer: TRAINING01
Description:
The install of application Microsoft Application Error Reporting from policy
GP 10 Install failed. The error was : Fatal error during installation.

I have searched everywhere to find a good msi package to deploy this but I
can't find one. Anyone know how to deploy this?
 
I'm pretty sure that that's not a recommended course of installation of GP.

There is a install package generator available upon installing the software on the server that may be of interest in you, but I'm pretty sure you'll need to visit every machine.

The new (old) Virtual machine model that micro$oft is pushing may help in this respect as I imagine a virtual terminal server would be a good bet to eliminate the individual desktop problem by centralizing the application rollout to a single or multiple terminal servers.

funny... I thought we got away from the as400 model....

ah well, what's old is new



-----------
and they wonder why they call it Great Pains!

jaz
 
Ya, I had to do some major hacking to get it to work. Sad that Microsoft is such a big company yet they can't get Dynamics GP setup so you can deploy to a large group of users without having to use TS.

Anyway, the Microsoft support tech that I talked to said it wasn't important to install so I removed it using a transform. Under the InstallExecuteSequence I set "Type19CA_INVALID_WATSON_COMMON" to Condition 0=1. Problem solved.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top