How to Infrastructure.

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