Make sure every machine in the enterprise (connected to LAN or always-on VPN) has the latest version of psexec.exe on the local C: drive.
Why not? That’s why.
AKA – the semi-automated, safety switch turned off, fully-loaded, drunk guy holding the trigger option.
- Download psexec.exe from live.sysinternals.com (or direct: https://live.sysinternals.com/psexec.exe) and place into AD domain SYSVOL scripts folder (e.g. \\contoso.com\netlogon)
$WebClient = New-Object System.Net.WebClient $WebClient.DownloadFile("https://live.sysinternals.com/psexec.exe","\\contoso.com\netlogon\psexec.exe"
- Create Group Policy Object (GPO) with Computer Preferences setting to copy psexec.exe from the SYSVOL share to a location on the local C: drive. Configure to “update” so that future version updates will be passed down to the clients.
- Create a Scheduled Task to keep the SYSVOL copy up to date with the latest version.
- Cheap (free)
- Fairly automated (just add water, makes it’s own sauce / set it and forget it)
- Smells like duct tape and coat hanger wire
AKA – The “I have a budget, so kiss my butt” option.
- SCCM package or application deployment
- You look cool pulling it off, but not as geeky as option 1.
- More moving parts under the hood.
- May require additional steps to maintain a consistent current version across all devices.
AKA – The “I don’t have a budget, so kiss my butt” option.
- Include within image configuration (MDT, SCCM, Ghost, Acronis, etc.)
- Difficult to maintain a consistent and current version across the enterprise
AKA – the “most fun to laugh about during the next beer-meeting” option
- Send the new guy around with a USB thumb drive
- Great fun in the office
- Do I really need to spell this out?