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

Unable to add database copy for DR mailbox server

$
0
0

Hi,

Recently i configured DR for our Exchange infra with 2 CAS server and 2 Mailbox server. For DR cas server i created a separate NLB as drmail.domain.local. And add the DR mailbox server in Existing DAG.  Now while trying to add a active database copy its showing following error. 

============

The seeding operation failed. Error: An error occurred while performing the seed operation. Error: Failed to open a log truncation context to source server 'DC-MAILBOX-02.domain.local'. Hresult: 0xc7ff07d7. Error: Failed to open a log
truncation context because the Microsoft Exchange Information Store service is not running. [Database: MBXDB03,
Server: DRC-MAILBOX-01.domain.local]
    + CategoryInfo          : InvalidOperation: (:) [Update-MailboxDatabaseCopy], SeedInProgressException
    + FullyQualifiedErrorId : [Server=DC-MAILBOX-02,RequestId=3bdf9fa0-7f18-4f05-a18e-f2d61369bcb7,TimeStamp=17-07-201
   6 10:00:48] 5C92F4F2,Microsoft.Exchange.Management.SystemConfigurationTasks.UpdateDatabaseCopy
    + PSComputerName        : dc-mailbox-02.domain.local

=====================

And when i try to verify the same Fail over cluster validation found the following error.

=======

    An error occurred while executing the test.
    There was an error getting information about the operating systems on the node.

    Unable to connect to DRC-MAILBOX-01.domain.local via WMI. This may be due to networking issues or firewall configuration on DRC-MAILBOX-01.domain.local.

    The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)

    ==============

 And cluster name is also not showing in Fail over cluster manager while try to connect to a cluster its givs the same error RPC server is unavailable. 

But from ECP which view the DAG members status its showing operational. Please help me to find a solution .

Thanks in advance.  


Need to copy mailbox from Exchange 2010 to MS Online

$
0
0

I perform the Hybrid Configuration from that site:

https://technet.microsoft.com/en-us/exdeploy2013/Checklist?state=2419-W-FQAIAAAAQAAAAA8AKFQAQAA~&f=255&MSPPError=-2147217396

When I try to do the moving step, I have those errors;

Summary: 1 item(s). 0 succeeded, 1 failed.
Elapsed time: 00:00:06


Test
Failed

Error:
Deserialization fails due to one SerializationException: System.Runtime.Serialization.SerializationException: Unable to find assembly 'Microsoft.Exchange.MailboxReplicationService.Common, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
   at System.Runtime.Serialization.Formatters.Binary.BinaryAssemblyInfo.GetAssembly()
   at System.Runtime.Serialization.Formatters.Binary.ObjectReader.GetType(BinaryAssemblyInfo assemblyInfo, String name)
   at System.Runtime.Serialization.Formatters.Binary.ObjectMap..ctor(String objectName, String[] memberNames, BinaryTypeEnum[] binaryTypeEnumA, Object[] typeInformationA, Int32[] memberAssemIds, ObjectReader objectReader, Int32 objectId, BinaryAssemblyInfo assemblyInfo, SizedArray assemIdToAssemblyTable)
   at System.Runtime.Serialization.Formatters.Binary.__BinaryParser.ReadObjectWithMapTyped(BinaryObjectWithMapTyped record)
   at System.Runtime.Serialization.Formatters.Binary.__BinaryParser.Run()
   at System.Runtime.Serialization.Formatters.Binary.ObjectReader.Deserialize(HeaderHandler handler, __BinaryParser serParser, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)
   at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize(Stream serializationStream, HeaderHandler handler, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)
   at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize(Stream serializationStream, HeaderHandler handler, Boolean fCheck, IMethodCallMessage methodCallMessage)
   at Microsoft.Exchange.Data.SerializationTypeConverter.<>c__DisplayClass3.<DeserializeObject>b__0()

Unable to find assembly 'Microsoft.Exchange.MailboxReplicationService.Common, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.

Exchange Management Shell command attempted:
'50038459-45a0-4cf4-bc46-42d9d7158752' | New-MoveRequest -Remote -RemoteHostName 'mail.sqliaison.com' -RemoteCredential 'System.Management.Automation.PSCredential' -TargetDeliveryDomain 'inedge.mail.onmicrosoft.com'

Elapsed Time: 00:00:06

The user is in the cloud synchronized with my local DC and I have assigned a license to it.

Any help would be appreciated/

OWA URL migration

$
0
0

Hi,

After migrating from Exchange 2003 >> 2010 to 2013, the URL for the Outlook Web Access change from myserver/exchange to myserver/owa.

Some users are used to use /exchange and prefer to keep using it.

I'm looking for a way to be able to user both URL (myserver/owa and /myserver/exchange).

Do you have any idea?

Ragards

Exchange 2013 co-existence with Exchange 2010 proxying issue.

$
0
0


Hello,  

I am testing Exchange 2010 and Exchange 2013 co-existence in my test lab at the moment, with a view to migrating our production environment to 2013 later in the year.  

The lab is setup, and the problem I'm having is that internal Outlook clients cannot open their respective mailboxes once the 2013 CAS server is introduced into the mix.  

 The setup is listed below:  

EXCHANGE 2010 Servers  

TESTLABEXCH01 - CAS,HT,MBX - Exchange 2010 SP3  

TESTLABEXCH02 - CAS,HT,MBX - Exchange 2010 SP3  

Both servers are part of a CAS Array - casarray01.testlab.local  

Both servers are part of a DAG - DAG01.testlab.local  

RpcClientAccessServer on all 2010 databases set to casarray01.testlab.local  

The A record for casarray01.testlab.local points to the IP of the VIP of a load balancer.  

The loadbalancer serves the following ports: 25,80,443,143,993,110,995,135,60200,60201  

OutlookAnywhere is enabled on both servers:  

ClientAuthenticationMethod : Ntlm  

IISAuthenticationMethods   : {Basic, Ntlm 

  

Internal and external mail flow works without issue before the 2013 server is introduced. 

Internal and external client access works without issue before the 2013 server is introduced. 

Part Two to follow.....



Matt

RPC Proxy doesn't work: 2013/2010 Co-Existence with Outlook Anywhere

$
0
0

ISSUE: Can't RPC Proxy Outlook Anywhere requests for Exchange 2010 mailbox users via the Exchange 2013 CAS.

SYMPTOMS: Externally with TestExchangeConnectivity.com, I get 'RPC Proxy Can't Be Pinged' with 'An HTTP 401 Unauthorized response was received from the remote Unknown server'.

SETUP:

Exchange 2013 CU2
Get-OutlookAnywhere Details:
ExternalHostname: webapp.mydomain.com
InternalHostname: ex2013.mydomain.local
ExternalClientAuthenticationMethod: Basic
InternalClientAuthenticationMethod: Ntlm
IISAuthenticationMethods: Basic, Ntlm, Negotiate
SSLOffloading: False

Certificate on 2013 server contains the names: ex2013.mydomain.local, webapp.mydomain.com, AutoDiscover.mydomain.local, AutoDiscover.mydomain.com, mydomain.local, mydomain.com

Exchange 2010 SP3 update rollup 1
Get-OutlookAnywhere Details:
ExternalHostname: webapp.mydomain.com
ClientAuthenticationMethod: Basic
IISAuthenticationMethods: Basic, Ntlm
SSLOffloading: False

Certificate on 2010 server contains the names: ex2010.mydomain.local, webapp.mydomain.com, autodiscover.mydomain.local, autodiscover.mydomain.com

Outlook providers:
EXCH  CertPrincipalName: msstd:webapp.mydomain.com
EXPR  CertPrincipalName: msstd:*.mydomain.com    (as I use an external reverse proxy with a public wildcard certificate)

ADDITIONAL DETAILS:
- With the above settings, Outlook 2010 doesn't seem to be able to proxy RPC through Exchange 2013.

Testing manually with RPCPING utility:
- Requests for port 6001 directed to Exchange 2010 for people with mailbox on Exchange 2010: works correctly
- Requests for port 6001 directed to Exchange 2013 for people with mailbox on Exchange 2013: works correctly
- Requests for port 6001 directed to Exchange 2013 for people with mailbox on Exchange 2010: error 401.1 Unauthorized

OWA and Activesync through Exchange 2013 for people with mailbox on Exchange 2010 are working fine.
Only RPC over HTTP seems to have problems.

- Here are some pertinent lines from the 2010 CAS server's IIS logs for a 2013 to 2010 RPC access:
2013-10-10 13:02:16 10.62.6.56 RPC_IN_DATA /rpc/rpcproxy.dll ex2010.mydomain.local:6001 443 - 10.62.6.50 MSRPC 401 1 2148074248 624
2013-10-10 13:02:16 10.62.6.56 RPC_OUT_DATA /rpc/rpcproxy.dll ex2010.mydomain.local:6001 443 - 10.62.6.50 MSRPC 401 1 2148074248 624
2013-10-10 13:02:16 10.62.6.56 RPC_IN_DATA /rpc/rpcproxy.dll - 443 - 10.62.6.50 HttpProxy.ClientAccessServer2010Ping 401 2 5 780

- Here are some pertinent lines from the 2013 CAS server's IIS logs for the same 2013 to 2010 RPC access:
2013-10-10 13:02:14 10.62.6.50 RPC_IN_DATA /rpc/rpcproxy.dll ex2010.mydomain.local:6001&RequestId=b6464f37-a9fe-4f84-a32b-ff9af689607c&cafeReqId=b6464f37-a9fe-4f84-a32b-ff9af689607c; 443 - 10.62.7.15 MSRPC - 401 1 2148074254 4726
2013-10-10 13:02:14 10.62.6.50 RPC_OUT_DATA /rpc/rpcproxy.dll ex2010.mydomain.local:6001&RequestId=4acc0118-7fac-49db-976d-152a4a6839b2&cafeReqId=4acc0118-7fac-49db-976d-152a4a6839b2; 443 - 10.62.7.15 MSRPC - 401 1 2148074254 0
2013-10-10 13:02:16 10.62.6.50 RPC_OUT_DATA /rpc/rpcproxy.dll ex2010.mydomain.local:6001&RequestId=a591fb11-98c3-44e6-90c7-f719c7047fe4&cafeReqId=a591fb11-98c3-44e6-90c7-f719c7047fe4; 443 dom\2010user 10.62.7.15 MSRPC - 401 0 64 1544
2013-10-10 13:02:16 10.62.6.50 RPC_IN_DATA /rpc/rpcproxy.dll ex2010.mydomain.local:6001&RequestId=fbb94579-8d0b-41d7-8103-45c945141bd7&cafeReqId=fbb94579-8d0b-41d7-8103-45c945141bd7; 443 dom\2010user 10.62.7.15 MSRPC - 200 0 64 1700

Any thoughts or comments are highly appreciated. Let me know if additional details are needed.

Mailbox Migration analysis using the AnalyzeMoveRequestStats.ps1 script

$
0
0

We are getting ready to start a massive migratin of mailboxes from 2010 to 2013.  

We just did a small pilot migration and here is the analysis.  What should I be looking at for the cause of the high IdleDuration time.  The documantation for the script says:  

IdleDuration

Amount of time that the MRSProxy service request waits in the MRSProxy service's in-memory queue due to limited resource availability.

But what does that limited Resource availability mean.  

Name                            : ProcessedStats1

StartTime                       :

EndTime                         : 7/12/2016 10:48:04 PM

MigrationDuration               : 04:40:09

MailboxCount                    : 182

TotalGBTransferred              : 71.61

PercentComplete                 : 98.51

MaxPerMoveTransferRateGBPerHour : 1.12

MinPerMoveTransferRateGBPerHour : 0.01

AvgPerMoveTransferRateGBPerHour : 0.22

MoveEfficiencyPercent           : 80.20

AverageSourceLatency            :

AverageDestinationLatency       :

IdleDuration                    : 89.61 %

SourceSideDuration              : 4.78 %

DestinationSideDuration         : 5.39 %

WordBreakingDuration            : 3.06 %

TransientFailureDurations       : 0.89 %

OverallStallDurations           : 0.03 %

ContentIndexingStalls           : 0.00 %

HighAvailabilityStalls          : 0.00 %

TargetCPUStalls                 : 0.03 %

SourceCPUStalls                 : 0.00 %

MailboxLockedStall              : 0.00 %

ProxyUnknownStall               : 0.00 %


Jeff C

I have two email domains say A.com and B.com in one exchange organization, need to hide contacts synchronized from domain C from Domain A

$
0
0
I have two email domains say  A.com and B.com in one exchange organization, I am synchronizing contacts from another company say C.com. In this case only A.com email users should see C.com, but B.com users should not see the synchronized contacts. How to achieve it?

Error 8207 when trying to install SP3 on Exchange2010

$
0
0

Upgrade stacks always at the same point and gives the following error. cannot proceed. Can you assist?

Failed Error: The following error was generated when "$error.Clear(); install-ExchangeSchema -LdapFileName ($roleInstallPath + "Setup\Data\"+$RoleSchemaPrefix+ "schema3.ldf") " was run: "There was an error while running 'ldifde.exe' to import the schema file 'C:\Windows\Temp\ExchangeSetup\Setup\Data\PostExchange2003_schema3.ldf'. The error code is: 8207. More details can be found in the error file: 'C:\Users\administrator\AppData\Local\Temp\2\ldif.err'". There was an error while running 'ldifde.exe' to import the schema file 'C:\Windows\Temp\ExchangeSetup\Setup\Data\PostExchange2003_schema3.ldf'.The error code is: 8207. More details can be found in the error file: 'C:\Users\administrator\AppData\Local\Temp\2\ldif.err' Click here for help...


Emails to distribution group using old server

$
0
0

Hello All,

We recently migrated from Exchange 2010 to Exchange 2013 and everything seemed to go well. However, we have one small issue that is preventing us from completely cutting the tie to the Exchange 2010 servers. When users send emails to distribution lists the emails are routed to the Exchange 2010 server.

Here is where we stand at the moment. We used the series of articles from MSExchange.org walking us through installing and moving from Exchange 2010 to Exchange 2013. The link to the articles is here. We have all the mailboxes moved to the new Exchange server and the new Exchange server is responsible for sending and receiving emails. Before uninstalling the old Exchange server, I turned off the old Exchange 2010 servers. I wanted to make sure everything was working before truly getting rid of the old servers. Every time I turn them off, I see emails sent to distribution lists sit in a queue for the old Exchange server. The emails will never send unless I turn the old server back on.

Has anyone experienced this or know what to look at or where to look?

Any guidance would be greatly appreciated.

Thank you,

Andy

EX2013 CU13 Setup crashes

$
0
0

Currently running EX2013 CU11. Downloaded EX2013 CU13. When I launch Setup, shortly after I select the default "Check for Updates" and click "Next", Setup closes with no error messages. This is logged in Application log:

Log Name:      Application
Source:        MSExchange Common
Date:          7/19/2016 3:30:37 PM
Event ID:      4999
Task Category: General
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      computer.domain.local
Description:
Watson report about to be sent for process id: 24404, with parameters: E12IIS, c-RTL-AMD64, 15.00.1210.002, ExSetupUI, M.E.Setup.AcquireLanguagePack, M.E.S.A.LanguagePackXmlHelper.GetDownloadFileInfoFromXml, System.ArgumentException, a588, 15.00.1210.002.
ErrorReportingEnabled: True

Log Name:      Application
Source:        Windows Error Reporting
Date:          7/19/2016 3:30:38 PM
Event ID:      1001
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      computer.domain.local
Description:
Fault bucket 126585538899, type 5
Event Name: E12IIS
Response: Not available
Cab Id: 0

Problem signature:
P1: c-RTL-AMD64
P2: 15.00.1210.002
P3: ExSetupUI
P4: M.E.Setup.AcquireLanguagePack
P5: M.E.S.A.LanguagePackXmlHelper.GetDownloadFileInfoFromXml
P6: System.ArgumentException
P7: a588
P8: 15.00.1210.002
P9:
P10:

Attached files:
C:\ExchangeSetupLogs\ExchangeSetupWatson.log
C:\ExchangeSetupLogs\ExchangeSetup.msilog
C:\Users\crescent\AppData\Local\Temp\7f84a5e7-c77c-4c31-85c7-1a91951f7b10\report.txt
C:\Users\crescent\AppData\Local\Temp\7f84a5e7-c77c-4c31-85c7-1a91951f7b10\report.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_c-RTL-AMD64_56526c72eec815b072d8559d2e5921ebdf3191_75d3c5af

Analysis symbol:
Rechecking for solution: 0
Report Id: a681aa11-4def-11e6-9438-00155d01de00
Report Status: 0
Hashed bucket: cf32413a69388d6fded3fa3ae89f6ae2

Log Name:      Application
Source:        Windows Error Reporting
Date:          7/19/2016 3:30:38 PM
Event ID:      1001
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      AVSI-EX2013.AVSIAV
Description:
Fault bucket 126585538899, type 5
Event Name: E12IIS
Response: Not available
Cab Id: 0

Problem signature:
P1: c-RTL-AMD64
P2: 15.00.1210.002
P3: ExSetupUI
P4: M.E.Setup.AcquireLanguagePack
P5: M.E.S.A.LanguagePackXmlHelper.GetDownloadFileInfoFromXml
P6: System.ArgumentException
P7: a588
P8: 15.00.1210.002
P9:
P10:

Attached files:
C:\ExchangeSetupLogs\ExchangeSetupWatson.log
C:\ExchangeSetupLogs\ExchangeSetup.msilog
C:\Users\crescent\AppData\Local\Temp\7f84a5e7-c77c-4c31-85c7-1a91951f7b10\report.txt
C:\Users\crescent\AppData\Local\Temp\7f84a5e7-c77c-4c31-85c7-1a91951f7b10\report.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_c-RTL-AMD64_56526c72eec815b072d8559d2e5921ebdf3191_75d3c5af

Analysis symbol:
Rechecking for solution: 0
Report Id: a681aa11-4def-11e6-9438-00155d01de00
Report Status: 0
Hashed bucket: cf32413a69388d6fded3fa3ae89f6ae2

The 2 ExchangeSetupLog files only have data from past installs. The folder in %temp% doesn't exist. None of the files are available in the WER folder. So all I have to go by is the Application log events.

If I elect not to check for updates, Setup proceeds.

If it's not an easy fix I'll proceed without checking for updates, but any idea what I should be looking for?

TIA

Exchange 2013 SSL Certs

$
0
0
My exchange Servers have lost all SSL Certs, We are in testing so we are just using self signed certs, My first exchange server is giving me error on the WEB Management Service and wont allow it to start, the error i find is

Microsoft Exchange could not load the certificate with thumbprint of E53D989B8A448375E903A0AB7CCC823A42B0F076 from the personal store on the local computer. This certificate was configured for authentication with other Exchange servers. Mail flow to other Exchange servers could be affected by this error. If the certificate with this thumbprint still exists in the personal store, run Enable-ExchangeCertificate E53D989B8A448375E903A0AB7CCC823A42B0F076 -Services SMTP to resolve the issue. If the certificate does not exist in the personal store, restore it from backup by using the Import-ExchangeCertificate cmdlet, or create a new certificate for the FQDN or the server enabled for SMTP by running the following command: New-ExchangeCertificate -DomainName serverfqdn -Services SMTP. Meanwhile, the certificate with thumbprint 0186F48794A78EA5E7CE3F9351B3E394D1AF63A7 is being used. I have recreated self signed certs in the EAC with the server FQDN as well as the externam FQDN, but this did not solve my issue, I am very new to exchange and am learing as i go so any help with this issue would be much appriciated.

Thanks


Devin Berard I.T Support Renfrew Victoria Hospital, Renfrew ON berardd@renfrewhosp.com

Office 365 migration data transfer

$
0
0

Hi,

We have an Exchange 2010 environment with an Exchange 2013 hybrid server over an ExpressRoute connection. Migrations to Office 365 is running smoothly, albeit a bit slow, but in general it's working well.

My question is around the type of data that is being sent between the hybrid server and O365 during the migration process. We have been asked to report on ExpressRoute utilisation, but all our network monitoring tools as well as those of the ISP shows no significant line utilisation during migration. Based on data volume (GB's) on the ExpressRoute we can see that data is traveling the correct way, but apart from the normal working hours spike, we cannot see any data.

Does the migration use a different file type or protocol for migrations, or is the packets just so small that it doesn't show significant data?

Thomas


Change the Internal URL for Exchange server 2010.

$
0
0

Hi Guys,

For the Migration of the Exchange server 2010 , I need to change the Internal URL for exchange services.

Current Setup: EX2010: CAS

                         EX2010B: Mailbox, HubTransport

At the Moment my Internal URL are like this.

https://svv-ex2010.domain.com/owa
https://svv-ex2010.domain.com/ecp
https://svv-ex2010.domain.com/OAB
https://svv-ex2010.domain.com/Micorsoft-Server-ActiveSync
https://svv-ex2010.domain.com/Autodiscover/Autodiscover.xml

and i am Planning to have more than 2 Client access server and since this is the migration of Exchange 2010 server. I want to change the Internal URL's with

https://mail.domain.com/owa
https://mail.domain.com/ecp
https://mail.domain.com/OAB
https://mail.domain.com/Micorsoft-Server-ActiveSync
https://mail.domain.com/Autodiscover/Autodiscover.xml

So for that I have created the DNS A Records with the Current Client Access ServerIP :192.168.1.10

I have also made the DNS-Resolve query to to check if i get the result or not and here is the Output.


PS C:\Users\test_admin> Resolve-DnsName imail

Name                                           Type   TTL   Section    IPAddress
----                                           ----   ---   -------    ---------
mail.domain.com                                A      3600  Answer     192.168.1.10(Current Ex )
mail.domain.com                                A      3600  Answer     192.168.1.11 (In future)


so i think i am ready with the New Namespace. (mail.domain.com) and later i can assign this Name spaces to all the services.

But my Problem comes at the Point of SSL Certificate. For Internal Clients we are using Self Signed Certificate with Private CA.we have Internal AD CS Services.

the Current SSL certificate which is being used at the moment doesn't have themail.domain.com as SAN Name.

so I am bit confused with Whole Process, how should i start here.

As far as i understood i need to re-request the certificate and then use the new Certificate with new SAN Name: mail.domain.com.

and then change the Internal URL of the Exchange server.

Guys,Please Help me and give me some tips , My problem is really complicated for me. i dont want to disturb the running workflow, therefore i am trying to prepared for all small issue.

it will be really nice if you guys can give me some tips about requesting the New Certificate with Correct SAN name and change the Internal URL for the migration.





2010 -> 2013 Public Folder migration failed - Property Expression isn't valid

$
0
0

We just migrated from 2003 to 2010, and now on to 2013.  I have Exchange 2013 CU3 installed, and all mailboxes moved.  When trying to move the public folders, I'm getting an error about DataValidationException.  Property expression <PF Name with spaces> isn't valid......

Many articles refer to a mail-enabled public folder with spaces can't have spaces in the alias.  This is NOT a mail-enabled public folder, so there isn't an alias that I can find.

Any ideas?

Thanks!

--Kent

Exchange 2013 upgrade failed on un-resolvable MSExchangeADTopology error

$
0
0

We have two domain controller in the building, that are all our servers.

I have exchange 2013 CU6 installed on one domain controller.

when I tried to upgrade to CU12, failed on the error below. After that, exchange server cannot start at all.

Had to use server bare metal recovery to get server back.

Tried again with CU13, failed again with same error.

can any expert help on get this upgrade?

thank you so much for your help.

BTW, there was Anti-virus program on the server when I installed CU12. After it failed, I uninstalled anti-virus app. Failed again on 2nd try with CU13.

Error:
The following error was generated when “$error.Clear();
if (!(get-service MSExchangeADTopology* | where {$_.name -eq “MSExchangeADTopology”}))
{
Install-ADTopologyService
}
else
{
Update-ServiceExecutable -ServiceName:MSExchangeADTopology -Executable:”Microsoft.Exchange.Directory.TopologyService.exe”
invoke-expression “sc.exe config MSExchangeADTopology depend= NetTcpPortSharing”
Uninstall-TopologyService
}
” was run: “System.Management.Automation.CommandNotFoundException: The term ‘sc.exe’ is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

at System.Management.Automation.CommandDiscovery.LookupCommandInfo(String commandName, CommandTypes commandTypes, SearchResolutionOptions searchResolutionOptions, CommandOrigin commandOrigin, ExecutionContext context)
at System.Management.Automation.CommandDiscovery.LookupCommandProcessor(String commandName, CommandOrigin commandOrigin, Nullable`1 useLocalScope)
at System.Management.Automation.ExecutionContext.CreateCommand(String command, Boolean dotSource)
at System.Management.Automation.PipelineOps.AddCommand(PipelineProcessor pipe, CommandParameterInternal[] commandElements, CommandBaseAst commandBaseAst, CommandRedirection[] redirections, ExecutionContext context)
at System.Management.Automation.PipelineOps.InvokePipeline(Object input, Boolean ignoreInput, CommandParameterInternal[][] pipeElements, CommandBaseAst[] pipeElementAsts, CommandRedirection[][] commandRedirections, FunctionContext funcContext)
at System.Management.Automation.Interpreter.ActionCallInstruction`6.Run(InterpretedFrame frame)
at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)”.



Exchange Migration Project

$
0
0

Good Day,

We are experiencing some issues with a migration we are doing, as such I figured I would post here with hopes that some of you can assist me with some of the problems we are having. In an effort to provide some insight we are attempting to migrate from a 2010 (2 CAS, 2 MBX) environment, to that of a 2013 (2 CAS, 2 MBX). the 2010 environment has been inherited, and was built before my time.

To date I have built out the new environment (2013) to where it co-exists within the existing infrastructure, I have migrated all settings and policies associated within the infrastructure to the new environment, all of this has been done without incident. I have configured mail flow to allow for the sending and receiving of mail from a mailbox within the 2013 environment. The problem we appear to be having is with proxying back to the legacy environment when pointed to the new (the modification of local hosts file to point to new exchange servers). It doesn’t work, I cannot connect to a mailbox that lives in the 2010 environment when pointed to the new…it continually prompts for credentials.

Another issue we appear to be having is this, I built a new outlook (2013) profile and pointed to the mailbox that lives on the 2013 servers, while it connects it is not without incident….it consistently prompts for credentials even though it shows as connected, I can cancel out of this and remain connected I’m just wondering why this happens (side note, I understand why it would prompt for credentials as I’m not logged on to the computer as that user, I don’t understand why it continues to prompt).

Regarding the proxy issue, I reached out to Microsoft Support and got some guidance (some of which I don’t fully understand, hence part of the reason I am writing this). What we found was that the legacy environment was built with a cas array. From what I am told in order for the proxying back to the legacy environment when a client is pointed to the new the cas array will need to be severed. I have never worked with cas array’s throughout my career, given that I am told that breaking this will sever connectivity to some of our legacy clients (outlook 2007 / 2010) I am a little intimidated by this.

Has anyone here encountered anything like this?, if so what steps did you take to resolve? 

The local domain needs to be prepared using Setup /PrepareDomain before server roles can be installed

$
0
0

Hello Everyone,

I've been installing Exchange servers since Exchange 5.5. I'm now installing Exchange 2013 with SP1 that will coexist with one Exchange 2010 SP3 server. I'm installing it on 2012 R2 Enterprise Edition. There is a root domain and one child domain. The Exchange Server is in the child domain.  Even though I've run the .\setup PrepareSchema, AD and domain and all were successful I still get the message below when running Exchange setup. If I look at what /preparedomain does it seems like it has done what is needed. I've run the /prepareschema, /preparead and /preparealldomains in the root domain & have even run /preparedomain over and over in the child domain. Like I said everytime I run these they are successful. Oh and my account belongs to all the right groups needed to run these. Any ideas would be appreciated!

The local domain needs to be prepared using Setup /PrepareDomain before server roles can be installed.

For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DomainPrepRequired.aspx


Imap and pop3 outlook connectivity issue.

$
0
0

Team,

I am having a problem while configuring pop3 setting on user desktop. Its giving my error for outgoing smtp server connection.

Please help to fixup.

Exchange 2013 CAS not proxying connections to Exchange 2010 during coexistence

$
0
0

Hello all,

for the second time, I am performing an Exchange 2010 to 2013 migration. For the second time, coexistence is not working as it should.

I have followed the migration assistant at https://technet.microsoft.com/en-us/exdeploy2013 to the T and it did not work. I did a reinstall of Exchange 2013 and followed other guides with no avail.

The environment is Exchange 2010 SP3 along side of Exchange 2013 SP1 (I will spare reasons for not going beyond SP1).

The most notable symptom of this problem is that when I access OWA on the 2013 CAS, I sign in using 2010 Credentials. I am then taken to https://mail.domain.com/owa/auth.owa -- where it hangs on a blank white page in Google Chrome, or the "This page can't be displayed" in IE.

OutlookAnywhere IS configured on Exchange 2010 in this scenario.

Does anyone have any suggestions or tips on where to look for something wrong?

Migrate old data to archive

$
0
0

Hi guys,

Scenario question

Current environment Exchange 2013 with large mailboxes and very old emails

New environment Exchange 2016 with Default MRM Policy / Personal 1 year move to archive policy

1) Is that policy configured on user, databaser or server level?

2) Will the old emails migrated to an in-place archive since it was originally received in the old environment for over 1 year ago or will the 1 year trigger from when it was migrated into the new environment?

3) is it possible to migrate emails newer than one year to the primary mailbox and emails older than 1 year directly into the in-place archive? (if the policy makes this separation one might not have to filter this migration, everything goes into the primary mailbox)

thanks!

Viewing all 7008 articles
Browse latest View live