· Home
· About
· Contact
· Privacy Policy

 News & Updates
·News Feed (RSS)    

 Online Store
· Buy Now
· License Types

· Customer Login
· Customer Support

· Free downloads
· Registered customers

 Windows Registry
· Registrar Registry

· Registrar Command
   Line Edition

 File Protection
· Undeluxe

 Crash Analysis
· WhoCrashed

 Security Tools
· SanityCheck
· AntiFreeze

 System Monitoring
· WhySoSlow
· LatencyMon
· MultiMon
· DispatchMon
· ObjMon

· ErrorLookup

 Software Bundle
· Power Pack

 Source Code
· Driver source code

· Driver Development

If you would like to receive a message now and then about product releases, upgrades and discounts,  then please enter your email address to subscribe to our newsletter. 

·  Introduction
·  Supported OS
·  Pro Edition
·  What's new
·  FAQ
·  Screen Shots
·  Download
·  Buy Now

Configuring remote systems for use with WhoCrashed

In order to allow WhoCrashed perform analysis of a remote computer on the network, the remote system must be accessible and configured accordingly.

Access to admin shares

The user who is running WhoCrashed should have acess to the admin shares on the remote machine to be analyzed so that the crash dump files on the remote machine can be accessed by WhoCrashed. If the remote system is running Windows 8 or Windows 2012 Server, the remote admin share is disabled by default and needs to be explicitly enabled.

Enabling the remote system for WMI

In addition to remote admin share access, WhoCrashed requires that a remote system is configured for WMI for crash dump analysis to succeed. This usually means that an exception for WMI needs to be present in the Firewall applet which is accessible from the control panel. For more information, refer to the following MSDN article:

Connecting to WMI Remotely Starting with Windows Vista

Copyright © 1997-2019 Resplendence Software Projects Sp. All rights reserved. Privacy Policy.
Page generated on 7/23/2019 11:46:20 AM. Last updated on 4/30/2019 3:46:32 PM.