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

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] **********************************************


Moving MailboxDatabase failed

$
0
0

Server: MS Server 2012

Exchange: Exchange 2013, Version 15.0 (Build 1104.5)

I have been trying to move a mailbox database and its log folderpath for several days. Every time it terminates with an error and the move fails. So i tried to move the logfolderpath and it worked perfectly. Log files have been moved. Again I tried to move the DB it failed again. please find below the error message. The size of the DB is close to 1TB. After the failing the DB is unmounted. There is an Edb file in the current location of the mailboxdatabase. also an Edb file in the new destination location. Size of both Edbs are the same. The error occured after about 10 hours of copying database file. I restarted the server and the mailboxdatabase mounts and i can send & receive mails fine. The file path to DB is same as before.


Processing data for a remote command failed with the following error message: <s:Envelope xml:lang="en-US"xmlns:s="http://www.w3.org/2003/05/soap-envelope"xmlns:a="http://schemas.xmlsoap.org/ws/2004/08/addressing"xmlns:x="http://schemas.xmlsoap.org/ws/2004/09/transfer" xmlns:e="http://schemas.xmlsoap.org/ws/2004/08/eventing"xmlns:n="http://schemas.xmlsoap.org/ws/2004/09/enumeration" xmlns:w="http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd" xmlns:p="http://schemas.microsoft.com/wbem/wsman/1/wsman.xsd"><s:Header><a:Action>http://schemas.dmtf.org/wbem/wsman/1/wsman/fault For more information, see the about_Remote_Troubleshooting Help topic.

   + CategoryInfo         : OperationStopped: (<Server_name>:String) [], PSRemotingTransportException

   + FullyQualifiedErrorId : JobFailure

   + PSComputerName        : <Server_name>


Any help is appreciated. Thank you


Can't remove the last Exchange 2010 Public Folder

$
0
0

I upgraded to Exchange 2013 and I don't need or want the Exchange 2010 public folders.  I need to remove the 2010 server, but if I shutdown the server, Outlook 2010 clients cannot load, they get stuck trying to connect to this last public folder...

I tried using the Public Folder Management Console in Exchange 2010 and I was able to delete all of the public folders except this last one, \Internet Newsgroups.  I get the error that I have the correct identity and that I have the correct permissions to delete it.

I followed the article,  https://technet.microsoft.com/en-us/library/dd876883(v=exchg.141).aspx and when I try and run the PS command:

Get-PublicFolder -Server server2010 "\" -Recurse -ResultSize:Unlimited | Remove-PublicFolder -Server server2010 -Recurse

I get an error,

Action 'Remove' could not be performed on object 'Internet Newsgroups'.

Internet Newsgroups
 Failed
 Error:
 Cannot delete the object '\Internet Newsgroups'. Please make sure that you specified the correct identity and that you have the correct permissions to delete it.

---

It looks like my Outlook 2010 client has this public folder cached and it is trying to connect to it and get hung and never connects.  Is there another way to delete this public folder? 

When I go into ADSI--> I do have under CN=Services, CN=Microsoft Exchange, CN=Domain, CN=Administrative Groups, CN=Exchange Administrative Group (FYDIBOHF23SPDLT), CN=Databases, CN=Public Folder Database

Should I delete this??? or is there a better way??

Cmdlet Extension Agent | New-MoveRequest

$
0
0

Hello together,

I have a question regarding the Cmdlet Extension Agent:

Can I "manipulate" the New-MoveRequest in the way, that I can grab the automatically selected target database, add a prefix to the database to generate the Archive-database Name and then take the new Name for "-ArchiveTargetDatabase" ?

The target is to move the Mailbox in a normal user mailbox database and the archive mailbox to an archive database.

Everytime I try a cmdlet, it says:

WARNING: The cmdlet extension agent with the index 0 has thrown an exception in OnComplete(). The exception is:
Microsoft.Exchange.Provisioning.ProvisioningException: ScriptingAgent: Exception thrown while invoking scriptlet for
OnComplete API: Specified method is not supported.. ---> System.NotSupportedException: Specified method is not
supported.

Thanks in advance!

Exchange in Inconsistent state after SP3

$
0
0

I installed SP3 on Exchange and none of the services started. Upon investigation there were a number of files missing from C:\Program Files\Microsoft\Exchange Server\Bin. notably MSExchangeADTopologyService.exe store.exe mad.exe

In ADSIEdit the serial number of Exchange is v8.1 (Build 30240.6) SP1, in the registry the build on Admin Tools 

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\v8.0\AdminTools ConfiguredVersion and UnpackedVersion are both 8.3.83.6 and 

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\v8.0\ClientAccessRole HubTransportRole and MailBoxRole are all ConfiguredVersion 8.1.240.6

Have read posts about editing serial numbers and registry to run setup /M:RecoverServer which currently fails because the current installed version is 8.3.83.6 and the last installed version is 8.1.240.6 so that registry entries and serial number in AD is the same.

Has anyone done this successfully? and what needs to be edited so I can recover/reapply SP3? There is no Watermark entry in the registry.

Thanks

Rachel

 

Exchange 2013 one AD Domain, different sites/subnets,multiple email domains ?

$
0
0

I'm the admin with basic knowledge of Exchange currently working at a branch office in an Organization with two main branches/sites in different cities, Site A(172.16.0.0/16) and Site B (172.18.0.0/16) both in an AD Domain "abc.com".  

I'am currently working at Site B which is part of an AD Domain "abc.com", whose Forest Root Domain is at Site A. Site A has an Exchange server handling emails only for users in Site A "alias@abc.com"......Due to the nature of business at Site B, we have 3 internet domains "efg.com, xyz.com and jkl.com" used for emails which are running on a Linux box.

My requirement is to move away from the Linux environment at Site B to and deploy and Exchange server (joined to the "abc.com" AD Domain) but handling emails for "efg.com, xyz.com and jkl.com" internet domains.

How can i achieve this. Thank you

RPC over HTTP trouble Exchange 2013/2007 coexistence, 2013 RPCProxy cannot ping GC.

$
0
0

I currently have an Exchange 2013/2007 coexistence scenario which gives me trouble with the RPC over HTTP part with users with a 2007 mailbox. the MS RCA website performs 2 tests with the MAPI address book endpoints, once against a 2007 mailbox server and once a against a GC/DC, the last one fails. The logs are from our test domain, but the exact same happens in the production domain. running CU8 (recently upgraded, but problem was exactly the same with CU7)

Testing the MAPI Address Book endpoint on the Exchange server.
 The address book endpoint was tested successfully.
 
Additional Details
 Elapsed Time: 7872 ms.
 
Test Steps
 
Attempting to ping the MAPI Address Book endpoint with identity: exmb11.domain.test:6004.
 The endpoint was pinged successfully.
 
Additional Details
 
The endpoint responded in 156 ms.
Elapsed Time: 4153 ms.


Testing the MAPI Address Book endpoint on the Exchange server.
 An error occurred while testing the address book endpoint.
 
Additional Details
 Elapsed Time: 3079 ms.
 
Test Steps
 
Attempting to ping the MAPI Address Book endpoint with identity: tdc01421.domain.test:6004.
 The attempt to ping the endpoint failed.
  <label for="testSelectWizard_ctl12_ctl06_ctl02_ctl09_ctl00_tmmArrow">Tell me more about this issue and how to resolve it</label>
 
Additional Details
 
The RPC_S_SERVER_UNAVAILABLE error (0x6ba) was thrown by the RPC Runtime process.
Elapsed Time: 3079 ms.



---
texmb11 = ex2007 mailbox
texfr11 = ex2007 CAS
tdc01421 = DC/GC
texch31 = 2013 multirole
---

other symptoms :

Browser test
https://texch31.domain.test/rpc/rpcproxy.dll?texmb11:6004 --> 503 (which is correct)
https://texch31.domain.test/rpc/rpcproxy.dll?tdc01421:6004 --> 404.0 Not Found

RPCPing
rpcping -t ncacn_http -s texmb11 -o RpcProxy=texch31.domain.test -P "user,dom,*" -I "user,dom,*" -H 2 -u 9 -a connect -F 3 -v 3 -e 6004
Success

rpcping -t ncacn_http -s tdc01421 -o RpcProxy=texch31.domain.test -P "user,dom,*" -I "user,dom,*" -H 2 -u 9 -a connect -F 3 -v 3 -e 6004
Fails!

so the Ex2013 RPCProxy doesn't proxy to the DC/GC, but the RPCProxy to an ex2007 mailbox server works fine, so the authentication methods configured are correct i'd say..

the same tests using the ex2007CAS server as RPC proxy all succeed!:

MS RCA is all green

https://texfr11.domain.test/rpc/rpcproxy.dll?texmb11:6004 --> 503
https://texfr11.domain.test/rpc/rpcproxy.dll?tdc01421:6004 --> 503 

rpcping -t ncacn_http -s texmb11 -o RpcProxy=texfr11.domain.test -P "user,dom,*" -I "user,dom,*" -H 2 -u 9 -a connect -F 3 -v 3 -e 6004
Success

rpcping -t ncacn_http -s tdc01421 -o RpcProxy=texfr11.domain.test -P "user,dom,*" -I "user,dom,*" -H 2 -u 9 -a connect -F 3 -v 3 -e 6004
Success!!

Logs

all tries against the 2013 CAS server generate '404' log entries in several logs int the Logging directory, the most explicit being the one in Program Files\Microsoft\Exchange Server\V15\Logging\HttpProxy\RpcHttp : HttpProxy_xxxxxx.LOG

2015-04-30T19:58:00.153Z,895cdf07-f2eb-4beb-b787-da02ba11b0c2,15,0,1076,0,,RpcHttp,webmail.domain.test,/rpc/rpcproxy.dll,,Basic,true,DOM\user,,,MSRPC,10.10.142.132,TEXCH31,404,,MailboxGuidWithDomainNotFound,RPC_IN_DATA,,,,,,,,,4,,,,1,,,0,,0,,0,0,,0,2,0,,,,,,,,,1,1,0,,1,,2,2,,?TDC01422.domain.test:6004,,BeginRequest=2015-04-30T19:58:00.153Z;CorrelationID=<empty>;ProxyState-Run=None;ProxyState-Complete=CalculateBackEnd;EndRequest=2015-04-30T19:58:00.153Z;,HttpProxyException=Microsoft.Exchange.HttpProxy.HttpProxyException:RPC server name passed in by client could not be resolved: TDC01422.domain.test   at Microsoft.Exchange.HttpProxy.RpcHttpProxyRequestHandler.ResolveToDefaultAnchorMailbox(String originalRpcServerName  String reason)    at Microsoft.Exchange.HttpProxy.RpcHttpProxyRequestHandler.ResolveAnchorMailbox()    at Microsoft.Exchange.HttpProxy.ProxyRequestHandler.InternalBeginCalculateTargetBackEnd(AnchorMailbox& anchorMailbox)    at Microsoft.Exchange.HttpProxy.ProxyRequestHandler.<BeginCalculateTargetBackEnd>b__3b();

the error suggests the name could not be resolved. but nslookup works fine. i can ping the tdc01421 correctly form texch31, it returns me the ipv4 address. i can telnet to port 6004 from texch31 server to tdc01421 giving me the correct 'ncacn_http' answer..

i look at the 'ValidPorts' and ValidPorts_Autoconfig_Exchange reg keys and filled them with the same i have on the 2007cas servers (all ex servers, all dc/gc's, all of them with netbios & fqdn ports 6001,6002 & 6004..) but also no success.

im out of ideas by now..

EXCHANGE SERVER 2013:INSTALLATION AND CONFIGURATION STEPS

$
0
0

 Greetings,

I am IT person recently asssigned to work as ana exchange administrator in my organization.The organization is also getting support and licence from microsoft.

Our current exchange servers is 2010 without service park.I have been assigned to do the following tasks;

- UPgraded the existing exchange 2010 with service park

-Backup all the whole exchange 2010 after installing service park

-Install and Configure new servcers for exchange 2013 running under win 2012.

-Restoring the back up from exch 2010 to new servers 2013.

Number of users 2600, mailboxes 8

The paln is two deploy new exchange servers 2013 of which the two will communicated to each other (load balance/redundancy).Also DAG Configuration.

PLEASE: Help me with step by step procedure ,guide,tools and required resources from exch 2010, sp to 2013.

My contacts: lelojohnmmasi@gmail.com , lelojohnmmasi@outlook.com, phone:+255752458912


CU 10 Install Error

$
0
0


I had an error updating my Exchange 2013 CU 8 to CU 10 last week - set up failed at step 14 of 18 Mailbox Role: Mailbox Service - the error was " Couldn't resolve the user or group "ourdomain/Microsoft Exchange Security Groups/Discovery Management." I have the full error below. I found two possible solutions to the error by googling and resolved and completed the install issue by deleting the DiscoverySearchMailbox {D919BA05-46A6-415f-80AD-7E09334BB852} user account from AD (the other possible solution was to disable the discovery search mailbox, but I could not do this because the install was already half way through. After setup completed, I ran Setup /PrepareAD /IAcceptblablabla... and the DiscoverySearchMailbox was recreated, but the mailbox was not.  I found the commands to recreate the mailbox and user and the discovery search is now working, but I would like to find out why did this setup error occurred. I didn't run PrepareAD prior to install - read some info that this was not needed from CU 8, but other than that we have a very vanilla setup - single forest domain, 2 DCs, one Exchange Server, small org (30 MBs), no fancy addons, I had disabled the AV prior to install, so I am hoping someone might be able to shed some light on why this error occurred on an account that existed previously?

Thanks in advance for any help - here is the full error received:

Error: The following error was generated when "$error.Clear(); $name = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxUniqueName; $dispname = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxDisplayName; $dismbx = get-mailbox -Filter {name -eq $name} -IgnoreDefaultScope -resultSize 1; if( $dismbx -ne $null) { $srvname = $dismbx.ServerName; if( $dismbx.Database -ne $null -and $RoleFqdnOrName -like "$srvname.*" ) { Write-ExchangeSetupLog -info "Setup DiscoverySearchMailbox Permission."; $mountedMdb = get-mailboxdatabase $dismbx.Database -status | where { $_.Mounted -eq $true }; if( $mountedMdb -eq $null ) { Write-ExchangeSetupLog -info "Mounting database before stamp DiscoverySearchMailbox Permission..."; mount-database $dismbx.Database; }
      $mountedMdb = get-mailboxdatabase $dismbx.Database -status | where { $_.Mounted -eq $true };
      if( $mountedMdb -ne $null )
      {
      $dmRoleGroupGuid = [Microsoft.Exchange.Data.Directory.Management.RoleGroup]::DiscoveryManagement_InitInfo.WellKnownGuid;
      $dmRoleGroup = Get-RoleGroup -Identity $dmRoleGroupGuid -DomainController $RoleDomainController -ErrorAction:SilentlyContinue;
      if( $dmRoleGroup -ne $null )
      {
        trap [Exception]
        {
          Add-MailboxPermission $dismbx -User $dmRoleGroup.Name -AccessRights FullAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
          continue;
        }

        Add-MailboxPermission $dismbx -User $dmRoleGroup.Identity -AccessRights FullAccess -DomainController $RoleDomainController -WarningAction SilentlyContinue;
      }
      }
      }
      }
    " was run: "Microsoft.Exchange.Data.Common.LocalizedException: Couldn't resolve the user or group "ourdomain/Microsoft Exchange Security Groups/Discovery Management." If the user or group is a foreign forest principal, you must have either a two-way trust or an outgoing trust. ---> System.SystemException: The trust relationship between the primary domain and the trusted domain failed.


at System.Security.Principal.NTAccount.TranslateToSids(IdentityReferenceCollection sourceAccounts, Boolean& someFailed) at System.Security.Principal.NTAccount.Translate(IdentityReferenceCollection sourceAccounts, Type targetType, Boolean forceSuccess) at System.Security.Principal.NTAccount.Translate(Type targetType) at Microsoft.Exchange.Configuration.Tasks.SecurityPrincipalIdParameter.GetUserSidAsSAMAccount(SecurityPrincipalIdParameter user, TaskErrorLoggingDelegate logError, TaskVerboseLoggingDelegate logVerbose) --- End of inner exception stack trace --- at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl) at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target) at Microsoft.Exchange.Configuration.Tasks.SecurityPrincipalIdParameter.GetUserSidAsSAMAccount(SecurityPrincipalIdParameter user, TaskErrorLoggingDelegate logError, TaskVerboseLoggingDelegate logVerbose) at Microsoft.Exchange.Configuration.Tasks.SecurityPrincipalIdParameter.GetSecurityPrincipal(IRecipientSession session, SecurityPrincipalIdParameter user, TaskErrorLoggingDelegate logError, TaskVerboseLoggingDelegate logVerbose) at Microsoft.Exchange.Management.RecipientTasks.SetMailboxPermissionTaskBase.InternalValidate() at Microsoft.Exchange.Management.RecipientTasks.AddMailboxPermission.InternalValidate() at Microsoft.Exchange.Configuration.Tasks.Task.b__b() at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

Thanks,

George

Only Mailbox migration to private cloud

$
0
0

Hello Everyone

What are the mailbox migration paths available to the private cloud Exchange 2010 (hosted setup).

Let's take an example of customer having 2000 users in his on premise.

I want to migrate only the mailboxes from this customer and the User accounts should remain as such with them.

They have share point , Lync and other applications running on their on premise which are dependent on these AD accounts.

My plan is to migrate only the mailboxes , enable outlook anywhere, owa and active sync for all these users .

What is the best way to complete this migration.

Any advices, suggestions is much appreciated.





Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com Thanks Sathish (MVP)

Cross Forest Migration Exchange 2013 Error StalledDueToMailboxLocked

$
0
0

Hi Folks, 

we are working on a cross forest migration for AD and Exchange, where Source Exchange is 2010 SP3 and Target new Exchange is 2013 CU8. while migrating the mailboxes we are getting the below issues and it takes ages to complete. i have migrated one mailbox earlier with 4.7 GB size it after lots of retries it took 28 hours to complete. 

below is another mailbox which is quite smaller in size to check but i am still getting the same problem. what could be the cause for this. i have done all custom settings for MRS proxy and client binding at source Exchange server, but the results are still the same.

Informational: The request has been temporarily postponed because the mailbox is locked. The Microsoft Exchange Mailbox Replication service will attempt to continue processing the request after 6/19/2015 2:40:07 PM.

OverallDuration                        : 00:28:43.5949514
TotalQueuedDuration                  : 00:00:04.9658754
TotalInProgressDuration                : 00:28:38.6290760
TotalStalledDueToHADuration            : 00:04:02.7186976
TotalStalledDueToMailboxLockedDuration : 00:12:38.8746309
TotalTransientFailureDuration          : 00:00:35.2813100
TotalIdleDuration                      : 00:04:50.2813457
TotalMailboxSize                      : 1.172 GB (1,258,052,697 bytes)
TotalMailboxItemCount                  : 37935
BytesTransferred                      : 343.6 MB (360,322,748 bytes)
BytesTransferredPerMinute              : 0 B (0 bytes)
ItemsTransferred                      : 24016

i am in a challenging situation, need urgent support.


Regards, Owais

Exchange Server 2013- Database Issue

$
0
0

Hello,

Currently in our scenario we are using Exchange server 2013 in house with Five databases, everything was properly working but  some users call me and said they are not able to recived any mails from last 1 hr their mailbox was properly connected in outlook, remaining all users are able to send and recive mail which are on other four databases.

users are facing issue in single database only, what will be the problem ?

Thanks,

Prashant M

Exchange 2013 - powershell tips not working

$
0
0

When I run exchange 2013 shell I get this errors:

Exchange tips file C:\Program Files\Microsoft\Exchange Server\V15\bin\\en\extips.xml not found!

This computer was part of different domain. We have uninstalled exchange2013, restarted the server, put the server to different domain and install exchange2013 again, maybe thats the reason, and how can we repair it?

With best regards


bostjanc

Are Exchange 2010 rollups cumilative?

$
0
0
Exchange 2010 SP3 system without any rollups.  Does Exchange 2010 SP3 RU11 include past rollups or do I need to install RU 1 through 11?

Fail edge server installation

$
0
0

Hi,

My edge server installation failed with the following message:

Error:
The following error was generated when "$error.Clear();
          new-receiveconnector `
            -Name ("Default internal receive connector " + [String][System.Environment]::MachineName ) `
            -Bindings 0.0.0.0:25 `
            -RemoteIPRanges 0.0.0.0-255.255.255.255 `
            -DomainSecureEnabled $true
        " was run: "Microsoft.Exchange.Configuration.Tasks.TaskException: The parent object for Default internal receive connector OFFICE02 could not be found. Please check that SMTP Receive Connectors exists.
   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.Configuration.Tasks.NewADTaskBase`1.InternalProcessRecord()
   at Microsoft.Exchange.Management.SystemConfigurationTasks.NewReceiveConnector.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

I have manually created a "Default internal receive connector OFFICE02" internet connector, but still the setup fails and notifies me that an incomplete installation is detected.

What I think that happened is that both the edge and hub transport role are installed on the same server due to an interface bug in the setup. I want to be able to uninstall this Exchange server to start over again. I rather avoid to remove the Exchange server with ADSIEdit.

The error seems to require another default connector apart from "Default internal receive connector OFFICE02". Could someone maybe list the full settings of all the receive connectors on an default edge server 2013? I think when I manually configure them, the setup may complete and allow me to uninstall. Hopefully.

Any advice?


Exchange 2010 and Exchange 2013 coexistence

$
0
0

Durring migration process which virtual directories from Exchange 2010 should be pointed to Exchange 2013, all of them?


bostjanc

Upgrade to exchange 2016 from Exchange 2010 SP3 with hybrid server into the cloud

$
0
0

Hi,

I have 6 Mailbox Servers, 2 HT servers 2 CAS servers and 1 Hybrid server for office 365.

2 ADFS Serves, 2 proxy servers behind a netscaler.

I am planning to do an upgrade to exchange 2016.  what is needed to do this upgrade mostly for the hybrid server does this need to be done and hybrid config needs to be re-run?

Any info would be appreciated

also does anyone know if there is a best practice security wise on how to publish OWA.  It looks like everything runs off the mailbox server  So I was thinking it would be a a good idea to have our netscaler use 2 mailbox servers( that don't have any mailboxes on it) so it could transfer requests to actual data so the netscaler doesn't have access to mailbox servers with real data on it.

any suggestions or thoughts are greatly appreciated

Thanks,

Joe

CU9 disables connection to Exchange 2013

$
0
0

In stage 14 cumulative update 9 throws this error twice:

Error:

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

       remove-PerfCounters -DefinitionFileName MailboxTransportSubmissionServicePerfCounters.xml

       new-PerfCounters -DefinitionFileName MailboxTransportSubmissionServicePerfCounters.xml

         " was run: "System.ComponentModel.Win32Exception (0x80004005): The configuration registry key is invalid

  at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)

  at Microsoft.Exchange.Management.Tasks.ManagePerfCounters.DeletePerfCounterCategory()

  at Microsoft.Exchange.Management.Tasks.RemovePerfCounters.InternalProcessRecord()

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

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

Now it is no longer possible to connect to the server from outlook. How to debug this?

Marcel



Retention Policy To Tasks

$
0
0

Does anyone know how to set a retention policy to tasks in Exchange 2013, it seems to be grouped with the inbox default folder which requires its own retention rules. There is an RPT for Calendars\Tasks however it does not seem to work despite not having a retention period. When I recover a deleted task, it auto deletes again per the "inbox" retention policy.

Thank you to anyone that can help!

Exchange 2013 Hybrid

$
0
0

Hi,

We are currently setting up an hybrid exchange (Exchange 2013 / Office365)

I have a question

If mailbox1 is on premises, will it have a copy on O365? So that if On Prem Exchange will be down, user1 can still access his email thru O365.

Does Hybrid Setup offer High Availabilty?

Viewing all 7129 articles
Browse latest View live


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