When trying to add your DAG node to backup exec you see the following error. The Backup Exec Remote Agent Must Be Installed And Running On All Nodes In The Dag
A guide on how to export mailboxes to PST in Exchange 2013 with a scheduled task, this applies to Exchange 2010 also.
With a quick powershell command we can stop users being able to log into the exchange 2013, Exchange 2010 or Exchange 2007 ECP.
When adding a node to your Exchange DAG you see an error stating The fully qualified domain name for node could not be found.Troubleshooting steps.
Information on how you can increase your mail servers life cycle by using a mail archiving solution such as GFI MailArchiver
When sending emails to certain domains to youget an error stating #450 4.7.1 Client Host Rejected Cannot Find Your Hostname ##. This is a reverse lookup error.
A guide on how to setup transports rules in exchange 2010 so that you can stop users sending or receiving email from people outside your email organization.
A quick simple guide on how to install the exchange 2010 product key into the exchange managment console.
A review of GFI MailArchiver, from installtion through to configuration. A run down of some of the great features offered and how they work
A guide on how to use the Exchange Managment Shell to setup IP blocklist providers in exchage 2010 and Exchange 2013
If you would like to see what your users actually do with email once they get it then this powershell command enables you to see and check what rules users are using on thier Outlook clients.
When you launch the EMC you see either the message The WinRM Client Received An Http Server Error Status (500) or The attempt to connect to http://server.domainname.com/powershell using “kerberos” authentication failed:Connecting to remote server failed with the following message:The WinRm client cannot process the request.It cannot determine the content type pf tje HTTP response from the destination computer. The content type is absent or invalid
When you try and create a new maiblox in Exchange 2007 or Exchange 2010 you get the following error Property expression “Administrator” isn`t valid.Valid strings are.Strings that includes `@` cannot be the last character. Here is the solution