Log in times

[MattDLEA]

Just put in a server 2012R2 as the only server so Domain controller its running in hyper-v

 

When clients come to log on it it takes an age... Where should I start looking first?

[FN-GM]

DNS is the first thing. Check your clients are pointing to the correct DNS servers and check DNS is healthy on those servers. 99% of the time slow logins are DNS.

[MattDLEA]

Cheers, restarted server and it seams to be slightly quicker.

I know the first time they log in will take longer due to creating the profile but what would should it be after that?

 

I only have GP redirecting Documents,Downloads,Favorites,Music,Pictures and videos

 

Cheers

[FN-GM]

Did you check the DNS?

[simpsonj]

Might be worth checking how many processors you've assigned to the server in Hyper-V. It doesn't ask you when you setup via the Wizard (IIRC) so I had mine with only one processor for a little while until I wondered why they couldn't run anything at any speed whatsoever!

 

Right click server in Hyper-V - Settings - Processor and have a quick look there. You will need to power off the virtual server to make any changes.

[MattDLEA]

Host Server DNS is set to BT's DNS server.

Virstual server is using itself as the DNS and alternative is BT's

 

Clients are set to pick up automatically.

 

I have a feeling it could be somethig to do with the virtual switch

[MattDLEA]

Processors was set to 1... I think I have 24 if i click above 12 it says

i this virtual machine is configured with the following

Sockets:2

NUMA nodes per socket:1

Virtual processors per NUMA node: 12

Memory per NUMA node :22824MB

 

Any ideas

 

*first time at virtualisation

[matt40k]

Virtual server is using itself as the DNS and alternative is BT's

 

Shouldn't it be set to use just itself (and another local dns server if you've got two DNS servers locally), then you have BTs setup under forwarders.

[FN-GM]

Host Server DNS is set to BT's DNS server.

Virstual server is using itself as the DNS and alternative is BT's

 

Clients are set to pick up automatically.

 

I have a feeling it could be somethig to do with the virtual switch

 

Follow Matts advice and check the clients DNS. Don't assume its right as DHCP might be setup incorrectly.

[psydii]

None of your infrastructure or clients should be using external DNS servers in TVP/IP settings. Not even as backup. Make sure the DHCP scope is configured to tell the clients to use only the DC's as their DNS servers.

 

Your DNS server on your DC should have the external (BT/8.8.8.8) DNS server set up as a forwarder.

 

Everything should be pointing to your DC.

 

If you need DNS capabilities even when your DC is down, add the DNS role to a standalone machine and have it as a non-AD replica of your AD DNS zone. Have your infrastructure that requires DNS before the DC can boot use this standalone server as its secondary DNS server (the DC being the primary).

[Roberto]

None of your infrastructure or clients should be using external DNS servers in TVP/IP settings. Not even as backup. Make sure the DHCP scope is configured to tell the clients to use only the DC's as their DNS servers.

 

Your DNS server on your DC should have the external (BT/8.8.8.8) DNS server set up as a forwarder.

 

Everything should be pointing to your DC.

 

If you need DNS capabilities even when your DC is down, add the DNS role to a standalone machine and have it as a non-AD replica of your AD DNS zone. Have your infrastructure that requires DNS before the DC can boot use this standalone server as its secondary DNS server (the DC being the primary).

 

This. So much this.

 

The only reason to have a LAN server or workstation that you wish to have participating in an AD domain pointing to an 'external' DNS is because you're bored with things working properly.

[Fazza]

Processors was set to 1... I think I have 24 if i click above 12 it says

i this virtual machine is configured with the following

Sockets:2

NUMA nodes per socket:1

Virtual processors per NUMA node: 12

Memory per NUMA node :22824MB

 

Any ideas

 

*first time at virtualisation

 

When you create a VM with Hyper-V it only assigns 1 CPU which means your server will be painstakingly slow - when creating a VM, berfore installing the OS I configure the CPU could to at least 2 and configure the RAM as well to be at least 2GB on startup and then Dynamic.

 

I would suggest that you shutdown the server and change the CPU count to at least 2, if you're not planning on having too many VMs on the host server then set it at 3 or 4 CPUs.