Archive for July 2013

Want to control the properties of e-mail messages sent to a specific domain in MS Exchange powershell   Leave a comment

Create a new remote domain by using the New-RemoteDomain cmdlet.

Type:

New-RemoteDomain -Name “Contoso.com Configuration” -DomainName contoso.com

Then modify the properties that you want for this remote domain by using the Set-RemoteDomain cmdlet:

Set-RemoteDomain “Contoso.com Configuration” -AutoReplyEnabled $True -AutoForwardEnabled $True

Posted July 31, 2013 by Prem Rana in EMS Commands (Powershell)

Tired of typing a long command every time that you want to do something in powershell MS exchange   Leave a comment

Set-Alias GetMre Get-ManagementRoleEntry

For all the current aliases, type:

Get-Alias

Posted July 31, 2013 by Prem Rana in EMS Commands (Powershell)

Forgot what the available parameters are on a cmdlet in powershell for exchange   Leave a comment

Just use tab completion! Type:

Set-Mailbox -<tab>

When you type a hyphen (-) and then press the TAB key, you cycle through all the available parameters on the cmdlet. Want to narrow your search? Type part
of the parameter’s name and then press the TAB key. Type:

Set-Mailbox -Prohibit<tab>

Posted July 31, 2013 by Prem Rana in EMS Commands (Powershell)

Did you know that you can allow users in your Exchange organization to publish their calendars to the Internet so that anyone can view their free/busy availability? Just configure a few settings to get started. To enable an Outlook Web App Virtual Directory and allow calendar publishing,   Leave a comment

Set-OWAVirtualDirectory -Identity <Client Access server> -ExternalURL <External URL for Client Access server> -CalendarPublishingEnabled $true

To set the web proxy for the Mailbox server, type:

Set-ExchangeServer -Identity “<Mailbox server>” -InternalWebProxy <webproxy URL>

Finish by setting up a sharing policy for the “Anonymous” Internet domain and assign the sharing policy to a user mailbox. First type:

New-SharingPolicy -Name “<policy name>” -Domains ‘Anonymous: CalendarSharingFreeBusySimple’ -Enabled $True

Then type:

Get-Mailbox -Identity <user alias> | Set-Mailbox -SharingPolicy “<policy name>”

Posted July 31, 2013 by Prem Rana in EMS Commands (Powershell)

How to Get quick health and status information for your mailbox database copies in powershell   Leave a comment

Get-DatabaseAvailabilityGroup DAG1 | %{ $_.Servers | %{ Get-MailboxDatabaseCopyStatus -Server $_ } }

Posted July 31, 2013 by Prem Rana in EMS Commands (Powershell)

How to Remove Distribution Group Membership Using Powershell in Exchange 2010   Leave a comment

 

$DGs= Get-DistributionGroup –ResultSize Unlimited
$DGs | where { (Get-DistributionGroupMember $_ –ResultSize Unlimited | foreach {$_.PrimarySmtpAddress}) -contains “TestUser1@prem.com”}
foreach( $dg in $DGs){Remove-DistributionGroupMember $dg -Member TestUser1@prem.com}

Posted July 29, 2013 by Prem Rana in EMS Commands (Powershell)

Event ID 1025 with error code “0x80041606” when you use Outlook in online mode to search for a keyword in Exchange Server 2007   Leave a comment

Event ID Details:-

Event ID : 1025
Category : None
Source : MSExchangeIS Mailbox Store
Type : Warning
Generated : <date>
Written : <date>
Machine : <computer>
Message : An error occurred on database “<storage group/mailbox database>”.
Function name or description of problem: Content Indexing received an unusual and
unexpect error code from MSSearch
Error: 0x80041606

 

Cause Of Issue:-

This issue occurs because Exchange Search has a query restriction of 200,000

nodes. When a prefix search exceeds the query restriction, the search returns

QUERY_E_TOOCOMPLEX. Therefore, 0x80041606 is logged as part of

event ID 1025. By default, all searches that use Outlook online mode in an

Exchange 2007 environment are prefix searches. If single digits or letters

are used, this causes the system to search for all numbers or words that begin

with the single digit or letter across the whole mailbox database. If the 200,000

nodes default limit is reached, the search returns the error.

Note The most common way to reach the 200,000 nodes limit is to search for

a word or phrase that contains a single digit or letter. There are also other less

common causes, such as entering very complex searches that have many AND,

OR, and NOT operators. Additionally, complex combinations of date ranges and

search terms, many entries in the To and From fields, or a combination of all

these things may cause the limit to be reached.

 

For More Details Check Below Link:-

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

Posted July 18, 2013 by Prem Rana in EMS Commands (Powershell)