We are consolidating our data from hard drives on multiple client
systems onto a single high performance file server. We want to make the
data move transparent to the client systems on which we are replacing
local disk with a share from the server (call it "bigserver").
We are using Windows XP on the clients and Windows 2003 on the server. We are running Active Directory.
For example, on client system "A", there is a 300GB local disk known as
E:. We copy the data to a share on the file server, being careful to
preserve permissions, etc., and putting it into a share called
"a-edrive". We create a GPO for client system A that includes a startup
script. The startup script looks like this:
net use e: \\bigserver\a-edrive
The drive mappings are updated on client system A so that we can use e:
for the network share. We reboot client system A, and E: is now mapped
to the share on bigserver. However, some things don't work right.
Services that start at boot time see the data, but don't seem to have
the right credentials to get full access.
What do we need to set up to make sure the client system has the same
access rights to the mapped E: as it did to the local disk?
We'd also like to preserve permission checking so that other users or
systems on the network don't have full access to the share unless there
are permissions that entitle them to such access.
Each of the client systems will end up with a dedicated share that is
used by that client system to replace one or more local disks.
This change needs to be transparent to any installed applications, as we
don't want to reconfigure application settings.