I've enabled remoting via Group Policy (AD) for our Windows 7 machines, and it's great, but the one small niggle I have is that it seems to take a while for the WinRM service to start. I can ping and run the Get-Service cmdlet (with the -computername parameter) against the newly-booted machine for maybe two minutes or so before WinRM finally enters the running state. Is this normal?
by DonJ at 2012-12-20 06:46:54
Not in my experience, no. You'd need to dig pretty deeply to discover why. Is WinRM being asked to start a large number of listeners? Is it waiting on a dependency service to start, and that service is slow? Are there a large number of local IPs being bound?