HDtechs
asked on
Only windows 7 pc's take 6-10 min login?
We currently have issues when logon windows 7 pc's only in a server 2003 domain environment. It takes 6-10 min to logon, i have disabled ipV6, there are no printers being deployed gpo and when i run a group policy results wizard it gives a GP Core failure. This is on a brand new windows 7 32bit pc. The other windows 7 is 64bit and a bit older but both started this yesterday. It also takes a couple of min to dameware into both pc's. I took pc out of domain, deleted from AD then put back in but that process took forever. Still not working. DNS resolves correctly. XP cpu's, run fine!!!
this is due to the dns not being pointed to the dns server
check the computers ip settings and manually enter the dns servers ip address which should be the domain controller
check the computers ip settings and manually enter the dns servers ip address which should be the domain controller
Are you using roaming profiles or redirected folders?
I also had same issue last year DNS was resolving correctly but clients still was logining 3-6 minutes. When I shutdown the prolematic DC all client were logining easyly. I have flushed the DNS and reregistered and problem went away. If it does not work and if you have 2nd DC you can configure your DHCP server to point other DNS server as primary.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Chief, what your saying makes sense b/c the redirected docs are not working from the gp core failure. I unplug from network and logins are ok. I am going to try what u suggest later today.
ASKER
Chief, Tried what you suggested and works great now. Dameware logins are fast and windows logins are less than 10 sec, but it still doesnt want to redirect folders on the windows 7 units. Again the XP world is fine.
ASKER
Worked great just wondering why we dont have the same issues with our other 2003 servers and w7 pc's.
Follow up:
You may not have had the same issuew with other W7 PCs because these PCs were not within an OU and looking for group policies. There are many reasons why other W7 PCs may not have worked. Did you put an ADML or ADMX into the sysvol, or just place them into the computers CN folder?
You may not have had the same issuew with other W7 PCs because these PCs were not within an OU and looking for group policies. There are many reasons why other W7 PCs may not have worked. Did you put an ADML or ADMX into the sysvol, or just place them into the computers CN folder?
ASKER
Thats the whole crazy thing about it. We have other 2003 servers with W7 and GPO's run fine. I put the ADMX in the sysvol and left the W& pc's in the original OU. We may have to start moving them to their own OU for best practice.
It really does make GPO administration easier when your Win 7 machines (and Vista, too, for that matter), are separated from your XP machines.
Just my 2¢ worth....
DrUltima
Just my 2¢ worth....
DrUltima
I think you will find the other W7 computers may have basic policies that quickly apply to almost any of the OS's. But, there are certain policies that are not forwards compatible with W7 boxes from a 2003 machine.
Any issues with Group Policy, Replication, DNS, WINS