Systems Triage

From Pumping Station One
Revision as of 00:44, 19 September 2014 by Hef (talk | contribs) (Created page with " Most of the stuff on this list needs to be carefully to not heavily disrupt existing services, and carries risk of destruction if done incorrectly. == Reboot Fails == * ngi...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Most of the stuff on this list needs to be carefully to not heavily disrupt existing services, and carries risk of destruction if done incorrectly.

Reboot Fails

  • nginx on bob
    • Failed last time it was rebooted, appears to be DNS related. I believe I fixed it, but havn't tested it yet --Hef (talk) 19:44, 18 September 2014 (CDT)

Second Domain Controller

All things samba related pretty much have to be tested in a dev environment, which means setting up your own personal samba AD domain.

Move VPN off of bob

Having the VPN servers on bob makes samba detect extra interfaces that are not easily routable. The vpn services should be moved off the domain controller

All proxmox VMs need to be on the raid

A few proxmox VM's have been created on the their hypervisors local hard drive. The option to do this has been removed, but the machines that were originally setup that way still exist.

Moving machines off of the local drives on onto the san/lvm setup sounds tricky, and I haven't looked into how to do this yet. --Hef (talk) 19:44, 18 September 2014 (CDT)

GPO Updates

All windows machines hooked into hardware should have GPO settings to disable all power settings.

User caching

This came up on the mailing list: http://support.microsoft.com/kb/172931

It looks like a good idea, but the article doesn't reference windows 8. If it works on windows 8, it looks straight forward to add to the GPO.

Sysvol syncing

samba doesn't do automatic /sysvol replication. An automatic syncing process should be setup between bob and dc01. see https://wiki.samba.org/index.php/SysVol_Replication for reference.