When it comes to installing Sage 200 service packs there are a few ways that it can be done, browse to the share from each client machine, copy and run on each machine, or set it up to deploy and run at the next login.

Deploying the service pack is quick, easy, it insures all services packs are installed on all client machines and makes it easier to install remotely.

  1. Copy the service pack to the Updates directory within the Sage share
  2. Go to Program Files/Sage/Sage 200
  3. Double click SageMMSUpdateAdmin.exe
  4. Enter the full Service Pack file name (including extension) into the File Name field i.e. Sage200v2011SP2.msp not Sage200v2011SP2
  5. Type a Version number etc.
  6. Click Save.
  7. This will Generate a file called DEPLOYMENT.DAT within C:\Program Files\Sage\Sage 200
  8. Put DEPLOYMENT.DAT into the Updates directory within the Sage share.
  9. Now Login to Sage 200 on each machine
  10. Download the update(s), as prompted
  11. Install the update(s), as prompted

NB. If other files have been deployed previously (i.e. there is something already in updates), and these need to continue deploying where required, there will already be a DEPLOYMENT.DAT file in the Updates directory. This should be copied to Program Files > Sage > Sage 200 before step 3 above. This way you will be amending the deployment already set up.

NB. If the SP has already been installed on to a machine before setting up the Deployment, it will still try to download and Install when you login to Sage 200 for the first time after setting up the deployment. In this instance allow the file to download. Then go to Program Files > Sage > Sage 200 > Updates. In here there should be a file called Deployment.xml.

  • Right click and “Open With” ‘Notepad’
  • There will be a line for each Deployment starting: <File Name =”Sage2002011SP2.msp”…..
  • On the line for your File Change the Status to = “2”  (It should be showing as “1”)  (Status 1 = Downloaded, Status 2 = Installed)
  • Close & Save.

This happens for me on the server(s) as I tend to manually install service packs here. I install the server(s) like this because once a service pack is installed to the server(s), you have to login to System Administration and update companies.