SCEP 2012 Exchange 2013 Exclusions

Hi, I am in need of assistance sorting out the exclusions for Exchange 2013 for SCEP. The problem is that SCEP seems to not like %ExchangeInstallPath%
littered all over the article https://technet.microsoft.com/en-us/library/bb332342(v=exchg.150).aspx
Checking on the exchange servers %ExchangeInstallPath% has a trailing slash (contrary to most other EV's like
%windir% %appdata% etc)
SCEP exclusions however must have a "\" in them otherwise they are not valid. This obviously leads to 2 slashes in the path when expanded out. Will the additional slash just be disregarded? I can obviously just type the full path myself but it
would be easiest to use the EV. Is this a bug?
Thanks

This certainly something to file on connect.microsoft.com or submit via your Microsoft support channels. The only thing I can think of as a way to work-around this is to create your own environment variables on the Exchange servers or use the actual path
with no variable. Neither is elegant necessarily, but I don't think you have much of a choice.
Jason | http://blog.configmgrftw.com | @jasonsandys

Similar Messages

How many CALs do i need? Server 2012 - Exchange 2013 - RDP

Hi,
(I apologize for the grammar and spelling mistakes, but im confident in the fact that the text is understandable. If not, please let me know. I have used UK English for spelling.)
I did some research and read the following:
(unable to post links, my email needs to be 'verified')
And some MS pages regarding the CALs for Windows 2008 R2 (don't ask why).
This is basically what i want to do:
OS:
Windows 2012 R2, possibly 2x because of the RDS role.
Roles Server1: Active Directory and Exchange 2013
Roles Server2: File server and RDS
Users:
20
PC’s:
Approx. 15. Not sure about the exact numbers, but i am sure that there are more users than client pc’s.
Users RDP:
Starting with 10 but eventually every user will be using RDP, so it might be also 20. The 10 we start with will not have the ability of logging into a client PC but RDP only.
MS Software:    Outlook 2010 or 2013, depends on the support by MS.
We are going to start with an AD with a home folder, roaming profiles and an email account. If everything go’s whell, we plan to start letting users connect tot heir workspace via RDP.
I came to the following conclusion and need your input on this:
20 User CALs, As far as i know, I need 1 user cal for an AD account and a RDP cal for
one RDP account. Without a User CAL, i cant issue a RDP user cal, is this correct?
20 RDP User CALs, does this mean that all my users can log into a RDS session via any client, even their own private pc?
No Device calls, redundant?
20 Exchange CALs, I am not sure about this one, the second link i found only mentions acces via web and mobile. I would also like to know if the Exchange CAL is per user or email. If it’s per user, then wat do i do with an email that is meant for multiple
users?
2 Server CALs, This is just buying 2012R2 isnt it? Does this also allow me to use one physically and the other as a VM in the physical one? Just asking, im not really going to use a VM.
Hope you guys can help me out on this one, i didn’t expect the CALs would bet his complicated.

Hi,
Under Per User licensing, you need a license for each unique human that will access the software. Based on what you have written above, below is a general description of the licenses you need:
20 Per User Windows Server CALs
20 Per User RDS CALs
20 Per User Exchange Standard CALs
1 Exchange Server 2013 Standard license
2 Windows Server 2012 R2 Standard licenses
Notes:
Each Server 2012 R2 Standard license allows you to install it on a physical server (up to 2 CPU sockets) with the Hyper-V role installed, and install it in 2 VMs. The key here from a licensing perspective is the installation on the physical server
is only being used for Hyper-V--if you use it for some other purpose (like AD, SQL, etc.) then you are only permitted to run 2012 R2 on 1 VM without an additional license. Running your servers as VMs is the common and recommended method now, unless
you have a specific reason not to.
I listed two 2012 R2 licenses above because from your description I get the idea that you will have 2 physical servers.
It is preferred to split key roles/functions onto separate VMs if possible. For example, it would be preferred to have Exchange on its own VM(s). This is obviously subject to your specific situation, budget, etc. In smaller environments
some roles will be combined in order to save money.
I did not include licenses for Office in the list above.
Yes, Per User licensing means the user can access the software from any device, even their own private pc.
I recommend you purchase licenses through a MS volume licensing program that fits your needs. Adding Software Assurance (SA) to your licenses will allow you to get the new versions when they are released as well as give some additional licensing rights.
As always, it is essential to read the Product Use Rights (PUR) document, licensing agreements, terms and conditions, etc., as applicable to your licenses.
I recommend you also take a look at the Office365 plans that include Office/Exchange/etc. There are Exchange-only plans as well. Depending on your needs it may be preferred to have your users access Exchange in the cloud and run RDS on premises.
Licensing Windows Server 2012 R2 Remote Desktop Services and Microsoft Desktop Applications for Use with RDS
http://www.microsoft.com/licensing/about-licensing/briefs/winserv2012-rds.aspx
Exchange Server 2013 licensing
http://products.office.com/en-us/exchange/microsoft-exchange-server-licensing-licensing-overview
-TP

AD/ Mailbox Restore Server 2012/Exchange 2013

So I went to Disable a user today in AD and accidentally Deleted him which killed his Mailbox. I'm trying to restore the user and the mailbox so I figured I'd start with the user:
Tried using the ADRestore tool and one scan found around 115 users. Anyone know how to restore 1 user using that tool? I looked at the AD Recycle Bin posts and I enabled that but nothing is showing up in that container.
Am I going down the right path? Need to restore the user first and then the Mailbox?
Edit: *** just did a rescan using adrestore and nothing is found. Am I hosed???
This topic first appeared in the Spiceworks Community

So I went to Disable a user today in AD and accidentally Deleted him which killed his Mailbox. I'm trying to restore the user and the mailbox so I figured I'd start with the user:
Tried using the ADRestore tool and one scan found around 115 users. Anyone know how to restore 1 user using that tool? I looked at the AD Recycle Bin posts and I enabled that but nothing is showing up in that container.
Am I going down the right path? Need to restore the user first and then the Mailbox?
Edit: *** just did a rescan using adrestore and nothing is found. Am I hosed???
This topic first appeared in the Spiceworks Community

SBS2008: Move email from Exchange 2007 to new server with Exchange 2013

We have an old server (SBS2008) and plan to buy a new server with (Server 2012). I need to move all the exchange emails, contacts & calendars to the new server. We will no longer use the old server.
Is there a document or migration tool that will help me understand how to move this data form the old exchange server to the new one?
Old Server:
SBS2008 running Exchange 2007
New Server:
Server 2012
Exchange 2013
Any help is appreciated!

Hi Dave,
It can be done, and as Larry suggested you will consider two Server 2012 installs in order to achieve an environment that looks like your current SBS roles; Exchange 2013 on an Active Directory controller isn't a good long-term solution (SBS did this for
you in the past).
For your size operation, a virtual server host, with a Windows Server 2012 license, and two virtual machines would probably be a suitable design model. In this manner, you have Server 2012 license that permits 1 +2 licenses (one host for virtualization,
up to 2 Virtual Machines on same host).
There's no migration tool. That comes with experience and usually trial and error. You earn the skills in this migration path, and for the average SBS support person you should plan on spending 3x (or more) your efforts estimate in hours planning your migration.
You can find a recommended migration path at this link to give you an idea of the steps, but its not exactly point by point going to cover you off for an sbs2008 to server 2012 w/exchange 2013 migration. But the high points are in here. If it looks
like something you would be comfortable with then you should research more.
http://blogs.technet.com/b/infratalks/archive/2012/09/07/transition-from-small-business-server-to-standard-windows-server.aspx
Specific around integrating Exchange 2013 into an Exchange 2007 environment, guidance for that can be found here:
http://technet.microsoft.com/en-us/library/jj898582(v=exchg.150).aspx
If that looks like something beyond your comfort level, then you might consider building a new 2012 server with Exchange 2013 environment out as new, manually export your exchange 2007 mailbox contents (to PST) and then import them into the new mail server,
and migrate your workstations out of old domain into new domain. Whether this is more or less work at your workstation count is dependent upon a lot of variables.
If you have more questions about the process, update the thread and we'll try to assist.
Hopefully this info answered your original question.
Cheers,
-Jason
Jason Miller B.Comm (Hons), MCSA, MCITP, Microsoft MVP

Exchange 2013 - The connection to Microsoft Exchange is unavailable

Hi there,
i have some problems on my new Exchange 2013 Server: Here is the topology:
1 serveur 2012 in workgroup with the Hyper-V role
2 VM: DC2012 is the DC of the domain: intra.mydomain.com, Windows 2012
The other VM is member of the domaine, Windows 2012, Exchange 2013 SP 1 installed.
So, i have dc2012.intra.mydomain.com and mail1.intra.mydomain.com (another DC: DC2008, name: dc2008.intra.mydomain.com)
I have some troubles with the SSL and the connexion of Outlook outside the LAN.
In the LAN on a client, i launch Outlook 2010 and the autodiscver make the rest. The connexion is ok.
But i have a client not in the LAN, so i configured a SSL. I made a request. First Question:
In the ECP, Server, Certificate, i have 3 times "Microsoft Exchange Server Auth Certificate" and 3 times "Microsoft Exchange" with differents dates. Why?
I installed my PKI on the DC2012, and paste the request and download the certificate. I retuned on the exchange server in ECP, Server, Certificate and treat the pending request. In Services i checked IMAP, POP, IIS, SMTP.
Then, in Server, Server, Mail1, OutlookAnywhere, in url extternal: mail.mydomain.com and Authentification: NTLM.
In ECP, Servers, Virtual Directories i wrote the same url external and internal: mail.mydomain.com for ECP, OWA, ActiveSync, OAB.
In my DNS on the DC, i created a CNAME record for mydomain.com et i created a A record for mail. on a client if i make nslookup then mail.mydomain.com the IP is the LAN IP of my exchange server.
I modified the MX record of my public domain: mail.mydomain.com to point on my Public IP. That works.
On the client outside of the LAN, i installed the root certificate and the exchange certificate.
second question:
Why my client outside of the LAN can't connext with outlook.
Thanks a lot for your answers and sorry for the long post.
Alex

I resolved my problem!
here is the solution that solved it:
actually, i tried to connect Outlook 2010 ti Exchange 2013. I knew that Exchange now connect Outllok via rpc over http(s), BUT, the Autodiscover (in LAN) transform the field server to something like that:
[email protected] , the xxx correspond to the GUID of the mailbox. So, for my remote user, i launch this command on Exchange 2013:
Get-Mailbox test | fl name, exchangeguid , it give to me the GUID, then in te field "Server" i fill ([email protected]): [email protected]
And in advanced parameters, same things i mentioned in previous post. And it works!!!!!
Thanks to me.

Issues with old calendar items after migration from SBS2008R1 to Windows 2012R2+Exchange 2013

Hello,
After migrating a customer from Windows Small Business Server 2008 R1 to Microsoft Windows Server 2012 (DC) and Microsoft Windows Server 2012 & Exchange 2013 there are a few issue regarding
the GAL and old migrated calender items that we are unable to resolve:
Old calender items which were Exported to PST when the Server 2008 R1 environment was still live were imported to the new mailbox of the user, located on the Exchange 2013 mail database. This
seemed to be working just fine.
The problems arise when a user tries to edit or re-send an old calender item. There actually are 2 problems:
1. When resending an old calender item, OLD GAL entries are used (even when re-entering the contact details) and the emails are send to nobody and you get the mail back from postmaster
2. When updating an old calender item you get an error that you do not have permissions, probably because you are NOT the 'old' Exchange user.
Thanks in advance!

Did you use Exmerge or similar to export?
You may have an issue like that explained here.
http://blogs.technet.com/b/sbs/archive/2009/05/21/cannot-reply-to-old-emails-or-modify-old-calendar-items-after-pst-mail-migration.aspx
Robert Pearman SBS MVP
itauthority.co.uk |
Title(Required)
Facebook |
Twitter |
Linked in |
Google+

Exchange 2013 OWA HTTP 500 error when opening another mailbox

We have an Windows Server 2012 Exchange 2013 server with OWA.
All users can login fine, but when I open another mailbox with my Admin account, having enabled access to that user's mailbox, the URL redirects to /owa/auth/errorfe.aspx?httpCode=500 and shows:
something went wrong
Sorry, we can't get that information right now. Please try again later. If the problem continues, contact your helpdesk
Google won't help me in this instance. Where in the eventlog are OWA events logged?

Hello,
I am joining to the thread opener, however, we do not use exchange server. we are using the Cloud services through Microsoft and as far as I know, the version is 2013 wave 15 (again, through Microsoft's cloud).
when I open the outlook, I can see the shared mailbox just fine.
when I open the office web access, and I search the mailbox through the 'add another mailbox..' It finds it however when I press the add button I get the HTTP 500 error.
when I tried to open a different mailbox (another shared mailbox I gave myself permissions for), it opens just fine.
it seems (from what I can tell) it is this specific shared mailbox that I cannot open through OWA while others I can.
when I try to open the mailbox in question through a different internet browser (Chrome) I get this Error:
NegotiateSecurityContext failed with for host 'db3pr04mb138.eurprd04.prod.outlook.com' with status'LogonDenied'
the error seems to be persistent on this specific mailbox only regardless to what browser I am trying to access with.
I can only assume that the solutions you (Winnie) offered isn't relevant in my case.
thanks in advance for any attempt to help me with this issue.

ConfigureMsgService fails with MAPI_E_NETWORK_ERROR (Exchange 2013)

Dear friends,
I've got a strange issue with Exchange server 2013. I am unable to configure profile with my own application.
The function ConfigureMsgService returns MAPI_E_NETWORK_ERROR (0x80040115).
The point of failure is this:
// Property structure to hold values we want to set.
#define PROPERTIES_NUM 5
SPropValue propValues[PROPERTIES_NUM];
memset(&propValues, 0, PROPERTIES_NUM * sizeof(SPropValue));
// PR_ROH_FLAGS
propValues[0].ulPropTag = PR_ROH_FLAGS;
propValues[0].Value.l = ROHFLAGS_USE_ROH |
  ROHFLAGS_HTTP_FIRST_ON_SLOW |
  ROHFLAGS_HTTP_FIRST_ON_FAST;
// PR_ROH_PROXY_AUTH_SCHEME
propValues[1].ulPropTag = PR_ROH_PROXY_AUTH_SCHEME;
propValues[1].Value.l = ROHAUTH_NTLM;
// PR_ROH_PROXY_SERVER
propValues[2].ulPropTag = PR_ROH_PROXY_SERVER;
propValues[2].Value.lpszW = (LPWSTR) wszRohProxyServer;
// Server
propValues[3].ulPropTag = PR_PROFILE_UNRESOLVED_SERVER;
propValues[3].Value.lpszA = (LPSTR) szServer;
// Email
propValues[4].ulPropTag = PR_PROFILE_UNRESOLVED_NAME;
propValues[4].Value.lpszA = (LPSTR) szEmailAddress;
// Configure the message service with the properties above.
hr = spMsgSvcAdmin->ConfigureMsgService(
(LPMAPIUID) pRow->aRow->lpProps[iSvcUID].Value.bin.lpb,
NULL, 0/*SERVICE_UI_ALLOWED*/, PROPERTIES_NUM, propValues );
This works well if SERVICE_UI_ALLOWED flag is used but fails with MAPI_E_NETWORK_ERROR
if "MSEMS" service is configured without configuration property sheet.
The code above also works if Exchange server is installed at the computer that also works as domain controller. But the problem occurrs if domain controller and exchange server are separate machines.
Enviroment:
Domain controller: Windows Server 2012
Exchange server: Windows Server 2012, Exchange 2013
Client machine: Outlook 2013 installed
I'm guessing that there is some issue with AD, but I've run out of ideas at this point.
Many thanks in advance for any suggestions.
tomas

Hi tomas,
I am also facing the same problem, my customized MAPI application is failing with MAPI_E_NETWORK_ERROR
(Exchange 2013).
The exchange server and the AD are on different boxes.
I tried following the
steps as suggested in the article but no effect.
Can you tell me what registry value do I need to set and in which machine do I need to set it.
I do not see the HKEY_CURRENT_USER\Software\Microsoft\Exchange\Exchange Provider in the registry.
Ankush

On Windows 2012 Terminal Server Outlook fails to connect to Exchange 2013

I have a new install of Windows 2012.  I have two physical servers. One is a W2012 std Domain Controller ("DC"). The Second is configured as W2012 HyperV  ("HV"). Under HV I have
two VMs. One VM is W2012/Exchange 2013 ("ExchVM) and the other is W2012/Terminal Server ("VMTS"). All systems are behind a firewall appliance. Exchange is working via Outlook and OWA internally and externally. The self
created SSL must be installed manually on external machines since it comes up as an untrusted certificate. Once installed remote outlook works and OWA works. I have configured the terminal server and I am able
to login remotely as various users under my "TS group". The problem is when ever I attempt to open Outlook for the 1st time, it fails to connect to the exchange server.   (Open Outlook 2013, click next
on the splash screen, "Yes" Add an Email Account splash screen, click next, Auto Account screen populates NAME and Email Address correctly, click next, Searching for mail server settings..., check on establishing network connection, check on searching
for alias@ domain, then fails the logging on to the mail server) The error reads: "Outlook cannot log on. Verify you are connected to the network and are using the proper server and mailbox name. The
connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action."   I am connected in RDS from offsite, and from the RD session I can access shared folders on ExchVM and DC. I have
tried have verified the server Exchange server name is correct via "Get=ClientAccessServer" command. I have also tried to use the guid via "Get-Mailbox
ALIAS | fl name, exchangeguid. Keep in mind all desktop users on the network are connecting to Outlook without issue.
I would appreciate any thoughts on solving this issue.

Hi,
According to your workaround, it seems that the Outlook Anywhere configuration in Outlook client is not correct when using the Autodiscover service.
Once you connected to Exchange server by manually settings, please run Test E-mail AutoConfiguration tool in external Outlook client to check the autodiscover service:
open Outlook - press CTRL key - right click on the Outlook icon from right bottom corner taskbar - Test Email AutoConfiguration. Put your email address - uncheck use guessmart and secure guessmart authentication - click Test to check your Autodiscover service.
Please check the Log tab and confirm whether the Autodiscover service is connected successfully. Also confirm if the connection issue happens to all external users when they open Outlook for the 1st time. In Exchange server, please make sure
autodiscover.domain.com has been included in your Exchange certificate which is assigned with IIS service.
Regards,
Winnie Liang
TechNet Community Support

Installing Exchange 2013 on Windows Server 2012 R2

Now that SP1 has been released, it is supported to run Exchange 2013 on Windows Server 2012 R2
But since it is not yet possible to download Exchange 2013 with integrated SP1 (slipstreamed), is the following installation procedure supported:
- Install Exchange 2013 (without SP1) on Windows Server 2012 R2
- Install SP1 on top of Exchange 2013
If this is not supported, can someone tell me when the Exchange 2013 with integrated SP1 (slipstreamed) download will be released?

yes the SP1 is the full product. if you need step by step instruction to migrate to this new version you can get info here : http://buenoflex.com/install-exchange-2013-sp1/
Arnaud Buonaccorsi - GSX Groupware Solutions
http://www.buenoflex.com
http://www.gsx.com <= The monitoring solution for Exchange and Sharepoint

Can't get OWA to work on Essentials 2012 R2 with Exchange 2013 on second server 2012 R2 std.

I have previously with success setup a working solution with server 2012 essentials, and a second server 2012 std. with exchange 2013, I did it following this guide: http://technet.microsoft.com/en-us/library/jj200172.aspx
Unfortunately I lost the server due to a cooling error which led to an un-repairable essentials 2012, since this was a new setup and also a test setup I didn't have any working backup solution setup at the time...tsk.tsk.
Since I had to make a complete do over I chose to try out the new R2 server editions, and set it up following the same guide, when it came to this part:
Download KB2732764 for ARR 2.5, and then install the update on the server that is running Windows Server 2012 Essentials.
Copy the SSL certificate file for Exchange Server to the server that is running Windows Server 2012 Essentials. The certificate file must contain the private key, and it must be in the PFX file format.
Note
If you are using a self-issued certificate, follow the instruction in the Exchange Server article Export an Exchange Certificate to export the certificate.
Open a command window as an administrator, and then open the %ProgramFiles%\Windows Server\Bin directory.
Based on you installation scenario, follow one of these steps to configure ARR:
If you are performing a clean setup, run the following command:
ARRConfig config –cert “path to the certificate file” –hostnames “host names for Exchange Server”
I noticed that the version of "Application request routing" had changed to version 3, so obviously I didn't need to dl the 2.5 update.. When I came to the part where I wa instructed to run arrconfig config etc. I noticed
that the ARRconfig file no longer where placed where the setup guide indicated, I then went ahead and tried som manual configuration regarding certificates and such. In the end I have a working solution where Exchange and OWA is working locally but OWA isn't
working outside my local domain, the link get's placed in the RWA and is indicating the correct link for the exchange server www.remote.clinten.dk I have a certificate which include to separate domain names aforementioned and remote.clinten.dk and
I get no errors indicating certificate errors, when I try to connect to www.remote.clinten.dk/owa from outside I get a 404 error, and when I connect to www.remote.clinten.dk I get the RWA login screen for the essentials RWA. Obviously I need to set up something
in ISS probably in the url rewrite section, but I can't seem to find the right setting.. Can someone help with this?
Btw. I have found the missing arrconfig file in c:\windows\system32\essentials" and tried to run the command as described in the guide "ARRConfig config –cert “path to the certificate file” –hostnames “host
names for Exchange Server”" but it doesn't seem to work, it just prompts with a guide for using the arrconfig command and examples of correct use, I also tried removing the "" from the guide, like this "ARRConfig
config –cert path to the certificate file –hostnames host names for Exchange Server",
when I ran it without the "" It didn't prompt me with anything nor did It indicate any errors, it did not however make my OWA work either..
I am aware that exchange 2013 atm. isn't officially supported on the R2 server, but the exchange works fine inside my domain, and the pop3/smtp also works from outside, since this Is a test environment, using only my own private domain and not a company
domain I figured it would be ok to run the risk.. ;)

Hi
found this on
https://social.technet.microsoft.com/Forums/en-US/1f099068-b3ed-44f3-a8c4-c22d760a8621/arr-broken-or-bad-syntax-exchange-2013-essentials-2012-r2?forum=winserveressentials
"Ok just an update for anyone else how has this issue.
The problem has been solved by Microsoft and I have included their findings below, but basically it comes down to a typo!
I often use notepad to have all the commands I need on hand, and I must have copied the command direct from the TechNet article or other website and customised the required fields. The issue with this is one of the characters did not “convert” - for want
of a better word. I should have retyped the whole command from scratch and it would have been right!
Thanks for everyone’s input and for Microsoft for getting to the bottom of it.
From Microsoft:
We have tested on your environment and here is the investigation result from our senior engineer:
================================================================
Basically the command fails due to invalid parameter, the invalid one is the ‘-‘. I think the one customer used is copied from the online document sample which translate to the unicode is 0x8211 means “en dash”, it
can’t be input by normal keyboard, so I pretty sure it is from web (mostly HTML document).
The one we check (compare) is ‘-‘ which has the code 0x45.
So it always failed to compare the parameter and ARRconfig.exe thought it is invalid parameter.
The solution is quite simple, just using keyboard to retype the command, using normal ‘-‘ and I have tried the password prompt shows
Best Regards,
Johnny Chen
Microsoft Partner Support Community Technical Support Engineer
Microsoft Global Partner Services"

Getting Error while installing Exchange 2013 on server 2012

Error During Exchange 2013 Mailbox Transport
Role Install On Server 2012
Exchange
Server forums
>
Exchange
Server 2013 - Setup, Deployment, Updates, and Migration
Question
1
Sign
in to vote
I was installing Exchange 2013 on Server 2012. The server is not a DC, but is a member of a domain with a 2008 R2 functional level, and I was logged in as a domain admin. There has never been an Exchange instance on this domain. I got past
the prerequisite checks, and the installer showed 15 steps, so I walked away. When I came back, I saw this:
Step 8 of 15: Mailbox role: Transport service
Error:
The following error was generated when "$error.Clear();
          $maxWait = New-TimeSpan -Minutes 8
          $timeout = Get-Date;
          $timeout = $timeout.Add($maxWait);
          $currTime = Get-Date;
          $successfullySetConfigDC = $false;
          while($currTime -le $timeout)
            $setSharedCDCErrors = @();
            try
              Set-SharedConfigDC -DomainController $RoleDomainController -ErrorVariable setSharedCDCErrors -ErrorAction SilentlyContinue;
              $successfullySetConfigDC = ($setSharedCDCErrors.Count -eq 0);
              if($successfullySetConfigDC)
                break;
              Write-ExchangeSetupLog -Info ("An error ocurred while setting shared config DC. Error: " + $setSharedCDCErrors[0]);
            catch
              Write-ExchangeSetupLog -Info ("An exception ocurred while setting shared config DC. Exception: " + $_.Exception.Message);
            Write-ExchangeSetupLog -Info ("Waiting 30 seconds before attempting again.");
            Start-Sleep -Seconds 30;
            $currTime = Get-Date;
          if( -not $successfullySetConfigDC)
            Write-ExchangeSetupLog -Error "Unable to set shared config DC.";
        " was run: "Unable to set shared config DC.".

Hi Deepak,
From the error description, I would like to clarify the following things:
1. Please ensure that IPv6 on the network adaptor is turned on.
2. Please check if the account that you used to install Exchange has necessary permissions to perform the installation.
3. Make sure that DNS is configured correctly.
Hope my clarification is helpful.
If there are any problems, please feel free to let me know.
Best regards,
Amy
Amy Wang
TechNet Community Support

Upgrade of Integation Services (Windows 2012 R2) on Windows 2008 R2 with Exchange 2013 SP1 DAG fails

Here is the scenario:
Legacy Host: Windows 2008 R2
Guest VM: Windows 2008 R2 with Exchange 2013 SP1 DAG cluster.
After importing the VM (2008 R2 and Exchange 2013 DAG) into a 2012 R2 host (Cluster). (copy VM files to new 2012 R2host) Everything works fine.
Then upgrading "Installation Services" (for Windows 2012 R2 host) on the imported VM runs fine with no errors to the "Restart" prompt. VM than shows: "Configuring Windows updates 32% complete. Do not turn
of your computer." Hangs there for about 20 minutes until is says "shutting down". Hangs there for 20 minutes until power off. Restart to normal start; "Preparing to configure Windows. Do not turnoff your computer." proceeds slowly
to "Configuring Windows updates 32% complete. Do not turn of your computer." hangs there again indefinite. Sometime hangs at shutdown cycle and "Configuring Windows updates 32% complete. Do not turn of your computer." indefinitely.
I moved 20 other machines from a 2008 R2 host to new Windows 2012 R2 hosts all of these machines install the 2012 R2 Integration services just fine on the 2008 R2 VM. Just the 2008 R2 VMs clustered (DAG) and Exchange 2013 SP1 do not take the Integration
Services upgrade.
Any advise from Microsoft? I know I could decommission the DAG and Exchange machines and install Integration services on the native box before Exchange and DAG and that would sure work, but I'd rather avoid that amount of work for a simple integration layer
upgrade.
Thanks
Gerhard Waterkamp ACSLA Inc.

Hi,
Could you try use the following method to fix this issue first?
1. Run the System Update Readiness Tool, then check if there is any error in the Checksur.log and checksur.persist.log.
1. Please run the System Update Readiness Tool on this affected server. Please download this tool from the following Microsoft article:
Description of the System Update Readiness Tool for Windows Vista, for Windows Server 2008, and for Windows 7
http://support.microsoft.com/kb/947821/en-us
2. The System Update Readiness Tool creates the log files that captures any issues that the tool found or fixed. The log files are located at the following location:
%SYSTEMROOT%\Logs\CBS\
3. Please paste the checksur.log here for analysis.
If there is no error found, please try the following step.
==================================
2. Use Fix it tool to reset the Windows Update components.
1. Open the following link.
http://support.microsoft.com/kb/971058/en-nz
2. Select Windows 8.1, Windows 8 and Windows 7 in the product selection box.
3. Click “Run Now” to reset the Windows Update components.
Note: We can reset the Windows Updates manually by following the steps in the KB above.
3. Use the System File Checker tool to repair missing or corrupted system files
1. Open the command promote with Administrators.
2. At the command prompt, type the following command, and then press ENTER:
sfc /scannow
Any errors are found in the steps above, please let me know.
Hope this helpful.
Best Regards,
Jason Zeng
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Setup Error 1603 with Exchange 2013 incl. SP1 on Windows Server 2012 R2

Hello all,
i've started the installation of a new Exchange 2013 with SP1 in a Windows 2012 R2 environment. New AD, no Exchange previously installed. Exchange ISO from
Volume Licensing Service Center (Filename: SW_DVD9_Exchange_Svr_2013w_SP1_MultiLang_Std_Ent_MLF_X19-35118.iso)
All the prerequisites are ok, installed also the “Unified Communications Managed API (UCMA) 4.0″ as requested.
Setup.exe i've started with "run as administrator" and all went well, until Step 11 of 15 (Mailbox role:Mailbox service).
Setup stopped and gives an error:
The following error was generated when "$error.Clear();
Install-MsiPackage `
-PackagePath ([System.IO.Path]::Combine($RoleLanguagePacksPath, "Setup\ServerRoles\UnifiedMessaging\MSSpeech_SR_TELE.nb-NO.msi")) `
-PropertyValues ("ARPSYSTEMCOMPONENT=1 ALLUSERS=1") `
-LogFile ([System.IO.Path]::Combine($RoleSetupLoggingPath, "InstallSpeech-nb-NO.msilog"))
" was run: "Installing product F:\Setup\ServerRoles\UnifiedMessaging\MSSpeech_SR_TELE.nb-NO.msi failed. Fatal error during installation. Error code is 1603. Last error reported by the MSI package is 'The cabinet file 'EngineInstanceData.cab'
required for this installation is corrupt and cannot be used. This could indicate a network error, an error reading from the CD-ROM, or a problem with this package.'.".
Exchange ECP is not working (HTTP Error 404.0 - Not Found), EMS (Shell) is working - if i try a get-mailboxserver it gives me the correct servername.
Exchange Services are running:
Running MSExchangeADTop... Microsoft Exchange Active Directory...
Running MSExchangeAntis... Microsoft Exchange Anti-spam Update
Running MSExchangeDelivery Microsoft Exchange Mailbox Transpor...
Running MSExchangeDiagn... Microsoft Exchange Diagnostics
Running MSExchangeEdgeSync Microsoft Exchange EdgeSync
Running MSExchangeHM Microsoft Exchange Health Manager
Stopped MSExchangeIMAP4BE Microsoft Exchange IMAP4 Backend
Running MSExchangeIS Microsoft Exchange Information Store
Running MSExchangeMailb... Microsoft Exchange Mailbox Replication
Running MSExchangeMigra... Microsoft Exchange Migration Workflow
Stopped MSExchangePOP3BE Microsoft Exchange POP3 Backend
Running MSExchangeRPC Microsoft Exchange RPC Client Access
Running MSExchangeServi... Microsoft Exchange Service Host
Running MSExchangeSubmi... Microsoft Exchange Mailbox Transpor...
Running MSExchangeTrans... Microsoft Exchange Transport
Running MSExchangeTrans... Microsoft Exchange Transport Log Se...
Running MSExchangeUM Microsoft Exchange Unified Messaging
So, how to proceed ? Try to download a new ISO for Exchange 2013 incl. SP1 and run the setup again ?
What happens to the existing (corrupt) installation of the exchange which is not working ?
Thanks for your help
Bruno

Hi,
From the error message, the cabinet file 'EngineInstanceData.cab' required for this installation is corrupt and cannot be used. I'm afraid you have to download a new ISO for Exchange 2013 incl. SP1 and run the setup again.
If it still doesn't work, I recommend you remove the failed Exchange server installation, then re-install Exchange server.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Exchange 2013 SP1 and SCOM 2012 R2

Hi there,
Hopefully someone can assist me with this issue, if it is one...
I am halfway through an Exchange migration, from Exchange 2010 SP3 on Server 2008 R2 to Exchange 2013 SP1 on Server 2012 R2.
76 users in total, roughly 80GB of Public Folders.
I have configured the 2013 environment with a cross datacenter DAG, also increased all of the timeouts of the cluster to take this into consideration, and everything appears to function as expected.
Added both 2013 machines to SCOM 2012 R2 for at least a week with no active users on it, and all monitoring reported ok, no issues.
Exchange 2010 is configured to use webmail.company.com for RPC over HTTP, which is what I have configured 2013 to use as well.
Implemented Microsoft ARR for client access to Exchange 2013, as opposed to ISA we've used for Exchange 2010.
A week ago, changed the DNS records for webmail.company.com from ISA to ARR, and all clients connected perfect.
Thought, ok, now we can start the migration. So far everything "seems" to be going perfect with the mailbox moves, however, SCOM is really noisy.
Attempted to reran the probe for EWS and got the error below:
Is there perhaps anyone that can assist me with these errors?
Cheers

FYI... IIS ARR is not supported for Exchange Server.
Check in event log if you are getting anything related to the issue.
About Outlook POP UP to end users. Check the event log on 2010/2013 for MRS events.
Are those mailboxes still moving or in move request?
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

SCEP 2012 Exchange 2013 Exclusions

Similar Messages

Maybe you are looking for