I have Exchange 2013 installed on the only domain controller.

When I go to put Exchange 2013 into maintenance mode from the Exchange Management Shell using the command:

Set-ServerComponentState server.domain.local -Component ServerWideOffline -State Inactive -Requester Maintenance

I get the following error:

"Set-ServerComponentState : The term 'Set-ServerComponentState' is not recognized as the name of a cmdlet, function,
script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is
correct and try again.
At line:1 char:1
+ Set-ServerComponentState server.domain.local -Component ServerWideOffline -State ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (Set-ServerComponentState:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException"

How do I put this Exchange server into maintenance mode?

I am trying to put Exchange into maintenance mode as the CU6 Cumulative Update is failing with the below error:

Error:The following error was generated when"$error.Clear();
          try
          {
            $Target = $env:COMPUTERNAME
            try
            {
              $exSrv = get-ExchangeServer $Target -ErrorAction SilentlyContinue
            }
            catch
            {
              Write-ExchangeSetupLog -Warning "Unable to set monitoring and server state to inactive.Setup will continue.";
            }

            if ($exSrv -eq $null)
            {
              Write-ExchangeSetupLog -Warning "$Target isnot an ExchangeServer.Unable to set monitoring and server state to inactive.Setup will continue.";
              return
            }

            Set-ServerComponentState $Target -Component Monitoring -Requester Functional -State Inactive
            Write-ExchangeSetupLog -Info "Monitoring has been set to Inactivewhile setup is running."

            Set-ServerComponentState $Target -Component RecoveryActionsEnabled -Requester Functional -State Inactive
            Write-ExchangeSetupLog -Info "RecoveryActionsEnabled has been set to Inactivewhile setup is running."

            Set-ServerComponentState $Target -Component ServerWideOffline -Requester Functional -State InActive
            Write-ExchangeSetupLog -Info "The server state has been set to Inactivewhile setup is running."
          }
          catch
          {
            Write-ExchangeSetupLog -Warning "Unable to set monitoring and server state to inactive.Setup can notcontinue.";
            throw;
          }" was run:"Microsoft.Exchange.Data.Directory.ADOperationException: Active Directory operation failed on EXCH01.domain.local. This error is not retriable. Additional information: Insufficient access rights to perform the operation.
Active directory response: 00002098: SecErr: DSID-03150E49, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0
 ---> System.DirectoryServices.Protocols.DirectoryOperationException: The user has insufficient access rights.
   at System.DirectoryServices.Protocols.LdapConnection.ConstructResponse(Int32 messageId, LdapOperation operation, ResultAll resultType, TimeSpan requestTimeOut, Boolean exceptionOnTimeOut)
   at System.DirectoryServices.Protocols.LdapConnection.SendRequest(DirectoryRequest request, TimeSpan requestTimeout)
   at Microsoft.Exchange.Data.Directory.PooledLdapConnection.SendRequest(DirectoryRequest request, LdapOperation ldapOperation, Nullable`1 clientSideSearchTimeout, IActivityScope activityScope, String callerInfo)
   at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException, Boolean isSync)
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Data.Directory.ADDataSession.AnalyzeDirectoryError(PooledLdapConnection connection, DirectoryRequest request, DirectoryException de, Int32 totalRetries, Int32 retriesOnServer)
   at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException, Boolean isSync)
   at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException)
   at Microsoft.Exchange.Data.Directory.ADDataSession.Save(ADObject instanceToSave, IEnumerable`1 properties, Boolean bypassValidation)
   at Microsoft.Exchange.Management.SystemConfigurationTasks.SetServerComponentState.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".Error:The following error was generated when"$error.Clear();
          try
          {
            $Target = $env:COMPUTERNAME
            try
            {
              $exSrv = get-ExchangeServer $Target -ErrorAction SilentlyContinue
            }
            catch
            {
              Write-ExchangeSetupLog -Warning "Unable to set monitoring and server state to inactive.Setup will continue.";
            }

            if ($exSrv -eq $null)
            {
              Write-ExchangeSetupLog -Warning "$Target isnot an ExchangeServer.Unable to set monitoring and server state to inactive.Setup will continue.";
              return
            }

            Set-ServerComponentState $Target -Component Monitoring -Requester Functional -State Inactive
            Write-ExchangeSetupLog -Info "Monitoring has been set to Inactivewhile setup is running."

            Set-ServerComponentState $Target -Component RecoveryActionsEnabled -Requester Functional -State Inactive
            Write-ExchangeSetupLog -Info "RecoveryActionsEnabled has been set to Inactivewhile setup is running."

            Set-ServerComponentState $Target -Component ServerWideOffline -Requester Functional -State InActive
            Write-ExchangeSetupLog -Info "The server state has been set to Inactivewhile setup is running."
          }
          catch
          {
            Write-ExchangeSetupLog -Warning "Unable to set monitoring and server state to inactive.Setup can notcontinue.";
            throw;
          }" was run:"Microsoft.Exchange.Data.Directory.ADOperationException: Active Directory operation failed on EXCH01.domain.local. This error is not retriable. Additional information: Insufficient access rights to perform the operation.
Active directory response: 00002098: SecErr: DSID-03150E49, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0
 ---> System.DirectoryServices.Protocols.DirectoryOperationException: The user has insufficient access rights.
   at System.DirectoryServices.Protocols.LdapConnection.ConstructResponse(Int32 messageId, LdapOperation operation, ResultAll resultType, TimeSpan requestTimeOut, Boolean exceptionOnTimeOut)
   at System.DirectoryServices.Protocols.LdapConnection.SendRequest(DirectoryRequest request, TimeSpan requestTimeout)
   at Microsoft.Exchange.Data.Directory.PooledLdapConnection.SendRequest(DirectoryRequest request, LdapOperation ldapOperation, Nullable`1 clientSideSearchTimeout, IActivityScope activityScope, String callerInfo)
   at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException, Boolean isSync)
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Data.Directory.ADDataSession.AnalyzeDirectoryError(PooledLdapConnection connection, DirectoryRequest request, DirectoryException de, Int32 totalRetries, Int32 retriesOnServer)
   at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException, Boolean isSync)
   at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException)
   at Microsoft.Exchange.Data.Directory.ADDataSession.Save(ADObject instanceToSave, IEnumerable`1 properties, Boolean bypassValidation)
   at Microsoft.Exchange.Management.SystemConfigurationTasks.SetServerComponentState.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".Error:The following error was generated when"$error.Clear();
          try
          {
            $Target = $env:COMPUTERNAME
            try
            {
              $exSrv = get-ExchangeServer $Target -ErrorAction SilentlyContinue
            }
            catch
            {
              Write-ExchangeSetupLog -Warning "Unable to set monitoring and server state to inactive.Setup will continue.";
            }

            if ($exSrv -eq $null)
            {
              Write-ExchangeSetupLog -Warning "$Target isnot an ExchangeServer.Unable to set monitoring and server state to inactive.Setup will continue.";
              return
            }

            Set-ServerComponentState $Target -Component Monitoring -Requester Functional -State Inactive
            Write-ExchangeSetupLog -Info "Monitoring has been set to Inactivewhile setup is running."

            Set-ServerComponentState $Target -Component RecoveryActionsEnabled -Requester Functional -State Inactive
            Write-ExchangeSetupLog -Info "RecoveryActionsEnabled has been set to Inactivewhile setup is running."

            Set-ServerComponentState $Target -Component ServerWideOffline -Requester Functional -State InActive
            Write-ExchangeSetupLog -Info "The server state has been set to Inactivewhile setup is running."
          }
          catch
          {
            Write-ExchangeSetupLog -Warning "Unable to set monitoring and server state to inactive.Setup can notcontinue.";
            throw;
          }" was run:"Microsoft.Exchange.Data.Directory.ADOperationException: Active Directory operation failed on EXCH01.domain.local. This error is not retriable. Additional information: Insufficient access rights to perform the operation.
Active directory response: 00002098: SecErr: DSID-03150E49, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0
 ---> System.DirectoryServices.Protocols.DirectoryOperationException: The user has insufficient access rights.
   at System.DirectoryServices.Protocols.LdapConnection.ConstructResponse(Int32 messageId, LdapOperation operation, ResultAll resultType, TimeSpan requestTimeOut, Boolean exceptionOnTimeOut)
   at System.DirectoryServices.Protocols.LdapConnection.SendRequest(DirectoryRequest request, TimeSpan requestTimeout)
   at Microsoft.Exchange.Data.Directory.PooledLdapConnection.SendRequest(DirectoryRequest request, LdapOperation ldapOperation, Nullable`1 clientSideSearchTimeout, IActivityScope activityScope, String callerInfo)
   at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException, Boolean isSync)
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Data.Directory.ADDataSession.AnalyzeDirectoryError(PooledLdapConnection connection, DirectoryRequest request, DirectoryException de, Int32 totalRetries, Int32 retriesOnServer)
   at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException, Boolean isSync)
   at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException)
   at Microsoft.Exchange.Data.Directory.ADDataSession.Save(ADObject instanceToSave, IEnumerable`1 properties, Boolean bypassValidation)
   at Microsoft.Exchange.Management.SystemConfigurationTasks.SetServerComponentState.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 windows 2012 DC installed and This is a production server, I know that Its not recommended to install exchange server on the DC. I had to do it because of management instructions.

I have tried to install the exchange 2013 and received many errors at the time of installations and then finally I changed the path for installation to D drive. its installed successfully.

The issue is its not opening the OWA or ECP.

The owa virtual directory got deleted as part of troubleshooting to recreate it. but after that its not creating, I reset the iis and created the virtual drive for owa from the iis console but not through powershell and then i thought to install the SP1 so that it can be fixed.

At the time of installation client access front end service role ..it gives error

Error:
The following error was generated when "$error.Clear();
          $FEOWAVdirIdentity = $RoleNetBIOSName + "\OWA (Default Web Site)";
          $FEOWAVdir = get-OwaVirtualDirectory -Identity $FEOWAVdirIdentity -DomainController $RoleDomainController;

          if ($FEOWAVdir -ne $null)
          {
            Set-OwaVirtualDirectory -Identity $FEOWAVdir.Identity -ExternalUrl $FEOWAVdir.ExternalUrl -InternalUrl $FEOWAVdir.InternalUrl -ExternalAuthenticationMethods $FEOWAVdir.ExternalAuthenticationMethods -BasicAuthentication ([Convert]::ToBoolean($FEOWAVdir.BasicAuthentication)) -WindowsAuthentication ([Convert]::ToBoolean($FEOWAVdir.WindowsAuthentication)) -DigestAuthentication ([Convert]::ToBoolean($FEOWAVdir.DigestAuthentication)) -FormsAuthentication ([Convert]::ToBoolean($FEOWAVdir.FormsAuthentication)) -LiveIdAuthentication ([Convert]::ToBoolean($FEOWAVdir.LiveIdAuthentication)) -OAuthAuthentication ([Convert]::ToBoolean($FEOWAVdir.OAuthAuthentication));
          }
        " was run: "You must set a default domain if LogonFormat is set to UserName.".

* First, I install Exchange 2013 SP1 on my server, so step 14 of 18 to 100% then alert error:

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

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: "Failed to mount database "Mailbox Database 0487331505". Error: An Active Manager operation failed. Error: The database action failed. Error: Operation failed with message: MapiExceptionJetErrorRequiredLogFilesMissing: Unable to mount database. (hr=0x80004005, ec=-543)
Diagnostic context:
    Lid: 65256  
    Lid: 10722   StoreEc: 0xFFFFFDE1
    Lid: 1494    ---- Remote Context Beg ----
    Lid: 45120   dwParam: 0x667F9F
    Lid: 57728   dwParam: 0x668155
    Lid: 46144   dwParam: 0x66851E
    Lid: 34880   dwParam: 0x66851E
    Lid: 34760   StoreEc: 0xFFFFFDE1
    Lid: 41344   Guid: 581e05de-0b68-45e0-af85-c1d96eb3e939
    Lid: 35200   dwParam: 0x548
    Lid: 46144   dwParam: 0x66885A
    Lid: 34880   dwParam: 0x66885A
    Lid: 56264   StoreEc: 0x1388    
    Lid: 46280   StoreEc: 0xFFFFFDE1
    Lid: 1750    ---- Remote Context End ----
    Lid: 1047    StoreEc: 0xFFFFFDE1 [Database: Mailbox Database 0487331505, Server: ex2013.dothanhauto.com]".

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

* After I run install Exchange 2013 SP1 again, so go to step 5 of 9 then alert error.

* Now, my Exchange 2013 not run. So bad. Please help me fix it! Thank you so much!

Hi

I am planning to migration public folder across the forest but unable find any documentation. can you guys share the step by step guide to move/migrate public folder. we have exchange 2013 in source and target forest.   

Please help!

Hello All,

I need a bit of help.  I took over a network that was running Small Business Server 2008 with Exchange installed.  I bought a new Dell and virtualized three servers.  One of my virtual servers has Windows Server 2012 and Exchange 2013. After I installed Exchange 2013, I went to migrate some mailboxes from the Exchange 2007 machine (SBS).  When I did, the test mailboxes moved but would not open in outlook. The mailboxes that I need to move are huge and the test box wasn't.

I contacted Microsoft and we could not figure it out.  So I just left all the mailboxes on the SBS Exchange 2007 system. I would like to remove the .VHD that has Exchange 2013 on it.  I am going to virtualize the SBS and then reformat the server that the SBS resides on.  I would then like to install 2012 R2 and Exchange 2007 on that server to migrate the mailboxes and kill the SBS virtual server.

First - Is this even possible?

Second - Can I kill the Exchange 2013 .vhd without any issues?

I don't know if Exchange 2013 has been improved and I should try it again but I am a bit gun shy now.  Any advice or help would be greatly appreciated.

Thanks

Will

Hi,

This is my Folder to Mailbox file, migrating public folders from 2010 to 2013:

"FolderPath","TargetMailbox""\","Hierarchy-PF""\IPM_SUBTREE\Office1","Office1-PF""\IPM_SUBTREE\Office2","Office2-PF""\IPM_SUBTREE\Office3","Office3-PF""\IPM_SUBTREE\Office4","Office4-PF"

All these PF mailboxes live in a dedicated database. But only the mailbox DB containing Hierarchy-PF is growing and my initial migration (New-PublicFolderMigrationRequest / Step 5 in the technet article) is over 50% percent complete. This mailbox is going to be over 300GB big and I gather the limit is 100GB, I'm sure that can be exceeded without problems, but I had several different reasons splitting the mailboxes and data the way I wanted above. 

Questions:

1. How do I achieve the end result I want? Do I need to add a \ to the end of the office1-5 ipm_subtree perhaps?

2. Is there any problem with me stopping the existing migration, deleting that request/mailbox/DB and starting over?

Thanks.

Hi,

We have a Windows Server 2008 R2 machine running Exchange 2010 (sorry, there wasn't an option for a 2010 forum). As a company which handles payments, we need to be PCI DSS registered and the scan has picked up a failing point being we don't have an SSL Certificate installed. I have purchased one via GoDaddy and followed the instructions on their site to install it, however the PCI DSS scan is still failing because of the following reason:-

"The following certificate was at the top of the certificate chain sent by the remote host, but is signed by an unknown certificate authority."

The certificate at the top of the chain is the 'built-in' default certificate. How do I promote the installed GoDaddy certificate to the top of the chain?

Thanks

I have a Barracuda filter receiving all inbound internet mail which delivers to the edge server (both in DMZ).  I have one 2010 edge server and one 2010 ht,cas,mailbox server.   I have added a 2013 server and started working on configuring virtual directories.  This is a far as I have gotten. Goal is once new box is working to move all mailboxes to 2013 server and remove 2010 mail box server and keep Barracuda and 2010 edge server to pass mail to the 2013 box.

My issue is the edge server is already passing inbound internet mail to the new 2013 server.  I see the mail being accepted by the Barracuda and message tracking on the edge shows it as delivered to the new 2013 server, but mailbox users never receive.

Is my solution to simply create a new send connector from the 2013 server to the 2010 box or could this be something else?

And why is it delivering to a server with now mailboxes on it yet?

Thank you for any help

dean

Hi Gents 

I am currently planning to upgrading one of our clients Exchange 2010 Server to Exchange 2013. I know that the simplest solution would be install exchange 2013 with CU2 and make the 2010 coexisting but below is what my limitations are

Currently - Customer is on a SBS physical server that has Exchange 2010 SP1 installed, only 30 clients at the moment. 

I have already prepared a server 2012r2 vm where i will install the Exchange 2013, My question is, can i simply just install the new exchange 2013 in the new VM server, Export all the mailbox as pst from the exchange 2010 server and then import all the mailbox pst into exchange 2013?

Given that they only have 30 clients and the current server is a physical server, i don't have enough time to plan a p2v migration or upgrade current exchange 2010 to sp3 for the coexistence to work so i thought maybe exporting and importing pst will be a better solution. can someone confirm if this will work or if you have tried this method at all ?

Hi,

I have a problem with a coexistence scenario with Exchange 2013 SP1 CU 6 and Exchange 2007.

I have migrated some mailbox to Exchange 2013 but i want to migrate back some mailbox.

I have use New-MoveResquest command to do this but the move failed with the status "FailedOther" and with PercentComplete "95"%

When i try the commandlet Get-MoveRequestStatistics "Name of the Mailbox" -IncludeReport | FL Report , i have this error message (I translate the message because it's in French originaly):

15/10/2014 16:55:30 [Mailbox] Fatal error UpdateMovedMailboxPermanentException has occurred
15/10/2014 16:55:30 [aaelyw96-vm] Offline Mailbox move was postponed , transient error.

Do you know what i can do for this error?

Thanks in advance.

Sebastien

Hello Guys

I have a mailflow issue, hoping someone can help with detail description, below is the setup

Exchange server 2010 SP3 with all roles in one server

Exchange server 2013 SP1 with CU6 with all roles in one server - this server is in a different subnet to the 2010 server. I am able to see exchange 2010 databases and mailboxes from Exchange 2013. For testing purposes, I have moved 3 mailbox from 2010 to 2013. These 3 mailbox, is able to send and receive email from Internet but to each other via OWA or Outlook. These 3 mailbox also not able to send to receive email from any mailbox that is still in 2010 server via OWA or Outlook. I am not planning the whole server cutover in a go and planning to do state by stage mailbox migration so I need mailflow working properly. When I send an email from one of the migrated mailbox that is in 2013 server, I can see that the email leaves the mailbox outbox and sits in the queue ..

Can someone please provide detailed solution what needs to be configured?

MCITP, MCSA, MCSE,VCP - Consultant, Solution Design, Implementation

Preparing for Migration from Exchange 2003 to Exchange 2010/13

and or Office 365, you'll need to find "Deleted Mailboxes".

Since PowerShell doesn't have any Calls direct to Ex2003 for this, we have to pull WMI objects.

This Script will pull all the Deleted Mailboxes from Ex2003 from your Ex2010 Native or Hybid Server.

$now = Get-Date #Used for timestamps
$date = $now
$Deleted_Mailboxes = Get-Wmiobject -namespace root\MicrosoftExchangeV2 -class Exchange_Mailbox -computer EX2003Server -Filter "DateDiscoveredAbsentInDS is not null" MailboxDisplayName,ServerName,StorageGroupName,StoreName,Size,DateDiscoveredAbsentInDS | sort-object MailboxDisplayName
$Deleted_Mailboxes | Export-Csv "F:\Reports\Deleted_Mailboxes$Date.csv" -NoTypeInformation
#Exports collected Data From Ex2003Server (your server name) to CSV on F drive

Hi All, I am working on a Migration project Ex2007 to Ex2013

I have few queries on this topic

1, Do we need to migrate(Upgrade) the Address List from Exchange 2007 to 2013? because when we migrate from Exchange 2003 to 2007 or 2010 we have convert the LDAP to OPATH.. Just want to clear on this topic

2, Can we place a FSW on Domain Controller?

I have seen few articles but they says, yes we can? but i dont see any such word in Tech Net website.

Need your feedback on this topic

Thanks,

Balgates

Regards, Balgates

Hi all,

When I try to connect to to Exchange powershell, this is what I get. Redirection disabled, binding seems correct (80 and 443 only with correct SSL) and ECP and other directories are working fine. Thanks

VERBOSE: Connecting to exchange.company.uni.edu.au.
New-PSSession : [exchange.company.uni.edu.au] The WinRM service cannot process the request because the request needs
to be sent to a different machine. Use the redirect information to send the request to a new machine.  Redirect
location reported: https://exchange.company.uni.edu.au/powershell?serializationLevel=Full;ExchClientVer=15.0.516.32;c
lientApplication=ManagementShell;TargetServer=;PSVersion=4.0&sessionID=Version_15.0_(Build_515.32)=rJqNiZqNgbqnvLe+sbi6
0Z6b0YqOipGWkJHRio7RmpuK0Z6Kgc7Gy87GxsnPzMmBzc3Qzs7Qzc/OzN/LxczIxc/L376y . To automatically connect to the redirected
URI, verify the "MaximumConnectionRedirectionCount" property of the session preference variable "PSSessionOption", and
use the "AllowRedirection" parameter on the cmdlet.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportRedirectException
    + FullyQualifiedErrorId : RedirectInformationRequired,PSSessionOpenFailed
Failed to connect to an Exchange server in the current site.
Enter the server FQDN where you want to connect.: exchange.company.com.au
VERBOSE: Connecting to exchange.company.com.au.
New-PSSession : [exchange.company.com.au] Connecting to remote server exchange.company.com.au failed with the following error
message : WinRM cannot process the request. The following error occurred while using Kerberos authentication: Cannot
find the computer exchange.company.com.au. Verify that the computer exists on the network and that the name provided is
spelled correctly. For more information, see the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : NetworkPathNotFound,PSSessionOpenFailed

I have two problems, but the second problem started when I tried to integrate an office web apps server with exchange 2013 so I am putting them into one post.

I have two Windows Server 2012 boxes, one with Exchange 2013 (both roles) one with only Office Web Apps Server 2013. Exchange 2013 was working perfectly internally and externally.

First issue - When I try and preview a document, I get the message "The WebReady Document Viewing service has been disabled by the administration for your organization. For more information, contact your helpdesk"."

I am not using https for this test setup (AllowHttp is True), and the http.../hosting/discovery URL works fine both internally and externally.  I followed this guide to integrate Exchange with my Office WA server:

http://technet.microsoft.com/library/2591b1be-92c4-4192-9f5e-e4e6b319170a

Second issue - if I access Exchange OWA on the internal URL http://server/owa, when I click on a message the right pane says in red text "Your request can't be completed right now. Please try again later.

If I access the external URL (even from an internal computer, where DNS is setup to resolve to the internal IP address of the exchange CAS), everything works fine (except for the Webready Document viewing)

This second issue only started occurring when I tried to integrate office web apps, but even If I remove the WACDiscoveryEndPoint from the exchange OrganizationConfig the problem persists.

Any help appreciated.

Blair

Hi,

I am working on our Exchange 2010-2013 migration and have come upon an issue after migrating test mailboxes. After migrating a mailbox to the 2013 database I am able to open it in OWA but when I try to open it via Outlook I get the error message "Cannot open your default e-mail folders. You must connect to Microsoft Exchange with the current profile before you can synchronize your folders with your Outlook data file (.ost)". I also get the same message when I create a new mailbox in the 2013 database and try to open it.

I have deleted and recreated the profile on the client. When I create the profile and let autodiscovery configure the information I get a message that the Ex2013 server is not available and the window comes up allowing me to enter the server and mailbox name. If I enter the Ex2013 server name I get the same error whether I enter the hostname of the server or the full DNS name. When I enter the Ex2010 server name it accepts it and converts it to the DNS name of the Ex2013 server but Outlook will still not open.

Both servers are single servers hosting all the roles. The Ex2010 server is using an internal certificate using the internal DNS. When I originally set up the Ex2013 server I did the same thing but have since purchased a SAN certificate based on our public DNS and installed that. The 2 names on the certificate are webmail.(xxxx).com and autodiscover.(xxxx).com. I was getting certificate errors on machines and now I have the SAN certificate that seems to have solved that problem.

I have a feeling I might have 2 problems, 1 with the autodiscover settings and another with the mailbox looking at the 2010 CAS rather than 2013. After doing some research I'm still a little lost in how I move forward on this one. Any help would be appreciated.

Peter Haase

All mailboxes migrated from 2007 to 2013, so next step is Public Folder migration. I think I've got all the steps laid out, but had one question about the PublicFoldertoMailboxMapGenerator.ps1 script.  I've been messing around with the size parameter (ie. .\PublicFoldertoMailboxMapGenerator.ps1 300MB, etc.). The resulting csv lists the number of PF mailboxes I should created based on the size I input.  In the results are things like: "Mailbox3","\IPM_SUBTREE\Telecommunications". Can I just renamed IPM_SUBTREE\Telecommunications to |IPM_SUBTREE\whatever? And does the migration just randomly distribute PF content among the PF mailboxes I create? Don't even know if it matters, but it seems odd to have it named IPM_SUBTREE\Telecommunications when it will contain PF folders from all different depts. Am I understanding it correctly?

I need to install Exchange 2010 in the same forest with Exchange 2013. However, mistakenly ran /PrepareSchema and /PrepareAD for Exchange 2013 before installing Exchange 2010 first.

I got the message "Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2010 server roles have been detected in this topology. After this operation, you will not be able to install any Exchange 2010 servers. For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.
aspx"

How can I undo AD prep for Exchange 2013?