Quantcast
Channel: Exchange Server 2013 - Setup, Deployment, Updates, and Migration 论坛
Viewing all 7008 articles
Browse latest View live

Migrating to 2013 from 2007 with Outlook Anywhere disabled

$
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

$
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

$
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

$
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?

how to uninstall first exchange 2013 server

$
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

$
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

$
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?

$
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

$
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.

Advice on hybrid setup ( office 365 + on premesis )

$
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.


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

$
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

minimal down time

$
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.

Mail Servers doesn't accept my Emails

$
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

$
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

$
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

$
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.

Read/Unread Emails on Mobile and Desktop

$
0
0

Hello,

I am trying to set up my account on exchange online, I have purchased Plan 1.
How do I set it up so that when I receive a message and open it on my desktop, it shows as read on my BB device, and vice-versa?

I  used to have an exchange account that linked my BB and desktop so that I could open a email on either one, and the message would be seen as read on another. It gets too confusing having the same email shown as unread.

Can anyone help me out?

Thanks

Changing domain name on Exchange 2013

$
0
0

Hi All,

Having changed the domain our 2012 AD Server is running on from domainv2.local to domain.com, in order to ensure valid wildcard SSL certificate can be used rather than a self signed with unmatched domain causing invalid SSL popups all the time, the Exchange 2013 server no longer works.  I should have looked at the implications to Exchange prior and from what I am reading there is no way to change the domain name used by Exchange as of 2003.

I currently cannot connect on EMS/ECP/OWA/Clients, and am slowly coming to terms with the fact that I will have to do a reinstall of the 2012 and exchange server on the new domain.

The current error I get on ECP is:

Server Error in '/ecp' Application.Cannot find information about the local server host.domain.com in Active Directory. This may be related to a change in the server name.
Can anyone please advise on the best procedure to follow to recover from this?  I want to keep as many settings as possible so that I can review them while installing the new server as it took some time to get it where I wanted it.

I assume that the main thing is to back up the database and the logs and then install using the same file paths.  But imagine there is a lot more that I will be able to retain if done properly.

Kind Regards,

Anthony

Error 1603 During SP2 Install

$
0
0

Greetings,

I am attempting to install SP2 for Exchange 2010 and any help would be greatly appreciated.

It is failing during the upgrade process at "Remove Exchange Files".  I had an issue where the original installation software was removed, but I downloaded SP1 and renamed the folder to match the installation directory.

The error during installation is:  

Error: Couldn't remove product with code 4934d1ea-be46-48b1-8847-f1af20e892c1.  Fatal error during installation.  Error code is 1603.

The final lines of the ExchangeSetup.log show:

/22/2013 18:52:53.0772] [0] **************
[12/22/2013 18:52:53.0772] [0] Setup will run the task 'uninstall-msipackage'
[12/22/2013 18:52:53.0772] [1] Setup launched task 'uninstall-msipackage -logfile 'C:\ExchangeSetupLogs\ExchangeSetup.msilog' -ProductCode '4934d1ea-be46-48b1-8847-f1af20e892c1' -PropertyValues 'BYPASS_CONFIGURED_CHECK=1 DEFAULTLANGUAGENAME=ENU''  
[12/22/2013 18:52:53.0788] [1] Active Directory session settings for 'Uninstall-MsiPackage' are: View Entire Forest: 'True', Configuration Domain Controller: 'servername.domain.local', Preferred Global Catalog: 'servername.domain.local', Preferred Domain Controllers: '{ servername.domain.local }'
[12/22/2013 18:52:53.0788] [1] Beginning processing uninstall-msipackage -LogFile:'C:\ExchangeSetupLogs\ExchangeSetup.msilog' -ProductCode:'4934d1ea-be46-48b1-8847-f1af20e892c1' -PropertyValues:'BYPASS_CONFIGURED_CHECK=1 DEFAULTLANGUAGENAME=ENU'
[12/22/2013 18:52:53.0819] [1] Removing MSI package with code '4934d1ea-be46-48b1-8847-f1af20e892c1'.
[12/22/2013 18:52:55.0129] [1] [ERROR] Unexpected Error
[12/22/2013 18:52:55.0129] [1] [ERROR] Couldn't remove product with code 4934d1ea-be46-48b1-8847-f1af20e892c1. Fatal error during installation. Error code is 1603.
[12/22/2013 18:52:55.0129] [1] [ERROR] Fatal error during installation
[12/22/2013 18:52:55.0270] [1] Ending processing uninstall-msipackage

The last lines from ExchangeSetup.msilog are as follows:

           ******* Product: {4934D1EA-BE46-48B1-8847-F1AF20E892C1}
           ******* Action: 
           ******* CommandLine: **********
MSI (s) (2C:38) [13:52:53:944]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (2C:38) [13:52:53:944]: Warning: Local cached package 'C:\Windows\Installer\13d51e.msi' is missing.
MSI (s) (2C:38) [13:52:53:944]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (2C:38) [13:52:53:944]: User policy value 'DisableMedia' is 0
MSI (s) (2C:38) [13:52:53:944]: Machine policy value 'AllowLockdownMedia' is 0
MSI (s) (2C:38) [13:52:53:944]: SOURCEMGMT: Media enabled only if package is safe.
MSI (s) (2C:38) [13:52:53:944]: SOURCEMGMT: Looking for sourcelist for product {4934D1EA-BE46-48B1-8847-F1AF20E892C1}
MSI (s) (2C:38) [13:52:53:944]: SOURCEMGMT: Adding {4934D1EA-BE46-48B1-8847-F1AF20E892C1}; to potential sourcelist list (pcode;disk;relpath).
MSI (s) (2C:38) [13:52:53:944]: SOURCEMGMT: Now checking product {4934D1EA-BE46-48B1-8847-F1AF20E892C1}
MSI (s) (2C:38) [13:52:53:944]: SOURCEMGMT: Media is enabled for product.
MSI (s) (2C:38) [13:52:53:944]: SOURCEMGMT: Attempting to use LastUsedSource from source list.
MSI (s) (2C:38) [13:52:53:944]: SOURCEMGMT: Trying source C:\Users\Administrator\Desktop\en_exchange_server_2010_sp1_x64_dvd_587827\.
MSI (s) (2C:38) [13:52:54:037]: Entering CMsiConfigurationManager::SetLastUsedSource.
MSI (s) (2C:38) [13:52:54:037]: Specifed source is already in a list.
MSI (s) (2C:38) [13:52:54:037]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (2C:38) [13:52:54:037]: Machine policy value 'DisableBrowse' is 0
MSI (s) (2C:38) [13:52:54:037]: Machine policy value 'AllowLockdownBrowse' is 0
MSI (s) (2C:38) [13:52:54:037]: Adding new sources is allowed.
MSI (s) (2C:38) [13:52:54:037]: Set LastUsedSource to: C:\Users\Administrator\Desktop\en_exchange_server_2010_sp1_x64_dvd_587827\.
MSI (s) (2C:38) [13:52:54:037]: Set LastUsedType to: n.
MSI (s) (2C:38) [13:52:54:037]: Set LastUsedIndex to: 1.
MSI (s) (2C:38) [13:52:54:037]: SOURCEMGMT: Resolved source to: 'C:\Users\Administrator\Desktop\en_exchange_server_2010_sp1_x64_dvd_587827\'
MSI (s) (2C:38) [13:52:54:146]: SRSetRestorePoint skipped for this transaction.
MSI (s) (2C:38) [13:52:54:178]: File will have security applied from OpCode.
MSI (s) (2C:38) [13:52:54:490]: SOFTWARE RESTRICTION POLICY: Verifying package --> 'C:\Users\Administrator\Desktop\en_exchange_server_2010_sp1_x64_dvd_587827\EXCHANGESERVER.MSI' against software restriction policy
MSI (s) (2C:38) [13:52:54:490]: SOFTWARE RESTRICTION POLICY: C:\Users\Administrator\Desktop\en_exchange_server_2010_sp1_x64_dvd_587827\EXCHANGESERVER.MSI has a digital signature
MSI (s) (2C:38) [13:52:54:708]: SOFTWARE RESTRICTION POLICY: C:\Users\Administrator\Desktop\en_exchange_server_2010_sp1_x64_dvd_587827\EXCHANGESERVER.MSI is permitted to run at the 'unrestricted' authorization level.
MSI (s) (2C:38) [13:52:54:708]: End dialog not enabled
MSI (s) (2C:38) [13:52:54:708]: Original package ==> C:\Users\Administrator\Desktop\en_exchange_server_2010_sp1_x64_dvd_587827\EXCHANGESERVER.MSI
MSI (s) (2C:38) [13:52:54:708]: Package we're running from ==> C:\Windows\Installer\8d24c.msi
MSI (s) (2C:38) [13:52:54:739]: APPCOMPAT: Uninstall Flags override found.
MSI (s) (2C:38) [13:52:54:739]: APPCOMPAT: Uninstall VersionNT override found.
MSI (s) (2C:38) [13:52:54:739]: APPCOMPAT: Uninstall ServicePackLevel override found.
MSI (s) (2C:38) [13:52:54:739]: APPCOMPAT: looking for appcompat database entry with ProductCode '{4934D1EA-BE46-48B1-8847-F1AF20E892C1}'.
MSI (s) (2C:38) [13:52:54:739]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (2C:38) [13:52:54:926]: MSCOREE not loaded loading copy from system32
MSI (s) (2C:38) [13:52:54:973]: Opening existing patch 'C:\Windows\Installer\1011c7.msp'.
MSI (s) (2C:38) [13:52:54:973]: Note: 1: 2203 2: C:\Windows\Installer\1011c7.msp 3: -2147287038 
MSI (s) (2C:38) [13:52:54:973]: Couldn't find local patch 'C:\Windows\Installer\1011c7.msp'. Looking for it at its source.
MSI (s) (2C:38) [13:52:54:973]: Resolving Patch source.
MSI (s) (2C:38) [13:52:54:973]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (2C:38) [13:52:54:973]: SOURCEMGMT: Media enabled only if package is safe.
MSI (s) (2C:38) [13:52:54:973]: SOURCEMGMT: Looking for sourcelist for product {0B5BC12B-31FF-4A4D-BF4F-B57BC45B6EBC}
MSI (s) (2C:38) [13:52:54:973]: SOURCEMGMT: Adding {0B5BC12B-31FF-4A4D-BF4F-B57BC45B6EBC}; to potential sourcelist list (pcode;disk;relpath).
MSI (s) (2C:38) [13:52:54:973]: SOURCEMGMT: Now checking product {0B5BC12B-31FF-4A4D-BF4F-B57BC45B6EBC}
MSI (s) (2C:38) [13:52:54:973]: SOURCEMGMT: Media is enabled for product.
MSI (s) (2C:38) [13:52:54:973]: SOURCEMGMT: Attempting to use LastUsedSource from source list.
MSI (s) (2C:38) [13:52:54:973]: SOURCEMGMT: Processing net source list.
MSI (s) (2C:38) [13:52:54:973]: Note: 1: 1402 2: UNKNOWN\Net 3: 2 
MSI (s) (2C:38) [13:52:54:973]: Note: 1: 1706 2: -2147483647 3: Exchange2010-KB2407028-x64-EN.MSP 
MSI (s) (2C:38) [13:52:54:973]: SOURCEMGMT: Processing media source list.
MSI (s) (2C:38) [13:52:54:973]: SOURCEMGMT: Resolved source to: 'Exchange2010-KB2407028-x64-EN.MSP'
MSI (s) (2C:38) [13:52:55:004]: Note: 1: 1314 2: Exchange2010-KB2407028-x64-EN.MSP 
MSI (s) (2C:38) [13:52:55:004]: Unable to create a temp copy of patch 'Exchange2010-KB2407028-x64-EN.MSP'.
MSI (s) (2C:38) [13:52:55:004]: Searching provided command line patches for patch code {0B5BC12B-31FF-4A4D-BF4F-B57BC45B6EBC}
MSI (s) (2C:38) [13:52:55:004]: Could not find source for missing patch {0B5BC12B-31FF-4A4D-BF4F-B57BC45B6EBC} -- orphaning this patch
MSI (s) (2C:38) [13:52:55:004]: Opening existing patch 'C:\Windows\Installer\f5fd60c.msp'.
MSI (s) (2C:38) [13:52:55:004]: Note: 1: 2203 2: C:\Windows\Installer\f5fd60c.msp 3: -2147287038 
MSI (s) (2C:38) [13:52:55:004]: Couldn't find local patch 'C:\Windows\Installer\f5fd60c.msp'. Looking for it at its source.
MSI (s) (2C:38) [13:52:55:004]: Resolving Patch source.
MSI (s) (2C:38) [13:52:55:004]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (2C:38) [13:52:55:004]: SOURCEMGMT: Media enabled only if package is safe.
MSI (s) (2C:38) [13:52:55:004]: SOURCEMGMT: Looking for sourcelist for product {49BBDF26-A486-4CC6-A67B-9CE95228A1E6}
MSI (s) (2C:38) [13:52:55:004]: SOURCEMGMT: Adding {49BBDF26-A486-4CC6-A67B-9CE95228A1E6}; to potential sourcelist list (pcode;disk;relpath).
MSI (s) (2C:38) [13:52:55:004]: SOURCEMGMT: Now checking product {49BBDF26-A486-4CC6-A67B-9CE95228A1E6}
MSI (s) (2C:38) [13:52:55:004]: SOURCEMGMT: Media is enabled for product.
MSI (s) (2C:38) [13:52:55:004]: SOURCEMGMT: Attempting to use LastUsedSource from source list.
MSI (s) (2C:38) [13:52:55:004]: SOURCEMGMT: Processing net source list.
MSI (s) (2C:38) [13:52:55:004]: Note: 1: 1402 2: UNKNOWN\Net 3: 2 
MSI (s) (2C:38) [13:52:55:004]: Note: 1: 1706 2: -2147483647 3: Exchange2010-KB2425179-x64-EN.MSP 
MSI (s) (2C:38) [13:52:55:004]: SOURCEMGMT: Processing media source list.
MSI (s) (2C:38) [13:52:55:020]: SOURCEMGMT: Resolved source to: 'Exchange2010-KB2425179-x64-EN.MSP'
MSI (s) (2C:38) [13:52:55:020]: Note: 1: 1314 2: Exchange2010-KB2425179-x64-EN.MSP 
MSI (s) (2C:38) [13:52:55:020]: Unable to create a temp copy of patch 'Exchange2010-KB2425179-x64-EN.MSP'.
MSI (s) (2C:38) [13:52:55:020]: Searching provided command line patches for patch code {49BBDF26-A486-4CC6-A67B-9CE95228A1E6}
MSI (s) (2C:38) [13:52:55:020]: Could not find source for missing patch {49BBDF26-A486-4CC6-A67B-9CE95228A1E6} -- orphaning this patch
MSI (s) (2C:38) [13:52:55:020]: Opening existing patch 'C:\Windows\Installer\5155564.msp'.
MSI (s) (2C:38) [13:52:55:020]: Note: 1: 2203 2: C:\Windows\Installer\5155564.msp 3: -2147287038 
MSI (s) (2C:38) [13:52:55:020]: Couldn't find local patch 'C:\Windows\Installer\5155564.msp'. Looking for it at its source.
MSI (s) (2C:38) [13:52:55:020]: Resolving Patch source.
MSI (s) (2C:38) [13:52:55:020]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (2C:38) [13:52:55:020]: SOURCEMGMT: Media enabled only if package is safe.
MSI (s) (2C:38) [13:52:55:020]: SOURCEMGMT: Looking for sourcelist for product {CFCC56CB-DB79-4EEE-9AAD-31BEE7E24B8C}
MSI (s) (2C:38) [13:52:55:020]: SOURCEMGMT: Adding {CFCC56CB-DB79-4EEE-9AAD-31BEE7E24B8C}; to potential sourcelist list (pcode;disk;relpath).
MSI (s) (2C:38) [13:52:55:020]: SOURCEMGMT: Now checking product {CFCC56CB-DB79-4EEE-9AAD-31BEE7E24B8C}
MSI (s) (2C:38) [13:52:55:020]: SOURCEMGMT: Media is enabled for product.
MSI (s) (2C:38) [13:52:55:020]: SOURCEMGMT: Attempting to use LastUsedSource from source list.
MSI (s) (2C:38) [13:52:55:020]: SOURCEMGMT: Processing net source list.
MSI (s) (2C:38) [13:52:55:020]: Note: 1: 1402 2: UNKNOWN\Net 3: 2 
MSI (s) (2C:38) [13:52:55:020]: Note: 1: 1706 2: -2147483647 3: Exchange2010-KB2529939-V3-x64-EN.MSP 
MSI (s) (2C:38) [13:52:55:020]: SOURCEMGMT: Processing media source list.
MSI (s) (2C:38) [13:52:55:036]: SOURCEMGMT: Resolved source to: 'Exchange2010-KB2529939-V3-x64-EN.MSP'
MSI (s) (2C:38) [13:52:55:036]: Note: 1: 1314 2: Exchange2010-KB2529939-V3-x64-EN.MSP 
MSI (s) (2C:38) [13:52:55:036]: Unable to create a temp copy of patch 'Exchange2010-KB2529939-V3-x64-EN.MSP'.
MSI (s) (2C:38) [13:52:55:036]: Searching provided command line patches for patch code {CFCC56CB-DB79-4EEE-9AAD-31BEE7E24B8C}
MSI (s) (2C:38) [13:52:55:036]: Could not find source for missing patch {CFCC56CB-DB79-4EEE-9AAD-31BEE7E24B8C} -- orphaning this patch
MSI (s) (2C:38) [13:52:55:036]: Opening existing patch 'C:\Windows\Installer\187bd522.msp'.
MSI (s) (2C:38) [13:52:55:036]: Note: 1: 2203 2: C:\Windows\Installer\187bd522.msp 3: -2147287038 
MSI (s) (2C:38) [13:52:55:036]: Couldn't find local patch 'C:\Windows\Installer\187bd522.msp'. Looking for it at its source.
MSI (s) (2C:38) [13:52:55:036]: Resolving Patch source.
MSI (s) (2C:38) [13:52:55:036]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (2C:38) [13:52:55:036]: SOURCEMGMT: Media enabled only if package is safe.
MSI (s) (2C:38) [13:52:55:036]: SOURCEMGMT: Looking for sourcelist for product {F4D6BF40-E4EF-4D52-A0EF-13A3765EAC88}
MSI (s) (2C:38) [13:52:55:036]: SOURCEMGMT: Adding {F4D6BF40-E4EF-4D52-A0EF-13A3765EAC88}; to potential sourcelist list (pcode;disk;relpath).
MSI (s) (2C:38) [13:52:55:036]: SOURCEMGMT: Now checking product {F4D6BF40-E4EF-4D52-A0EF-13A3765EAC88}
MSI (s) (2C:38) [13:52:55:036]: SOURCEMGMT: Media is enabled for product.
MSI (s) (2C:38) [13:52:55:036]: SOURCEMGMT: Attempting to use LastUsedSource from source list.
MSI (s) (2C:38) [13:52:55:036]: SOURCEMGMT: Processing net source list.
MSI (s) (2C:38) [13:52:55:036]: Note: 1: 1402 2: UNKNOWN\Net 3: 2 
MSI (s) (2C:38) [13:52:55:036]: Note: 1: 1706 2: -2147483647 3: Exchange2010-KB2579150-V2-x64-EN.MSP 
MSI (s) (2C:38) [13:52:55:036]: SOURCEMGMT: Processing media source list.
MSI (s) (2C:38) [13:52:55:051]: SOURCEMGMT: Resolved source to: 'Exchange2010-KB2579150-V2-x64-EN.MSP'
MSI (s) (2C:38) [13:52:55:051]: Note: 1: 1314 2: Exchange2010-KB2579150-V2-x64-EN.MSP 
MSI (s) (2C:38) [13:52:55:051]: Unable to create a temp copy of patch 'Exchange2010-KB2579150-V2-x64-EN.MSP'.
MSI (s) (2C:38) [13:52:55:051]: Searching provided command line patches for patch code {F4D6BF40-E4EF-4D52-A0EF-13A3765EAC88}
MSI (s) (2C:38) [13:52:55:051]: Could not find source for missing patch {F4D6BF40-E4EF-4D52-A0EF-13A3765EAC88} -- orphaning this patch
MSI (s) (2C:38) [13:52:55:051]: Opening existing patch 'C:\Windows\Installer\388caa28.msp'.
MSI (s) (2C:38) [13:52:55:051]: Note: 1: 2203 2: C:\Windows\Installer\388caa28.msp 3: -2147287038 
MSI (s) (2C:38) [13:52:55:051]: Couldn't find local patch 'C:\Windows\Installer\388caa28.msp'. Looking for it at its source.
MSI (s) (2C:38) [13:52:55:051]: Resolving Patch source.
MSI (s) (2C:38) [13:52:55:051]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (2C:38) [13:52:55:051]: SOURCEMGMT: Media enabled only if package is safe.
MSI (s) (2C:38) [13:52:55:051]: SOURCEMGMT: Looking for sourcelist for product {1FC3E0DE-4E52-4A87-8589-3DEF36D5A184}
MSI (s) (2C:38) [13:52:55:051]: SOURCEMGMT: Adding {1FC3E0DE-4E52-4A87-8589-3DEF36D5A184}; to potential sourcelist list (pcode;disk;relpath).
MSI (s) (2C:38) [13:52:55:051]: SOURCEMGMT: Now checking product {1FC3E0DE-4E52-4A87-8589-3DEF36D5A184}
MSI (s) (2C:38) [13:52:55:051]: SOURCEMGMT: Media is enabled for product.
MSI (s) (2C:38) [13:52:55:051]: SOURCEMGMT: Attempting to use LastUsedSource from source list.
MSI (s) (2C:38) [13:52:55:051]: SOURCEMGMT: Processing net source list.
MSI (s) (2C:38) [13:52:55:051]: Note: 1: 1402 2: UNKNOWN\Net 3: 2 
MSI (s) (2C:38) [13:52:55:051]: Note: 1: 1706 2: -2147483647 3: Exchange2010-KB2582113-x64-EN.MSP 
MSI (s) (2C:38) [13:52:55:051]: SOURCEMGMT: Processing media source list.
MSI (s) (2C:38) [13:52:55:067]: SOURCEMGMT: Resolved source to: 'Exchange2010-KB2582113-x64-EN.MSP'
MSI (s) (2C:38) [13:52:55:067]: Note: 1: 1314 2: Exchange2010-KB2582113-x64-EN.MSP 
MSI (s) (2C:38) [13:52:55:067]: Unable to create a temp copy of patch 'Exchange2010-KB2582113-x64-EN.MSP'.
MSI (s) (2C:38) [13:52:55:067]: Searching provided command line patches for patch code {1FC3E0DE-4E52-4A87-8589-3DEF36D5A184}
MSI (s) (2C:38) [13:52:55:067]: Could not find source for missing patch {1FC3E0DE-4E52-4A87-8589-3DEF36D5A184} -- orphaning this patch
MSI (s) (2C:38) [13:52:55:067]: Opening existing patch 'C:\Windows\Installer\42deb541.msp'.
MSI (s) (2C:38) [13:52:55:067]: Note: 1: 2203 2: C:\Windows\Installer\42deb541.msp 3: -2147287038 
MSI (s) (2C:38) [13:52:55:067]: Couldn't find local patch 'C:\Windows\Installer\42deb541.msp'. Looking for it at its source.
MSI (s) (2C:38) [13:52:55:067]: Resolving Patch source.
MSI (s) (2C:38) [13:52:55:067]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (2C:38) [13:52:55:067]: SOURCEMGMT: Media enabled only if package is safe.
MSI (s) (2C:38) [13:52:55:067]: SOURCEMGMT: Looking for sourcelist for product {0C2E937A-2A16-4364-9C73-DF990814DD48}
MSI (s) (2C:38) [13:52:55:067]: SOURCEMGMT: Adding {0C2E937A-2A16-4364-9C73-DF990814DD48}; to potential sourcelist list (pcode;disk;relpath).
MSI (s) (2C:38) [13:52:55:067]: SOURCEMGMT: Now checking product {0C2E937A-2A16-4364-9C73-DF990814DD48}
MSI (s) (2C:38) [13:52:55:067]: SOURCEMGMT: Media is enabled for product.
MSI (s) (2C:38) [13:52:55:067]: SOURCEMGMT: Attempting to use LastUsedSource from source list.
MSI (s) (2C:38) [13:52:55:067]: SOURCEMGMT: Processing net source list.
MSI (s) (2C:38) [13:52:55:067]: Note: 1: 1402 2: UNKNOWN\Net 3: 2 
MSI (s) (2C:38) [13:52:55:067]: Note: 1: 1706 2: -2147483647 3: Exchange2010-KB2608646-x64-EN.MSP 
MSI (s) (2C:38) [13:52:55:067]: SOURCEMGMT: Processing media source list.
MSI (s) (2C:38) [13:52:55:067]: SOURCEMGMT: Resolved source to: 'Exchange2010-KB2608646-x64-EN.MSP'
MSI (s) (2C:38) [13:52:55:067]: Note: 1: 1314 2: Exchange2010-KB2608646-x64-EN.MSP 
MSI (s) (2C:38) [13:52:55:067]: Unable to create a temp copy of patch 'Exchange2010-KB2608646-x64-EN.MSP'.
MSI (s) (2C:38) [13:52:55:067]: Searching provided command line patches for patch code {0C2E937A-2A16-4364-9C73-DF990814DD48}
MSI (s) (2C:38) [13:52:55:067]: Could not find source for missing patch {0C2E937A-2A16-4364-9C73-DF990814DD48} -- orphaning this patch
MSI (s) (2C:38) [13:52:55:082]: SequencePatches starts. Product code: {4934D1EA-BE46-48B1-8847-F1AF20E892C1}, Product version: 14.1.218.15, Upgrade code: {A4A259AB-A77F-4039-832A-27B431DDFFEA}, Product language 1033
MSI (s) (2C:38) [13:52:55:082]: SequencePatches returns success.
MSI (s) (2C:38) [13:52:55:082]: Final Patch Application Order:
MSI (s) (2C:38) [13:52:55:082]: Other Patches:
MSI (s) (2C:38) [13:52:55:082]: Internal Exception during install operation: 0xc0000005 at 0x000007FEFF0435E1.
MSI (s) (2C:38) [13:52:55:082]: WER report disabled for silent install.
MSI (s) (2C:38) [13:52:55:082]: WER report disabled for non-console install.
MSI (s) (2C:38) [13:52:55:082]: Internal MSI error. Installer terminated prematurely.

MSI (s) (2C:38) [13:52:55:082]: MainEngineThread is returning 1603
MSI (s) (2C:C0) [13:52:55:082]: No System Restore sequence number for this installation.
MSI (s) (2C:C0) [13:52:55:082]: User policy value 'DisableRollback' is 0
MSI (s) (2C:C0) [13:52:55:082]: Machine policy value 'DisableRollback' is 0
MSI (s) (2C:C0) [13:52:55:082]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (2C:C0) [13:52:55:082]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 
MSI (s) (2C:C0) [13:52:55:098]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 
MSI (s) (2C:C0) [13:52:55:098]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2 
MSI (s) (2C:C0) [13:52:55:098]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2 
MSI (s) (2C:C0) [13:52:55:098]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
MSI (s) (2C:C0) [13:52:55:098]: Restoring environment variables
MSI (c) (C4:68) [13:52:55:098]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
MSI (c) (C4:68) [13:52:55:098]: MainEngineThread is returning 1603
=== Verbose logging stopped: 12/22/2013  13:52:55 ===


Autodiscover sending .local address to remote users

$
0
0

We have an sbs 2011 server and are trying to use the autodiscover feature for clients that are not located in the office.  The problem we see is everything works except the exchange server address it uses is "domain.local" instead of "domain.com".  I have read a ton of blogs but cant seem to find what I need to change so the server name given to the remote users is the local name.

TIA,

Josh


TIA Josh

Viewing all 7008 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>