Link to home
Start Free TrialLog in
Avatar of Jeff Perkins
Jeff PerkinsFlag for United States of America

asked on

Windows 7 domain logon issues.

I am promoting systems to a domain, no problems until one particular machine is giving me a fit.
Windows 7 pro.  Joined domain with no problem.
Added domain user to local admin group (for my purposes to add various software)
logged in with user account, profile created no problem
logged out, logged back in with admin account and used 'windows enabler' to allow me to copy the old user profle to the new user profile, created when logging into domain. (i've used this and done this procedure without any problems in the past)
still no suspected problem until
I log into user on domain and it logs in then before desktop even appears it logs me back out to log in screen.
Avatar of btdownloads7
btdownloads7
Flag of United States of America image

Something obviously went wrong when using Windows Enabler. Can you log in as any other user (either on local machine or domain)? If so, you'll want to delete the user folder for that new profile created for the domain user and let it re-create it on next login. You should really do the profile transfer manually instead of using Windows Enabler to endure it's done properly.
Avatar of Jeff Perkins

ASKER

ok, profile transfer manually, you mean just copy all the stuff in the user profile folder to the new one?
I can log in as the local profile, as well as admin and so on, have already deleted and tried the same steps over, I think there may be something in the old profile which is causing a problem, but don't know where to start looking ....
ASKER CERTIFIED SOLUTION
Avatar of btdownloads7
btdownloads7
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
sounds like userinit.exe errors associated with spyware.

check registry to invalid entries for userinit


HKLM\\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\Userinit

the normal value is
C:\WINDOWS\system32\userinit.exe
definitely not the infection issue Harel, already knew about that, but thanks for the try.
I think you hit the nail on the head BT with conflicting credentials. this is the only user on my network where there was same user name as the new user on domain. this network was a mess when I got here, have put a lot of time in getting them set up right and this one wass last and most important machine. seems I'll have to try a change to different user credentials and see if that will allow it.
I can't even copy the usual stuff from the old profile, because when I do, it won't allow me to even run explorer.exe. I tried just copying folders without user.dat and the accompanying files.
I'm going to try creating a whole new user with different login name and see if I can do it that way... she has way too much stuff to copy everything and it's getting late on a sat... wish me luck.
I'm not suggesting it's infected, just that it sounds like a userinit issue with the logon/logoff thing.

what does the user account do on another machine?

harel,
the local user profile works fine, and so does the domain profile after it's just created... but if you copy the stuff from the local profile to the new domain profile that is when you have issues... and yes thank you, I've checked userinit and made all confirmations in the registry concerning that....
anything weird in the user's startup folder in start menu?

are you moving everything from the old profile? or just documents, favorites, desktop, pictures and music?

yeah I get it, not userinit :) i wasn't trying to keep harping on it.
I looked through everything I could find, I think bt hit the nail on the head, I believe it was a case of too close info. Could have been something that was done by previous tech.  
  As a last ditch effort, I recreated a new user in the AD, changed her name a tad and then copied the entire contents of local profile and everything worked like a charm.  
   I appreciate your help, and apologize if I sounded snippy, was just getting late on a Sat and really tired...
The solution was to create an entirely new profile in the AD and copy contents of the needed profile.  The answer given pointed me in the right direction and was very helpful in eliminating possibilities.
I converted a network and the owner INSISTED on same domain, same usernames, same passwords, and not formatting the terminal server, so like $5000.00 (2 Microsoft cases)and 2 weeks later, we finally got all the weirdness worked out.  it's amazing how many places a windows AD can cache user info:)
Worst part was, they had a 6k server sitting there, a workgroup of 11 machines, 4 of them home edition, none of the files or dbases on the server, another old NT server running that wasn't even being accessed, no domain setup, no security, scattered spatterings of antivirus, the only thing the dell server was being used for was to transmit the daily invoices via fax software....LOL  
   Taken a while to get this one straightened out... about half of the users were registered as sbs users, but for what I'm really not sure....
You been stealing my customers?  the owners son is probably a programer and set it all up, and dad is real proud :)
Actually, they had an IT guy come in, but I can't say anything bad about him now... he just recently passed away....
died of guilt? sorry bad taste ;-)