1st DC crashed and 2nd DC will not create profiles when users logon.

Posted on 2010-01-10
Medium Priority
Last Modified: 2013-12-23
I am running Windows 2003 Server and the first Domain Controller has died. I transferred all the FSMO roles and Global Catalog server to the second Domain Controller. When users attempt to login the Login is slow and it kept showing window stating "setting up wallpaper" and it would not disappear. Also no connection via outlook to the Exchange server. I am able to web browse however. After logging out, checked DC02 and not showing any profile for new account.

I am a new Administrator and am very lost can anyone lend some advice? Thanks in advance!
Question by:morarc
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions

Assisted Solution

KGG earned 664 total points
ID: 26276911
Hi there,

Is 2nd DC host name is different from 1st DC. If yes, then you need to incorpates in profile path location for all users.

For example - \\DC1\Profiles$\User1 to \\DC2\Profiles$\User1

Ensure Profiles folder is created and shared with everyone.


LVL 49

Accepted Solution

Akhater earned 668 total points
ID: 26278223
can you explain what you mean by " After logging out, checked DC02 and not showing any profile for new account."

if you go to any user in ad and check its properties does it have a home folder or profile path etc... if so what is it pointing to ?

on what server is your exchange server ? are you sure it is pointing to the correct DNS ?
LVL 31

Assisted Solution

by:Henrik Johansson
Henrik Johansson earned 668 total points
ID: 26278733
Any error in eventlogs or popup on client during logon process?

If you mean that roaming profiles are used, check that the correct path is specified in the profiles tab of the user object in ADUC.
Does DNS configuration on the client (ipconfig/all) point on the correct DNS server? If DNS server isn't available or cen't resolve the internal domain, client will atlast timeout and failover to WINS/NETBIOS name resolving giving lack of logon performance.
If getting a temporary profile due to problem with loading the profile, the profile will not be saved to file server share.

Author Closing Comment

ID: 31675148
All very helpful troubleshooting techniques, thank you!

Featured Post

New feature and membership benefit!

New feature! Upgrade and increase expert visibility of your issues with Priority Questions.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

We recently endured a series of broadcast storms that caused our ISP to shut us down for brief periods of time. After going through a multitude of tests, we determined that the issue was related to Intel NIC drivers on some new HP desktop computers …
Resolve DNS query failed errors for Exchange
Michael from AdRem Software explains how to view the most utilized and worst performing nodes in your network, by accessing the Top Charts view in NetCrunch network monitor (https://www.adremsoft.com/). Top Charts is a view in which you can set seve…
If you’ve ever visited a web page and noticed a cool font that you really liked the look of, but couldn’t figure out which font it was so that you could use it for your own work, then this video is for you! In this Micro Tutorial, you'll learn yo…
Suggested Courses

752 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question