How to Infrastructure.

While not IT related, it is something that I feel is important to get out there as it caused me years of missery that was easily fixed through a minor diet change. If you have or know someone who as stomach or intestinal issues like constant nausea, dry heaving a feeling like someone has either punched you in the gut or someone is wringing out your intestines then please read this. For those who don't have time for the full story, I removed nitrates from my diet. Switched any meat I ate to uncured and my water to purified water.  That means its been treated via either reverse osmosis or distillation. This removes the nitrates.  And I mean all water. Cooking, drinking, cleaning teeth, everything. For those that have some time.... I was relatively healthy.  I ran occasionally, I wasn't over or under weight. I could have done with a bit more muscle but health wise all was good. I attended a children's birthday party at an unnamed children's focused entertainment ...

Want to manage exchange from the command line but don't want to install the tools or RDP into servers.  Follow these steps and assuming your virtual directories are jacked up you should be able to connect from any powershell window. Run $creds = Get-Credential Enter your exchange admin credentials in the pop up box. Run $session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri <webmail URL>/PowerShell -Credential $creds Run Import-PSSession $session It should now start importing the cmdlets to a temporary location on your machine. Once that's completed your done.  You can now managed exchange.  Depending on what sort of firewall\load balancing you have going on, this will also work from outside the company.  You might also think about just copying the commands into a .ps1 file.  That will turn it into a script and you can ...

If you are migrating your public folders from Exchange 2010\2007 to Exchange 2013\Exchange online you may run into a nice error that complains about Mapi connection issues when creating the migration job.  Exact error will be something like MapiExceptionLogonFailed: Unable to make connection to the server. (hr=0x80040111, ec=-2147221231). The solution, luckily is pretty simple.  This error has probably occurred because you don't have a mailbox databases on the exchange 2010 server.  Just create another mailbox database and try creating the migration job again.  I would also suggest excluding this new database from provisioning in case someone gets carried away and tries to create a new mailbox in this database. As with anything you find on the Internet use this at your own risk.  Just because it worked for me doesn't mean it will work for you.

MBAM is installed,  group policies are set.  You install the MBAM client and nothing happens. First place to start is the Eventlog.  Open eventvwr.msc and browse through to ' Applications and Services Logs\Microsoft\Windows\MBAM' .  In my case I had 'TPM hardware is missing error' This was an easy one to sort out.  Just reboot, enter the BIOS and enable the TPM module.  Some manufacturers do offer tools to do this remotely so might be worth checking with your vendors on this one if you have a bunch of machines to do. Once the machine came back up it still wasn't encrypting the disk so back to the eventlog we go. This time I was presented with 'Unable to connect to the MBAM Recovery and Hardware service.  Access was denied by the remote endpoint.' For this one I started with checking access to the endpoint.  To do this open up regedit and browse to 'HKLM\Software\Policies\Microsoft\FVE\MDOPBitLockerManagement' .  Copy...

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...