9 replies
by jimbb
by cgrasso
by drdon
You should be sure that the users have access to the imagenw server. Container login script could be used and then map K:=imagenw\
I also would make sure both servers are in the same container if possible.
by cgrasso
by keithpup
I think that it would be easiest to add a line that pionts to next available server instead of a specific letter (thus avoiding mix up over users specific mapping)
Map next imagenw\sys:data or
map k:=imagenw\sys:data
by cgrasso
These answers are all correct, however they ignore one aspect of this problem.
SnapServers support bindery, but NOT Directory Services.
You will need to create a bindery attachment to the server, as well as creating new user IDs for everyone on the snapserver.
If you run NT on the desktops, and security isn't too much of an issue, you COULD set up 1 ID for everyone, and sign them in with net use k: \\imagenw\volumename /user:xxx password. (I THINK you can, anyway...)
Sorry I didn'thave better news for ya.
Kev.
by cgrasso
by cgrasso
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending