I work for a software development company and the company uses a development
tool called Forte (product of Sun Solaris). Through this application, we
access information on our network through mapped drives. In the past with
Windows NT Server and Windows 2000 Server, we would have the Forte Service
log on as a network account and the Forte application would see the mapped
network drives on the local machine.

This doesn't work with Windows 2003. I stopped the Forte Service and tried
running Forte as an application on the server and it finally recognizes the
mapped network drives.

So my questions are these: What is the difference between how Windows 2003
runs services compared to Windows 2000 and earlier? How can I get the
application to see the mapped network drives in Windows 2003?

Talthax wrote:
I don't think Win2003 is any different from any older version.
Generally, services don't use login scripts/mapped drives. Services are
designed to run when nobody is logged in, and mapped drives are for the
convenience of real people, not for computers. Can you not just have it use
a UNC path? If not for some reason, can you use a scheduled batch file to
map the drive with the credentials it needs?