Vamos a ver cómo trabajar con herramientas para detectar posibles errores en nuestros controladores de dominio después de nuestras instalaciones.
POSIBLES ERRORES
Error DCdiag frsevent
Starting test: frsevent
There are warning or error events within the last 24 hours after the
SYSVOL has been shared. Failing SYSVOL replication problems may cause
Group Policy problems.
solucion:
net stop ntfrs
net start ntfrs
Errores de W32Time
El típico error de Sistema con origen W32Time que nos dice algo así como...
El proveedor de tiempo NtpClient se ha configurado para adquirir la hora desde uno o más recursos de hora, sin embargo, ninguno de los recursos está accesible No se hará un intento de ponerse en contacto con un recurso durante 15 minutos. NtpClient no tiene recurso de hora exacta.
Check the Event Viewer (eventvwr.msc) This link is external to TechNet Wiki. It will open in a new window. and review the entries in the System Log This link is external to TechNet Wiki. It will open in a new window. . After you have either resolved or decided to ignore those errors, archive the event log This link is external to TechNet Wiki. It will open in a new window. and then clear it (or if you don't care to save the events, simply clear the log This link is external to TechNet Wiki. It will open in a new window. ).
Configuring the Windows Time service to use an internal hardware clock
1. Click "Start", click "Run", type "regedit" (without the quotation
marks), and then click "OK".
2. Locate and then click the following registry subkey:
"HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config\Ann
ounceFlags"
3. In the right pane, right-click "AnnounceFlags", and then click
"Modify".
4. In "Edit DWORD Value", type "A" (without the quotation marks) in the
"Value data" box, and then click "OK".
5. Quit Registry Editor.
6. At the command prompt, type the following command to restart the Windows Time service, and then
press ENTER:
"net stop w32time && net start w32time" (without the quotation marks)
