SID history using PowerShell command

This is not the SID of ice age it regards to the security identifier of an object located in Active Directory. The user account SID can be extracted using the PowerShell cmdlet and modified them easily.



To find the properties of user with SID history detail

Get-ADUser "Mail.COM/Region/Asia/Rajis" –properties sidhistory

To search user on specific OU or domain

Get-ADUser -fILTER {nAME -eq "Rajis"} -SearchBase "OU=Asia,OU=Region,DC=MAIL,DC=COM" –properties sidhistory

 To remove SID history value as 

Get-ADUser -fILTER {nAME -eq "Rajis"} -SearchBase "OU=Asia,OU=Region,DC=MAIL,DC=COM" –properties sidhistory | foreach {Set-ADUser $_ -remove @{sidhistory=$_.sidhistory.value}}

Exchange 2013 Backup Status Alert

 Today created a task schedule which can able to read the backup status of all the Exchange 2013 database and provide you email report to your inbox.

This makes easier for our daily operation to review the backup status.

 Login to the Exchange Server - Go to Administrative Tools - Click Task Scheduler - Create New Task

 Task: Exchange 2013 Backup Status

 Description: To Monitor Exchange 2013 Backup Status

 Program/Script: C:\Windows\System32\WindowsPowerShell\v1.0\Powershell.exe

 Add Arugument: -Command ".'E:\Program Files\Microsoft\Exchange Server\V15\Bin\RemoteExchange.ps1'; Connect-ExchangeServer -auto; Send-MailMessage -From admin@mail.com -To rajis@mail.com,u1@mail.com -SmtpServer server.mail.com -Subject Exchange_2013_Backup_Status -body (Get-MailboxDatabase -Status * | Where-Object {$_.Mounted -like "True"} | Select-Object Identity, Mounted*, Last* | Sort-Object LastFullBackup -desc | format-table -autosize | out-string)"

 Note: Change the From Address, To Address, SMTPServer Detail according to your infra

Exchange 2013 Mailbox Move Request History

After the mailbox is moved from the legacy version (Exchange 2007 or 2010) to Exchange server 2013 we sometimes need to understand the duration of time, mailbox size, when the move started and completed from the source to target server.

There are various way to see them if they are recent move

1. Login in the Exchange Admin Center - Go to Recipient - Click Migration - Click Detail
2. Using the Powershell cmdlet Get-MoveRequest raji.subramanian@mail.com | fl
3. If you have used batch migration use the following powershell cmdlet

Get-MigrationUser raji.subramanian@mail.com | fl
Get-MigrationUserStatistics raji.subramanian@mail.com | fl

But the above report will be displayed until the move request ID present in the exchange server 2013. Incase if they are deleted or need to find the move request account detail that was performed long back ago.
Use the following Powershell cmdlet to acheive it

Get-MailboxStatistics -Identity raji.subramanian@mail.com -IncludeMoveHistory
Get-MailboxStatistics -Identity raji.subramanian@mail.com -IncludeMoveReport

Note: I don't see any major difference on the powershell output displayed for IncludeMoveReport and IncludeMoveHistory parameter.

Restart Exchange Service on Multiple Server using Powershell Command

Restart Exchange Service on Multiple Server using Powershell Command

Microsoft Exchange Service can be restarted using services.msc graphical console. But using powershell command it makes the job easier.

To check list of service use the following powershell command

Get-Service -ComputerName | Sort-Object Status

To restart Netlogon service on single computer

Get-Service -ComputerName -Name Netlogon | Restart-Service

To Stop MSExchangeUM service for group of computer

Create computer.txt file on list the servers name on it and save in C drive as computer.txt file

Server1
Server2
Server3

Then run the following command based upon your requirement

Get-Content C:\Computer.txt | ForEach-Object { Stop-Service -InputObject $(Get-Service -Computer $_ -Name MSExchangeUM ) }
To Start MSExchangeUMCR service for group of computer

Get-Content C:\Computer.txt | ForEach-Object { Start-Service -InputObject $(Get-Service -Computer $_ -Name MSExchangeUMCR ) }
To Restart the service which is equal to stop and start the service

Get-Content C:\Computer.txt | ForEach-Object { Restart-Service -InputObject $(Get-Service -Computer $_ -Name netlogon) }

Outlook Web App 2013 - Light Version.

Outlook Web App 2013 - Light Version.

Outlook Web App 2013 light version can support lower version browser and can connect at low bandwidth also.

To enable light version for Exchange server 2013 Outlook Web App.

From Server End execute the following powershell to get applied for end users

Set-OWAMailboxPolicy -Identity "Light OWA Users" -PremiumClientEnabled $False

Set-CASMailbox -Identity "[UserName]" -OWAMailboxPolicy "Light OWA Users".

End user can also able to apply Exchange server 2013 Outlook Web App.by themselves

To change Outlook Web App 2013 into Light version - Log-in to Outlook Web Apps - Click on "Display Setting"  (right side top corner) - Select Outlook Web App Version

The following list of features will not be available with light version on comparing them with premium version of Outlook Web App 2013

1. Spelling checker, Reading pane, Conversation view
2. Notifications, Reminders & Weekly calendar views
3. Right-click menu & Drag-and-drop
4. Resource mailbox management
5. Voice mail options
6. Favorites
7. OCS integration
8. Public folders
9. Share a calendar, Open a shared calendar, Monthly calendar views
10. Retention Policies
11. Users can create and edit personal distribution lists & server-side rules
12. RMS protection
13. RBAC - Change user settings & Administrator settings
14. Web-ready document viewing
15. Nickname cache
16. Message tracking
17. Advanced search
18. MailTips
19. Exchange control panel
20. Attach message to a message

Combining Muliple DAG and MAPI networks - Exchange 2010 DAG Network

Combining Muliple DAG and MAPI networks - Exchange 2010 DAG Network

When you have Primary Site and secondary site hosting Exchange 2010 Mailbox server and configuring DAG network. You can able to view four network under DAG network

 2 MAPI network one in Primary Site (170.0.0,x/16) and one in secondary site (170.1.0,x/16).
 2 Replication network one in Primary Site (30.0.1.0/24) and one in secondary site (30.0.2.0/24).

This can be collasped easily using the following Exchange Powershell Command

Set-DatabaseAvailabilityGroupNetwork DAG1DAGNetwork01 -Subnets 170.0.0,0/16,170.1.0,0/16

Set-DatabaseAvailabilityGroupNetwork DAG1DAGNetwork02 -Subnets 30.0.1.0/24,30.0.2.0/24

Still the network holds the default name inorder to have proper nomenclature run the following command

Set-DatabaseAvailabilityGroupNetwork DAG1DAGNetwork01 -Name MAPI_Network

Set-DatabaseAvailabilityGroupNetwork DAG1DAGNetwork02 -Name Replication_Networ

The following command will disable replication traffic through the MAPI network.

Set-DatabaseAvailabilityGroupNetwork MAPI_Network –ReplicationEnabled $false

In Exchange Server 2013 we don't need to perform the collapsing of DAG Network since it does automatically Ref: http://technet.microsoft.com/en-us/library/dd297927%28v=exchg.150%29.aspx

Exchange management Powershell Error Message: The WSMan client cannot process the request. Proxy is not supported under HTTP transport.

Exchange management Powershell Error Message:

New-PSSession : Connecting to remote server failed with the following error message : The WSMan client cannot process the request. Proxy is not supported under HTTP transport. Change the transport to HTTPS and specify valid proxy information and try again. For more information, see the
about_Remote_Troubleshooting Help topic.
+                 & $script:NewPSSession `
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : AccessDenied,PSSessionOpenFailed
Exception calling "GetSteppablePipeline" with "1" argument(s): "No session has been associated with this implicit
remoting module"
+             $steppablePipeline = $scriptCmd.GetSteppablePipeline($myInvocation.C ...
+     + CategoryInfo          : NotSpecified: (:) [], ParentContainsErrorRecordException
    + FullyQualifiedErrorId : RuntimeException

 Solution:

• Verify the session state using the powershell command  - Get-Pssession | fl The value are  All, Opened, Disconnected, Closed, and Broken.
• Remove the broken powershell session using the command - remove-pssession -id 1
• Check the internet proxy setting - Go to internet Explorer - Tools - Internet Options - Connections - Lan Settings
• Verify the netsh winhttp show proxy
• Export the registry and then delete the WinHttpSettings key from the registry location HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\Connections\WinHttpSettings

Ref: http://blogs.technet.com/b/exchange/archive/2010/02/04/3409289.aspx
        http://exchangeserverpro.com/exchange-2010-certificate-revocation-checks-and-proxy-settings/

Exchange Powershell command error message Microsoft.PowerShell.Commands.Internal.Format.AutosizeInfo Microsoft.PowerShell.Commands.Internal.Format.TableHeaderInfo

Exchange Powershell command error message

 Microsoft.PowerShell.Commands.Internal.Format.AutosizeInfo Microsoft.PowerShell.Commands.Internal.Format.TableHeaderInfo
On executing the below powershell on exporting to html file it will result error message in the html file
Get-MailboxDatabase -Status | Sort-Object DatabaseSize -Descending | ft Name, DatabaseSize -Autosize | ConvertTo-HTML -head $a | Out-File C:\Temp\DBFileSize.htm
Solution:
On removing the format-table and -autosize from the powershell command the error message disappered. Finally the command changed as follows,
Get-MailboxDatabase -Status | Sort-Object DatabaseSize -Descending | Select-Object Name, DatabaseSize, AvailableNewMailboxSpace | ConvertTo-HTML | Out-File C:\Temp\DBFileSize.htm

Failover Primary Active Manager in Exchange Server 2013 DAG

Failover Primary Active Manager in Exchange Server 2013 DAG

1. Verify the cluster group
Command: cluster group

2. Move the cluster to the another DAG node
Command: cluster.exe Group "Cluster Group" /MoveTo:

3. Verifying Replication health check
Command: Test-ReplicationHealth

4. Verifying Primary Active Manager:

Command: Get-DatabaseAvailabilityGroup -Identity -Status | fl name,primaryactivemanager
 

Step by Step installation Exchange server 2013 Cumulative Update 3

Step by Step installation Exchange server 2013 Cumulative Update 3

Although the installation of Exchange server 2013 CU3 is simple few steps needs to be consider while deploying.

• Restart the exchange server before deploying the patch – This will let’s the other user’s session will be dropped and also if there is any pending restart will get cleared off

• There are several places a restart flag could be squirreled.  This is not an exhaustive list:
• Look at HKLM\SYSTEM\CurrentControlSet\Control\Session Manager
• PendingFileRenameOperations
• Use Sysinternals Pendmoves.exe to see if there are pending operations
• HKLM\Software\Microsoft\Windows\CurrentVersion\Component Based Servicing
• RebootPending

• When you are installing using command prompt don’t use exchange management PowerShell instead use the windows PowerShell. Open the windows PowerShell using “Run As” and type the username and credential that holds admin privilege

• In Exchange 2013 it is mandatory to accept the license agreement - /IAcceptExchangeServerLicenseTerms

• After Exchange 2013 Cumulative Update 3 installation we will not able to revert back

Exchange 2013 Quarantine Mailbox

Exchange 2013 Quarantine Mailbox

To find the quarantine mailbox -  Get-mailbox administrator | fl *isq*

The following registry path is created used to store the keys:

HKLM\SYSTEM\CurrentControlSet\Services\MSExchangeIS\\Private-{db guid}\QuarantinedMailboxes\{mailbox guid}

In this path the following keys will be created:

    CrashCount: the amount of crashes detected
    LastCrashTime: the timestamp of the last occurance of a crash
    QuarantineState: is a mailbox quarantined or not
    QuarantineTime: the time the mailbox is placed in quarantine

If the issue doesn’t occur again in two hours the registry key used to store the counter is deleted. The 2 hours is a value which can’t be changed. But there are two other interesting keys:

    MailboxQuarantineCrashThreshold: how many issue may occur before a mailbox is put in quarantine
    MailboxQuarantineDurationInSeconds: how long is the mailbox placed in quarantine

When mailbox put in quarantine it doesn't passes to OPEN_AS_ADMIN flag

Solution:

To manually release the mailbox you will first need to know the GUID of the mailbox. You can lookup the GUID by using the get-mailboxstatistics cmdlet just like this:

Get-Mailbox support |select name, GUID
Once you have found the GUID you will need to find the corresponding registry path. As discussed earlier each poisoned mailbox has the key MailboxQuarantineDurationInSeconds modify the value to for example 0 or 1. After you’ve made the registry key change perform one of the following tasks:

•     Dismount/mount the database
•     Restart the Information Store
•     Reboot your server

Exchange Server 2013 Outlook Anywhere SSLOffloading

Exchange Server 2013 Outlook Anywhere SSLOffloading

The product team made Exchange 2013 Outlook Anywhere SSLOffloading the default value as true which is not in the Exchange 2007/2010. Not sure is there any specific reason but it should be enabled for SSL offloading. The documentation is not much clear as we have in Exchange 2010 and 2007 other than just note on Exchange 2013 powershell command to configure Outlook anywhere: -

Exchange 2013 Ref: http://technet.microsoft.com/en-us/library/bb123545%28v=exchg.150%29.aspx

Exchange 2007 -  Ref: http://technet.microsoft.com/en-us/library/bb123889%28v=exchg.80%29.aspx

Do not use this option unless you are sure that you have an SSL accelerator that can handle SSL offloading. If you do not have an SSL accelerator that can handle SSL offloading, and you select this option, Outlook Anywhere will not function correctly.

Exchange 2010 - Ref: http://technet.microsoft.com/en-us/library/bb123542%28v=exchg.141%29.aspx

Don't use this option unless you're sure that you have an SSL accelerator that can handle SSL offloading. If you don't have an SSL accelerator that can handle SSL offloading, and you select this option, Outlook Anywhere won't function correctly.

http://social.technet.microsoft.com/wiki/contents/articles/1267.how-to-configure-ssl-offloading-in-exchange-2010.aspx

Exchange Server 2013 Message Tracking

Exchange 2013 Message Tracking

Message Tracking is enabled default in Exchange 2013 mailbox server. To configure message tracking

Syntax

Set-TransportService -MessageTrackingLogEnabled <$true | $false> -MessageTrackingLogMaxAge

-MessageTrackingLogMaxDirectorySize -MessageTrackingLogMaxFileSize -MessageTrackingLogPath -MessageTrackingLogSubjectLoggingEnabled <$true|$false>

The default limits are

Individual message tracking log files is 10 MB.
Maximum size for the directory that contains the message tracking log files is 1000 MB.
Maximum age for the message tracking log files is 30 days.

To track the emails in Exchange 2013

Get-MessageTrackingLog -Start “Feb 25 2013” | Out-GridView

Get-messagetrackinglog -Start “Feb 25 2013” -ResultSize Unlimited | select-object eventid,timestamp,messageid,sender,recipients,messagesubject | out-gridview

Ref: http://technet.microsoft.com/en-us/library/bb124375%28v=exchg.150%29.aspx#Structure

Exchange Server 2010 Service Pack 3 Rollup Update 3

Exchange Server 2010 Service Pack 3 Update Rollup 3

Most of the Exchange 2010 CAS issue got fixed in Rollup 3.

Find the detail as follows

http://support.microsoft.com/kb/2891587/en-us?sd=rss

http://www.microsoft.com/en-us/download/details.aspx?id=41173

Issues that the update rollup resolves

Update Rollup 3 for Exchange Server 2010 SP3 contains the fix for the security issue that is described in Security Bulletin MS13-061 and resolves the issues that are described in the following Microsoft Knowledge Base (KB) articles:

• 2715761 "550 5.6.0" NDR when you send a yearly recurring meeting request in an Exchange Server 2010 environment
• 2839533 RPC Client Access service freezes in an Exchange Server 2010 environment
• 2840454 "The rules on this computer do not match the rules on Microsoft Exchange" error when you manage rules by using Outlook 2013 in an Exchange Server 2010 environment
• 2874070 Public folders are exposed although the user does not have rights to see the parent folders in an Exchange Server 2010 SP3 environment
• 2878175 Client Access server crashes when you use Outlook with a Riverbed WAN optimizer in an Exchange Server 2010 environment
• 2879320 Retention action setting is not updated in FAI items by running the Set-RetentionPolicyTag cmdlet in an Exchange Server 2010 environment
• 2879736 Office 365 users cannot retrieve an on-premises user’s free/busy data in an Exchange Server 2010-based hybrid deployment
• 2880153 RPC Client Access Service crashes if Outlook is in online mode in an Exchange Server 2010 environment
• 2880290 RPC Client Access service crashes when you use Outlook in ANSI online mode in an Exchange Server 2010 environment
• 2882467 RPC Client Access service stops if Outlook is in online mode in an Exchange Server 2010 environment
• 2882677 BlackBerry device is not redirected in an Exchange Server 2010 environment
• 2886469 EAS client receives status code 8 during synchronization in an on-premises Exchange Server 2010 environment
• 2886567 "Objects added to a BindingSource's list must all be of the same type" error message when you add an additional domain name in Exchange Server 2010 SP3
• 2887574 RPC Client Access service freezes when your mailbox reaches the quota limit in an Exchange Server 2010 environment
• 2888406 Mailbox Replication service crashes when you try to move mailboxes in an Exchange Server 2010 environment
• 2888906 Events 1000, 4999, and 9775 are logged when Store.exe crashes on an Exchange Server 2010 SP3 Mailbox server
• 2888911 W3wp.exe crashes when you decline a meeting request by using Outlook Web App or an EWS application in an Exchange Server 2010 environment
• 2890650 Items in the Drafts folder are not stamped with the retention policy tag in an Exchange Server 2010 or 2013 environment
• 2891194 Exchange ActiveSync devices are marked as "Blocked" in EMS and EMC when the devices are synchronizing with the Exchange Server 2010 server
• 2892337 Outlook client freezes when you try to sort email folders by columns in an Exchange Server 2010 environment
• 2893437 Delegate can read your AD RMS protected messages by using Outlook Web App in an Exchange Server 2010 environment
• 2896304 Background image is displayed incorrectly in an email message when a disclaimer rule is enabled in an Exchange Server 2010 environment
• 2899146 You cannot drag email messages to other folders by using Outlook Web App in an Exchange Server 2010 environment

Exchange Server 2013 Cumulative Update 3

Exchange Server 2013  Cumulative Update 3 got released which fix most of the issue Exchange 2013 issues...

You can download them from - http://www.microsoft.com/en-us/download/details.aspx?id=41175

Issues that the cumulative update resolves

Cumulative Update 3 for Microsoft Exchange Server 2013 contains the fix for the security issue that is described in Security Bulletin MS13-061 and resolves the issues that are described in the following Microsoft Knowledge Base (KB) articles:

• 2874216 Security issue that is described in Security Bulletin MS13-061 is resolved by an Exchange Server update
• 2865161 "Errors: Failed exporting item id: from source id" when you try to copy search results in an Exchange Server 2013 environment
• 2871980 Child domains are not displayed for selection when you create a mailbox by using EAC in an Exchange Server 2013 environment
• 2878160 "The Active Directory user wasn't found" error when you create or update an In-Place eDiscovery search in an Exchange Server 2013 environment
• 2882608 Exchange Server 2013 does not share the inproxy.dll file
• 2886115 Retention policies are not applied to Exchange Server 2013 mailboxes when user accounts are on different domains
• 2888274 WebClientReadFormQueryString string and WebClientEditFormQueryString string return incorrect URLs in an Exchange Server 2013 environment
• 2888315 Event 2112 or 2180 is logged when you try to back up a database in an Exchange Server 2013 environment
• 2888612 Retention policy does not work after you run a cmdlet in an Exchange Server 2013 environment
• 2889786 Sign-in format for Outlook Web App on mobile devices is not adjusted according to the Set-OwaVirtualDerictory cmdlet in an Exchange Server 2013 environment
• 2890650 Items in the Drafts folder are not stamped with the retention policy tag in an Exchange Server 2010 or 2013 environment
• 2895487 "Copy Search Results" option does not work in an Exchange server 2013 environment
• 2895500 DBCS characters appear garbled when you run some PowerShell scripts in EMS in an Exchange Server 2013 environment
• 2895678 "Nombre de usuario\dominio" is displayed unexpectedly on the Spanish version of the OWA and EAC logon pages in an Exchange Server 2013 environment
• 2902929 You cannot forward an external meeting request in an Exchange Server 2013 environment
• 2902929 You cannot forward an external meeting request in an Exchange Server 2013 environment
• 2902933 "Generate incident report" does not display the "Bcc" field in an Exchange Server 2013 environment
• 2902934 Korean language localization issue in Exchange 2013 OWA user interface
• 2902936 You cannot change SMTP addresses for distribution groups by using EAC in an Exchange Server 2013 environment
• 2902938 You cannot preview Office documents in shared folders by using Outlook Web App in an Exchange Server 2013 environment
• 2902939 EMS connection error when you separately install an Exchange Server 2013 Mailbox server and a Client Access server
• 2883203 Exchange Server 2013 restarts frequently after Cumulative Update 2 is installed
• 2890814 No redirection to the Outlook Web App URL for Exchange Online users in an Exchange hybrid deployment

Exchange 2013 Autodiscover Features

• Autodiscover wont't works when the email addresss is hidden from Exchagne address list
• The email clients supports Autodiscover are Outlook 2007/2010/2013, Outlook 2011 for Mac OS X support Autodiscover and the built-in mail clients for Windows Phone and Apple iOS.
• Autodiscover provides - Availability service, the out of office (OOF) service, the OAB download endpoint, the Unified Messaging service, Exchange Administration Center (EAC), public folder mailboxes, shared mailboxes, and site mailboxes

Exchange Server Installation Failure - WaterMarks

Exchange 2013 Cumulative Update 3

Today on viewing the KB article for Backup restore failure found they have launched Exchange 2013 Cumulative Update 3 which is the know cause for backup restoration failure...

This is a known issue in versions of Exchange Server 2013 that are earlier than Cumulative Update 3. This issue occurs because the LOG_SIGNATURE_ID and LOG_SIGNATURE_TIMESTAMP elements in the Backup Components Document have a value of 0 in the backup stage. However, the Exchange VSS writer prohibits restoring data in this state.

http://support.microsoft.com/kb/2903768/en-us?sd=rss&spid=730 


But the good news is that they have still not launched Exchange 2013 Cumulative Update 3. Microsoft is so fast in publishing the KB before they launch the product in public.. :)

Bug in Exchange 2013 Cumulative Update 2

Unable to increase the exchange database to 100 after upgrading to Exchange 2013 Cumulative Update 2 Enterprise Edition from RTM

Log Name:      Application
Source:        MSExchangeIS
Event ID:      40003
Task Category: High Availability
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Test-MBX-0.exchange.msft
Description:
Exceeded the max number of 50 databases on this server.

Solution:

Type your Enterprise Edition product key on the server again and restart the Microsoft Exchange Information Store service. This will fix the issue

New features in Exchange 2013 Client Access Server

• In Exchange 2010 CAS a client connects to provides an encrypted cookie after the client is authenticated.Passing that cookie to a different CAS means that the receiving CAS can’t read it, so it has to ask the client to authenticate again.
• In Exchange 2013, the CAS authentication cookie is encrypted with the public key of the certificate assigned to the CAS, so any server that has the corresponding private key can decrypt the cookie.
• The Exchange 2013 CAS role server includes a new proxy engine, httpproxy.dll. This replaces the role of the oldrpcproxy.dll, and Exchange 2013 CAS thus cannot proxy RPC traffic directly. When it receives HTTPS encapsulated RPC traffic, it cannot de-encapsulate it directly; instead, it must proxy it to another CAS server that still has rpcproxy.dll. For this proxy operation to succeed, the Exchange 2013 mailbox server or the downlevel CAS servers must have rpcproxy.dll installed (it’s installed by default on the Exchange 2013 mailbox role), and they must be enabled for Outlook Anywhere.