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

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/


Exchange 2013 enable forwarding option does not save the recipient address

$
0
0

Hi,

I am having issue on Exchange 2013 that unable to save forwarding recipient address in mail flow option. While browsing on Forward address and select recipient address it shows the blank and do not show the address.

Can anyone suggest how to save the recipient address in mail flow.

Thanks

Exchange STD 2013 key for Exchange STD 2010 install

$
0
0
We have an exchange std 2013 key and installed exchange std 2010 sp1, because we thought they were backwards compatiable; however the key for 2013 does not work for 2010. Were we wrong in our thinkging?

Default Folders Policy/Items retention period not respected ?

$
0
0

Hello, 

We have Exchange Server 2007 SP3 and we've set up a default folders policy to erase all mailbox content older than 31 days. 

However in three mailboxes we've sampled this policy isn't properly applied : the mailboxes had mails newer than 31 days deleted ( some 20 days, some 28 days, mine had only 14 days old mails !

Can you please explain to me why this is happening? 

Exchange 2013 in a lab vm, unable to send externally, message is queued on Exchange server

$
0
0

Hello,

I have an Exchange 2013 server Im just testing out and labbing on. I'm able to send mail internall through OWA and it works fine, I'm trying to send to external addresses, for now just live.com and it doesnt seem to leave my server. I get the following error:

3/31/2015 9:09AM winsvr12-lab.sethslab.local
The message has been queued on server 'winsvr12-lab.sethslab.local' since 3/31/2015 4:09:01am (UTC-10:00) Hawaii. The last attempt to send the message was at 3/31/2015 4:24:40am (UTC-10:00)Hawaii and generated the error '[{LRT=};{LED=};{FQDN=};{IP=}]'.

I have went through and setup my Send Connector as follows:
General - Connector is enabled
Delivery - Network Settings is to use the MX record
Scoping - Address space type is SMTP, Domain is set to *, and Cost is 1. The source server is my winsvr12-lab.sethslab.local which has both the Mailbox and CAS roles installed.

In the Servers > DNS Lookups, I have set the External DNS lookups to use the DNS server configured on my Hyper-V adapter.

My server roles are IIS, AD DS, and DNS(have not set up any of my own records yet).

Exchange 2010 to 2013 ADprep stopped at 37 percent

$
0
0
Running fine and stopped at 37%. Permissions are good and everything seems fine. The install logs shows the schema getting set for exchange 2013 and then ...

Exchange 2013 and 2007 coexistence with ISA 2006

$
0
0

Short and simple question: Should this configuration work, am I just missing something stupid or do we need to rethink the entire architecture?Should Exchange 2013 directly internet-facing CAS be able to redirect 2007 mailbox users to ISA-published Exchange 2007 OWA without double authentication in coexistence scenario?

I have a Exchange 2007 environment which works just fine:
- Two CAS servers and two mailbox servers
- OWA and AS are published to internet with an ISA 2006 gateway.
- ISA is configured to have FBA authentication on web listener, doing LDAP auth from two domains (the same domain where the Exchange servers are and an another domain in different forest) and delegating to Exchange as basic auth.
- On Exchange FBA is disabled for OWA, Basic and Integrated enabled.

Now we would like to introduce an Exchange 2013 server to the environment, switch client access over to it and have users accessing their OWA emails on the Exchange 2007 mailboxes before the mailboxes are transferred to Exchange 2013. ISA 2006 will be decommissioned together with the Exchange 2007 environment and Exchange 2013 will be directly internet facing, but at least the first attempt to get this to work failed.

We have two separate single-name certificates, let's call them mail.company.com and mail2007.company.com. The later one is for the legacy email, and first one is used and has been used for the actual client connections.

- mail.company.com is assigned to Exchange 2013 CAS, mail2007.company.com to ISA server listener.
- DNS records to mail.company.com are switched to point to Exchange 2013 CAS public IP, mail2007.company.com to ISA public IP.
- ISA rules were updated to accept the mail2007.company.com host name and multiple different authentication configurations were tried.
- Exhange 2007 OWA and other virtual directories were updated to use mail2007.company.com as the external URL.

I could get Exchange 2013 OWA to authenticate the user and forward the connection to ISA FBA, but with any configuration I couldn't get rid of double authentication. Disabling ISA FBA and letting client authenticate with Exchange directly didn't work out any better.


Exchange 2010 Server in Resource Forest Migration to User Forest as Exchange 2013

$
0
0

Hi,

I am working on the planning to achieve the cross forest migration for exchange 2010 with an upgrade to 2013.

in my environment Exchange 2010 is deployed in Resource forest and all the mailboxes are linked with their users in user forest.

now problem is how to get this migration done and how these linked mailboxes will be connected to their users in user forest after migration.

need food for thought...


Regards, Owais


Recipient Containers Not Updating in EAC.

$
0
0

I have 2 CAS and 2 MBX servers installed in the parent Root Domain with 2 child domains. I have added OUs to the clildren domains and they will not show up when trying to add a mailbox on the root domain server. I am unable to even see the new OUs. Also, if I try to create a user from Exchange, I cannot place them in the child domain OUs. Where is my design lacking here? I really need some help with this. Thanks in advance.

Lance Lingerfelt

Event 2112 MSExchange ADAcces new 2013 CoExist 2007

$
0
0

Greetings all and thanks in advance,

Migrating from EX2007 to EX2013 (CU7), in a Co-Existence type mode.  I have a flat domain, with several domain controllers at various branches across the state.  I ran setup.exe /prepareAD and /PrepareDomain prior to the installation at the location where the Exchange server is held.  Install completed and for the most part I'm operational.  The EX2013 server is giving me the Event 2112 for many, if not all of my other domain controllers in our environment:

  Log Name:      Application
  Source:        MSExchange ADAccess
  Date:          4/1/2015 7:19:07 AM
  Event ID:      2112
  Task Category: Topology
  Level:         Warning
  Keywords:      Classic
  User:          N/A
  Computer:      E15M01.HALFF.AD
  Description:
  Process Microsoft.Exchange.Directory.TopologyService.exe (PID=3676). The Exchange computer     DomainController02.Domain.AD does not have Audit Security Privilege on the domain controller   DomainController02.Domain.AD. This domain controller will not be used by Exchange Active Directory Provider.
  Event Xml:
  <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

I manually ran setup.exe /PrepareDomain on one of the DC's that was showing up in the event log.  After running this on that DC, Exchange was no longer reporting the 2112 error for that DC. 

What have I missed during the installation?  Doesn't sound like the domain is properly replicating this to the other domain controllers.  When I manually ran setup /preparedomain on another DC outside of this branch, I was prompted that "Windows Management Framework 3.0" was not installed.  Setup completed as expected after this component was installed.  If the other DCs are missing this component, could this perhaps be the reason why the Exchange info was not replicated to the other DCs?

Thanks,

Willis

POP/IMAP issue Exchange 2013

$
0
0

Hi,

I have started the migration of Exchange 2010 to Exchange 2013. Exchange 2010 is single server with all roles and Exchange 2013 with 1 CAS and 1 Mailbox. Initially plan was to verify the Windows XP users can connect with Exchange 2013 but there was a lot of issues and stop XP machines migration. Windows 7 machines are working perfectly without any issue.

Now decided to configure POP/IMAP on XP machines. The test of incoming POP/IMAP is fine and receiving emails from internal to external domains but the SMTP is giving errorSend test e-mail: Your server does not support the connection encryption type specified. Try changing the encryption method. Contact the administrator of the mail server or Internet service provider for further assistance.

Can some guide what I am missing during the configuration.

Thanks

Updating 2013 SP1 to CU8 Error - Set-SharedConfigDC Fails

$
0
0

I have two 2012 servers running Exchange 2013 SP1. They are both multi-role servers and are members of a DAG and are also load-balanced behind a Citrix Netscaler. I was ready to begin moving my mailboxes from 2010 to 2013 when I ran into a problem. In order to try and resolve this problem, I attempted to update to CU8.

(After a successful mailbox move, I am unable to open my own mailbox in Outlook (2013 or 2010). I receive an error that "the set of folders cannot be opened". I am, however, able to view my mailbox from another migrated mailbox which has "full access" to it. After some unsuccessful attempts to figure it out, I decide that I should probably update Exchange to the latest before I start messing with other things. Bad mistake.)

The CU8 setup fails in the Set-SharedConfigDC step with the error "No Minimal Required Number of Suitable Directory Servers Found in Forest".

I've read that I need IPv6 enabled. It had previously been "unchecked" in the NIC settings of the Exchange and DC servers. I've enabled it on the Exchange server and two of the DCs one of which is a GC. No luck. I've also added the "Exchange Servers" and "Exchange Subsystem" groups to the AD "Administrators" group which was another suggestion I received.

The DCs are in a different subnet from the Exchange server.  I am running at domain functional level of 2003.

And just to reiterate: I had successfully installed Exchange 2013 SP1 with IPv6 "unchecked" on all Exchange and DC servers before the CU8 update failed.

-edit- Here's the relevant section of the log:

[04/01/2015 09:50:52.0841] [2] Active Directory session settings for 'Set-SharedConfigDC' are: View Entire Forest: 'True', Configuration Domain Controller: 'AC-DC1.mydomain.network', Preferred Global Catalog: 'AC-DC1.mydomain.network', Preferred Domain Controllers: '{ AC-DC1.mydomain.network }'
[04/01/2015 09:50:52.0841] [2] User specified parameters:  -DomainController:'AC-DC1.mydomain.network' -ErrorVariable:'setSharedCDCErrors' -ErrorAction:'SilentlyContinue'
[04/01/2015 09:50:52.0841] [2] Beginning processing Set-SharedConfigDC
[04/01/2015 09:51:47.0056] [2] The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.network Site Default-First-Site-Name and connected Sites..
[04/01/2015 09:51:47.0056] [2] No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.network Site Default-First-Site-Name and connected Sites.
[04/01/2015 09:51:47.0056] [2] The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.network Site Default-First-Site-Name and connected Sites..
[04/01/2015 09:51:47.0056] [2] No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.network Site Default-First-Site-Name and connected Sites.
[04/01/2015 09:51:47.0071] [2] Ending processing Set-SharedConfigDC
[04/01/2015 09:51:47.0071] [2] Beginning processing Write-ExchangeSetupLog
[04/01/2015 09:51:47.0071] [2] An error ocurred while setting shared config DC. Error: The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.network Site Default-First-Site-Name and connected Sites..
[04/01/2015 09:51:47.0071] [2] Ending processing Write-ExchangeSetupLog
[04/01/2015 09:51:47.0087] [2] Beginning processing Write-ExchangeSetupLog
[04/01/2015 09:51:47.0087] [2] Waiting 30 seconds before attempting again.
[04/01/2015 09:51:47.0087] [2] Ending processing Write-ExchangeSetupLog
[04/01/2015 09:52:17.0100] [2] Active Directory session settings for 'Set-SharedConfigDC' are: View Entire Forest: 'True', Configuration Domain Controller: 'AC-DC1.mydomain.network', Preferred Global Catalog: 'AC-DC1.mydomain.network', Preferred Domain Controllers: '{ AC-DC1.mydomain.network }'
[04/01/2015 09:52:17.0100] [2] User specified parameters:  -DomainController:'AC-DC1.mydomain.network' -ErrorVariable:'setSharedCDCErrors' -ErrorAction:'SilentlyContinue'
[04/01/2015 09:52:17.0100] [2] Beginning processing Set-SharedConfigDC
[04/01/2015 09:53:11.0367] [2] The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.network Site Default-First-Site-Name and connected Sites..
[04/01/2015 09:53:11.0367] [2] No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.network Site Default-First-Site-Name and connected Sites.
[04/01/2015 09:53:11.0367] [2] The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.network Site Default-First-Site-Name and connected Sites..
[04/01/2015 09:53:11.0367] [2] No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.network Site Default-First-Site-Name and connected Sites.
[04/01/2015 09:53:11.0367] [2] Ending processing Set-SharedConfigDC
[04/01/2015 09:53:11.0382] [2] Beginning processing Write-ExchangeSetupLog
[04/01/2015 09:53:11.0382] [2] An error ocurred while setting shared config DC. Error: The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.network Site Default-First-Site-Name and connected Sites..
[04/01/2015 09:53:11.0382] [2] Ending processing Write-ExchangeSetupLog
[04/01/2015 09:53:11.0382] [2] Beginning processing Write-ExchangeSetupLog
[04/01/2015 09:53:11.0382] [2] Waiting 30 seconds before attempting again.
[04/01/2015 09:53:11.0398] [2] Ending processing Write-ExchangeSetupLog
[04/01/2015 09:53:41.0412] [2] Beginning processing Write-ExchangeSetupLog
[04/01/2015 09:53:41.0412] [2] [ERROR] Unable to set shared config DC.
[04/01/2015 09:53:41.0412] [2] [ERROR] Unable to set shared config DC.
[04/01/2015 09:53:41.0412] [2] Ending processing Write-ExchangeSetupLog
[04/01/2015 09:53:41.0428] [1] The following 1 error(s) occurred during task execution:
[04/01/2015 09:53:41.0428] [1] 0.  ErrorRecord: Unable to set shared config DC.
[04/01/2015 09:53:41.0428] [1] 0.  ErrorRecord: System.Exception: Unable to set shared config DC.
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
   at Microsoft.Exchange.Management.Deployment.WriteExchangeSetupLog.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)
[04/01/2015 09:53:41.0428] [1] [ERROR] The following error was generated when "$error.Clear();
          $maxWait = New-TimeSpan -Minutes 8
          $timeout = Get-Date;
          $timeout = $timeout.Add($maxWait);
          $currTime = Get-Date;
          $successfullySetConfigDC = $false;

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

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

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

          if( -not $successfullySetConfigDC)
          {
            Write-ExchangeSetupLog -Error "Unable to set shared config DC.";
          }" was run: "System.Exception: Unable to set shared config DC.
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
   at Microsoft.Exchange.Management.Deployment.WriteExchangeSetupLog.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
[04/01/2015 09:53:41.0428] [1] [ERROR] Unable to set shared config DC.
[04/01/2015 09:53:41.0428] [1] [ERROR-REFERENCE] Id=AllADRolesCommonServiceControl___ee47ab1c06fb47919398e2e95ed99c6c Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[04/01/2015 09:53:41.0428] [1] Setup is stopping now because of one or more critical errors.
[04/01/2015 09:53:41.0428] [1] Finished executing component tasks.
[04/01/2015 09:53:41.0522] [1] Ending processing Install-BridgeheadRole
[04/01/2015 10:25:25.0150] [0] CurrentResult setupbase.maincore:396: 0
[04/01/2015 10:25:25.0150] [0] End of Setup
[04/01/2015 10:25:25.0150] [0] **********************************************

Problem: Mixed Exchange 2007 / 2013 CAS Servers with wildcard certificates in Europe and non-wildcard Certficate in China

$
0
0

Hi,

we have following problem. We have a mixed multi-domain one-forest AD environment. We also have still a mixed exchange 2007 / 2013 environment. We also have different CAS Servers for 2007 SP3 (RU15) and 2013 (CU8) in europe and one 2007 SP3 (RU15) CAS Server in China, because of bad connection to Europe. For the Migration to 2013 in Europe we installed a wildcard-certificate *.xyz.com and used the Set-OutlookProvider EXPR -CertPrincipalName msstd:*.xyz.com, so the wildcard certificate is accepted. Everything in Europe works fine, inside and outside also between exchange 2007 and 2013 (both CAS Server 2013 and 2007 use the same wildcard certificate). But since the change of the Set-OutlookProvider EXPR we are facing problems with our CAS Server in China, because this server has a different non-wildcard certificate and a different domain name (cas-server.xyz-china.com instead xyz.com). Now we have the problem that this Chinese CAS server the Outlook Anywhere does not work anymore and prompts always for the username. As I see it is because of the EXPR change. Is it possible to set the the Outlook-Provider EXPR per Cas-Server ? (They also have their own Autodiscover on this front-end server). Because I see that the Outlook-Provider can only be stored forest-wide.
If not the other solution would be to register the chinese cas server in our xyz.com domain and use the same wildcard certificate on this system right ?
Any help would be appreciate….

Exchange 2013 - schema prep (net assambly error)

$
0
0

Setup.exe /prepareschema /IAcceptExchangeserverlicenseterms

gives error:  [ERROR] An attempt was made to load an assembly from a network location which would have caused the assembly to be sandboxed in previous versions of the .NET Framework. This release of the .NET Framework does not enable CAS policy by default, so this load may be dangerous. If this load is not intended to sandbox the assembly, please enable the loadFromRemoteSources switch. Seehttp://go.microsoft.com/fwlink/?LinkId=155569 for more information. ; Any hints how to solve this?


bostjanc

Applying CU4 for Exchange 2013 SP1 in a mixed 2010 / 2013 Environment

$
0
0
We're planning to apply Exchange 2013 SP1 CU in our mixed 2010 / 2013 environment. We'd also like to apply Exchange 2010 SP3 Rollup 5 as well. Are there any gotchas or best practices on what update to apply first?

Orange County District Attorney


Erreur dans l'étape 10

$
0
0
SVP quelqu'un peut m'aider?

Erreur :
L'erreur suivante est survenue lors de l'exécution de "$error.Clear(); 
          if (!$RoleIsDatacenter)
          {
            $arbUsers = @(get-user -Filter {lastname -eq "MSExchApproval 1f05a927-3be2-4fb9-aa03-b59fe3b56f4c"} -IgnoreDefaultScope -ResultSize 1);
            if ($arbUsers.Length -ne 0)
            {
              $mbxname = $arbUsers[0].name;
              $mbxs = @( get-mailbox -arbitration -Filter {name -eq $mbxname} -IgnoreDefaultScope -resultSize 1 );
              if ( $mbxs.length -eq 0)
              {
                $dbs = @(get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
                if ($dbs.Length -ne 0)
                {
                  enable-mailbox -Arbitration -identity $arbUsers[0] -database $dbs[0].Identity;
                }
              }
            }
          }
        " : "Le serveur actif de la base de données Mailbox Database 1944627809 (949279cd-baab-43ef-afbf-9705fde6860d) est introuvable.".

Deploy Exchange 2013 in multiple domain scenario

$
0
0
I currently have an AD forest abc.com under which there are 2 domains def.abc.com and ghi.abc.com. Exchange 2013 is deployed in domain ghi.abc.com. Now I want to add a third domain jkl.abc.com and use exchange 2013 for it. I want to use the same exchange which is currently deployed in ghi.abc.com by adding  new servers and use the same namespace etc. Do I need to do anything special for it or just add servers and start creating mailboxes.

What process?

$
0
0


Error:

Setup can't continue with the upgrade because the SFSEM (10884) has open files. Close the process, and then restart Setup.

For more information, visit: 

How can this be helpful?

 

http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.ProcessNeedsToBeClosedOnUpgrade.aspx



E2K13 Maintenance Mode

$
0
0

I have read articles on how to prepare and put an E2K13 DAG member into maintenance mode.  I have just completed putting a DAG member into maintenance mode; however, when I ran cmdlet: Set-MailboxServer <servername>  -DatabaseCopyActivationDisabledAndMoveNow   which is supposed to take care of activating databases on the other node member , it did not work and I had to manually move the databases to another node member.

Am I running the correct cmdlet or can you tell me what I may have done wrong:

Articles read: 
http://blogs.technet.com/b/nawar/archive/2014/03/30/exchange-2013-maintenance-mode.aspx

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

http://vanhybrid.com/2013/11/28/script-putting-exchange-server-2013-into-maintenance-mode/

http://letsexchange.blogspot.com/2013/03/exchange-2013-maintenance-mode.html

delete email prior to ex2013 migration

$
0
0

I am migrating to exchange 2013 from ex2007sp3.  Prior to moving mailboxes to the ex13 server, I have been tasked with deleting messages from the Exch2007sp3 database older than 90 days. 

This is my pshell cmd so far:

Get-Mailbox -Database "private information store" | Export-Mailbox -EndDate “1/1/2015” -ExcludeFolders "\Calendar" -DeleteContent -BadItemLimit 100

I plan to change the Delete Item Retention to 0 days so that the messages are truly gone.

Does anyone have a better suggestion?

 Thanks

Viewing all 7008 articles
Browse latest View live


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