[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

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

"Applying Personal Settings" Logon to Domain Delay

We have a few users at one of our remote locations who're experiencing extremely long delays when logging on to the domain in the morning, up to 10 minutes stuck at applying personal settings. My first thought was it might be a dns issue, yet it doesn't affect anyone else in the office. We've tried rebooting the servers which has helped a little ( but not enough ). I tried adding each specific users domain name as an account on their individual machines and that didn't do anything either. I should mention that if I have them log on as local administrator this issue doesn't happen...only when trying to log on to the domain either as the user or domain admin.

Any help would be greatly appreciated



Casey
0
logan510
Asked:
logan510
  • 6
  • 5
1 Solution
 
Mad_JasperCommented:
It could be a DNS issue on the local machines if their DNS settings are not pointing to an internal DNS server. If the DNS settings on the machine are pointing to an external DNS server, login times can be lengthy.

Do the users use roaming profiles? There are several issues related to roaming profiles that may cause that problem.

It could be the user's local profiles. Try renaming the user's current profile and allow the user to log in and recreate the profile. If the user logs in in an acceptable amount of time, move the users documents, favorites, desktop icons, etc. to the new profile.
0
 
Mad_JasperCommented:
The preferred method of configuring DNS is to point your internal clients to your internal DNS server and then to have external queries forwarded to the external DNS servers.

GL
0
 
logan510Author Commented:
No roaming profiles are being used.
0
Nothing ever in the clear!

This technical paper will help you implement VMware’s VM encryption as well as implement Veeam encryption which together will achieve the nothing ever in the clear goal. If a bad guy steals VMs, backups or traffic they get nothing.

 
Mad_JasperCommented:
Have you checked the local DNS settings on the troubled computers?
0
 
logan510Author Commented:
If everyone on the domain at this office was configured the same way and their PC's imaged using the same standard, why would it be a dns issue? Just curious.






Casey
0
 
Mad_JasperCommented:
Well, I was confusing your question with another question.

I would look at the local profile issue. Rename the users current profile and have user log in again. A new local profile will be created that is void of all the junk and clutter that can be associated with user profiles. If the user now logs on quickly, then he/she had a corrupt profile. Necessary files can be copied from the old profile to the new profile. I would limit copying files to desktop icons, my documents, and favorites. You don't want to copy that which may have corrupted the profile in the first place.

You may want to consider any login scripts that may run when the user logs in, such as a mapped drive to discontinued shared folder.

GL
0
 
Mad_JasperCommented:
Any news yet?
0
 
logan510Author Commented:
My boss doesn't believe it's a profile issue, he thinks it has to do with the network. I found a fix that might work in group policy that has the user waiting for the network at logon as opposed to using the cached credentials. This may work, but what about the people with laptops who travel and try to logon with their profile? If it's waiting for the network and there is no network, will they be able to logon to their laptops? I appreciate all the suggestions so far btw.



Thanks
Casey
0
 
Mad_JasperCommented:
Well, I misread you original post. I thought you are able to log in ok with the domain admin account. Read the explanation for the group policy before making changes. Unless I use roaming profiles, I always leave that default.
0
 
logan510Author Commented:
Well, we tried a regkey fix that has appeard to work...but not on everyone's PC. My bos and I continue to look into the issue as one of our other remote locations is starting to report similar problems.





Casey
0
 
logan510Author Commented:
With some help from Microsoft we were able to correct the problem. The main fix was lowering the MTU size, too many packets were being dropped and/or fragmented. Once we lowered the MTU at each remote location...logon times went from 5-10 minutes to less than 30 seconds.
        Since nobody came up with the answer, or comment that led to the answer I'll be requesting a mod close this topic. Thanks to everyone for the feedback, it's appreciated.





Thanks
Casey
0
 
GhostModCommented:
Closed, 500 points refunded.

GhostMod
Community Support Moderator
0

Featured Post

Veeam and MySQL: How to Perform Backup & Recovery

MySQL and the MariaDB variant are among the most used databases in Linux environments, and many critical applications support their data on them. Watch this recorded webinar to find out how Veeam Backup & Replication allows you to get consistent backups of MySQL databases.

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