Important Notice: On February 29th, this community was put into read-only mode. All existing posts will remain but customers are unable to add new posts or comment on existing. Please feel to join our Community Discord for any questions and discussions.

Can't access ADMIN$ when system in Computer OU

Alex Rose

November 23, 2015 10:52

Hi.

I'm using PDQ Deploy in conjunction with MDT 2013 to "pull" a package via a Task Sequence.

Overall, it is working well except for one thing. If the new computer sits in the default Computers OU that new domain joined PC's get added to it won't pull the package and shows the computer as offline.

If the computer is somewhere else in our AD structure then the package installs fine.

The ADMIN$ share does not seem to be available for those computers in the default OU.

Can anyone shed some light on this and what I need to do to get round this other than pre-staging the computer account somewhere other than the default OU?

Thanks.

Comments

3 comments

mmuni
November 23, 2015 16:04

sounds like the account that you are using does not have admin access until the PC is moved to an OU that applies the users group to local admins.

0
Brigg Angus
November 23, 2015 21:50

This could also be due to a particular GPO that's applied to the default OU. If you run RSOP or GPResult on one of the machines in the default OU against one in a another container, are the results different, and if so, how?

0
Jason Hanks
December 03, 2015 15:58

Hi Alex,

Did you find a solution to this?

0