question

MaherRamadan-2265 avatar image
0 Votes"
MaherRamadan-2265 asked MaherRamadan-2265 answered

not able to install exchange 2019 in exhange 2013 envirounment

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)".

office-exchange-server-administrationoffice-exchange-online-itprooffice-exchange-server-deployment
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

MaherRamadan-2265 avatar image
0 Votes"
MaherRamadan-2265 answered

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

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

AshokM-8240 avatar image
0 Votes"
AshokM-8240 answered MaherRamadan-2265 commented

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
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

yes i did, as far as i can see the schema is extended, this is per the setup logs, if i run it separately it throws a funny error, it says the user i am using is enterprise admin but yes it is not ok to run this command, i have added the user account to all groups you could imagine - all admin groups, even exchange groups yes it is the same, i will confirm on the CU part

0 Votes 0 ·

CU23 now exchange is installed but power shell is not working not connecting to any exchange server

0 Votes 0 ·
KaelYao-MSFT avatar image
0 Votes"
KaelYao-MSFT answered MaherRamadan-2265 commented

@maherramadan-2265
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.


· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Do you mean you uninstalled the servers by removing them from ADSI edit? It’s not supported and may cause problems.
no when i uninstall them the where removed so they disappeared, they where removed properly
Have you run /prepareAD before install?
the first time i installed them i did not run that as the installation should take care of that, yes i will run that and share the errors

0 Votes 0 ·
MaherRamadan-2265 avatar image
0 Votes"
MaherRamadan-2265 answered MaherRamadan-2265 published

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

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

AshokM-8240 avatar image
0 Votes"
AshokM-8240 answered MaherRamadan-2265 commented

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

· 3
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

thanks AshokM
it is added to the trusted subsystem group, rebooted the server
we managed to install a fresh copy of exchange without errors!!! the only thing left now is that freshly installed server is connecting to PowerShell but to other servers

but no on the local host

VERBOSE: Connecting to
New-PSSession : [EXCHSRV] Connecting to remote server EXCHSRV failed with the following error
message : 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], PSRemotin
gTransportException
+ FullyQualifiedErrorId : -2144108173,PSSessionOpenFailed

0 Votes 0 ·

now i am getting this

New-PSSession :myserver Connecting to remote server myserver failed with the following error
message : 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], PSRemotin
gTransportException
+ FullyQualifiedErrorId : -2144108173,PSSessionOpenFailed

0 Votes 0 ·

@MaherRamadan-2265
Please try recreating the powershell virtual directory on the Exchange 2019 server which has problems.
Follow these steps:
1.open Powershell and run this command

  Add-PSSnapin Microsoft.Exchange.Management.PowerShell.SnapIn; 

2.remove the PowerShell virtual directory from the default web site

 Remove-PowerShellVirtualDirectory “Powershell (Default Web Site)”

3.recreate the PowerShell virtual directory

 New-PowerShellVirtualDirectory -Name Powershell -RequireSSL:$False

4.restart IIS

 iisreset /noforce


See if it can solve your problem.


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.

0 Votes 0 ·
MaherRamadan-2265 avatar image
0 Votes"
MaherRamadan-2265 answered MaherRamadan-2265 edited

sorry did not work, i also did the binding solution here

https://www.experts-exchange.com/articles/34069/Blank-Page-Screen-In-OWA-EAC-Exchange-2013-2016-2019-Server.html

Error occurred during the Kerberos reponse.
[Server=myserver, TimeStamp = 911/2020 14:48:37]
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], PSRemotin
gTransportException
+ FullyQualifiedErrorId : -2144108173,PSSessionOpenFailed

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

MaherRamadan-2265 avatar image
0 Votes"
MaherRamadan-2265 answered

now i am getting this error - another fresh installation

New-PSSession : [server-01.domain] Processing data from remote server exch-01.sbc.sa failed with the following error
message: [ClientAccessServer=server,BackEndServer=server.domain,RequestId=f6739ccd-2789-45ba-a56a-a5b7d900aecb,TimeSt
amp=9/12/2020 2:28:03 AM]
[AuthZRequestId=00b8ab23-5922-4662-becc-cf93db5d1c89][FailureCategory=AuthZ-CmdletAccessDeniedException] The operation
couldn't be performed because 'domain\servername$' 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], PSRemotin
gTransportException
+ FullyQualifiedErrorId : IncorrectProtocolVersion,PSSessionOpenFailed

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

MaherRamadan-2265 avatar image
0 Votes"
MaherRamadan-2265 answered AshokM-8240 commented

now i am getting this error - another fresh installation

New-PSSession : [server-01.domain] Processing data from remote server exch-01.sbc.sa failed with the following error
message: [ClientAccessServer=server,BackEndServer=server.domain,RequestId=f6739ccd-2789-45ba-a56a-a5b7d900aecb,TimeSt
amp=9/12/2020 2:28:03 AM]
[AuthZRequestId=00b8ab23-5922-4662-becc-cf93db5d1c89][FailureCategory=AuthZ-CmdletAccessDeniedException] The operation
couldn't be performed because 'domain\servername$' 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], PSRemotin
gTransportException
+ FullyQualifiedErrorId : IncorrectProtocolVersion,PSSessionOpenFailed

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Can you add the Exchange powershell snapin in Windows powershell using the below method,

Open the Windows powershell as run as administrator
Run the below command,

Add-PSSnapin Microsoft.Exchange.Management.PowerShell.SnapIn

Then run, Get-ExchangeServer.

Please post the error in case if it doesn't work.

Login to EAC and check if the powershell virtual directory has the proper internal URL
Check the powershell virtual directories settings in IIS

https://docs.microsoft.com/en-us/exchange/clients/default-virtual-directory-settings?view=exchserver-2019

0 Votes 0 ·
MaherRamadan-2265 avatar image
0 Votes"
MaherRamadan-2265 answered AshokM-8240 commented

thanks AshokM
no errors, only CAS servers showing roles as none which i don't believe is an issue, i think this issue has something to do with AD
it must, i re installed exchange many times with no errors, either AD miss configuration or policy issue

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Does the output of the Get-ExchangeServer show CAS role for Exchange 2019? Can you please post the screenshot of Get-ExchangeServer | select ServerRole,AdminDisplayVersion

Are you able to access https://localhost/ecp on the new Exchange 2019? Are you able to see the Powershell virtual directory in IIS?

can you please check the powershell virtual directory URL and settings as provided in the earlier comment.

0 Votes 0 ·
MaherRamadan-2265 avatar image
0 Votes"
MaherRamadan-2265 answered

no mailbox

Get-ExchangeServer | select ServerRole,AdminDisplayVersion

Mailbox Version 15.0 (Build 1497.2)
Mailbox Version 15.0 (Build 1497.2)
Mailbox Version 15.0 (Build 1497.2)
None Version 15.0 (Build 1497.2)
None Version 15.0 (Build 1497.2)
Mailbox Version 15.0 (Build 1497.2)
None Version 15.0 (Build 1497.2)
Mailbox Version 15.2 (Build 659.4)
Mailbox Version 15.2 (Build 659.4)
Mailbox Version 15.2 (Build 659.4)

Are you able to access https://localhost/ecp on the new Exchange 2019? (yes) Are you able to see the Powershell virtual directory in IIS? (yes)

can you please check the powershell virtual directory URL and settings as provided in the earlier comment.
if you mean the cert binding, i don't think this is an issue, i have checked on older serves the binding of exchange self signed cert on the back end site and that is ho wit is, however i have change that to be the same on the front end and same issue

one more note, when i add the new server to exchange management security group (bad thing to do) it starts connecting to other servers but not itself or the other 2019, it says this server is not assigned any role - when i add it there it starts connecting to older servers only

one more - guess this proves the PS VD is ok, from the server i am able to connect over power shell using the below approach and that is who i was able to get the above results


$UserCredential = Get-Credential
$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri http://myserverFQDN/PowerShell/ -Authentication Kerberos -Credential $UserCredential
Import-PSSession $Session -DisableNameChecking

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.