Using Exchange PowerShell:
Set-MapiVirtualDirectory -Identity "servername\mapi (Default Web Site)" -InternalUrl https://subdomain.domain.com/mapi -ExternalUrl https://subdomain.domain.com/mapi -IISAuthenticationMethods NTLM,Negotiate
Set-OrganizationConfig -MapiHttpEnabled $true
Mostrar mensagens com a etiqueta Exchange. Mostrar todas as mensagens
Mostrar mensagens com a etiqueta Exchange. Mostrar todas as mensagens
quarta-feira, 20 de janeiro de 2016
sexta-feira, 11 de dezembro de 2015
Add an IP Block List Provider to Exchange Server 2013 Edge Transport
One of the transport agents that is installed on the Exchange 2013 Edge Transport server is the connection filter agent.
When your Exchange organization is receiving spam you can add the IP addresses of the spammers to an IP block list on the Edge Transport server. However this is quite inefficient, as you’ll constantly be adding new IP addresses to the list.
A more effective approach is to use one or more IP block list providers, such as Spamhaus (my personal favourite) or SpamCop.
To add Spamhaus to your connection filter agent run the follow Exchange Management Shell command on the Edge Transport server.
Note you can change the rejection message that it sent back to the sender.
You can add multiple providers, just make sure you check their guidance on whether there are issues adding multiple lookup domains from the same provider. Also make sure you check their terms and conditions and comply with any commercial usage policies they have.
[PS] C:\>Get-TransportAgent Identity Enabled Priority -------- ------- -------- Connection Filtering Agent True 1 Address Rewriting Inbound Agent True 2 Edge Rule Agent True 3 Content Filter Agent True 4 Sender Id Agent True 5 Sender Filter Agent True 6 Recipient Filter Agent True 7 Protocol Analysis Agent True 8 Attachment Filtering Agent True 9 Address Rewriting Outbound Agent True 10
The connection filter agent looks at the IP address of a server that is making an SMTP connection to the Edge Transport server and decides whether to block or allow the connection. It makes the decision by looking up the IP address in a block list, allow list, or by querying a block/allow list provider.
When your Exchange organization is receiving spam you can add the IP addresses of the spammers to an IP block list on the Edge Transport server. However this is quite inefficient, as you’ll constantly be adding new IP addresses to the list.
A more effective approach is to use one or more IP block list providers, such as Spamhaus (my personal favourite) or SpamCop.
To add Spamhaus to your connection filter agent run the follow Exchange Management Shell command on the Edge Transport server.
[PS] C:\>Add-IPBlockListProvider -Name Spamhaus -LookupDomain zen.spamhaus.org -AnyMatch $true -Enabled $true -RejectionResponse "IP address is listed by Spamhaus"
Note you can change the rejection message that it sent back to the sender.
[PS] C:\>Set-IPBlockListProvider Spamhaus -RejectionResponse "IP address is listed by Spamhaus Zen."
You can add multiple providers, just make sure you check their guidance on whether there are issues adding multiple lookup domains from the same provider. Also make sure you check their terms and conditions and comply with any commercial usage policies they have.
[PS] C:\>Get-IPBlockListProvider
Name LookupDomain Priority ---- ------------ -------- Spamhaus zen.spamhaus.org 1 SpamCop bl.spamcop.net 2After the block list provider has been in place for a day or two you can see the results by running the Get-AntispamTopRBLProviders.ps1 script that ships with Exchange.
[PS] C:\Program Files\Microsoft\Exchange Server\V15\scripts>.\get-AntispamTopRBLProviders.ps1 Name Value ---- ----- Spamhaus 12
quarta-feira, 25 de novembro de 2015
How to Defrag an Exchange 2010 Mailbox Database
http://exchangeserverpro.com/defrag-exchange-2010-mailbox-database/
Exchange Server 2010 mailbox databases grow in size as the data within them grows. But they will never shrink when data is removed from them.
For example if you have a 20Gb mailbox database file and move 4Gb worth of mailboxes to another database, the file will remain at 20Gb in size.
However, the database itself will have 4Gb of “white space” in it, which is space that is available for new data to be written without growing the size of the file.
Your options to reclaim that space are to either:
- Create a new mailbox database and move all the mailboxes to that database
- Perform an offline defrag of the existing database to shrink the file
Each option has pros and cons. An offline defrag involves an outage for all users on that database, but may be more convenient if there is not additional storage available to allocate to the Exchange server to hold the new database.
On the other hand a mailbox migration has fewer risks, can be less disruptive as a whole, but will generate a lot of transaction logging that needs to be kept under control so it may take longer (ie several nights/weekends to migrate) as opposed to just one outage for a defrag.
Determining Free Space in an Exchange 2010 Mailbox Database
In Exchange 2010 you can see how big your mailbox databases are, and how much white space they have, by running the following command in the Exchange Management Shell.
[PS] C:\>Get-MailboxDatabase -Status | ft name,databasesize,availablenewmailboxspace -auto
Name DatabaseSize AvailableNewMailboxSpace
---- ------------ ------------------------
MB-HO-01 18.26 GB (19,604,766,720 bytes) 9.544 GB (10,247,766,016 bytes)
MB-HO-02 15.63 GB (16,785,670,144 bytes) 3.696 GB (3,968,761,856 bytes)
MB-HO-Archive-01 648.1 MB (679,542,784 bytes) 134.6 MB (141,164,544 bytes)
In the example above the database MB-HO-01 is 18.26Gb in size but has 9.544Gb white space due to archiving that has occurred. If you want to reclaim that disk space then the file can be shrunk by using eseutil to defrag it.
In this example I will demonstrate how to defrag a mailbox database for a single Exchange 2010 Mailbox server that is not a member of a Database Availability Group.
Do not follow the procedure in this document if your Mailbox server is a member of a DAG. Before you defrag any mailbox database please read and understand the pros and cons of this operation and make the best decision for your specific situation.
Preparing to Defrag an Exchange 2010 Mailbox Database
The first thing to be aware of when planning a defrag is that you can only perform this task when the database is dismounted. This means that users with mailboxes on that database will not be able to access their email while you are defragging it.
The second thing to be aware of is that you need some available disk space to perform the defrag. This is because a new file is written during the defrag process, so for a period of time both the old and new files will exist, as well as a temporary file that eseutil creates.
So to plan for an Exchange 2010 mailbox database defrag you need an amount of free space equivalent to 1.1x the predicted size of the new file.
In this example that would be:
18.26 – 9.544 = 8.7
8.7 x 1.1 = 9.57
In other words, I’ll need about 10Gb of free disk space to run this defrag. Since I don’t have that much free space on the same drive as the database I will need to specify a different temporary location when I run eseutil. This can be another local drive or a UNC path, just be aware that if you are using a UNC path the defrag will take longer due to network latency.
Before proceeding you should be sure that you have a good, working backup that you can use for recovery if something goes wrong during the defrag.
Using ESEUtil to Defrag an Exchange 2010 Mailbox Database
Open the Exchange Management Shell and navigate to the folder containing the database file.
cd D:\Data\MB-HO-01
Dismount the mailbox database.
Dismount-Database MB-HO-01
No run ESEUtil to defrag the file.
[PS] D:\Data\MB-HO-01>eseutil /d MB-HO-01.edb /t\\testserver\defrag\temp.edb
Extensible Storage Engine Utilities for Microsoft(R) Exchange Server
Version 14.01
Copyright (C) Microsoft Corporation. All Rights Reserved.
Initiating DEFRAGMENTATION mode...
Database: MB-HO-01.edb
Defragmentation Status (% complete)
0 10 20 30 40 50 60 70 80 90 100
|----|----|----|----|----|----|----|----|----|----|
...................................................
Moving '\\testserver\defrag\temp.edb' to 'MB-HO-01.edb'...
File Copy Status (% complete)
0 10 20 30 40 50 60 70 80 90 100
|----|----|----|----|----|----|----|----|----|----|
...................................................
Note:
It is recommended that you immediately perform a full backup
of this database. If you restore a backup made before the
defragmentation, the database will be rolled back to the state
it was in at the time of that backup.
Operation completed successfully in 3788.218 seconds.
Mount the database again.
mount-Database MB-HO-01
You can now see that the file is smaller, and all the white space is gone.
Get-MailboxDatabase -Status | ft name,databasesize,availablenewmailboxspace -auto
Name DatabaseSize AvailableNewMailboxSpace
---- ------------ ------------------------
MB-HO-01 8.328 GB (8,942,190,592 bytes) 5.219 MB (5,472,256 bytes)
MB-HO-02 15.63 GB (16,785,670,144 bytes) 3.696 GB (3,968,761,856 bytes)
MB-HO-Archive-01 648.1 MB (679,542,784 bytes) 134.6 MB (141,164,544 bytes)
As you saw when ESEUtil completed you should run a full backup of the database at your next backup window.
How to use Nslookup to verify MX record configuration
The example below shows how MX records appear for the fictitious domain, example.com.
C:\> nslookup
Default Server: pdc.corp.example.com
Address: 192.168.6.13
> server 172.31.01.01
Default Server: dns1.example.com
Address: 172.31.01.01
> set q=mx
> example.com.
Server: dns1.example.com
Address: 10.107.1.7
example.com MX preference = 10, mail exchanger = mail1.example.com
example.com MX preference = 10, mail exchanger = mail2.example.com
example.com MX preference = 10, mail exchanger = mail3.example.com
example.com MX preference = 10, mail exchanger = mail4.example.com
example.com MX preference = 10, mail exchanger = mail5.example.com
mail1.example.com internet address = 172.31.31.01
mail2.example.com internet address = 172.31.31.02
mail3.example.com internet address = 172.31.31.03
mail4.example.com internet address = 172.31.31.04
mail5.example.com internet address = 172.31.31.05
In this example, the preconfigured DNS server is behind a proxy server. Therefore, an external or Internet DNS server with a known IP address of 172.31.01.01 was used to perform the query. Next, the query type was set to MX to locate the mail exchangers for example.com. In this example, five SMTP servers are equally balanced, each with its own IP address. However, your domain might only have a single entry, as seen in the following example:
contoso.com MX preference = 10, mail exchanger = mailbox.contoso.com
mailbox.contoso.com internet address = 10.57.22.3
segunda-feira, 23 de novembro de 2015
Removing a Mailbox from Quarantine in Exchange Server 2013
n Exchange Server 2010 the process required more manual work (you can check the step by step http://itprocentral.com/releasing-a-mailbox-from-exchange-server-2010-quarantine/ ), however a new set of cmdlets *-MailboxQuarantine were introduced and they help the administrator to add and remove mailboxes in the quarantine.
A good way to check a list of all mailboxes that are being quarantined is using the following cmdlet:
Get-Mailbox –Server <Server-Name> –ResultSize unlimited | Get-MailboxStatistics | Where-Object { $_.IsQuarantined –eq $True } | Select DisplayName,IsQuarantined,QuarantineEnd
In order to remove a mailbox from there, just use the following the cmdlet:
Disable-MailboxQuarantine <mailbox>
http://itprocentral.com/removing-a-mailbox-from-quarantine-in-exchange-server-2013/
quinta-feira, 15 de outubro de 2015
terça-feira, 7 de outubro de 2014
Move to the Cloud (Office 365)
Microsoft gives no real option to send files to Office 365, there are some really good options out there
Like this: http://www.thinkscape.com/SharePoint-Online-File-Migration-Tool/
Very good tool with an integrated checking rules on file size, path's and file types that will not be sent over. So you can clean your file system before a full copy.
Subscrever:
Mensagens (Atom)