i m looking at windows workstation users switching to linux workstations all of them are authenticated by windows AD domain controller. the windows AD has some logon scripts which do not run on linux some the scripts are as below to map shared drives on the file server NET USE G: \\172.16.2.2\FINANCE NET USE G: \\172.16.2.2\AUDIT linux by default doesnt recognise these scripts. can Wine help me here??
iinfi wrote:> i m looking at windows workstation users switching to linux workstations > all of them are authenticated by windows AD domain controller.No, Wine does not support windows netowrking in any way shape or form. You'll have to use Samba for that.
samba doesnt detect the AD logon scripts either .... hence i was looking for an alternative. thanks... do you know any workaround where AD logon scripts like net use d: \\192.168.5.1\share can be detected at logon on linux workstations authenticating from windows AD we are looking to migrate 200 odd windows workstation users to linux n hence using using fstab and automount using pam_mount is not feasible as this would mean locking users to their own workstations and everytime a user needs something additional .. the sysadmin will v to change the fstab file on the client machine. thanks for your time
iinfi wrote:> samba doesnt detect the AD logon scripts either .... > > hence i was looking for an alternative. > > thanks... do you know any workaround where AD logon scripts like > > net use d: \\192.168.5.1\share > > can be detected at logon on linux workstations authenticating from windows AD > > we are looking to migrate 200 odd windows workstation users to linux n hence using using fstab and automount using pam_mount is not feasible as this would mean locking users to their own workstations and everytime a user needs something additional .. the sysadmin will v to change the fstab file on the client machine. > >And the last is a problem? That is called SECURITY and you should be enforcing it, not allowing your users to install whatever they feel they need. James McKenzie
sorry u misunderstood me. incase of windows ad, incase of any change in user/group requirements akk the sysadmin needs to do is to make a change to group /user policies at the AD server. here you will need to change/edit the file at the user end.
iinfi wrote:> sorry u misunderstood me. >I did not misunderstand you, I did not have all of the facts on what you were trying to do.> incase of windows ad, incase of any change in user/group requirements ask the sysadmin needs to do is to make a change to group /user policies at the AD server. >Good security practice, but do you have a policy in effect on how configuration changes are made and recorded? Otherwise, this could become a security risk and a lot of effort.> here you will need to change/edit the file at the user end. > >This is not good. However, Wine does not work with Active Directory at this point. I would like to see the bridge implemented, but this is a great deal of effort and maybe outside the scope of this project. Others would have to make that judgement call. All I do is work with the Wine code and Macs. James McKenzie
On Sun, Feb 8, 2009 at 7:37 PM, iinfi <wineforum-user at winehq.org> wrote:> sorry u misunderstood me. > > incase of windows ad, incase of any change in user/group requirements akk the sysadmin needs to do is to make a change to group /user policies at the AD server. > > here you will need to change/edit the file at the user end. > > > > > >Would nfs be feasible? -- -Austin
austin987 wrote:> Would nfs be feasible?How's it any different then cifs? Mount is a mount regardless of what FS it is. OP, the only thing I'd recommend write a script for user to grab the logon script from AD, parse it and add appropriate mounts. Shouldn't be too hard to do. And you don't have to add anything into fstab.
thank you. i m not good at scripting. i will chk how i can pull the scripts from AD and parse them.
@vitamin do you know where the AD scripts will be stored in linux box when the user logs in? if know this. then i sud be able to parse it to make the AD scripts work