Run Microsoft Support and Recovery Assistant to diagnose the issue.
1.Start Registry Editor.
In Windows 10 and Windows 8, press the Windows Key + R to open a Run dialog box. Type regedit.exe and then press OK.
In Windows 7, click Start , type regedit in the Search programs and files box, and then press Enter.
2.Locate and then select the following registry subkey:
Notex.0 in this registry path corresponds to the Outlook version (16.0 = Outlook 2016, 15.0 = Outlook 2013, 14.0 = Outlook 2010, 12.0 = Outlook 2007).
3.Review the following possible DWORD values that may be located under the \Autodiscover subkey.
•ExcludeHttpsRootDomain – ignores Autodiscover.XML on domain website
•ExcludeScpLookup – Ignores local hosted exchange settings
Full Article link
The database size limit for Exchange 2003 standard is 16GB, however SP2 for Exchange 2003 allows you to remove that limit. The default size for priv.edb after installing SP2 for Exchange 2003 is 18GB this can easily be changed for database sizes upto 75GB per database.
The steps below explain how to increase the 18GB limit by editing the registry. Edit the registry at your own risk, I will not accept any responsibility if you run into problems.
- On the Exchange 2003 server, run regedit
- Navigate to the following registry key
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeIS\Server name\Private-Mailbox Store GUID
- Create a new DWORD entry called “Database Size Limit in GB”
- Change from Hexidecimal to Decimal and enter the value of the size in GB that you wish the maximum DB size to be.
- Exit from the registry editor
- You should now either restart the Information Store or dismount and mount the store in question.
The maximum database size for the priv.edb should have now been increased to the value you set in the new DWORD
During as SBS2003 migration to SBS2011, while decommissioning the source server (SBS2003) before Exchange 2003 can be removed you will have to remove the routing group connector from Exchange 2003 and Exchange 2010. You can use the Exchange System Manager to remove the 2003 to 2010 connector. To remove the connector from the destination server 2010 to 2003 you will use the Exchange Management Shell using the below command.
Remove-RoutingGroupConnector -Identity “Exchange Administrative Group (FYDIBOHF23SPDLT)\Exchange Routing Group (DWBGZMFD01QNBJR)\DestinationServer to SourceServer” -DomainController DestinationServer.LocalDomain.local
Make sure you change the following first;
DestinationServer = name of new SBS 2011 Server
SourceServer = name of old SBS 2003 Server
LocalDomain.local = name of the local domain
The use of this code is done at your own risk.
When migrating a SBS 2003 server to SBS 2011 you may receive the error “The received certificate has expired” whilst migrating the public folders from Exchange 2003 to Exchange 2010, if you do follow the steps below.
To remove the SSL binding to an incorrectly published certificate
- Navigate to the virtual root Exadmin in IIS.
- Right-click Exadmin, click Properties, and then click Directory Security.
- In the Secure Communications section, click Edit.
- Clear the Require secure channel (SSL) checkbox.
- If the Require 128-bit encryption checkbox is selected and is greyed out, perform these steps:
- Select Require secure channel (SSL).
- Clear Require 128-bit encryption.
- Clear Require secure channel (SSL).
- Launch the ADSI Edit tool from the Windows Support Tools. For more information about using the ADSI tool, see ADSI Edit (adsiedit.msc).
- In the left pane, click Configuration, and then click each of the following to expand:CN=ConfigurationCN=ServicesCN=Microsoft ExchangeCN=CN=Administrative Groups
CN=First Administrative Group
- Right-click CN=Exadmin, and then click Properties.
- In the list of attributes, scroll down to msExchSecureBindings, select it, and then click Edit.
- Select the entry :443:, click Remove, and then click OK.
- Click Apply, then click OK.
- Exit ADSI Edit.
- Close and reopen Exchange System Manager.
This article is given as is and I will not be held liable for anything that happens to your system.
Microsoft recently announced that Windows Small Business Server (SBS) 7 and Windows Small Business Server (SBS) Codename “Aurora”.
The next version of Windows Small Business Server will include a richer remote access experience, and updates to all of the component software in the suite to the latest versions (Windows Server 2008 R2, Microsoft Exchange Server 2010 SP1, Microsoft SharePoint 2010 Foundation, Windows Server Update Services 3.0 and Microsoft SQL Server 2008 R2). As a result, small business customers will find significant security and management enhancements, as well as much richer features for providing file-and-print, e-mail and Internet services to employees. Windows SBS 7 will support up to 75 users. Continue reading “Microsoft announce new SBS servers”