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. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
