BPA shows domain prepped for Exchange 2007 SP1 after SP3 install

Hello,
I have a Client with a domain that is at 2003 domain functional level and 2000 forest level.
The client had Exchange 2007 SP1 and I have just upgraded it to SP3. There is one CAS, one Hub Transport, and one Mailbox Server (All three had Exchange 2007 SP1).
The domain and forest were prepped earlier by someone else and when I ran the installation program, it didn't pop up any errors on any of the servers.
The upgrade to SP3 is in preperation to Exchange 2010. Everything is working ok. I have checked:
1) In ADSIEdit, Exchange System Objects properties: Object Version =11221.
2) In ADSIEdit, Services>Microsoft Exchange>Organization: Object Version =11222
3) In ADSIEdit, RangeUpper value of ms-Exch-Schema-Version-Pt object = 14625
However, When I run the Exchange BPA, it reports that the domain is prepped for Exchange Server 2007 Service Pack 1 (In informational items). This is an informational item and not a warning or alert. However, I am concerned. Is this normal, and will it affect
the migration to Exchange 2010?
Thanks,
HA

Hello Ha20,
Based on my experience, it will not affect the migration. However, it’s recommended to prepare the schema again to avoid any potential issues.
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Similar Messages

  • Upgrade Exchange 2007 sp1 to sp3

    Good day,
    I have 3 exchange 2007 sp1 servers in my domain in different subnets. I need to upgrade all of them to sp3. i started with one branch server that is not in the same site with the domain schema master and im getting errors during instalation preparations
    that -  "    Organization Checks              ......................... FAILED
         Setup needs to contact the Active Directory schema master but this computer
     is not in the same Active Directory site as the schema master (Default-First-Si
    te-Name).
         Setup encountered a problem while validating the state of Active Directory:
     Exchange organization-level objects have not been created, and setup cannot cre
    ate them because the local computer is not in the same domain and site as the sc
    hema master.  Run setup with the /prepareAD parameter on a computer in the domai
    n toyota and site Default-First-Site-Name, and wait for replication to complete.
        Hub Transport Role Checks        ......................... FAILED
         Setup encountered a problem while validating the state of Active Directory:
     Exchange organization-level objects have not been created, and setup cannot cre
    ate them because the local computer is not in the same domain and site as the sc
    hema master.  Run setup with the /prepareAD parameter on a computer in the domai
    n toyota and site Default-First-Site-Name, and wait for replication to complete.
        Client Access Role Checks        ......................... FAILED
         Setup encountered a problem while validating the state of Active Directory:
     Exchange organization-level objects have not been created, and setup cannot cre
    ate them because the local computer is not in the same domain and site as the sc
    hema master.  Run setup with the /prepareAD parameter on a computer in the domai
    n toyota and site Default-First-Site-Name, and wait for replication to complete.
        Mailbox Role Checks              ......................... FAILED
         Setup encountered a problem while validating the state of Active Directory:
     Exchange organization-level objects have not been created, and setup cannot cre
    ate them because the local computer is not in the same domain and site as the sc
    hema master.  Run setup with the /prepareAD parameter on a computer in the domai
    n toyota and site Default-First-Site-Name, and wait for replication to complete.
    My question is do i need to first upgrade the one in the same site with the scema master? and what will happen to the other remote server in different subnets?? how will i upgrade them given these errors?
    Regards,
    Brian

    Good day,
    I have 3 exchange 2007 sp1 servers in my domain in different subnets. I need to upgrade all of them to sp3. i started with one branch server that is not in the same site with the domain schema master and im getting errors during instalation preparations
    that -  "    Organization Checks              ......................... FAILED
         Setup needs to contact the Active Directory schema master but this computer
     is not in the same Active Directory site as the schema master (Default-First-Si
    te-Name).
         Setup encountered a problem while validating the state of Active Directory:
     Exchange organization-level objects have not been created, and setup cannot cre
    ate them because the local computer is not in the same domain and site as the sc
    hema master.  Run setup with the /prepareAD parameter on a computer in the domai
    n toyota and site Default-First-Site-Name, and wait for replication to complete.
        Hub Transport Role Checks        ......................... FAILED
         Setup encountered a problem while validating the state of Active Directory:
     Exchange organization-level objects have not been created, and setup cannot cre
    ate them because the local computer is not in the same domain and site as the sc
    hema master.  Run setup with the /prepareAD parameter on a computer in the domai
    n toyota and site Default-First-Site-Name, and wait for replication to complete.
        Client Access Role Checks        ......................... FAILED
         Setup encountered a problem while validating the state of Active Directory:
     Exchange organization-level objects have not been created, and setup cannot cre
    ate them because the local computer is not in the same domain and site as the sc
    hema master.  Run setup with the /prepareAD parameter on a computer in the domai
    n toyota and site Default-First-Site-Name, and wait for replication to complete.
        Mailbox Role Checks              ......................... FAILED
         Setup encountered a problem while validating the state of Active Directory:
     Exchange organization-level objects have not been created, and setup cannot cre
    ate them because the local computer is not in the same domain and site as the sc
    hema master.  Run setup with the /prepareAD parameter on a computer in the domai
    n toyota and site Default-First-Site-Name, and wait for replication to complete.
    My question is do i need to first upgrade the one in the same site with the scema master? and what will happen to the other remote server in different subnets?? how will i upgrade them given these errors?
    Regards,
    Brian
    Prepare the domains as required. You have to prep the forest first for SP3 before upgrading Exchange itself
    Follow all the instructions
    http://technet.microsoft.com/en-us/library/bb125224(v=exchg.141).aspx
    Prepare Active Directory and Domains
    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • Exchange 2003 sp2 to exchange 2007 sp1 upgrade error

    Hi,
    We had Windows 2003 DCs and Exchange 2003 servers. We migrated AD DCs to windows 2008 R2 at parent domain.
    We have one parent domain and 10 child domains in remote sites .3 remote sites have been migrated to windows 2008 R2.
    Now at parent domain I am trying to install exchange 2007 SP1 on a server with windows 2008 R2 SP1. I am facing certain issues:
    1. When I run setup /PrepareSchema on this new exchange server , the organization check fails with error stating that : cannot find at least one DC running windows 2003 SP1 or later in DC=xyx,DC=com. This could be the result of moving DC objects in AD. Check
    that at least one DC running windows server 2003 SP1 or later is located in the "Domian Controllers" OU and rerun setup".
    2. When I try to install exchange server 2007 , I get the following error
    Object cannot be saved because its ExchangeVersion property is 0.10 (14.0.100.0), which is not supported
    by the current version 0.1 (8.0.535.0). You will need a later version of Exchange.".
    Can any one shed light on this issue.
    Regards
    Syed
    sa

    You cannot install Exchange 2007 SP1 on Windows 2008 R2 SP1 as it is unsupported.
    Only version of Exchange 2007 supported when OS is Windows 2008 R2 or R2 SP1 is Exchange 2007 SP3.
    Where are you installing Exchange ? child or parent domain ?
    2. When I try to install exchange server 2007 , I get the following error "Object
    cannot be saved because its ExchangeVersion property is 0.10 (14.0.100.0), which is not supported by the current version 0.1 (8.0.535.0). You will need a later version of Exchange.".
    Above error indicates that Exchange setup is trying to modify
    a version of an object which might have been created when organization is prepared for Exchange 2010. don't you have exchange 2010 Servers already in your environment ?
    Please give more information about your current email infrastructure
    and whether if you are installing exchange on parent or child domain?
    Pavan Maganti ~ ( Exchange | 2003/2007/2010/E15(2013)) ~~ Please remember to click “Vote As Helpful" if it really helps and "Mark as Answer” if it answers your question, “Unmark as Answer” if a marked post does not actually answer your
    question. ~~ This Information is provided is "AS IS" and confers NO Rights!!

  • Improper decoding of base64 encoded attachment on Exchange 2007 SP1

    I'm using Exchange 2007 SP1. My java application sends email to users of exchange 2007 SP1. The email contains an email as an attachment which is base64 encoded . This email when sent to users on exchange 2007 SP1 shows blank attachment. The same email when sent to users on different exchange (e.g. Exchange 2003) shows the correct attachment i.e. the attachments are not blank. While sending the mail i'm setting name of the attachment in Content-Type header but it is not there when we look at the rfc contents of the mail received on ex 2007 SP1.  It seems exchange 2007 is not able to decode the base 64 contents properly. Below are the rfc contents of the mail which show few headers in the attachment part instead of the base64 content. Please suggest some solution to it. It's urgent.
    Received: from test80.psjpr.com (192.168.0.243) by exchange01.psjpr.com
     (192.168.0.138) with Microsoft SMTP Server id 8.1.263.0; Fri, 11 Apr 2008
     18:53:12 +0530
    From: Admin <[email protected]>
    To: test test1 <[email protected]>
    Date: Fri, 11 Apr 2008 18:53:12 +0530
    Subject: Retrieved from : testingggggg
    Thread-Topic: Retrieved from : testingggggg
    Thread-Index: Acib1zFeboxSL6S4RuaeI0AaCou0pQ==
    Message-ID: <[email protected]>
    Accept-Language: en-US
    Content-Language: en-US
    X-MS-Exchange-Organization-AuthAs: Anonymous
    X-MS-Exchange-Organization-AuthSource: exchange01.psjpr.com
    X-MS-Has-Attach: yes
    X-MS-TNEF-Correlator:
    Content-Type: multipart/mixed;
     boundary="_002_9c2e5956bc9b49efbbc61a358f61698bexchange01psjprcom_"
    MIME-Version: 1.0
    --_002_9c2e5956bc9b49efbbc61a358f61698bexchange01psjprcom_
    Content-Type: text/plain; charset="iso-8859-1"
    Content-Transfer-Encoding: quoted-printable
    The message you requested is attached.
    --_002_9c2e5956bc9b49efbbc61a358f61698bexchange01psjprcom_
    Content-Type: message/rfc822
    Subject:
    Thread-Index: Acib1zFexS+KMQAOSD+lcMut076Wyg==
    Accept-Language: en-US
    X-MS-Has-Attach:
    X-MS-TNEF-Correlator:
    Content-Type: text/plain; charset="us-ascii"
    Content-Transfer-Encoding: quoted-printable
    MIME-Version: 1.0
    --_002_9c2e5956bc9b49efbbc61a358f61698bexchange01psjprcom_--

    Did you ever this to work ?

  • Receive Connector stopped working after Update Rollout 2 for Exchange 2007 SP2

    One of the Exchange 2007 servers receive connector has stopped working since installing the latest rollout update for Exchange 2007 SP2 - for some reason the following error is received (when troubleshooting on the adjacent server) :
    "Remote server server.domain.co.uk failed the mail acceptance test. MAIL FROM command: Respond = 530 5.7.1 Client was not authenticated."
    Most admins will know you usually get this when first setting up Exchange and the receive connector not allowing anonymous connections. But our setup has been working for well over a year with no problems. Even enabling anonymous connections still doesn't fix the problem.
    Our setup is 2 exchange servers across 2 sites, with the problematic server never receiving email from the internet, only from the other Exchange server (which is internet facing). The above error is received when the internet facing server is relaying email over to the problematic server. Though in the message queue the following error is received:
    "SMTPSEND.DNS.NonExistantDomain; nonecistant domain"
    After testing DNS that all seems fine, so I don't believe it's a DNS problem.
    Any ideas why this would happen?
    Thanks,
    Matt

    Hi Matt....
    To receive e-mails from the external servers or domains or clients, you can setup a new receive connector on Hub Transport Server. To do this task, you can go through the steps mentioned in this blog....
    https://mailsolutions.wordpress.com/2015/02/06/resolving-error-530-5-7-1-client-was-not-authenticated-with-receiver-connector/
    Hope this will work
    Thanks

  • Legacy Namespace for Exchange 2007 to 2013 co-existence

    We are migrating from Exchange 2007 to 2013, during the co-existence phase, where is the legacy.{domain.com} namespace used? We are at the point now that we want to move all services over to the Exchange 2013 CAS servers, however... GPO settings
    are used to point outlook clients to mail.{domain.com} for Outlook Anywhere. If DNS is updated to point mail.{domain.com} to the Exchange 2013 servers, will there be an issue with connectivity for people still on the Exchange 2007 servers? Do these people
    need to point to legacy.{Domain.com} or will mail.{domain.com} proxy the connection to the legacy namespace? I would like to know if the GPO settings will interfer with the settings that Autodiscovery provide back.
    I have read a bunch or articles on the approach, but I am still fuzzy on where legacy.{domain.com} comes into play.
    Thanks in advance for your help.

    In coexistence with exchange 2013 and legacy version the request happens in 2 types.
    For Exchange 2010 –
    Exchange 2013 does a Proxy for owa and ews requests for users in exchange 2010.
    For Exchange 2007 –
    Exchange 2013 does redirection for owa and ews requests for users in Exchange 2007.
    Certificates:
    All the required SAN entries for UM,webservices and activesync should be created.
    Add external owa legacy URL to the public certificate and install it on both Exchange 2007 and
    Exchange 2013 only then owa redirection will work.
    You need to Include internal Legacy. Domain.com on Exchange 2007 Certificate for OWA co-
    Existence.
    Following change needs to be done in Firewall
    External OWA URL should be directed to exchange 2013 Internet Facing CAS.
    External EWS URL should be directed to  exchange 2013 Internet Facing CAS.
    External Autodiscover URL should should be directed to  Exchange 2013 CAS.
    External ActivesyncVirtualDirectory should be directed to Exchange 2013 CAS.
    External UMvirtualDirectory should be directed to  Exchange 2013 CAS.
    Create new NAT rule on firewall for Legacy.domain.com to Exchange 2007 CAS. You can do this as well.By doing this users will be able to log on directly using the URL https://legacy.domain.com/owa with
    a mailbox on Exchange 2007.
    External and Internal DNS settings
    Public DNS - Map all of your external public DNS records (ews,owa,activesync etc.,) to your
    exchange 2013 public IP if you have dedicated one for 2013 or FQDN of your internet facing CAS server.
    Example:
    Current external owa URL (contoso.domain.com) – point it to dedicated exchange 2013 public ip or internet facing exchange 2013 CAS FQDN.
    Current External Autodiscover – point it to dedicated exchange 2013 public ip or internet
    facing exchange 2013 CAS FQDN
    Internal DNS – Configure the Exchange 2007 to point SCP AutoDiscoverURI to Exchange 2013 Client
    Access FQDN by changing DNS entry for Autodiscover.domain.com to exchange 2013 CAS sever Ip
    address
    The internal DNS records should point to the internal host name and IP address of your Exchange
    2013 Client Access server
    Make sure that legacy.contoso.com resolves to CAS2007 in internal and external DNS.
    Authentication Settings:
    This part is little bit tricky. You need to plan according to your organization. If you have FBA configured in TMG or ISA server then you need to configure accordingly.
    Set the owa virtual directory authentication only to  Basic in exchange 2007.
    In exchange 2013 set owa virtual directory to only (Windows Authentication) or only (form-based authentication) or only (Basic, No redirection, SSL Enabled) depends according to your setup.
    Things to check:
    If you have redirection configured in IIS on the Exchange 2007 Server Make sure that the above
    Virtual Directories doesn’t have it configured.
    If you have FBA enabled on ISA or TMG then disable FBA on Exchange 2013 CAS else users will be prompted twice for authentication
    For further references you can refer my article below
    http://exchangequery.com/2014/09/24/owaews-configuration-in-exchange-20132007-coexistence/
    Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com Thanks Sathish (MVP)

  • Migrating Exchange 2007 SP1 to Exchange 2013

    Follow the Exchange Deployment Assistant to the letter and you will not have issues.http://technet.microsoft.com/en-ca/exdeploy2013/Checklist.aspxAnd my guide:You need to make sure your OutlookAnywhere and AutoDiscover settings are setup properly along with Split-DNS. OutlookAnywhere and Split-DNS are vital for future-proofing your Exchange configuration and making it work properly now, regardless if you use Exchange 2007, 2010, or 2013. For Exchange 2013, OutlookAnywhere is a requirement and Split-DNS is Best Practice. If you are on Exchange 2007 or 2010, and you do not have OutlookAnywhere enabled, enable OutlookAnywhere and follow this guide.You should always use NTLM over Basic authentication, as Basic sends the username and password in the clear, and NTLM is Windows Authentication. On Exchange 2013, you also have a new option...

    This is a slightly daunting task I must admit. I am migrating an old exchange 2007 SP1 installation over to 2013 SP1 and looking for good advice and/or tips. I am finding the whole thing slightly unnerving as there seems to be about a million caveats give or take a few thousand. There seems to be about the same amount of tips, tricks and guides as well, but sadly they are not quite consistent and some are down right contradicting each other.I'm reading similar questions here on spiceworks, and it seems like I'm reading about one horrible episode after another. By now, I assume most have migrated already, so I though I might pick some brains and figure out the best way to do this ;)Might software like CodeTwo Exchange Migration or Dell Migration Manager be a good idea? Are there maybe similar tools available as well?Any feedback is very...
    This topic first appeared in the Spiceworks Community

  • GroupWise 7.0 API Gateway is supported for Exchange 2007?

    Can someone confirm that GroupWise 7.0 API Gateway is supported for Exchange 2007?
    I found a note in a guide that stated it was not YET supported as of 1/27/2008.

    bwalker2,
    It appears that in the past few days you have not received a response to your
    posting. That concerns us, and has triggered this automated reply.
    Has your problem been resolved? If not, you might try one of the following options:
    - Visit http://support.novell.com and search the knowledgebase and/or check all
    the other self support options and support programs available.
    - You could also try posting your message again. Make sure it is posted in the
    correct newsgroup. (http://forums.novell.com)
    Be sure to read the forum FAQ about what to expect in the way of responses:
    http://support.novell.com/forums/faq_general.html
    If this is a reply to a duplicate posting, please ignore and accept our apologies
    and rest assured we will issue a stern reprimand to our posting bot.
    Good luck!
    Your Novell Product Support Forums Team
    http://support.novell.com/forums/

  • OWA Blank Logon Page After Update Rollup 12 for Exchange 2007 SP3

    Hello
    After installing Update Rollup 12 for Exchange 2007 SP3, can no longer access OWA - internally or externally through Internet Explorer -  I just get a blank page (with IE). If I use Chrome or Firefox, and it uses the basic logon, I get a page with just
    text, and am able to logon successfully. I have looked at several related forums, but have not found a fix yet. I've seen several people with similar issue have had success by copying contents from a previous owa folder version to the latest one, then running
    Updateowa.ps1 and restarting IIS. This did not resolve the issue for me.
    Another forum suggested running remove-owavirtualdirectory and
    new-owavirtualdirectory, however I haven't attempted that yet, as I'm unsure how I could reverse the changes that the command runs if things get worse.
    Any assistance will be appreciated.

    Hi,
    I encountered a same situation,after recreating
    the virtual directory, the issue was solved.
    The following article for you reference:
    How To: Recreate OWA Virtual Directory – Exchange 2007
    Hope this helps!
    Thanks.
    Niko Cheng
    TechNet Community Support

  • Upgrading from Exchange 2007 SP2 to SP3 stops and fails with Performance Counter

    We are upgrading from Exchange 2007 SP2 to SP3.
    Exchange Server is on Windows 2008 Enterprise 64 bit OS -SP2
    DC is on windows 2008 Enterprise 32 bit OS - SP2
    When we run Exchange SP3 setup.exe GUI, it runs through the pre-requisites completely and then starts to configure the Hub Transport services but @ exactly 55% it throws an error window "Exchange Server Setup encountered an error"
    On repeating this process i noticed it throws the same error at 55% while "Performance COunter Configuring". Please find below the entries of exchangesetup.log
    [2/1/2015 1:09:30 PM] [0] **********************************************
    [2/1/2015 1:09:30 PM] [0] Starting Microsoft Exchange 2007 Setup
    [2/1/2015 1:09:30 PM] [0] **********************************************
    [2/1/2015 1:09:30 PM] [0] Operating System version: Microsoft Windows NT 6.0.6002 Service Pack 2.
    [2/1/2015 1:09:30 PM] [0] Setup version: 8.3.83.6.
    [2/1/2015 1:09:30 PM] [0] Logged on user: chakfig\Administrator.
    [2/1/2015 1:09:30 PM] [0] Command Line Parameter Name='mode', Value='Upgrade'.
    [2/1/2015 1:09:30 PM] [0] Command Line Parameter Name='sourcedir', Value='J:\EXSP01\SP3'.
    [2/1/2015 1:09:30 PM] [0] Command Line Parameter Name='fromsetup', Value=''.
    [2/1/2015 1:09:30 PM] [0] ExSetupUI was started with the following command: '-mode:upgrade -sourcedir:J:\EXSP01\SP3 /FromSetup'.
    [2/1/2015 1:09:30 PM] [0] Setup is choosing the domain controller to use
    [2/1/2015 1:09:31 PM] [0] Setup is choosing a local domain controller...
    [2/1/2015 1:09:35 PM] [0] Setup has chosen the local domain controller PGCDC.chakfig.local for initial queries
    [2/1/2015 1:09:35 PM] [0] PrepareAD has been run, and has replicated to this domain controller; so setup will use PGCDC.chakfig.local
    [2/1/2015 1:09:35 PM] [0] Setup is choosing a global catalog...
    [2/1/2015 1:09:35 PM] [0] Setup has chosen the global catalog server PGCDC.chakfig.local.
    [2/1/2015 1:09:35 PM] [0] Setup will use the domain controller 'PGCDC.chakfig.local'.
    [2/1/2015 1:09:35 PM] [0] Setup will use the global catalog 'PGCDC.chakfig.local'.
    [2/1/2015 1:09:35 PM] [0] Exchange configuration container for the organization is 'CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=chakfig,DC=local'.
    [2/1/2015 1:09:35 PM] [0] Exchange organization container for the organization is 'CN=chakfig,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=chakfig,DC=local'.
    [2/1/2015 1:09:35 PM] [0] Setup will search for an Exchange Server object for the local machine with name 'PGCVMEXG'.
    [2/1/2015 1:09:35 PM] [0] Exchange Server object found : 'CN=PGCVMEXG,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=chakfig,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=chakfig,DC=local'.
    [2/1/2015 1:09:35 PM] [0] The following roles are unpacked: BridgeheadRole ClientAccessRole MailboxRole AdminToolsRole 
    [2/1/2015 1:09:35 PM] [0] The following roles are installed: BridgeheadRole ClientAccessRole MailboxRole AdminToolsRole 
    [2/1/2015 1:09:35 PM] [0] The local server has some Exchange files installed.
    [2/1/2015 1:09:35 PM] [0] Setup will use the path 'J:\EXSP01\SP3' for installing Exchange.
    [2/1/2015 1:09:35 PM] [0] Setup will discover the installed roles from server object 'CN=PGCVMEXG,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=chakfig,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=chakfig,DC=local'.
    [2/1/2015 1:09:35 PM] [0] 'BridgeheadRole' is installed on the server object.
    [2/1/2015 1:09:35 PM] [0] 'ClientAccessRole' is installed on the server object.
    [2/1/2015 1:09:35 PM] [0] 'MailboxRole' is installed on the server object.
    [2/1/2015 1:09:35 PM] [0] The server is cluster type: 'None'.
    [2/1/2015 1:09:35 PM] [0] The requested cluster type: 'None'.
    [2/1/2015 1:09:35 PM] [0] The installation mode is set to: 'BuildToBuildUpgrade'.
    [2/1/2015 1:09:35 PM] [0] An Exchange organization with name 'chakfig' was found in this forest.
    [2/1/2015 1:09:35 PM] [0] Active Directory Initialization status : 'True'.
    [2/1/2015 1:09:35 PM] [0] Schema Update Required Status : 'False'.
    [2/1/2015 1:09:35 PM] [0] Organization Configuration Update Required Status : 'False'.
    [2/1/2015 1:09:35 PM] [0] Domain Configuration Update Required Status : 'False'.
    [2/1/2015 1:09:35 PM] [0] The locally installed version is 8.3.83.6.
    [2/1/2015 1:09:35 PM] [0] Exchange Installation Directory : 'C:\Program Files\Microsoft\Exchange Server'.
    [2/1/2015 1:09:35 PM] [0] The backup copy of the install path is 'C:\Program Files\Microsoft\Exchange Server'.
    [2/1/2015 1:09:35 PM] [0] The backup copy of the previously installed version is '8.2.176.2'.
    [2/1/2015 1:09:36 PM] [0] Setup is determining what organization-level operations to perform.
    [2/1/2015 1:09:36 PM] [0] Because the value was specified, setup is setting the argument OrganizationName to the value chakfig.
    [2/1/2015 1:09:36 PM] [0] The installed .msi file is current for this version of setup.
    [2/1/2015 1:09:36 PM] [0] RootDataHandler has 1 DataHandlers
    [2/1/2015 1:12:38 PM] [0] End of Setup
    [2/1/2015 1:12:38 PM] [0] **********************************************
    [2/1/2015 2:17:36 PM] [0] **********************************************
    [2/1/2015 2:17:36 PM] [0] Starting Microsoft Exchange 2007 Setup
    [2/1/2015 2:17:36 PM] [0] **********************************************
    [2/1/2015 2:17:36 PM] [0] Operating System version: Microsoft Windows NT 6.0.6002 Service Pack 2.
    [2/1/2015 2:17:36 PM] [0] Setup version: 8.3.83.6.
    [2/1/2015 2:17:36 PM] [0] Logged on user: chakfig\Administrator.
    [2/1/2015 2:17:37 PM] [0] Command Line Parameter Name='mode', Value='Upgrade'.
    [2/1/2015 2:17:37 PM] [0] Command Line Parameter Name='sourcedir', Value='J:\EXSP01\SP3'.
    [2/1/2015 2:17:37 PM] [0] Command Line Parameter Name='fromsetup', Value=''.
    [2/1/2015 2:17:37 PM] [0] ExSetupUI was started with the following command: '-mode:upgrade -sourcedir:J:\EXSP01\SP3 /FromSetup'.
    [2/1/2015 2:17:41 PM] [0] Setup is choosing the domain controller to use
    [2/1/2015 2:17:41 PM] [0] Setup is choosing a local domain controller...
    [2/1/2015 2:17:43 PM] [0] Setup has chosen the local domain controller PGCDC.chakfig.local for initial queries
    [2/1/2015 2:17:43 PM] [0] PrepareAD has been run, and has replicated to this domain controller; so setup will use PGCDC.chakfig.local
    [2/1/2015 2:17:43 PM] [0] Setup is choosing a global catalog...
    [2/1/2015 2:17:43 PM] [0] Setup has chosen the global catalog server PGCDC.chakfig.local.
    [2/1/2015 2:17:43 PM] [0] Setup will use the domain controller 'PGCDC.chakfig.local'.
    [2/1/2015 2:17:43 PM] [0] Setup will use the global catalog 'PGCDC.chakfig.local'.
    [2/1/2015 2:17:43 PM] [0] Exchange configuration container for the organization is 'CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=chakfig,DC=local'.
    [2/1/2015 2:17:43 PM] [0] Exchange organization container for the organization is 'CN=chakfig,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=chakfig,DC=local'.
    [2/1/2015 2:17:43 PM] [0] Setup will search for an Exchange Server object for the local machine with name 'PGCVMEXG'.
    [2/1/2015 2:17:43 PM] [0] Exchange Server object found : 'CN=PGCVMEXG,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=chakfig,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=chakfig,DC=local'.
    [2/1/2015 2:17:43 PM] [0] The following roles are unpacked: BridgeheadRole ClientAccessRole MailboxRole AdminToolsRole 
    [2/1/2015 2:17:43 PM] [0] The following roles are installed: BridgeheadRole ClientAccessRole MailboxRole AdminToolsRole 
    [2/1/2015 2:17:43 PM] [0] The local server has some Exchange files installed.
    [2/1/2015 2:17:43 PM] [0] Setup will use the path 'J:\EXSP01\SP3' for installing Exchange.
    [2/1/2015 2:17:43 PM] [0] Setup will discover the installed roles from server object 'CN=PGCVMEXG,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=chakfig,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=chakfig,DC=local'.
    [2/1/2015 2:17:43 PM] [0] 'BridgeheadRole' is installed on the server object.
    [2/1/2015 2:17:43 PM] [0] 'ClientAccessRole' is installed on the server object.
    [2/1/2015 2:17:43 PM] [0] 'MailboxRole' is installed on the server object.
    [2/1/2015 2:17:43 PM] [0] The server is cluster type: 'None'.
    [2/1/2015 2:17:43 PM] [0] The requested cluster type: 'None'.
    [2/1/2015 2:17:43 PM] [0] The installation mode is set to: 'BuildToBuildUpgrade'.
    [2/1/2015 2:17:43 PM] [0] An Exchange organization with name 'chakfig' was found in this forest.
    [2/1/2015 2:17:43 PM] [0] Active Directory Initialization status : 'True'.
    [2/1/2015 2:17:43 PM] [0] Schema Update Required Status : 'False'.
    [2/1/2015 2:17:43 PM] [0] Organization Configuration Update Required Status : 'False'.
    [2/1/2015 2:17:43 PM] [0] Domain Configuration Update Required Status : 'False'.
    [2/1/2015 2:17:43 PM] [0] The locally installed version is 8.3.83.6.
    [2/1/2015 2:17:43 PM] [0] Exchange Installation Directory : 'C:\Program Files\Microsoft\Exchange Server'.
    [2/1/2015 2:17:43 PM] [0] The backup copy of the install path is 'C:\Program Files\Microsoft\Exchange Server'.
    [2/1/2015 2:17:43 PM] [0] The backup copy of the previously installed version is '8.2.176.2'.
    [2/1/2015 2:17:43 PM] [0] Setup is determining what organization-level operations to perform.
    [2/1/2015 2:17:43 PM] [0] Because the value was specified, setup is setting the argument OrganizationName to the value chakfig.
    [2/1/2015 2:17:43 PM] [0] The installed .msi file is current for this version of setup.
    [2/1/2015 2:17:43 PM] [0] RootDataHandler has 1 DataHandlers
    [2/1/2015 2:17:47 PM] [0] Validating options for the 4 requested roles
    [2/1/2015 2:17:47 PM] [0] UpgradeModeDataHandler has 5 handlers and 5 work units
    [2/1/2015 2:17:52 PM] [0] Validating options for the 4 requested roles
    [2/1/2015 2:17:52 PM] [0] UpgradeModeDataHandler has 5 handlers and 5 work units
    [2/1/2015 2:17:53 PM] [0] **************
    [2/1/2015 2:17:53 PM] [0] Setup will run the task 'test-setuphealth'
    [2/1/2015 2:17:53 PM] [1] Setup launched task 'test-setuphealth -DomainController 'PGCDC.chakfig.local' -DownloadConfigurationUpdates $true -ExchangeVersion '8.3.83.6' -Roles 'Bridgehead' -ScanType 'PrecheckUpgrade' -SetupRoles 'Bridgehead','ClientAccess','Mailbox','AdminTools'
    -TargetDir 'C:\Program Files\Microsoft\Exchange Server''  
    [2/1/2015 2:17:53 PM] [1] Beginning processing.
    [2/1/2015 2:18:19 PM] [1] Beginning processing.
    [2/1/2015 2:18:19 PM] [1] Administrator Active Directory session settings are:  View Entire Forest: 'True', Configuration Domain Controller: 'PGCDC.chakfig.local', Preferred Global Catalog: 'PGCDC.chakfig.local', Preferred Domain Controllers: '{ PGCDC.chakfig.local
    [2/1/2015 2:18:19 PM] [1] Searching objects "PGCVMEXG" of type "Server" under the root "$null".
    [2/1/2015 2:18:19 PM] [1] Previous operation run on domain controller 'PGCDC.chakfig.local'.
    [2/1/2015 2:18:19 PM] [1] Previous operation run on domain controller 'PGCDC.chakfig.local'.
    [2/1/2015 2:18:19 PM] [1] Preparing to output objects. Maximum result set size "unlimited".
    [2/1/2015 2:18:20 PM] [1] Ending processing.
    [2/1/2015 2:18:20 PM] [1] Beginning processing.
    [2/1/2015 2:18:20 PM] [1] Administrator Active Directory session settings are:  View Entire Forest: 'True', Configuration Domain Controller: 'PGCDC.chakfig.local', Preferred Global Catalog: 'PGCDC.chakfig.local', Preferred Domain Controllers: '{ PGCDC.chakfig.local
    [2/1/2015 2:18:20 PM] [1] Searching objects of type "SmtpSendConnectorConfig" with filter "$null", scope "SubTree" under the root "Administrative Groups".
    [2/1/2015 2:18:20 PM] [1] Previous operation run on domain controller 'PGCDC.chakfig.local'.
    [2/1/2015 2:18:20 PM] [1] Preparing to output objects. Maximum result set size "unlimited".
    [2/1/2015 2:18:20 PM] [1] Ending processing.
    [2/1/2015 2:18:20 PM] [1] Ending processing.
    [2/1/2015 2:18:20 PM] [0] **************
    [2/1/2015 2:18:20 PM] [0] Setup will run the task 'test-setuphealth'
    [2/1/2015 2:18:20 PM] [1] Setup launched task 'test-setuphealth -DomainController 'PGCDC.chakfig.local' -DownloadConfigurationUpdates $false -ExchangeVersion '8.3.83.6' -Roles 'ClientAccess' -ScanType 'PrecheckUpgrade' -SetupRoles 'Bridgehead','ClientAccess','Mailbox','AdminTools'
    -TargetDir 'C:\Program Files\Microsoft\Exchange Server' -IISInstalled $true'  
    [2/1/2015 2:18:20 PM] [1] Beginning processing.
    [2/1/2015 2:18:26 PM] [1] Beginning processing.
    [2/1/2015 2:18:26 PM] [1] Administrator Active Directory session settings are:  View Entire Forest: 'True', Configuration Domain Controller: 'PGCDC.chakfig.local', Preferred Global Catalog: 'PGCDC.chakfig.local', Preferred Domain Controllers: '{ PGCDC.chakfig.local
    [2/1/2015 2:18:55 PM] [1] Searching objects of type "SmtpSendConnectorConfig" with filter "$null", scope "SubTree" under the root "Administrative Groups".
    [2/1/2015 2:18:55 PM] [1] Previous operation run on domain controller 'PGCDC.chakfig.local'.
    [2/1/2015 2:18:55 PM] [1] Preparing to output objects. Maximum result set size "unlimited".
    [2/1/2015 2:18:55 PM] [1] Ending processing.
    [2/1/2015 2:18:55 PM] [1] Ending processing.
    [2/1/2015 2:18:55 PM] [0] **************
    [2/1/2015 2:18:55 PM] [0] Setup will run the task 'test-setuphealth'
    [2/1/2015 2:18:55 PM] [1] Setup launched task 'test-setuphealth -DomainController 'PGCDC.chakfig.local' -DownloadConfigurationUpdates $false -ExchangeVersion '8.3.83.6' -Roles 'ClientAccess' -ScanType 'PrecheckUpgrade' -SetupRoles 'Bridgehead','ClientAccess','Mailbox','AdminTools'
    -TargetDir 'C:\Program Files\Microsoft\Exchange Server' -IISInstalled $true'  
    [2/1/2015 2:18:55 PM] [1] Beginning processing.
    [2/1/2015 2:19:01 PM] [1] Beginning processing.
    [2/1/2015 2:19:01 PM] [1] Administrator Active Directory session settings are:  View Entire Forest: 'True', Configuration Domain Controller: 'PGCDC.chakfig.local', Preferred Global Catalog: 'PGCDC.chakfig.local', Preferred Domain Controllers: '{ PGCDC.chakfig.local
    [2/1/2015 2:19:01 PM] [1] Searching objects "PGCVMEXG" of type "Server" under the root "$null".
    [2/1/2015 2:19:01 PM] [1] Previous operation run on domain controller 'PGCDC.chakfig.local'.
    [2/1/2015 2:19:01 PM] [1] Previous operation run on domain controller 'PGCDC.chakfig.local'.
    [2/1/2015 2:19:01 PM] [1] Preparing to output objects. Maximum result set size "unlimited".
    [2/1/2015 2:19:01 PM] [1] Ending processing.
    [2/1/2015 2:19:01 PM] [1] Ending processing.
    [2/1/2015 2:19:01 PM] [0] **************
    [2/1/2015 2:19:01 PM] [0] Setup will run the task 'test-setuphealth'
    [2/1/2015 2:19:01 PM] [1] Setup launched task 'test-setuphealth -DomainController 'PGCDC.chakfig.local' -DownloadConfigurationUpdates $false -ExchangeVersion '8.3.83.6' -Roles 'Mailbox' -ScanType 'PrecheckUpgrade' -SetupRoles 'Bridgehead','ClientAccess','Mailbox','AdminTools'
    -TargetDir 'C:\Program Files\Microsoft\Exchange Server' -IISInstalled $true'  
    [2/1/2015 2:19:01 PM] [1] Beginning processing.
    [2/1/2015 2:19:04 PM] [1] Beginning processing.
    [2/1/2015 2:19:04 PM] [1] Ending processing.
    [2/1/2015 2:19:07 PM] [1] Beginning processing.
    [2/1/2015 2:19:07 PM] [1] Administrator Active Directory session settings are:  View Entire Forest: 'True', Configuration Domain Controller: 'PGCDC.chakfig.local', Preferred Global Catalog: 'PGCDC.chakfig.local', Preferred Domain Controllers: '{ PGCDC.chakfig.local
    [2/1/2015 2:19:07 PM] [1] Searching objects "PGCVMEXG" of type "Server" under the root "$null".
    [2/1/2015 2:19:07 PM] [1] Previous operation run on domain controller 'PGCDC.chakfig.local'.
    [2/1/2015 2:19:07 PM] [1] Previous operation run on domain controller 'PGCDC.chakfig.local'.
    [2/1/2015 2:19:07 PM] [1] Preparing to output objects. Maximum result set size "unlimited".
    [2/1/2015 2:19:07 PM] [1] Ending processing.
    [2/1/2015 2:19:08 PM] [1] Ending processing.
    [2/1/2015 2:19:20 PM] [0] Setup is determining what organization-level operations to perform.
    [2/1/2015 2:19:20 PM] [0] Because the value was specified, setup is setting the argument OrganizationName to the value chakfig.
    [2/1/2015 2:19:20 PM] [0] The installed .msi file is current for this version of setup.
    [2/1/2015 2:19:20 PM] [0] RootDataHandler has 1 DataHandlers
    [2/1/2015 2:19:20 PM] [0] **************
    [2/1/2015 2:19:20 PM] [0] Setup will run the task 'Install-BridgeheadRole'
    [2/1/2015 2:19:20 PM] [1] Setup launched task 'Install-BridgeheadRole -DomainController 'PGCDC.chakfig.local' -UpdatesDir 'J:\EXSP01\SP3\Updates''  
    [2/1/2015 2:19:20 PM] [1] Beginning processing.
    [2/1/2015 2:19:20 PM] [1] Attempting Install for BridgeheadRole.
    [2/1/2015 2:19:20 PM] [1] The following roles are current: 
    [2/1/2015 2:19:26 PM] [1] Reading components for role 'BridgeheadRole' from 'res://BridgeheadRoleDefinition.xml'
    [2/1/2015 2:19:26 PM] [1] Found 22 components
    [2/1/2015 2:19:26 PM] [1] Loaded component 'All Roles Common First - Run Once' with 10 task info blocks from 'res://AllRolesCommonFirst_RunOnce.xml'
    [2/1/2015 2:19:26 PM] [1] Loaded component 'All Roles Common First' with 8 task info blocks from 'res://AllRolesCommonFirst.xml'
    [2/1/2015 2:19:27 PM] [1] Loaded component 'All Roles Precompile Management Binaries' with 30 task info blocks from 'res://AllRolesPrecompileManagementBinaries.xml'
    [2/1/2015 2:19:27 PM] [1] Loaded component 'Bridgehead Permissions Configuration' with 1 task info blocks from 'res://BridgeheadLocalPermissionsComponent.xml'
    [2/1/2015 2:19:27 PM] [1] Loaded component 'Common Perf Counters ' with 2 task info blocks from 'res://CommonPerfCountersComponent.xml'
    [2/1/2015 2:19:27 PM] [1] Loaded component 'Provision Server' with 9 task info blocks from 'res://ProvisionServerComponent.xml'
    [2/1/2015 2:19:28 PM] [1] Loaded component 'All Active-Directory Roles Common' with 14 task info blocks from 'res://AllADRolesCommon.xml'
    [2/1/2015 2:19:28 PM] [1] Loaded component 'Exchange 2003 Pseudo-MTA Configuration' with 1 task info blocks from 'res://LegacyMTAComponent.xml'
    [2/1/2015 2:19:28 PM] [1] Loaded component 'Exchange 2003 SMTP VSI Configuration' with 1 task info blocks from 'res://LegacySMTPComponent.xml'
    [2/1/2015 2:19:29 PM] [1] Loaded component 'Transport Perf Counters' with 21 task info blocks from 'res://TransportPerfCountersComponent.xml'
    [2/1/2015 2:19:29 PM] [1] Loaded component 'Enable RPC-EPMAP firewall exception' with 1 task info blocks from 'res://RpcEpmapFirewallException.xml'
    [2/1/2015 2:19:29 PM] [1] Loaded component 'Bridgehead Role Setter' with 1 task info blocks from 'res://BridgeheadRoleSetterComponent.xml'
    [2/1/2015 2:19:29 PM] [1] Loaded component 'Transport Common Configuration' with 22 task info blocks from 'res://TransportCommonComponent.xml'
    [2/1/2015 2:19:30 PM] [1] Loaded component 'Bridgehead Perf Counters' with 8 task info blocks from 'res://BridgeheadPerfCountersComponent.xml'
    [2/1/2015 2:19:30 PM] [1] Loaded component 'Bridgehead Configuration' with 18 task info blocks from 'res://BridgeheadComponent.xml'
    [2/1/2015 2:19:30 PM] [1] Loaded component 'Transport Log Search Service' with 1 task info blocks from 'res://TransportLogSearchServiceComponent.xml'
    [2/1/2015 2:19:31 PM] [1] Loaded component 'Data Storage Configuration' with 1 task info blocks from 'res://DataStorageComponent.xml'
    [2/1/2015 2:19:31 PM] [1] Loaded component 'Monitoring Service Configuration' with 5 task info blocks from 'res://MonitoringComponent.xml'
    [2/1/2015 2:19:31 PM] [1] Loaded component 'Active Directory Topology Service Configuration' with 2 task info blocks from 'res://AllADRolesCommonServiceControl.xml'
    [2/1/2015 2:19:31 PM] [1] Loaded component 'Bridgehead Service Configuration' with 3 task info blocks from 'res://BridgeheadServiceControl.xml'
    [2/1/2015 2:19:32 PM] [1] Loaded component 'Transport Common Service Control' with 1 task info blocks from 'res://TransportCommonServiceControl.xml'
    [2/1/2015 2:19:32 PM] [1] Loaded component 'All Roles Common Last' with 4 task info blocks from 'res://AllRolesCommonLast.xml'
    [2/1/2015 2:19:32 PM] [1] The following roles are installed: BridgeheadRole ClientAccessRole MailboxRole AdminToolsRole 
    [2/1/2015 2:19:32 PM] [1] Writing informational script to 'C:\ExchangeSetupLogs\Install-BridgeheadRole-20150201-1419320497.ps1'
    [2/1/2015 2:19:32 PM] [1] Executing '$RoleIsClusterNode = $False', handleError = False
    [2/1/2015 2:19:32 PM] [2] Launching sub-task '$error.Clear(); $RoleIsClusterNode = $False'.
    [2/1/2015 2:19:32 PM] [1] Executing '$RoleRoles = "BridgeheadRole,ClientAccessRole,MailboxRole,AdminToolsRole"', handleError = False
    [2/1/2015 2:19:32 PM] [2] Launching sub-task '$error.Clear(); $RoleRoles = "BridgeheadRole,ClientAccessRole,MailboxRole,AdminToolsRole"'.
    [2/1/2015 2:19:32 PM] [1] Executing '$RoleIsAdminToolsRoleInstalled = $True', handleError = False
    [2/1/2015 2:19:32 PM] [2] Launching sub-task '$error.Clear(); $RoleIsAdminToolsRoleInstalled = $True'.
    [2/1/2015 2:19:32 PM] [1] Executing '$RoleNetBIOSName = "pgcvmexg"', handleError = False
    [2/1/2015 2:19:32 PM] [2] Launching sub-task '$error.Clear(); $RoleNetBIOSName = "pgcvmexg"'.
    [2/1/2015 2:19:32 PM] [1] Executing '$RoleInvocationID = "20150201-1419320497"', handleError = False
    [2/1/2015 2:19:32 PM] [2] Launching sub-task '$error.Clear(); $RoleInvocationID = "20150201-1419320497"'.
    [2/1/2015 2:19:32 PM] [1] Executing '$RoleInstallPath = "C:\Program Files\Microsoft\Exchange Server\"', handleError = False
    [2/1/2015 2:19:32 PM] [2] Launching sub-task '$error.Clear(); $RoleInstallPath = "C:\Program Files\Microsoft\Exchange Server\"'.
    [2/1/2015 2:19:32 PM] [1] Executing '$RoleStartTransportService = $True', handleError = False
    [2/1/2015 2:19:32 PM] [2] Launching sub-task '$error.Clear(); $RoleStartTransportService = $True'.
    [2/1/2015 2:19:32 PM] [1] Executing '$RoleLoggedOnUser = "chakfig\Administrator"', handleError = False
    [2/1/2015 2:19:32 PM] [2] Launching sub-task '$error.Clear(); $RoleLoggedOnUser = "chakfig\Administrator"'.
    [2/1/2015 2:19:32 PM] [1] Executing '$RoleInstallationMode = "BuildToBuildUpgrade"', handleError = False
    [2/1/2015 2:19:32 PM] [2] Launching sub-task '$error.Clear(); $RoleInstallationMode = "BuildToBuildUpgrade"'.
    [2/1/2015 2:19:32 PM] [1] Executing '$RolePreviousVersion = "8.2.176.2"', handleError = False
    [2/1/2015 2:19:32 PM] [2] Launching sub-task '$error.Clear(); $RolePreviousVersion = "8.2.176.2"'.
    [2/1/2015 2:19:32 PM] [1] Executing '$RoleIsMailboxRoleInstalled = $True', handleError = False
    [2/1/2015 2:19:32 PM] [2] Launching sub-task '$error.Clear(); $RoleIsMailboxRoleInstalled = $True'.
    [2/1/2015 2:19:32 PM] [1] Executing '$RoleBinPath = "C:\Program Files\Microsoft\Exchange Server\Bin"', handleError = False
    [2/1/2015 2:19:32 PM] [2] Launching sub-task '$error.Clear(); $RoleBinPath = "C:\Program Files\Microsoft\Exchange Server\Bin"'.
    [2/1/2015 2:19:32 PM] [1] Executing '$RoleSetupLoggingPath = "C:\ExchangeSetupLogs"', handleError = False
    [2/1/2015 2:19:32 PM] [2] Launching sub-task '$error.Clear(); $RoleSetupLoggingPath = "C:\ExchangeSetupLogs"'.
    [2/1/2015 2:19:32 PM] [1] Executing '$RoleFqdnOrName = "pgcvmexg"', handleError = False
    [2/1/2015 2:19:32 PM] [2] Launching sub-task '$error.Clear(); $RoleFqdnOrName = "pgcvmexg"'.
    [2/1/2015 2:19:32 PM] [1] Executing '$RoleTargetVersion = "8.3.83.6"', handleError = False
    [2/1/2015 2:19:32 PM] [2] Launching sub-task '$error.Clear(); $RoleTargetVersion = "8.3.83.6"'.
    [2/1/2015 2:19:32 PM] [1] Executing '$RoleUpdatesDir = "J:\EXSP01\SP3\Updates"', handleError = False
    [2/1/2015 2:19:32 PM] [2] Launching sub-task '$error.Clear(); $RoleUpdatesDir = "J:\EXSP01\SP3\Updates"'.
    [2/1/2015 2:19:32 PM] [1] Executing '$RoleIsClientAccessRoleInstalled = $True', handleError = False
    [2/1/2015 2:19:32 PM] [2] Launching sub-task '$error.Clear(); $RoleIsClientAccessRoleInstalled = $True'.
    [2/1/2015 2:19:32 PM] [1] Executing '$RoleRoleName = "BridgeheadRole"', handleError = False
    [2/1/2015 2:19:32 PM] [2] Launching sub-task '$error.Clear(); $RoleRoleName = "BridgeheadRole"'.
    [2/1/2015 2:19:32 PM] [1] Executing '$RoleDomainController = "PGCDC.chakfig.local"', handleError = False
    [2/1/2015 2:19:32 PM] [2] Launching sub-task '$error.Clear(); $RoleDomainController = "PGCDC.chakfig.local"'.
    [2/1/2015 2:19:32 PM] [1] Executing '$RoleProductPlatform = "amd64"', handleError = False
    [2/1/2015 2:19:32 PM] [2] Launching sub-task '$error.Clear(); $RoleProductPlatform = "amd64"'.
    [2/1/2015 2:19:32 PM] [1] Executing '$RoleIsBridgeheadRoleInstalled = $True', handleError = False
    [2/1/2015 2:19:32 PM] [2] Launching sub-task '$error.Clear(); $RoleIsBridgeheadRoleInstalled = $True'.
    [2/1/2015 2:19:32 PM] [1] Executing '$RoleLoggingPath = "C:\Program Files\Microsoft\Exchange Server\Logging"', handleError = False
    [2/1/2015 2:19:32 PM] [2] Launching sub-task '$error.Clear(); $RoleLoggingPath = "C:\Program Files\Microsoft\Exchange Server\Logging"'.
    [2/1/2015 2:19:32 PM] [1] Found 136 tasks to execute
    [2/1/2015 2:19:32 PM] [1] Processing component 'All Roles Common First - Run Once' (Configuring the server.).
    [2/1/2015 2:19:32 PM] [1] Executing 'if ($RoleProductPlatform -eq "amd64") { $watsonMSI = 'dw20sharedamd64.msi'; $watsonMSILogFileName = 'Installdw20sharedamd64.msilog'; } else { $watsonMSI = 'dw20shared.msi'; $watsonMSILogFileName = 'Installdw20shared.msilog';
    } install-MsiPackage -PackagePath ($RoleInstallPath + "bin\$watsonMSI") -LogFile ($RoleSetupLoggingPath + "\$watsonMSILogFileName") -UpdatesDir $RoleUpdatesDir -PropertyValues ("APPGUID=`"{24B2C164-DE66-44fe-B468-A46D9D5E6B31}`"
    LOGVERBOSE=1");', handleError = False
    [2/1/2015 2:19:32 PM] [2] Launching sub-task '$error.Clear(); if ($RoleProductPlatform -eq "amd64") { $watsonMSI = 'dw20sharedamd64.msi'; $watsonMSILogFileName = 'Installdw20sharedamd64.msilog'; } else { $watsonMSI = 'dw20shared.msi'; $watsonMSILogFileName
    = 'Installdw20shared.msilog'; } install-MsiPackage -PackagePath ($RoleInstallPath + "bin\$watsonMSI") -LogFile ($RoleSetupLoggingPath + "\$watsonMSILogFileName") -UpdatesDir $RoleUpdatesDir -PropertyValues ("APPGUID=`"{24B2C164-DE66-44fe-B468-A46D9D5E6B31}`"
    LOGVERBOSE=1");'.
    [2/1/2015 2:19:32 PM] [2] Beginning processing.
    [2/1/2015 2:19:33 PM] [2] ProductCode is '95120000-00b9-0409-1000-0000000ff1ce'.
    [2/1/2015 2:19:33 PM] [2] PackagePath was set to 'C:\Program Files\Microsoft\Exchange Server\bin\dw20sharedamd64.msi'; normalizing to 'C:\Program Files\Microsoft\Exchange Server\bin\dw20sharedamd64.msi'.
    [2/1/2015 2:19:33 PM] [2] ProductCode is '95120000-00b9-0409-1000-0000000ff1ce'.
    [2/1/2015 2:19:33 PM] [2] Installing MSI package 'C:\Program Files\Microsoft\Exchange Server\bin\dw20sharedamd64.msi'.
    [2/1/2015 2:19:34 PM] [2] Ending processing.
    [2/1/2015 2:19:34 PM] [1] Executing 'Set-InstallPathInAppConfig -ConfigFileRelativePath "Scripts\" -ConfigFileName "Exchange2007.xml" -ReplacementString "%ProgramFiles%\Microsoft\Exchange Server\";', handleError = False
    [2/1/2015 2:19:34 PM] [2] Launching sub-task '$error.Clear(); Set-InstallPathInAppConfig -ConfigFileRelativePath "Scripts\" -ConfigFileName "Exchange2007.xml" -ReplacementString "%ProgramFiles%\Microsoft\Exchange Server\";'.
    [2/1/2015 2:19:34 PM] [2] Beginning processing.
    [2/1/2015 2:19:34 PM] [2] Ending processing.
    [2/1/2015 2:19:34 PM] [1] Executing 'Remove-XmlNode -XmlFileRelativePath "Scripts\" -XmlFileName "Exchange2007.xml" -XmlNodeNameToRemove "_locDefinition";', handleError = False
    [2/1/2015 2:19:34 PM] [2] Launching sub-task '$error.Clear(); Remove-XmlNode -XmlFileRelativePath "Scripts\" -XmlFileName "Exchange2007.xml" -XmlNodeNameToRemove "_locDefinition";'.
    [2/1/2015 2:19:34 PM] [2] Beginning processing.
    [2/1/2015 2:19:34 PM] [2] ExchangeInstallPath = C:\Program Files\Microsoft\Exchange Server\, Relative Path = Scripts\, Xml Full File Path = C:\Program Files\Microsoft\Exchange Server\Scripts\Exchange2007.xml, Xml Node Name = _locDefinition
    [2/1/2015 2:19:34 PM] [2] Ending processing.
    [2/1/2015 2:19:34 PM] [1] Executing 'Set-InstallPathInAppConfig -ConfigFileRelativePath "Scripts\" -ConfigFileName "Exchange2007Edge.xml" -ReplacementString "%ProgramFiles%\Microsoft\Exchange Server\";', handleError = False
    [2/1/2015 2:19:34 PM] [2] Launching sub-task '$error.Clear(); Set-InstallPathInAppConfig -ConfigFileRelativePath "Scripts\" -ConfigFileName "Exchange2007Edge.xml" -ReplacementString "%ProgramFiles%\Microsoft\Exchange Server\";'.
    [2/1/2015 2:19:34 PM] [2] Beginning processing.
    [2/1/2015 2:19:34 PM] [2] Ending processing.
    [2/1/2015 2:19:34 PM] [1] Executing 'Remove-XmlNode -XmlFileRelativePath "Scripts\" -XmlFileName "Exchange2007Edge.xml" -XmlNodeNameToRemove "_locDefinition";', handleError = False
    [2/1/2015 2:19:34 PM] [2] Launching sub-task '$error.Clear(); Remove-XmlNode -XmlFileRelativePath "Scripts\" -XmlFileName "Exchange2007Edge.xml" -XmlNodeNameToRemove "_locDefinition";'.
    [2/1/2015 2:19:34 PM] [2] Beginning processing.
    [2/1/2015 2:19:34 PM] [2] ExchangeInstallPath = C:\Program Files\Microsoft\Exchange Server\, Relative Path = Scripts\, Xml Full File Path = C:\Program Files\Microsoft\Exchange Server\Scripts\Exchange2007Edge.xml, Xml Node Name = _locDefinition
    [2/1/2015 2:19:34 PM] [2] Ending processing.
    [2/1/2015 2:19:34 PM] [1] Executing 'Set-InstallPathInAppConfig -ConfigFileRelativePath "Scripts\" -ConfigFileName "Exchange2007_WinSrv2008.xml" -ReplacementString "%ProgramFiles%\Microsoft\Exchange Server\";', handleError = False
    [2/1/2015 2:19:34 PM] [2] Launching sub-task '$error.Clear(); Set-InstallPathInAppConfig -ConfigFileRelativePath "Scripts\" -ConfigFileName "Exchange2007_WinSrv2008.xml" -ReplacementString "%ProgramFiles%\Microsoft\Exchange Server\";'.
    [2/1/2015 2:19:34 PM] [2] Beginning processing.
    [2/1/2015 2:19:34 PM] [2] Ending processing.
    [2/1/2015 2:19:34 PM] [1] Executing 'Remove-XmlNode -XmlFileRelativePath "Scripts\" -XmlFileName "Exchange2007_WinSrv2008.xml" -XmlNodeNameToRemove "_locDefinition";', handleError = False
    [2/1/2015 2:19:34 PM] [2] Launching sub-task '$error.Clear(); Remove-XmlNode -XmlFileRelativePath "Scripts\" -XmlFileName "Exchange2007_WinSrv2008.xml" -XmlNodeNameToRemove "_locDefinition";'.
    [2/1/2015 2:19:34 PM] [2] Beginning processing.
    [2/1/2015 2:19:34 PM] [2] ExchangeInstallPath = C:\Program Files\Microsoft\Exchange Server\, Relative Path = Scripts\, Xml Full File Path = C:\Program Files\Microsoft\Exchange Server\Scripts\Exchange2007_WinSrv2008.xml, Xml Node Name = _locDefinition
    [2/1/2015 2:19:34 PM] [2] Ending processing.
    [2/1/2015 2:19:34 PM] [1] Executing 'Set-InstallPathInAppConfig -ConfigFileRelativePath "Scripts\" -ConfigFileName "Exchange2007Edge_WinSrv2008.xml" -ReplacementString "%ProgramFiles%\Microsoft\Exchange Server\";', handleError
    = False
    [2/1/2015 2:19:34 PM] [2] Launching sub-task '$error.Clear(); Set-InstallPathInAppConfig -ConfigFileRelativePath "Scripts\" -ConfigFileName "Exchange2007Edge_WinSrv2008.xml" -ReplacementString "%ProgramFiles%\Microsoft\Exchange Server\";'.
    [2/1/2015 2:19:34 PM] [2] Beginning processing.
    [2/1/2015 2:19:34 PM] [2] Ending processing.
    [2/1/2015 2:19:34 PM] [1] Executing 'Remove-XmlNode -XmlFileRelativePath "Scripts\" -XmlFileName "Exchange2007Edge_WinSrv2008.xml" -XmlNodeNameToRemove "_locDefinition";', handleError = False
    [2/1/2015 2:19:34 PM] [2] Launching sub-task '$error.Clear(); Remove-XmlNode -XmlFileRelativePath "Scripts\" -XmlFileName "Exchange2007Edge_WinSrv2008.xml" -XmlNodeNameToRemove "_locDefinition";'.
    [2/1/2015 2:19:34 PM] [2] Beginning processing.
    [2/1/2015 2:19:34 PM] [2] ExchangeInstallPath = C:\Program Files\Microsoft\Exchange Server\, Relative Path = Scripts\, Xml Full File Path = C:\Program Files\Microsoft\Exchange Server\Scripts\Exchange2007Edge_WinSrv2008.xml, Xml Node Name = _locDefinition
    [2/1/2015 2:19:34 PM] [2] Ending processing.
    [2/1/2015 2:19:34 PM] [1] Executing 'Set-WERRegistryMarkers;', handleError = False
    [2/1/2015 2:19:34 PM] [2] Launching sub-task '$error.Clear(); Set-WERRegistryMarkers;'.
    [2/1/2015 2:19:34 PM] [2] Beginning processing.
    [2/1/2015 2:19:34 PM] [2] Ending processing.
    [2/1/2015 2:19:35 PM] [1] Processing component 'All Roles Common First' (Creating the Exchange server configuration in the Active Directory).
    [2/1/2015 2:19:35 PM] [1] Executing '$RoleNames = $RoleRoles.Replace('Role','').Split(','); .\ServiceControl.ps1 EnableServices $RoleNames', handleError = False
    [2/1/2015 2:19:35 PM] [2] Launching sub-task '$error.Clear(); $RoleNames = $RoleRoles.Replace('Role','').Split(','); .\ServiceControl.ps1 EnableServices $RoleNames'.
    [2/1/2015 2:19:35 PM] [1] Executing 'Set-LocalPermissions', handleError = False
    [2/1/2015 2:19:35 PM] [2] Launching sub-task '$error.Clear(); Set-LocalPermissions'.
    [2/1/2015 2:19:35 PM] [2] Beginning processing.
    [2/1/2015 2:19:49 PM] [2] Ending processing.
    [2/1/2015 2:19:49 PM] [1] Executing 'get-service | where { $_.Name -ieq "HealthService" } | stop-service -Force:$true', handleError = False
    [2/1/2015 2:19:49 PM] [2] Launching sub-task '$error.Clear(); get-service | where { $_.Name -ieq "HealthService" } | stop-service -Force:$true'.
    [2/1/2015 2:19:49 PM] [1] Executing 'get-service | where { $_.Name -ieq "MOM" } | stop-service -Force:$true', handleError = False
    [2/1/2015 2:19:49 PM] [2] Launching sub-task '$error.Clear(); get-service | where { $_.Name -ieq "MOM" } | stop-service -Force:$true'.
    [2/1/2015 2:19:49 PM] [1] Executing 'get-service | where { $_.Name -ieq "OnePoint" } | stop-service -Force:$true', handleError = False
    [2/1/2015 2:19:49 PM] [2] Launching sub-task '$error.Clear(); get-service | where { $_.Name -ieq "OnePoint" } | stop-service -Force:$true'.
    [2/1/2015 2:19:49 PM] [1] Executing '$mofFilePath = ($RoleInstallPath + "bin\Exchange.MOF"); $mflFilePath = ($RoleInstallPath + "bin\Exchange.MFL"); compile-moffile -MofFilePath:$mofFilePath; compile-moffile -MofFilePath:$mflFilePath;',
    handleError = True
    [2/1/2015 2:19:49 PM] [2] Launching sub-task '$error.Clear(); $mofFilePath = ($RoleInstallPath + "bin\Exchange.MOF"); $mflFilePath = ($RoleInstallPath + "bin\Exchange.MFL"); compile-moffile -MofFilePath:$mofFilePath; compile-moffile
    -MofFilePath:$mflFilePath;'.
    [2/1/2015 2:19:49 PM] [2] Beginning processing.
    [2/1/2015 2:19:49 PM] [2] Exchange tracing provider was installed successfully.
    [2/1/2015 2:19:49 PM] [2] Ending processing.
    [2/1/2015 2:19:49 PM] [2] Beginning processing.
    [2/1/2015 2:19:49 PM] [2] Exchange tracing provider was installed successfully.
    [2/1/2015 2:19:49 PM] [2] Ending processing.
    [2/1/2015 2:19:49 PM] [1] Processing component 'All Roles Precompile Management Binaries' (Pre-compiling management binaries.).
    [2/1/2015 2:19:49 PM] [1] Executing '$fullPath = [System.IO.Path]::Combine($RoleInstallPath, "bin\microsoft.Exchange.Rpc.dll"); precompile-ManagedBinary -BinaryName $fullPath;', handleError = False
    [2/1/2015 2:19:49 PM] [2] Launching sub-task '$error.Clear(); $fullPath = [System.IO.Path]::Combine($RoleInstallPath, "bin\microsoft.Exchange.Rpc.dll"); precompile-ManagedBinary -BinaryName $fullPath;'.
    [2/1/2015 2:19:49 PM] [2] Beginning processing.
    [2/1/2015 2:19:49 PM] [2] Starting: C:\Windows\Microsoft.NET\Framework64\v2.0.50727\ngen.exe arguments: install "C:\Program Files\Microsoft\Exchange Server\bin\microsoft.Exchange.Rpc.dll" /verbose
    [2/1/2015 2:19:50 PM] [2] Process standard output: Microsoft (R) CLR Native Image Generator - Version 2.0.50727.4252
    Copyright (c) Microsoft Corporation.  All rights reserved.
    Installing assembly C:\Program Files\Microsoft\Exchange Server\bin\microsoft.Exchange.Rpc.dll
    All compilation targets are up to date.
    [2/1/2015 2:19:50 PM] [2] Process standard error: 
    [2/1/2015 2:19:50 PM] [2] Ending processing.
    [2/1/2015 2:19:50 PM] [1] Executing '$fullPath = [System.IO.Path]::Combine($RoleInstallPath, "bin\microsoft.Exchange.Common.IL.dll"); precompile-ManagedBinary -BinaryName $fullPath;', handleError = False
    [2/1/2015 2:19:50 PM] [2] Launching sub-task '$error.Clear(); $fullPath = [System.IO.Path]::Combine($RoleInstallPath, "bin\microsoft.Exchange.Common.IL.dll"); precompile-ManagedBinary -BinaryName $fullPath;'.
    [2/1/2015 2:19:50 PM] [2] Beginning processing.
    [2/1/2015 2:19:50 PM] [2] Starting: C:\Windows\Microsoft.NET\Framework64\v2.0.50727\ngen.exe arguments: install "C:\Program Files\Microsoft\Exchange Server\bin\microsoft.Exchange.Common.IL.dll" /verbose
    [2/1/2015 2:19:50 PM] [2] Process standard output: Microsoft (R) CLR Native Image Generator - Version 2.0.50727.4252
    Copyright (c) Microsoft Corporation.  All rights reserved.
    Installing assembly C:\Program Files\Microsoft\Exchange Server\bin\microsoft.Exchange.Common.IL.dll
    All compilation targets are up to date.
    [2/1/2015 2:19:50 PM] [2] Process standard error: 
    [2/1/2015 2:19:50 PM] [2] Ending processing.
    [2/1/2015 2:19:50 PM] [1] Executing '$fullPath = [System.IO.Path]::Combine($RoleInstallPath, "bin\Microsoft.Exchange.Diagnostics.dll"); precompile-ManagedBinary -BinaryName $fullPath;', handleError = False
    [2/1/2015 2:19:50 PM] [2] Launching sub-task '$error.Clear(); $fullPath = [System.IO.Path]::Combine($RoleInstallPath, "bin\Microsoft.Exchange.Diagnostics.dll"); precompile-ManagedBinary -BinaryName $fullPath;'.
    [2/1/2015 2:19:50 PM] [2] Beginning processing.
    [2/1/2015 2:19:50 PM] [2] Starting: C:\Windows\Microsoft.NET\Framework64\v2.0.50727\ngen.exe arguments: install "C:\Program Files\Microsoft\Exchange Server\bin\Microsoft.Exchange.Diagnostics.dll" /verbose
    [2/1/2015 2:19:51 PM] [2] Process standard output: Microsoft (R) CLR Native Image Generator - Version 2.0.50727.4252
    Copyright (c) Microsoft Corporation.  All rights reserved.
    Installing assembly C:\Program Files\Microsoft\Exchange Server\bin\Microsoft.Exchange.Diagnostics.dll
    All compilation targets are up to date.
    [2/1/2015 2:19:51 PM] [2] Process standard error: 
    [2/1/2015 2:19:51 PM] [2] Ending processing
    [2/1/2015 2:20:07 PM] [2] Process standard error: 
    [2/1/2015 2:20:07 PM] [2] Ending processing.
    [2/1/2015 2:20:07 PM] [1] Executing '$fullPath = [System.IO.Path]::Combine($RoleInstallPath, "bin\Microsoft.Exchange.PowerShell.configuration.dll"); precompile-ManagedBinary -BinaryName $fullPath;', handleError = False
    [2/1/2015 2:20:07 PM] [2] Launching sub-task '$error.Clear(); $fullPath = [System.IO.Path]::Combine($RoleInstallPath, "bin\Microsoft.Exchange.PowerShell.configuration.dll"); precompile-ManagedBinary -BinaryName $fullPath;'.
    [2/1/2015 2:20:07 PM] [2] Beginning processing.
    [2/1/2015 2:20:07 PM] [2] Starting: C:\Windows\Microsoft.NET\Framework64\v2.0.50727\ngen.exe arguments: install "C:\Program Files\Microsoft\Exchange Server\bin\Microsoft.Exchange.PowerShell.configuration.dll" /verbose
    [2/1/2015 2:20:10 PM] [2] Process standard output: Microsoft (R) CLR Native Image Generator - Version 2.0.50727.4252
    Copyright (c) Microsoft Corporation.  All rights reserved.
    Installing assembly C:\Program Files\Microsoft\Exchange Server\bin\Microsoft.Exchange.PowerShell.configuration.dll
    All compilation targets are up to date.
    [2/1/2015 2:20:10 PM] [2] Process standard error: 
    [2/1/2015 2:20:10 PM] [2] Ending processing.
    [2/1/2015 2:20:10 PM] [1] Executing '$fullPath = [System.IO.Path]::Combine($RoleInstallPath, "bin\Microsoft.Exchange.Management.SnapIn.Esm.dll"); precompile-ManagedBinary -BinaryName $fullPath;', handleError = False
    [2/1/2015 2:20:10 PM] [2] Launching sub-task '$error.Clear(); $fullPath = [System.IO.Path]::Combine($RoleInstallPath, "bin\Microsoft.Exchange.Management.SnapIn.Esm.dll"); precompile-ManagedBinary -BinaryName $fullPath;'.
    [2/1/2015 2:20:10 PM] [2] Beginning processing.
    [2/1/2015 2:20:10 PM] [2] Starting: C:\Windows\Microsoft.NET\Framework64\v2.0.50727\ngen.exe arguments: install "C:\Program Files\Microsoft\Exchange Server\bin\Microsoft.Exchange.Management.SnapIn.Esm.dll" /verbose
    [2/1/2015 2:20:12 PM] [2] Process standard output: Microsoft (R) CLR Native Image Generator - Version 2.0.50727.4252
    Copyright (c) Microsoft Corporation.  All rights reserved.
    Installing assembly C:\Program Files\Microsoft\Exchange Server\bin\Microsoft.Exchange.Management.SnapIn.Esm.dll
    All compilation targets are up to date.
    [2/1/2015 2:20:12 PM] [2] Process standard error: 
    [2/1/2015 2:20:12 PM] [2] Ending processing.
    [2/1/2015 2:20:12 PM] [1] Processing component 'Bridgehead Permissions Configuration' (Setting folder and registry permissions).
    [2/1/2015 2:20:12 PM] [1] Executing 'Set-LocalPermissions -Feature:"Bridgehead"', handleError = False
    [2/1/2015 2:20:12 PM] [2] Launching sub-task '$error.Clear(); Set-LocalPermissions -Feature:"Bridgehead"'.
    [2/1/2015 2:20:12 PM] [2] Beginning processing.
    [2/1/2015 2:20:12 PM] [2] Ending processing.
    [2/1/2015 2:20:12 PM] [1] Processing component 'Common Perf Counters ' (Configuring performance counters).
    [2/1/2015 2:20:12 PM] [1] Executing 'new-perfcounters -DefinitionFileName ExchangeTopologyPerformanceCounters.xml', handleError = True
    [2/1/2015 2:20:12 PM] [2] Launching sub-task '$error.Clear(); new-perfcounters -DefinitionFileName ExchangeTopologyPerformanceCounters.xml'.
    [2/1/2015 2:20:12 PM] [2] Beginning processing.
    [2/1/2015 2:20:12 PM] [2] Processing file: C:\Program Files\Microsoft\Exchange Server\Setup\Perf\ExchangeTopologyPerformanceCounters.xml
    [2/1/2015 2:20:12 PM] [2] Performance counter name is Latest Exchange Topology Discovery Time in Seconds, type is NumberOfItems32.
    [2/1/2015 2:20:12 PM] [2] Performance counter name is Number of Exchange Topology Discoveries, type is NumberOfItems32.
    [2/1/2015 2:20:12 PM] [2] Performance counter name is Number of Siteless Servers, type is NumberOfItems32.
    Appreciate if someone can help us move forward in this scenario.
    We have
    1. disabled anti virus and tried.
    2. removed watermarks and action entries in the registry
    3. tried almost everything mentioned on google but i am not able to move forward.
    Please help. we need this as part of our migration to Exchange 2013 for co-existence.
    Thank you.
    Philip

    ExchangeSetup.log (part 3)
    [2/2/2015 8:06:45 PM] [1] Executing '$RoleSetupLoggingPath = "C:\ExchangeSetupLogs"', handleError = False
    [2/2/2015 8:06:45 PM] [2] Launching sub-task '$error.Clear(); $RoleSetupLoggingPath = "C:\ExchangeSetupLogs"'.
    [2/2/2015 8:06:45 PM] [1] Executing '$RoleFqdnOrName = "pgcvmexg"', handleError = False
    [2/2/2015 8:06:45 PM] [2] Launching sub-task '$error.Clear(); $RoleFqdnOrName = "pgcvmexg"'.
    [2/2/2015 8:06:45 PM] [1] Executing '$RoleTargetVersion = "8.3.83.6"', handleError = False
    [2/2/2015 8:06:45 PM] [2] Launching sub-task '$error.Clear(); $RoleTargetVersion = "8.3.83.6"'.
    [2/2/2015 8:06:45 PM] [1] Executing '$RoleUpdatesDir = "C:\SP3\Updates"', handleError = False
    [2/2/2015 8:06:45 PM] [2] Launching sub-task '$error.Clear(); $RoleUpdatesDir = "C:\SP3\Updates"'.
    [2/2/2015 8:06:45 PM] [1] Executing '$RoleIsClientAccessRoleInstalled = $True', handleError = False
    [2/2/2015 8:06:45 PM] [2] Launching sub-task '$error.Clear(); $RoleIsClientAccessRoleInstalled = $True'.
    [2/2/2015 8:06:45 PM] [1] Executing '$RoleRoleName = "BridgeheadRole"', handleError = False
    [2/2/2015 8:06:45 PM] [2] Launching sub-task '$error.Clear(); $RoleRoleName = "BridgeheadRole"'.
    [2/2/2015 8:06:45 PM] [1] Executing '$RoleDomainController = "PGCDC.platcorp.local"', handleError = False
    [2/2/2015 8:06:45 PM] [2] Launching sub-task '$error.Clear(); $RoleDomainController = "PGCDC.platcorp.local"'.
    [2/2/2015 8:06:45 PM] [1] Executing '$RoleProductPlatform = "amd64"', handleError = False
    [2/2/2015 8:06:45 PM] [2] Launching sub-task '$error.Clear(); $RoleProductPlatform = "amd64"'.
    [2/2/2015 8:06:45 PM] [1] Executing '$RoleIsBridgeheadRoleInstalled = $True', handleError = False
    [2/2/2015 8:06:45 PM] [2] Launching sub-task '$error.Clear(); $RoleIsBridgeheadRoleInstalled = $True'.
    [2/2/2015 8:06:45 PM] [1] Executing '$RoleLoggingPath = "C:\Program Files\Microsoft\Exchange Server\Logging"', handleError = False
    [2/2/2015 8:06:45 PM] [2] Launching sub-task '$error.Clear(); $RoleLoggingPath = "C:\Program Files\Microsoft\Exchange Server\Logging"'.
    [2/2/2015 8:06:45 PM] [1] Found 136 tasks to execute
    [2/2/2015 8:06:45 PM] [1] Processing component 'All Roles Common First - Run Once' (Configuring the server.).
    [2/2/2015 8:06:45 PM] [1] Executing 'if ($RoleProductPlatform -eq "amd64") { $watsonMSI = 'dw20sharedamd64.msi'; $watsonMSILogFileName = 'Installdw20sharedamd64.msilog'; } else { $watsonMSI = 'dw20shared.msi'; $watsonMSILogFileName = 'Installdw20shared.msilog';
    } install-MsiPackage -PackagePath ($RoleInstallPath + "bin\$watsonMSI") -LogFile ($RoleSetupLoggingPath + "\$watsonMSILogFileName") -UpdatesDir $RoleUpdatesDir -PropertyValues ("APPGUID=`"{24B2C164-DE66-44fe-B468-A46D9D5E6B31}`"
    LOGVERBOSE=1");', handleError = False
    [2/2/2015 8:06:45 PM] [2] Launching sub-task '$error.Clear(); if ($RoleProductPlatform -eq "amd64") { $watsonMSI = 'dw20sharedamd64.msi'; $watsonMSILogFileName = 'Installdw20sharedamd64.msilog'; } else { $watsonMSI = 'dw20shared.msi'; $watsonMSILogFileName
    = 'Installdw20shared.msilog'; } install-MsiPackage -PackagePath ($RoleInstallPath + "bin\$watsonMSI") -LogFile ($RoleSetupLoggingPath + "\$watsonMSILogFileName") -UpdatesDir $RoleUpdatesDir -PropertyValues ("APPGUID=`"{24B2C164-DE66-44fe-B468-A46D9D5E6B31}`"
    LOGVERBOSE=1");'.
    [2/2/2015 8:06:45 PM] [2] Beginning processing.
    [2/2/2015 8:06:45 PM] [2] ProductCode is '95120000-00b9-0409-1000-0000000ff1ce'.
    [2/2/2015 8:06:45 PM] [2] PackagePath was set to 'C:\Program Files\Microsoft\Exchange Server\bin\dw20sharedamd64.msi'; normalizing to 'C:\Program Files\Microsoft\Exchange Server\bin\dw20sharedamd64.msi'.
    [2/2/2015 8:06:45 PM] [2] ProductCode is '95120000-00b9-0409-1000-0000000ff1ce'.
    [2/2/2015 8:06:45 PM] [2] Installing MSI package 'C:\Program Files\Microsoft\Exchange Server\bin\dw20sharedamd64.msi'.
    [2/2/2015 8:06:47 PM] [2] Ending processing.
    [2/2/2015 8:06:47 PM] [1] Executing 'Set-InstallPathInAppConfig -ConfigFileRelativePath "Scripts\" -ConfigFileName "Exchange2007.xml" -ReplacementString "%ProgramFiles%\Microsoft\Exchange Server\";', handleError = False
    [2/2/2015 8:06:47 PM] [2] Launching sub-task '$error.Clear(); Set-InstallPathInAppConfig -ConfigFileRelativePath "Scripts\" -ConfigFileName "Exchange2007.xml" -ReplacementString "%ProgramFiles%\Microsoft\Exchange Server\";'.
    [2/2/2015 8:06:47 PM] [2] Beginning processing.
    [2/2/2015 8:06:47 PM] [2] Ending processing.
    [2/2/2015 8:06:47 PM] [1] Executing 'Remove-XmlNode -XmlFileRelativePath "Scripts\" -XmlFileName "Exchange2007.xml" -XmlNodeNameToRemove "_locDefinition";', handleError = False
    [2/2/2015 8:06:47 PM] [2] Launching sub-task '$error.Clear(); Remove-XmlNode -XmlFileRelativePath "Scripts\" -XmlFileName "Exchange2007.xml" -XmlNodeNameToRemove "_locDefinition";'.
    [2/2/2015 8:06:47 PM] [2] Beginning processing.
    [2/2/2015 8:06:47 PM] [2] ExchangeInstallPath = C:\Program Files\Microsoft\Exchange Server\, Relative Path = Scripts\, Xml Full File Path = C:\Program Files\Microsoft\Exchange Server\Scripts\Exchange2007.xml, Xml Node Name = _locDefinition
    [2/2/2015 8:06:47 PM] [2] Ending processing.
    [2/2/2015 8:06:47 PM] [1] Executing 'Set-InstallPathInAppConfig -ConfigFileRelativePath "Scripts\" -ConfigFileName "Exchange2007Edge.xml" -ReplacementString "%ProgramFiles%\Microsoft\Exchange Server\";', handleError = False
    [2/2/2015 8:06:47 PM] [2] Launching sub-task '$error.Clear(); Set-InstallPathInAppConfig -ConfigFileRelativePath "Scripts\" -ConfigFileName "Exchange2007Edge.xml" -ReplacementString "%ProgramFiles%\Microsoft\Exchange Server\";'.
    [2/2/2015 8:06:47 PM] [2] Beginning processing.
    [2/2/2015 8:06:47 PM] [2] Ending processing.
    [2/2/2015 8:06:47 PM] [1] Executing 'Remove-XmlNode -XmlFileRelativePath "Scripts\" -XmlFileName "Exchange2007Edge.xml" -XmlNodeNameToRemove "_locDefinition";', handleError = False
    [2/2/2015 8:06:47 PM] [2] Launching sub-task '$error.Clear(); Remove-XmlNode -XmlFileRelativePath "Scripts\" -XmlFileName "Exchange2007Edge.xml" -XmlNodeNameToRemove "_locDefinition";'.
    [2/2/2015 8:06:47 PM] [2] Beginning processing.
    [2/2/2015 8:06:47 PM] [2] ExchangeInstallPath = C:\Program Files\Microsoft\Exchange Server\, Relative Path = Scripts\, Xml Full File Path = C:\Program Files\Microsoft\Exchange Server\Scripts\Exchange2007Edge.xml, Xml Node Name = _locDefinition
    [2/2/2015 8:06:47 PM] [2] Ending processing.
    [2/2/2015 8:06:47 PM] [1] Executing 'Set-InstallPathInAppConfig -ConfigFileRelativePath "Scripts\" -ConfigFileName "Exchange2007_WinSrv2008.xml" -ReplacementString "%ProgramFiles%\Microsoft\Exchange Server\";', handleError = False
    [2/2/2015 8:06:47 PM] [2] Launching sub-task '$error.Clear(); Set-InstallPathInAppConfig -ConfigFileRelativePath "Scripts\" -ConfigFileName "Exchange2007_WinSrv2008.xml" -ReplacementString "%ProgramFiles%\Microsoft\Exchange Server\";'.
    [2/2/2015 8:06:47 PM] [2] Beginning processing.
    [2/2/2015 8:06:47 PM] [2] Ending processing.
    [2/2/2015 8:06:47 PM] [1] Executing 'Remove-XmlNode -XmlFileRelativePath "Scripts\" -XmlFileName "Exchange2007_WinSrv2008.xml" -XmlNodeNameToRemove "_locDefinition";', handleError = False
    [2/2/2015 8:06:47 PM] [2] Launching sub-task '$error.Clear(); Remove-XmlNode -XmlFileRelativePath "Scripts\" -XmlFileName "Exchange2007_WinSrv2008.xml" -XmlNodeNameToRemove "_locDefinition";'.
    [2/2/2015 8:06:47 PM] [2] Beginning processing.
    [2/2/2015 8:06:47 PM] [2] ExchangeInstallPath = C:\Program Files\Microsoft\Exchange Server\, Relative Path = Scripts\, Xml Full File Path = C:\Program Files\Microsoft\Exchange Server\Scripts\Exchange2007_WinSrv2008.xml, Xml Node Name = _locDefinition
    [2/2/2015 8:06:47 PM] [2] Ending processing.
    [2/2/2015 8:06:47 PM] [1] Executing 'Set-InstallPathInAppConfig -ConfigFileRelativePath "Scripts\" -ConfigFileName "Exchange2007Edge_WinSrv2008.xml" -ReplacementString "%ProgramFiles%\Microsoft\Exchange Server\";', handleError
    = False
    [2/2/2015 8:06:47 PM] [2] Launching sub-task '$error.Clear(); Set-InstallPathInAppConfig -ConfigFileRelativePath "Scripts\" -ConfigFileName "Exchange2007Edge_WinSrv2008.xml" -ReplacementString "%ProgramFiles%\Microsoft\Exchange Server\";'.
    [2/2/2015 8:06:47 PM] [2] Beginning processing.
    [2/2/2015 8:06:47 PM] [2] Ending processing.
    [2/2/2015 8:06:47 PM] [1] Executing 'Remove-XmlNode -XmlFileRelativePath "Scripts\" -XmlFileName "Exchange2007Edge_WinSrv2008.xml" -XmlNodeNameToRemove "_locDefinition";', handleError = False
    [2/2/2015 8:06:47 PM] [2] Launching sub-task '$error.Clear(); Remove-XmlNode -XmlFileRelativePath "Scripts\" -XmlFileName "Exchange2007Edge_WinSrv2008.xml" -XmlNodeNameToRemove "_locDefinition";'.
    [2/2/2015 8:06:47 PM] [2] Beginning processing.
    [2/2/2015 8:06:47 PM] [2] ExchangeInstallPath = C:\Program Files\Microsoft\Exchange Server\, Relative Path = Scripts\, Xml Full File Path = C:\Program Files\Microsoft\Exchange Server\Scripts\Exchange2007Edge_WinSrv2008.xml, Xml Node Name = _locDefinition
    [2/2/2015 8:06:47 PM] [2] Ending processing.
    [2/2/2015 8:06:47 PM] [1] Executing 'Set-WERRegistryMarkers;', handleError = False
    [2/2/2015 8:06:47 PM] [2] Launching sub-task '$error.Clear(); Set-WERRegistryMarkers;'.
    [2/2/2015 8:06:47 PM] [2] Beginning processing.
    [2/2/2015 8:06:47 PM] [2] Ending processing.
    [2/2/2015 8:06:47 PM] [1] Processing component 'All Roles Common First' (Creating the Exchange server configuration in the Active Directory).
    [2/2/2015 8:06:47 PM] [1] Executing '$RoleNames = $RoleRoles.Replace('Role','').Split(','); .\ServiceControl.ps1 EnableServices $RoleNames', handleError = False
    [2/2/2015 8:06:47 PM] [2] Launching sub-task '$error.Clear(); $RoleNames = $RoleRoles.Replace('Role','').Split(','); .\ServiceControl.ps1 EnableServices $RoleNames'.
    [2/2/2015 8:06:47 PM] [1] Executing 'Set-LocalPermissions', handleError = False
    [2/2/2015 8:06:47 PM] [2] Launching sub-task '$error.Clear(); Set-LocalPermissions'.
    [2/2/2015 8:06:47 PM] [2] Beginning processing.
    [2/2/2015 8:07:00 PM] [2] Ending processing.
    [2/2/2015 8:07:00 PM] [1] Executing 'get-service | where { $_.Name -ieq "HealthService" } | stop-service -Force:$true', handleError = False
    [2/2/2015 8:07:00 PM] [2] Launching sub-task '$error.Clear(); get-service | where { $_.Name -ieq "HealthService" } | stop-service -Force:$true'.
    [2/2/2015 8:07:00 PM] [1] Executing 'get-service | where { $_.Name -ieq "MOM" } | stop-service -Force:$true', handleError = False
    [2/2/2015 8:07:00 PM] [2] Launching sub-task '$error.Clear(); get-service | where { $_.Name -ieq "MOM" } | stop-service -Force:$true'.
    [2/2/2015 8:07:00 PM] [1] Executing 'get-service | where { $_.Name -ieq "OnePoint" } | stop-service -Force:$true', handleError = False
    [2/2/2015 8:07:00 PM] [2] Launching sub-task '$error.Clear(); get-service | where { $_.Name -ieq "OnePoint" } | stop-service -Force:$true'.
    [2/2/2015 8:07:00 PM] [1] Executing '$mofFilePath = ($RoleInstallPath + "bin\Exchange.MOF"); $mflFilePath = ($RoleInstallPath + "bin\Exchange.MFL"); compile-moffile -MofFilePath:$mofFilePath; compile-moffile -MofFilePath:$mflFilePath;',
    handleError = True
    [2/2/2015 8:07:00 PM] [2] Launching sub-task '$error.Clear(); $mofFilePath = ($RoleInstallPath + "bin\Exchange.MOF"); $mflFilePath = ($RoleInstallPath + "bin\Exchange.MFL"); compile-moffile -MofFilePath:$mofFilePath; compile-moffile
    -MofFilePath:$mflFilePath;'.
    [2/2/2015 8:07:00 PM] [2] Beginning processing.
    [2/2/2015 8:07:01 PM] [2] Exchange tracing provider was installed successfully.
    [2/2/2015 8:07:01 PM] [2] Ending processing.
    [2/2/2015 8:07:01 PM] [2] Beginning processing.
    [2/2/2015 8:07:01 PM] [2] Exchange tracing provider was installed successfully.
    [2/2/2015 8:07:01 PM] [2] Ending processing.
    [2/2/2015 8:07:01 PM] [1] Processing component 'All Roles Precompile Management Binaries' (Pre-compiling management binaries.).
    [2/2/2015 8:07:01 PM] [1] Executing '$fullPath = [System.IO.Path]::Combine($RoleInstallPath, "bin\microsoft.Exchange.Rpc.dll"); precompile-ManagedBinary -BinaryName $fullPath;', handleError = False
    [2/2/2015 8:07:01 PM] [2] Launching sub-task '$error.Clear(); $fullPath = [System.IO.Path]::Combine($RoleInstallPath, "bin\microsoft.Exchange.Rpc.dll"); precompile-ManagedBinary -BinaryName $fullPath;'.
    [2/2/2015 8:07:01 PM] [2] Beginning processing.
    [2/2/2015 8:07:01 PM] [2] Starting: C:\Windows\Microsoft.NET\Framework64\v2.0.50727\ngen.exe arguments: install "C:\Program Files\Microsoft\Exchange Server\bin\microsoft.Exchange.Rpc.dll" /verbose
    [2/2/2015 8:07:02 PM] [2] Process standard output: Microsoft (R) CLR Native Image Generator - Version 2.0.50727.4252
    Copyright (c) Microsoft Corporation.  All rights reserved.
    Installing assembly C:\Program Files\Microsoft\Exchange Server\bin\microsoft.Exchange.Rpc.dll
    All compilation targets are up to date.
    [2/2/2015 8:07:02 PM] [2] Process standard error: 
    [2/2/2015 8:07:02 PM] [2] Ending processing.
    [2/2/2015 8:07:02 PM] [1] Executing '$fullPath = [System.IO.Path]::Combine($RoleInstallPath, "bin\microsoft.Exchange.Common.IL.dll"); precompile-ManagedBinary -BinaryName $fullPath;', handleError = False
    [2/2/2015 8:07:02 PM] [2] Launching sub-task '$error.Clear(); $fullPath = [System.IO.Path]::Combine($RoleInstallPath, "bin\microsoft.Exchange.Common.IL.dll"); precompile-ManagedBinary -BinaryName $fullPath;'.
    [2/2/2015 8:07:02 PM] [2] Beginning processing.
    [2/2/2015 8:07:02 PM] [2] Starting: C:\Windows\Microsoft.NET\Framework64\v2.0.50727\ngen.exe arguments: install "C:\Program Files\Microsoft\Exchange Server\bin\microsoft.Exchange.Common.IL.dll" /verbose
    [2/2/2015 8:07:02 PM] [2] Process standard output: Microsoft (R) CLR Native Image Generator - Version 2.0.50727.4252
    Copyright (c) Microsoft Corporation.  All rights reserved.
    Installing assembly C:\Program Files\Microsoft\Exchange Server\bin\microsoft.Exchange.Common.IL.dll
    All compilation targets are up to date.
    [2/2/2015 8:07:02 PM] [2] Process standard error: 
    [2/2/2015 8:07:02 PM] [2] Ending processing.
    [2/2/2015 8:07:02 PM] [1] Executing '$fullPath = [System.IO.Path]::Combine($RoleInstallPath, "bin\Microsoft.Exchange.Diagnostics.dll"); precompile-ManagedBinary -BinaryName $fullPath;', handleError = False
    [2/2/2015 8:07:02 PM] [2] Launching sub-task '$error.Clear(); $fullPath = [System.IO.Path]::Combine($RoleInstallPath, "bin\Microsoft.Exchange.Diagnostics.dll"); precompile-ManagedBinary -BinaryName $fullPath;'.
    [2/2/2015 8:07:02 PM] [2] Beginning processing.
    [2/2/2015 8:07:02 PM] [2] Starting: C:\Windows\Microsoft.NET\Framework64\v2.0.50727\ngen.exe arguments: install "C:\Program Files\Microsoft\Exchange Server\bin\Microsoft.Exchange.Diagnostics.dll" /verbose
    [2/2/2015 8:07:02 PM] [2] Process standard output: Microsoft (R) CLR Native Image Generator - Version 2.0.50727.4252
    Copyright (c) Microsoft Corporation.  All rights reserved.
    Installing assembly C:\Program Files\Microsoft\Exchange Server\bin\Microsoft.Exchange.Diagnostics.dll
    All compilation targets are up to date.
    [2/2/2015 8:07:02 PM] [2] Process standard error: 
    [2/2/2015 8:07:02 PM] [2] Ending processing.
    [2/2/2015 8:07:02 PM] [1] Executing '$fullPath = [System.IO.Path]::Combine($RoleInstallPath, "bin\Microsoft.Exchange.Common.dll"); precompile-ManagedBinary -BinaryName $fullPath;', handleError = False
    [2/2/2015 8:07:02 PM] [2] Launching sub-task '$error.Clear(); $fullPath = [System.IO.Path]::Combine($RoleInstallPath, "bin\Microsoft.Exchange.Common.dll"); precompile-ManagedBinary -BinaryName $fullPath;'.
    [2/2/2015 8:07:02 PM] [2] Beginning processing.
    [2/2/2015 8:07:02 PM] [2] Starting: C:\Windows\Microsoft.NET\Framework64\v2.0.50727\ngen.exe arguments: install "C:\Program Files\Microsoft\Exchange Server\bin\Microsoft.Exchange.Common.dll" /verbose
    [2/2/2015 8:07:03 PM] [2] Process standard output: Microsoft (R) CLR Native Image Generator - Version 2.0.50727.4252
    Copyright (c) Microsoft Corporation.  All rights reserved.
    Installing assembly C:\Program Files\Microsoft\Exchange Server\bin\Microsoft.Exchange.Common.dll
    All compilation targets are up to date.
    [2/2/2015 8:07:03 PM] [2] Process standard error: 
    [2/2/2015 8:07:03 PM] [2] Ending processing.
    [2/2/2015 8:07:03 PM] [1] Executing '$fullPath = [System.IO.Path]::Combine($RoleInstallPath, "bin\Microsoft.Exchange.Core.Strings.dll"); precompile-ManagedBinary -BinaryName $fullPath;', handleError = False
    [2/2/2015 8:07:03 PM] [2] Launching sub-task '$error.Clear(); $fullPath = [System.IO.Path]::Combine($RoleInstallPath, "bin\Microsoft.Exchange.Core.Strings.dll"); precompile-ManagedBinary -BinaryName $fullPath;'.
    [2/2/2015 8:07:03 PM] [2] Beginning processing.
    [2/2/2015 8:07:03 PM] [2] Starting: C:\Windows\Microsoft.NET\Framework64\v2.0.50727\ngen.exe arguments: install "C:\Program Files\Microsoft\Exchange Server\bin\Microsoft.Exchange.Core.Strings.dll" /verbose
    [2/2/2015 8:07:03 PM] [2] Process standard output: Microsoft (R) CLR Native Image Generator - Version 2.0.50727.4252
    Copyright (c) Microsoft Corporation.  All rights reserved.
    Installing assembly C:\Program Files\Microsoft\Exchange Server\bin\Microsoft.Exchange.Core.Strings.dll
    All compilation targets are up to date.
    [2/2/2015 8:07:03 PM] [2] Process standard error: 
    [2/2/2015 8:07:03 PM] [2] Ending processing.
    [2/2/2015 8:07:03 PM] [1] Executing '$fullPath = [System.IO.Path]::Combine($RoleInstallPath, "bin\Microsoft.Exchange.Net.dll"); precompile-ManagedBinary -BinaryName $fullPath;', handleError = False
    [2/2/2015 8:07:03 PM] [2] Launching sub-task '$error.Clear(); $fullPath = [System.IO.Path]::Combine($RoleInstallPath, "bin\Microsoft.Exchange.Net.dll"); precompile-ManagedBinary -BinaryName $fullPath;'.
    [2/2/2015 8:07:03 PM] [2] Beginning processing.
    [2/2/2015 8:07:03 PM] [2] Starting: C:\Windows\Microsoft.NET\Framework64\v2.0.50727\ngen.exe arguments: install "C:\Program Files\Microsoft\Exchange Server\bin\Microsoft.Exchange.Net.dll" /verbose
    [2/2/2015 8:07:04 PM] [2] Process standard output: Microsoft (R) CLR Native Image Generator - Version 2.0.50727.4252
    Copyright (c) Microsoft Corporation.  All rights reserved.
    Installing assembly C:\Program Files\Microsoft\Exchange Server\bin\Microsoft.Exchange.Net.dll
    All compilation targets are up to date.

  • Best Migration Method for Exchange 2007 with multiple accepted domains

    We are trying to determine which method would be best for us as we migrate to O365.  Scenario as follows:
    1) Multiple accepted domains (each in their own OU in AD); example: domainA.com, domainB.com
    2) Exchange is 2007; clients will be upgrading the Outlook 2013
    3) Would like to be able to sync mailboxes starting anytime but be able to cut over a domain at a time.
    Tested so far with staged migration but it appears that with this, there is a change in the TargetAddress sending all mail to the O365.  Even changing MXs didn't redirect the message as it reaches the Exchange box and immediately goes to O365.
    We haven't tried the cutover as we're only able to test with the production box and if that somehow cutover the entire box, we'd be .. well, it wouldn't be good.  
    Anyone had any experience so that our #3 point would be doable, that would be great.  
    Thx
    George

    Hi George,
    According to your description, I understand that the issue is related to Exchange migration from Exchange 2007 to Exchange Online for Office 365. This forum focuses on some general discussion about Office 365 ProPlus which
    is the version of Office that comes with many Office 365 plans. Therefore, I suggest we can post the issue in Microsoft Exchange Online (Office 365) forum for more professional suggestions:
    http://social.technet.microsoft.com/Forums/en-US/home?forum=onlineservicesexchange
    Hope you can find the solution soon.
    Regards,
    Winnie Liang
    TechNet Community Support

  • Troubleshooting and Introduction for Exchange 2007/2010 AutoDiscover - Details about "Test E-mail AutoConfiguration"

    AutoDiscover is a new feature in Exchange 2007, to provide access to Microsoft Exchange features (OAB, Availability service, UM) for Outlook 2007
    clients or later.
    We can determine whether problems related to AutoDiscover via OWA.
    For example:
    OOF is not working in Outlook Client but it is working in OWA.
    When we realized this issue is not related to Outlook Client side and network side after performing some troubleshooting steps, it should be something
    abnormal on AutoDiscover.
    There is a common tool to check AutoDiscover in Outlook, Test E-mail AutoConfiguration.
    Today, we will introduce AutoDisocver and “Test E-mail AutoConfiguration” in details. Hope it is helpful for AutoDiscover troubleshooting and self-learning.
    1. Differences between “Test E-mail AutoConfiguration” and other tools
    The “Test-OutlookWebServices” cmdlet allows us to test the functionality of the following services:
    Autodisocver
    Exchange Web Services
    Availability Service
    Offline Address Book
    When we run “Test-OutlookWebServices”, it returns all the web services’ states.
    However, some information are useless for some scenarios.
    For example:
    We just want our Exchange 2010 Server working internally. So it is unnecessary to enable Outlook Anywhere.
    However, when we run “Test-OutlookWebServices”, it returns Outlook Anywhere errors because the Outlook Anywhere does not need to been enabled.
    In contrast, using “Test E-mail Autodiscover” is more intuitive.
    If there is any problems, it will return error code from the test result, like 0x8004010F etc. We can do some research from TechNet articles or MS
    KBs.
    Although it is difficult to say where the specific problem is just via the error codes, we can combine with IIS logs to perform troubleshooting and
    find the root of problem.
    2. How to use “Test E-mail AutoConfiguration” Tool
    a. Open Outlook, we can find there is an Outlook Icon at the right bottom of System tray. Holding down “Ctrl” button and right click the Outlook Icon, we will see “Test E-mail
    AutoConfiguration” option. Please see Figure 01.
    Figure 01
    b. Click “Test E-mail AutoCofiguration” and input user name, uncheck the “Use Guessmart” and “Secure Guessmart Authentication” checkboxes, then click “Test”. Please see
    Figure 02.
    Figure 02
    c. “Test E-mail AutoConfiguration” result panel and log panel. Please see Figure 03 and Figure 04.
    Figure 03
    Figure 04
    3. How to understand “Test E-mail AutoConfiguration” result
    According to the Figure 03, we found there are many URLs in the “Test E-mail AutoConfiguration” result panel. Let us understand the details of these
    URLs.
    If we these URLs are not the correct ones, we can re-setting or re-creating them via commands.
    - Internal OWA URL:
    https://vamwan310.vamwan.com/owa/
    OWA internal access.
    - External OWA URL:
    https://mail.vamwan.com/owa/
    OWA external access.
    - Availability service URL:
    https://vamwan310.vamwan.com/EWS/Exchange.asmx
    Free/Busy, OOF and meeting suggestions.
    - OOF URL:
    https://vamwan310.vamwan.com/EWS/Exchange.asmx
    Out of Office access.
    - OAB URL:
    https://vamwan310.vamwan.com/OAB/023ef307-b18a-4911-a52c-de26700f6173/
    OAB access.
    - Exchange Control Panel URL:
    https://vamwan310.vamwan.com/ecp/
    ECP access.
    4. AutoDiscover Tips
    - AutoDiscover Service itself is a web application running on the AutoDiscover virtual directory (not a server service) designed to provide connection information to various
    clients.
    - The AutoDiscover service is automatically installed and configured when CAS role is added to any Exchange Server.
    - AutoDisocver virtual directory is created in IIS within the Default Web Site.
    - A Sercive-Connection-Point (SCP) object is created in AD.
    - The SCP contains a URL to the AutoDiscover service. This is for intranet clients so they do not have to use DNS to locate the AutoDiscover service.
    - In AD this object is located at the following location:
    DC=<domain>, CN=Configuration, CN=Services, CN=Microsoft Exchange, CN=First Organization, CN=Administrative Groups, CN=Exchange Administrative
    Group, CN=Servers, CN=<CAS Name>, CN=Protocols, CN=AutoDiscover, CN=<CAS Name>
    - Setup creates the AutoDiscover URL based on the following structure:
    <CASNetbiosName>.domain.com/AutoDiscover/AutoDiscover.xml
    If a PKI certificate is not already present, a self-signed certificate is installed on the Default Web Site. 
    To help allow this certificate pass the Issues to test it is set up with a Subject Alternative Name containing urls.
    If a PKI certificate is present, that certificate is utilized and configured for use in IIS.
    The Outlook Provider is used to configure separate settings for the Exchange PRC protocol (internal to network), Outlook Anywhere (Exchange HTTP protocol), and WEB:
    EXCH, EXPR, WEB
    The
    EXCH and EXPR setting are vital for the proper configuration of Outlook.
    5. AutoDiscover Workflow
    General Process flow:
    There are various components surrounding the AutoDiscover Service and all are necessary to complete a request. Including IIS, AutoDiscover service
    itself, the provider, and AD.
    a.
    Client constructs service URL and submits Autodiscover Request. First attempt to locate the SCP object in AD. So, DNS is not needed.
    b.
    IIS Authenticates User.
    c.
    Is the Autodiscover service in the appropriate forest?
    + If YES.
        1)
    Parse/Validate Request
        2)
    Is there a provider that can service the Request?
    ++ If YES
          a)
    Config provider processes request and returns config settings.
          b)
    Return config setting to client
    ++ If NO
    Inform client we cannot process request
    + If NO.
    Redirect client to Autodiscover service in the appropriate forest.
    Methods to find Autodiscover services: SCP and DNS
    Domain-joined
    a. Find SCP first.
    The SCP contains the URL to the AutoDiscover service.
    URL: https://CAS01.contoso.com(CAS’ FQDN)/AutoDiscover/AutoDiscover.xml
    If more than one SCP object is found in AD (it means there are multiple CAS servers in the Exchange organization), Outlook client will choose one of the SCP entries that
    are in the same site to obtain the AutoDisocover URL.
    b. If we cannot find SCP object, then Outlook client will use DNS to locate AutoDiscover.
    Outlook parses out the domain (SMTP suffix) via your EmaiAddress, then attempts to connect to the predetermined order of URLs via the suffix.
    For example: If my email address is
    [email protected]
    Outlook tries POST commands to the following order of URLs:
    https://contoso.com/autodiscover/autodiscover.xml
    https://autodiscover.contoso.com/autodiscover/autodiscover.xml
    NOTE: The URLs above is by design, hardcode
    and cannot be changed.
    c.
    If those fail, Outlook tries a simple redirect to another URLs in IIS:
    http://contoso.com/autodiscover/autodiscover.xml
    http://autodiscover.contoso.com/autodiscover/autodiscover.xml
    If none of these URLs work then DNS is most likely not set up correctly.
    We can test that by pinging one of the above URLs.
    If that is successful, we must ensure the URLs contoso.com or autodiscover.contoso.com are actually pointing to the CAS server.
    If the ping fails then there is a chance that DNS is not set up correctly so be sure to check that the URLs are even registered.
    NOTE: If contoso.com is a non-CAS server,
    we should add a Host record with just AutoDiscover. And point that entry to your CAS server that is running AutoDiscover.
    d.
    If still failed, we can use DNS SRV lookup for _autodiscover._tcp.contoso.com, then “CAS01.contoso.com” returned. Outlook will ask permission from the user to continue
    with AutoDiscover to post to https://CAS01.contoso.com/autodiscover/autodiscover.xml
    Non-Domain-joined
    It first tries to locate the Autodiscover service by looking up the SCP object in AD. However the client is unable to contact AD, it tries to locate
    the Autodiscover service by using DNS.
    Then, same as step b, c, d in
    Domain-joined scenario.
    6. How to change the AutoDiscover
    service location order forcibly?
    By default, Outlook client locates AutoDiscover service in that order above.
    We can also change the order forcibly.
    a.
    If we want to locate AutoDiscover service via one of the autodiscover URLs, please running following command in EMS:
    Set-ClientAccessServer -identity <servername> -AutodiscoverServiceInternalUri https://autodiscover.contoso.com/autodiscover/autodiscover.xml(URL
    that you want)
    b. If we want to locate AutoDiscover service via
    SRV record, please follows this KB to set up SRV:
    http://support.microsoft.com/kb/940881
    7. How to check AutoDiscover Healthy
    a. We should make sure the AutoDiscover
    is healthy before using AutoDiscover to perform troubleshooting.
    b.
    We can browse following URL in IE explorer:
    https://autodiscover.vamwan.com/autodiscover/autodiscover.xml
    If it returns “code 600”, that means AutoDiscover is healthy.
    Screenshot as below:
    c. AutoDiscover itself returns errors to the requesting client if the incoming request does not contain the appropriate information to complete a
    request.
    The following table explains the possible errors that could be returned.
    Error   Value
    Description  
    600
    Mailbox not found and a   referral could not be generated.
    601
    Address supplied is not   a mailbox. The provided email address is not something a client can connect to.   It could
    be a group or public folder.
    602
    Active Directory error.
    603
    Others.
    The 600 “Invalid Request” error is returned because a user name was not passed to the service. That is OK for this test because this does confirm
    the service is running and accepting requests.
    d.
    If AutoDiscover service is not working well, I suggest re-building the AutoDiscover Virtual Directory for testing.
    Steps as below:
    1) Running following command in EMS to remove the AutoDiscover VD (we cannot delete it via EMC):
    Remove-AutodiscoverVirtualDirectory -Identity "CAS01\autodiscover(autodiscover.contoso.com)"
    Please refer:
    http://technet.microsoft.com/en-us/library/bb124113(v=exchg.141).aspx 
    2)
    Running following command in EMS to verify whether we have removed the AutoDisocver VD successfully:
    Get-AutodiscoverVirtualDirectory | FL
    Please refer:
    http://technet.microsoft.com/en-us/library/aa996819(v=exchg.141).aspx
    3)
    Running following command in EMS to re-creating a new AutoDiscover VD:
    New-AutodiscoverVirtualDirectory -Websitename <websitename> -BasicAuthentication:$true -WindowsAuthentication:$true
    Please refer:
    http://technet.microsoft.com/en-us/library/aa996418(v=exchg.141).aspx
    8. Common issues
    a. Outlook Disconnection
    Issue and Troubleshooting
    Issue:
    Sometimes the Outlook clients cannot connect to the Exchange server after migrating to a new Exchange server or changing to new CAS. The Outlook clients
    always connect to the old CAS server.
    Troubleshooting:
    To solve this issue, we should change the SCP via following command:
    Set-ClientAccessServer -Identity
    <var>CAS_Server_Name</var> -AutodiscoverServiceInternalUri
    https://mail.contoso.com(newCAS’FQDN)/autodiscover/autodiscover.xml
    b. Autodiscover
    Certificate issue
    Tips on Certificate:
    Exchange requires a certificate to run an SSL protocol such as HTTPS. We can use the certificate that supports subject alternate names (SAN) in Exchange.
    This is to allow the certificate to support resources that have different names, such as Outlook Anywhere and the Autodisocver Web application.
    Issue and Troubleshooting
    Issue:
    We receiver the Certificate Principal Mismatch error when we use a SAN certificate.
    Troubleshooting:
    1) Please determine the FQDN that the client
    uses to access the resource. Steps as below:
    OutlookàToolsàAccount
    SettingsàE-mailàclick
    the Exchange accountàChangeàMore
    SettingsàConnectionàExchange
    Proxy Settingsànote the FQND that list in the
    Only connect to proxy servers that have this principal name in their certificate box.
    2)
    Please using EMS to determine the value for the CerPrincipalName attribute: Get-OutlookProvider
    This command returns the result for the EXPR name.
    3)
    Please re-setting the CertPrincipalName attribute to match the FQDN via following command:
    Set-OutlookProvider EXPR –CertPrincipalName: “msstd:<FQDN the certificate is issued to>”
    9. Resource for reference:
    Autodiscover and Exchange 2007
    http://technet.microsoft.com/en-us/library/bb232838(v=exchg.80).aspx
    White Paper: Understanding the Exchange 2010 Autodiscover Service
    http://technet.microsoft.com/en-us/library/jj591328(v=exchg.141).aspx
    Certificate Principal Mismatch
    http://technet.microsoft.com/en-us/library/aa998424(v=exchg.80).aspx
    Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

    HI,
     I get following?  when run the test?  user is login to Domain A but accessing exchange in Domain B?

  • Exchange 2007/2010 Console doesn't show up Exchange 2007 Databases after RBAC Implementation

    I have implemented a RBAC model after which Exchange 2010/2007 Console won't show up Exchange 2007 Mailbox Databases.
    Everything was working fine up until the Users were members of "Exchange Recipient Administrators" Group.
    I have created Custom Roles based on PArent Roles, Mail Recipients, Mail Recipient Creation, Distribution Groups & Public Folders and assigned that to a universal security group "Helpdesk operations". I removed membership for Helpdesk operations
    from "Exchange Recipient Administrators" Group and assigned the Custom Roles to "Helpdesk Operations" using the cmdlet below:
    New-ManagementRoleAssignment "Custom Role" -SecurityGroup "HelpDesk Operations"
    Exchange 2010 console shows Exchange 2010 Databases but not Exchange 2007 DAtabases. Exchange 2007 console doesn't show up any databases on New-Mailbox and simply displays a message "No Objects Found".
    Even Get-MailboxDatabase REturns blank output on Exchange 2007 SHell. Please help me with this and let me know in case if there is something that i need to be looking at!
    any help on this is much appreciated.
    M.P.K ~ ( Exchange | 2003/2007/2010/E15(2013)) ~~ Please remember to click “Vote As Helpful" if it really helps and "Mark as Answer” if it answers your question, “Unmark as Answer” if a marked post does not actually answer your question. ~~ This
    Information is provided is "AS IS" and confers NO Rights!!

    Hi,
    I recommend you use the following cmdlet and check the result.
    Get-MailboxDatabase -Server "Exchange 2007 server name"
    In my environment, if I don't specify the Server parameter on Exchange 2010 Management Shell, Exchange 2007 mailbox database can't be displayed. If I specify the Server parameter, Exchange 2007 mailbox database will be displayed.
    What's more, please check if the account you use has been delegated the Exchange View-Only Administrator role.
    Here is a thread for your reference.
    Get-MailboxDatabase
    http://technet.microsoft.com/en-us/library/bb676367(v=exchg.80).aspx
    Hope it helps.
    Best regards,
    Amy
    Amy Wang
    TechNet Community Support

  • Mail Sender Adapter for Exchange 2007 IMAPS account

    Hi everybody,
    I have the following todo:
    I configured a Mail Sender Adapter that is supposed to fetch mails from an IMAP account.
    The mails contain text files with data to be processed by XI 3.0 SP 22.
    The mail server is Exchange 2007 and requires IMAPS. IMAP is not enough. I read the notes
    - 893590 - XI 3.0 Mail sender adapter with IMAP or POP with SSL problem
    - 856599 - FAQ: XI 3.0 / PI 7.0 / PI 7.1 Mail Adapter
    and configured the sender apapter as follows:
    URL:                     imaps://<ip address>/owa
    Authentication method:     Plain
    User:                    <domain>\<user>
    Password:                       topsecret
    Poll Interval: 5
    The first challenge is to setup the adapter with SSL. To do so, I added the Exchange server's
    root SSL certificate in the default truststore service-ssl via the KeyStorage service.
    This is necessary, as far as I know, to successfully validate the Exchange server's trusted
    certifacate which is being transfered to XI during SSL handshake.
    Since the communication channel in RWB is in status error with following message:
    mail client job stopped completly
    exception caught during processing mail message; java.io.IOException: invalid IMAP status response; not finding * STATUS, but 001I NO owa doesn't exist.
    mail client job scheduled,
    I do not know how to setup SSL for IMAPS. I successfully tested a PING to the Exchange server.
    Are there already experiences with Exchange 2007?
    What I have to do to fetch mails from an Exchange 2007 IMAPS folder/account with a Mail Sender Adapter?
    Kind regards,
    Andreas

    Hi,
    It should be imap and not imaps.
    You can try imap://xxx.xxx.de:993/Inbox
    Make sure that port 993 is correct. If you have doubt, then you may try 143 which is default port instead of 993 in the above url.
    regards,
    ganesh.

  • Autodiscovery from external Exchange 2007 SP1

    Dear all,
    We have 1 Exchange 2007 and 1 CAS server running and a Terminal Server. All Outlook 2007 clients are connecting using HTTPS/RPC internally and external. Now our problem is that when we try to configure an outlook client 2007 from the outside, that the "Online Search for your server settings" fails. We constantly get the credentials (u/p) prompt which is provided the correct credentials but are not accepted.
    From inside (for example on the Terminal Server) everything works fine (incl. OAB, OOF, etc). So this should be something with login to autodiscover.
    Conclusion:
    When we try to connect to: https://externaladdress.domain.net/autodiscover/autodiscover.xml (from the CAS server) we can logon with every valid credential. Now when we try to connect to the above mentioned address from ANY other internal server, or external address, we are not able to login and are constantly prompted with the UserName and Password window.
    Does anybody have a clue what's wrong here?
    Regards,
    David.

    Hi Scott and Rajnish,
    Thanks for your response.
    We do not use a firewall to be honest (at this moment). I forgot to mention that we also use a url autodiscover.domain.net as a redirect to webmail.domain.net (our CAS server). Redirect seems to work fine, as I tried to connect to: autodiscover.domain.net/autodiscover/autodiscover.xml and I'm prompted with username and password window (which also does not authenticate). The 
    The report from the url: https://www.testexchangeconnectivity.com/
    Testing RPC/HTTP connectivity
    RPC/HTTP test failed
    Test Steps
    Attempting to test Autodiscover for EMAIL REMOVED
    Testing Autodiscover failed
    Test Steps
    Attempting each method of contacting the AutoDiscover Service
    Failed to contact the AutoDiscover service successfully by any method
    Test Steps
    Attempting to test potential AutoDiscover URL https://domain.net/AutoDiscover/AutoDiscover.xml
    Failed testing this potential AutoDiscover URL
    Test Steps
    Attempting to test potential AutoDiscover URL https://autodiscover.domain.net/AutoDiscover/AutoDiscover.xml
    Failed testing this potential AutoDiscover URL
    Test Steps
    Attempting to contact the AutoDiscover service using the HTTP redirect method.
    Failed to contact AutoDiscover using the HTTP Redirect method
    Test Steps
    Attempting to resolve the host name autodiscover.domain.net in DNS.
    Host successfully resolved
    Additional Details
    Testing TCP Port 80 on host autodiscover.domain.net to ensure it is listening and open.
    The port was opened successfully.
    Checking Host autodiscover.domain.net for an HTTP redirect to AutoDiscover
    Received Redirect (HTTP 301/302) Response successfully.
    Additional Details
    Attempting to test potential AutoDiscover URL https://webmail.otherdomain.net/Autodiscover/Autodiscover.xml
    Failed testing this potential AutoDiscover URL
    Test Steps
    Attempting to resolve the host name webmail.otherdomain.net in DNS.
    Host successfully resolved
    Additional Details
    Testing TCP Port 443 on host webmail.otherdomain.net to ensure it is listening and open.
    The port was opened successfully.
    Testing SSL Certificate for validity.
    The certificate passed all validation requirements.
    Test Steps
    Attempting to send AutoDiscover POST request to potential autodiscover URLs.
    Failed to obtain AutoDiscover settings when sending AutoDiscover POST request.
    Test Steps
    Attempting to Retrieve XML AutoDiscover Response from url https://webmail.otherdomain.net/Autodiscover/Autodiscover.xml for user EMAIL REMOVED
    Failed to obtain AutoDiscover XML response.
    Additional Details
    A Web Exception occurred because an HTTP 401 - Unauthorized response was received from Unknown
    Further I've spend more than 1 week to find a solution, and read a lot of articles, including the one Scott mentioned in his post.
    I hope that we can resolve this :-(
    Regards,
    David.

Maybe you are looking for