Estou gravemente precisando de sua ajuda e assistência.
Temos um problema com nosso logon e inicialização no sistema Windows 7 Enterprise. Temos mais de 3000 Windows Desktops situados em mais de 20 edifícios em torno do campus. Quase todos os computadores do campus têm o problema que vou descrever. Passei mais de um mês espiando por arquivos etl do Windows Performance Analyzer (Um ótimo produto) e centenas de milhares de logs de eventos. Eu venho a você hoje humilhado que eu não consegui descobrir isso.
O problema de simplesmente colocar nossos tempos de logon é extremamente longo. Um primeiro tempo médio de logon é de aproximadamente 2-10 minutos, dependendo do software instalado. Todos os computadores são o Windows 7, os computadores mais antigos com 5 anos de idade. Os tempos de inicialização em vários computadores variam de bom (1-2 minutos) a muito ruim (5-60). Nosso segundo tempo logons variam de 30 segundos a 4 minutos.
Temos uma conexão gigabit entre cada computador na rede.
Temos 5 controladores de domínio que também funcionam como nossos servidores DNS.
Testes iniciais nos levaram a acreditar que isso era um problema de software. Então, passei alguns dias testando máquinas apenas para encontrar resultados inconsistentes dos arquivos etl do xperfview. Cada subconjunto de computadores no campus tinha um subconjunto diferente de problemas de software, nenhum deles parecia interferir no logon apenas na inicialização.
Então, comecei a analisar nossa política de grupo e localizei algumas IDs de evento muito interessantes.
Mais ou menos com timestamps, torna-se evidente que a rede talvez seja o problema.
1:25:57 - Group Policy is trying to discover the domain controller
information
1:25:57 - The network link has been disconnected
1:25:58 - The processing of Group Policy failed because of lack of
network connectivity to a domain controller. This may be a transient
condition. A success message would be generated once the machine gets
connected to the domain controller and Group Policy has successfully
processed. If you do not see a success message for several hours, then
contact your administrator.
1:25:58 - Making LDAP calls to connect and bind to active directory.
DC1.ourdomain.edu
1:25:58 - Call failed after 0 milliseconds.
1:25:58 - Forcing rediscovery of domain controller details.
1:25:58 - Group policy failed to discover the domain controller in
1030 milliseconds
1:25:58 - Periodic policy processing failed for computer
OURDOMAIN\%name%$ in 1 seconds.
1:25:59 - A network link has been established at 1Gbps at full duplex
1:26:00 - The network link has been disconnected
1:26:02 - NtpClient was unable to set a domain peer to use as a time
source because of discovery error. NtpClient will try again in 3473457
minutes and DOUBLE THE REATTEMPT INTERVAL thereafter.
1:26:05 - A network link has been established at 1Gbps at full duplex
1:26:08 - Name resolution for the name %Name% timed out after none of
the configured DNS servers responded.
1:26:10 – The TCP/IP NetBIOS Helper service entered the running state.
1:26:11 - The time provider NtpClient is currently receiving valid
time data at dc4.ourdomain.edu
1:26:14 – User Logon Notification for Customer Experience Improvement
Program
1:26:15 - Group Policy received the notification Logon from Winlogon
for session 1.
1:26:15 - Making LDAP calls to connect and bind to Active Directory.
dc4.ourdomain.edu
1:26:18 - The LDAP call to connect and bind to Active Directory
completed. dc4. ourdomain.edu. The call completed in 2309
milliseconds.
1:26:18 - Group Policy successfully discovered the Domain Controller
in 2918 milliseconds.
1:26:18 - Computer details: Computer role : 2 Network name :
(Blank)
1:26:18 - The LDAP call to connect and bind to Active Directory
completed. dc4.ourdomain.edu. The call completed in 2309
milliseconds.
1:26:18 - Group Policy successfully discovered the Domain Controller
in 2918 milliseconds.
1:26:19 - The WinHTTP Web Proxy Auto-Discovery Service service entered
the running state.
1:26:46 - The Network Connections service entered the running state.
1:27:10 – Retrieved account information
1:27:10 – The system call to get account information completed.
1:27:10 - Starting policy processing due to network state change for
computer OURDOMAIN\%name%$
1:27:10 – Network state change detected
1:27:10 - Making system call to get account information.
1:27:11 - Making LDAP calls to connect and bind to Active Directory.
dc4.ourdomain.edu
1:27:13 - Computer details: Computer role : 2 Network name :
ourdomain.edu (Now not blank)
1:27:13 - Group Policy successfully discovered the Domain Controller
in 2886 milliseconds.
1:27:13 - The LDAP call to connect and bind to Active Directory
completed. dc4.ourdomain.edu The call completed in 2371
milliseconds.
1:27:15 - Estimated network bandwidth on one of the connections: 0
kbps.
1:27:15 - Estimated network bandwidth on one of the connections: 8545
kbps.
1:27:15 - A fast link was detected. The Estimated bandwidth is 8545
kbps. The slow link threshold is 500 kbps.
1:27:17 – Powershell - Engine state is changed from Available to
Stopped.
1:27:20 - Completed Group Policy Local Users and Groups Extension
Processing in 4539 milliseconds.
1:27:25 - Completed Group Policy Scheduled Tasks Extension Processing
in 5210 milliseconds.
1:27:27 - Completed Group Policy Registry Extension Processing in 1529
milliseconds.
1:27:27 - Completed policy processing due to network state change for
computer OURDOMAIN\%name%$ in 16 seconds.
1:27:27 – The Group Policy settings for the computer were processed
successfully. There were no changes detected since the last successful
processing of Group Policy.
Qualquer ajuda seria apreciada. Por favor, peça qualquer informação relevante e ela será fornecida o mais rápido possível.