Thanks!
The original creation of the map needs to be done at command line
(originally (years ago) an SFU hotfix patch was required to create maps with
a (.) in them) but after that they are fairly easy to maintain using
ADSIEDIT. Once you have a working NIS for the standard maps use nismap
create to generate the structure for your master and other maps.
nismap create -i1 -g" " -y auto.master
nismap add -a MYDOMAIN -s MYSERVER -e "/home yp:auto.home" -r yes auto.master
You can add other maps to your master. We use auto.home, auto.tools, and
auto.util.
Then create your auto.home structure...
nismap create -i1 -g" " -y auto.home
and add entries to it
nismap add -a MYDOMAIN -s MYSERVER -e "user HMSERVER:/home/user" -r yes
auto.home
Check at each stage that things are what you expect with the yp* commands
from command line on the server or any client. Once your maps look correct
you may need to adjust your /etc/nsswitch.conf on the *nix side of things.
Once things are working you can add, del, and modify with the nismap command
line but it is just as easy to use adsiedit.msc and modify things directly.
If you have multiple servers make sure you do a yppush from the master to
propagate things.
Post back with questions or if you need additional help.
At our site things are constantly getting moved around to different
locations. With automounting it's a simple matter of moving the resource and
changing the autofs pointer. This really provides for a lot of admin
flexibility and a great amount of transparency to users.
--
David Thomas Hodan
Thanks for the examples. It's a HUGE help as MS provides none.
Thanks again,
Lewis
- Ashish
/custsvc auto_custsvc
/export auto_export
/public auto_public
/home auto_home -nobrowse,proto=udp
/- auto_direct
/export/users auto_home -nobrowse,rw,hard,bg
/xfn -xfn
I deleted one of the entries as follows:
C:\Documents and Settings>nismap del -a genband -k "/custsvc" auto.master
Activity = Removing map = 'auto.master'
SUCCESS
Removing object. object = 'CN=/custsvc'
DN=
'CN=/custsvc,CN=auto.master,CN=genband,CN=defaultMigrationContainer30,DC=genband,DC=com'.
SUCCESS
removing NIS entries from AD
Looks good right? But when I ypcat the auto.master map again the /custsvc
entry
is still there!! Why is this? I could understand if I was running the
ypcat command on a NIS client or other slave server as the propagation might
not have happened yet. I daresay that even if I wait till tomorrow the entry
will still be there. Other changes seem to take affect quickly, why not with
this one?
Thanks.
- Ashish
Thanks for the reply. I just applied the hotfix, rebooted the server, and
then
deleted the entry from auto.master. It won't even let me delete the entry
now
even though it appears to be there:
C:\ypcat -d genband -k auto.master
/custsvc auto_custsvc
/nt auto_nt
/export auto_export
/public auto_public
/home auto_home -nobrowse,proto=udp
/- auto_direct
/net -hosts -nosuid,nobrowse
/export/users auto_home -nobrowse,rw,hard,bg
/xfn -xfn
C:/nismap del -a genband -k /custsvc auto.master
Activity = Removing map = 'auto.master'
FAILURE
No map entry found
object class = 'auto.master', key '/custsvc'.
FAILURE
removing NIS entries from AD
What the heck is up with that??
Thanks,
Ed