John,
 
At one point I had a similar issue.  Instead I used a GPO for the
users.  Within that I ran a script and used credentials that would allow
it to run.  That was under scheduled tasks.  Just another option.
 
Tom

>>> "Kelsey, John" <[email protected]> 8/24/2010 3:00 PM >>>

The DFS root share is located on the DC.  Should I move the DFS root
share over to the file server?  Maybe having it on the DC is messing me
all up?  Whats the best practice there?
 

From: Miller Bonnie L. [mailto:[email protected]] 
Sent: Tuesday, August 24, 2010 2:39 PM
To: NT System Admin Issues
Subject: RE: 2008 DFS Question

 
Where is your DFS root share located?  If it’s not in the same
location, you might need to add Domain computers there as well.
 

From: Kelsey, John [mailto:[email protected]] 
Sent: Tuesday, August 24, 2010 10:59 AM
To: NT System Admin Issues
Subject: RE: 2008 DFS Question

 
But where does the computer account need permission at?  I have both
the share and NTFS at ‘everyone’.  Isn’t ‘everyone’ in fact everyone
(including computer accounts) ?
 

From: Paul Hutchings [mailto:[email protected]] 
Sent: Tuesday, August 24, 2010 1:54 PM
To: NT System Admin Issues
Subject: RE: 2008 DFS Question

 
I think you’ve answered your own question?  To deploy software via GPO
to the computer, the computer account needs to have access to the files,
so as you said you need to do whatever you usually to assign permissions
to a group that contains the computers (or use something like Domain
Computers).
 
Paul
 

From: Kelsey, John [mailto:[email protected]] 
Sent: 24 August 2010 18:51
To: NT System Admin Issues
Subject: 2008 DFS Question

 
Single namespace on a 2008 domain controller. Target resides on a 2008
file server.  DFS links work just dandy for users.  They can browse the
the links, install software, etc.  HOWEVER…when deploying software to
the computer using the DFS path, the install fails saying the ‘location
is unavailable’.  Software deployment to a user works just fine.
 
I’m convinced it’s a security setting somewhere, almost like the
computer account can’t access the DFS path.  When I add the computer
account to the ‘domain users’ group, the deployment succeeds.
 
I’ve checked the share permissions on the target, NTFS permissions on
the target and those look ok.  Is there something I need to do special
to allow computers accounts to read DFS paths?
 
Thanks all!!
 
*************************************
John C. Kelsey
DuBois Regional Medical Center
(:  814.375.3073  
2  :   814.375.4005
*:   [email protected] 
*************************************
 

 

This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they are
addressed. If you have received this email in error please notify the
system manager. This message contains confidential information and is
intended only for the individual named. If you are not the named
addressee you should not disseminate, distribute or copy this e-mail. 
  
  

 

This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they are
addressed. If you have received this email in error please notify the
system manager. This message contains confidential information and is
intended only for the individual named. If you are not the named
addressee you should not disseminate, distribute or copy this e-mail. 
  
  
 
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they are
addressed. If you have received this email in error please notify the
system manager. This message contains confidential information and is
intended only for the individual named. If you are not the named
addressee you should not disseminate, distribute or copy this e-mail. 
 
 

Confidentiality Notice:  This e-mail message, including attachments, is
for the sole use of the intended recipient(s) and may contain
confidential and privileged information.  Any unauthorized review, use,
disclosure, or distribution is prohibited.  If you are not the intended
recipient, please contact the sender by reply e-mail 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/>  ~

Reply via email to