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
Steve,
We discovered the same problem when we tried deploying software using GPO in AD. The only way we could do it in the end was to use a share on a Windows server and not use the filer at all. This wasn't a problem in our case because the .msi file was tiny.
Microsoft would say this is one reason why you should buy a "Windows Powered NAS box" as it enables all Windows server specific functions to be utilized as if it was a Windows server.
We would say of course the only reason why we didn't buy a Windows powered NAS box was because we want it to be reliable!
Anyway if anyone has a way around this problem, I am all ears.
Kind regards, Richard
----- Original message ----- From: "Steve Evans" sevans@foundation.sdsu.edu To: toasters@mathworks.com Date: Wed, 24 Nov 2004 10:20:53 -0800 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
-
Richard Collins -
Steve Evans