Thanks for the reply. I know (now) that it is not recommended to install software from the netlogon share, but what I found was that any system that had opportinistic locking disabled would fail to install software assigned through group policy. Either re-enabling opportunistic locking, or creating a new group policy that installed the software from a regular shared folder solves the problem, so it is definately the combination of disabling opportunistic locking and installing from netlogon that causes a problem. Assuming that you have some workstations on which opportunist locking is disabled (we had to do this to prevent problems with our accounting software), then it sounds like I should be good to go moving the msi files to a DSFR volume. Thanks again.
________________________________ From: Miller Bonnie L. [mailto:[email protected]] Sent: Wednesday, February 17, 2010 4:19 PM To: NT System Admin Issues Subject: RE: Windows Installer, opportunistic locking and the Netlogon share I'm not sure I can comment on the opportunistic locking (I may have missed that thread), but Sysvol, which holds Netlogon, uses FRS to replicate. The only time I know of where this isn't true is if you've got 2008+ and have specifically made some changes to use DFSR. I can tell you that we have our msi files on DFSR volumes and have not had trouble with failed installations due to opportunistic locking issues. Prior to DFSR, we used to have them on a separate DFS (FRS) volume and that also worked (waaaay back to Win2k server SP1). We've never installed our MSIs from netlogon. From: Ralph Smith [mailto:[email protected]] Sent: Tuesday, February 16, 2010 10:46 AM To: NT System Admin Issues Subject: Windows Installer, opportunistic locking and the Netlogon share I recently had a problem in which applications assigned through group policy were not installing on some computers, which turned out to be a combination of the fact that I stored the apps in the NETLOGON share, and also had disabled opportunistic locking on the failing computers. This is in a Windows XP SP3, Windows Server 2003 SP2 environment. My question is: When I finish upgrading all of our locations to Windows 2008 R2, with still almost all XP SP3 clients, will I run into a similar problem if I put the application's .msi files in a DFSR share as I had with the 2003 NETLOGON share? I'm not sure what is unique about the NETLOGON share that causes this problem, and wondering if it has to do with being part of a DFS with replication share also. Thanks for any insight. Ralph Smith Confidentiality Notice: ****************** This communication, including any attachments, may contain confidential information and is intended only for the individual or entity to whom it is addressed. Any review, dissemination, or copying of this communication by anyone other than the intended recipient is strictly prohibited. If you are not the intended recipient, please contact the sender by reply email, delete and destroy all copies of the original message. Confidentiality Notice: ---------------------------------- This communication, including any attachments, may contain confidential information and is intended only for the individual or entity to whom it is addressed. Any review, dissemination, or copying of this communication by anyone other than the intended recipient is strictly prohibited. If you are not the intended recipient, please contact the sender by reply email, delete and destroy all copies of the original message. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
