Windows Server 2003
--
Questions
--
Followers
Top Experts
I have recently installed windows 7 on some computer in the organisation to test it out. I have three test computers connected to the production network now. All of them with clean installations of windows 7.
My problem is that all of the three computers uses 6 - 7 minutes to logon to the user account. Every computer with a different useraccount. The same accounts are fast on WinXP. The AD server is a windows 2003 server. There are some folder redirection on my documents etc. There is also a login script for mapping some drives and printers.
I've attached the gpsvc log from one of the computers.
Does anyone see what causes this and knows how to solve it?
Here is some "cut &Â paste" from the log where the time has some big jumps.
FIRST ONE... Seems to be a problem with Network location awareness...
GPSVC(4b8.5ac) 18:14:37:134 Waiting for NlaSvc failed with 0x0
GPSVC(4b8.5ac) 18:14:37:134 Wait for network connectivity timed out... proceeding to apply policy.
GPSVC(4b8.5ac) 18:14:37:134 NlaOpenQuery failed with 0x6ba
GPSVC(4b8.598) 18:16:38:944 Target = Machine
SECOND...
GPSVC(4b8.bc0) 18:17:57:290 Target = Machine
GPSVC(7f0.1f4) 18:17:57:296 Client_RegisterForNotifica
GPSVC(7f0.1f4) 18:17:57:303 CGPNotify::RegisterForNoti
GPSVC(7f0.1f4) 18:17:57:310 CGPNotify::RegisterForNoti
GPSVC(7f0.1f4) 18:17:57:317 Client_InitialRegisterForN
GPSVC(4b8.bc0) 18:17:57:323 Target = S-1-5-18
GPSVC(4b8.bc0) 18:17:57:330 Could not find user by sid, finding user by session id
GPSVC(4b8.bc0) 18:17:57:336 Caller requesting for user notification/lock is from session 0
GPSVC(7f0.1f4) 18:17:57:343 Client_RegisterForNotifica
GPSVC(7f0.1f4) 18:17:57:350 CGPNotify::RegisterForNoti
GPSVC(4b8.bc0) 18:17:57:350 Could not find user by sid, finding user by session id
GPSVC(4b8.bc0) 18:17:57:362 Caller requesting for user notification/lock is from session 0
GPSVC(4b8.bbc) 18:19:03:129 Target = Machine
THIRD...
GPSVC(4b8.5f8) 18:19:21:719 Target = Machine
GPSVC(4b8.aa4) 18:19:21:720 Client_RegisterForNotifica
GPSVC(4b8.5f8) 18:19:21:721 Target = Machine, ChangeNumber 0
GPSVC(4b8.aa4) 18:19:21:722 CGPNotify::RegisterForNoti
GPSVC(4b8.5f8) 18:19:25:796 Target = Machine
GPSVC(4b8.5f8) 18:19:25:797 Target = Machine, ChangeNumber 0
GPSVC(f58.9a8) 18:20:50:839 CGPNotify::RegisterForNoti
GPSVC(f58.9a8) 18:20:50:840 Client_InitialRegisterForN
GPSVC(4b8.e94) 18:20:50:841 Target = Machine
FOURTH....
GPSVC(4b8.e94) 18:20:50:844 Target = S-1-5-18
GPSVC(4b8.e94) 18:20:50:845 Could not find user by sid, finding user by session id
GPSVC(4b8.e94) 18:20:50:845 Caller requesting for user notification/lock is from session 0
GPSVC(f58.9a8) 18:20:50:845 Client_RegisterForNotifica
GPSVC(f58.9a8) 18:20:50:846 CGPNotify::RegisterForNoti
GPSVC(4b8.e94) 18:20:50:846 Target = S-1-5-18, ChangeNumber 0
GPSVC(4b8.e94) 18:20:50:847 Could not find user by sid, finding user by session id
GPSVC(4b8.e94) 18:20:50:848 Caller requesting for user notification/lock is from session 0
GPSVC(1228.122c) 18:21:30:951 CGPNotify::RegisterForNoti
GPSVC(1228.122c) 18:21:30:960 Client_InitialRegisterForN
GPSVC(4b8.4d4) 18:21:30:993 Target = Machine
Look at the attached file for full log.
gpsvc.log
Zero AI Policy
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
1. Roaming Profile size, you can right click the user profile folder to check the size of this roaming profile. Try to reduce and delete unnecessary data. Â
2. Third party program blocks the roaming profile to be loaded. You can perform a clean boot to see if the logon gets faster.
3. Group Policy settings blocks the user logon. I found a customer resolved his similar issue by enabling the entry" Hide an disable all items on the desktop" under User Configuration/Administrati
4. Corrupted roaming profile, if it is the case, try to create a new account and manually copy data to the new one.
To  Fix a corrupted user profile see: http://windows.microsoft.com/en-US/Windows7/Fix-a-corrupted-user-profile?fcb38c10
Short of that, do you have static IP Addresses on the computers, and are they definately pointing to the correct DNS Addresses?
https://www.experts-exchange.com/questions/24881627/Win2k8-Join-Domain-and-Lose-Network-Connectivity.html
It looks to be the gpo causing slow logon from the logs.
Run gpupdate /force & see the event viewer.Are you getting successful apply of  GPO?
Go to local area connection,click properties,click connect,advanced> speed &Â duplex> select 100MBPS full duplex,reboot the dc.
Also check very imp GPO's are applying properly yo that system or not,if not disjoin the system from the domain &Â rejoin it.
Also,give try to updating nic drivers.






EARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
Primary should be pointing to dc with AD-Integrated dns &Â alternate to secondary dc with dns.
Nslookup should able to resolve host to ip &Â vice versa of the system as well as dc &Â adc too.
DNS looks fine. I will try to disable the GPOs and see if one of them is causing the problem.
I'm encountering slow login issues on a domain where Trend Micro Worry Free Business Security is in use on the client PCs - they're very slow when logging in and they're NOT connected to the domain.
Can you please let me know what your fix was?
Thanks!

Get a FREE t-shirt when you ask your first question.
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
Windows Server 2003
--
Questions
--
Followers
Top Experts
Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).