How to Infrastructure.

If your deploying the Splunk Forwarder to send event logs to your Splunk servers, you may or may not know that it doesn't just grab your logs and send them off.  Binds to a port for some reason.  By default it grabs 8089. If you're in a decent sized environment, which if you can afford Splunk I assume you are, then you will probably find at least 1 existing app that is already using that port and that's where this post comes in. The problem will present itself by you trying to start the Splunk service and the Splunk service telling you, "nope I am not starting." First thing to check is the log file.  This can be found in the install directory under the var\log\splunk subfolders.  By default, the full path will be c:\program files\SplunkUniversalForwarder\var\log\splunk. Once you're here, open up the splunkd.log file.  Scroll through for something listed as FATAL.  In our case, that shows HTTPServer - Could not bind to port 8089.  Now if you...

Got yourself a Hyper-V host on a nice HP server and can't connect to it remotely from the Hyper-V manager?  You are not alone.  Assuming your error is something like the error below then I may be able to help. The WS-Management service cannot process the request.  The class Msvm_RegisteredProfile does not exist in the root/interop namespace. This has something to do with the HP tools messing with the registration of the MOF's.  All we need to do to fix it is register the MOF files.  To do this, open an administrative command prompt on the server and run the following command. MOFCOMP %SYSTEMROOT%\System32\WindowsVirtualization.V2.mof That will parse through the MOF file and register it on the system leaving you with the nice screenshot below. You should now be able to use your local Hyper-V console to connect to the server and manage away. As with anything you find on the Internet use this at your own risk.  Just because it...