asked on

windows 2008 active directory OU issues

Hi
we have a windows 2008 R2 std server that has replaced a single W2003 Std server as the only gc server on a single domain, the old w2003 server will at some point have dcpromo run on it and switched off. All data and applications are now working on the new server fine. The process of adding the new server, tranfering GC roles all went as expected.

However, if a PC is now added (after being removed during diagnosis) to the domain (same domain name as before) the computer shows up in the standard "computers" OU list withing AD, not within the "domain name" OU that was created in AD and transfered accross from the old server.

these computers are also experiencing network connection issues (thats why they were removed and re-added), that are intermitent. Like not connectimg to shares, and most supprisingly one of them creates a "temp" local user profile everytime it boots?
I tried removing the few Win7 PCs and re-adding but they still have issues, there are no group policy rules added that i am aware of to the domain OU that would make this happen?

all win xp pcs are working fine, although i have not removed any and readded?
any ideas??

ASKER CERTIFIED SOLUTION

netjgrnaut

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Ackles

I want you to clarify something, you said there are temp profiles.

1) Are the temp profiles still there after rejoining the domain?
2) Did you try to logon with other user than for the one creating temp profile?
3) Does this user get temp profile if logged on another computer?

Try putting this little utility on the computer you are having problem & see if you get green ticket. It should show you status near the clock:

http://www.microsoft.com/download/en/details.aspx?id=23018

If you are not getting authenticated via domain, moving the computer to any OU is not gonna help you as kerberos fails no GPO applies.

Please also check the clock of your W7.

A

Ackles

Please also post errors from Event Logs.
I am sure there would be many interesting errors there.

exact1

ASKER

littele etra info: the win7 pcs were added by another company (before the new server), they worked fine at first but then had issues connecting to other Win7 shares (a requirement), we found out this was an issue with some bundled HP Security Suite and drive encryption software, Once that software was removed the Win7 systems could access other Win7 workstation shares (a i say, a requirement). We also had some network / internet issues at about the same time which threw some confussion in, this turned out to be a DNS ISP issue which was resoleved. Part of the diagnosis also resulted in the removal and re adding to the domain.

netjgrnaut:
thanks, I sort of expected that answer ref OU after I posted it, so manually moving them to the OU that was previously created will be ok, I can confirm that was a standard OU added on the w2003 server without any GP edits. thanks.

Ackles:
thanks, answers to your questions;

1) Are the temp profiles still there after rejoining the domain?
yes, one is created everytime a user (any user inc admin) logs on
2) Did you try to logon with other user than for the one creating temp profile?
yes - creates temp profile
3) Does this user get temp profile if logged on another computer?
No

I have suggested the other company rebuild the Win7 PCs and add to the domain again without the HP software, and see what happens with a vanilla install with all win updates.

I did google and see this temp profile has an issue with the clock not syncing...will look into it.
Being in the wrong OU should not casue the temp profile on the local PC??????

SOLUTION

Ackles

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

exact1

ASKER

I have just suggested exactly that to the Win7 company. Awaiting their response.

Ackles

Any update?

exact1