Microsoft Technology

Disable Azure AD Sync and Federated Authentication ( ADFS ) in O365

2022-04-19T16:04:00.004+05:30

Applies To : Microsoft Office 365

ADFS and AD Sync Tool.

Objective / Scenario :

we want to transfer the custom domain "abc.org" from O365 Tennent "A" to Office 365 Tennent "B".

But, "abc.org" is configured with On-Premise Active Directory and ADFS Authorization tool, moreover, we have deleted the ADFS Server prior to disabling it in O365 Tennent, Due to this Users were not able to authenticate with ADFS.

To Authenticate users, the authentication method must change and make the default "onmicrosoft.com" domain to all users to remove the custom domain from Tennent "A".

The below steps demonstrate how to remove ADFS Federated authentication without ADFS accessibility.

Step 1: Open Window PowerShell with "Administrative" rights.

Step 2 : Install MSOnline Module if not installed already " Install-Module MSOnline "

Step 3 : "Connect - MsolService" and Give Username and Password.

Step 4 : "Get-MsolDomain" command to get the Custom domain and Authentication Methods used.

Step 5 : you can see the Custom domain "abc.org" is using "federated" Authentication.

Step 6 : in this step we will disable ADFS "federated" authentication to "managed".

Command : "Set-MsolDomainAuthentication - DomainName abc.com -Authentication Managed"

Step 7 : now check once again with "Get-MsolDomain" custom domain now converted with "Managed"

Step 8: Still you will not able to do modification in users' primary e-mail due to AD Sync, needs to disable AD Sync with O365.

Step 9 : "Set-MsolDirSyncEnabled -EnableDirSync $false" and Confirm "Y"

Step 10 : Wait for 15 to 30 min to reflect changes.

Step 11 : Now you can change All users' Primary E-mail IDs from Custom Domain to Default Onmicrosoft.com domain.

Step 12 : After successfully changing of primary E-mail id then remove Custom Domain and add it to the new Tennent.

Failed to open mailbox abc@abc.onmicrosoft.com" "failed to access mailbox" " Mailbox does not exist"

2022-04-14T23:34:00.000+05:30

Applies to : Veeam Backup for O365, Exchange Server 2013, 2016, 2019

Problem: Cross Tennent Veeam backup restore error " Failed to open mailbox abc@abc.onmicrosoft.com" "failed to access mailbox" " Mailbox does not exist"

Scenario: I have Two Office 365 Tennent "A" and "B", I want to migrate all mailbox data from Tennent "A" to Tennent "B" ( Cross Tennent Migration ).

I Used the Veeam O365 backup tool to backup of all mailbox,Sharepoint, One Drive data from Tennent "A" and Create Restore Task to Tennent "B".

Diagnose :

1) Download Backup Logs from Veeam Console. https://helpcenter.veeam.com/docs/vbo365/guide/vbo_exporting_logs.html?ver=60

2) Found below error in log file.

Resolution :

1. Login to the Office 365 Exchange Admin Portal.

2. Go to Permissions, then under Admin Roles click the '+' symbol to add a new role and enter the Name and Description 'CloudMigratorImpersonation'.

3. Click the '+' symbol under 'Roles:', select ApplicationImpersonation, click 'add →' then 'OK'

4. Click the '+' symbol under 'Members:' and select your Admin User, click 'add →' then 'OK'

5. Click 'Save' in the 'Role Group' window and you will then see the Impersonation role listed in Admin Roles.

You can now use application impersonation with your admin user in CloudMigrator.

Reference :

https://answers.microsoft.com/en-us/msoffice/forum/all/exchange-impersonation-error-unable-to-open-user/834c4ea9-6cb5-4df4-9011-433ba501f6d2

https://www.techieshelp.com/exchange-2013-configuring-impersonation-applications/

Microsoft Exchange Active Sync "HTTP error 500.24 - Internal Server Error" and "An HTTP 500 response was returned from IIS7"

2022-04-14T14:40:00.005+05:30

Applies to : Microsoft Exchange Server 2016

Problem: Mails on Mobile Devices are not synching, from internal/external networks.

further, diagnose open https://testconnectivity.microsoft.com and got below error " An HTTP 500 response was returned from IIS7"

I tried to access Microsoft Active Sync Virtual directory from web browser "https://example.contoso.com/Microsoft-Server-ActiveSync" and got the below error " HTTP Error 500.24 - Internal Server Error"

RESOLUTION :

1) Open IIS Management console

2) Select, Default Website, and Navigate to the Active Sync virtual directory.

3) Open Advance Settings and Copy Path of the Virtual Directory.

4) Go to the Virtual Directory path and Find "Web.config" file. ( Example Path : %Exchange Server Installation Directory%\ClientAccess\Sync\web.config" )

5) Open "web.config" file in Text Editor and Find "impersonate". ( Make Copy of the original file prior to editing )

6) Setup value, impersonate=True to False.

7) Save File and Restart IIS Server.

References :

https://social.technet.microsoft.com/Forums/en-US/e60ebbf2-f8d2-403f-8d20-aada110bfd72/activesync-problem-http-500-response?forum=exchangesvr3rdpartyappslegacy

https://helpcenter.gsx.com/hc/en-us/articles/115006225328-Exchange-2010-CAS-Check-ActiveSync-500-Internal-Server-Error

https://www.azure365pro.com/exchange-activesync-returned-an-http-500-response-internal-server-error/

how to activate Office365

2015-01-29T11:27:00.000+05:30

Hi,

Please find Office 365 Activation Process and customer support detail for india.

Please find process to activate Office 365 through the tab Online Service Activation.

Once you have acquire the OSA key, you may proceed to click below link for your Office 365 activation:

https://portal.office.com/Commerce/ProductKeyStart.aspx

Microsoft Volume Licensing Services Support Center

Email: vlservp@microsoft.com

India: 000800 440 1555 (Toll-Free Number) / 1 (212) 444 0497 (Toll Number)

For more information on Volume Licensing/Software Assurance:

http://www.microsoft.com/licensing/sa/default.mspx

Kindly be informed that Office 365 is a license that gives a user the right to access for Cloud services. Hence you are unable to get any setup or media to download from the VLSC web page.

You may contact our CPC team at 1800 200 2052 for Office 365 configuration and further assistance.

Thank you for your continued support towards Microsoft products and services.

Regards,,

Gaurang Patel

Office 365 Lync Online SRV settings in Plesk DNS Control Panel

2015-01-29T11:22:00.000+05:30

Problem:

Office 365 Lync Online SRV Records are not getting verified by Office 365 DNS.

Symptoms :

Rest of all Records are getting verified without any issue like "CNAME", "MX" , "A" Records, but when you set SRV Records for Lync Online in Plesk DNS control penal it is not allow you to set WEIGHT to "0" and priority to "100"

Resolution :

After so many diagnose I found that removing the _ from the sip and tls setting and setting the priority and weight to 0 allow it to verify.

UNIX or Linux OS servers that host DNS don’t require the underscore (_) when you add SRV records to the DNS host. If your DNS host is running UNIX or Linux and the SRV records aren’t resolving correctly, remove the underscore from the host name of the SRV record.

After setting above value please wait for at least 10 minutes to reflect DNS records changes, it may also depend on your internet speed and DNS Propagation Speed.

now open Office 365 Admin page and change DNS settings, Select Verify domain button to verify DNS changes and hurrayyyyy!!!!! Congratulations you have successfully configured Office 365 DNS records. Now your Lync will be up and running.

hope this may help.

Regards,,

Gaurang Patel

2015-01-13T17:19:00.002+05:30

Now a Day’s NAS Storage is very Popular in SMB and MSMB Market for various Use case like File Sharing , Disaster Recovery , Virtualization and most importantly Backup to Disk.

Netgear Ready NAS Provides in-build Backup software where you can create Backup jobs directly and initiate backup on NAS, however it is also provide RSYNC Protocol and Netgear Replication over the wan which can take backup of your NAS to another NAS in any corner of the world, you just need is an Internet Connection and most important without any Internet LIVE IP.

However Replication has some Pros and Cons, it is maintaining Backup revision on All Backup Data which is more convenient at the time of actual restoration of data and sometime Backup job fails because of PPP session initiation failed from remote end.

By the Help of RSYNC replication technology you can replicate Primary NAS Data to DR NAS with Actual Data Format with More accuracy but you need Live IP address on Primary location is preferred, it would be great if you have Live IP on both end.

Here I am going to make an exact replica of primary NAS (DATA only) to DR Location NAS, so I am going to use Live IP address on Primary location and use dynamic IP address on DR end.

To implement this scenario on your network please follow below steps.

HO Side :

· Create Users and Groups Locally or Synchronise with Active Directory.

· Design Folder Structure as per your need and give appropriate Permission.

· Enable RSYNC on all Folders which you want to Replicate / Synchronize.

· Add host and User for Additional RSYNC Security.

· Take System Configuration backup of “Share Access” , “ Users and Groups” , “Services” and store to appropriate location. ( do not store on NAS )

DR Side :

· Manually Create identical Folders same as HO Side ( double check the spelling and white space, advisable to copy Name )

· Create RSYNC Backup jobs for all respective folders which you want to replicate.

· Schedule backup frequency as per your environment.

Restoration Process :

· Restore NAS 1 Configuration backup on DR NAS which will restore File and Folder backup permission as well as users and groups.

· Move DR NAS to HO side and Rotate IP Address.

That’s IT…… within minimum hours your environment will be up and running.

Network Connectivity Diagram.

1 1) Open Admin Console -> Go to Accounts Tab. Create Local Users and Groups.

2) In case of Active Directory Domain Scenario Go to Accounts - > Authentication. Account Type = Active Directory. NetBIOS Domain Name = example. FQDN = example.com. Container OU= left blank for all OU or specify user Define OU. Include Trusted Domain = Yes / No ( for AD Trusted domain Authentication ) Administrator Name = Administrator Users name. Administrator password = < user password > Directory Server Address = IP address or host name. Do not Cache ADS accounts locally = yes / no ( once you enable this option it will go to active directory server each and every time )

Exchange 2013 Outlook and OWA Search Does Not Work

2014-11-20T18:26:00.000+05:30

Exchange 2013 Outlook and OWA Search Does Not Work

As with all previous versions of OWA, Exchange 2013 has a search function that is above the mail column as seen below.

I came across an issue recently where if you did a search in OWA 2013, no results would be show, no matter what information I used as the search keywords. No matter what no search results where found. In Exchange 2013 , the search index is stored with the Mailbox store where the users are located. To resolve this issue and build the OWA 2013 and the Exchange search index again we needed to do the following. This error may also occur withOutlook clients that are not in cached mode.

1) Stop Service

navigate to services stop the Microsoft Exchange Search & Microsoft Exchange Search Host Controller service.

2) Locate User Mailbox Database.

Once done locate the folder on your server where the Mailbox database is where the user is trying to search from. For example mine is here.

C:\Program Files >Microsoft > Exchange Server > V15 > Mailbox > Mailbox Database 1403936621

If you are unsure where the the mailbox database is use the command below from power-shell.

Get-MailboxDatabase "yourmailboxdatabase" |fl name,*path*

Once the path is located you will find a folder name with a long “GUID” and the word Single on the end.

3) Rename this folder .old.

We then need to start the Microsoft Exchange Search service again, The server will now begin to rebuild its search index.

Give it plenty of time to rebuild then issue the command below and make sure the status of Content Index Status is seen as healthy.

Get-MailboxDatabaseCopyStatus

As seen below, if it says healthy try your search and you should see that your search results now appear in Outlook and OWA 2013.

Setting up Vtiger CRM PBX Manager with Asterisk

2014-11-12T16:57:00.000+05:30

Setting up PBX Manager with Asterisk

For official configuration Guide please login to here.

After going through Official configuration guide then I realise that there should be one step by step guide with snapshots for newcomers or who are not familiar with Asterisk PBX and Linux.

I tried to make this step by step very simple and more understandable for all, so please give me any suggestion from your side to make this documentation better.

I have separated configuration parts in different steps.

1) Scenario with Network Diagram.

2) Required Software’s.

3) Vtiger Side Configuration.
4) Asterisk Side Configuration.
5) Troubleshooting.

Network Diagram

Vtiger Server:

Windows 7 32 bit , Dual Core CPU , 4 GB RAM , 40 GB HDD.

Vtiger 6.1

Zoiper SIP Soft Client with 2009 Extension Configured.

Asterisk Server:

Dual Core CPU , 4 GB RAM , 40 GB HDD

AsteriskNOW 5.211.65 (User Any Asterisk Based PBX like FreePBX , Elastix etc..)

Java Jetty Installed.

Note : this scenario has been developed in Virtual Environment ( Vmware Workstation 10 ) in my case.

Configure your Asterisk credentials in Vtiger

After installing Vtiger Asterisk Connector, please follow few simple steps to configure your Asterisk Server information in Vtiger CRM :

1. Login to your CRM instance and click on icon on the top right corner of the CRM.

2. Click CRM Settings.

3. Click PBX Manager under Integration in Settings sidebar.

4. Edit Asterisk Server Details.

Vtiger Asterisk App URL - configure server name where Vtiger Asterisk Connector is installed as shown:

Syntax : Protocol://Asterisk_Server_IP:Port

Protocol	http/https
Asterisk_Server_IP	Your Asterisk Server IP
Port	Server Port configured in Vtiger Asterisk Connector config file.

Outbound Context - Vtiger specific context configured in your Asterisk Server

Outbound Trunk - Trunk configured in your Asterisk server for Outgoing Calls.

Vtiger Secret Key - Unique key generated for authentication, which has to be configured in Vtiger Asterisk Connector.

5. Click Save button.

Note : in my case I am not using any trunk for Outgoing Calls, I just want to test internal Calls only in my LAB. So please Add your Outbound trunk Name which is configured in Asterisk GUI -> Connectivity -> Trunks. ( Name is Case Sensitive so be careful ).

Configure the extension number for each user

For each user who is allowed to handle incoming and outgoing calls from the CRM, the extension number should be configured in the User preferences page.

1. Open My Preferences.

2. Configure user number in CRM Phone Extension field under “More Information” block.

Number format:

Extension: [Extension_number]

e.g., 2001

Once configuration is completed on both sides i.e., Vtiger and Asterisk, you are now ready to make and receive calls in the CRM.

Vtiger Asterisk Connector Installation on Asterisk Server

Introduction

Vtiger Asterisk application acts a gateway to connect to Vtiger CRM from the Asterisk Server. It makes it easy for Vtiger and Asterisk interaction over HTTP when incoming or outgoing calls need to be handled.

Features

Vtiger Asterisk Connector provides following features:

1. Connect to Vtiger and notify the incoming call.

2. Accept commands from Vtiger and forward it to Asterisk (Click-to-Call).

3. Call recording file management.

Installation.

1. Download Asterisk Connector ( PBXMagager )Add-on from Official Website.

2. Download WinSCP and connect to Asterisk server .

3. Transfer VtigerAsteriskConnector-1.2.zip to root folder ( / ).

4. Login to Asterisk Server by using putty.exe or ssh terminal and unzip VtigerAsteriskConnector with “unzip VtigerAsteriskConnector-x.y.zip” Command.

5. Open /VtigerAsteriskConnector/conf/ VtigerAsteriskConnector.properties and update information as below.

6. Copy and Paste the Vtiger Secret Key that is generated in your Vtiger Instance.

You can find this under Vtiger CRM > Settings > Integration > PBXManager > Asterisk Server Details.

7. Copy Vtiger URL exact the same because it is case sensitive so better to copy and paste from web browser.

8. Cd /VtigerAsteriskConnector/Bin

9. ./Start.sh

10. Test Vtiger Connector website is working or not http://192.168.1.87:8383 the result should be as below.

11. If you find above result then you are ready with VtigerAsteriskConnector Configuration.

Asterisk Configuration File Changes

1) Change In extensions.conf ( /etc/Asterisk/extensions_custom.conf )

Create Vtiger SIP Extension

1) Open Asterisk GUI -> Applications -> Extensions.

2) Create SIP Extensions.

Configure Asterisk Manager User

1) Open Asterisk GUI -> Settings -> Asterisk Manager Users

2) Create “vtiger” User with ALL Permission.

3) Make 0.0.0.0 / 0.0.0.0 in Deny Entry.

4) Permit 127.0.0.1/255.255.255.0&192.168.1.0/255.255.255.0&192.168.1.94/255.255.255.255

5) Click on Submit.

6) Save Changes.

Check /etc/Asterisk/manager_additional.conf

Add VtigerAsteriskConnector Script in to startup.

1) Open Asterisk server terminal and give below command.

2) Echo sh /VtigerAsteriskConnector/bin/start.sh >> /etc/rc.local

Troubleshooting

1) Monitor Logs in /VtigerAsteriskConnector/Logs

a. nohup.webapp.<date>.out

b. nohup.agi.<date>.out

2) Start or restart VtigerAsteriskConnector Scripts /VtigerAsteriskConnector/bin/

a. Start.sh

b. Stop.sh

c. Agi.sh

d. Webapp.sh

3) Check webapp is running or not by visiting http://192.168.1.87:8383 it should show above Scripts in browser.

Restore missing Standard TCP/IP Port type for Printer

2014-04-22T15:36:00.000+05:30

Restore missing Standard TCP/IP Port type for Printer

If the TCP/IP port option is missing you need to re-add it.
First, make sure that the following files are in C:\Windows\System32\:

tcpmib.dll
tcpmon.dll
tcpmon.ini
tcpmonui.dll

If they are missing, you will need to copy them there from either the i386 directory (if you have one) or from the original install CD.
Then, copy the following lines to NOTEPAD and save the file to your desktop as “printer.reg”

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitors\Standard TCP/IP Port]
“Driver”=”tcpmon.dll”
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitors\Standard TCP/IP Port\Ports]
“LprAckTimeout”=dword:000000b4
“StatusUpdateInterval”=dword:0000000a
“StatusUpdateEnabled”=dword:00000001

Once it’s saved to your desktop, double-click printer.reg and say “OK” to the warning that you will be adding the keys to your registry.

Reboot the Server and the TCP/IP port option should be back.

About these ads

Exchange 2010 SP1, SP2 or Sp3 Error: Setup cannot continue with the upgrade because the “beremote()” process has open files.

2013-11-12T16:08:00.000+05:30

Exchange 2010 SP1, SP2 or Sp3 Error: Setup cannot continue with the upgrade because the “beremote()” process has open files.

Error:

Setup cannot continue with the upgrade because the “beremote()” process has open files:
The error listed above is not something to really stress about.

Resolution:

If you running Symantec Backup Exec you will need to stop the services and then retry the checks, they should all pass and allow you to carry on with your installation.

Regards,,
Gaurang Patel

Step by Step Adobe Reader Enterprise Depolyment

2013-09-17T13:22:00.000+05:30

Adobe Reader Enterprise Depolyment

The steps below are the ones I followed to distribute and configure Adobe Reader X in an enterprise environment

Setup a distribution agreement for Adobe products http://www.adobe.com/mena_en/products/reader/distribution.html

Download the latest Adobe Reader base release e.g. 10.1.0 as an msi file

Download the latest Adobe Reader quarterly update e.g. AdbeRdrUpd1013.msp

Download the Adobe Customization Wizard X http://www.adobe.com/support/downloads/detail.jsp?ftpID=4950

Place the Adobe Reader msi file and the msp patch file in a folder. Create an empty file called Setup.ini in the folder containing the msi and msp.

Run the Adobe Customization Wizard and load the Adobe Reader msi file. Choose your installation options, e.g. removing the EULA prompt, disabling updates etc. and save the mst into the folder holding the installation files.

Run the command below to silently install Adobe Reader, update it using the msp file and apply the customizations in the mst file.

msiexec.exe /i “\\%SERVER%\SoftwareDistribution\Packages\AdobeReader_X\AdbeRdr1010_en_US.msi” PATCH=”\\%SERVER%\SoftwareDistribution\Packages\AdobeReader_X\AdbeRdrUpd1013.msp” TRANSFORMS=”\\%SERVER%\SoftwareDistribution\Packages\AdobeReader_X\Custom_Install.mst” /qn

exchange spam filter exchange spam filter exchange spam filter exchange spam filter exchange spam filter

SharePoint People Picker, Audiences And Active Directory Trusts

2013-09-17T13:19:00.001+05:30

SharePoint People Picker, Audiences And Active Directory Trusts

The following post covers issues I came across when configuring SharePoint 2010 to work with an Active Directory (AD) trust. In this scenario, SharePoint and user accounts are in domain A and a two-way transitive trust has been created with domain B. Domain B holds news users who need access to SharePoint.
The first issue was the error below, which occurred when setting permissions for AD users and groups from domain B using the People Picker.

“No exact match was found. Click the item(s) that did not resolve for more options“

As a two-way trust exists between the two domains and the web application is using Windows authentication, SharePoint should have been able to locate users and groups in the trusted domain. However, this wasn’t the case and I had to run the commands on this page http://technet.microsoft.com/en-us/library/cc263460.aspx. The STSADM –o setapppassword –password <password> command has to be run on every SharePoint server running the Windows SharePoint Services Web Application service. The stsadm.exe –o setproperty –pn peoplepicker-searchadforests –pv <list of forests or domains> -url <webapp> command is run on one SharePoint server running the Windows SharePoint Services Web Application.
The next issue occurred when using the Audience Picker to set an audience on a web part for a group from domain B. Unlike the People Picker which queries AD, the Audience Picker queries the user profile database for imported users. In this case I was able to search for the security group from the trusted domain, the group was listed as containing members, but the audience setting failed to work. This error was caused by a mismatch between the NETBIOS name of domain B and the FQDN, e.g. the NETBIOS name was DOMAINB-XY and the FQDN was DOMAINB.COM. In order to fix the problem I followed the steps listed here http://blogs.msdn.com/b/russmax/archive/2010/03/20/sharepoint-2010-provisioning-user-profile-synchronization.aspx. The basic steps are:

Ensure Grant Replicate Directory Changes has been correctly assigned on domain B http://technet.microsoft.com/en-us/library/hh296982.aspx
Set the NetBiosDomainNamesEnabled property to true for the User Profile Service Application
Delete and recreate the AD connection within SharePoint for the import of users from domain B
Import users from domain B.

exchange spam filter exchange spam filter exchange spam filter exchange spam filter exchange spam filter exchange spam filter exchange spam filter

In Place Upgrade Of Windows Server 2008 R2 Standard To Enterprise Or Datacenter Edition

2013-09-17T13:16:00.000+05:30

In Place Upgrade Of Windows Server 2008 R2 Standard To Enterprise Or Datacenter Edition

If you want to upgrade a server running Windows Server 2008 R2 Standard to either the Enterprise, or Datacenter editions, it’s possible to do so online, without re-installing Windows.

Suggested Method will not disturb your existing Windows installation or applications installed on previous version.

Here i will show you the step by step upgradation of windows standard to datacenter edition, if you want to upgrade to Enterpise edition than just use "ServerEnterprise" insted of "ServerDataCenter" with Enterprise Product key as mentioned below product key table.

So are you ready to upgrade??? let's Start...

Open command prompt with run as Administrator rights and type DISM /Online /Get-CurrentEdition. This will return the current Windows version.

Type DISM /Online /Get-TargetEditions to list the Windows editions to which this server can be upgraded.

If you type DISM /Online /Set-Edition:ServerDataCenter you’ll get the message in the screenshot below. This is because even if you’re using a KMS server for internal activation, you have to provide a product key. Fortunately, Microsoft have a page that lists the KMS client setup keys http://technet.microsoft.com/en-us/library/ff793421.aspx. On this page you can find keys for Windows Server 2008 R2 Enterprise and Datacenter.

Typing DISM /Online /Set-Edition:ServerDataCenter /ProductKey:xxxxxx will upgrade the operating system. All that’s required to complete the upgrade is a reboot.

Please find below Upgradation keys for diffrent possible versions, i recommend you to use Any time Upgrade for Client OS.




Platform	Operating system edition	Product key
Windows 7 and Windows Server 2008 R2
Client			Windows 7 Professional	FJ82H-XT6CR-J8D7P-XQJJ2-GPDD4
Client			Windows 7 Professional N	MRPKT-YTG23-K7D7T-X2JMM-QY7MG
Client			Windows 7 Professional E	W82YF-2Q76Y-63HXB-FGJG9-GF7QX
Client			Windows 7 Enterprise	33PXH-7Y6KF-2VJC9-XBBR8-HVTHH
Client			Windows 7 Enterprise N	YDRBP-3D83W-TY26F-D46B2-XCKRJ
Client			Windows 7 Enterprise E	C29WB-22CC8-VJ326-GHFJW-H9DH4
Server			Windows Server 2008 R2 Web	6TPJF-RBVHG-WBW2R-86QPH-6RTM4
Server			Windows Server 2008 R2 HPC edition	TT8MH-CG224-D3D7Q-498W2-9QCTX
Server			Windows Server 2008 R2 Standard	YC6KT-GKW9T-YTKYR-T4X34-R7VHC
Server			Windows Server 2008 R2 Enterprise	489J6-VHDMP-X63PK-3K798-CPX3Y
Server			Windows Server 2008 R2 Datacenter	74YFP-3QFB3-KQT8W-PMXWJ-7M648
Server			Windows Server 2008 R2 for Itanium-based Systems	GT63C-RJFQ3-4GMB6-BRFB9-CB83V
Windows Vista and Windows Server 2008
Client			Windows Vista Business	YFKBB-PQJJV-G996G-VWGXY-2V3X8
Client			Windows Vista Business N	HMBQG-8H2RH-C77VX-27R82-VMQBT
Client			Windows Vista Enterprise	VKK3X-68KWM-X2YGT-QR4M6-4BWMV
Client			Windows Vista Enterprise N	VTC42-BM838-43QHV-84HX6-XJXKV
Server			Windows Web Server 2008	WYR28-R7TFJ-3X2YQ-YCY4H-M249D
Server			Windows Server 2008 Standard	TM24T-X9RMF-VWXK6-X8JC9-BFGM2
Server			Windows Server 2008 Standard without Hyper-V	W7VD6-7JFBR-RX26B-YKQ3Y-6FFFJ
Server			Windows Server 2008 Enterprise	YQGMW-MPWTJ-34KDK-48M3W-X4Q6V
Server			Windows Server 2008 Enterprise without Hyper-V	39BXF-X8Q23-P2WWT-38T2F-G3FPG
Server			Windows Server 2008 HPC	RCTX3-KWVHP-BR6TB-RB6DM-6X7HP
Server			Windows Server 2008 Datacenter	7M67G-PC374-GR742-YH8V4-TCBY3
Server			Windows Server 2008 Datacenter without Hyper-V	22XQ2-VRXRG-P8D42-K34TD-G3QQC
Server			Windows Server 2008 for Itanium-Based Systems	4DWFP-JF3DJ-B7DTH-78FJB-PDRHK

error: Your request can't be completed right now. Please try again in a few moments.

2013-08-21T13:47:00.000+05:30

error: 2013 Your request can't be completed right now. Please try again in a few moments.

I have setup Microsoft Exchange 2013 on windows 2012 Standard server operating system with Clean installation without any error.

After installation I did many configuration and Testing than decided to Fully update the Exchange server as well as windows 2012 server.

I found two update of Microsoft Exchange 2013 standard server on Microsoft TechNet

Cumulative Update 1 and 2

if you download Cumulative update 2 than no need to download CU1 because CU2 includes the CU1.

Cumulative Update file has very large size 1.3 GB which can be downloaded from below URL.

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

http://blogs.technet.com/b/exchange/archive/2013/07/09/released-exchange-server-2013-rtm-cumulative-update-2.aspx

After Applying exchange Cumulative Update I landed with new error and not able to open Exchange Control Panel configurations.

Error:

error: Your request can't be completed right now. Please try again in a few moments.

I was wondering why this problem occurred after updating the exchange server earlier it was working fine without any error, in a resolution I search a lot on a website but couldn't find proper solution than I recall the configuration did earlier before updating the server and found one clue and resolved my problem.

Cause :

Invalid site binding entry in Exchange Back End website

Resolution :

1) open Administration Tools

2) open IIS

3) Nevigate to exchange back end website

4) Click on Site Binding

5) Remove user defined Site binding.

6) Restart IIS / Restart server

7) you are Done!!!!

This solution works in my case !!!!

Regards,,

Gaurang Patel

Windows Server Backup failed to backup with error 0x81000101

2013-07-25T15:30:00.000+05:30

Windows Server Backup failed to backup with error 0x81000101

Symptom:

Sometimes Windows Server Backup failed to backup the data. The error is:

The shared restore point operation failed with error (0x81000101) The creation of a shadow copy has timed out. Try this operation again.

In the event viewer, found the following error:

The backup operation that started at '‎**** has failed because the Volume Shadow Copy Service operation to create a shadow copy of the volumes being backed up failed with following error code '2155348001'. Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.

Cause:

Windows Server Backup is timing out during shadow copy creation since it is taking more than 10 minutes.

Resolution:

- Run regedit.exe and navigate to "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\SPP"

- Create a new Registry value of type DWORD with name "CreateTimeout"

- Change value to 12000000(21060*1000 = 20 mins) in decimal

More information:

http://blogs.technet.com/b/filecab/archive/2009/09/16/diagnosing-failures-in-windows-server-backup-part-1-vss-spp-errors.aspx

System State Backup Failed on Windows 2008 R2 SP1 with Windows Backup

2013-07-16T16:17:00.002+05:30

Dear All,
I am running Windows Server 2008 R2 SP1 Domain Controller and have a scheduled job to backup only the System State data to a volume (D drive) on the server itself.

Periodically and randomly the job fails with a status message in the Windows backup console saying "Failed. The operation was stopped. Detailed error: Access is denied"

In the event log I see the following

I checked online for the above error code and found MS Hotfix 2182466 but when I try to install it, it says "The update is not applicable to your computer" (I have verified the hotfix is the correct one for the server I am running).

Resolution :

After searching a lot on internet and suddenly I found solution.

TrendMicro Antivirus Software is installed on server so that I have disabled it and bOOOOOMMMMM!!!!!!!! windows system state backup has completed without any error...

Exchange Server 2007 / 2010 Transport: 452 4.3.1 Insufficient system resources

2013-06-15T16:33:00.000+05:30

Exchange Server 2007 / 2010 Transport: 452 4.3.1 Insufficient system resources

In my hotel room in Orlando, getting ready for an Exchange 2007 transport presentation tomorrow morning at TechMentor. When trying to telnet to the SMTP port of an Exchange 2007 Hub Transport server, I got the following error:

452 4.3.1 Insufficient system resources

Not a good thing the night before a presentation – Murphy’s law at work again!
The Application Event Log has Event ID 15002 from MSExchangeTransport saying “The resource pressure is constant at High. Statistics… “. The event goes on to tell you that inbound mail submission has stopped, and it’s due to disk space being low on the volume where the queue database is located.

Figure 1: Event ID 15002 logged by MSExchangeTransport
Exchange Server 2007 transport queues are not the familiar .eml files you see in Exchange Server 2003/2000, which reside in the \mailroot\vsi <1>\queue folder (<1> is the instance number of the SMTP virtual server) on the file system. Yes, transport queues have been moved to a JET database of its own.

What’s Back Pressure?

In Exchange Server 2007, the Transport service monitors system resources such as disk space and memory on Transport servers (the Hub Transport and the Edge Transport servers), and stops message submission if it’s running low on these resources. It continues to deliver existing messages in the queue. When resource utilization returns to normal, it resumes message submission. The feature is called Back Pressure.
In this case, Exchange required 4 Gigs of free disk space on the volume where the Queue database was located – I had about 3.95 Gigs. :)

Changes to Back Pressure settings in Exchange Server 2007 SP1

The Back Pressure settings in Exchange Server 2007 RTM stop inbound mailflow if free disk space is below 4 Gigs. This static threshold has been lowered in SP1 to a more realistic 500 MB.

The Resolution

Many configuration options for transport servers are saved in an XML file named EdgeTransport.exe.config (it’s the same file name on both server roles— Edge Transport and Hub Transport) located in \Exchange Server\Bin\.
To get transport to resume submissions, you can use any of the following methods. All of the following require you to edit the EdgeTransport.exe.config file.

Disable BackPressure: Although Microsoft doesn’t recommend it, it does provide a way to Disable Back Pressure
Tweak BackPressure thresholds: Modify BackPressure parameters to more accurately define what’s high utilization for your deployment or server configurations, as explained in the above docs.
Move the queue database to another volume: Another resolution, and the one I used in this case, was to move the queue database to another volume with ample of free space, using the following procedure:
1. Add the following key in the <AppSettings> section in EdgeTransport.exe.config, as documented in “How to Change the Location of the Queue Database“:
  
  <add key=“QueueDatabasePath” value=”D:\Queue\QueueDB” />
2. Save the file and restart the Microsoft Exchange Transport service from the Services console or by using the Restart-Service cmdlet (Restart-Service MSExchangeTransport).

Message submission resumes.

how to increase Virtual Processor ( vCPU) in Hyper-v Guest OS

2013-03-25T16:45:00.000+05:30

Hi,

here I will show you how to increase Virtual CPU for particular Hyper-V guest OS, basically hyper-v (windows Server 2008 R2 Sp1 )Supports only 4 Virtual CPUs which is a limitation of Hyper-V, the limitation of Hyper-v is described on below TechNet article.

http://technet.microsoft.com/en-us/library/ee405267(WS.10).aspx

So if you want to increase Virtual CPU of the GUST please follow below Steps.

1) Shutdown all Virtual Servers.

2) Stop All Hyper-V Services ( services.msc)

3) Open Hyper-V data Store where GUEST server .VHD is stored.

4) Open Virtual Machine Folder and edit .xml file.

5) Edit below parameter in .xml File.

<processors>
<count type=”integer”>8</count><features>
< limit type=”bool”>False</limit>
< /features>
< limit type=”integer”>100000</limit>
< limit_cpuid type=”bool”>False</limit_cpuid>
< reservation type=”integer”>0</reservation>
< weight type=”integer”>100</weight>
< /processors>

6) Save and Close the file.
7) Start Hyper-V Services.
8) Start Guest server.
9) Check the Processor ( you need to restart )
10) Done!!!!

Note : 1) Physical host should have enough core to support more cores for Ex: Physical server has only 4 Core and you want to assign 6 core then it won't work.

2) this is a work around solution so please take care before making change in production environment.

3) for more information please follow http://social.technet.microsoft.com/Forums/en-US/virtualmachingmgrhyperv/thread/cf17b31f-3ef9-49c8-93a0-a6d6b83b2bbe

regards,,
Gaurang

step by step installation of Microsoft Exchange 2013

2013-01-29T18:37:00.000+05:30

Hello Friends,

i will show you how to setup Microsoft Exchange 2013 server, First of all i would like to show you the Compatibility matrix of MS Exchange 2013 as mentioned below.

Note: Once you install / Prepare AD for MS Exchange 2013 you won't be able to install MS Exchange 2010 or later version.

Operating System Requirement:

Operating system

Windows Server 2012
Windows Server 2008 R2 Standard with SP1
Windows Server 2008 R2 Enterprise with SP1
Windows Server 2008 R2 Datacenter RTM or later

Operating system for Management Tools (on a computer with 64bit processor)

Windows Server 2012
Windows Server 2008 R2 Standard with SP1
Windows Server 2008 R2 Enterprise with SP1
Windows Server 2008 R2 Datacenter RTM or later
64-bit edition of Windows 8 Release Preview
64-bit edition of Windows 7 with SP1

Active Directory Server Requirement:

Schema Master

In each Active Directory site where you plan to install Exchange 2013 Preview, you must have at least one writable domain controller running any of the following:

Windows Server 2012
Windows Server 2008 R2 Standard or Enterprise SP1 or later
Windows Server 2008 R2 Datacenter RTM or later
Windows Server 2008 Standard or Enterprise SP1 or later (32-bit or 64-bit)
Windows Server 2008 Datacenter RTM or later

Schema Master

Windows Server 2012
Windows Server 2008 R2 Standard or Enterprise
Windows Server 2008 Standard or Enterprise (32-bit or 64-bit)
Windows Server 2003 Standard Edition with Service Pack 2 (SP2) or later (32-bit or 64-bit)
Windows Server 2003 Enterprise Edition with SP2 or later (32-bit or 64-bit)

Global Catalog Server

At least one Global Catalog server in every Active Directory site where you are planning to install Exchange Server 2013 Preview on,

Windows Server 2012
Windows Server 2008 R2 Standard or Enterprise
Windows Server 2008 R2 Datacenter RTM or later
Windows Server 2008 Standard or Enterprise (32-bit or 64-bit)
Windows Server 2008 Datacenter RTM or later

Active Directory Forest

Active Directory must be at Windows Server 2003 forest functionality mode or higher.

Prerequisites for Windows 2008 R2 SP1:

Required Windows roles and features

Open Powershell (Open Powershell window with elevated rights by right-clicking it "Run as Administrator") and import server module first with "Import-Module ServerManager" command then install/enable Operating System components as per below;

Client Access and Mailbox role
Import-Module ServerManager
Add-WindowsFeature Desktop-Experience, NET-Framework, NET-HTTP-Activation, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Web-Server, WAS-Process-Model, Web-Asp-Net, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI

Required Software

Uninstall Microsoft Visual C++ 11 Beta Redistributable (x64)
(Control Panel -> Programs and Features -> Uninstall)

Register ASP.NET with .NET Framework 4.5 in Internet Information Services (IIS)
Open CMD
Run this command:
%SystemDrive%\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -ir -enable

Restart the IIS services:
IISReset

Windows Server 2012 prerequisites

Open Powershell (Open Powershell window with elevated rights by right-clicking it "Run as Administrator") and import server module first with "Import-Module ServerManager" command then install/enable Operating System components as per below;

Client Access and Mailbox role
Import-Module ServerManager
Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation

Required Software

Uninstall Microsoft Visual C++ 11 Beta Redistributable (x64)
(Control Panel -> Programs and Features -> Uninstall)

Prepare Schema and AD

Prepare the Active Directory Schema to install Exchange Server 2013 (basically this will extend the schema). You will have to insert the Exchange Server 2013 RTM DVD (Media Kit)

– Assumption, DVD ROM drive letter is D:\ and Exchange Server Installation Setup path is D:\Setup.exe –

Open PowerShell or CMD in admin mode

D:\Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms

D:\Setup.exe /PS /IAcceptExchangeServerLicenseTerms

Now that the Schema is being prepared, we will have to move on to the next step and prepare the Active Directory Topolgy.

Before you run this command you should have your Exchange Server 2013 Organization name

D:\Setup.exe /PrepareAD /OrganizationName:<name> /IAcceptExchangeServerLicenseTerms

D:\Setup.exe /PAD /OrganizationName:<name> /IAcceptExchangeServerLicenseTerms

Now that the Schema and the AD are prepared,

Run the Exchange Server Setup from the DVD (Run as Administrator)

It will request to check for updates, select Connect to the internet and check for updates and click next

necessary updates will be downloaded , in my case there was no updates

Files are being copied to install Exchange Server 2013

Initializing the Exchange Server 2013 Setup

Gives and Introduction to the Exchange Server 2013, upon reading click next

Accept the License Agreement (you are supposed to read this) and click next

I will have left the default setting of selecting the “Use Recommended Settings” option and click next

The Server roles that are to be installed select and click next. Notice that Exchange Server 2013 does not contain all the server roles that were introduced in Exchange 2007 and 2010. It has been reduced to 2 now (to read more click here)

The path of the installation and the required space for the installation. click next upon making the changes

Malware Protection Settings – I am leaving it on – default setting and click next

Readiness check – whether your server is ready for Exchange 2013, click install once done

Installation begins and it has 14 steps. It will take some time

Setup completion, read and click finish.

Exchange Server 2013 program shortcuts on Windows Server 2012. Note that the Exchange Management Console (EMC) is no where to be seen. This is because the traditional EMC is being moved to a web interface

https://servername/owa

https://<Exchange Server FQDN/IP>/ecp
https://localhost/ecp

Error while installing Exchange 2013

2013-01-29T18:21:00.000+05:30

Installation Fail of Exchange 2013 in PrepareAD and Setup.exe

[ERROR] Setup encountered a problem while validating the state of Active Directory: Couldn’t find the Enterprise Organization container.
[08/23/2012 16:50:04.0804] [0] The Exchange Server setup operation didn’t complete. More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
[08/23/2012 16:50:04.0804] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\V15\Setup, was not found.
[08/23/2012 16:50:04.0804] [0] End of Setup

More Error details from ExchageSetupLog

[08/23/2012 18:53:19.0615] [0] Setup is choosing a local domain controller…
[08/23/2012 18:53:28.0981] [0] Setup has chosen the local domain controller SRVR2012.WIN12.COM for initial queries
[08/23/2012 18:53:29.0614] [0] [ERROR] Setup encountered a problem while validating the state of Active Directory: Couldn’t find the Enterprise Organization container.
[08/23/2012 18:53:29.0614] [0] [ERROR] Couldn’t find the Enterprise Organization container.
[08/23/2012 18:53:29.0614] [0] Setup will use the domain controller ”.
[08/23/2012 18:53:29.0614] [0] Setup will use the global catalog ”.
[08/23/2012 18:53:29.0614] [0] Exchange configuration container for the organization is ‘CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=WIN12,DC=COM’.
[08/23/2012 18:53:29.0614] [0] No Exchange organization container was found for the organization. Message: ‘Couldn’t find the Enterprise Organization container.’.
[08/23/2012 18:53:29.0614] [0] Setup will search for an Exchange Server object for the local machine with name ‘SRVR2012′.
[08/23/2012 18:53:29.0723] [0] No Exchange Server with identity ‘SRVR2012′ was found.

CAUSE :

Generally this problem occurs when unsuccessful installation of Exchange server 2013 found in Active directory Forest.

SOLUTION :

First of all Delete the Exchange Server Folder – "C:\Program Files\Microsoft\Exchange Server."

Log on to the domain controller with administrative credentials.
Click Start, click Programs, click Administrative Tools and then click Active Directory Users and Computers.
In the Active Directory Users and Computers management console pane, click View from the toolbar menu and select Advanced Features.
In the Active Directory Users and Computers management console pane, locate the incorrect, duplicate Microsoft Exchange System Objects container or organizational unit (OU).
Verify the incorrect, duplicate Microsoft Exchange System Objects container or OU does not contain valid Active Directory objects.
Right-click the incorrect, duplicate Microsoft Exchange System Objects container or OU and then click Delete.
Confirm the deletion by clicking Yes in the Active Directory dialog box.

For More information Please visit microsoft Technet website :
http://technet.microsoft.com/en-us/library/aa998138%28v=exchg.80%29.aspx

Now Run the setup again. :) :)

MP Control Failed To Start

2013-01-18T12:57:00.003+05:30

Error :

SMS_MP_CONTROL_MANAGER failed to start with 0x8004100e SMS_MP_CONTROL_MANAGER in MPCONTROL.LOG

Cause :

0x8004100e = WBEM_E_INVALID_NAMESPACE

Resolution :

To resolve above problem needs to check WMI Permissions or follow below steps.

1) Reboot Site Server. ( also Reboot Database server if installed separately. ) OR

2) Uninstall SCCM Client from Site Server. OR

3) Open Command Prompt on Site server and type winmgmt /salvagerepository command to refresh WMI Permission. OR

4) Reset Site System will reinstall Management Point.

Facing Issue while running Report Builder in SCCM 2012

2013-01-04T14:43:00.000+05:30

Facing Problem to run SQL Report builder Tool from SCCM 2012 Server.

Cause :

if you are using SQL 2008 R2 server for SCCM 2010 in your orgenization,

By default SCCM 2012 server configured to use report Builder 2.0 and SQL 2008 R2 uses Report Builder 3.0 version which needs to change.

Resolution :

in order to resolve this issue needs to modify Registry value as mentioned below.

1. Go to RUN and Open Regedit.exe / regedit32.exe

2. \HKLM\Software\Wow6432Node\Microsoft\ConfigMge10\AdminUI\Reporting\ReportBuilderApplicationManifestName.

3. Change the Value from "ReportBuilder_2_0_0_0.application" to "ReportBuilder_3_0_0_0.application"

4. That's It!!!!

Portal Web Site Control Manager detected PORTALWEB is not responding to HTTP requests. The http status code and text is 500, Internal Server Error.

2013-01-04T13:26:00.000+05:30

Facing Error accessing the Application Catalog Web Site on SCCM 2012.

Status Message Error in SCCM:
Component: SMS_PORTALWEB_CONTROL_MANAGER

Message ID: 8000

Description:

"Portal Web Site Control Manager detected PORTALWEB is not responding to HTTP requests. The http status code and text is 500, Internal Server Error."

Cause :

This issue occurs because the Applicationhost.config file for Windows Process Activation Service (WAS) has the following section defined, and this section is incompatible with the .NET Framework 4.0:
<add name="ServiceModel" type="System.ServiceModel.Activation.HttpModule, System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" preCondition="managedHandler" />
This section should be defined as follows:
<add name="ServiceModel" type="System.ServiceModel.Activation.HttpModule, System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" preCondition="managedHandler,runtimeVersionv2.0" />

This is caused by an issue with .Net 4.0, so perform the following on the Web Server hosting the Application Catalog Website Point (and also possibly the Application Catalog Web Service Point - In my tests, both roles are on the same system):

Resolution Steps :

1) Open Command Prompt ( cmd.exe ) on SCCM server or where you have installed Application Catalog Role installed.

2) Navigate to below path

%windir%\Microsoft.NET\Framework\v4.0.30319

%windir%\Microsoft.NET\Framework64\v4.0.30319 (on a 64-bit computer)

3) Run "aspnet_regiis.exe /iru" Command.

4) that's It!!!!!!!

For more information please Go through below Microsoft Knowledgeable Article.

Related Technet article: http://support.microsoft.com/kb/2015129

SMTP Custome Error Codes

2012-10-23T14:30:00.001+05:30

SUMMARY
Error codes that can be displayed in the SMTP debug and activity log files.
DETAIL
The easiest way to determine why inbound messages are not being processed by the SMTP connector is to examine the SMTP Activity and Debug logs. The logs can be found in the MailEnable Admin MMC -> Servers -> Localhost -> Connectors ->SMTP Logs.
These log files record SMTP transactions and their associated response codes.
These response codes are explained further with possible resolutions below:

220 Service ready

Error Description: This response is sent from the SMTP server when a remote SMTP client or host has successfully connected to the SMTP service.

221 Service closing transmission channel

Error Description: This response is sent from the server when the remote server/client has notified that it is closing the connection. You would commonly notice this command after a QUIT command was received.

250 Requested mail action okay, completed

Error Description: This response indicates that a SMTP command was received by the server and successfully processed.

354 Start mail input; end with .

Error Description: This response is sent by the SMTP server and instructs a remote SMTP server or client that the DATA command was accepted and that it can commence sending the actual message. A message consists of;
[first the message headers],[CRLF].[CRLF] then
[the actual message body],[CRLF].[CRLF]

421 Service not available, closing transmission channel

Error Description: This response is sent by the SMTP server to a remote SMTP server or SMTP client to indicate that the MailEnable SMTP Server is currently unavailable.

Error Resolution: When this error is returned in the logs or to a client then it usually means that the data store in particular the configuration directory data cannot be accessed.
When using a default install of MailEnable you can check and repair the permissions on the MailEnable TAB delimited configuration files by comparing and/or executing the commands in step 6 of the following article:
Article ME020073
If you have changed your default installation to use the MailEnable database provider and are using an SQL database server while getting this error then ensure that the database is online. If the database is online then ensure MailEnable services are able to connect and retrieve data from the database tables you may also find errors for this within the server Event Logs.

451 Requested action aborted: error in processing

Error Description: This response is sent by the SMTP server to a remote SMTP Server or SMTP client to indicate that the MailEnable SMTP Server is currently unable to complete the transaction or command. There can often be more information contained within the SMTP debug logs for this error.

Error Resolution:When this error is returned in the logs or to a client then it usually means that the data store in particular the configuration directory data cannot be accessed. The first thing to check is that your hard drive is not full or faulty or in some cases ensure that any quotas enabled on the drive are not being exceeded. Information on these types of problems can usually be found in the server Event Logs.
When using a default install of MailEnable you can check and repair the permissions on the MailEnable TAB delimited configuration files by comparing and/or executing the commands in step 6 of the following article:
Article ME020073
If you have changed your default installation to use the MailEnable database provider and are using an SQL database server while getting this error then ensure that the database is online. If the database is online then ensure MailEnable services are able to connect and retrieve data from the database tables.

451 Temporary server error. Please try again later.

Error Description: This response is sent by the SMTP server to a remote SMTP Server or SMTP client to indicate that the MailEnable SMTP Server is currently unable to complete the transaction or command. There can often be more information contained within the SMTP debug logs for this error.

Error Resolution: When this error is returned in the logs or to a client then it usually means that the data store in particular the configuration directory data cannot be accessed. The first thing to check is that your hard drive is not full or faulty or in some cases ensure that any quotas enabled on the drive are not being exceeded. Information on these types of problems can usually be found in the server Event Logs.
When using a default install of MailEnable you can check and repair the permissions on the MailEnable TAB delimited configuration files by comparing and/or executing the commands in step 6 of the following article:
Article ME020073
If you have changed your default installation to use the MailEnable database provider and are using an SQL database server while getting this error then ensure that the database is online. If the database is online then ensure MailEnable services are able to connect and retrieve data from the database tables.

451 Requested action aborted: This mail account has sent too many messages in a short amount of time. Please try later.

Error Description: Means that the SMTP configuration setting to limit the the quantity of messages sent per hour has been reached. The message sent in this instance has failed and will need to be retried by the client.
Error Resolution: This feature is disabled by default. You can review this and increase the configured amount of messages per hour or accept the error as correctly limiting a sender or domain.

In the MailEnable Professional or Enterprise manual the settings can be found at:
Post Office Restriction - Administration->Post Office configuration->Restrictions->Limit Maximum SMTP recipients
Mailbox Restriction - Administration->Post Office actions->Create Mailbox->Restrictions->Limit SMTP usage to a maximum of

451 This server employs greylisting as a means of reducing spam. Please resend e-mail shortly

Error Description: This is the temporary error returned to a connecting server when they try to send to an address for the first time while the MailEnable Greylisting spam protection feature is enabled.
Error Resolution: You can in this situation disable the Greylisting service or whitelist the connecting IP. By whitelisting the IP in the Greylisting feature options it means that when this server connects to the MailEnable SMTP service next it will bypass the Greylisting check.

In the ME Admin MMC the option is configurable at:
Note: MailEnable Professional version users can set this feature at a global level only so the first configuration option below applies. Enterprise users as with most features can also configure this at a post office and mailbox level.
ME Admin MMC->Servers->Localhost->SMTP "Properties"->Greylisting (TAB)
In the MailEnable Professional or Enterprise manual the setting can be found at:
Greylisting Global Configuration - Configuration of connectors, services and agents->SMTP Connector->SMTP - Greylisting
Post Office Restriction - Administration->Post Office configuration->Feature Selection->Force Greylisting for all users
Mailbox Restriction - Administration->Post Office actions->Create Mailbox->Spam->Enable Greylisting
451 The IP Address you are sending from was reported as a source of spam. Please contact your e-mail administrator.

Error Description: If a connecting IP has been found in a configured DNS blacklist then this error can be returned to the client and server.
Error Resolution: The best resolution in this case if you want to receive messages from the sending server is to alert the connecting server administrator that they are listed on a blacklist and need to get themselves removed. In some cases it can be easier to whitelist their IP in the SMTP whitelist option as this will bypass any Blacklist checks on the inbound. You can find out more on this rejection in the SMTP debug logs it should also list the blacklist name that the connecting IP was found in.

Note: We are assuming that the default setting in the blacklisting action feature is set to "Dont Accept Email". If this setting is configured to "Mark As Spam" then the message will be accepted and processed by internal filter actions.
In the MailEnable Professional or Enterprise manual the settings can be found at:
Global Restriction - Configuration of connectors, services and agents->SMTP Connector->SMTP Reverse DNS blacklisting
451 ESMTP MailEnable Service temporarily refused connection at [time] from IP [xxx.xxx.xxx.xxx] because the server is too busy

Error Description: When the SMTP service inbound connection limit is reached the service will reply with this temporary error. Usually in this situation the remote server will automatically retry the send to the service.
Error Resolution: This error is a warning and it should be reveived and considered correctly if increasing this inbound thread limit for the error. The default setting for this feature restriction is 32 connections or threads which for most servers will be enough. In high throughput servers you may find that this limit needs to be increased and as such you increase it as you feel, usually 256 is enough for most servers.
If this limit is being reached then you can check the SMTP activity logs and see how many connections you are getting before the error is returned in the logs. While checking make sure the inbound connections appear to be valid and not all coming from one IP or one domain/sender if they are repeating then you should use the other information in the logs to check if the messages are legitimate or the sender needs blocking.
The limit is in place to help prevent spammers or hackers from completing a DOS attack on the server and sending an unlimited and untimed connection based attack to your server.
In some cases if this error continues it can be a good idea to review your DNS Blacklisting service. If you have too many blacklists or one blacklist is timing out on connection then it can tie up your inbound connections for too long. The best way to check this is to disable all blacklists except one along with disabling the URL blacklisting to see if it helps.
Article ME020343

In the MailEnable Professional or Enterprise manual the setting can be found at:
Configuration of connectors, services and agents->SMTP Connector->Inbound->Maximum number of concurrent connections
452 Too many recipients

Error Description: Means that the SMTP configuration setting to limit the inbound recipients per transaction or message has been exceeded.
Error Resolution: This error is a warning and it should be reviewed and considered correctly if increasing this limit. The limit is in place to help prevent spammers or hackers from completing a DOS attack on the server and sending to a large amount of recipients in one connection. You may need to increase or disable this setting if you are sending mail outs as this error can be triggered when you are trying to send a mail out from a script or send mail program.

Article ME020268
In the MailEnable Professional or Enterprise manual the setting can be found at:
Configuration of connectors, services and agents->SMTP Connector->SMTP - Security->Restrict the number of recipients per email
452 You are not permitted to send to remote domains

Error Description: When this error is shown in the client and/or logs it means that the internal MailEnable configuration setting to limit a mailbox, post office or server has been enabled. By default this setting is not enabled but when changed it can prevent a singular mailbox, or all mailboxes in a domain or even on the server to only be able to send locally to their own domain.
Error Resolution: If this error is believed to be in error then it can be disabled in the ME Admin MMC. In each of the configuration options below you can change the option to allow the mailboxes to send to local and remote domains or restrict mailboxes to only send to local addresses.

Note: MailEnable Professional version users can set this feature at a global level only so the first configuration option below applies.
The first place to check for this setting is at the global level in the ME Admin MMC at:
ME Admin MMC->Servers->Localhost "Properties"->Policies (TAB)->Sender Policy
If the setting above is set to the option "Sending policy determined by postoffice" then you need to check the following place:
ME Admin MMC->Post Offices->[Post Office Name] Properties->Restrictions (TAB)->"The sender policy determines whether users can only send messages to a local domain"
If the above setting is set to "Sending policy determined by mailbox" then you need to check the following place.
ME Admin MMC->Messaging Manager->Post Offices->[Post Office Name]->Mailboxes->[Mailbox Name] "Properties"->Restrictions (TAB)->"User can only send to their local domain"
In the MailEnable Professional or Enterprise manual the settings can be found at:
Global Restriction - Administration->Server Configuration->Policies->Sender Policy
Post Office Restriction - Administration->Post Office configuration->Restrictions->Same Domain Restriction
Mailbox Restriction - Administration->Post Office actions->Create Mailbox->Restrictions->Local Sender Restriction
500 Message rejected because it contains links to an IP address that is blacklisted

Error Description: As a message is being received the SMTP service will resolve links in the message and check these against the configured blacklist. If the destination IP from the resolve is listed in a configured blacklist the message will be rejected with this error.

Note: We are assuming that the default setting in the blacklisting action feature is set to "Don't Accept Email". If this setting is configured to "Mark As Spam" then the message will be accepted and processed by internal filter actions.
Note: When URL blacklisting is executed we check the first section of the message only, about 20 lines. Checking large messages with many links can affect performance. In most situations, if not all, this is enough as spammers do not tend to send many links or large messages.

Error Resolution: The best resolution if you want to receive messages from the sending server is to alert the connecting server administrator that they are sending message links that are listed on a blacklist. In some cases it can be easier to whitelist their IP in the SMTP whitelist option as this will bypass any URL Blacklist checks on the inbound. You can find out more on this rejection in the SMTP debug logs it should also list the blacklist name that the connecting IP was found in.

In the MailEnable Professional or Enterprise manual the settings can be found at:
Global Restriction - Configuration of connectors, services and agents->SMTP Connector->SMTP Reverse DNS blacklisting
500 Syntax Error, command unrecognized

Error Description: This error means that a remote client or server has sent a command that is not recognized by the MailEnable SMTP service.
Error Resolution: The best way to find out more about this error is to check the SMTP activity log at the time of the connection as the command will be listed in the log transaction.

501 Syntax error in parameters or arguments

Error Description: This error means that the remote server is sending incorrect commands through to the server. Often this can occur when the message contains a line that is too long and as such cannot be read by the MailEnable SMTP service.
Error Resolution: Check the SMTP activity and debug logs in this situation as there should be more information on what is occurring. If the logs do not help then check how the message is being sent to see if you can find anything that is abnormal.

501 Invalid Address

Error Description: This error means that the address format used in the sending client is not correct. Usually this is checked in a standard retail client but when using scripts or web pages it may not be the case.
Error Resolution: Check the SMTP activity logs as they should show what format and what characters are being used for the addresses. Check in particular for incorrect characters, here is a list of correct email address characters;
Use any ASCII alphanumeric character plus (`!', `#', `$', `% `&', `*' `+', `-' `~', and whatever you can find in between ASCII 33 and 47).
In short, you should use lower case characters, numbers and the underscore to create your email address.

501 Your domain does not seem to be valid, Could not find MX record for your domain.

Error Description: This error means that the sending email address contains a domain that is not a registered domain name.
Error Resolution: This check is done when the following feature is enabled. The sender should check their email client settings and ensure that their configured email sender address contains a correct and valid domain name after the @ sign.

In the MailEnable Professional or Enterprise manual the setting can be found at:
MailEnable Manual - Configuration of connectors, services and agents->SMTP Connector->SMTP -Security->reject mail if sender address is from an invalid domain
502 Command not implemented

Error Description: This error means the remote client or server is trying to send a command that is not supported by the SMTP service.
Error Resolution: Use the SMTP activity logs to find out what command was sent to the MailEnable SMTP service. The commands that MailEnable lists and can use are listed in the SMTP service on the Advanced SMTP tab if the command is not listed then it is not supported or incorrect. On this tab the commands can also be enabled or disabled the feature can be found in the following location of the ME Admin MMC:
ME Admin MMC->Servers->Localhost->Connectors->SMTP "Properties"->Advanced SMTP (TAB)->Allowed SMTP commands

503 Bad sequence of Commands
Error Description: The error means that the remote client has sent a command to the server that is not in the correct and recognised order for the SMTP service.
Error Resolution: Use the SMTP activity logs to find out what the commands were and that they were issued in the correct order.
503 Bad sequence of commands. You must specify the recipients of a message before you can send it
Error Description: The error means that a client or server has tried to send a message to the MailEnable SMTP service without the presence of or a correct SMTP address in the TO, CC or BCC field.
Error Resolution: Check the client that is sending and determine why it is not correct you may also find out more in the MailEnable SMTP activity log.
503 Bad sequence of commands. Could not process DATA command when in this state
Error Description: The error means that a client or server has tried to send a message to the MailEnable SMTP service but has sent the DATA command out of sequence.
Error Resolution: Check the client that is sending and determine why it is not correct usually you will see that the client is sending a DATA command while the SMTP service is expecting another command like RCPT TO, EHLO
503 Bad sequence of commands. Could not process RCPT command when in this state
Error Description: The error means that a client or server has tried to send a message to the MailEnable SMTP service but has sent the RCPT TO command out of sequence.
Error Resolution: Check the client that is sending and determine why it is not correct. Usually you will see that the client is sending a RCPT TO command while the SMTP service is expecting another command.
503 This mail server requires authentication when attempting to send to a non-local e-mail address. Please check your mail client settings or contact your administrator to verify that the domain or address is defined for this server.
Error Description: This error means that the server or client has connected to the MailEnable SMTP service but has not entered a RCPT TO mail address that exists on the server but the domain for the incorrect address does reside on the server. The order of checks in this situation are;
1. Does the domain exist on the server (Yes)
2. Does the address exist in the address-map.tab file or table on the server (No)
3. Has the client authenticated. (Due to earlier No at 2 this check has not occurred.
As the connection has not authenticated meaning that one of the options above in 1 or 2 have not been met then the error is returned.
Error Resolution: The resolution here really resolves around when you think this error is being returned when it should not be. If the address is thought to exist on the server then you need to check the SMTP logs activity for the transaction and then the debug to see if there are any error descriptions that better explain what happened when the address was sent to. Then you should check your configuration to ensure that the address does exist. It can also be a good idea to check the address-map.tab file in the MailEnable\Config directory or relevant database table for a line that contains the mailbox name in question. If you are checking why the sender could not relay through the server then you should at this time check the client settings and ensure that the outbound settings in the client are configured as such so they can relay through the server to non local email addresses.
Article ME020198
503 Too many invalid commands were received. Terminating Session
Error Description: This error means that the threshold of the MailEnable SMTP security feature has been reached for too many invalid or unrecognized commands sent to the server.
Error Resolution: If this error is not working the way you expected then you can disable the feature or increase the configured limit so the connection is not dropped prematurely.
In the ME Admin MMC the option is configurable at:
ME Admin MMC->Servers->Localhost->SMTP "Properties"->Security (TAB)->Connection Dropping
In the MailEnable Professional or Enterprise manual the settings can be found at:
Configuration of connectors, services and agents->SMTP Connector->SMTP Security->Drop a connection when the failed number of commands or recipients reaches504 Access to this user account has been denied by the mail administrator
Error Description: When this error is returned to a client it means that the mailbox has been configured by an administrator to not allow authentication.
Enterprise users may have a mailbox placed into this reject authentication status if the mailbox reaches the Server Password Policy lockout limit.
The Server Password Policy lockout limit in the ME Admin MMC is configurable at:
ME Admin MMC->Localhost "Properties"->Policies (TAB)->Password Policies
In the MailEnable Professional or Enterprise manual the settings can be found at:
Administration->Server configuration->Policies
Error Resolution: You can remove the mailbox authentication lock from the mailbox in the mailbox properties within the ME Admin MMC.
In the ME Admin MMC the option is configurable at:
ME Admin MMC->Messaging Manager->Post Offices->[Post Office Name]->Mailboxes->[Mailbox Name] "Properties"->General (TAB)->Prevent user from authenticating.
In the MailEnable Professional or Enterprise manual the settings can be found at:
Administration->Post office actions->Create mailbox->General->Prevent user from authenticating
504 User account has been disabled by the mail administrator
Error Description: When this error is returned to a client it means that the mailbox has been configured by an administrator to not allow authentication.
Enterprise users may have a mailbox placed into this reject authentication status if the mailbox reaches the Server Password Policy lockout limit.
The Server Password Policy lockout limit in the ME Admin MMC is configurable at:
ME Admin MMC->Localhost "Properties"->Policies (TAB)->Password Policies
In the MailEnable Professional or Enterprise manual the settings can be found at:
Administration->Server configuration->Policies
Error Resolution: You can remove the mailbox authentication lock from the mailbox in the mailbox properties within the ME Admin MMC.
In the ME Admin MMC the option is configurable at:
ME Admin MMC->Messaging Manager->Post Offices->[Post Office Name]->Mailboxes->[Mailbox Name] "Properties"->General (TAB)->Prevent user from authenticating.
In the MailEnable Professional or Enterprise manual the settings can be found at:
Administration->Post office actions->Create mailbox->General->Prevent user from authenticating550 Requested action not taken: mailbox unavailable or not local
Error Description: This error means that the server or client has connected to the MailEnable SMTP service but has not entered a RCPT TO mail address or domain that exists on the server. The address is checked in the local configuration files in particular the address-map.tab file or database table.
Error Resolution: The resolution here really resolves around when you think this error is being returned when it should not be. If the address is thought to exist on the server then you need to check the SMTP activity logs for the transaction and then the debug to see if there are any error descriptions that better explain what happened when the address was sent to. Then you should check your configuration to ensure that the address does exist. It can also be a good idea to check the address-map.tab file in the MailEnable\Config directory or relevant database table for a line that contains the mailbox name in question. 550 Requested action not taken. The domain you are sending from is not permitted to access this server
Error Description: When this error is returned to a client it means that the domain has been blocked from sending to any address in the receiving post office.
In the ME Admin MMC this is configurable at:
ME Admin MMC->Post Offices->[Post Office Name]->Domains->[Domain Name] "Properties"->Blacklist (TAB)->Domains
In the MailEnable Professional or Enterprise manual the settings can be found at:
Administration->Post office actions->Create domain->Blacklist550 This mail server requires authentication (0) when attempting to send via this SMTP (submission) port
Error Description: When this error is received it means that the MailEnable server SMTP service has been configured to force all inbound connections to authenticate. This setting is designed mainly for servers that want all mail to come from a remote spam checking service as it forces connections that send to and through the server to authenticate unless they are allowed relay by IP. All other connections even when simply sending to the server will fail with this error if this is not the case.
In the ME Admin MMC this is configurable at:
ME Admin MMC->Servers->Localhost->SMTP Properties->Inbound (TAB)->"Properties"->Port Settings [Button]->SMTP Port->"Requires connections to authenticate before sending email"
Or for alternate SMTP listening port:
ME Admin MMC->Servers->Localhost->SMTP Properties->Inbound (TAB)->"Properties"->Port Settings [Button]->Submission Port->"Requires connections to authenticate before sending email"
In the MailEnable Professional or Enterprise manual the settings can be found at:
Configuration of connectors, services and agents->SMTP Connector->Inbound->Requires connections to authenticate before sending email
Error Resolution: The resolution is determined by whether you want this feature to be enabled or not. If you are getting this error when you are not expecting then ensure that this feature is not enabled for either SMTP port. If you require this feature and understand what it does then ensure any servers that are required to send through the server and not authenticate are added to the inbound IP relay list.
551 User not local: authentication required for relaying
Error Description: This error means that the server or client has connected to the MailEnable SMTP service but has not entered a valid MAIL FROM mail address. The address is checked in the local configuration files in particular the auth.tab file or database table.
This error can also mean that the mailbox that has been entered into the MAIL FROM address line is local on the server but has been disabled on the server by a server administrator or in some cases a control panel.
Error Resolution: The resolution here really resolves around when you think this error is being returned when it should not be. If the address is thought to exist on the server then you need to check the SMTP logs activity for the transaction and then the debug to see if there are any error descriptions that better explain what happened when the from address was entered. Then you should check your configuration to ensure that the address does exist. It can also be a good idea to check the auth.tab file in the MailEnable\Config directory or relevant database table for a line that contains the mailbox name in question.
If the mailbox has been disabled then you can find the setting for this in the following location.
In the ME Admin MMC this is configurable at:
ME Admin MMC->Messaging Manager->Post Offices->[Post Office Name]->Mailboxes->[Mailbox Name] "Properties"->General (TAB)->Domains->Mailbox is disabled
In the MailEnable Professional or Enterprise manual the settings can be found at:
Administration->Post office actions->Create mailbox->General->Logon disabled551 Sender address is not valid for your login. Check your email program settings
Error Description: This error is returned when a client is connecting to relay through the MailEnable server and has authenticated with a correct mailbox address but in the sender field of the mailbox the address does not match. If this was not prevented it means that a mailbox on the server can authenticate correctly as one address but be able to send with a different from address in effect the sender would be creating a forged email.
Error Resolution: If you want to allow these email addresses to be different then you will need to disable the security feature in the SMTP options.
In the ME Admin MMC this is configurable at:
ME Admin MMC->Servers->Localhost->Connectors->SMTP "Properties"->Security (TAB)->Authenticated senders must use valid sender address
In the MailEnable Professional or Enterprise manual the settings can be found at:
Configuration of connectors, services and agents->SMTP Connector->SMTP Security->Authenticated senders must use valid sender address
552 Message size exceeds fixed maximum message size
Error Description: This error is displayed when either the configured SMTP inbound or outbound limit has been exceeded.
Error Resolution: You can find out about which SMTP option either inbound or outbound was the one that prevented the message by checking the SMTP activity logs. If the message is inbound in the log you will see SMTP-IN at the start of the line if the message was restricted while leaving the server (outbound) then the log line will contain SMTP-OU.
The inbound SMTP limit is configurable at the following location:
ME Admin MMC->Servers->Localhost->Connectors->SMTP "Properties"->Inbound (TAB)->Advanced Settings |Button|->Advertised maximum message size + Enforce this message size
The outbound SMTP limit which places a limit on relayed messages is configured at the following location:
ME Admin MMC->Servers->Localhost->Connectors->SMTP "Properties"->Outbound (TAB)->Limit outbound message size

554 The IP address of the sender (xxx.xxx.xxx.xxx) was found in a DNS blacklist database and was therefore refused
Error Description: This error means that an inbound connection has been detected as being listed in one of your configured DNS blacklists within the SMTP options.
To find out more about this feature check the MailEnable manual:
In the MailEnable Professional or Enterprise manual the settings can be found at:
Configuration of connectors, services and agents->SMTP Connector->Reverse DNS blacklistingError Resolution: The resolution in this situation varies depending on the inbound connection itself and your verification of the validity of the sender. In short if the sender is blacklisted and you want to receive mail from this sender then you should suggest/request that they remove themselves from the blacklist (Click here for more) Article ME020166. In some situations this resolution can be too slow or troublesome and as such you can either stop checking this particular blacklist by removing it from the SMTP blacklist options configuration or you can add the connecting IP to the Whitelist of the SMTP service this will ensure that any future connections from this IP bypass the blacklist check.

554 The IP address of the sender (xxx.xxx.xxx.xxx) does not match the SPF record for the sender domain
Error Description: This error correlates to the SPF checking feature within the MailEnable SMTP service settings. The SPF feature checks for a valid SPF record to be configured in DNS and then acts on this according to your actions configured in the SPF feature within ME Admin MMC.
To find out more about this feature check the MailEnable manual:
In the MailEnable Professional or Enterprise manual the settings can be found at:
Configuration of connectors, services and agents->SMTP Connector->Sender Policy Framework (SPF)Error Resolution: In a similar manner to the Blacklisting feature the resolution in this situation varies depending on the inbound connection itself and your verification of the validity of the sender. If the sender is rejected in this situation and you want to receive mail from this sender then you should suggest/request that they correct their SPF record and /or ensure that they have one configured (Click here for more) Article ME020345. In some situations this resolution can be too slow or troublesome and as such you can either turn off the checking of SPF altogether or you can add the connecting IP to the Whitelist of the SMTP service this will ensure that any future connections from this IP bypass the SPF check.

Requested action not taken: mailbox unavailable or not local

2012-10-23T14:26:00.001+05:30

Hi Friends,

i have setup exchange 2010 on premise and Recently facing issues regarding email bounce from google App with below error.

Error :

"550 Requested action not taken: mailbox unavailable" only form some of the mail server.
and
"Requested action not taken: mailbox unavailable or not local"

to resolve this issue i search a lot on internet but not able to find any propper solution, after investigation i found the solution and working fine without any problem,

Resolution :

configure Gateway firewall for SMTP Traffic or disable Email scan for Mail server.

in my next blog i will describe various smtp errors with cause and resolutions.

thanks,
Gaurang Patel

Microsoft Technology

Disable Azure AD Sync and Federated Authentication ( ADFS ) in O365

Failed to open mailbox abc@abc.onmicrosoft.com" "failed to access mailbox" " Mailbox does not exist"

Microsoft Exchange Active Sync "HTTP error 500.24 - Internal Server Error" and "An HTTP 500 response was returned from IIS7"

how to activate Office365

Office 365 Lync Online SRV settings in Plesk DNS Control Panel

Problem:

Symptoms :

Resolution :

Exchange 2013 Outlook and OWA Search Does Not Work

Setting up Vtiger CRM PBX Manager with Asterisk

Restore missing Standard TCP/IP Port type for Printer

Restore missing Standard TCP/IP Port type for Printer

Exchange 2010 SP1, SP2 or Sp3 Error: Setup cannot continue with the upgrade because the “beremote()” process has open files.

Exchange 2010 SP1, SP2 or Sp3 Error: Setup cannot continue with the upgrade because the “beremote()” process has open files.

Step by Step Adobe Reader Enterprise Depolyment

Adobe Reader Enterprise Depolyment

SharePoint People Picker, Audiences And Active Directory Trusts

SharePoint People Picker, Audiences And Active Directory Trusts

In Place Upgrade Of Windows Server 2008 R2 Standard To Enterprise Or Datacenter Edition

error: Your request can't be completed right now. Please try again in a few moments.

error: 2013 Your request can't be completed right now. Please try again in a few moments.

Windows Server Backup failed to backup with error 0x81000101

Windows Server Backup failed to backup with error 0x81000101

Symptom:

Sometimes Windows Server Backup failed to backup the data. The error is:

The shared restore point operation failed with error (0x81000101) The creation of a shadow copy has timed out. Try this operation again.

In the event viewer, found the following error:

Cause:

Windows Server Backup is timing out during shadow copy creation since it is taking more than 10 minutes.

Resolution:

- Run regedit.exe and navigate to "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\SPP"

- Create a new Registry value of type DWORD with name "CreateTimeout"

- Change value to 12000000(2*10*60*1000 = 20 mins) in decimal

More information:

http://blogs.technet.com/b/filecab/archive/2009/09/16/diagnosing-failures-in-windows-server-backup-part-1-vss-spp-errors.aspx

System State Backup Failed on Windows 2008 R2 SP1 with Windows Backup

Exchange Server 2007 / 2010 Transport: 452 4.3.1 Insufficient system resources

Exchange Server 2007 / 2010 Transport: 452 4.3.1 Insufficient system resources

What’s Back Pressure?

Changes to Back Pressure settings in Exchange Server 2007 SP1

The Resolution

how to increase Virtual Processor ( vCPU) in Hyper-v Guest OS

step by step installation of Microsoft Exchange 2013

Error while installing Exchange 2013

Installation Fail of Exchange 2013 in PrepareAD and Setup.exe

More Error details from ExchageSetupLog

Now Run the setup again. :) :)

MP Control Failed To Start

Error :

Cause :

Resolution :

Facing Issue while running Report Builder in SCCM 2012

Portal Web Site Control Manager detected PORTALWEB is not responding to HTTP requests. The http status code and text is 500, Internal Server Error.

Facing Error accessing the Application Catalog Web Site on SCCM 2012.

SMTP Custome Error Codes

Requested action not taken: mailbox unavailable or not local

- Change value to 12000000(21060*1000 = 20 mins) in decimal