Click here to try ElectraSoft's software for FREE
Click here to try ElectraSoft's software for FREE

Message threads about security and running as a service issues:

===================================
============ Message 1 ============
===================================
   From: Riley J. McIntire
     To: Jon Krahmer
Subject: HardDrive Security

Hi Jon,

We received the upgrade, and appreciate it.

I thought you might be interested in what we had to do get it working as 
a service.

I don't know about most of your customers but here we needed for security 
reasons to install Faxmail in a directory other than ?:\faxmailn. It was
actually e:\fax\faxmailn.

This worked fine when manually starting it. Using NT 4.0, we simply
shared e:\fax as \\server\fax, and connected x: to \\server\fax on the 
same server. Thus we had x:\faxmailn as the faxmail directory.

This didn't work after installing as a service. We get an error like
"File does not exist" for x:\faxmailn\faxmodem.cfg. Also other, similar
errors for this file as I played around trying to get it to work.

Anyway, what I found was using a substituted drive instead of a mapped 
drive worked:

SUBST X: E:\FAX

As you probably know, this doesn't "stick" after a reboot. What I ended
up doing was making a batch file (called it FMNW.BAT) and edited the 
registry to reflect the name change. In the batch file I put the
substitute command and it worked fine.

I would think there's a more elegant way to do this, but I can't think of 
it now. Anyway, I thought you might be interested...

Thanks again,

Riley

===================================
============ Message 2 ============
===================================
   From: Jon Krahmer
     To: Riley J. McIntire
Subject: FMNW.BAT contents

Hello Riley,

Can you give me the lines in your FMNW.BAT please?

         Kind Regards, 
         Jon Krahmer, ElectraSoft

===================================
============ Message 3 ============
===================================
   From: Riley J. McIntire
     To: Jon Krahmer
Subject: RE: FMNW.BAT contents

Hey Jon,

If we want faxmailn as a directory off the root of some drive, say x:, and 
faxmailn is a sub directory of e:\fax:

@echo off
%systemroot%\system32\subst.exe x: e:\fax
x:\faxmailn\fmnw.exe

If you call the above FMNW.BAT, where you edit the Parameter key with the
registry string (in your example):

?:\faxmailn\FMNW.EXE

one has to change it to 

?:\faxmailn\FMNW.BAT

Might be an idea to call the batch file something else for the sake of 
clarity.

I also noticed an "orphan/inactive" command window on the desktop after 
making the above changes and doing a test boot. It doesn't hurt anything,
but I don't care for it. Haven't had a chance to play with it yet to get
rid of it.

Cheers,

Riley

===================================
============ Message 4 ============
===================================
From: Riley J. McIntire
To: Jon Krahmer
Subject: RE: FW: Upgrade policy

Hi Jon,

I don't have the last email that went between us so I hope you remember 
this...

If you recall, you requested a batch file for your customers use in 
starting FaxMail as an NT 4.0 service. I sent you the one I was using,
but hadn't had time to redo it--it left an open command window--this one 
works better.

I just added the start and exit commands and it starts up cleanly

Listing of FMNW.BAT

@echo off
%systemroot%\system32\subst.exe x: e:\fax
start x:\faxmailn\fmnw.exe
exit

Cheers,

Riley

===================================
============ Message 5 ============
===================================
From: peter@helpnet.com.au (Peter Moulding)
Subject: Service surprise
Date: Mon, 7 Apr 1997 22:50:15 +1000
X-MSMail-Priority: Normal
X-UIDL: 55edd90ff29711abd33d3e58193590e0

Hello Jon,
Your customers using Faxmail as a service may be interested in another 
way to reassign disks.

Services run with a unique user id. Therefor they are not authorized
to use normal permissions. The batch process gives us the flexibility
to create the assignment under the user id of the batch process.

Assume directory Faxmailn is on a server as \fax\faxmailn and \fax is 
shared as \\server\fax. To use a batch procedure to create assignments,
go to the network client and:

Step 1:
Create a small batch procedure c:\runfax.bat containing:
	net use x: \\server\fax
	x:\faxmailn\fmne.exe
	net use x: /del

Point the scheduling service to c:\runfax.bat. In the Electrasoft
srvany http://www.electrasoft.com/srvany/ example, at step 9 replace:
	?:\faxmailn\fmnw.exe
with
	c:\runfax

Runfax.bat lets you insert any type of network connection. As runfax is
running under the user id of the scheduled service, runfax creates 
assignments with the right security id.

You could use the batch procedure to include a backup of a local user 
directory to the server. Assume user Fred creates all his letters to
customers in directory c:\cust, you could include, in Fred's Runfax.bat, 
the line
	xcopy c:\cust\*.* x:\Fred\cust\ /s/e/v

Peter Moulding
HelpNet
Helping PCs survive January 1, 2000

===================================
============ Message 6 ============
===================================
From: geir@nordic-innovator.no (Geir Hansen)
Subject: NT service on mapped drives
Date: Fri, 28 May 1999 11:18:13 -0000

Hello Jon,

Your customers using 32BitFax or FaxMail as a service on NT, may be 
interested in another way to reassign disks.

The problems with doing as the examples shown on your web site, is that by 
using a batch file as a "fake" service, you can't start and stop the Fax 
service manually.

In the Resource Kit for Windows NT (and on several download sites on the 
Internet), you can find an installable service called AutoExNT. The 
AutoExNT service allows you to run a custom batch file (AutoExNT.bat) when 
you start the computer, without having to log on to the computer.

Example:
Assume you have installed the 32BitFax into two mapped network drives as 
this: Workstation disk = M: (mapped to the shared directory 
D:\Fax\Program) Server disk = N: (mapped to the shared directory 
D:\Fax\Data)

1)
Create AutoExNT.bat with these lines:
@%systemroot%\system32\subst M: "D:\Fax\Program" > NUL: 2>&1
@%systemroot%\system32\subst N: "D:\Fax\Data" > NUL: 2>&1

2)
Install the AutoExNT service running the batch file above, and restart the 
computer.

3)
Install the 32BitFax as a service as described in your document "Run 32bit 
Fax as an NT Service" as disk M: and N: were real drives. When you edit 
the registry also add this:
Under the registry key for your service (eg. 
HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/FaxMailSrv), add the key 
Linkage. Under the key Linkage, add a value with name = OtherDependencies, 
data type = REG_MULTI_SZ and string = AutoExNT

This way, you can start and stop the Fax service as normal with NT 
utilities.


Geir Hansen
Nordic Innovator AS
geir@nordic-innovator.no