B
Bill P
I have a problem when running an application on a group
of Network Load Balanced servers. The application demands
that they share some common storage. This is most cheaply
and easily provided by making a drive mapping on each of
the servers to the common area.
But drive mapping requires that a user logs in to make
that mapping and these servers can sit for weeks without
anyone logging into the desktop. So we dug out the
old "run command as a service" and set it up with a "net
use" command to make the mapping at boot time. Best
practise and the network security made us run this
service as a named user rather than the "local system"
account. The application services are also run by the
same named user, so they always see the common drive.
The problem I have is that other users logging into the
desktop on the servers do not see the mapped drive. Best
practise suggests that the account running the service
should not be allowed to login to the desktop. But when
our "support" user logs in to perform some maintenance,
they cannot see the mapped drive.
Is there any way I can make a mapped drive visible to all
users? Or are drive mappings so tied up with user
profiles that I have to accept the status quo. Any chance
with using something in the "all users" profile?
Thanks for reading this far and for any suggestions.
Bill
of Network Load Balanced servers. The application demands
that they share some common storage. This is most cheaply
and easily provided by making a drive mapping on each of
the servers to the common area.
But drive mapping requires that a user logs in to make
that mapping and these servers can sit for weeks without
anyone logging into the desktop. So we dug out the
old "run command as a service" and set it up with a "net
use" command to make the mapping at boot time. Best
practise and the network security made us run this
service as a named user rather than the "local system"
account. The application services are also run by the
same named user, so they always see the common drive.
The problem I have is that other users logging into the
desktop on the servers do not see the mapped drive. Best
practise suggests that the account running the service
should not be allowed to login to the desktop. But when
our "support" user logs in to perform some maintenance,
they cannot see the mapped drive.
Is there any way I can make a mapped drive visible to all
users? Or are drive mappings so tied up with user
profiles that I have to accept the status quo. Any chance
with using something in the "all users" profile?
Thanks for reading this far and for any suggestions.
Bill