Exchange 2013 S/MIME with Server 2008 R2

So I am trying to configure S/MIME on my 2013 Exchange server, but the process in which I need to export the rootca is vague and only applies to Server 2012/Windows 8 because of the export-certificate command.
http://technet.microsoft.com/en-us/library/hh848628.aspx
My domain consists of a single DC/CA and member server that hosts Exchange. Both servers are on Server 2008 R2, and I have installed PowerShell v4.0 on my DC to try an export the certificate but it continues to fail with:
export-certificate : The term 'export-certificate' 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.
The examples given to set up the export are equally vague:
PS C:\>$cert= (Get-ChildItem -Path cert:\CurrentUser\My\EEDEF61D4FF6EDBAAD538BB08CCAADDC3EE28FF) <--What path is this referencing??If anybody has experience doing this I would greatly appreciate some guidance.Mike

I was able to figure out the export portion. I needed to select both of my Root CA's certificates then run through the export wizard and export to .sst was available. Now the problem I'm having is when attempt to import the certs into Exchange
2013.
[PS] C:\>Set-SmimeConfig -SMIMECertificateIssuingCA (Get-Content rootca1.sst -Encoding Byte)
Starting a command on the remote server failed with the following error message : The WinRM client sent a request to the remote WS-Management service and was notified that the request size exceeded the configured MaxEnvelopeSize quota.
For more information, see the about_Remote_Troubleshooting Help topic.
+ CategoryInfo : OperationStopped: (exchange.contoso.com:String) [], PSRemotingTransportExcept
ion
+ FullyQualifiedErrorId : JobFailure
+ PSComputerName : exchange.contoso.com

Similar Messages

Exchange 2013 SP1 on Windows Server 2008 R2 Enterprise - BSOD after DAG creation

Hi,
We are running Exchange 2007 SP3 RU13 on Windows 2003 R2 with SP2 in a 2003 native AD environment and recently decided to upgrade to Exchange 2013. We installed a pair of new DELL R420 servers running Windows 2008 R2 Enterprise then threw Exchange 2013 SP1
onto them. This all went fine and the servers are running stable.
We connected the second NIC of each server to the other via a separate switch, the second NIC has Client for MS Networks and File/Printer Sharing disabled plus a totally separate subnet with no DNS or GW address assigned. DAG setup was run and completed
OK. I created the DAG network in Exchange and enabled replication, I also left replication enabled across the production LAN. Finally, I went into the advanced network settings and made sure the replication network was below the production network in the binding
order.
After an hour or two the BSOD's started.. both servers would crash within a few minutes of each other and reboot with a Kernel Panic. I have attached the contents of the dump file below. This seems to happen every few hours and it always seems to be the
server hosting the passive DB copies crashes first, followed by the server hosting the active copies. Note that if we disable the replication NIC on both servers they do not crash.
I got the impression from somewhere that perhaps the servers had mixed up the binding order and were trying to use the replication network as primary, losing access to AD and rebooting (which I have read is the behaviour for Exchange now). It appears the
Exchange Health service has killed WININIT which causes the crash.
Thanks!!!
The crash dump text is below:
CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa80192ebb30, Terminating object
Arg3: fffffa80192ebe10, Process image file name
Arg4: fffff80001dc37b0, Explanatory message (ascii)
Debugging Details:
PROCESS_OBJECT: fffffa80192ebb30
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: wininit
FAULTING_MODULE: 0000000000000000
PROCESS_NAME: MSExchangeHMWo
BUGCHECK_STR: 0xF4_MSExchangeHMWo
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80001e4cab2 to fffff80001abebc0
STACK_TEXT:
fffff880`0d7f39c8 fffff800`01e4cab2 : 00000000`000000f4 00000000`00000003 fffffa80`192ebb30 fffffa80`192ebe10 : nt!KeBugCheckEx
fffff880`0d7f39d0 fffff800`01df7abb : ffffffff`ffffffff fffffa80`1bcf3060 fffffa80`192ebb30 fffffa80`383ea060 : nt!PspCatchCriticalBreak+0x92
fffff880`0d7f3a10 fffff800`01d77674 : ffffffff`ffffffff 00000000`00000001 fffffa80`192ebb30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x17486
fffff880`0d7f3a60 fffff800`01abde53 : fffffa80`192ebb30 fffff880`ffffffff fffffa80`1bcf3060 00000000`00000000 : nt!NtTerminateProcess+0xf4
fffff880`0d7f3ae0 00000000`7772157a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`34eed638 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7772157a
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: wininit.exe
FAILURE_BUCKET_ID: X64_0xF4_MSExchangeHMWo_IMAGE_wininit.exe
BUCKET_ID: X64_0xF4_MSExchangeHMWo_IMAGE_wininit.exe
Followup: MachineOwner

Hi Darrkon,
I suggest checking the status of the HealthMailbox on each of servers.
Also try to re-create the mailbox. You can safely delete and recreate health mailboxes.
Be aware that any local Managed Availability probes that are using the these mailboxes will fail until the Microsoft Exchange Health Manager is restarted. Once that service is restarted, it will recreate any mailboxes that it needs.
More details in the following similar thread, just for your reference:
BSOD after creating DAG
http://social.technet.microsoft.com/Forums/exchange/en-US/44d1cd98-cba1-4ed0-b0e7-8aa76ee3eabc/bsod-after-creating-dag
Thanks
Mavis
Mavis Huang
TechNet Community Support

Error During install Exchange 2013 through Powershell on Server 2012 "Mailbox role: Client Access service"

Dear all
During install Exchange 2013 through Powershell on Server 2012 I got this error in Mailbox role: Client Access service :
The following error was generated when "$error.Clear();
$BEVdirIdentity = $RoleNetBIOSName + "\OWA (Exchange Back End)";
new-OwaVirtualDirectory -Role Mailbox -WebSiteName "Exchange Back End" -DomainController $RoleDomainController
set-OwaVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;
" was run: "An error occurred while creating the IIS virtual directory 'IIS://MONAMBX2.mona.local/W3SVC/2/ROOT/o
wa' on 'MONAMBX2'.".
The following error was generated when "$error.Clear();
$BEVdirIdentity = $RoleNetBIOSName + "\OWA (Exchange Back End)";
new-OwaVirtualDirectory -Role Mailbox -WebSiteName "Exchange Back End" -DomainController $RoleDomainController
set-OwaVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;
" was run: "The operation couldn't be performed because object 'MONAMBX2\OWA (Exchange Back End)' couldn't be fo
und on 'MonaDc1.mona.local'.".
Any advice please !!

I can't answer your question but I had a similar issue when I was trying to move our mailbox database off the C: drive. Our environment still has an Exchange 2007 server in it and when I was trying to move the database on the 2013 server, I would get
error messages saying the database does not exist. It seemed like it was trying to move the database on the 2007 server from the similar error messages that I was getting. To get around it, I deleted the database and created a new one on the drive
where we wanted it.
I discovered this when I was configuring the Antispam settings. I deleted our 2007 settings, added them to the 2013 shell, the settings appeared on our 2007 server. The shell on 2013 was making changes to 2007.
I'm not sure if there is a "Get|Set or New" command that I/we should be using when this happens. Or maybe my issues will be fixed if I just remove the Exchange 2007 server? I'm not ready to do that yet because I can't configure the spam filtering
on 2013 yet with its shell not being able to make the changes that we need.
I don't know if your environment is in coexistence mode like mine.
Hopefully someone else out there has an answer or can tell us when/how the shell can make the appropriate changes to the 2013 server. Does this happen after the 2007 server is removed?

Exchange 2013 EAC coexistence with Exchange 2007

Dear All,
I have an exchange organization comprized of single Exchange 2007 SP3 UR 15 running on Win2008 SP2 and two recently installed Exchange 2013 SP1 CU7 with CAS and Mailbox role running on Win 2012 R2.
Imidiantly after Exchange 2013 install, I am not able to login to Exchange 2013 EAC. When I enter my credentials domain\username, the EAC page simpli dose a quick refresh and I am back where I started.
I have tryid mutiple UTLs to access EAC page, such as:
https://localhost/ecp?ExchClientVer=15
https://localhost/ecp?ExchClientVer=14
https://localhost/ecp
Each of them show the same result, a page gets refreshet. I have tryid to move my Exchange Organization user mailbox to Exchange 2013 to see if that helps but the result.
I also noticed that OWA dosent work for mailboxes that are on Exchange 2013, they are redirected to Exchange 2007 even thou they are on Exchange 2013.
Any idea on this one?
Thank you
b.

Hi,
From your description, I would like to verify if you have configured Exchange 2013 namespace and virtual directories (such as OWA, ECP, OAB, Web Services, AutoDiscover)correctly. Please make sure these virtual directories are configured correctly and check
the result.
For more information about Exchange 2007 migration to Exchange 2013, here is a helpful blog for your reference.
Step-by-Step Exchange 2007 to 2013 Migration
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-2-step-by-step-exchange-2007-to-2013-migration.aspx
Hope this can be helpful to you.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

Configuration Exchange 2013 DAG on two Server Data center 2012 with Hyper -V roles

Dears,
I try to planning and installation two hosts ( Data center 2012 servers) then install Hyper-V role on both this server, then create VM on each Data center server to be install Exchange 2013 on them.
After that I want to configure DAG between Exchanges servers, so what are the prerequisite to do that ?
Note: I use external IBM storage that will be located all VMs and DAG
Many thanks

Hi Moon,
In addition to Gulab's suggestion, I would like to clarify the following things:
1. Yes, we can use Standard or Datacenter version of the Windows Server 2012 operating system to configure Exchange 2013 DAG.
2. Each member of the DAG should be running the same operating system.
3. The DAG with an even number of members should have a witness server. A witness server is a server outside a DAG that's used to achieve and maintain quorum when the DAG has an even number of members.
What's more, here are some helpful articles for your reference.
Planning for High Availability and Site Resilience
http://technet.microsoft.com/en-us/library/dd638104(v=exchg.150).aspx#HR
High Availability and Site Resilience
http://technet.microsoft.com/en-us/library/dd638137(v=exchg.150).aspx
Hope it helps.
If there are any problems, please feel free to let me know.
Best regards,
Amy
Amy Wang
TechNet Community Support

Exchange 2013 in coexistence with 2010, Outlook keep looking for Exchange 2010 server slow connection

All,
not sure if this topic has already answered, but can't find anything around.
Here's the scenario. Migrating from a single Exchange 2010 to a cluster of 2 + 1 Exchange 2013. Two in a site, One in the other site (DC).
I have migrated successfully a firsat batch of users. Mail flow works perfectly. The only thing is that often the migrated users are experiencing a long time (about 30 minutes) to get their Outlook syncronized. Both OL 2010 and 2013 doesn't make any difference.
They're using OL Anywhere, and I've already tried to rebuild the profile.
From a check on the OL connection status, looks like they're still looking for something on EX2010, but no idea what could be. If I disable the cache mode it works smooth and quick.
My best guess is that is something in cache they're trying to keep updated... but still this doesn't explain the huge delay.
Any help would be highly appreciated!
Thanks!

Hi Alessandro,
What happens in OWA? I guess it should be good.
Did you have public folders with Exchange 2010? Were they moved over to Exch 2013? Technically you should move the PF to the latest version from the legacy version before moving over the users?
- Moved the PF to OL2013. same behaviour
May be the outlook clients are looking for th OAB? Did you move the OAB to Exchange 2013?
- Did this too.
Try running outlook on safe mode and see what happens? may be one of the outlook add-in's are looking for something on Exchange 2010?
- Will try that....
Can you do a Test Email Auto Configuration in outlook (Hold CNTRL key and right click on outlook icon on status bar) and see if the exchange url's are pointed to Exch 2013?
- Will try that....
Is this happening to all migrated users or specific? Are they BlackBerry users?
- All users and there are no BB users
Do you have any archived emails on those migrated users? May be outlook is looking for some archived stuff on the Exch 2010 side?
- I instructed Exchange to migrate also the archiving database, however There are no archived mailbox on 2010
Could this be because of any calendar entries? May be migrated user mailboxes are having issues with working with non-migrated mailbox calendars?
- This maybe a possibility. I have only 10 users actively using Exchange, while all others have the mailboxes only because they've Lync. I've completed all migrations today, so there shouldn't be anything left on 2010
Let me know how it went - all the best!
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. Regards, Siva

Accessing Exchange 2013 Mailboxes from Terminal Server hosted on Server 2003 Std - Cert Issues

We are in the midst of deploying an Exchange 2013 SP1 CU5 environment and have run into some issues. Currently there is a good coexistence between a single Exchange 2007 server and the 5 2013 servers. Mail is flowing through 2013 and then being
relayed to 2007 when necessary.
We have a number of Server 2003 Terminal Servers. On two separate machines, both running the lastest rollups of Outlook 2010, any user with a 2013 mailbox receives a password prompt after launching Outlook. It is trying to connect to one of the
two CAS, fills in the user's account, and will not accept any password. In addition, a window pops up behind stating "There is a problem with the proxy server's security certificate. the name on the security certificate is invalid or does
not match the name of the target site mail.pvschemicals.com. Outlook is unable to connect to the proxy server. (error code 0)." 2007 mailboxes are not affected.
We have checked pretty much everything that we can think of. Virtual Directories are good, certificate is good, etc. The strange thing is that only happens on 2003 TS machines, so I have to think that it's related. Our 2008 TS' are just
find.
We have applied the 2003 SHA2 certificate hotfix.

Hi,
According to your description, the configurations of Outlook Anywhere are proper. And based on my research, the issue can be related to the version of the terminal server 2003. Thus, please check if your terminal 2003 server is 2003 R2 SP2 or later.
For more information, you can refer to the following thread:
http://social.technet.microsoft.com/Forums/exchange/en-US/295bf2bc-584b-4de2-85fb-94096fac52e7/outlook-connectivity-problem-on-2003-term-server-exchange-2013?forum=exchangesvrclients
Thanks,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Angela Shi
TechNet Community Support

Exchange 2013 / 2010 coexistence with different public domains

Currently in my organization
1x Exchange 2010 Standard w/SP3 - Client Access / Hub Transport
1x Exchange 2010 Standard w/SP3 - Unified Messaging Server (we also have Lync 2013 in the environment)
1x Exchange 2010 Standard w/SP3 - Mailbox
In my organization, we have approximately 600 mailboxes - 100 office staff, and 500 field employees using a mixture of Outlook 2007/2010/2013 and various mobile devices. Most of our field employees are in remote locations, several hundred
miles away. We have no IT staff in any of our field locations.
We also have two public domains that we use, though we are trying to phase out the old one to unify everything.
domain-old.com - Used when the company had a different name. All Exchange services are published with this one.
domain-new.com - Used after the company changed names. The goal is to publish all Exchange services with this one.
domain.local - Our internal Active Directory domain.
We use Microsoft Exchange Online Protection for all inbound/outbound email. We publish OWA, ActiveSync, etc. through our Sophos firewall. Also, we have two KEMP LoadMaster appliances that for high availability that we currently use for Lync 2013; they are
severely underutilized.
Goals for the Exchange migration
My primary goal is to introduce high availability into our environment by introducing redundancy on multiple levels. I would like to accomplish this by utilizing Exchange 2013 since we will need to purchase additional licensing anyway. My idea of the
final topology is:
2x KEMP LoadMaster appliances providing reverse proxy and load balancing to the CAS servers
2x Physical servers running Hyper-V, separated physically but in the same AD site. Each one would run:
1x VM with Exchange 2013 Standard w/SP1 - Client Access
1x VM with Exchange 2013 Enterprise w/SP1 - Mailbox - Utilizing DAGs for high-availability
I'd like all the new Exchange services to be published under the domain-new.com domain - such as mail.domain-new.com, mail.domain-new.com/owa, smtp.domain-new.com, etc.
We have purchased two new physical servers that will be Hyper-V hosts running Server 2012R2. My timeframe to start this project is within the next two weeks, so I'll be running the new Exchange 2013 VMs under Server 2012, not R2 as it won't be supported
until Exchange 2013 SP3 is released.
Deployment Plan
Install Exchange 2013 on new VMs.
Create CAS Array object.
Configure Exchange 2013 to publish under the new namespace.
Perform mailbox moves to 2013 for a small group (1-5 users) at a time. Recreate Outlook profiles and mobile device profiles for that group. Test and move to the next group.
Once all users are moved to the new namespace, decommission the Exchange 2010 servers.
Unknowns
My primary unknown is about the namespaces. All of the guides I have read strictly deal with keeping the existing namespace and having the Exchange 2013 CAS proxy requests to Exchange 2010 for mailboxes still on 2010. This should never be an issue for us
since we'll be using the new domain for each mailbox we move.
My question boils down to, is this a supported way to migrate to Exchange 2013? And if so, are there some materials or information to help me perform it this way?

Hi,
From the description, you want to install Exchange 2013 in another domain and then migrate from Exchange 2010 to Exchange 2013.
About DAG, all servers in a DAG must be running the same operating system. If there is only one mailbox server, there is no need to deploy DAG.
About CAS array, we should know that the CAS Array no longer exists in Exchange 2013.
About the namespace, based on my knowledge, we can introduce a new namespace. Just as what you said "This should never be an issue for us since we'll be using the new domain for each mailbox we move".
Here are some articles about how to upgrade from Exchange 2010 to Exchange 2013 in the same organization.
Checklist: Upgrade from Exchange 2010
Install Exchange 2013 in an Existing Exchange 2010 Organization
Upgrade from Exchange 2010 to Exchange 2013
Hope this helps.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Install Sharepoint 2013 Foundation on Windows Server 2008 R2

Could anyone please help me with the steps to install the Sharepoint 2013 foundation (including SQL express) with Windows Server 2008 R2 ?

You just need to download Foundation, run the pre-req installer, then run the setup executable, select Single Server, and this will install both SQL Express and Foundation. This isn't typically a 'recommended' setup, but it is an easy one.
Trevor Seward, MCC
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Exhcange 2003 on a 2003 server to exchange 2013 on a 2012 server - problems...

Hi
I removed my 2003 exhcange server physically and installed a 2012 server with exchange 2013 on it.
How do I get it to work? Where do I manage the exh 2013 server, through web interface only?
It installed, and worked for a few days (after i first had to remove the 2003 exchange server).
Now i only get "done" in the web interface after loggin in, outlook does'nt find the server when trying to connect to accounts and i can't access it through powershell (exchange management shell) and the Exchange Toolbox does not work neither... The
services are running though, but that's about it.
It won't uninstall cause there is mailboxes etc on the mailbox database..
My servers are on a standalone network, cut of from the internett..
How do I get a clean slate to install echange from scratch?? We only have a few users, so they won't mind..
Any help would be appreciated.. As of now, the server does nothing...

Hi andjohnsen,
What error did you get when you access it through EMS (exchange management shell)?
In addition, I recommend you remove all the exchange 2003 residual information and check if any helps:
Remove (legacy) Exchange server using ADSIEdit
Best regards,
Niko Cheng
TechNet Community Support

Can you use Forefront protection 2010 on a Exchange 2013 sp1 on-premises server?

Is it possible?
What are the alternatives if we exclude Exchange online protection?
Does this mean if you migrate from exchange 2010 to exchange 2013 you have "thrown your money away" for purchising forefront solution? Are there any "upgrade" forefront less-cost solution from 2010 to alternative versions?
with best regards,
bostjanc

Hi,
The following KB lists the supported Exchange Server versions.
http://technet.microsoft.com/en-us/library/ff921059.aspx
Best Regards,
Joyce
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

SP1 for Exchange 2013 install fails with ECP virtual directory issues and now transport service won't start and mail is unavailable

SP1 for Exchange 2013 install failed on me with ECP virtual directory issues:
Error:
The following error was generated when "$error.Clear();
          $BEVdirIdentity = $RoleNetBIOSName + "\ecp (name)";
          $be = get-EcpVirtualDirectory -ShowMailboxVirtualDirectories -Identity $BEVdirIdentity -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
          if ($be -eq $null)
          new-EcpVirtualDirectory -Role Mailbox -WebSiteName "name" -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 'server/name'.
Parameter name: VirtualDirectoryName".
Error:
The following error was generated when "$error.Clear();
          $BEVdirIdentity = $RoleNetBIOSName + "\ECP (name)";
          $be = get-EcpVirtualDirectory -ShowMailboxVirtualDirectories -Identity $BEVdirIdentity -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
          if ($be -eq $null)
          new-EcpVirtualDirectory -Role Mailbox -WebSiteName "name" -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 'server\ECP (name)' couldn't be found on 'DC0xx.domain.com'.".
Error:
The following error was generated when "$error.Clear();
          $BEVdirIdentity = $RoleNetBIOSName + "\ECP (name)";
          $be = get-EcpVirtualDirectory -ShowMailboxVirtualDirectories -Identity $BEVdirIdentity -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
          if ($be -eq $null)
          new-EcpVirtualDirectory -Role Mailbox -WebSiteName "name" -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 'server\ECP (name)' couldn't be found on 'DC0xx.domain.com'.".
!! And now transport service won't start and mail is unavailable !!
Any help would be appreciated.
I have removed the ecp site from default site and attempting to rerun SP1 now. I do not have high hopes. :(

Hi,
Thanks for your response.
From the error description, you need to manually remove the ECP with IIS manager in both the Default Web Site and the Exchange Back End firstly. And then continue the upgrade to check the result.
Hope this can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support

Installing Exchange 2007 on a Windows Server 2008

Hello I am new to the Microsoft forum and I have a quick question and please let me know if im posting my question in the wrong place. Im doing a school project were you have two servers with Windows Server 2008 installed on them. The first server suppose
to have Active directory and domain services followed by dns which I did. The second server which I just found out suppose to have installed Netframework 3.0, Wpa and Desktop experience roles then install Microsoft Exchange 2007. Well my issue is when I try
to install exchange on my second server it keeps giving me a error message saying my Active directory cannot be contacted or may not exist and that my second server has the wrong security credentials. I've taken the steps that Microsoft has advise by checking
my domain. Which I used the command Dcdiag.exe on my first server and it saids the domain is able to be contacted. Also when I joined my second domain I made sure to put the domain name of the first server in all caps followed by /Administrator and my password
and it said welcome to the domain. So has anybody run into that type of error message when trying to install exchange 2007 on a separate server? Lastly forget to include I also have web server IIS installed on the second server as well. Exchange is then asking
for IIS 7.0 ? So any tips or troubleshooting would be helpful since my professor wasn't much a help and I gotta turn this lab stuff in by next week.
thanks gmoney38

Not sure I need to check that through the dns is working far as ive seen in the server manager . Because I remember before I did this one command for the dns and it said something was wrong with the host A record. So I went through the hierarchy of
windows to that file and opened it up through the notepad it showed my loopback ip address 127.0.0.1 and localhost and not my domain name which I choose contoso01.com so from a previous forum I read if you change the localhost name to that domain name
that it would help but im not sure if this would in my case. Thanks for answering my question Mr. Ed but I still need some more help through!
gmoney38 ps plus im using vmware for this project to have the two servers i wonder if this is why im having issues!

Exchange 2013 issues along with toolbox and exchange powershell

I have a server 2012 with exchange 2013, no errors on install, we have about 50 user mailboxes setup. about 3-5 times a day sending and receiving will stop working, we have to reboot about 3 or 4 times then it starts working again.
Also the Exchange power shell doesnt work, we get :
VERBOSE: Connecting to NVSVMSX.KATV.local.
New-PSSession : [nvsvmsx.katv.local] Processing data from remote server nvsvmsx.katv.local failed with the following
error message: [ClientAccessServer=NVSVMSX,BackEndServer=nvsvmsx.katv.local,RequestId=3c4178cd-3e21-4ebf-9c65-23e5855cf
17f,TimeStamp=11/11/2014 6:53:03 PM]
[AuthZRequestId=b12c2ecf-ff1f-42df-b0f8-441878180bfa][FailureCategory=AuthZ-CmdletAccessDeniedException] The user
"KATV.local/Computers/NVSVMSX" 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 Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
gTransportException
+ FullyQualifiedErrorId : IncorrectProtocolVersion,PSSessionOpenFailed
we get that 3 times then nothing.
Also on the Toolbox we get MMC error
"Type is not resolved for member "Microsoft.Exchange.Configuration...."
Please help, we are at a loss and not sure what to do at this point, we have looked every where for a permissions issue and have found nothing so far.
thank you
BD

Hi,
Please check if this user was in Organization Management Group. If not, please use the following cmdlet to add this user to this group.
Add-RoleGroupMember “OrganizationManagement” -Member <member>
If this issue still exists, Run Setup /PrepareSchema and Setup /PrepareAD again.
In addition, please refer to this similar thread
https://social.technet.microsoft.com/Forums/sharepoint/en-US/33038c63-a993-4032-9355-023ae91a1c6a/cant-access-ecp-after-install?forum=exchangesvrdeploy
And hope KB 2898571 will be helpful for you.
To solve ToolBox issue, please try to install or uninstall ASP.NET 4.5 on Windows 8 or Windows Server 2012, use one of the following options:
Run the following command from an administrative command prompt: dism /online /enable-feature /featurename:IIS-ASPNET45
For Windows 8 client computers, turn on "IIS-ASPNET45" in "Turn Windows Features On/Off" under "Internet Information Services-> World Wide Web Services -> Application Development Features -> ASP.NET 4.5".
For Windows Server 2012 computers, enable "IIS-ASPNET45" using Server Manager, under "Web Server (IIS) -> Web Server ->Application Development -> ASP.NET 4.5".
Refer from
http://support.microsoft.com/kb/2736284
Best Regards.

Exchange 2013 Sp1 Coexistence with Exchange 2010 SP3 CU5 HTTP 500

I`m trying to make working OWA coexistence between Exchange 2013 SP1 and Exchange 2010 SP3 CU5.
When user login in to OWA where his mailbox is located on Exchange 2013 server it logon successful and owa opened. When i try to login to the same url with user whose mailbox is located on Exchange 2010 server i get Error http 50
The website cannot display the page : HTTP 500 »https://URLEXCHANGE2013/owa/auth.owa«
The same is, when i use https:// URLEXCHANGE2013/ecp?ExchClientVer=14
URL on Exchange 2013 are different as fro Exchange 2010.
I even tried to setup Internal URL for Exchange 2010 to bi set to »null ,Saem error
Exchange server 2013 Sp1 is installed on Windows server 2012 R2.

Assumption is correct. I have even enable verbose logging, and i can see MSExchange Front End HTTP Proxy , that successfully connect to Exchange 2010 server.
But remember Exchange 2013 is fresh installation on Windows server 2012 R2.
IIS LOG
2014-03-04 08:52:53 fe80::99d1:f542:a4d3:b469%12 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6001&CorrelationID=<empty>;&RequestId=391fd8b3-2b98-494a-8812-d38feda2e5a0&cafeReqId=391fd8b3-2b98-494a-8812-d38feda2e5a0;
443 companyNT\SM_9c071c4922fd420fb fe80::99d1:f542:a4d3:b469%12 MSRPC - 200 0 0 5484
2014-03-04 08:52:53 fe80::99d1:f542:a4d3:b469%12 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6001&CorrelationID=<empty>;&RequestId=27cfafa2-8224-4563-918b-0b228c6ee8d4&cafeReqId=27cfafa2-8224-4563-918b-0b228c6ee8d4;
443 - fe80::99d1:f542:a4d3:b469%12 MSRPC - 401 1 2148074254 0
2014-03-04 08:52:53 fe80::99d1:f542:a4d3:b469%12 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6001&CorrelationID=<empty>;&RequestId=6d930bcd-7bbc-415a-a25a-8d6488e91401&cafeReqId=6d930bcd-7bbc-415a-a25a-8d6488e91401;
443 - fe80::99d1:f542:a4d3:b469%12 MSRPC - 401 1 2148074254 15
2014-03-04 08:52:55 10.1.0.36 GET /owa/ &CorrelationID=<empty>;&cafeReqId=551cfdd9-18ac-42d8-aea3-cbb546c9d9fb; 443 - 10.1.0.36 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+6.3;+WOW64;+Trident/7.0;+.NET4.0E;+.NET4.0C) https://OWA.company.com/
302 0 0 9937
2014-03-04 08:52:56 10.1.0.36 GET /owa/auth/logon.aspx url=https%3a%2f%2fOWA.company.com%2fowa%2f&reason=0&CorrelationID=<empty>;&cafeReqId=c1b97df9-ec56-4906-b2f5-965551b720ae; 443 - 10.1.0.36 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+6.3;+WOW64;+Trident/7.0;+.NET4.0E;+.NET4.0C)
https://OWA.company.com/ 200 0 0 1015
2014-03-04 08:52:56 10.1.0.36 GET /owa/auth/logon.aspx replaceCurrent=1&url=https%3a%2f%2fOWA.company.com%2fowa%2f&CorrelationID=<empty>;&cafeReqId=b92ca682-04f4-4d4f-931e-9a95680ab9ea; 443 - 10.1.0.36 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+6.3;+WOW64;+Trident/7.0;+.NET4.0E;+.NET4.0C)
- 200 0 0 671
2014-03-04 08:52:58 10.1.0.36 GET /ecp/ &CorrelationID=<empty>;&cafeReqId=093bd01a-de59-4519-80f6-067484122091; 443 - 10.1.0.36 Mozilla/4.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+MSEXCHMON;+ACTIVEMONITORING) - 302 0 0 0
2014-03-04 08:52:58 10.1.0.36 GET /owa/auth/logon.aspx url=https%3a%2f%2fEXCH2013%2fecp%2f&reason=0&CorrelationID=<empty>;&cafeReqId=c2f7565d-ee6a-48f8-8d86-16d5d3ca65c1; 443 - 10.1.0.36 Mozilla/4.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+MSEXCHMON;+ACTIVEMONITORING)
- 200 0 0 0
2014-03-04 08:52:58 10.1.0.36 GET /ecp/ &CorrelationID=<empty>;&cafeReqId=ba633030-2376-4bad-a32f-8f160bd87bd4; 443 - 10.1.0.36 Mozilla/4.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+MSEXCHMON;+ACTIVEMONITORING) - 302 0 0 0
2014-03-04 08:52:58 10.1.0.36 GET /owa/auth/logon.aspx url=https%3a%2f%2fEXCH2013%2fecp%2f&reason=0&CorrelationID=<empty>;&cafeReqId=5e94172c-d97c-46a9-a602-6030d6f7da2c; 443 - 10.1.0.36 Mozilla/4.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+MSEXCHMON;+ACTIVEMONITORING)
- 200 0 0 0
2014-03-04 08:52:58 10.1.0.36 GET /owa/auth/logon.aspx replaceCurrent=1&url=https%3a%2f%2fEXCH2013%2fecp%2f&CorrelationID=<empty>;&cafeReqId=9ba2caf3-2a03-44a2-8477-2724689e139c; 443 - 10.1.0.36 Mozilla/4.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+MSEXCHMON;+ACTIVEMONITORING)
- 200 0 0 46
2014-03-04 08:52:58 10.1.0.36 GET /owa/auth/15.0.847/scripts/premium/flogon.js &CorrelationID=<empty>;&cafeReqId=62bb4655-3bfa-4e07-aa62-27c93e7e8b4d; 443 - 10.1.0.36 Mozilla/4.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+MSEXCHMON;+ACTIVEMONITORING)
- 200 0 0 0
2014-03-04 08:52:59 10.1.0.36 POST /owa/auth.owa &CorrelationID=<empty>;&cafeReqId=9d52ec1a-2ee1-4954-85e6-89e7e5df407a; 443 [email protected] 10.1.0.36 Mozilla/4.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+MSEXCHMON;+ACTIVEMONITORING)
- 302 0 0 812
2014-03-04 08:52:59 ::1 GET /OWA/Calendar/[email protected]/calendar/calendar.html &CorrelationID=<empty>;&cafeReqId=4ea66475-9a47-41a4-81cb-6b569715d0d6; 443 - ::1 AMProbe/Local/ClientAccess - 200 0 0 8859
2014-03-04 08:53:01 10.1.0.36 POST /owa/auth.owa &CorrelationID=<empty>;&cafeReqId=b3db7480-2192-436c-b01d-29d0e528cfec; 443 UseronEX2010 10.1.0.36 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+6.3;+WOW64;+Trident/7.0;+.NET4.0E;+.NET4.0C) https://OWA.company.com/owa/auth/logon.aspx?replaceCurrent=1&url=https%3a%2f%2fOWA.company.com%2fowa%2f
500 0 0 187
2014-03-04 08:53:04 127.0.0.1 GET /Microsoft-Server-ActiveSync/default.eas &CorrelationID=<empty>;&cafeReqId=2e2a655b-00b9-42ae-8789-1e452e6579c3; 443 [email protected] 127.0.0.1 AMProbe/Local/ClientAccess
- 200 0 0 8265
2014-03-04 08:53:14 10.1.0.36 GET /ecp/ &CorrelationID=<empty>;&cafeReqId=8741886f-b9b1-46f9-8c15-baf35809a12c; 443 [email protected] 10.1.0.36 Mozilla/4.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+MSEXCHMON;+ACTIVEMONITORING)
- 200 0 0 15265
2014-03-04 08:53:14 127.0.0.1 GET /OWA/auth.owa &CorrelationID=<empty>;&cafeReqId=8ad938fb-f2c3-42bf-8718-da62b122422c; 443 - 127.0.0.1 AMProbe/Local/ClientAccess - 302 0 0 15
HTTPERR LOG :
2014-03-04 08:51:48 10.1.0.36 13937 10.1.0.36 444 HTTP/1.1 RPC_IN_DATA /rpc/rpcproxy.dll?EXCH2013.companyNT.local:6001 400 2 BadRequest MSExchangeRpcProxyAppPool
2014-03-04 08:51:48 fe80::99d1:f542:a4d3:b469%12 13872 fe80::99d1:f542:a4d3:b469%12 444 HTTP/1.1 RPC_IN_DATA /rpc/rpcproxy.dll?EXCH2013.companyNT.local:6001 400 2 BadRequest MSExchangeRpcProxyAppPool
2014-03-04 08:52:25 10.1.0.36 13937 10.1.0.36 444 HTTP/1.1 RPC_IN_DATA /rpc/rpcproxy.dll?EXCH2013.companyNT.local:6001 400 2 Connection_Dropped MSExchangeRpcProxyAppPool
2014-03-04 08:52:25 fe80::99d1:f542:a4d3:b469%12 13872 fe80::99d1:f542:a4d3:b469%12 444 HTTP/1.1 RPC_IN_DATA /rpc/rpcproxy.dll?EXCH2013.companyNT.local:6001 400 2 Connection_Dropped MSExchangeRpcProxyAppPool
2014-03-04 08:52:30 127.0.0.1 14122 127.0.0.1 443 HTTP/1.1 GET /RPC/[email protected] 404 - NotFound -
2014-03-04 08:52:30 ::1%0 14121 ::1%0 443 HTTP/1.1 GET /ecp/ReportingWebService/ 404 - NotFound -
2014-03-04 08:54:42 ::1%0 14117 ::1%0 444 - - - - - Timer_ConnectionIdle -
2014-03-04 08:54:48 10.1.0.36 14211 10.1.0.36 444 HTTP/1.1 RPC_IN_DATA /rpc/rpcproxy.dll?EXCH2013.companyNT.local:6001 400 2 BadRequest MSExchangeRpcProxyAppPool
2014-03-04 08:54:48 fe80::99d1:f542:a4d3:b469%12 14285 fe80::99d1:f542:a4d3:b469%12 444 HTTP/1.1 RPC_IN_DATA /rpc/rpcproxy.dll?EXCH2013.companyNT.local:6001 400 2 BadRequest MSExchangeRpcProxyAppPool
2014-03-04 08:55:35 10.1.0.36 14211 10.1.0.36 444 HTTP/1.1 RPC_IN_DATA /rpc/rpcproxy.dll?EXCH2013.companyNT.local:6001 400 2 Connection_Dropped MSExchangeRpcProxyAppPool
2014-03-04 08:55:35 fe80::99d1:f542:a4d3:b469%12 14285 fe80::99d1:f542:a4d3:b469%12 444 HTTP/1.1 RPC_IN_DATA /rpc/rpcproxy.dll?EXCH2013.companyNT.local:6001 400 2 Connection_Dropped MSExchangeRpcProxyAppPool
Trace login, ok it is xml, so print is..
-Request Summary
Site
1
Process
8232
Failure Reason
STATUS_CODE
Trigger Status
500
Final Status
500
Time Taken
500 msec
Url
http://EXCH2013.companyNT.local:80/powershell?clientApplication=ActiveMonitor;PSVersion=4.0&sessionID=Version_15.0_(Build_846.0)=rJqNiZqNgZuQkpqT0pqH0ZuQkpqTkYvRk5CcnpOBzsbLzsbGyczJyIHPzNDPy9DNz87L38/Gxc/KxcrJ
App Pool
MSExchangePowerShellFrontEndAppPool
Authentication
Kerberos
User from token
companyNT\SM_9c071c4922fd420fb
Activity ID
{8000134C-0001-E300-B63F-84710C7967BB}
-Errors & Warnings
No.↓
Severity
Event
Module Name
157. view trace
Warning
-MODULE_SET_RESPONSE_ERROR_STATUS
ModuleName
ManagedPipelineHandler
Notification
EXECUTE_REQUEST_HANDLER
HttpStatus
500
HttpReason
Request Failed
HttpSubStatus
0
ErrorCode
The operation completed successfully.
(0x0)
ConfigExceptionInfo
ManagedPipelineHandler
See all events for the request

Exchange 2013 S/MIME with Server 2008 R2

Similar Messages

Maybe you are looking for