We are using exactly the same setup in our environment. We
have GPO's applied to machines where the MSI-files are located on a
filer.
What you need to be aware of:
- the filer needs to have Kerberos
enabled
- if it is a ntfs qtree the machine accounts need to have
read access - probably "Domain Computers":Read
- the NetApp needs to have a valid user mapping from the
Windows machine account to a valid Unix id.
We have the default Unix user set to:
wafl.default_unix_user
nobody
and have a entry for nobody in
/etc/passwd
nobody:*:65534:65534:Guest for
NT:/root:/bin/sh
I don't believe that we
have configured anything else to get the
software installation working - but I could be wrong - that was some years
ago...
If it doesn't work set the options cifs.trace_login to on
and watch the console for mapping errors.
Carsten
Sorry, I'm applying the GPO to workstations to install
certain software. The software package (the msi) is being housed on the
Filer. When you assign the software to a machine it tries to connect with
the machine credentials and fails.
Steve Evans
SDSU Foundation
What kind of GPO would
you want to assign to a filer? Is the filer part of the
domain?
From: Steve
Evans [mailto:sevans@foundation.sdsu.edu]
Sent: Wednesday, November 24, 2004 10:21
AM
To:
toasters@mathworks.com
Subject:
Group Policy Software Installations
Where trying to deploy a piece of
software via Group Policy. If we assign it to the user it works fine, but
if we assign it to the machine it can't find the source on the
Filer. If we move the installation package to a Win2k3 machine we can
assign it to the machine. Anyone know how to fix this with
Filers?
Steve
Evans
SDSU
Foundation