We've migrated users mailboxes from Exchange 2010 to Exchange 2013, and trying to resolve resting nuisances. One of them: now users can't change its membership in distribution groups (universal distribution groups) with Open MemberJoinRestriction / MemberDepartRestriction using Outlook.

Exploring RBAC role entries I discover that they keep reference to Exchange 2010, like this:

(Microsoft.Exchange.Management.PowerShell.E2010) Get-CalendarNotification -Credential -Debug -DomainController -ErrorAction -ErrorV
ariable -Identity -OutBuffer -OutVariable -ReadFromDomainController -ResultSize -Verbose -WarningAction -WarningVariable

Is it Ok Or I have to upgrade RBAC entries?

Dmitry

I am trying to use this utility to move the emails/contacts/etc. in some of my local PST files into an email account on Exchange Online (the cloud) through Office 365.

I have set up the "Online Connection Settings" and have connected successfully using the "check" button to my Office 365 global administrative account.

Next I added my PST file using the  "Add from Folder..." button.

The problem is that when I click on "Set mailbox..."( to direct the emails/contacts/etc. to be added to the correct email address in my company) the list never loads, it simply says "The Central Service is retrieving the mailbox data, try again in a moment".

It has been like this for several hours and shows no signs of change.

I need to be able to load .pst files from my old domain into the exchange cloud and NEVER USE THEM AGAIN. This means actually importing the emails, not just adding the .pst file to Outlook.

Please advise why the tool cannot find my company's email addresses and how to fix.

-Joe

P.S: I have already posted this in the Office 365 forums, they gave me the "not officially supported" nonsense and sent me here.

I just installed CU6 over SP1 at 8PM uk time 12/09/2014 and for the first time with no errors.

However all databases are mounted byt content index status is unknown.

Get-MailboxDatabaseCopyStatus | Ft Name,contentindexstate, Contentindexerrormessage -Autosize

shows the following error message: Could not find registry value of Index Status for database

And yes checking the key nothing is their (Sophos AV is off)

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v15\Search\IndexStatus

I tried restarting services and recreating the index server to no avail. How on earth do I get contentindex back?

I also have server 2 on a different lan subnet same domain 10mb fibre link, upgrading from sp1 to cu6 but it takes hours to perform the mailbox role transport service, about 3 hours before I finally get an error.

On that server I need to check if the error match's this article [cant link too tired to try and make it! - DiscoverySearchMailbox issue maybe]

On that server the keys exist.

If I stick with server 1 for now does anyone know how to kick the index service back into touch or restore working keys for the registry.

I am unable to create a new migration endpoint, receiving the following message:

***BEGINQUOTE***

***END QUOTE***

When I visit the test connectivity site and perform the Outlook Anywhere (RPC over HTTP) test, I don't get any errors.

 Where do I go from here? 

Hello everyone,

I'd like to know if it is ok/safe to install Exchange Server 2013 on Windows Server 2012 Standard?

As I started doing some research and noticed a page where Microsoft states they don't recommend running Exchange on Server 2012 Standard, and recommend making 2 different servers one for Active Directory and another for Exchange.
On that page they also listed some features that wouldn't work in case of Exchange is running on Server 2012. And that it may put a larger data load if setup this way.
I am hoping someone knowledgeable can explain and tell me if it is safe to use such setup or if it is better to use something like SBS 2011 Standard instead, which has Exchange included?

Has anyone installed Exchange 2013 on Server 2012 Standard successfully and used it for more then several months without problems?

Also just to give an idea on my background, I've been in IT field fairly long but haven't really updated to newer versions much and mainly used SBS 2003 and 2008 only with a few clients so haven't used 2008 too much.

Thanks in advance.

Hi,

I'm installing Exchange 2013 on a new server (Windows 2012) with AD on it (transferred from an old server). The remnants of AD from the old server have been removed, and the server completely removed from the network. However, when I try to install Exchange 2013 on the new box (not transferring mailboxes etc...fresh install), I get the following error during Readiness Checks:

There doesn't seem to be any further connection to the old box (Win 2008 R2 with Exchange 2010). All references were deleted in AD, and the box is switched off. 

Any ideas how I can check if a piece of the old server exists or how to get around this?  I've looked through all the folders in the AD Sites & Services, ADSI Edit, and AD Users & Computers.

Thanks,

Rob

When trying to install Exchange 2013 with SP1 on a Windows 2012 R2 Standard server (member server) in an existing organization containing one Exchange 2010 server with SP3 and RU7 installed I get the following message during the Readiness Check:

Error:

All Exchange 2010 servers in the organization must have Exchange 2013 Service Pack 3 or later installed. The following servers don't meet this requirement: .......

I have confirmed that the versions and build numbers of the exchange 2010 install are correct.  I have confirmed that AD schema is at the correct version.  Thank you

We have a single 2013 multi-role Exchange server in our environment.  I have noticed that whenever a single DC goes offline I lose connectivity to Exchange. When I look at the services on the Exchange server i see that  EXCHANGE 2013 AD Topology Service has crashed. The specific server that causes this is a DC / GC in a different site. It holds the domain naming master role.  There is a DC/GC in the same site as the Exchange server. The domain is at 2008r2 functional level. Please let me know if there is anything else I have omitted  about my environment that is pertinent to answering this question.

Thank you

Jim

Hi There

I want to migrate from my on-premise Exchange 2013 server to Exchange Online.

I have setup my Office 365 account and sync'd my users using DirSync.

After the migration I want to decommission my Exchange 2013 server thus I do not want aHybrid Migration.

I can't do a cutover migration because I have completed the DirSync. 

"If you’ve activated and installed the Windows Azure Active Directory Sync tool, you can’t run a cutover migration." - http://technet.microsoft.com/en-us/library/jj874016(v=exchg.150).aspx

So I believe that leaves me with a Stage Migration. http://technet.microsoft.com/en-us/library/jj874018(v=exchg.150).aspx

But... I can't says technet

"You can’t use a staged migration to migrate Exchange 2010 or Exchange 2013 mailboxes to Exchange Online" - http://technet.microsoft.com/en-us/library/jj874018(v=exchg.150).aspx

Q1: What model should I choose for this migration?

Q2: Should I stop the directory sync and delete all the users and perform a cutover migration and then start up the directory sync again?

Q3: How would I remove Exchange 2013 from a Hybrid Environment? If I choose the Hybrid path I'm finding it difficult to find documentation on decommissioning Exchange 2013 from that setup.

Jason

Hi Exchange experts,

we are currently have just added a new subnet in our LAN environment. previously we are using VLAN 10 (192.168.10.x/24) for both our servers and clients. Now, we have added one VLAN call VLAN 15 (192.168.15.x/24). the routing has been done between these two VLANs. VLAN 15 is able to ping VLAN 10 servers without any problem. However, VLAN 15 is only not able to ping CAS ARRAY for exchange transport. because of this, the connection from outlook to exchange server is not able to go thru the TCP, only RPC over HTTPS, which is outlook anywhere.

May I know what could be the issue? since VLAN 10 and VLAN 15 routing has been done and both are able to ping to each other, except CAS Array, I don't think there is problem with network routing.

What could be the cause of the issue. I need your kind advise.

Thanks.

Regards,

Henry

I'm fairly sure the issue is related to the fact that I had installed Exchange server 2013 CU1 on a Windows server 2012 box, and then uninstalled it. I then installed Exchange Server 2013 SP1 after rebuilding the servers to 2012 R2.

When I try to install a Mail App I get the error "Exchange Server doesn't support the requested version.".  I don't see any correlated errors in the event logs to figure out what exactly is going on.  If I use the powershell commandlet get-app to see what apps are available for a user I get the same thing.

I do have Exchange Server 2010 SP3 servers in my domain that I will eventually be migrating off of.  If anyone can give me some pointers of where to look for what might be broken I'd really appreciate it.

Hi all,

doing migration of mailboxes from 2010-2013 servers.So far migrated over 1k mailboxes and everything been working fine.Now i get problem with last mailbox.This is a shared mailbox and around 12gb in size.Have moved it to another 2010 database and was fine,but to different 2013 database it is stuck at 10% with error Transientfailure.

I have tried with the switch -whatif and it didnt show any error.

Any tips on what i can do to fix this?

thanks!

Please 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. Thank you! Off2work

Greetings all,

I found this blog entry from the Exchange team about publishing Exchange 2013 through TMG.

http://blogs.technet.com/b/exchange/archive/2012/11/21/publishing-exchange-server-2013-using-tmg.aspx

One thing I'd like to do now is change the TMG FBA screen to showthe same form as Exchange 2013 shows. Does anyone know whats involved in doing this? can I just "copy" a directory from the Exchange server to TMG with the required forms?

Hi,

I have a problem with my Exchange 2010 SP1 deploy in Windows server 2008 R2,

I try upgrade to Exchange 2010 SP3, an error happened when step progress CAS role

I already try delete owaVirtualDirectory from adsiedit, Exchange management console, and from IIS manager but still it say virtual directory 'owa' already exists in my server.

Can anyone help me how resolve this problem?

Thanks.

Best Regards,

Henry Stefanus

Hello all,

     This is my first post here. I fear our organization may have made a grave error. Here is our basic setup:

1. Location 1 - 3 2008 R2 standard servers in a domain. 1 Exchange 2010 sp3 server.
2. Location 2 - 3 2008 R2 standard servers in the same domain connected over CISCO VPN. 1 Exchange 2010 sp3 server

Our objective was to replicate the first site at the second site. We have setup DFS and made a BDC at the second site, no issues. However, I have been doing some reading on Exchange replication, and it looks like we are in trouble. I had read that Exchange 2010 could be fully replicated over two servers (unlike 2007). However, I now have read that this requires the Enterprise edition of Windows server 2008 R2. So, I guess I have three questions to start:

1. Is there ANY way we can replicate site 1 to site 2 with the current setup? Even if it means site 2 is "inactive" unless we need it for a failure at site 1?
2. If not, can we upgrade to the enterprise edition for the servers? Any idea on cost?
3. If we upgrade to Enterprise, is there a decent place to go to read on how to setup the second site?

Thanks very much.

Hi all,

we traid to install Exchange CU6 as a upgrade from Exchange 2013 SP1. The Setup Fails like this:

E:\Sources\Ex2013CU6>setup /m:upgrade /IAcceptExchangeServerLicenseTerms

Welcome to Microsoft Exchange Server 2013 Cumulative Update 6 Unattended Setup
Copying Files...
File copy complete. Setup will now collect additional information needed for
installation.
Languages
Mailbox role: Transport service
Client Access role: Front End Transport service
Mailbox role: Client Access service
Mailbox role: Unified Messaging service
Mailbox role: Mailbox service
Management tools
Client Access role: Client Access Front End service

Performing Microsoft Exchange Server Prerequisite Check

                                                              FAILED
 An unexpected error has occurred and a Watson dump is being generated: Object r
eference not set to an instance of an object.

     Object reference not set to an instance of an object.

The Exchange Server setup operation didn't complete. More details can be found
in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.

[09/15/2014 13:53:00.0941] [0] **********************************************
[09/15/2014 13:53:00.0956] [0] Starting Microsoft Exchange Server 2013 Cumulative Update 6 Setup
[09/15/2014 13:53:00.0956] [0] **********************************************
[09/15/2014 13:53:00.0956] [0] Local time zone: (UTC+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna.
[09/15/2014 13:53:00.0956] [0] Operating system version: Microsoft Windows NT 6.2.9200.0.
[09/15/2014 13:53:00.0956] [0] Setup version: 15.0.995.29.
[09/15/2014 13:53:00.0972] [0] Logged on user: LOC\administrator.
[09/15/2014 13:53:01.0019] [0] Command Line Parameter Name='mode', Value='Upgrade'.
[09/15/2014 13:53:01.0019] [0] Command Line Parameter Name='iacceptexchangeserverlicenseterms', Value=''.
[09/15/2014 13:53:01.0019] [0] Command Line Parameter Name='sourcedir', Value='E:\Sources\Ex2013CU6'.
[09/15/2014 13:53:01.0285] [0] RuntimeAssembly was started with the following command: '/m:upgrade /IAcceptExchangeServerLicenseTerms /sourcedir:E:\Sources\Ex2013CU6'.
[09/15/2014 13:53:01.0300] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\v8.0, wasn't found.
[09/15/2014 13:53:01.0300] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v14, wasn't found.
[09/15/2014 13:53:01.0300] [0] Copying Files...
[09/15/2014 13:53:01.0316] [0] Starting copy from E:\Sources\Ex2013CU6\Setup\ServerRoles\Common to C:\Windows\Temp\ExchangeSetup.
[09/15/2014 13:53:02.0816] [0] Finished copy from E:\Sources\Ex2013CU6\Setup\ServerRoles\Common to C:\Windows\Temp\ExchangeSetup.
[09/15/2014 13:53:02.0816] [0] File copy complete. Setup will now collect additional information needed for installation.
[09/15/2014 13:53:02.0831] [0] Assembly dll file location is C:\Windows\Temp\ExchangeSetup\Microsoft.Exchange.Setup.Console.dll
[09/15/2014 13:53:06.0613] [0] Setup is choosing the domain controller to use
[09/15/2014 13:53:07.0003] [0] The MSExchangeADTopology has a persisted domain controller: LOC-srv1201.LOC.local
[09/15/2014 13:53:11.0253] [0] PrepareAD has been run, and has replicated to this domain controller; so setup will use LOC-srv1201.LOC.local
[09/15/2014 13:53:11.0253] [0] Setup is choosing a global catalog...
[09/15/2014 13:53:11.0331] [0] Setup has chosen the global catalog server LOC-srv1201.LOC.local.
[09/15/2014 13:53:11.0347] [0] Setup will use the domain controller 'LOC-srv1201.LOC.local'.
[09/15/2014 13:53:11.0347] [0] Setup will use the global catalog 'LOC-srv1201.LOC.local'.
[09/15/2014 13:53:11.0347] [0] Exchange configuration container for the organization is 'CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=LOC,DC=local'.
[09/15/2014 13:53:11.0347] [0] Exchange organization container for the organization is 'CN=LOC,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=LOC,DC=local'.
[09/15/2014 13:53:11.0394] [0] Setup will search for an Exchange Server object for the local machine with name 'LOC-SRV7210'.
[09/15/2014 13:53:11.0738] [0] Exchange Server object found : 'CN=LOC-SRV7210,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=LOC,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=LOC,DC=local'.
[09/15/2014 13:53:12.0128] [0] The following roles have been unpacked: BridgeheadRole ClientAccessRole MailboxRole UnifiedMessagingRole FrontendTransportRole AdminToolsRole CafeRole
[09/15/2014 13:53:12.0128] [0] The following datacenter roles are unpacked:
[09/15/2014 13:53:12.0128] [0] The following roles are installed: BridgeheadRole ClientAccessRole MailboxRole UnifiedMessagingRole FrontendTransportRole AdminToolsRole CafeRole
[09/15/2014 13:53:12.0144] [0] The local server has some Exchange files installed.
[09/15/2014 13:53:12.0175] [0] Server Name=LOC-SRV7210
[09/15/2014 13:53:12.0238] [0] Setup will use the path 'E:\Sources\Ex2013CU6' for installing Exchange.
[09/15/2014 13:53:12.0238] [0] Setup will discover the installed roles from server object 'CN=LOC-SRV7210,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=LOC,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=LOC,DC=local'.
[09/15/2014 13:53:12.0238] [0] 'BridgeheadRole' is installed on the server object.
[09/15/2014 13:53:12.0238] [0] 'ClientAccessRole' is installed on the server object.
[09/15/2014 13:53:12.0253] [0] 'MailboxRole' is installed on the server object.
[09/15/2014 13:53:12.0253] [0] 'UnifiedMessagingRole' is installed on the server object.
[09/15/2014 13:53:12.0253] [0] 'CafeRole' is installed on the server object.
[09/15/2014 13:53:12.0253] [0] 'FrontendTransportRole' is installed on the server object.
[09/15/2014 13:53:12.0253] [0] The installation mode is set to: 'BuildToBuildUpgrade'.
[09/15/2014 13:53:13.0425] [0] An Exchange organization with name 'LOC' was found in this forest.
[09/15/2014 13:53:13.0425] [0] Active Directory Initialization status : 'True'.
[09/15/2014 13:53:13.0425] [0] Schema Update Required Status : 'False'.
[09/15/2014 13:53:13.0425] [0] Organization Configuration Update Required Status : 'False'.
[09/15/2014 13:53:13.0425] [0] Domain Configuration Update Required Status : 'False'.
[09/15/2014 13:53:13.0441] [0] The locally installed version is 15.0.847.32.
[09/15/2014 13:53:13.0441] [0] Exchange Installation Directory : 'C:\Program Files\Microsoft\Exchange Server\V15'.
[09/15/2014 13:53:13.0535] [0] Setup is determining what organization-level operations to perform.
[09/15/2014 13:53:13.0535] [0] Because the value was specified, setup is setting the argument OrganizationName to the value LOC.
[09/15/2014 13:53:13.0581] [0] RootDataHandler has 1 DataHandlers
[09/15/2014 13:53:13.0581] [0]      Languages
[09/15/2014 13:53:13.0581] [0]      Mailbox role: Transport service
[09/15/2014 13:53:13.0581] [0]      Client Access role: Front End Transport service
[09/15/2014 13:53:13.0581] [0]      Mailbox role: Client Access service
[09/15/2014 13:53:13.0581] [0]      Mailbox role: Unified Messaging service
[09/15/2014 13:53:13.0581] [0]      Mailbox role: Mailbox service
[09/15/2014 13:53:13.0581] [0]      Management tools
[09/15/2014 13:53:13.0581] [0]      Client Access role: Client Access Front End service
[09/15/2014 13:53:13.0613] [0] Validating options for the 7 requested roles
[09/15/2014 13:53:13.0613] [0] UpgradeModeDataHandler has 17 handlers and 17 work units
[09/15/2014 13:53:13.0675] [0] Performing Microsoft Exchange Server Prerequisite Check
[09/15/2014 13:53:13.0925] [0] **************
[09/15/2014 13:53:13.0925] [0] Setup will run the task 'Start-PreConfiguration'
[09/15/2014 13:53:13.0941] [1] Setup launched task 'Start-PreConfiguration -Mode 'BuildToBuildUpgrade' -Roles 'LanguagePacks','BridgeheadRole','FrontendTransportRole','ClientAccessRole','UnifiedMessagingRole','MailboxRole','AdminToolsRole','CafeRole'' 
[09/15/2014 13:53:15.0472] [1] [ERROR] Object reference not set to an instance of an object.
[09/15/2014 13:53:15.0472] [1] [WARNING] An unexpected error has occurred and a Watson dump is being generated: Object reference not set to an instance of an object.
[09/15/2014 13:53:16.0144] [1] [ERROR] Object reference not set to an instance of an object.
[09/15/2014 13:53:16.0144] [1] [ERROR] Object reference not set to an instance of an object.
[09/15/2014 13:53:16.0175] [0] [ERROR] Exception has been thrown by the target of an invocation.
[09/15/2014 13:53:16.0175] [0] [ERROR] Object reference not set to an instance of an object.
[09/15/2014 13:53:16.0175] [0] [ERROR] Object reference not set to an instance of an object.
[09/15/2014 13:53:16.0175] [0] CurrentResult SetupLauncherHelper.loadassembly:444: 1
[09/15/2014 13:53:16.0175] [0] The Exchange Server setup operation didn't complete.  More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
[09/15/2014 13:53:16.0175] [0] CurrentResult main.run:235: 1
[09/15/2014 13:53:16.0175] [0] CurrentResult setupbase.maincore:396: 1
[09/15/2014 13:53:16.0175] [0] End of Setup
[09/15/2014 13:53:16.0175] [0] **********************************************

hi 

I have another fresh exchange 2013

i cant login to owa with error :    :) something went wrong

It seems authentication issue 

Ecp is working with no issues .

Identity                      : EXCHCASSRV1\owa (Default Web Site)
Name                          : owa (Default Web Site)
InternalUrl                   : https://exchcassrv1.corp.net/owa
ExternalUrl                   : 
ClientAuthCleanupLevel        : High
InternalAuthenticationMethods : {Basic, Fba}
BasicAuthentication           : True
WindowsAuthentication         : False
DigestAuthentication          : False
FormsAuthentication           : True
LiveIdAuthentication          : False
AdfsAuthentication            : False
OAuthAuthentication           : False
ExternalAuthenticationMethods : {Fba}

Identity                      : EXCHCASSRV2\owa (Default Web Site)
Name                          : owa (Default Web Site)
InternalUrl                   : https://exchcassrv2.corp.net/owa
ExternalUrl                   :
ClientAuthCleanupLevel        : High
InternalAuthenticationMethods : {Basic, Fba}
BasicAuthentication           : True
WindowsAuthentication         : False
DigestAuthentication          : False
FormsAuthentication           : True
LiveIdAuthentication          : False
AdfsAuthentication            : False
OAuthAuthentication           : False
ExternalAuthenticationMethods : {Fba}

Identity                      : EXCHMBXSRV1\owa (Exchange Back End)
Name                          : owa (Exchange Back End)
InternalUrl                   :
ExternalUrl                   :
ClientAuthCleanupLevel        : High
InternalAuthenticationMethods : {Ntlm, WindowsIntegrated}
BasicAuthentication           : False
WindowsAuthentication         : True
DigestAuthentication          : False
FormsAuthentication           : False
LiveIdAuthentication          : False
AdfsAuthentication            : False
OAuthAuthentication           : False
ExternalAuthenticationMethods : {Fba}

Identity                      : EXCHMBXSRV2\owa (Exchange Back End)
Name                          : owa (Exchange Back End)
InternalUrl                   :
ExternalUrl                   :
ClientAuthCleanupLevel        : High
InternalAuthenticationMethods : {Ntlm, WindowsIntegrated}
BasicAuthentication           : False
WindowsAuthentication         : True
DigestAuthentication          : False
FormsAuthentication           : False
LiveIdAuthentication          : False
AdfsAuthentication            : False
OAuthAuthentication           : False
ExternalAuthenticationMethods : {Fba}



[PS] C:\Windows\system32>^A

need help

MCP MCSA MCSE MCT MCTS CCNA

Hello, I have researched and talked with a couple of people both at Microsoft and Dell to no avail as to the situation I am in. I am currently trying to help a small company get their email moved from Office 365 back on an on premise exchange 2013 server. The biggest issue is the MX Record, how to get it to point to the on premise exchange server. I have found nothing on the internet as to how to do this procedure and was told by Dell that they have no documentation on it. I am now curious as to if such a procedure actually does exist and if one decides to move to Office 365 are they forced to stay there. I would greatly appreciate any insight if anyone is aware of such a procedure. Thanks.

Ruben