Getting Powershell errors and I notice the following:
I have 2 Domain Controllers and both have Microsoft Exchange Service Account OUs but only one
has Microsoft Exchange System Objects.
Is that correct or are the DCs out of sync and if so how to I sync them. I have tried thru AD Sites and Service but the Object OU never copies over.
Any assistance is appreciated.
Thanks
Dave
Dave Kozlowski
Hi,
I tried to do a migration from Exchange 2007 to Exchange 2013 about 2 months ago. I used this document http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx
But I also used this technet one http://technet.microsoft.com/en-us/library/jj898581(v=exchg.150).aspx
However when bringing up the Exchange 2013 mail server there was no mail flow (when using the default receive connectors) after moving all the mail boxes from Exchange 2007 which meant I had to move all the mailboxes back. Infact there was no mail flow within the Exchange 2013 server (I.E. when emailing from user1 to user2 that were both hosted on Exchange 2013 the mail would not send, it would stay in the outbox of user1). When I discovered that there was a mail flow issue I started googling and change a whole bunch of things and now I cannot remember what I changed and what the defaults values are. What is the best way to move forward from here. We are currently still running Exchange off the Exchange 2007 server but I still have all the mailboxes on the 2013 server so I cannot uninstall exchange 2013 to start over.
Hi All,
Wonder if any of you can assist with a public folder issue I am having with Exchange 2013. We have migrated from Exchange 2010 to 2013.
I have followed the guide for public folder migration here http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx
Everything went fine and as per the document - except I had to use the "largeitemlimit" parameter to get the public folder migration to complete.
We tested the public folder migration by adding content to public folders and creating public folders and it all appeared to be OK, we completed the migration and removed our old public folder databases from Exchange 2010.
However we noticed later that users cannot CREATE folders in SOME public folders. It appears from some testing that any folder that does not lie in the first public folder mailbox, end users cannot create public folders. Administrators can create them fine from the ECP - just not from outlook.
It also appears some users cannot see some folders that they have permissions to.
Can anyone assist with some ideas to resolve ?
Thanks.
I am actually trying to test to move our exchange ccr environment to new hardware (will upgrade after that).
initially my installation went fine and after install, I was able to replicate. the problem happens only after I moved the passive node to another hardware, installation went fine, it is just now having this issues with "access denied" and"read error" in application log even though reseeding seems happening as files are copied to the passive node.(tried different methods/reseeding remove logs, reinstall passive node without success)
question: I would like to just re-install active and passive nodes (leave all other exchange servers/hub,cas,edge/ along) and use the same name, ip, etc ...? Do I need to modify AD settings prior to the re-install? anything else need to be removed/updated prior to the re-install?
any suggestions is appreciated!
thanks
Hello,
I am getting the error message listed in the topic subject when i try to install the Exchange Server 2013 SP1 Evaluation Mode downloaded from your website. After completing all requirements & pre-requisites, I started the installation with the Mailbox& Client Access role selected, when i get to the screen which says "Readiness Check" main page subject, and the progress says Configuring Prerequisites, before any progress in the %, i get the error message:
The Type initializer for 'Microsoft.Exchange.Configuration.Tasks.ThrottlingModule1' threw an exception
and it says retry.
Knowing that the server is a member of a domain.How would i resolve this issue?
Thanks,
Elie
Hi folks, I need to know how to migrate room and equipment mailboxes cross-forest from an Ex2010 forest to a Ex2013 forest. For the time being, the Ex2013 forest is just going to be a Resource Forest. We've got an ERP system (and other things) to plan for before we actually migrate the AD accounts/computers, etc. I've got the process down for normal mail users, but need some guidance on rooms and equipment.
When I tried running the Prepare-MoveRequest script for a 2010 Room, it created a disabled mail user in 2013. Will this convert to a room mailbox once we migrate the Room mailbox? If not, what's the correct way to do such a move?
There are only about 100 mailboxes, we're migrating over a two night period, so we aren't worried about a plan for any coexistence.
I need some advise on updating Exchange 2013.
[Main setup]
Domain:
DC Server 2012 R2 (DFL & FFL 2008 R2)
Exchange:
CAS 2013 on 2012 R2 no CU
MBX01 2013 on 2012 R2 no CU (DAG)
MBX02 2013 on 2012 R2 no CU (DAG)
[Updates]
After the main setup we installed 2013 CU3 for DC compatibility.
[Next update]
We want to install SP1 on the 2013 Servers. Is this recommended? What can go wrong as it is an unsupported configuration. 2012 R2 and Exchange 2013 CU3. Especially WinRM 3.0 vs 4.0.
MBX01 wont go into MMode and its impossible to activate DB on it. We also have lot of warnings and errors on all 3 servers. About diskspace and so on, we are sure diskspace is not a issue.
Can we force SP1 on a 2012 R2 and Exchange 2013 cu3 setup without damaging the Exchange organization? Any recommendations?
Hello All,
I`m unable to roll Alternate Service account to the following env:
2x Exchange 2013 SP1 CAS Only Servers on Windows Server 2012 R2
3X Exchange 2013 SP1 MB Only Servers on Windows Server 2012 R2
It was working fine on the same environment in the same domain, but with Exchange 2013 CU3 on Windows Server 2012.
Here is the output:
[PS] D:\Exchange Server\scripts>.\RollAlternateServiceAccountPassword.ps1 -ToSpecificServers server6,server7
GenerateNewPasswordFor contoso\casasa$ -Verbose
========== Starting at 04/09/2014 14:57:42 ==========
VERBOSE: Effective parameters that were passed to this script:
Key Value
--- -----
ToSpecificServers True
GenerateNewPasswordFor contoso\casasa$
Verbose True
Identity {server6, server7}
VERBOSE: Examining the state of the local runspace ...
VERBOSE: Preparing the destination ...
VERBOSE: Destination server identities: server6 server7
VERBOSE: Retrieving CAS server objects with credentials (passwords=False):
server6, server7
VERBOSE: Retrieving ASA credentials from server server6
VERBOSE: Creating a new PowerShell session for server6. contoso.com
VERBOSE: Connecting to server6. contoso.com
Cannot process argument transformation on parameter 'Identity'. Cannot convert value "server6" to type
"Microsoft.Exchange.Configuration.Tasks.ClientAccessServerIdParameter". Error: "Cannot convert hashtable to an object
of the following type: Microsoft.Exchange.Configuration.Tasks.ClientAccessServerIdParameter. Hashtable-to-Object
conversion is not supported in restricted language mode or a Data section."
+ CategoryInfo : InvalidData: (:) [Get-ClientAccessServer], ParameterBindin...mationException
+ FullyQualifiedErrorId : ParameterArgumentTransformationError,Get-ClientAccessServer
+ PSComputerName : server6.contoso.com
VERBOSE: Retrieving ASA credentials from server server7
VERBOSE: Creating a new PowerShell session for server7. contoso.com
VERBOSE: Connecting to server7. contoso.com
Cannot process argument transformation on parameter 'Identity'. Cannot convert value "server7" to type
"Microsoft.Exchange.Configuration.Tasks.ClientAccessServerIdParameter". Error: "Cannot convert hashtable to an object
of the following type: Microsoft.Exchange.Configuration.Tasks.ClientAccessServerIdParameter. Hashtable-to-Object
conversion is not supported in restricted language mode or a Data section."
+ CategoryInfo : InvalidData: (:) [Get-ClientAccessServer], ParameterBindin...mationException
+ FullyQualifiedErrorId : ParameterArgumentTransformationError,Get-ClientAccessServer
+ PSComputerName : server7. contoso.com
VERBOSE: Destination servers:
VERBOSE: Checking version requirements for the destination servers ...
VERBOSE: Preparing the credential source ...
VERBOSE: Looking up account casasa$ in domain contoso
RecordErrors : Couldn't figure out valid servers from the specified destination scope. Check your parameters and try
again.
At D:\Exchange Server\scripts\RollAlternateServiceAccountPassword.ps1:996 char:1
+ RecordErrors -ExceptionsOnly { $script:success = Body }
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException
+ FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,RecordErrors
Retrieving the current Alternate Service Account configuration from servers in scope
VERBOSE: Retrieving CAS server objects with credentials (passwords=False):
Alternate Service Account properties:
Per-server Alternate Service Account configuration as of the time of script completion:
========== Finished at 04/09/2014 14:58:18 ==========
THE SCRIPT HAS FAILED
[PS] D:\Exchange Server\scripts>
I also noticed differences in the behavior of other cmdlets. I guess these are coming from PS 4.0 that comes with Server 2012 R2.
Can someone suggest resolution, different then revisiting the script?
Thanks
Environment: Exchange 2013 SP1 installed on Windows 2012 R2 in a coexistence with Exchange 2010.
So, let me start by mentioning I've read and tried everything here:
http://social.technet.microsoft.com/Forums/en-US/34ed5347-90f9-4ab7-91c3-9665f8ace432/ecp-redirects-to-owa-in-exchange-2013?forum=exchangesvradminlegacy
And here:
http://social.technet.microsoft.com/Forums/en-US/fe43a7b6-0c4a-446e-a205-100c1ccfaec3/exchange-2013-ecp-redirects-to-owa?forum=exchangesvradmin
So in other words, I have already tried: (also on the first two below, I've tried https://localhost, https://myserver.domain.local)
So please, do not suggest me trying these steps again or reading the other threads, I have already tried all above multiple times. I always mark answers and always give helpful votes when they
are deserved.
Thanks
Hi
We've had to uninstall one of our Exchange 2013 servers to reinstall a fresh copy.
The uninstall went fine, but now the RemoteMonitoring healthset is showing unhealthy. On checking there is still a healthmanagerobservermonitor for the removed server.
Does anyone know of a way to remove this monitor?
Thanks
Andy
I was having great time with my Exchange Server 2013 until I tried to clone it to avoid fresh installation of another Exchange 2013 server. Steps taken
(1)Clone the Exchange1 and turn it off
(2) Brought the Clone Exchange2, renamed it, change the IP configurations,
(3) Re-ran the ADprep/Doamin prep
(4) Checked the ASDIedit to verify the Schema/configuration in AD
(5) Restarted I and was able to logon to the Exchange2
(6) Brought up the Exchange1, but unable to logon because the name was no longer in AD database
-----------------------------------------------------------------------------------------------------------------
What I did to fix this:
(7) Rejoin the Exchange1 to the domain - and was able to logon
(8) Unable to access ECP or OWA of any of the two servers.
(9) Errors received - Fix the configuration file of the application
My Question - How to I fix the configuration file as suggested (via powershell or GUI or ASDIedit.msc)?
Environment:
Win Server 2003 R2 SP2 GC running Exchange 2007 SP2
Win Server 2012 R2 PDC GC
Win Server 2012 R2 SharePoint 2013
Win Server 2012 R2 Exchange 2013
Problem:
When I tried to migrate from the exchange 2013 from the exchange 2007 I get the following message from the Exchange 2013 setup;
All Exchange 2007 Servers in the organization must have exchange 2007 sp3 or later installed.
Issue:
I downloaded Exchange 2007 sp3 but when I install it I get the following error message which will not allow me to continue no matter how many times I reboot, the good thing after rebooting is you do not have to start from the begin and picks up where it left off;
Summary: 10 item(s). 5 succeeded, 1 failed.
Elapsed time: 00:52:33
Organization Preparation
Completed
Elapsed Time: 00:19:23
Preparing Setup
Completed
Elapsed Time: 00:03:09
Remove Exchange Files
Completed
Elapsed Time: 00:13:37
Preparing Files
Completed
Elapsed Time: 00:00:02
Copy Exchange Files
Completed
Elapsed Time: 00:08:28
Hub Transport Role
Failed
Error:
Unable to cast COM object of type 'Interop.MSClusterLib.ClusterClass' to interface type 'Interop.MSClusterLib.ISCluster'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{F2E606E4-2631-11D1-89F1-00A0C90D061E}' failed due to the following error: No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE)).
Warning:
An unexpected error has occurred and debug information is being generated: Unable to cast COM object of type 'Interop.MSClusterLib.ClusterClass' to interface type 'Interop.MSClusterLib.ISCluster'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{F2E606E4-2631-11D1-89F1-00A0C90D061E}' failed due to the following error: No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE)).
Elapsed Time: 00:07:53
Client Access Role
Cancelled
Mailbox Role
Cancelled
Management Tools
Cancelled
Finalizing Setup
Cancelled
I have been searching the internet and have not found anything related to this and anything I do find related to SQL or office.
Any tips, links or helpful information with be appreciated greatly as I would like to put this behind me!
Regards,
Dividu
Hi Guys,
Most probably I am going to deliver one project in nearest future, which included to move Mailboxes and mail data from Novel Group-wise to Exchange 2013. i want to know what should be the approach and what are the per-requisites that need to be consider to perform Migration steps in above scenario? please let me know how the mail-flow work to/from Group-wise to exchange 2013 and vice-verse. please suggest me some initial steps and URLs for this requirement. i want to be clarified logically before i suggest any solution on this to my customer.
step by step docs will be more helpful to achieve this goal..
Regards,
Aanand Singh
Hi Experts,
I am facing issue while installing exchange 2013 sp1 in mixed(2007, 2010 and 2013) environment, the issue is: CAS role not installing/configuring "Echangeweb" (ews) virtual directory if i install only CAS role. If i install CAS role and mailbox role then there is no issue, everything is fine.
In single CAS role installation, "EWS" folder is creating inside "Exchangeweb" folder but it shows empty folder.
If any one have any idea please let me know, why this is happening? was i am doing anything wrong while installing?
Regards,
Ravi Nalla
Hewlett-Packard
ravinalla
Hi
I'm getting these errors while trying to install Microsoft Exchange Server 2013 on my Windows Server 2008 R2 SP1 the user i'm using is the Administrator and it is already a member of "Enterprise Admins" and "Schema Admins"
in my organization there is 6 Exchange server 2013 in 3 site windows server 2012 in this case
I have to install exchange 2013 in windows Server 2008 r2 sp1
the functional level 2008 R2 I getting these errors please help.
Errors:
This computer doesn't belong to a valid Active Directory site. Check the site and subnet definitions.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.InvalidADSite.aspx
Error:
A reboot from a previous installation is pending. Please restart the system and then rerun Setup.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.RebootPending.aspx
Error:
There is a pending reboot from a previous installation of a Windows Server role or feature. Please restart the computer and then run Setup again.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.PendingRebootWindowsComponents.aspx
Error:
You must be a member of the 'Organization Management' role group or a member of the 'Enterprise Admins' group to continue.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.GlobalServerInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedBridgeheadFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedCafeFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedFrontendTransportFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedMailboxFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedClientAccessFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedUnifiedMessagingFirstInstall.aspx
Error:
Setup encountered a problem while validating the state of Active Directory: Could not find information about the local site. This can be caused by incorrect configuration of subnets or sites or by replication latency. See the Exchange setup log for more
information on this error.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.AdInitErrorRule.aspx
Error:
Either Active Directory doesn't exist, or it can't be contacted.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.CannotAccessAD.aspx
I have got this information from digicert http://www.digicert.com/internal-names.htm is there any way to ensure all clients works properly.
Should we have to change our internal domain names to external ones, this will be a problem and visible. It gives us insecured feeling.
Experts please throw your views.
Thanks!
Regards, Ganesh, MCTS, MCP, ITILV2 This posting is provided with no warranties and confers no rights. Please remember to click Mark as Answer and Vote as Helpful on posts that help you. This can be beneficial to other community members reading the thread.
When installing the sp1 update for exchange 2013 we came across these errors:
The following error was generated when "$error.Clear();
$BEVdirIdentity = $RoleNetBIOSName + "\ECP (Exchange Back End)";
$be = get-EcpVirtualDirectory -ShowMailboxVirtualDirectories -Identity
$BEVdirIdentity -DomainController $RoleDomainController -ErrorAction SilentlyCo
ntinue;
if ($be -eq $null)
{
new-EcpVirtualDirectory -Role Mailbox -WebSiteName "Exchange Back End"
-DomainController $RoleDomainController;
set-EcpVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication
:$false -WindowsAuthentication:$true;
}
set-EcpVirtualdirectory -Identity $BEVdirIdentity -InternalUrl $null -
ExternalUrl $null;
. "$RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1"
-AppPoolName:"MSExchangeECPAppPool" -Version:"v4.0";
" was run: "The virtual directory 'ecp' already exists under 'exchangeserver.domain.local/Exchange Back End'.
Parameter name: VirtualDirectoryName".
The following error was generated when "$error.Clear();
$BEVdirIdentity = $RoleNetBIOSName + "\ECP (Exchange Back End)";
$be = get-EcpVirtualDirectory -ShowMailboxVirtualDirectories -Identity
$BEVdirIdentity -DomainController $RoleDomainController -ErrorAction SilentlyCo
ntinue;
if ($be -eq $null)
{
new-EcpVirtualDirectory -Role Mailbox -WebSiteName "Exchange Back End"
-DomainController $RoleDomainController;
set-EcpVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication
:$false -WindowsAuthentication:$true;
}
set-EcpVirtualdirectory -Identity $BEVdirIdentity -InternalUrl $null -
ExternalUrl $null;
. "$RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1"
-AppPoolName:"MSExchangeECPAppPool" -Version:"v4.0";
" was run: "The operation couldn't be performed because object 'exchangeserver
\ECP (Exchange Back End)' couldn't be found on 'dcserver.domain.local'.".
The following error was generated when "$error.Clear();
$BEVdirIdentity = $RoleNetBIOSName + "\ECP (Exchange Back End)";
$be = get-EcpVirtualDirectory -ShowMailboxVirtualDirectories -Identity
$BEVdirIdentity -DomainController $RoleDomainController -ErrorAction SilentlyCo
ntinue;
if ($be -eq $null)
{
new-EcpVirtualDirectory -Role Mailbox -WebSiteName "Exchange Back End"
-DomainController $RoleDomainController;
set-EcpVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication
:$false -WindowsAuthentication:$true;
}
set-EcpVirtualdirectory -Identity $BEVdirIdentity -InternalUrl $null -
ExternalUrl $null;
. "$RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1"
-AppPoolName:"MSExchangeECPAppPool" -Version:"v4.0";
" was run: "The operation couldn't be performed because object 'exchangeserver
\ECP (Exchange Back End)' couldn't be found on 'dcserver.domain.local'.".
I have not been able to find any information on the cause of these errors, any help would be appreciated.
Hi everyone,
I've successfully installed multiple Mailbox and CAS 2013 SP1 servers into an existing Exchange 2010 environment.
However, when I get to the Edge Transport role on a separate server, at step 7 of 9, it throws the following error:
Error: The following error was generated when "$error.Clear(); new-ExchangeServer" was run: "Value cannot be null. Parameter name: Cannot get child of ADObjectId: this is a GUID based ADObjectId.".
Any ideas what could be causing this? I haven't been able to find anything of significance while searching around...
Thanks!
We are in the middle of an Exchange 2013 migration from 2007 and this is the 2nd time I've encountered this issue. The migrated user cannot open outlook or log into owa. The error that is thrown in owa is below. I cant really find any info on this error. Also, notice the date. No idea where its getting that. We've moved about 7000 users and I've seen this on two of them. I'd appreciate any insight on this. Thanks.
X-OWA-Error: SDServerErr;Microsoft.Exchange.UM.UMCommon.InvalidPrincipalException X-OWA-Version: 15.0.847.32 X-FEServer: server01 X-BEServer: server01.domain.com Date: 1/2/1601 2:47:50 PM
Rich
Hi folks,
I am planning my exchange 2010 migration to 2013.
Right now I am doing some labs. In my lab the certificate from my internal CA is Invalid. I did everything like the MVA videos explained and also I already ave some exchange experience.
I guess the problem is in the internal CA.
How can I troubleshoot this?
Thanks!