Network Install

Mapshop

Network Installation Steps for IT Professionals.

Before you get started, let's just inventory what you'll need to successfully install the eMapshop on your network. You will need the following:

The name of the server where the eMapshop is going. This is usually the name you see in a Universal naming scheme after the //. So for example if you're used to seeing //servera then the name of your server is servera. The type of server doesn't make a lot of difference. It could be Windows2003 or 8, Linux or Novell. It could even be as basic as a shared directory on another PC running XP in the same network. It's the OS on the client that matters and as long as it's XP,Vista or Win7 or OS X on the Mac you're good to go.

A client to use for the initial install. The eMapshop is never installed directly on the server, it is always installed through a client. It is probably a PC in IT with read/write privileges on the server. If this client is a PC it MUST have .Net 2.0 installed on it. We'll talk about how to verify that in a minute.

A network share ( a drive letter like M: or S:) mapped to a directory on the server and optionally a subdirectory. Subdirectories are handy if you want to install multiple packages on one server. For example you could put a grade level 9~12 package on a subdirectory called eMapshopHighSchool and a K~5 package on a subdirectory called eMapshopElementary.

Locate the disk in the package that has the NetworkTools directory on it.

1. Start by prepping the initial install client PC. Most likely, this will be a PC in the IT department. Make sure that this client has .Net 2.0 installed on it and has full read/write/delete privileges for the shared drive. Verify that by going to the command prompt and run the caspolinquiry.bat found in the NetworkTools directory on your install disk. Watch it run. Are all the necessary directories there? Here's another way to make sure that .Net 2.0 is installed on the machine in question. Look for this directory and file path on the C:\ drive of the PC you are using for the install. C:\windows\microsoft.Net\Framework\V2.0.50727. If not, install .Net 2.0 by running the dotnetfx.exe file from the NetworkTools directory on the Install disk. Once you are sure the the client has .Net 2.0 installed, run the Caspol.bat found in the Network Tools folder. Execute the Caspol.bat from the Command prompt so you can see all its responses. Note: If you are running Win7 you must run the command prompt by right-clicking the cmd executable and choose "run as administrator". It will stop and ask you for the name of your server. This is the server name for the network share/drive you where you will install the software. Enter just the server name, not the directories on that server where you plan to put the software. After you key that in, you hit ENTER then F6 then ENTER. Then the batch file will execute the Caspol correctly. Watch for caspol to return the word SUCCESS after it runs. Just because it says "Success" does not mean you entered the server name correctly. Verify the name displayed in the lines from the .bat file with the name you intended to enter.

2. Now you can install eMapshop using the directions that came with the software except that you chose the drive letter of the network share instead of the default c: installation. The install script will also copy all the map files up to the server at the same time. It will also put the eMapshop icon of the desktop on this first client. On a big package, it can take up to 15 minutes to copy all the files from the install DVD up to your network share.

3. For all other client workstations, primarily teacher and administrator PC's, install ArcReader, (unless you're running the PDF only version) .Net 2.0 (if necessary) and run the Caspol.bat one time on each client as detailed above.

4. Finally, place shortcut to the executable x:\subdirectoryname\digitalschoolmaps.exe where x is the drive letter of your network share on the teacher's desktop. And insert the directory on that network share if you have installed it on a subdirectory located on that share.

5. If you have ver 2.2 and also purchased the optional Klett-Perthes Digital Atlas, it is pre-programmed to run on the user's c:\program files directory. However, it can run off the network instead. But you will have to call support to have your program modified. Cal 800-532-6675.
New in ver 2.3 the client will ask you for the path of the Klett-Perthes executable the first time it runs. This is your opportunity to point the package to any network location where you have installed the Klett package.

	The name of the server where the eMapshop is going. This is usually the name you see in a Universal naming scheme after the //. So for example if you're used to seeing //servera then the name of your server is servera. The type of server doesn't make a lot of difference. It could be Windows2003 or 8, Linux or Novell. It could even be as basic as a shared directory on another PC running XP in the same network. It's the OS on the client that matters and as long as it's XP,Vista or Win7 or OS X on the Mac you're good to go.
	A client to use for the initial install. The eMapshop is never installed directly on the server, it is always installed through a client. It is probably a PC in IT with read/write privileges on the server. If this client is a PC it MUST have .Net 2.0 installed on it. We'll talk about how to verify that in a minute.
	A network share ( a drive letter like M: or S:) mapped to a directory on the server and optionally a subdirectory. Subdirectories are handy if you want to install multiple packages on one server. For example you could put a grade level 9~12 package on a subdirectory called eMapshopHighSchool and a K~5 package on a subdirectory called eMapshopElementary.
	Locate the disk in the package that has the NetworkTools directory on it.