Difference between revisions of "Arcgis10"
(→Introduction) |
m (→Producing the install image) |
||
Line 9: | Line 9: | ||
= Producing the install image = | = Producing the install image = | ||
+ | If your %SOFTWARE% directory is stored somewhere where it is not easy to get write permissions from a windows admin account (eg on a well locked down samba share), then it is possible to perform all of these step on a separate computer and then copy the completed directory to your %SOFTWARE% directory. | ||
− | + | Copy the contents of your DVD onto your server. You should have a directory that looks like this: | |
+ | <pre> | ||
+ | dir /L /OG %software%\GIS\ArcDesktop10 | ||
+ | </pre> | ||
+ | |||
+ | In order to slipstream the service packs into the install image it is necessary to create an admin install of just the desktop component (ie the setup which is in the "desktop folder"). Because of the length of some of the various filenames in the unpacked ArcGIS installer, I always find it necessary to use the "SHORTFILENAMES=TRUE" option when creating an admin install of ArcGIS. | ||
+ | |||
+ | <pre> | ||
+ | msiexec /a %software%\GIS\ArcDesktop10\desktop\setup.msi SHORTFILENAMES=TRUE | ||
+ | </pre> | ||
+ | This is interactive installer will ask you to define a location for the admin install. I've used %software%\GIS\ArcDesktop10\arceditor in the package below. | ||
+ | |||
+ | Now download the service packs | ||
= Main package = | = Main package = |
Revision as of 13:30, 24 February 2011
Contents
Introduction
ArcGIS Desktop is a proprietary and full featured desktop GIS package produced by ESRI (http://www.esri.com). In addition to the core software there are various service packs, SDKs, extensions and plugins that you may need to include in your deployment. Fortunately enterprise deployment is described in detail in this white paper:(http://www.esri.com/library/whitepapers/pdfs/arcgis10-enterprise-deployment.pdf)
There are two key considerations for how to deploy this software:
- What licensing mechanism you will be using (standalone or licence server)?
- How you plan to manage service packs (slipstream them into the install image or apply them to the clients after the main installation)?
The example package below is for a standalone licence and service packs slip streamed into the install image.
Producing the install image
If your %SOFTWARE% directory is stored somewhere where it is not easy to get write permissions from a windows admin account (eg on a well locked down samba share), then it is possible to perform all of these step on a separate computer and then copy the completed directory to your %SOFTWARE% directory.
Copy the contents of your DVD onto your server. You should have a directory that looks like this:
dir /L /OG %software%\GIS\ArcDesktop10
In order to slipstream the service packs into the install image it is necessary to create an admin install of just the desktop component (ie the setup which is in the "desktop folder"). Because of the length of some of the various filenames in the unpacked ArcGIS installer, I always find it necessary to use the "SHORTFILENAMES=TRUE" option when creating an admin install of ArcGIS.
msiexec /a %software%\GIS\ArcDesktop10\desktop\setup.msi SHORTFILENAMES=TRUE
This is interactive installer will ask you to define a location for the admin install. I've used %software%\GIS\ArcDesktop10\arceditor in the package below.
Now download the service packs