Quantcast
Viewing all 7008 articles
Browse latest View live

Exchange 2013 Licensing for DAG

Hi,

I have a single server with Exchange 2013 Enterprise license applied.  I have created two new servers on a newer OS that I have setup as a DAG.  Can I apply the same license to these new servers without running into issues? I will be decommissioning the old Exchange server once I have moved the mailboxes over.  The two new servers are currently running a trial version.

Thanks

Migrating from Communigate Pro to Exchange 2013

Hi all,

My company is currently using Communigate Pro and 90% of users use web-based email, the rest use Outlook PST. We currently need to migrate all the users' mailboxes to Exchange 2013. I have already tried one tool namely Transend Migrator which does the job but the licensing is really expensive. Anyone can please propose an alternative, preferably free one, how I can do this. Thanks in advance.

Regards,

Khaleel

Exchange 2010 to 2013 Mailbox migrations with Archive - using wrong MRS Servers

We have multiple sites all running their own Exchange 2010 servers with all Archive mailboxes hosted in our primary datacentre.

We are now migrating those sites to new Exchange 2013 servers, and the Primary Mailboxes are being moved to local Exchange 2013 servers, and the Archives are being moved to Exchange 2013 Archive Databases hosted in the primary datacentre.

For example, user is in Site B with Archive hosted in Site A. New Exchange server is in Site B. New Archive Exchange Server is in Site A.

When I instigate the move, the move request is using the MRS Server in Site B, which is moving the Primary Mailbox nicely. However, and here is the big issue, it is moving the archive in Site A, via Site B, back to Site A.

That is a real issue when the network link between site A and site B can only provide about a 10MB link, due to everything else running on the link.

How can we get the Primary to use an MRS Server in its own site, and the Archive move to use an MRS Server in its own site, without doing the move via the MRS Server in a different site?

We can't change the MRS Server setting using the set-moverequest and we can't move the Primary with one command and the Archive with another as they complain about being on 2010 or 2013 only, not one on each.

Please help, this is getting to be a big issue

Thanks

On Behalf and Full access users list

Please help me with the command line which gives me the list of users who has send on behalf and Full access on others mailbox.

:Error: Configuration file is not well-formed XML ERROR] Filename: \\?\C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\OAB\web.config

Hi All,

I got an error message saying below while installing step 13 of 15: Client access role: client access front end service while installing Exchange2k13 SP1 on Windows 2k12 server.

Error:
The following error was generated when "$error.Clear(); 
          $InternalOabUrl = "https://" + $RoleFqdnOrName + "/OAB";
          new-OabVirtualDirectory -Role ClientAccess -DomainController $RoleDomainController -InternalUrl $InternalOabUrl;
          get-OabVirtualDirectory -server $RoleFqdnOrName -DomainController $RoleDomainController | set-OabVirtualDirectory -OAuthAuthentication:$true;
        " was run: "Filename: \\?\C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\OAB\web.config
Line number: 613
Error: Configuration file is not well-formed XML

".

In the Exchange setup logs i found the below 

Processing object "EXCHANGE2K13\OAB (Default Web Site)".
[12/01/2014 01:20:12.0668] [2] [ERROR] Filename: \\?\C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\OAB\web.config
Line number: 613
Error: Configuration file is not well-formed XML


[12/01/2014 01:20:12.0668] [2] [WARNING] An unexpected error has occurred and a Watson dump is being generated: Filename: \\?\C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\OAB\web.config
Line number: 613
Error: Configuration file is not well-formed XML

Any suggestions?

Regards

Anusha

Email id not working

hi,

domain name-- galaxyroyale.com

i have changed existing hosting to new one. now i am not able to receive email. please help me how can i get cname records and mx records.

Decommission Exchange Server 2013 after migration to Office365

We had an on-premises Exchange Server 2013 failure with multiple hard disk failures.

Since we already had an Office365 E3 plan, we decided to bite the bullet and move to Exchange Online.  Since we did not have ADFS or Dirsync yet and time was against us to get email flowing as quickly as possible, we imported all the users into Office365, i.e. disconnected from our AD.

We then setup all their Outlook 2013 profiles with Office365 and imported their mailboxes from PSTs, so they are all up and running on Office365 now (still disconnected from our AD).

I would like to decommission our on-premises Exchange 2013, since our current setup is not very common, i.e. Office365 mailboxes which are not linked to our AD.

I would like some pointers and guidance how to go about this.

Thanks

Chris

Database Script

Hi,

I'm trying to create the database volumes via the exported scripts from the Exchange 2013 calculator, to try and simulate a deployment. I've scaled back for the home lab, but basically I want to use the script to create the volumes and mountpoints etc.

The spreadsheet has 4 DB's per volume and I've setup 8 DB's so it should create 2 volumes...

I run the script, it creates the first volume and first 4 DB's without any issues, then it won't create the second volume so it creates the folders in the mountpoint folder (Just not mounted...)

The VM I've setup is very basic for home testing before scaling up for clients, but has the following disk

Disk 0 = OS\Exchange etc.
Disk 1 = Offline
Disk 2 = Offline

It does the first part correctly, so what am I doing wrong?

Any help/advice would be appreciated

Michael 


CU2 installation hangs on step 9: Languages

Hi

I started the update of Exchange 2013 CU2. Everything went fine, but now it hangs since about 3 hours at "Step 9 of 18: Languages".

What can I do???

Regards
Peter

Excahnge 2010 to 2013 Migration - multiple mailboxes

Hello,

We are trying estimate the time it will take to migrate our users from Exchange 2010 to 2013.

I understand we can migrate them in multiple batches but how many are actually moving at one time?

So if i batch migrate 20 mailboxes, are all 20 moving consecutively, or are 5 moving and 15 queued?

Hope you can understand what I'm asking.

Thanks

Lee

Migrate mailbox from Exchange 2007 to Exchange 2013, mailbox stay in queue

Hi,

I'm trying to migrate a mailbox but the request is staying in queue, according to : Get-moverequest | Get-Moverequeststatistics

Configuration server Exchange 2007 SP3 :

Domain : test.com

OS : Windows 2008 server SP2 (not R2)

Firewall : OFF

Exchange roles are on separate three  servers : CAS - MAILBOX - HUB.

Configuration Server Exchange 2013 :

Domain : new.com

OS: Windows 2012 R2

Firewall : OFF

This environment is on a closed network unable to reach internet.

I have try to restart the Replication service, but it didn't worked.

I've searched a lot but i can't find any information to help me. The mailbox stays in queue....

Anyone ever had this issue?

Thanks you and have a nice day.

Only senders inside my organization in delivery management option in Distribution list

<p></p><span class="LW_CollapsibleArea_Title" jQuery18207072558190786025="117">Delivery management</span> <div class="LW_CollapsibleArea_HrDiv"><hr class="LW_CollapsibleArea_Hr" /></div><div class="sectionblock"><p>Use this section to manage who can send email to this group.</p><ul><li><p><strong>Only senders inside my organization</strong>&nbsp;&nbsp;&nbsp;Select this option to allow only senders in your organization to send messages to the group. This means that if someone outside of your organization sends an email message to this group, it will be rejected. This is the default setting</p></li></ul></div>

Senders inside set using exchange power shell

How do I set a Distribution Group to "Senders inside  my organization in delivery management” using Enchange PowerShell commands?

 

Exchange database copy

Teams,

After creating Database and adding database copy to another server as a passive  i am getting error message. Because still database is not created in passive please suggest.

The database file wasn't found after log replay. The copy will be set to failed. Database: 'T1DB09\EXMAIL02'. File Path: 'C:\ExchangeDatabase\LUN05\DB09\Mailbox Database 1.edb'.

autodiscover fails in Ex2010/Ex2013 co-existence

Dear readers,

Currently we are in the preparation phase of the migration from Exchange 2010 to Exchange 2013. I have followed the Exchange Deployment Assistant, but unfortunately it does not work as expected.

I think i might have created an autodiscover loop and I don’t know how to fix it. Our setup
2x 2010CAS 192.168.2.10, 192.168.2.11
2x 2010MBX 192.168.2.20, 192.168.2.21 (DAG01)
2x 2013CAS 192.168.2.110, 192.168.2.111
2x 2013MBX 192.168.2.120, 192.168.2.121 (DAG02)

autodiscover.ourextdomain.com for internal clients point to 192.168.2.110
webmail.ourextdomain.com for internal clients point to 192.168.2.110

For now company policy does not allow making the Exchange services available externally. So all the clients only connect internally (on the corporate network or using VPN), also webmail is only accessible internally.

On all the CAS servers (meaning both 2010 and 2013) I have set the internal and external URL for every service (EWS, ECP, OWA, OAB, ActiveSync, Autodiscover, Outlook Any Where) to point to the same external domain: webmail.ourextdomain.com and autodiscover.ourextdomain.com. (This is how I interpreted it from the Exchange Deployment Assistant).

If an internal Outlook 2010 user tries to use autodiscover to connect to his mbx on 2010, he gets httpstatus 401 and 401 errors and autodiscover to <url> failed 0x80004005, 0x800C8203 and is unable to successfully connect. An outlook 2010 user with a 2013 mbx can connect successfully.

If I change autodiscover.ourextdomain.com to point to 192.168.2.10, it is the other way around. The outlook 2010 user with 2010 mbx can connect, but the outlook 2010 user with 2013 mbx cannot.

My guess is that the configuration for the internal and external URLs is not correct, but I am not sure how to fix this. Does anyone have an idea? We have a third part wildcard certificate which I installed on all the CAS servers. This gave certificate errors at first, for some reason clients were still trying to connect to a .local server address. This seems to be fixed after I re-created the Autodiscover vdirs.

As we have had a lot of issues with the certificate (a lot of calls at the service desk) I am a little less enthusiastic about changing the internal and external URLs again, until I am a little more certain it is the right change to make.

Maybe useful info:

- Exchange 2010 did not have Outlook Anywhere enabled until I started following the Exchange deployment assistant

- Exchange 2010 has been an upgrade from Exchange 2003 (there are no Exchange 2003 servers anymore, as than I would not be able to start the 2013 installation at all).

- Running Exchange 2010 SP3 ur7, migrating to Exchange 2013 cu6

Anyone any ideas or pointers in the right direction?


Installing Exchange 2013 CU 6 failed

Hello, we have a big problem with installing CU6 on a new installed exchange 2013 server. Here's the error message:

Error:

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

          if ($RoleIsDatacenter -ne $true -and $RoleIsDatacenterDedicated -ne $true)

          {

          if (Test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue)

          {

          $sysMbx = $null;

          $name = "SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}";

          $dispName = "Microsoft Exchange";

          Write-ExchangeSetupLog -Info ("Retrieving mailboxes with Name=$name.");

          $mbxs = @(Get-Mailbox -Arbitration -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1 );

          if ($mbxs.Length -eq 0)

          {

          Write-ExchangeSetupLog -Info ("Retrieving mailbox databases on Server=$RoleFqdnOrName.");

          $dbs = @(Get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);

          if ($dbs.Length -ne 0)

          {

          Write-ExchangeSetupLog -Info ("Retrieving users with Name=$name.");

          $arbUsers = @(Get-User -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);

          if ($arbUsers.Length -ne 0)

          {

          Write-ExchangeSetupLog -Info ("Enabling mailbox $name.");

          $sysMbx = Enable-Mailbox -Arbitration -Identity $arbUsers[0] -DisplayName $dispName -database $dbs[0].Identity;

          }

          }

          }

          else

          {

          if ($mbxs[0].DisplayName -ne $dispName )

          {

          Write-ExchangeSetupLog -Info ("Setting DisplayName=$dispName.");

          Set-Mailbox -Arbitration -Identity $mbxs[0] -DisplayName $dispName -Force;

          }

          $sysMbx = $mbxs[0];

          }

          # Set the Organization Capabilities needed for this mailbox

          if ($sysMbx -ne $null)

          {

          # We need 1 GB for uploading large OAB files to the organization mailbox

          Write-ExchangeSetupLog -Info ("Setting mailbox properties.");

          set-mailbox -Arbitration -identity $sysMbx -UMGrammar:$true -OABGen:$true -GMGen:$true -ClientExtensions:$true -MailRouting:$true -MessageTracking:$true -PstProvider:$true -MaxSendSize 1GB -Force;

          Write-ExchangeSetupLog -Info ("Configuring offline address book(s) for this mailbox");

          Get-OfflineAddressBook | where {$_.ExchangeVersion.CompareTo([Microsoft.Exchange.Data.ExchangeObjectVersion]::Exchange2012) -ge 0 -and $_.GeneratingMailbox -eq $null} | Set-OfflineAddressBook -GeneratingMailbox $sysMbx.Identity;

          }

          else

          {

          Write-ExchangeSetupLog -Info ("Cannot find arbitration mailbox with name=$name.");

          }

          }

          else

          {

          Write-ExchangeSetupLog -Info "Skipping creating E15 System Mailbox because of insufficient permission."

          }

          }

        " was run: "Microsoft.Exchange.ProvisioningAgent.RusException:  Failed to generate proxy address. Additional information: General Error.

   at Microsoft.Exchange.DefaultProvisioningAgent.Rus.SingleProxySession.CheckReturnCode(ReturnCode rc)

   at Microsoft.Exchange.DefaultProvisioningAgent.Rus.SingleProxySession.CheckProxy(RecipientInfo pRecipientInfo, String pwszProxyAddr)

   at Microsoft.Exchange.DefaultProvisioningAgent.Rus.ProxySession.CheckSingleProxy(ProxyAddressTemplate baseAddress, RecipientInfo recipientInfo, ProxyAddress oldProxyAddress)

   at Microsoft.Exchange.DefaultProvisioningAgent.Rus.ProxySession.GenerateProxies(IConfigurationSession configSession, IRecipientSession recipientSession, IRecipientSession globalCatalogSession, IEnumerable`1 baseAddresses, IEnumerable`1 oldProxies, RecipientInfo recipientInfo, ADRecipient recipient, LogMessageDelegate logger)

   at Microsoft.Exchange.DefaultProvisioningAgent.Rus.ProxySession.CreateProxies(IConfigurationSession configSession, IRecipientSession recipientSession, IRecipientSession globalCatalogSession, IEnumerable`1 baseAddresses, ADRecipient recipient, LogMessageDelegate logger)

   at Microsoft.Exchange.DefaultProvisioningAgent.Rus.EmailAddressPolicyHandler.UpdateEmailAddresses(List`1 allPolicies, ADRecipient recipient, LdapFilterProvider filterProvider)

   at Microsoft.Exchange.DefaultProvisioningAgent.Rus.EmailAddressPolicyHandler.UpdateRecipient(ADRecipient recipient)

   at Microsoft.Exchange.ProvisioningAgent.DefaultRUSProvisioningHandler.UpdateRecipient(ADRecipient recipient)

   at Microsoft.Exchange.ProvisioningAgent.RUSProvisioningHandler.UpdateAffectedIConfigurable(IConfigurable writeableIConfigurable)

   at Microsoft.Exchange.Provisioning.ProvisioningLayer.UpdateAffectedIConfigurable(Task task, IConfigurable writeableIConfigurable, Boolean checkProvisioningLayerAvailability)

   at Microsoft.Exchange.Configuration.Tasks.SetTaskBase`1.InternalValidate()

   at Microsoft.Exchange.Configuration.Tasks.SetRecipientObjectTask`3.InternalValidate()

   at Microsoft.Exchange.Management.Common.SetMailEnabledRecipientObjectTask`3.InternalValidate()

   at Microsoft.Exchange.Management.RecipientTasks.SetUserBase`2.InternalValidate()

   at Microsoft.Exchange.Management.RecipientTasks.SetMailboxBase`2.InternalValidate()

   at Microsoft.Exchange.Management.RecipientTasks.SetMailbox.InternalValidate()

   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()

   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

After this error message, the exchange installation is incomplete, there is no repair possible. Also remove the installation is not possible because there is an incomplete update installed.

Any ideas how to solve this?

Exchange 2013 Post CU6 Update and issue

Dear All,

I have below Environment:

2 Exchange server 2013 Mailbox Server with D.A.G

2 Exchange server 2013 CAS Server.

i planned to update above server from cu5 To Cu6.

I have succesfully updated mailbox servers to cu6 without any issues.

But i am facing one issue with CAS-Server update to cu6 .I have updated one CAS Server to cu6.But as soon as i shutdown the non-updated CAS server my outlook client is not connecting to updated client access server.

Before Update when i use to shutdown one cas server my outlook client use to connect to second cas server vice-versa.

please help me......

Exhcange 2013 installation error "The local domain needs to be updated", but domainprep has been run

Hello,

A few weeks ago, we ran the necessary /prepareschema /preparead /preparealldomains commands to get our Exhange 2010 Org ready to install Exchange 2013 SP1.  When we tried installing the first server today, we get an error:

[11/14/2014 23:42:02.0466] [1] [REQUIRED] The local domain needs to be updated. You must be a member of the 'Domain Admins' group and 'Organization Management' role group, or 'Enterprise Admins' group to continue.

We verified the ObjectVersion of both the Forest (15844) and Domain (13236), and it appears to be consistent with what you would expect for 2013 SP1.

Anybody have any ideas what could be wrong?

Thanks.

Exchange 2013 cu6 upgrade with Exchange 2007 client(NOT server) environment

From the articles in Google I know there is a risk if you upgrade your exchange server 2013 to CU6, in a environment coexistence with Exchange server 2007.

However we are in a Exchange server 2007 client environment, not server, all the office outlook clients in SCCM are still using Outlook 2007 client, expert please confirm if it is safe to install CU6 in such a environment like this, or what should I pay extra attention?

The upgrade is in a government environment so quite important to make sure everything goes right, basically we are in a DAG environment have Melbourne mailbox server, CAS server and Sydney mailbox server and CAS server as another pool.

The general steps I think is

1. prepare the AD schema update 3 days before doing the actual upgrade,

2. Put all 4 servers into maintenance mode one by one, MEL mailbox server --> MEL CAS server --> SYD mailbox server --> SYD CAS server.

3. Upgrade SYD mailbox server and CAS server first, reboot, take them out of maintenance mode, see if client can receive and send mail, all services is up.

4.  If SYD pool works well, perform the upgrade in MEL mailbox and CAS as well.

5. Reboot and check if send receive mails are OK, all services are up and running, replication is fine, etc.

Anyone has experience please comment and please let me know if I miss any or should pay extra attention to which part?

New-MigrationBatch -excludefolders fails claiming 'excludefolders' is not a parameter

Hi. I have been migrating users with no issue for awhile now. I finally ran into my first issue where an account will not migrate. When I look at the report for this user, I see this:

Regular Items: 921, 331.2 MB (347,243,378 bytes)
Regular Deleted Items: 155, 6.936 MB (7,273,005 bytes)
FAI Items: 76, 0 B (0 bytes)
FAI Deleted Items: 0, 0 B (0 bytes)
12/2/2014 3:00:40 PM [server01] Stage: FinalIncrementalSync. Percent complete: 95.
12/2/2014 3:00:40 PM [server01] Mailbox store finalization is complete.
12/2/2014 3:00:40 PM [server01] SessionStatistics updated.
12/2/2014 3:00:40 PM [server01] Verifying mailbox contents...
12/2/2014 3:00:45 PM [server01] A missing item was encountered: Missing Item (IPM.Note) Subject:"Fake Subject for sake of posting", Folder:"Deleted Items"

There were a lot of these entries and then this is the last part of the report:

12/2/2014 3:00:46 PM [server01] Mailbox contents verification complete: 64 folders, 978 items, 331.2 MB (347,240,561 bytes).
12/2/2014 3:00:46 PM [server01] Stage: FinalIncrementalSync. Percent complete: 95.
12/2/2014 3:00:46 PM [server01] Fatal error TooManyMissingItemsPermanentException has occurred.

I deleted the migration batch and recreated it. The same errors were seen. I don't know if there is a time frame where these messages will be fully deleted and no longer be attempted to be moved by future migration attempts. If so, how long do I wait until trying to migrate this user again?

Specifically to the title of this post, I attempted to create a migration request that would exclude the "Deleted Items" folder since all the failures were in that folder. I tried to create the migration batch using this command:

new-migrationbatch -name move1 -csvdata ([System.IO.File]::ReadAllBytes("C:\move1.csv")) -baditemlimit 100 -targetdatabases "db 1" -ExcludeFolders "Deleted Items"

I get this error when I try to create that migration batch:

[PS] C:\Windows\system32>new-migrationbatch -local -name move1 -csvdata ([System.IO.File]::ReadAllBytes("C:\move1.csv")) -baditemlimit 100 -targetdatabases "db 1" -excludefolders "Deleted Items"
A parameter cannot be found that matches parameter name 'excludefolders'.
    + CategoryInfo          : InvalidArgument: (:) [New-MigrationBatch], ParameterBindingException
    + FullyQualifiedErrorId : NamedParameterNotFound,New-MigrationBatch
    + PSComputerName        : server01.domain.com

I looked at the documentation for New-MigrationBatch (http://technet.microsoft.com/en-us/library/jj219166%28v=exchg.150%29.aspx) and it says that -excludefolders is a parameter. Why cannot I not get a batch to create using this parameter?


Viewing all 7008 articles
Browse latest View live


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