Exchange 2013 AntiSpam

Enable Antispam Services on Exchange 2013 Mailbox Server 

& $env:ExchangeInstallPath\Scripts\Install-AntiSpamAgents.ps1
Restart-Service MSExchangeTransport
Set-TransportConfig -InternalSMTPServers @{Add="192.168.0.7"}

Sender Filter Agent

Add-IPBlockListProvider -name zen.spamhaus.org -lookupdomain zen.spamhaus.org
Set-SenderFilterConfig -BlankSenderBlockingEnabled $true
Set-SenderFilterConfig -RejectionResponse "Message rejected as spam by Exchange2013 Content Filtering."

Recipient Filter Agent

Set-RecipientFilterConfig -RecipientValidationEnabled $true

Tarpitting

Get-ReceiveConnector | Set-ReceiveConnector -TarpitInterval 00:00:10

Check SCL Histogram

& $env:ExchangeInstallPath\Scripts\get-antispamSCLHistogram.ps1

.

.

 

Exchange 2013 – something went wrong

http://support.microsoft.com/kb/2603736

http://technet.microsoft.com/library/bb331958.aspx#SH

MSExchangeDiagnostics Event 1006

The performance counter ‘\\EXCHANGE2013\MSExchangeIS Store(mailbox database 1736747621)\Quarantined Mailbox Count’ sustained a value of ’1.00′, for the ’10′ minute(s) interval ending at ’27/02/2013 3:30:00 AM’. Additional information: None. Trigger Name:StoreQuarantinedMailboxCountTrigger. Instance:mailbox database 1736747621

Add User to Dashboard – Server 2012 Essentials

To manually import user names into the Dashboard on Server 2012 Essentials:

  1. On Server 2012 Essentials, open a Command Prompt window as an administrator.
  2. Type   cd “\Program Files\Windows Server\Bin”   and press ENTER.
  3. Type   WssPowerShell.exe    and then press ENTER.
  4. Type   Import-WssUser –Name <username>    and then press ENTER.
  5. Repeat Step 4 for each user name that you want to import into the Dashboard.

 

.

 

Exchange 2013 Mailbox Import Failed – How to deal with it

Powershell commands:
Give yourself rights to Import Mailboxes (not turned on by default):
New-ManagementRoleAssignment –Role "Mailbox Import Export" –User Administrator
Import a single PST:
New-MailboxImportRequest -Mailbox Peter -FilePath \\exchange\PSTarchive\outlook.pst
Import Multiple Mailboxes:
This example imports all of the .pst files on a shared folder. Each .pst file name is named after a corresponding user’s alias, e.g.  peter.pst
Dir \\exchsvr\PSTarchive\*.pst | %{ New-MailboxImportRequest -Name Import20120527 -BatchName Import20120527 -Mailbox $_.BaseName -FilePath $_.FullName}
Check Status of all recent Imports:
Get-MailboxImportRequest
Output Report of an Import to file
Get-MailboxImportRequestStatistics Peter\Import20120527 -IncludeReport | fl > c:\imports\report.txt
Output a Report of all currently Failed Imports
Get-MailboxImportRequest -Status Failed |  Get-MailboxImportRequestStatistics -IncludeReport | fl > c:\imports\allfailedreport.txt

Resume all failed Imports (try again)
Get-MailboxImportRequest -Status Failed |  Resume-MailboxImportRequest
.
Two reasons for Mailbox Import to fail:
1.   Large Items  -  There are emails larger than the message size limits you have set on the Exchange Transport components,  connectors, etc.
Since the default is 10MB,  any emails in the mailbox larger than 10MB will cause the import to fail.
Places to increase message size:
Set-TransportConfig -MaxReceiveSize 50MB -MaxReceiveSize 50MB
 Get-ReceiveConnector | Set-ReceiveConnector -MaxMessageSize 50MB
 Get-SendConnector | Set-SendConnector -MaxMessageSize 50MB
Then:
Wait 2 hours, or

Restart these services?

  • MSExchangeMailSubmission
  • MSExchangeTransport
  • MSExchangeMailboxAssistants
or Restart Exchange Server
2.   Bad Items  -  Corrupt messages in the PST.
May need to run ScanPST several/many times on each PST before it is marked as clean.
ScanPST is installed in ProgramFiles/Office  folder,  but is GUI only, no command-line.
cscanpst is a command line wrapper for ScanPST.
ScanPSTAll is a script that automates cscanpst/ScanPST combo so you can queue up a lot of files to repair.
To make a script that will run ScanPSTAll 20 times,  make a new batch file next to ScanPSTAll script and put this line in there 20 times:   call ScanPSTALL.cmd



3.  If all else fails  -  You can tell the importer to skip bad/large emails and continue on.  The bad/large emails will not be imported.

Add these parameters to the New-MailboxImportRequest command.
-BadItemLimit 100   -AcceptLargeDataLoss
.

Outlook Security Alert – Exchange 2013

You may receive an error message when using Outlook:

Security Alert:  The name on the security certificate is invalid or does not match the name of the site.

Although you may have a valid certificate installed on your Exchange server,  the security alert references a server name that isn’t on the certificate.   Outlook is receiving the incorrect server name from the Client Access Server role in response to an Autodiscover request.

On the Exchange server,  open Powershell and run this command:

Get-ClientAccessServer -Identity EXCHANGE2013 | ft AutoDiscoverServiceInternalUri

This will confirm that the Autodiscover Uri does not match the name on the certificate.  Run this command to change the Autodiscover Uri:

Set-ClientAccessServer -Identity EXCHANGE2013 -AutoDiscoverServiceInternalUri https://mail.domain.com.au/Autodiscover/Autodiscover.xml

Replace EXCHANGE2013 with the local name of your Exchange Server or Client Access Server.   Replace mail.domain.com.au with the name referenced in your SSL Certificate.

 

.

 

Exchange 2013 – 421 4.3.2 Service Not Available

Exchange 2013 has a bug that causes this error message to be returned when sending email / telnetting to port 25:

421 4.3.2 Service not available

Restarting the Microsoft Exchange Hub Transport service resolves the issue temporarily, but it returns within a few hours.

Apparently this issue is caused by adding a custom Receive Connector in Exchange 2013 and choosing the Hub Transport Role instead of the FrontEnd Transport Role for the receive connector.

The solution,  (aside from restarting the Transport service every hour)  is to remove any Receive Connectors that you have added to the server (you can leave the default ones in-place),  and recreate your receive connectors using the FrontEnd Transport option.

Word on the street is that Microsoft don’t consider this a bug ?!?

Oh well,  I have made the changes to my Exchange 2013 server, and testing now to confirm all is well.

.

Can’t install Windows 2012 on a machine that came with Windows 8 OEM pre-loaded

When installing Windows 2012 on a machine that comes with Windows 8 OEM pre-installed,  you may receive a message:

The product key entered does not match any of the Windows images available for installation. Enter a different product key

Windows 8 OEM PCs have the Product ID (PID) recorded in the UEFI BIOS (e.g. Dell Optiplex 9010).  When installing Windows 2012,  it checks the UEFI BIOS and if it finds a key in there it attempts to use it to install Windows.  Of course this fails with an error because the key is for Windows 8 instead of Windows 2012.

The workaround for this is to add the correct 2012 key to the installation media in a file named PID.TXT.  The installation process will check for the PID.TXT file first and ignore the UEFI key.   Of course you can’t just add a file to your Installation DVD,  so I suggest converting it to a bootable USB key using the Windows 7 USB/DVD Download Tool (http://www.microsoftstore.com/store/msstore/html/pbPage.Help_Win7_usbdvd_dwnTool).   See the below links for more info….

Windows 8 or Windows Server 2012 installation may fail with error message: The product key entered does not match any of the Windows images available for installation. Enter a different product key.    http://support.microsoft.com/kb/2796988/EN-US

Windows Setup Edition Configuration and Product ID Files (EI.cfg and PID.txt).  http://technet.microsoft.com/en-us/library/hh824952.aspx
.

User cannot access desktop files

A user with Windows 7 connecting to an SBS2011 server.  He copies files to his desktop from the server, but when he gets home the files are not there.

It turns out that the user was placing very large files and folders on his desktop which was hitting both the 7GB limit for Offline Files, but was also using folder paths that exceeded the 255 character limit.

Server 2012 Essentials 0xc000021a

Error after power failure 0xc000021a
Last Known Good – doesn’t work
Safe Mode – doesn’t work
Ran chkdsk in Advanced Tools mode

Eventually gave up and rebuilt server from scratch, as it was still in a build phase when this issue happened.

SBS 2011 Sharepoint Critical Event Notification

You may continue to receive this error even after following the KB article it references:

An alert was detected on your network. Further investigation into the issue is recommended.

Computer: SBS-01
Date/Time generated: 10/19/2012 9:00:05 AM
Title: Immediate action may be required due to a SharePoint error. See KB2580174 for details
Source: SharePoint Foundation

1.   Make sure you have run PSCONFIG successfully after installing any Sharepoint updates.   http://blogs.technet.com/b/sbs/archive/2011/05/24/you-must-manually-run-psconfig-after-installing-sharepoint-2010-patches.aspx

2.   Check Sharepoint Central Admin -> Servers in Farm, to see if there is still an upgrade that is available.  If so, then PSCONFIG hasn’t completed successfully.

3.   Check the Sharepoint Health Analyzer to identify any reported issues.  Some may not be possible to resolve in your environment, so modifying the alert settings is the next step: http://msmvps.com/blogs/bradley/archive/category/86.aspx