not able to install exchange 2019 in exhange 2013 envirounment

Maher Ramadan 286 Reputation points
2020-09-08T19:44:52.96+00:00

hello, this error is driving me crazy, installation fails at stage 7 - transport role with the below error
those exch 2019 servers where already installed before but their power shell virtual directory crashed from some reason, so i decided to remove them and reinstall
the servers are gone from the servers ou under adsi edit admin group
no one server crashed as below is visible but still failing

Error:
The following error was generated when "$error.Clear();
if ($server -eq $null)
{
new-exchangeserver -DomainController $RoleDomainController -Name $RoleNetBIOSName
}
" was run: "Microsoft.Exchange.Data.Directory.SystemConfiguration.DefaultAdministrativeGroupNotFoundException: Could not find the default Administrative Group 'Exchange Administrative Group (FYDIBOHF23SPDLT)'.
at Microsoft.Exchange.Data.Directory.SystemConfiguration.ADTopologyConfigurationSession.GetAdministrativeGroup(String callerFilePath, Int32 callerFileLine, String memberName)
at Microsoft.Exchange.Data.Directory.SystemConfiguration.ADTopologyConfigurationSession.GetAdministrativeGroupId(String callerFilePath, Int32 callerFileLine, String memberName)
at Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeServer.PrepareDataObject()
at Microsoft.Exchange.Configuration.Tasks.SetTaskBase`1.InternalValidate()
at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__91_1()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

Exchange Online
Exchange Online
A Microsoft email and calendaring hosted service.
6,199 questions
Exchange | Exchange Server | Management
0 comments No comments
{count} votes

Accepted answer
  1. Maher Ramadan 286 Reputation points
    2020-10-29T09:36:44.95+00:00

    thank you all i ended up creating a windows powershell shortcut with exchange snapin pre mounted on it

    a workaround but it works

    %SystemRoot%\system32\WindowsPowerShell\v1.0\powershell.exe -NoExit Add-PSSnapin Microsoft.Exchange.Management.PowerShell.SnapIn%SystemRoot%\system32\WindowsPowerShell\v1.0\powershell.exe -NoExit Add-PSSnapin Microsoft.Exchange.Management.PowerShell.SnapIn

    0 comments No comments

12 additional answers

Sort by: Most helpful
  1. Ashok M 6,846 Reputation points
    2020-09-09T06:25:18.463+00:00

    Hi,

    Did you run the below commands using the Exchange 2019 setup file before the installation? If not, please prepare the Active directory before the installation

    setup.com /PrepareSchema /IAcceptExchangeServerLicenseTerms

    setup.com /PrepareAD /IAcceptExchangeServerLicenseTerms

    For Coexistence, Exchange 2013 Cumulative Update 21 (CU21) or later is required on all Exchange 2013 servers in the organization, including Edge Transport servers.


  2. Kael Yao 37,751 Reputation points Moderator
    2020-09-09T07:06:56.357+00:00

    @Maher Ramadan
    Hi,
    the servers are gone from the servers ou under adsi edit admin group
    Do you mean you uninstalled the servers by removing them from ADSI edit? It’s not supported and may cause problems.

    Have you run /prepareAD before install?
    Please run the command and see if the problem persists. Make sure your account is a member of the Enterprise Admins security group.
    If you see any error code, post the detailed information in text or by screenshot.
    (Notice: Please hide your personal information in the screenshot for security.)


    If the response is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


  3. Maher Ramadan 286 Reputation points
    2020-09-09T18:37:45.617+00:00

    this is the error

    VERBOSE: Connecting to EXH
    New-PSSession : [exh] Processing data from remote server exh failed with the following error message:
    [ClientAccessServer=EXH,BackEndServer=exh,RequestId=6a345a7c-33ff-47f7-989b-042ba4bfa107,TimeStamp=9/9/2020
    6:29:19 PM] [AuthZRequestId=2fc6b190-07c6-4eb7-acae-ebe62f1df425][FailureCategory=AuthZ-CmdletAccessDeniedException] The
    operation couldn't be performed because '\exh$' couldn't be found. For more information, see the
    about_Remote_Troubleshooting Help topic.
    At line:1 char:1

    • New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Micr ...
    • ~~~~~~~~~~~~~~~~~~~~~~~
    • CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotingTransportE
      xception
    • FullyQualifiedErrorId : IncorrectProtocolVersion,PSSessionOpenFailed
      VERBOSE: Connecting to AZ
      New-PSSession : [az..sa] Processing data from remote server az..sa failed with the following error
      message: [AuthZRequestId=6667a20e-9a3b-4f71-9189-e42a5dad5f9d][FailureCategory=AuthZ-CmdletAccessDeniedException] The user
      ".sa/VMSERVERS/EXH" isn't assigned to any management roles. For more information, see the about_Remote_Troubleshooting
      Help topic.
      At line:1 char:1
    • New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Micr ...
    • ~~~~~~~~~~~~~~~~~~~~~~~
    • CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotingTransportE
      xception
    • FullyQualifiedErrorId : IncorrectProtocolVersion,PSSessionOpenFailed
      VERBOSE: Connecting to AZ
      New-PSSession : [az02..sa] Processing data from remote server az02..sa failed with the following error
      message: [ClientAccessServer=AZ02,BackEndServer=exh,RequestId=11cd6c1e-b819-4e2d-a3f9-0b36a1657655,TimeStamp
      =9/9/2020 6:30:28 PM] [AuthZRequestId=4b53601f-5844-410a-bb47-a07d38490e69][FailureCategory=AuthZ-CmdletAccessDeniedException]
      The operation couldn't be performed because '\EXH$' couldn't be found. For more information, see the
      about_Remote_Troubleshooting Help topic.
      At line:1 char:1
    • New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Micr ...
    • ~~~~~~~~~~~~~~~~~~~~~~~
    • CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotingTransportE
      xception
    • FullyQualifiedErrorId : IncorrectProtocolVersion,PSSessionOpenFailed
      VERBOSE: Connecting to EXH-
      New-PSSession : [exh-cas..sa] Processing data from remote server exh-cas..sa failed with the following error message:
      [AuthZRequestId=408e073a-add8-4e56-8630-60ce47fa8e0b][FailureCategory=AuthZ-CmdletAccessDeniedException] The user
      ".sa/VMSERVERS/EXH" isn't assigned to any management roles. For more information, see the about_Remote_Troubleshooting
      Help topic.
      At line:1 char:1
    • New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Micr ...
    • ~~~~~~~~~~~~~~~~~~~~~~~
    • CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotingTransportE
      xception
    • FullyQualifiedErrorId : IncorrectProtocolVersion,PSSessionOpenFailed
    0 comments No comments

  4. Ashok M 6,846 Reputation points
    2020-09-09T20:06:40.173+00:00

    So, prepareSchema and PrepareAD ran without any issues and the error was thrown only during the setup. Also, now the exchange 2019 has been installed but unable to connect the powershell. Please correct me if i misunderstood.

    For the powershell error, try adding the exchange server object to the "Exchange Trusted subsystem" if its not already present and the logged on/administrator account to the "Organization management" group and check again


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.