Windows login speed, its taking machines a while to log into the 2k3 SBS server...
Windows login speed, its taking machines a while to log into the 2k3 SBS server...
Are few are:
Speed of the Client PC
Number of GPO's that need to be processed
Size of Profile
Location of Profile
Location of Logon server
Hope that helps.
Intel i5 2500K
Gbyte Z68mx-ud3
2x 4GB Corsair Vengance
NEC ND3540A BLACK DVDR
1TB HDD
Sony SDM-HS75P 17" TFT
Logitech Cordless Mouse and Keyboard LX700
Ok,
Client PC
XP64/3200
1Gb RAM
80Gb
Profile is new, no files in My Docs.
XP can be a little bit of a pain if people try an log in as soon as the login screen is displayed.
did you join the SBS client to the domain properly ( ie login locally and browse to http://sbsserver/connectcomputer )
my Virtualisation Blog http://jfvi.co.uk Virtualisation Podcast http://vsoup.net
The machines being left for a good few mintues after the logon screen shows.
The machines are on DHCP (not supplied by the server)
The machine was connected to the domain when it was installed, I take it things are done differently dependant on how you join then?
SBS clients run much hapiper if they are joined to the domain with the wizard ( this is where folk who are used to regular W2k3 server tend to slip up
is DHCP assigning your SBS box as a DNS server ( this is needed )
why are you not using the SBS box as DHCP ? it is much happier to let it get on with it ( as I think it uses a couple of extra options that basic DHCP can miss out )
my Virtualisation Blog http://jfvi.co.uk Virtualisation Podcast http://vsoup.net
Ability to locate a domain controller - make sure the primary DNS points to an internal server.
Ability to locate & copy group policies.
You can check for the KB on "userenv logging" to create a debug log which can help you see where the delays occur with client logons.
Sometimes people like to stop various services which they think aren't essential for Windows to run, but don't realise (in a domain environment especially) this can slow things down a lot.
Having a DC run as a file server and an internet gateway or RAS server is also inadvisable, the extra services can create delays for local clients in some configurations.
~ I have CDO. It's like OCD except the letters are in alphabetical order, as they should be. ~
PC: Win10 x64 | Asus Maximus VIII | Core i7-6700K | 16GB DDR3 | 2x250GB SSD | 500GB SSD | 2TB SATA-300 | GeForce GTX1080
Camera: Canon 60D | Sigma 10-20/4.0-5.6 | Canon 100/2.8 | Tamron 18-270/3.5-6.3
not really an option when you use SBSHaving a DC run as a file server and an internet gateway or RAS server is also inadvisable, the extra services can create delays for local clients in some configurations.
its supposed to be a one box does everything solution..
my money is goin on DNS.
my Virtualisation Blog http://jfvi.co.uk Virtualisation Podcast http://vsoup.net
Oh, another thing which can cause logon delays is if you have wireless adapters in the clients which are enabled but you don't have a WLAN to connect to - the ordering of the network adapters can mean Windows will try to get a working connection to the DC through the wireless NIC before it tries the wired one.
Disable wireless NICs if you don't use them (note, turning off the radio through the 3rd party control applet is not enough - it still presents a NIC to configure to Windows).
Multi-homed clients (and servers) can also create problems, always check you don't have more than 1 default gateway configured.
~ I have CDO. It's like OCD except the letters are in alphabetical order, as they should be. ~
PC: Win10 x64 | Asus Maximus VIII | Core i7-6700K | 16GB DDR3 | 2x250GB SSD | 500GB SSD | 2TB SATA-300 | GeForce GTX1080
Camera: Canon 60D | Sigma 10-20/4.0-5.6 | Canon 100/2.8 | Tamron 18-270/3.5-6.3
The servers not the DHCP server due to the router doing it atm as the servers not on 24/7 due to me installing rebooting etc etc.
Theres nothing else on the server atm, its just one machine.
Its also slow syncing stuff when you log out.
Rite, Chris wins...
Put the server as the 1st DNS and the router as the 2nd and left the rest to DHCP, works nice now, cheers girls...
windows firewall usually is a pain in the bum
There are currently 1 users browsing this thread. (0 members and 1 guests)