Client System Administration tool 1.0.2

Client System Administration tool 1.0.2

Code can be downloaded from the original technet post here.

ACSA was built with the Helpdesk administrator in mind. Troubleshooting desktop issues requires a vast array of tools and knowledge. ACSA brings those tools together in one central location and adds additional functionality.


This script is tested on these platforms by the author. It is likely to work on other platforms as well. If you try it and find that it works on another platform, please add a note to the script discussion to let others know.
Online Peer SupportFor online peer support, join The Official Scripting Guys Forum! To provide feedback or report bugs in sample scripts, please start a new discussion on the Discussions tab for this script.

DisclaimerThe sample scripts are not supported under any Microsoft standard support program or service. The sample scripts are provided AS IS without warranty of any kind. Microsoft further disclaims all implied warranties including, without limitation, any implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample scripts and documentation remains with you. In no event shall Microsoft, its authors, or anyone else involved in the creation, production, or delivery of the scripts be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample scripts or documentation, even if Microsoft has been advised of the possibility of such damages.

ACSA Requirements:
- Powershell v2
- Quest ActiveDirectory Tools for Powershell (http://www.quest.com/powershell)
- PSExec.exe (http://technet.microsoft.com/en-us/sysinternals/bb897553)
Optional: Trace32.exe (For tailing log files)

Usage: Run the ACSA.ps1 script and type in a partial computer name to search for it in Active Directory.  This brings up a second form with a list of computers that match the search criteria and the users that are logged into them.  If you already know the name of the computer you would like to manage remotely, you can type that directly into the text box on the main form.

Features:

• Connects to currently logged-in domain on startup
• Search for PC - Search Active Directory for computers matching the string in the textbox
• System Info - Gathers info about PC, user session, make/model, hardware, OS, networking and McAfee
• Local Admins - Enumerates local administrators and allows you to remove them
• Applications - Enumerates installed software and allows you to uninstall
• Startup Items - Enumerates startup items and allows you to remove them
• Processes - Enumerates running processes and allows you to kill them
• Remote Desktop - Remote desktop into computer
• Remote Assistance - Initiate remote assistance session with remote computer
• View C Drive - Opens explorer to the C drive of remote computer
• Restart Computer - Restarts remote computer (Includes confirmation)
• File Menu
  • Connect to domain... - Connect to a different domain
  • Find User in AD - Enter user's name, search for it in AD and output to Grid View
  • Find User on PC - Enter computer name, see who is logged into it and then search for that user in AD
• View Menu
  • View McAfee AntiVirus logs
  • View WSUS logs
  • View Event Viewer
  • View Services
  • View Local Users/Groups
• Quick Fix
  • Group Policy Update - Run 'gpupdate /force'
  • Lock Computer - Lock the remote computer
  • McAfee DAT Update - Updates DATS
  • Reader Fix IE Plugin - Update Reader's exe path in registry to fix IE plugin
  • Rename Computer - Renames remote computer and reboots it
  • WSUS - Detect - Run 'wuauclt /detectnow'
  • WSUS - Report - Run 'wuauclt /reportnow'
  • WSUS - Reset Client ID - Fixes an issue where computers do not show up in WSUS

Blog Posting:  Arposh Client System Administration