Need help with server application installation...

Dew itt right

2[H]4U
Joined
Oct 28, 2005
Messages
3,314
I'm building a new server for a family friend who owns a body shop. The server uses Windows Server 2003 and connects to 4 workstations via a switch. The current problem I'm having is with the installation of the claim/estimate software installation. When you start the installation it asks you to choose a "drive letter to associate with the destination location" and to make sure that the letter chosen is available on all connected workstations. I assume this means it's mapping the shared folder with the drive letter chosen? However no matter which drive letter I choose I get the following error message:

"The drive letter associated to the destination location could not be created. Setup cannot proceed and will exit"

Any ideas? The software being installed it Mitchell's Ultramate 7.0...
 
Ahh Mitchells.....

Create a share...and give that share full rights to start off with.
Using the substitute command, make a batch file to substitute a drive letter on the server for that share. Plop that in the startup folder if you want, so every time the server reboots, the script makes the substituted drive letter. That drive letter you use for the subst drive should be the same drive letter workstations use to see this share.

Now install to that path.
 
I'm sorry but I have no idea how to create batch files. My networking skills are pretty sub-par. I guess I didn't assume this would be that complicated. Are there any tutorials or references you could point me to to help with this task? It almost sounds like making a mapped drive, no?
 
Right click a blank area like on the desktop, new, file....call it, oh, sub.bat
Accept the prompts of changing the extension.
Now it will have that batch file look for an icon, sort of like a box.
Right click, edit...and type in the following for example..assuming your Mitchell folder that's shared is in the root of drive D on the server.

subst n: d:\mitchell

Now once saved, copy that file to the startup folder.

Or, you can actually on the server you can actually map a drive to the share just like you were at a workstation. Whichever way works easier for you..if you want to do mapping like on a client workstation, no problem....6 of one, half a dozen of the other...same end result. :)

I'm guessing that you're set up the Windows server in just workgroup mode...which in all honesty is fine for a little 4x PC shop.

Some tips for ya...encourage the boss of the garage to insist that nobody..NOBODY..uses the server as a workstation. Just let it sit in the corner doing nothing but serving.

Beef up the security on the workstations, a good antivirus, some additional malware protection, Firefox as a browser. Shop guys love the XXX stuff, and you'll have porn dialers on these PCs in no time.

Get those industrial waterproof rubber flexible keyboards for the shop PCs.
 
When I map the drive and run the installation it removes the mapped drive letter from y list of options. So I started the installation process up to where it lets me choose the drive letter, pick an available one, THEN map the shared folder to that drive letter, then press ok on the installation. This seemed to work and the files started installing until I got this error message...

error1.bmp


When I click okay this pops up...

error2.bmp


...and the installation stops. Any ideas?
 
Been a few years since I've installed Mitchell.....are you supposed to run the install/setup FROM/ON the server, or from a workstation pushing the netsetup/workstation/data setup files to a mapped drive ON the server..as in, across the network?

Can we assume that the server is healthy? Hasn't been sitting at this garage and possibly infested with malware?
 
For multiuser setup it gets installed on the Server and the workstations get installed from a mapped drive on the server. And I just built the server this week so yeah, it's clean. I'll see if tech support is open on weekends...
 
Back
Top