LazyAdminKit – Version 0.1

LazyAdminKit – version 0.1

Screenshots

Requirements

-Powershell 2.0
-Net Framework 3.5
-Permissions on remote machines (You should always use RunAs with your domain admin account)

Features

Launcher

-Command Prompt
-Powershell
-mRemote (Optional, some requirement are needed, see below)

Server (once you typed the name of a server)

-Launch Remote Command prompt (using Sysinternal PSEXEC)
-Launch Remote Desktop (console mode)
-Launch C$ via Explorer
-Launch HP ILO (using http://ilo-ServerName)
-Launch ping with –t parameter
-Launch http://servername:80
-Launch Dell OpenManage (https://Servername:1311/)
-Launch HP HomePage (https://ServerName:2381/)

Tab1: INFO (still for the server entered in the box)

-Get Operating System info, Service pack info, Last Boot info
-Get Hard Drives information (usage/freespace/volume name/volume letter)
-Get Ram usage, PageFile usage
-Get Shares List with Path location,description,…
-Get Drivers List
-Get Services list
-Get Processes list
-Get Dell OpenManage Version
-Launch PsInfo for the remote machine
-Launch PsLoggedOn for the remote machine
-Get RDP Session and Ask Which one to kill
-Get Local Administrators Group Members

Tab2: MSC (still for the server entered in the box)

-Launch Computer Management MSC for the remote server
-Launch Services MSC for the remote server
-Launch EventViewer MSC for the remote server
-Launch IIS MSC for the remote server (IIS console need to be installed through appwiz.cpl)

Tab3: Network

-Ping the server
-Trace route the server
-Use Netstat to get LISTENING ports on the server
-Check the DNS Entry of the server with NSLOOKUP
-Get IpConfig of the server

If you are using mRemote

You will need to set a system variable %mremote% with the path of the installation folder.

(ie %mremote% = “c:\program files\mremote\”)

Written by xav197

May 30, 2010 at 9:31 pm

Posted in LazyAdminKit

Tagged with LazyAdminKit

LazyAdminKit