Viral Rathod Exchange Server 2016 Blog

Microsoft Exchange Server Blog

  • Click here to Register for Experts-Exchange Account

  • My Experts Exchange Profile

  • Disclaimer

    All information is provided "AS IS" with no warranties, and confer no rights, and as such you perform at your own risk.

    NOTE: You should always make a backup of your server or export the registry before making any changes to it.

How to test autodiscover connection for a user

Posted by viralr on December 2, 2016

Test-OutlookWebServices -identity: test@example.com –MailboxCredential (Get-Credential)


 

Posted in Exchange Server 2003 Posts | Leave a Comment »

Email Server SMTP Test for Outgoing E-mails

Posted by viralr on February 24, 2015

Email Server SMTP Test for Outgoing E-mails :-

If you are facing issues where your outgoing Emails are consistently rejected by other servers or land up in Junk Email or SPAM folders of the recipient mail box, this test can help you in identifying the problems.

Testing Process

  1. Send an Email to test@allaboutspam.com
  2. That email will bounce with a URL in the bounce messge.
  3. Either click on the URL or Copy/paste the URL in a browser.
  4. You will see report on your Email Server.

 

Ref : http://www.allaboutspam.com/email-server-test/

Posted in Exchange Server 2003 Posts, Exchange Server 2007 Posts, Exchange Server 2010 Posts | Leave a Comment »

Exchange 2013- Blank ECP / OWA screen, event ID 15021 HttpEvent in system event log

Posted by viralr on February 20, 2015

Exchange 2013- Blank ECP / OWA screen, event ID 15021 HttpEvent in system event log : An error occurred while using SSL configuration for endpoint 127.0.0.1:443 :

When you log in to OWA or EMC using a browser, you may see a blank screen after you enter your credentials. You may also notice that the event log shows event 15201:

An error occurred while using SSL configuration for endpoint 0.0.0.0:444

empty page

This can be caused by an incorrect certificate being assigned to the port. To fix this error,

  • Open the Command Prompt
  • Run – netsh http show sslcert

InvalidCert

  • Copy and save content on notepad or take a screenshot of port 443’s certificate hash and application ID because we will need it.
  • export content
  • Delete the certificate causing errors (Given on Screen Shot)
  • netsh http delete sslcert ipport=0.0.0.0:444
  • delete-certificate-causing-errors
  • Read out the certificate hash from the certificate

certificate-hash

  • Assign new certificate: netsh http add sslcert ipport=0.0.0.0:444 certhash=XXXXXX  appid=”{XXXXXXX}”

    add cert

  • Do IISRESET OR REBOOT the server
  • Good luck!

Posted in Exchange Server 2013 Posts | Leave a Comment »

This message is too large to send. To be able to send it, make the message smaller, for example, by removing attachments.

Posted by viralr on May 29, 2014

Unable to send large attachments and get this bounce back:

From: postmaster@MYDOMAIN.LOCAL [mailto:postmaster@MYDOMAIN.LOCAL]
Sent: Wednesday, May 28, 2014 4:14 PM
To: Mathews, John
Subject: Undeliverable: FW: Re: Remaining
Delivery has failed to these recipients or groups:
user@mydomain.com
This message is too large to send. To be able to send it, make the message smaller, for example, by removing attachments.

Diagnostic information for administrators:
Generating server: EXCHANGESERVER.MYDOMAIN.LOCAL
user@mydomain.com
#< #5.2.3 smtp;550 5.2.3 RESOLVER.RST.SendSizeLimit.Org; message too large for this organization> #SMTP#

To troubleshoot this issue use the following steps:-

The email size restriction for user mailbox will be applied in the following order

  1. Global Transport configuration settings
  2. Send connector size restriction
  3. Receive connector size restriction
  4. In the user mailbox properties of send and receive size limit

Please use the below command to check the limts,

To verify global transport settings all Hub Transport servers in the Exchange Organization :-

Get-TransportConfig | ft MaxSendSize, MaxReceiveSize

To modify the sending and receiving email message size to 100 MB in the global Tranport configuration

Set-TransportConfig –MaxSendSize 20MB –MaxReceiveSize 100MB

To verify and modify the send connector size,Send connector are used to send emails out of the exchange organization and the default size is 10 MB.

Get-SendConnector | ft name, MaxMessageSize

Set-SendConnector <Connector Name> –MaxMessageSize 50MB

To verify and modify the receive connector size,Receive connector are used to receive emails from the internet or application and the default size is 10 MB.

Get-ReceiveConnector | ft name, MaxMessageSize

Set-ReceiveConnector <Connector Name> –MaxMessageSize 50MB

The send and receive email message size can be granular controlled in the user mailbox properties. To verify the and modify the size

Get-mailbox | ft Name, MaxSendSize, MaxReceiveSize

Set-Mailbox “test” –MaxSendSize 20MB –MaxReceiveSize 20MB

 

——————————————————————————————————————————————-

There are various error message which is listed below will occur if the value is not configured as per the above rule.

Error 1:

The following recipient(s) could not be reached:

test@test.com on 01/15/2014 3:54 PM

This message is larger than the current system limit or the recipient’s mailbox is full. Create a shorter message body or remove attachments and try sending it again.

<mail.com #5.2.3 smtp;450 5.2.3 Msg Size greater than allowed by Remote Host>

Error 2:

The following recipient(s) could not be reached

test@test.com  on 01/15/2014 3:54 PM

This message is larger than the current system limit or the recipient’s mailbox is full. Create a shorter message body or remove attachments and try sending it again.

<mail.com #5.2.3 smtp;550 5.2.3 RESOLVER.RST.SendSizeLimit; message too large for this sender>

Error 3:

Delivery has failed to these recipients or distribution lists:

administrator@mail.com
This message exceeds the maximum message size allowed. Microsoft Exchange will not try to redeliver this message for you. Please make the message smaller — by removing attachments, for example — and try sending it again, or provide the following diagnostic text to your system administrator.

Diagnostic information for administrators:
Generating server: MBX01.mail.com
administrator@mail.com
#550 5.2.3 RESOLVER.RST.SendSizeLimit; message too large for this sender ##

Error 4

OWA Error – The request filter module is configured to deny a request that exceeds the request content length”

Error 5

EWS Error –   Email is goes in drafts or never leaves the outbox and the client receives an “exceeded the size limit”

Posted in Exchange Server 2013 Posts | Leave a Comment »

Internet Explorer 11 Only Allows “Use the light version of Outlook Web App”

Posted by viralr on February 17, 2014

If you upgraded to Windows 8.1 and tried to access Outlook Web App with the new Internet Explorer 11, you probably noticed that the “Use the light version of Outlook Web App” checkbox is checked and disabled on the login page:

owa-light

That means that IE11 is willing to render only the basic version of OWA which was originally designed to target legacy browsers. This is quite embarassing, because IE11 is a really modern browser even in the preview! The solution is to force IE to render OWA in compatibility mode. You can add the site to the compatibility list in the Tools –> Compatibility View Settings dialog: Click Add button

Compability

compatibility-view-settings

IF the above settings didn’t resolve the issue then try to add your OWA URL to the list of sites in the Intranet Zone in the Tools –> Internet Options –> Security –> Local intranet –> Sites –> Advanced dialog.

According to some forum posts, the same issue arises with Office 365 and some popular websites like GitHub as well.

Ref : http://gyorgybalassy.wordpress.com/2013/07/05/use-owa-in-full-version-with-ie11/

Posted in Exchange Server 2010 Posts, Exchange Server 2013 Posts | Leave a Comment »

Exchange Server 2013

Posted by viralr on September 14, 2013

What’s New In Exchange 2013 –

What’s New In Exchange 2013 Video From Trainsignal :-

Installing Exchange Server 2013 –

Exchange 2013 Installation Training Video From Trainsignal :-

Transition from Exchange 2003 to Exchange 2010 to Exchange 2013 –

Transition from Exchange 2003 to Exchange 2010 to Exchange 2013 Video from Trainsignal :-

Exchange 2010 to Exchange 2013 Migration Docs from petenetlive :-

Migration From Exchange 2010 to Exchange 2013 Part 1

http://www.petenetlive.com/KB/Article/0000788.htm

Migration From Exchange 2010 to Exchange 2013 Part 2

http://www.petenetlive.com/KB/Article/0000789.htm

Posted in Exchange Server 2013 Posts | Leave a Comment »

Active Directory Interview Question and Answer

Posted by viralr on September 5, 2013

Active Directory Interview Question and Answer :-

1) Whar are the New Features in Windows Server 2008 R2:-

1. Active Directory Administrative Center—For administrators, the biggest change in Server 2008 R2 is undoubtedly the new Active Directory Administrative Center, which replaces the older Active Directory, Domains and Trusts, Sites and Services, and Users and Computers management tools. The Active Directory Administrative Center is built on top of PowerShell and its actions are scriptable. One really nice feature is the new Active Directory Recycle Bin.

2. Remote server management—Server Manager was one of the best improvements in Server 2008 because it provides a centralized and useful console for managing Windows Server. However, Server Manager is limited to working with the local system. With R2, Server Manager can be installed on network clients and can be used to manage remote Server 2008 systems.

3. PowerShell 2.0—Server 2008 R2 includes PowerShell 2.0, which features improved WMI cmdlets and support for running scripts on remote systems, creating ScriptCmdlets, and running background jobs. In addition, R2 has a new graphical PowerShell UI for developing and debugging PowerShell scripts. PowerShell 2.0 is compatible with PowerShell 1.0

4. Support for the .NET Framework in Server Core—One of the biggest disappointments in the original Server 2008 release was the lack of support for the .NET Framework in Server Core, which meant that technologies that seemed perfect for Server Core, such as Windows PowerShell and ASP.NET applications, couldn’t run on Server Core. R2 fixes this problem by adding support for a subset of the .NET Framework that supports both ASP.NET and PowerShell.

5. Live Migration—Probably one of the most anticipated features in R2, Live Migration improves VM availability by letting you move Hyper-V VMs between hosts with no downtime. Live Migration is Microsoft’s answer to VMware’s VMotion. Live Migration is built on top of R2’s new Cluster Shared Volumes technology, which lets multiple cluster nodes concurrently access the same LUN.

6. New Hyper-V—A new Hyper-V release is included in Server 2008 R2. A prerelease version of Hyper-V was shipped with the original Windows Server 2008. R2 includes the latest version of Hyper-V. In this version, VMs are able to address up to 32 cores per VM, and the use of TCP Offload and Jumbo Frames provides improved networking performance. One of the biggest improvements in Hyper-V is support for the next item, Live Migration.

7. Remote Desktop Services—Another change in Windows Server 2008 R2 is the rebranding of Terminal Services to Remote Desktop Services. However, the changes aren’t in name alone. The new Remote Desktop Services includes support for the Aero Glass interface, multiple monitors, and DirectX 11, 10 and 9.

8. Core Parking—Windows Server 2008 R2’s new Core Parking functionality enables improved power management. Core Parking lets the OS suspend cores that aren’t in use, thereby saving the power required to run those cores. Parked cores can be reactivated in milliseconds to respond to increased workloads.

9. Support for 256 cores—Improved scalability is another important feature in Server 2008 R2, which will be able to utilize up to 256 cores. This number is a huge jump from the 64-core limit in the original Windows Server 2008.

10. 64-bit only—Windows Server 2008 R2 marks the first time that the Windows Server OS will be 64-bit only, meaning that Server 2008 R2 must run on x64-compatible hardware. Almost all of today’s popular server hardware will accommodate this requirement, but the R2 release won’t run on 32-bit systems.

2) System State Backup includes which components ?

The system state Backup includes the following components on a domain controller:

  • Active Directory (NTDS)
  • The boot files
  • The COM+ class registration database
  • The registry
  • The system volume (SYSVOL)
And on a non-domain controller, the following components are included:
  • The boot file
  • The COM+ class registration database
  • The registry

When a member server or domain controller with a certificate server is installed, the following additional item is also included:

  • Certificate Server

Note: System State information is backed up and restored as a unit.

3)

Posted in Exchange Server 2003 Posts | Leave a Comment »

Exchange 2010 EMC “initialization failed” error execution of scripts is disabled on this system

Posted by viralr on November 15, 2011

Exchange server 2010 and I have just launched the EMC and received the following error.  

Initialization failed

ConsoleInitialize.ps1 cannot be loaded because the execution of scripts is disabled on this system

Cause :-

—————

The reason for this error is the security setting on your pc that does not allow you to execute a script.  This is the so-called Execution Policy. By default, the Execution Policy is set to Restricted. This setting means that you may not run any PS1 script at all.

An overview of the policy levels:

Restricted: Individual cmdlets can run, but not saved Powershell scripts. This is the default setting.
AllSigned: Scripts can run, but must have a digital signature even if written on the local computer. Prompts you before running scripts from trusted publishers.
RemoteSigned: Scripts written on the local computer do not need a digital signature, but any script downloaded from outside (email, IM, Internet) must have a signature to execute. 
Unrestricted: Any script can run, but scripts downloaded from outside will run with a warning.

If you’re working on a desktop and just experimenting with PowerShell, the best is to set the policy-level to Unrestricted. This allows you do everything with annoying security boundaries. Just be careful not to run every script you download from the internet 🙂
If you’re working in a production environment and only want to run self-written scripts, the RemoteSigned level should be loosy enough.

Resolution :-

——————–

To change the Execution Policy to Unrestricted, type the following command in Powershell

Set-ExecutionPolicy Unrestricted

To change the Execution Policy to RemoteSigned (to run your own scripts), type the following command in Powershell

Set-ExecutionPolicy RemoteSigned

And that’s it! Your scripts can be run. Have fun !!!!!!!

Posted in Exchange Server 2010 Posts | 3 Comments »

Exchange 2010 Unable to start EdgeSync service on Hub Transport server

Posted by viralr on November 12, 2011

Exchange 2010 HT/CAS/MB on Windows Server 2008 R2 x64

When i try to start edge sync service on HT server, i get an error 

1) Event Id 1070

“EdgeSync has failed. See the EdgeSync Log for more details.” and 

2) Warning Event Id 1045

Initialization failed with exception: Microsoft.Exchange.EdgeSync.Common.EdgeSyncServiceConfigNotFoundException: Couldn’t find EdgeSync service configuration object for the site PDO-GKL. If the configuration object doesn’t exist in the Active Directory location CN=EdgeSyncService,CN=PDO-GKL,CN=Sites,CN=Configuration,DC=pdosolutions,DC=net, create it using the New-EdgeSyncServiceConfig cmdlet. If the object does exist, check its permissions.. If this warning frequently occurs, contact Microsoft Product Support.

Resolution :

1) Open Exchange power shell

2)  Run command “New-EdgeSyncServiceConfig”

3) After that I was able to start the EdgeSync.

Hope this helps.

Posted in Exchange Server 2010 Posts | 5 Comments »

Exchange 2007 Error updating public folder with free/busy information on virtual machine,The error number is 0x8004010f.

Posted by viralr on November 4, 2011

Problem Description :  Event Id 8207   is frquently occurring on the server :-
—————————————————————————————————-
 
Error updating public folder with free/busy information on virtual machine,The error number is 0x8004010f.
 
 
 
Resolution :-
——————–
1) For Outlook  2003 user make sure you have OAB public folder under system folders,use the following procedure to create OAB public folder
 
 1) Open Powershell
2) Run the command
 
Get-PublicFolder “\non_ipm_subtree\schedule+ free busy” –recurse |fl name,*rep*

3) Found “First Administrative Group” replica is missing ,this replica is needed for old outlook 2003clients

PS] C:\Windows\System32>Get-PublicFolder “\non_ipm_subtree\schedule+ free busy”
 -recurse |fl name,*rep*

Name                           : SCHEDULE+ FREE BUSY
LocalReplicaAgeLimit           :
Replicas                       : {}
ReplicationSchedule            : {}
UseDatabaseReplicationSchedule : True
Name                           : EX:/o=YourORGNAme/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)
LocalReplicaAgeLimit           :
Replicas                       : {Public Folder Database}
ReplicationSchedule            : {}
UseDatabaseReplicationSchedule : True
 
4) To resolve this issue run the following command
 
new-publicfolder -name “EX:/o=YourORGNAME/ou=First Administrative Group” -path “\non_ipm_subtree\schedule+ free busy”
 
Note :  “EX:/o=YourORGNAME (Please change this value to your organization Name ,you will get your organization name from above command)
 

5) Make sure you have now First Administrative Group” replica as per below results ………………

Get-PublicFolder “\non_ipm_subtree\schedule+ free busy” –recurse |fl name,*rep*

[PS] C:\Windows\System32>Get-PublicFolder “\non_ipm_subtree\schedule+ free busy”
 -recurse |fl name,*rep*
Name                           : SCHEDULE+ FREE BUSY
LocalReplicaAgeLimit           :
Replicas                       : {}
ReplicationSchedule            : {}
UseDatabaseReplicationSchedule : True
Name                           : EX:/o=YourORGNAME/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)
LocalReplicaAgeLimit           :
Replicas                       : {Public Folder Database}
ReplicationSchedule            : {}
UseDatabaseReplicationSchedule : True
Name                           : EX:/o=YourORGNAME/ou=First Administrative Group
LocalReplicaAgeLimit           :
Replicas                       : {Public Folder Database}
ReplicationSchedule            : {}
UseDatabaseReplicationSchedule : True
 
If the above steps does not resolve the issue,then check the following points………….
 
 -Outlook 2007  uses Autodiscover and OAB virtual directory to download the OAB.
-From EMC make sure you have OAB Web based distribution enabled
-On Exchange 2007  under Program file>Microsoft>Exchanhe server you have ExchangeOAB folder which is shared (this will be -created if 2007 server is generating OAB)and you will see a folder inside it with guid value.
-In CAS server Restart Microsoft Exchange file distribution service.
-In CAS server open IIS and check for OAB virtual directory and see if there is any folder un it (guid value).Make sure  Autodiscover and OAB URL are set correctly,to set the URL follow KB http://support.microsoft.com/kb/940726
 
–Hope this post helps to resolve 8207 issue.
 
 Refrence :

Posted in Exchange Server 2007 Posts | 2 Comments »