Autodiscover errors after installing a ssl certificate on a Exchange server

When you install a Exchange 2007 or 2010 client access server and using outlook 2007 or 2010. You will get a autodiscover error by default. Also connect with outlook webaccess or web app you get a certificate error.

To solve this problem you will have to import the certificate on all computers. Another way is to buy a trusted third party certificate. In most cases this will be a SAN / UCC certificate so you can use multiple names on the certificate, webmail.domain.name, autodiscover.domain.name, servername.domain.name and for a transition legacy.domain.name.

But after you request and installed the certificate you still get a autodiscover or certificate error.

Possible solution: you will have to change some autodiscover and client access setting, I will describe the wat to check and change the settings with the Exchange management shell. Some settings can also be changed by GUI.

Check the AutoDiscoverServiceInternalUri with the following command: Get-ClientAccessServer |ft Identity,AutoDiscoverServiceInternalUri
To change the setting: Set-ClientAccessServer -Identity “SERVERNAME” -AutoDiscoverServiceInternalUri “https://url.domain.name/autodiscover/autodiscover.xml”

For the next options you can set for both internal and external a different url. But you can choose to use same url for both in that case you will have to setup your internal and external dns right.

Check the AutodiscoverVirtualDirectory Get-AutodiscoverVirtualDirectory |ft internalurl,externalurl
To change the settings:
Set-AutodiscoverVirtualDirectory -Identity ‘SERVERNAME\Autodiscover (Default Web site)’ -ExternalUrl https://externalurl.domain.name/Autodiscover/Autodiscover.xml’
Set-AutodiscoverVirtualDirectory -Identity ‘SERVERNAME\Autodiscover (Default Web site)’ -InternalUrl ‘https://internalurl.domain.name/Autodiscover/Autodiscover.xml’

Check the WebServicesVirtualDirectory InternalUrl and ExternalUrl Get-WebServicesVirtualDirectory |ft internalurl,externalurl
To change the settings:
Set-WebServicesVirtualDirectory -Identity ‘SERVERNAME\EWS (Default Web site)’ -ExternalUrl ‘https://externalurl.domain.name/EWS/Exchange.asmx’
Set-WebServicesVirtualDirectory -Identity ‘SERVERNAME\EWS (Default Web site)’ -InternalUrl ‘https://internalurl.domain.name/EWS/Exchange.asmx’

You will have to do the same thing for all the next option. If you don’t use one of these options you can consider skipping the setting.

Get-OabVirtualDirectory |ft internalurl,externalurl
Set-OabVirtualDirectory -Identity “SERVERNAME\OAB (Default Web site)” -InternalUrl ‘https://internalurl.domain.name/OAB’
Set-OabVirtualDirectory -Identity “SERVERNAME\OAB (Default Web site)” -ExternalUrl ‘https://externalurl.domain.name/OAB’

Get-ActiveSyncVirtualDirectory |ft internalurl,externalurl
Set-ActiveSyncVirtualDirectory -Identity “SERVERNAME\Microsoft-Server-ActiveSync (Default Web Site)” -InternalUrl ‘https://internalurl.domain.name/OAB’
Set-ActiveSyncVirtualDirectory -Identity “SERVERNAME\Microsoft-Server-ActiveSync (Default Web Site)” -ExternalUrl ‘https://externalurl.domain.name/OAB’

Get-OwaVirtualDirectory |ft internalurl,externalurl
Set-OwaVirtualDirectory -Identity “SERVERNAME\owa (Default Web Site)” -InternalUrl ‘https://internalurl.domain.name/OAB’
Set-OwaVirtualDirectory -Identity “SERVERNAME\owa (Default Web Site)” -ExternalUrl ‘https://externalurl.domain.name/OAB’

Get-UMVirtualDirectory |ft internalurl,externalurl
Set-UMVirtualDirectory -Identity “SERVERNAME\UnifiedMessaging (Default Web site)” -InternalUrl ‘https://internalurl.domain.name/UnifiedMessaging/Service.asmx’
Set-UMVirtualDirectory -Identity “SERVERNAME\UnifiedMessaging (Default Web site)” -ExternalUrl ‘https://externalurl.domain.name/UnifiedMessaging/Service.asmx’

Note: when you using SBS 2008 you should replace (Default Web site) by (SBS Web Applications)

Posted in Blog, Exchange 2007, Exchange 2010 at September 3rd, 2010. 3 Comments.

Logon Failure on database while accessing or moving mailboxes

We were migrating a SBS 2003 server to a new SBS 2008 server via the swing migration method. After turning on the SBS 2008 server and temporary dc / exchange 2003 server we were not able to access or move the exchange 2003 mailboxes.

The mailbox move gives a: “The move-mailbox task for mailbox ‘mailboxname’ failed. Error: Failed to open mailbox with error: The operation failed.” error on the SBS 2008 (Exchange 2007) server.

On the Exchange 2003 server we get a: Event id 1022: “Logon Failure on database “First Storage Group\Mailbox Store” – Windows account domain\accountname; mailbox /o=domain/ou=first administrative group/cn=Recipients/cn=accountname.Error: 1144″ error.

Solution: It looks like that after forklift and update a exchange 2003 database it could take some time to connect because AD has to replicate the information between the 2 domain controllers. When this is done everything works fine. This can also occur after moving the exchange mailboxes to a the new sbs 2008 / exchange 2007 server.

Posted in Blog, Exchange 2007, SBS 2008 at August 17th, 2010. No Comments.

Default gateway disappears after restarting SBS 2008 server

Everytime you restart a Small Business Server 2008 the default gateway disappears.

Solution: When you take a look at the following registry key: HKLM/System/CurrentControlSet/Services/Tcpip/Parameters/Interfaces/ CLSID of the network card this is happening for, you’ll probably notice it by viewing the ipaddress value. Then open the “DefaultGateway” value. In our case you see the default gateway but above it there is an empty line. After removing the empty line, restarting works fine and the problem didn’t occur anymore.

Additonal information can be found on the official SBS blog

Posted in Blog, SBS 2008 at August 8th, 2010. 2 Comments.

Migrating printers using printbrm(ui) gives print monitor is unknown error

For migrating printer drivers and setting from a Windows 2003 SBS server to a Windows 2008 SBS server. I first updated all printers on the Windows 2003 SBS server so they have x64 drivers installed. After that I used printbrm(ui) on a Windows 2008 server to export all drivers and settings to a export file. This file I copied to my new Windows 2008 SBS server and tried to import it using printbrm(ui). When finished I got a lot of warnings and errors and most printers were not created. The following event id 37 was logged:

“Printbrm.exe (the Printer Migration Wizard or the command-line tool) could not restore driver HP LaserJet 4200 PCL 6 (Windows NT x86) while restoring print queues from a file. Error reported: 0x80070bb8. The specified print monitor is unknown.
. This can occur if the driver requires a file that Printbrm.exe did not back up or if the user does not have permission to install drivers on the destination computer.”

The problem was not the driver or not enough permissions. But when you take a look at the Windows 2003 SBS server in the printer properties, advanced tab, Print Processor properties, for the failing printers the print processor didn’t use the winprint – raw processor, but a HP and some characters – raw processor.

Solution: For some strange reason the export function doesn’t export the print processor. Change the print processor to winprint raw, make a new export and import that file everything works fine.

After importing if needed it self chooses to use a other print processor available at the new server.

Posted in Blog, SBS 2008, Windows 2008 at July 28th, 2010. No Comments.

SBS 2008 (exchange 2007) unable to receive mail

After migrating a Windows SBS 2003 server to a Windows SBS 2008 server no new external (internet) mail is deliverd to the new server. E-mailing internal works fine.

Solution: When you take a look in the Exchange 2007 Server Manager at server configuration, Hub Transport you see only a “Default Servername” receive connector:

SBS2008 default receive connector
Take a look at the properties and then the network tab, you probably see at receive mail from remote servers that have these IP addresses: only the internal ip addresses.

Option 1: You can change this to –

Option 2: You can recreate the “Windows SBS Internet Receive Servername” receive connector. Open a Exchange Management Shell and use the following command:
new-receiveconnector -Name “Windows SBS Internet Receive SERVER-NAME” -RemoteIPRanges,, -Bindings “” -AuthMechanism “Tls” -PermissionGroups “AnonymousUsers” -Usage “Internet” -Server “SERVER-NAME”

Change the command to your ip address in this example the server ip is

Option 2 is prefferred I’ve seen some strange problems with option 1 do’nt know for sure if this was relelated to this issue but if you can use option 2

Posted in Blog, Exchange 2007, SBS 2008 at July 23rd, 2010. No Comments.

Errors trying to move Windows SharePoint Services Data on SBS 2008

When you try to move Windows SharePoint Services Data via the Windows Small Business Server (SBS) 2008 server console, Backup and Server Storage on the tab Server Storage. You get this error: “An error occurred while attempting to move the Windows SharePoint Services data.” The remote server returned an error: (401) Unauthorized.

SharePoint Services Data move error

Solution: This error can occure after installing Microsoft Knowledge Base update kb957097. Read the article or this kb926642 carefully there are some methods to change a registry key witch give a solution. After changing the registry you have to restart your SBS 2008 server before the change take effect.

After restarting the server again tried to move Windows SharePoint Services Data the following error occurred: “An error occurred while attempting to move the Windows SharePoint Services data.” The remote name could not be resolved: ‘companyweb’

SharePoint Services data move error

Solution: In DNS Manager create a cname record “companyweb” in your Forward Lookup Zone Domain.local and point this to servername.domain.local. (don’t forget the . dot at the end)

Posted in Blog, SBS 2008 at July 21st, 2010. 3 Comments.
Sharing Buttons by Linksku