IT & Desktop admin Resources

  1. Reset windows 7 admin password locally: http://www.howtogeek.com/96630/how-to-reset-your-forgotten-windows-password-the-easy-way/
  2. the trust relationship between this workstation and the primary domain failed: https://community.spiceworks.com/how_to/108912-fix-the-trust-relationship-between-this-workstation-and-the-primary-domain-failed
    1. http://implbits.com/active-directory/2012/04/13/dont-rejoin-to-fix.html
  3. Windows Perfmon:
    1. https://software.intel.com/en-us/articles/use-windows-performance-monitor-for-infrastructure-health
    2. http://searchdatacenter.techtarget.com/tip/What-to-look-for-when-conducting-benchmark-tests-with-Perfmon
    3. Customizing Performance Monitor: https://technet.microsoft.com/en-us/library/2008.08.pulse.aspx
    4. Components: baselines / benchmark sampling intervals / counters / centralized monitor
    5. Commong bottlenecks in Five areas: Physical disk, memory, process, CPU, and network.
    6. Sampling intervals: balance size of log file and server load
      1. 15 minutes: good window to establishing baseline;
      2. 15 seconds: average elapsed time for a 4-hour issue;
      3. 5 minutes: average elapsed time for a 8-hour issue
    7. Guidelines (https://technet.microsoft.com/en-us/library/2008.08.pulse.aspx):
      1. Disk
        1. LogicalDisk\% Free Space: alert at <15%; consider add space;
        2. PhysicalDisk\% Idle Time: saturated <20%; consider replacing faster disk system;
        3. PhysicalDisk\Avg. Disk Sec/Read OR PhysicalDisk\Avg. Disk Sec/Write : alert at >25ms; 10ms for SQL & Exchange server; consider replacing faster disk system;
        4. PhysicalDisk\Avg. Disk Queue Length: alert at > 2x of the number of spindles;
        5. Memory\Cache Bytes: memory being used for file system cache; alert at >300MB;
      2. Memory
        1. Memory\% Committed Bytes in Use: amount of virtual memory in use, alerts at >80%; consider add more memory;
        2. Memory\Available Mbytes: alerts at < 5%; consider add more memory;
        3. Memory\Free System Page Table Entries: maybe memory leak for <5000;
        4. Memory\Pool Non-Paged Bytes: maybe memory leak for >175MB;
        5.  Memory\Pool Paged Bytes: mayge memory leak for >250MB;
        6. Memory\Pages per Second: alerts at >1000 as a result of excessive paging, maybe memory leak;
      3. Processor
        1. Processor\% Processor Time: alerts at >85%; consider replace faster processor;
        2. Processor\% User Time: elapsed time the processor spends in user mode; alerts at high value; consider optimize the applications;
        3. Processor\% Interrupt Time: processor spends receiving and servicing hardware interruptions; possible hardware issue if > 15%;
        4. System\Processor Queue Length: alerts at 2x No. of CPUs; not enough processing powers;
      4. Network
        1. Network Interface\Bytes Total/Sec: Send and receive per NIC; saturated if > 70%; for 100MB NIC, alerts at >8.7MB/sec;
        2. Network Interface\Output Queue Length: network saturation if  >2; consider faster NIC or segmenting network;
      5. Process
        1. Process\Handle Count: total number of handles that are currently open by a process; alerts at >10,000 for handle leak;
        2. Process\Thread Count: number of threads currently active in a process, alerts at >500 between min. and max.;
        3. Process\Private Bytes:  memory allocated that cannot be shared with other processes; alerts at >250 of thread leakage between min. and max. 
      6. Conclusion:
        1. save as templates for later use
        2. remote monitoring is good practice but cannot monitor server that is running out of resources;

 

IT & Desktop admin Resources