Quantcast
Channel: Exchange Server 2013 - Setup, Deployment, Updates, and Migration forum
Viewing all 7129 articles
Browse latest View live
↧

minimal down time

December 18, 2013, 8:48 am
$
0
0

We have an Exchange 2010 Server and are looking to migrate to Exchange 2013. I have setup new server and everything is working. I did move one mailbox and it does send and receive email. My concern is down time. We would like as little down time as possible.

Our exchange 2010 server has the SSL Certificate. Do I move the certificate to the new server, migrate all mailboxes and swap IP addresses on the servers?

Of do I get a new certificate for the Exchange 2013 server, migrate mailboxes, setup another mx record and add entries with Registrar and firewall?

Thank you for the assistance.

↧
Search

[Exchange 2013] Unable to start Exchange Toolbox

December 7, 2012, 4:07 am
$
0
0

Hello all,

I have installed Exchange 2013 (CAS Role) on a Windows 2008 R2 server. All the requirements where passed.

After installing and the reboot, I am unable to start the Exchange Toolbox. It gives the following error:

Unhandled Exception in Managed Code Snap-in

FX:{714FA079-DC14-470f-851C-B7EAAA4177C1}

Exception type: System.Runtime.Serialization.SerializationException

Exception stack trace:

   at Microsoft.ManagementConsole.Internal.IMessageClient.ProcessRequest(Request request)
   at Microsoft.ManagementConsole.Executive.RequestStatus.BeginRequest(IMessageClient messageClient, RequestInfo requestInfo)
   at Microsoft.ManagementConsole.Executive.SnapInRequestOperation.ProcessRequest()
   at Microsoft.ManagementConsole.Executive.Operation.OnThreadTransfer(SimpleOperationCallback callback)

Any help is appreciated and with kind regards,

Willem-Jan

↧
↧

Exchange 2013 Public Folder Migration Problem

December 18, 2013, 2:39 pm
$
0
0

Hi All,

Wonder if any of you can assist with a public folder issue I am having with Exchange 2013. We have migrated from Exchange 2010 to 2013.

I have followed the guide for public folder migration here http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx

Everything went fine and as per the document - except I had to use the "largeitemlimit" parameter to get the public folder migration to complete.

We tested the public folder migration by adding content to public folders and creating public folders and it all appeared to be OK, we completed the migration and removed our old public folder databases from Exchange 2010.

However we noticed later that users cannot CREATE folders in SOME public folders. It appears from some testing that any folder that does not lie in the first public folder mailbox, end users cannot create public folders.  Administrators can create them fine from the ECP - just not from outlook.

It also appears some users cannot see some folders that they have permissions to.

Can anyone assist with some ideas to resolve ?

Thanks.

↧

Can i change my Exchange 2003 organization to NATIVE MODE if my Front-End Exchange server is Windows 2000 Server

December 13, 2013, 12:26 pm
$
0
0

I am planing to upgrade from exchange server 2003 to exchange server 2010. I understand 2010 can co-exisist with 2003, but my 2003 organization must be in NATIVE MODE, not a problem because i don't have anymore MS Server 2000 domain controllers, they were decommisioned a few moths after we moved to AD. However my Front-End exchange server that sits on my DMZ is running Exchange server 2003 on Windows 2000 Server.

Can i change my Exchange 2003 organization to NATIVE MODE if my Front-End Exchange server is on the Windows 2000 Server OS? If not, will i have to setup a new Front-End Exchange server on at least Windows Server 2003 to replace the 2000 server setup?

It's been a very long time since these servers were configured so i may need help setting up a new Front-End server if it will be required.

thanks

B

Bobby

↧

Migrating to 2013 from 2007 with Outlook Anywhere disabled

December 19, 2013, 1:17 pm
$
0
0

Hello

I'm in the middle of a migration from 2007 With Outlook anywhere disabled.

After I installed 2013 I added the external url to both inside and outside url's on CliantAccess, o-anywhere url and Virtual catalogs.

When I configured the External Access domain on the 2013 it also added this on the external url's on the 2007 server. On the 2007 server i manuelly changed the external url's to the Legacy name which is mail.domain.com. The New server is webmail.domain.com both internally and externally. The servers real name is xxmail.domain.internal

After this, when I configure an Outlook Client With a user on the old server With autodiscover it configures it With Outlook anywhere, not mapi, but With the external name of the New server, webmail.domain.com under http Proxy settings. When I then moved this user to the New server it stopped working in Outlook.

Is the best approch to enable Outlook anywhere on the 2007 server before migrating the users or can I og from mapi/rpc to rpc over http in 2013 without Outlook problems?

Regards

↧
↧

No Access to modern Public Folders (Exchange 2013) from Windows XP

December 9, 2013, 4:41 am
$
0
0

Hi there,

i tried a lot and did a lot of research so i just want to share that information. When you try to open the Public Folders from XP Client you receive:

Windows 7 works fine.

The Mailbox it self works fine, Outlook 2007 or 2010 (patched) makes no difference, Autodisdover works fine.

Regkey for XP is allready set:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa]
"lmcompatibilitylevel"=dword:00000003

Auth is set to NTLM.

We found this:

  1. Critical: 12/4 Outlook (all version) on Windows XP cannot access Exchange 2013 CU3 modern Public Folders, when their mailbox is on 2013 CU3 server
    • Only critical if you have Windows XP clients, which many organizations still do
    • Workaround: Have users use OWA or W7+ workstation

http://blog.jasonsherry.net/2013/11/25/exchange-2010-sp3-ru3-2013-cu3-released/

-> We have a Support-Case running and ill update you.

↧

New Top Support Solutions blog

December 19, 2013, 10:16 pm
$
0
0

Hello

As part of our efforts to keep our communities informed about the most relevant content that address the top questions that we are getting in out forums and other support channels we want to introduce the new “Top Solution Content” blog (http://blogs.technet.com/b/topsupportsolutions).

In this blog you will find up-to-date and valuable information about Microsoft top support solutions for several of our popular products in the Server and Tools portfolio. You can use the tags (http://blogs.technet.com/b/topsupportsolutions/archive/tags) to easily locate the product of your preference or visit the home page to see what’s going on for the different Microsoft Enterprise and developer products. As a blog you can also subscribe to post and comments using the RSS feeds.

We hope this will reduce time and effort when you are looking for relevant content. Enjoy it!

Thanks

Microsoft Support team

↧

Exchange 2010 SP2 Update error on SBS 2011

December 18, 2012, 1:47 pm
$
0
0

hello,

I installed Exchange 2010 sp2 on a Windows sbs 2011 (german). Everything looks fine. But until the Cient Access Role Update, the Setup crashes, the error Messages is too long, to display on the Setup window, so the hole Setup crahes. In the error log, the following error is displayed:

[12.18.2012 21:08:06.0394] [1] The following 65 error(s) occurred during task execution:
[12.18.2012 21:08:06.0394] [1] 0.  ErrorRecord: Der Typ [Microsoft.Web.Administration.ServerManager] kann nicht gefunden werden. Stellen Sie sicher, dass die Assembly, die diesen Typ enthält, geladen wird.
[12.18.2012 21:08:06.0394] [1] 0.  ErrorRecord: System.Management.Automation.PSArgumentException: Der Typ [Microsoft.Web.Administration.ServerManager] kann nicht gefunden werden. Stellen Sie sicher, dass die Assembly, die diesen Typ enthält, geladen wird.
   bei System.Management.Automation.MshCommandRuntime.ThrowTerminatingError(ErrorRecord errorRecord)
[12.18.2012 21:08:06.0394] [1] [ERROR] The following error was generated when "$error.Clear(); 
          function SetConfigurationSectionAttribute([System.String]$sectionPath, [System.String]$locationPath, [System.String]$attributeName, [System.Object]$value)
          {
            $serverManager = New-Object Microsoft.Web.Administration.ServerManager;
            $configuration = $serverManager.GetApplicationHostConfiguration();
            $configurationSection = $configuration.GetSection($sectionPath, $locationPath);
            $configurationSection.GetAttribute($attributeName).Value = $value;
            $serverManager.CommitChanges();
          }

The server looks fine, Mailbox and owa are available

get-exchangeserver Show 14.2 (Build 247.5) as Version number. Is the sp 2 installed successfully?

↧
Search

how to uninstall first exchange 2013 server

December 12, 2013, 11:09 am
$
0
0
I have an existing exchange 2010 SP3 organization.  I am planning to install Exchange 2013 RTM on a production server
to try it out.
 
Can I easily uninstall the exchange 2013 completely after I am finished ? Is it just a matter of control panel/ add remove programs?

Anand_N


↧
↧

Some clients migrated from 2007 is presented with the self signed certificate in 2013

December 20, 2013, 4:55 am
$
0
0

I have migrated from 2007 to 2013. I did a couple of test migrations and on the ones with domain member computers Outlook is giving a certificate warning. The certificate they are presented with is the default self signed certificate on the 2013 server. Even though I have added a trusted public certificate to Exchange and checked of to use With IIS.

I see that the default certificate is also checked of to use With IIS and it cant be removed in ECS. Shouldnt this be removed from IIS all together when adding a New certificate? And why does some Clients gets presented With the self signed and some With the Public? For instance owa is presented With the Public cert. Also and Outlook I tested from outside the domain.

Regards

↧

Migrating Mailbox from Exchange 2003 to Exchange 2010 and suspending migration

December 20, 2013, 4:14 am
$
0
0

Hi,

If I am migrating a mailbox from Exchange 2003 to Exchange 2010 and I want to pause the migration because it is going to run into the next business day.

If I "suspend move request" will this allow the Exchange 2003 user to access their mailbox, or will the 2003 mailbox remain offline in the suspended state?

Celtic

↧

Exchange 2013/2007 coexistence: Configure Exchange 2013 directories on both 2013 CAS servers?

December 20, 2013, 9:18 am
$
0
0

I'm in the middle of setting up a Exchange 2013 and Exchange 2007 coexistence. My current Exchange architecture looks like this:

Exchange 2007

MKE Site:

Ex-CASHub01 - CAS/Hub transport

Ex-CASHub02 - CAS/Hub transport/Active Sync

Ex-MBX01 - mailbox server

Exchange 2013

LA Site:

LA-CAS01

LA-MBX01

LA-MBX02

MKE Site:

MKE-CAS01

MKE-MBX01

MKE-MBX02

Resources online I've found show that when configuring virtual directories for Exchange 2013 to provide the identity of my 2013 CAS server but I have two. Do I configure that on both 2013 CAS boxes? Also, when configuring the legacy namespace and creating the DNS records, am I to assume that I need to create 2 host A records for my 2013 CAS boxes to point to my "MAIL" record? 

Here are the online resources I'm following to guide me:

http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-3-step-by-step-exchange-2007-to-2013-migration.aspx

http://technet.microsoft.com/en-us/library/hh529912(v=exchg.150).aspx

↧

Exchange Online Protection Standalone for Exchange 2013 On-premise

July 24, 2013, 9:26 am
$
0
0

hello:

I'm about to deploy Exchange server 2013 on-premise for my company and we are going to subscribe EOP standalone. After reading the description from technethttp://technet.microsoft.com/en-us/library/jj723119(v=exchg.150).aspx , I'm confuse about how am I going to manage user.

1. Do I need to have ADFS,DirSync server ready on my local datacenter to synchronize user with EOP?

2. I just need basic spam filtering feature, will EOP work with Exchange 2013 on-premise without having ADFS & DirSync?

Thanks.

↧
↧

Recommended Active Directory version before upgrading Exchange 2003 -> 2013?

November 19, 2013, 6:31 pm
$
0
0

Hi,

We are planning an Exchange Server upgrade from 2003 -> 2013.  The directory servers are all on 2003.  I see that Exchange 2010 and 2013 will run on 2003 directory services.

Are there benefits to upgrading the domain controllers to 2008 or 2012 before we upgrade Exchange?

Thanks!

--Kent

↧

Big Headache re-installing exchange

December 20, 2013, 11:54 pm
$
0
0

I have had to re-install exchange but during install just after it installs the transport roles section 7 it hangs with the following screen. Any help please

Error:

The following error was generated when "$error.Clear();

            Write-ExchangeSetupLog -Info "Setting up FIPS configuration based on Exchange Install Path";

            $FipsDataPath = [System.IO.Path]::Combine($RoleInstallPath, "FIP-FS\Data");

            $FipsEnginesPath = [System.IO.Path]::Combine($FipsDataPath, "Engines");

            Write-ExchangeSetupLog -Info "Loading FipFs snapin";

            Add-PsSnapin Microsoft.Forefront.Filtering.Management.PowerShell -ErrorAction SilentlyContinue;

            Set-ConfigurationValue -XPath "/fs-conf:Configuration/fs-sys:Machine/fs-sys:Paths/fs-sys:TraceFile" -Value $FipsDataPath -Confirm:$false

Set-ConfigurationValue -XPath "/fs-conf:Configuration/fs-sys:Machine/fs-sys:Paths/fs-sys:Engines" -Value $FipsEnginesPath -Confirm:$false

            # Copy Microsoft Engine to Engines folder during the install

            $FipsBinPath = [System.IO.Path]::Combine($RoleInstallPath, "FIP-FS\Bin");

            $MicrosoftEngineSourcePath = [System.IO.Path]::Combine($FipsBinPath, "Engine\Microsoft");

            $MicrosoftEngineDestinationPath = [System.IO.Path]::Combine($FipsEnginesPath, "amd64\Microsoft");

            $MicrosoftEngineExists = Test-Path $MicrosoftEngineDestinationPath

            if(! $MicrosoftEngineExists)

            {

              Robocopy $MicrosoftEngineSourcePath $MicrosoftEngineDestinationPath /S /COPYALL

            }

           

          " was run: "Creating an instance of the COM component with CLSID {2DC947D7-A2DC-4276-A554-891346CE2032} from the IClassFactory failed due to the following error: 8007000e Not enough storage is available to complete this operation. (Exception from HRESULT: 0x8007000E (E_OUTOFMEMORY)).".

Error:

The following error was generated when "$error.Clear();

            Write-ExchangeSetupLog -Info "Setting up FIPS configuration based on Exchange Install Path";

            $FipsDataPath = [System.IO.Path]::Combine($RoleInstallPath, "FIP-FS\Data");

            $FipsEnginesPath = [System.IO.Path]::Combine($FipsDataPath, "Engines");

            Write-ExchangeSetupLog -Info "Loading FipFs snapin";

            Add-PsSnapin Microsoft.Forefront.Filtering.Management.PowerShell -ErrorAction SilentlyContinue;

            Set-ConfigurationValue -XPath "/fs-conf:Configuration/fs-sys:Machine/fs-sys:Paths/fs-sys:TraceFile" -Value $FipsDataPath -Confirm:$false

            Set-ConfigurationValue -XPath "/fs-conf:Configuration/fs-sys:Machine/fs-sys:Paths/fs-sys:Engines" -Value $FipsEnginesPath -Confirm:$false

            # Copy Microsoft Engine to Engines folder during the install

            $FipsBinPath = [System.IO.Path]::Combine($RoleInstallPath, "FIP-FS\Bin");

            $MicrosoftEngineSourcePath = [System.IO.Path]::Combine($FipsBinPath, "Engine\Microsoft");

            $MicrosoftEngineDestinationPath = [System.IO.Path]::Combine($FipsEnginesPath, "amd64\Microsoft");

            $MicrosoftEngineExists = Test-Path $MicrosoftEngineDestinationPath

            if(! $MicrosoftEngineExists)

            {

              Robocopy $MicrosoftEngineSourcePath $MicrosoftEngineDestinationPath /S /COPYALL

            }

           

          " was run: "Creating an instance of the COM component with CLSID {2DC947D7-A2DC-4276-A554-891346CE2032} from the IClassFactory failed due to the following error: 8007000e Not enough storage is available to complete this operation. (Exception from HRESULT: 0x8007000E (E_OUTOFMEMORY)).".

↧
Search

Advice on hybrid setup ( office 365 + on premesis )

December 20, 2013, 8:37 pm
$
0
0

Hi,

Presently we are using office 365 E2 enterprise edition in our environment

we would like to add an on-premises setup (exchange 2010 or exchange 2013)
in our organization which uses the same "abc.com" domain.

Main motto is, for users who need to access to all the features like lync,sharepoint sites etc. and large mailboxe size would be  given accounts on office 365 server ,remaining will get accounts on the on-premise exchange server. 

Hybrid setup with exchange 2010 would also be fine ,if hybrid setup with 2013 is not supported.

Any one have any advice on what would be the best setup?

Thank you.


↧

Mail Servers doesn't accept my Emails

December 15, 2013, 12:55 am
$
0
0

I am getting the following reply when sending mails to GMail:

"Our system has detected an unusual rate of unsolicited mail originating from your IP address"

I have the following setup (3 VMs):

DC (Windows 2012, 1 NIC (Private)

Exchange2013 (Windows 2012, 1 NIC (Private)

NAT (Windows 2012, 2 NICs (Private, Public)

I am able to send Emails to other servers like HushMail.com, however I couldn't receive from them

I got a domain name from Godaddy.com with the public IP.

Where exactly to put the public IP, is it in DNS, NAT or Exchange??

↧
↧

Changing Domain Controller for Exchange 2013

December 21, 2013, 1:54 pm
$
0
0

Folks

I have an Exchange 2013 running on Server 2012.

Old DC on Server 2008.

I want to decommission the 2008 server. I have build a 2012 DC and for the life of can not work out how to change the DC that my exchange box uses????

Using Set-ADServerSettings cmdlet only seems to change the server for that current session?? reboot and back to the old DC...

When I use the Se-ExchangeServer cmdlet, I get domain controller cant be found. I have set the execution policy on the dc to unrestricted and still Domain controlleer cant be found..

New dc is a GC..

Any ideas would be good.

-graham

↧

Error During Exchange 2013 Mailbox Transport Role Install On Server 2012

November 2, 2012, 6:29 am
$
0
0

I was installing Exchange 2013 on Server 2012.  The server is not a DC, but is a member of a domain with a 2008 R2 functional level, and I was logged in as a domain admin.  There has never been an Exchange instance on this domain.  I got past the prerequisite checks, and the installer showed 15 steps, so I walked away.  When I came back, I saw this:

Step 8 of 15: Mailbox role: Transport service

Error:
The following error was generated when "$error.Clear();
          $maxWait = New-TimeSpan -Minutes 8
          $timeout = Get-Date;
          $timeout = $timeout.Add($maxWait);
          $currTime = Get-Date;
          $successfullySetConfigDC = $false;

          while($currTime -le $timeout)
          {
            $setSharedCDCErrors = @();
            try
            {
              Set-SharedConfigDC -DomainController $RoleDomainController -ErrorVariable setSharedCDCErrors -ErrorAction SilentlyContinue;
              $successfullySetConfigDC = ($setSharedCDCErrors.Count -eq 0);

              if($successfullySetConfigDC)
              {
                break;
              }
              Write-ExchangeSetupLog -Info ("An error ocurred while setting shared config DC. Error: " + $setSharedCDCErrors[0]);
            }
            catch
            {
              Write-ExchangeSetupLog -Info ("An exception ocurred while setting shared config DC. Exception: " + $_.Exception.Message);
            }

            Write-ExchangeSetupLog -Info ("Waiting 30 seconds before attempting again.");
            Start-Sleep -Seconds 30;
            $currTime = Get-Date;
          }

          if( -not $successfullySetConfigDC)
          {
            Write-ExchangeSetupLog -Error "Unable to set shared config DC.";
          }
        " was run: "Unable to set shared config DC.".

The only option on the screen was exit, so I did.  I checked the start menu, and there were two new Exchange icons, but I did not click them.  I ran the installer again, and it detected an incomplete install, the only option was to click next to finish the install, so I clicked next.  This time, I eventually got the same error, except the screen showed "Step 8 of 15: Mailbox role: Transport service."  I did install some Exchange 2010 prerquisites on the server before Exchange Server 2013 came out, and I can rebuild the server and try the install again if that would be best, but I thought I should post here first and try to work through this since the product is so fresh.  Any suggestions?

↧

Autodiscover not working after exchange 2010 migration to new server

December 17, 2013, 6:39 am
$
0
0
I'm migrating from one Exchange 2010 server to another on new hardware.  I've loaded Exchange, moved mailboxes, tested connectivity, everything seems to be working.  I created new connectors on the new server and pointed my firewall to redirect emails to the new server, seems to work.

However, I'm running the Exchange connectivity tester and it's failing.  It looks like the external url for autodiscover is incorrect.  (The internal one looks fine).

This is what it is showing for the url:  https://mydomain.com/AutoDiscover/AutoDiscover.xml

This is what it should be showing:  https://mail.mydomain.com/AutoDiscover/AutoDiscover.xml

I checked nslookup for autodiscover.mydomain.com and it is pointing to the correct ip address that is being redirected by my firewall to the new exchange server.



-------------------------------------------------------------------------------------------

The Microsoft Connectivity Analyzer is testing Exchange ActiveSync.
  The Exchange ActiveSync test failed.
 
Additional Details
 
Elapsed Time: 7943 ms.
 
Test Steps
 
Attempting the Autodiscover and Exchange ActiveSync test (if requested).
  Testing of Autodiscover for Exchange ActiveSync failed.
 
Additional Details
 
Elapsed Time: 7941 ms.
 
Test Steps
 
Attempting each method of contacting the Autodiscover service.
  The Autodiscover service couldn't be contacted successfully by any method.
 
Additional Details
 
Elapsed Time: 7941 ms.
 
Test Steps
 
Attempting to test potential Autodiscover URL https://mydomain.com/AutoDiscover/AutoDiscover.xml
  Testing of this potential Autodiscover URL failed.
 
Additional Details
 
Elapsed Time: 1325 ms.
 
Test Steps
 
Attempting to resolve the host name mydomain.com in DNS.
  The host name resolved successfully.
 
Additional Details
 
IP addresses returned: 71.125.36.157
Elapsed Time: 25 ms.
Testing TCP port 443 on host mydomain.com to ensure it's listening and open.
  The specified port is either blocked, not listening, or not producing the expected response.
   Tell me more about this issue and how to resolve it
 
Additional Details
 
A network error occurred while communicating with the remote host.
Elapsed Time: 1299 ms.
Attempting to test potential Autodiscover URL https://autodiscover.mydomain.com/AutoDiscover/AutoDiscover.xml
  Testing of this potential Autodiscover URL failed.
 
Additional Details
 
Elapsed Time: 6173 ms.
 
Test Steps
 
Attempting to resolve the host name autodiscover.mydomain.com in DNS.
  The host name resolved successfully.
 
Additional Details
 
IP addresses returned: 71.125.36.155
Elapsed Time: 23 ms.
Testing TCP port 443 on host autodiscover.mydomain.com to ensure it's listening and open.
  The port was opened successfully.
 
Additional Details
 
Elapsed Time: 112 ms.
Testing the SSL certificate to make sure it's valid.
  The SSL certificate failed one or more certificate validation checks.
 
Additional Details
 
Elapsed Time: 6037 ms.
 
Test Steps
 
The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server autodiscover.mydomain.com on port 443.
  The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
 
Additional Details
 
Remote Certificate Subject: CN=MAIL.mydomain.com, Issuer: CN=mydomain-VR1-CA, DC=mydomain, DC=com.
Elapsed Time: 5960 ms.
Validating the certificate name.
  Certificate name validation failed.
   Tell me more about this issue and how to resolve it
 
Additional Details
 
Host name autodiscover.mydomain.com doesn't match any name found on the server certificate CN=MAIL.mydomain.com.
Elapsed Time: 1 ms.
Attempting to contact the Autodiscover service using the HTTP redirect method.
  The attempt to contact Autodiscover using the HTTP Redirect method failed.
 
Additional Details
 
Elapsed Time: 268 ms.
 
Test Steps
 
Attempting to resolve the host name autodiscover.mydomain.com in DNS.
  The host name resolved successfully.
 
Additional Details
 
IP addresses returned: 71.125.36.155
Elapsed Time: 24 ms.
Testing TCP port 80 on host autodiscover.mydomain.com to ensure it's listening and open.
  The port was opened successfully.
 
Additional Details
 
Elapsed Time: 112 ms.
The Microsoft Connectivity Analyzer is checking the host autodiscover.mydomain.com for an HTTP redirect to the Autodiscover service.
  The Microsoft Connectivity Analyzer failed to get an HTTP redirect response for Autodiscover.
 
Additional Details
 
An HTTP 403 forbidden response was received. The response appears to have come from Unknown. Body of the response: You do not have permission to view this directory or page.
Headers received:
Content-Length: 58
Content-Type: text/html
Date: Tue, 17 Dec 2013 13:21:08 GMT
Server: Microsoft-IIS/7.5
X-Powered-By: ASP.NET
Elapsed Time: 131 ms.
Attempting to contact the Autodiscover service using the DNS SRV redirect method.
  The Microsoft Connectivity Analyzer failed to contact the Autodiscover service using the DNS SRV redirect method.
 
Additional Details
 
Elapsed Time: 174 ms.
 
Test Steps
 
Attempting to locate SRV record _autodiscover._tcp.mydomain.com in DNS.
  The Autodiscover SRV record wasn't found in DNS.
   Tell me more about this issue and how to resolve it
 
Additional Details
 
Elapsed Time: 174 ms.
↧
Viewing all 7129 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>