segunda-feira, 16 de setembro de 2019

Microsoft EndPoint Protection - Failed to open the local machine Group Policy

Erros: 0x8007000D / 0x80004005
  1. Uninstall Endpoint from Client Computer (add/remove).
  2. Uninstall SCCM agent on the computer: c:\windows\ccmsetup\ccmsetup.exe /uninstall
  3. Rename current registry.pol at C:\Windows\System32\GroupPolicy\Machine to registry.old
  4. Install SCCM client via SCCM / \\sccmserver\sms_sma\Client\ccmsetup.exe SMSSITECODE=AAA FSP=SCCMServer
  5. Let it install the agent and Endpoint and it will automatically recreate registry.pol
  6. Now, Antimalware Policy should be back.

segunda-feira, 21 de maio de 2018

Troubleshooting Windows Defender or Endpoint Protection client

- Rename the Software Distribution folder on your computer

  1. Stop the Automatic Updates service
    1. Click Start and search for services.msc, and then click OK.
    2. Right-click the Automatic Updates service, and then click Stop.
    3. Minimize the Services snap-in.
  2. Rename the SoftwareDistribution directory as follows:
    1. Click Start and search for cmd, and then click OK.
    2. Type cd %windir%, and then press Enter.
    3. Type ren SoftwareDistribution SDTemp, and then press Enter.
    4. Type exit, and then press Enter.
  3. Start the Automatic Updates service as follows:
    1. Maximize the Services snap-in.
    2. Right-click Automatic Updates service, and then click Start.
    3. Close the Services snap-in window.

- Reset the Microsoft antivirus update engine on your computer

  1. Click Start and search for cmd, and then click OKand then right-click Command Prompt, and then select Run as administrator.
  2. In the Command Prompt window, type the following commands and press Enter after each command:
    Cd\
    Cd program files\windows defender
    Mpcmdrun -RemoveDefinitions -all
    Exit
  3. Restart your computer.
  4. Open Windows Defender or
    Endpoint Protection, click the Update tab, and then click Update.
  5. If the issue persists, proceed to the next step.

- Manually install the virus and spyware definition updates


Material completo -> https://docs.microsoft.com/en-us/sccm/protect/deploy-use/troubleshoot-endpoint-client


segunda-feira, 11 de setembro de 2017

quarta-feira, 24 de maio de 2017

Como alterar facilmente a sub-rede do escopo de um DHCP Server.

Você precisará salvar essas informações:
- IPs excluídos
- Reserva (s)
- Opção (ões) do escopo do DHCP

Existe uma maneira fácil de fazê-lo com NETSH, execute o comando:

     netsh dhcp server \\"Server" scope "ip_of_scope" dump > c:\dhcp.txt

Edite o arquivo dhcp.txt e altere a linha:
     dhcp Server \\"Server" add scope 192.168.0.0 255.255.255.0 "Pool DHCP" ""

Salve o arquivo e quando estiver pronto, apague o escopo DHCP e executar o comando:
    netsh exec c: \ dhcp.txt


quinta-feira, 31 de março de 2016

Boas Praticas após clone de VM Linux

Best Practices Linux VMWare Clonning

After you clone the VM login and...

1) rm -rf /etc/ssh/ssh_host_*
2) Edit the hostname in /etc/sysconfig/network
3) rm -rf /etc/udev/rules.d/70-*
4) Remove the HWADDR line and UUID line from /etc/sysconfig/network-scripts/ifcfg-eth* file(s). Also change the IP address in this/these files
5) If you'd like, delete all the logs from /var/log and build logs from /root

Reboot VM

domingo, 14 de fevereiro de 2016

Windows 2008 - Domain Controller - Blue Screen - Recovery NDTS

Windows 2008 x86, erro, tela azul, Domain Controller, Directory Services Restore Mode, event id 1003 e 1168
  1. Restart the server and press F8 key, select Directory Services restore mode.
  2. Log in with the local administrator username and password
  3. Type: cd \windows\system32
  4. Type: NTDSUTIL
  5. Type: activate instance NTDS
  6. Type: files
  7. If you encounter an error stating that the Jet engine could not be initialized exit out of ntdsutil.
  8. Type: cd\
  9. Type: md backupad
  10. Type: cd \windows\ntds
  11. Type: copy ntds.dit c:\backupad
  12. Type: cd \windows\system32
  13. Type: esentutl /g c:\windows\ntds\ntds.dit
  14. This will perform an integrity check, (the results indicate that the jet database is corrupt)
  15. Type: esentutl /p   c:\windows\ntds\ntds.dit
  16. Agree with the prompt
  17. Type: cd \windows\ntds
  18. Type: move *.log c:\backupad   (or just delete the log files)
This should complete the repair.  To verify that the repair has worked successfully:
  1. Type: cd \windows\system32
  2. Type: ntdsutil
  3. Type: activate instance ntds
  4. Type: files        (you should no longer get an error when you do this)
  5. Type: info       (file info should now appear correctly)
One final step, now sure if it’s required:
From the NTDSUTIL command prompt:
  1. Type: Semantic Database Analysis
  2. Type: Go
fonte: http://distefano.biz/blog/index.php/2013/01/22/windows-server-2008domain-controller-failed-to-start/

Dell T110 - Windows 2008 x86 - PERC S300, falha no boot após falta de energia

Baixar o driver da controladora PERC - Salvar em um pen-drive

Download File

http://www.dell.com/support/home/us/en/19/Drivers/DriversDetails?driverId=WPJ2J

Boot no servidor com mídia de instalação do S.O.

Selecionar o idioma

Selecionar "Modo de reparação"

Carregar o driver da controladora PERC

Selecionar a partição de sistema e Avançar

Prompt de comando

bootrec /fixmbr
bootrec /fixboot
bootrec /rebuildbcd
x:\sources\recovery\StartRep.exe





quarta-feira, 30 de dezembro de 2015

Limpeza manual da "ConflictAndDeleted" no DFSR

Manually Clearing the ConflictAndDeleted Folder in DFSR

http://blogs.technet.com/b/askds/archive/2008/10/06/manually-clearing-the-conflictanddeleted-folder-in-dfsr.aspx


segunda-feira, 27 de julho de 2015

Cisco - DHCP reservar IP

show ip dhcp binding

-> selecionar o identifier/IP a reservar e executar o clear

clear ip dhcp binding "IP"

-> criar o escopo reservas e cadastrar os IP's / identifiers


conf t

ip dhcp pool RESERVA1
 host 192.168.1.1 255.255.255.0
 client-identifier 0154.04a6.822e.0d

ip dhcp pool RESERVA2
 host 192.168.1.2 /24
 client-identifier 0148.5b39.bb26.8d

ip dhcp pool RESERVA3
 host 192.168.1.3 /24
 client-identifier 01a4.badb.06e2.78

ip dhcp pool RESERVA4
 host 192.168.1.4 /24
 client-identifier 0174.867a.fa14.92