[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 333
  • Last Modified:

AD Permissions problem with new server

Newly joined Windows Server 2008 R2 computer to a newly set up domain -- when logged in as a new (domain) user (with domain admin permissions) -- can't run anything.   You get this message:

"Windows cannot access the specified device, path or file.  You may not have appropriate permissions to access the item."

If you log in as a local machine user - everything runs.

I've never seen this problem before.
0
paulflint
Asked:
paulflint
2 Solutions
 
BawerCommented:
try giving the domain user permission on C drive and other drives, also note that you may not have setup a roaming profile and the profile is not loading....
0
 
paulflintAuthor Commented:
Yes but this doesn't make sense - you don't HAVE to use roaming profiles with domain workstations and as for drive permissions -- howcome I don't have this with another 100 PC domain I can add brand new computers to with no problem .. !!

Paul
0
 
petelettinCommented:
is the time in sync

Pete :-)
0
The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

 
paulflintAuthor Commented:
petelettin -- yep, time is all synced !

paul

The problem seems to be with the active directory and group policy -- it just isn't being picked up by the newly joined server.
0
 
Will SzymkowskiSenior Solution ArchitectCommented:
I would recommend using rsop.msc on the problematic machine. This will allow you to troubleshoot the GPO issue on this machine. You can also use gpresult /v. This will also give you detailed information, to see what is exactly being applied to the machine.

Another thing you can do is check the event viewer as this will also help...
0
 
MisterTwelveCommented:
HI.
I try this
1. disjoint machine from domain
2. reboot Machine
3. Join Machine to domain again and reboot again.
I think this resolve the problem
0
 
paulflintAuthor Commented:
Problem lay with VM images -- needed to run sysprep WITH "generalize" as security tokens were conflicting and AD just didn't like the imposter machines (vm's).  Sysprep with generalize .. THEn join domains, etc. - all good.   Thanks all.
0

Featured Post

Never miss a deadline with monday.com

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now