FlipsideReality Once upon a time, in a land far far away…

Sage 200 Active directory deployment that works.

I recently had to deploy the sage 200 client, and unsurprisingly the deployment docs were wrong. They make reference to an installshield msi that doesn't exist on the install CD. It is there, but it's packed inside another msi. This is how I did it.

Note that I'm using a MSSQL2008 server, so this may be different if you are using 2005.

• Grab the SP3 msp file for sage, Sage200V2009ClientSP3.msp (I have no idea where from)
• Run the setup exe from the client folder of the CD on a client machine.
• Progress throug hte install to the point where it asks for paths.
• Browse to the %temp% folder (start -> run, enter %temp% and hit enter)
• Look in a folder called _isXX, it should be at the top
• Copy the iiscript1150.msi file to your deployment path
• Now look in the temp folder for a folder called {7775F8DA-E53D-4D25-95B2-76BF9539EFB3}
• Copy the following files from that folder to your deployment path: Microsoft WSE 3.0 Runtime.msi, msxml6.msi, sqlncli.msi, SQLSysClrTypes.msi, SharedManagementObjects.msi.
• Look on the install CD, and copy the following files to your deployment path: SQLSERVER2008_ASADOMD10.msi, SQLSERVER2008_ASAMO10.msi
• Open a command prompt and navigate to the client install folder of the CD and run:

 D:\Sage 200 Client>msiexec /p "[PATH]\Sage200V2009ClientSP3.msp" /a "Sage 200 Client.msi" LOGON_PATH="\\[SERVER]\Sage\logon" SPOOL_PATH="\\[SERVER]\Sage\spool"

• The administrative install will ask you where you want to put the deployment. Choose the deployment path with all the other MSI's in it.
• Create a GPO to deploy the software, and include the MSI's in the following order:

1. msxml6.msi
2. sqlncli.msi
3. SQLSysClrTypes.msi
4. SharedManagementObjects.msi
5. SQLSERVER2008_ASADOMD10.msi
6. SQLSERVER2008_ASAMO10.msi
7. Microsoft WSE 3.0 Runtime.msi
8. Sage 200 Client.msi

And that should be it