• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 10320
  • Last Modified:

stuck on applying security policy to the system

I had to unjoin a compute from the domain.  i added it to the workgroup under the same computer name.... rebooted that computer

i went to the 2008 active directory server. deleted the computer account from ou

went back to the computer and added it to the domain.
computer rebooted fine and i logged in with domain admin credentials and it is stuck on
applying security policy to the system...
been this way for 30 minutes...

the computer does show up in active directory users and computers...
any ideas?
0
jamesmetcalf74
Asked:
jamesmetcalf74
3 Solutions
 
BCipolloneCommented:
Hmm....  Verify that in AD the computer has the correct security groups applied

If so...
unplug the network cable.  Login, plug the cable back in and blow away any network settings...

netsh winsock reset
ipconfig /flushdns
arp -d *
ipconfig /release
ipconfig /renew

try again

0
 
hvillanuCommented:
Hi,
Instead remove the computer of the AD,  Try to reset the computer object/account.

In case you have more than one DC run on a DOS prompt
C:\>gpupdate /force

Then on the computer
1) un-join and restart
2) Rejoin and restart but login with local account
3) Restart and login on the domain, with an AD account without custom group policies.

-hope helps-
0
 
SandeshdubeyCommented:
First you need to disjoint the PC from domain.

Login to DC open active directory users and computers delete computer object of the disjoint PC.You also need to delete the old computer name assigned to PC.

Open the DNS console delete the host A record and ptr record of the PC.Here also delete both old and new record of the PC.

Wait fot the replication to happen between the DC's if multiple DC exist in the network.Once the done Join the PC to domain.This should fix the issue.thanks
0
 
J.R. SitmanCommented:
thanks for all the help, but nothing worked. Had to take a drive from our other server and put it in. The drives are mirrored so putting the bad one in the other server, it rebuilt it.  We disconnected the bad server from the network, renamed it with the new drive and changed it's IP.  All is good.
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

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