Exchange server and and antispam

Dear All,
I have exchange 2010, and forefront proctection 2010 for exchange server. But i dont see many option for antispam. I would like all spam emails goes to separate folder and they are not downloaded to outlook and user can view them by logiinng into owa. But
i dont see this option. 
i cannot see any option where user should be freely able to to blacklist or white list for his own user mailbox.
Am i have selected right product or i have to install different antispam that have rich of feature. 

Hi,
you can configure that spam emails are put into quarantine in FPE. But only the Administrator has access to it. There is no way that a user can access it.
FPE interacts with the junk E-Mail filter of Outlook. If a user put an E-Mail address or domain into the blocked senders this information will be used by FPE to block specific e-mails.
Greetings
Christian
Christian Groebner MVP Forefront

Similar Messages

  • Microsoft Exchange Server 2003 and Windows 8 Compatibility

    Is there a fix or workaround for accessing email via Outlook 2013 (Windows 8) when your company uses Microsoft exchange server 2003 and has not plans on upgrading it any time soon. I am a remote employee so I am the only one that has this problem in the
    company. I can access email through an owa account but it's a pain. I tried to set up a rule to have all incoming mail forwarded to my gmail account in Outlook 2013, but that did not work. Any other ideas?

    If server has enabled ActiveSync you can use Windows 8 Mail Client - works almost like Outlook.
    AFAIR Outlook 2013 can't work with Exchange 2003.
    Regards, Konrad Sagala, MCT, MCSE+M, MCITP: Exchange 2007/2010, Lync 2010, Office365, Windows 2008, Virtualization

  • Exchange Server 2010 and Iphone Version 4s or 5S, HTML Rendering on Iphone

    We have Exchange Server 2010 and using Iphone to receive and Send emails,
    When HTML based emails are opened from Iphone, The email just shows the text and not the HTML
    So the HTML is not rendered on IPhone, if the same email is FORWARDED from Outlook and opened on Iphone HTML is rendered correctly.

    You either restart or reset your phone and the issue should resolve.

  • Our exchange server crashed and we lost all contact and calendar data.  We found an app to get the contacts off of people's phone to import but can't find the same for calendar.  How do I get my calendar info off my phone and in to new exchange server?

    Our exchange server crashed and we lost all contact and calendar data.  We found an app to get the contacts off of people's phone to import but can't find the same for calendar.  How do I get my calendar info off my phone and in to new exchange server?

    You'd have to think through this, but it seems like if you are using Outlook, and the items vanished from the Outlook client as well as the server,that you could re-populate Outlook using iTunes. 

  • Exchange Server 2013 and Remote Access VPN on a single server running Windows Server 2012?

    Just by way of background, I have been installing and administering network servers, e-mail systems, VPN servers, and the like for many years.  However, my involvement with Exchange and Windows Server has been mostly on the forensics and data recovery
    level, or as a (sophisticated) user.  I have never tried to deploy either from scratch before.  My deployment experiences have been mostly with Linux in recent years, and with small private or personal "servers" running such cutting edge
    software as Windows XP back when it was new.  And even NetWare once.
    When a client asked me if I could set up a server for his business, running Exchange Server (since they really want Outlook with all of its bells and whistles to work, particularly calendars) and providing VPN access for a shared file store, I figured it
    could not be too difficult given that its a small business, with only a few users, and nothing sophisticated in the way of requirements.  For reasons that don't bear explaining here, he was not willing to use a vendor hosting Exchange services or cloud
    storage.  There is no internal network behind the server; it is intended to be a stand-alone server, hanging off a static IP address on the Internet, providing the entirely mobile work-force of about 10 people with Exchange-hosted e-mail for their computers
    and phones, a secure file store, and not much else.  If Exchange didn't need it, I would not need to install Active Directory, for example.  We have no direct need for its services.
    So I did the research and it appears, more by implication than outright assertion, that I should be able to run Windows Server 2012 with Exchange Server 2013 on a server that also hosts Remote Access (VPN only) and does nothing else.  And it appears
    I ought to be able to do it without virtualizing any of it.  However, I have spent the last three or four days fighting one mysterious issue after another.  I had Remote Access VPN working and fairly stable very quickly (although it takes a very
    long time to become available after the server boots), and it has mostly remained reliable throughout although at times while installing Exchange it seems to have dropped out on me.  But I've always been able to get it back after scrounging through the
    logs to find out what is bothering it.  I have occasionally, for a few minutes at a time, had Exchange Server willing to do everything it should do (although not always everything at the same time).  At one point I even received a number of e-mails
    on my BlackBerry that had been sent to my test account on the Exchange Server, and was able to send an e-mail from my BlackBerry to an outside account.
    But then Exchange Server just stopped.  There are messages stuck in the queues, among other issues, but the Exchange Administration Center refuses now to display anything (after I enter my Administrator password, I just get a blank screen, whether on
    the server or remotely).
    So, I am trying to avoid bothering all of you any more than I have to, but let me just begin with the basic question posed in the title: Can I run Exchange Server (and therefore Active Directory and all of its components) and Remote Access (VPN only) on
    a single Windows Server 2012 server?  And if so, do I have to run virtual machines (which will require adding more memory to the server, since I did not plan for it when I purchased it)?  If it can be done, can anyone provide any pointers on what
    the pitfalls are that may be causing my problems?  I am happy to provide whatever additional information anyone might like to help figure it out.
    Thanks!

    An old thread but I ran into this issue and thought I share my solution since I ran into the same issue. Configuring VPN removes the HTTPS 443 binding on the Default Site in IIS for some strange reason; just go and editing the bindings, add HTTPS and things
    should be back to normal.

  • A problem with Win 7 Pro, Outlook Web Access based on Exchange Server 2003, and two different domains

    Dear Microsoft Support,
    As mentioned in the title,
    I have two domains. One is Domain A at HQ. The other one is Domain A at branch office. A laptop having Win 7 Pro OS is a client of Domain A. The Domain A has Exchange Server 2003. Users of Domain B get connected to Exchange Server for email services. In
    all clients of the Domain B, IP address of the email server added in C:\Windows\System 32\drivers\etc\host file.
    Whereas in the clients of Domain A it was not done, because all the servers including the email server belong to the Domain A.
    Now, a user with Domain A's client (it is a laptop) came to Branch office and wanted to access the Outlook (using Outlook Web Access). since there is no IP address added in the Host file of the laptop, connectivity to email is not possible. When I try to
    add the IP address, I was not able to do so due to Domain A's security reasons.
    So, let me know, is there a way out to add the IP address in the host file of the Domain A's client.
    Thanks in advance.
    Ravi Sekhar Modukuru

    I would suggest adding the mailserver address in Domain B's DNS. Would that be possible?
    I agree. The correct solution in this case (since it appears you already have a two-way Domain Trust in place) is to properly configure DNS in Domain 'B' to be a secondary of Domain 'A' and completely eliminate the need to maintain the HOSTS file.
    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

  • Exchange Server 2013 and RADIUS server(freeRADIUS2)

    I am a student and doing an internship. I have to test Microsoft Exchange Server 2013.
    I am using Windows Server 2012, I already installed Exchange
    Server 2013 on it and everything works as intended.
    But I couldn't find out how to configure my Windows Server 2012 in order to authenticate my mailbox users from Exchange Server 2013 with a RADIUS
    server which is not on my Windows Server 2012. I have to use their RADIUS server ( freeRADIUS2 ), the RADIUS server from
    the company where I am doing my internship.
    I already did the checklist that is on http://technet.microsoft.com/en-us/library/cc772591.aspx. I configured the NPS as
    a RADIUS proxy, because that's what I need.
    So after doing everything that is on that checklist, my question is:
    Is it possible that the Exchange Server 2013 will use my NPS which is now configured as a NPS RADIUS proxy to authenticate my mailbox users that I have on my Exchange Server 2013?

    thanks for such a quick response.
    Just a small question about the link that you put. Does member server mean other server other than domain controller?
    Regards,
    Yes, Also the server on which you are installing Exchange should have exchange installed.
    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.

  • Exchange Server 2013 and ms-Exch-SMTP-Accept-Authoritative-Domain-Sender

    Hello, Team!
    I think I’ve found a serious issue in last CU releases. This is the case:
    1 Multirole server Exchange 2013 SP1 (and older) , one creceive connector from internet to this server, no edge, nothing.
    I care about preventing spoofing my company’s email addresses, and remove remove the ms-Exch-SMTP-Accept-Authoritative-Domain-Sender transport permission from anonymous senders.
    To do this, we usually simple run powershell command
    Remove-ADPermission <ReceiveConnector Name> –user “NT AUTHORITY\Anonymous Logon” –ExtendedRights ms-Exch-SMTP-Accept-Authoritative-Domain-Sender
    This command works on Exchange SP1, the client (telnet session, f.e.) which try spoof address of company will be refused. (see screenshot below)
    But in Exchange 2013 CU5, CU6 and even CU7 release this revoke permissions DOESN’T WORKS without any errors, softly. I've try Powershell and ADSI but
    unsuccessfully.
    Then we take off permission on connector above,
    we keep 3 default permissions:
    Accept-any-sender
    Accept-Routing-Headers
    Submit-Message to Server
    It is wonderful works only on server SP1, but not on servers with older versions, which have right settings.
    The saddest thing is I have information about Office 365 this behavior reproduced too. And I also think what in your lab you could take 15 minutes and play this simply thing....
    I found only that information on connector side is diffenent on SP1 and CU5,6,7.
    This is normal connection on SP1, when somebody try spoofed address. We can see a 250 AUTH Response on server side, and server refuse fake connection, all right.
    And on CU5 and newest versions we doesnt see this code. Maybe auth mechanism miss something?
    Any suggestions? On MS connect site a didn't found exchange bugs topic :)

    Hi Dmitriy,
    Thanks for your update.
    Then how about the receive connector configuration? Are they using the same authentication settings?
    Thanks.
    I would like to clarify the situation a little
    for you.
    I carried out a large migration project environment from EX2010 to 2013.
    When I support this environment for 2013 more than two years.
    And setting worked well in 2010,CU1,CU2,CU3,and finally in
    SP1 over from my upgrades.
    Understand that it does not work in versions of
    the above, and I'd really like
    to know why.
    I repeat that I would like to know
    in the first place, why it
    does not work anymore?
    Why it is not documented?
    As You can see, if you approach with the existing
    and available information on the problem, not
    you will immediately understand that there are serious problems
    caused serious changes.
    I want to attract the attention of the  Exchange team  and other peoples
    to the problem and find out why
    this is happening.
     

  • Writing client app to connect to Exchange Server 2013 and set OOF for users on vacation

    I am coding an C# app that should connect to Exchange Server 2013 on-premise (Servers Location is not in our Company). I`ve got an account (User and Pass) with readonly admin-rights for now and want to read and set OutOfOffice Objects for other users. I
    decide to use EWS Managed API over Autodiscovery but I am bit confuse how
    I tried to connect with "service.UseDefaultCredentials = true" and read contacts -> this code works:
    try
                ExchangeService _service
    = new ExchangeService(ExchangeVersion.Exchange2013_SP1);
                _service.Credentials
    = new WebCredentials("service.exchange",
    "1234", "domain");
                _service.TraceEnabled
    = true;
                _service.TraceFlags
    = TraceFlags.All; _service.UseDefaultCredentials
    = true;
                _service.AutodiscoverUrl("[email protected]",
    RedirectionUrlValidationCallback);
                foreach
    (Contact contact in _service.FindItems(WellKnownFolderName.Contacts,
    new ItemView(2)))
    var test = contact;
            catch
    (Exception exception)
                Console.WriteLine(exception);
    After that I tried the same with _service.UseDefaultCredentials = false; got error -> "The Autodiscover service couldn't be located." I am not shure if this "direct log on" is the right way, On msdn I've read about "delegate access"
    and "Impersonation" (NTLM and Basic Authentication) I'am a bit confused. Can anybody help me?

    hi,
    when you set a credential, you don't have to set the UseDefaultCredentials property (it is already updated).
    For autodiscover, you should try to set the property EnableScpLookup to True if you are in the Exchange domain or it is known by the current domain.
    Autodiscover uses a domain query (through Active Directory) and/or a dns query (this requires a DNS register for autodiscover.domain.net) to determine the access to the autodiscover service URI.
    Regards,
    Désiré GOVIN Refresh IT Solutions

  • Exchange Server 2013 and Office 365 Integration

    If we are using Exchange Server 2013 on premise, can we have 2 of our users integrated with Office 365 so that they can utilize their Exchange Server email account with the apps and features of Office 365?

    Hi,
    You can deploy a hybrid environment using Exchange 2013 CU2 or later version with Office 365.
    Could you please tell me what do you mean by "we have 2 of our users integrated with Office 365 so that they can utilize their Exchange Server email account with the apps and features of Office 365"?
    Here is my understanding: You create these two mailboxes on Exchange 2013, but you need to allow for redirection from the on-premises OWA environment to the Office 365 OWA. If that is your case, you need to specify a target URL for your organization(for
    example, www.outlook.com/contoso.com). If I have misunderstood your concern, please let me know.
    For more information, here is an article for your reference.
    Plan an Exchange Online hybrid deployment in Office 365
    http://technet.microsoft.com/en-us/library/hh852414.aspx
    Hope it helps.
    Best regards,
    Amy Wang
    TechNet Community Support

  • Trying to install Exchange Server 2013 and receive this error.

    Hello,
    I have a computer running Windows Server 2012 R2 Standard. I have completed all the prerequisites to install Exchange Server 2013. It all was going good until the install started. Then I received the below error. Does anyone have any suggestions? I am new
    to Exchange Server so would thank and appreciate any help I could get to resolve this issue.
    Thank You,
    Stan
    Error:
    The following error was generated when "$error.Clear(); 
    initialize-ExchangeUniversalGroups -DomainController $RoleDomainController -ActiveDirectorySplitPermissions $RoleActiveDirectorySplitPermissions
    " was run: "Microsoft.Exchange.Management.Tasks.InvalidWKObjectException: The well-known object entry B:32:A7D2016C83F003458132789EEB127B84:CN=Exchange Servers\0ADEL:16cd035a-6201-492f-b85f-1e28cc9f9ee0,CN=Deleted Objects,DC=MULTIAXCNC,DC=local on
    the otherWellKnownObjects attribute in the container object CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=MULTIAXCNC,DC=local points to an invalid DN or a deleted object.  Remove the entry, and then rerun the task.
       at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
       at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
       at Microsoft.Exchange.Management.Tasks.InitializeExchangeUniversalGroups.CreateGroup(ADOrganizationalUnit usgContainer, String groupName, Int32 groupId, Guid wkGuid, String groupDescription, GroupTypeFlags groupType, Boolean createAsRoleGroup)
       at Microsoft.Exchange.Management.Tasks.InitializeExchangeUniversalGroups.CreateGroup(ADOrganizationalUnit usgContainer, String groupName, Int32 groupId, Guid wkGuid, String groupDescription)
       at Microsoft.Exchange.Management.Tasks.InitializeExchangeUniversalGroups.InternalProcessRecord()
       at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
       at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

    Here is the error I am getting and the last setup log I can find. Any help how to get past the error would be helpful.
    Thank You,
    Stan
    Error
    The following error was generated when "$error.Clear();
              Install-ExchangeCertificate -WebSiteName "Exchange Back End" -services "IIS, POP, IMAP" -DomainController $RoleDomainController -InstallInTrustedRootCAIfSelfSigned $true
              if ($RoleIsDatacenter -ne $true -And $RoleIsPartnerHosted -ne $true)
                Install-AuthCertificate -DomainController $RoleDomainController
            " was run: "Microsoft.Exchange.Management.SystemConfigurationTasks.AddAccessRuleCryptographicException: Could not grant Network Service access to the certificate with thumbprint 845C42A131A8A73487400A91491182FB95B81612
    because a cryptographic exception was thrown. ---> System.Security.Cryptography.CryptographicException: Access is denied.
       at Microsoft.Exchange.Security.Cryptography.X509Certificates.TlsCertificateInfo.CAPIAddAccessRule(X509Certificate2 certificate, AccessRule rule)
       at Microsoft.Exchange.Security.Cryptography.X509Certificates.TlsCertificateInfo.AddAccessRule(X509Certificate2 certificate, AccessRule rule)
       at Microsoft.Exchange.Management.SystemConfigurationTasks.ManageExchangeCertificate.EnableForServices(X509Certificate2 cert, AllowedServices services, String websiteName, Boolean requireSsl, ITopologyConfigurationSession dataSession, Server server,
    List`1 warningList, Boolean allowConfirmation, Boolean forceNetworkService)
       --- End of inner exception stack trace ---
       at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
       at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
       at Microsoft.Exchange.Management.SystemConfigurationTasks.InstallExchangeCertificate.EnableForServices(X509Certificate2 cert, AllowedServices services)
       at Microsoft.Exchange.Management.SystemConfigurationTasks.InstallExchangeCertificate.InternalProcessRecord()
       at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
       at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
    Setup Log Below
    # Default Install steps for ClientAccessRole.
    # Programmatically generated on 7/5/2014 10:58:24 PM.
    # Variable Declarations
    $RoleAllRoles = 'BridgeheadRole,GatewayRole,ClientAccessRole,MailboxRole,UnifiedMessagingRole,FrontendTransportRole,AdminToolsRole,MonitoringRole,CentralAdminRole,CentralAdminDatabaseRole,CentralAdminFrontEndRole,LanguagePacksRole,CafeRole,FfoWebServiceRole,OSPRole'
    $RoleBinPath = 'C:\Program Files\Microsoft\Exchange Server\V15\Bin'
    $RoleCustomerFeedbackEnabled = $True
    $RoleDatacenterPath = 'C:\Program Files\Microsoft\Exchange Server\V15\Datacenter'
    $RoleDatacenterServiceEndpointABCHContactService = '<ServiceEndpoint><Url>http://pvt-contacts.msn.com/abservice/abservice.asmx</Url></ServiceEndpoint>'
    $RoleDatacenterServiceEndpointDomainPartnerManageDelegation = '<ServiceEndpoint><Url>https://domains.live.com/service/managedelegation.asmx</Url></ServiceEndpoint>'
    $RoleDatacenterServiceEndpointDomainPartnerManageDelegation2 = '<ServiceEndpoint><Url>https://domains.live.com/service/managedelegation2.asmx</Url></ServiceEndpoint>'
    $RoleDatacenterServiceEndpointLiveFederationMetadata = '<ServiceEndpoint><Url>https://nexus.passport.com/FederationMetadata/2006-12/FederationMetadata.xml</Url></ServiceEndpoint>'
    $RoleDatacenterServiceEndpointLiveGetUserRealm = '<ServiceEndpoint><Url>https://login.live.com/GetUserRealm.srf</Url></ServiceEndpoint>'
    $RoleDatacenterServiceEndpointLiveServiceLogin2 = '<ServiceEndpoint><Url>https://login.live.com/RST2.srf</Url></ServiceEndpoint>'
    $RoleDatacenterServiceEndpointMsoFederationMetadata = '<ServiceEndpoint><Url>https://nexus.microsoftonline-p.com/FederationMetadata/2006-12/FederationMetadata.xml</Url></ServiceEndpoint>'
    $RoleDomainController = 'MULTIAX2012.MULTIAXCNC.local'
    $RoleExternalCASServerDomain = $null
    $RoleFqdnOrName = 'MULTIAX2012.MULTIAXCNC.local'
    $RoleInstallationMode = 'Install'
    $RoleInstallPath = 'C:\Program Files\Microsoft\Exchange Server\V15\'
    $RoleInvocationID = '20140705-2258240578829153548'
    $RoleIsAdminToolsRoleInstalled = $True
    $RoleIsBridgeheadRoleInstalled = $True
    $RoleIsDatacenter = $False
    $RoleIsDatacenterDedicated = $False
    $RoleIsFfo = $False
    $RoleIsPartnerHosted = $False
    $RoleLanguagePacksPath = 'C:\Exchange\'
    $RoleLoggedOnUser = 'MULTIAXCNC\Administrator'
    $RoleLoggingPath = 'C:\Program Files\Microsoft\Exchange Server\V15\Logging'
    $RoleNetBIOSName = 'MULTIAX2012'
    $RoleNoSelfSignedCertificates = $False
    $RolePreviousVersion = $null
    $RoleProductPlatform = 'amd64'
    $RoleRoleName = 'ClientAccessRole'
    $RoleRoles = 'BridgeheadRole,AdminToolsRole'
    $RoleSetupLoggingPath = 'C:\ExchangeSetupLogs'
    $RoleTargetVersion = '15.00.0913.022'
    $RoleUpdatesDir = $null
    # Component tasks
    # Tasks for 'All Roles Common First' component
    # [ID = AllRolesCommonFirst___3e69ba31a53e4c29a2d6bffcf78cc614, Wt = 5, isFatal = True] "Starting the WMI service."
    7/5/2014 10:58:24 PM:
              if (Get-Service winmgmt* | ?{ $_.Name -ieq "winmgmt" })
                Set-Service winmgmt -StartupType Automatic
                Start-SetupService -ServiceName winmgmt
    # [ID = AllRolesCommonFirst___56139ce4432346ecb7936afae4c3a9cc, Wt = 1, isFatal = True] "Creating the Exchange server configuration object in Active Directory."
    7/5/2014 10:58:24 PM:
              & $RoleBinPath\ServiceControl.ps1 EnableServices $RoleRoleName.Replace('Role','')
    # [ID = AllRolesCommonFirst___edc23bc11a4e4119a6a4ee802ff1ea49, Wt = 1, isFatal = True] "Creating the Exchange server configuration object in Active Directory."
    7/5/2014 10:58:24 PM:
              if ($RoleRoles)
                & $RoleBinPath\ServiceControl.ps1 EnableServices $RoleRoles.Replace('Role','').Split(',')
    # [ID = AllRolesCommonFirst___62f13a063b2846a5ab20765bb7a3fc51, Wt = 5, isFatal = True] "Starting the Remote Registry service."
    7/5/2014 10:58:25 PM:Start-SetupService -ServiceName RemoteRegistry
    # [ID = AllRolesCommonFirst___00573a17b6e34c26842a6646830d57fa, Wt = 1, isFatal = True] "Creating the Exchange server configuration object in Active Directory."
    7/5/2014 10:58:25 PM:Set-LocalPermissions
    # [ID = AllRolesCommonFirst___77668249568048d3812fb7cdba08c58b, Wt = 1, isFatal = False] "Creating the Exchange server configuration object in Active Directory."
    7/5/2014 10:59:35 PM:
              $mofFilePath =  ($RoleInstallPath + "bin\Exchange.MOF");
              $mflFilePath =  ($RoleInstallPath + "bin\en\Exchange.MFL");
              compile-moffile -MofFilePath:$mofFilePath;
              compile-moffile -MofFilePath:$mflFilePath;
    # [ID = AllRolesCommonFirst___f557448f44964e5eaa5dba792a3c4f09, Wt = 1, isFatal = True] "Creating the Exchange server configuration object in Active Directory."
    7/5/2014 10:59:35 PM:
               Add-FirewallException -FirewallRule (New-Object Microsoft.Exchange.Security.WindowsFirewall.MSExchangeRPCByPortRule)
    # [ID = AllRolesCommonFirst___84a0f0e2c2f44db2b537e9696c26fc3e, Wt = 1, isFatal = True] "Creating the Exchange server configuration object in Active Directory."
    7/5/2014 10:59:35 PM:
               Add-FirewallException -FirewallRule (New-Object Microsoft.Exchange.Security.WindowsFirewall.MSExchangeRPCEPMapByPortRule)
    # Tasks for 'ClientAccess Permissions Configuration' component
    # [ID = ClientAccessLocalPermissionsComponent___6246589bb8494a3580c22c26e18451d1, Wt = 1, isFatal = True] "Setting folder or registry permissions for the Mailbox role: Client Access service. "
    7/5/2014 10:59:35 PM:Set-LocalPermissions -Feature:"ClientAccess"
    # Tasks for 'Exchange 2003 Registry Configuration' component
    # [ID = LegacyRegistryMarkersComponent___7d6dadc1069b42ac93eadd1143c04a1a, Wt = 1, isFatal = True] "Installing/Removing registry values used by Exchange 2003 components"
    7/5/2014 11:00:01 PM:set-ExsetdataRegistryMarkers
    # Tasks for 'Client Access Perf Counters' component
    # [ID = ClientAccessPerfCountersComponent___deb99c54869843b68426390615283ab7, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:00:01 PM:new-PerfCounters -DefinitionFileName OwaInstallSingleCounters.xml
    # [ID = ClientAccessPerfCountersComponent___ca78563ec1f1468982d1a2e59c6001bd, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:00:15 PM:new-PerfCounters -DefinitionFileName EcpPerfCounters.xml
    # [ID = ClientAccessPerfCountersComponent___e69a559428fb42029ca3261e795b216d, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:00:21 PM:new-PerfCounters -DefinitionFileName RwsPerfCounters.xml
    # [ID = ClientAccessPerfCountersComponent___c335490f948a4b16b5e2d2ce5f1eb9e7, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:00:26 PM:new-PerfCounters -DefinitionFileName InfoworkerAvailabilityPerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___5af856aa00ae485ca206c5cdd13e9128, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:00:31 PM:new-PerfCounters -DefinitionFileName InfoworkerSharingPerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___86121d1b951e43fb934f1f1d573362eb, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:00:35 PM:new-PerfCounters -DefinitionFileName ThrottlingPerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___ea5896b92c494834b1a93c4620fcaef4, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:00:42 PM:new-PerfCounters -DefinitionFileName MiddleTierStoragePerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___dab6f03bdf5141efb7b017c3009fb9e6, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:00:48 PM:new-PerfCounters -DefinitionFileName ActiveManagerClientPerfmon.xml
    # [ID = ClientAccessPerfCountersComponent___5471455db0ef4610bf68fe7ad9417e19, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:00:53 PM:new-PerfCounters -DefinitionFileName RmsPerfCounters.xml
    # [ID = ClientAccessPerfCountersComponent___81ad52cb2950483196b52371b4d992c8, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:00:58 PM:new-PerfCounters -DefinitionFileName InfoworkerMailTipsPerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___072bf6737f1c42a0a8847ce35cf8a0c7, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:01:03 PM:new-PerfCounters -DefinitionFileName InfoworkerUserPhotosPerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___50b64611f7444bb49d50e00c206d2c13, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:01:08 PM:new-PerfCounters -DefinitionFileName AirSyncCounters.xml
    # [ID = ClientAccessPerfCountersComponent___f2620ff8c3754396a8ea7d77257e2895, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:01:14 PM:new-PerfCounters -DefinitionFileName ClientAccessRulesPerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___4ef0f16c017840a583ace9f062300207, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:01:19 PM:new-PerfCounters -DefinitionFileName Imap4Counters.xml
    # [ID = ClientAccessPerfCountersComponent___135fb06dadd9403a83ceebb290638efe, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:01:24 PM:new-PerfCounters -DefinitionFileName Pop3Counters.xml
    # [ID = ClientAccessPerfCountersComponent___312e8d44e92b45e0809f9d3d5dc2cfc0, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:01:29 PM:new-PerfCounters -DefinitionFileName WsPerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___3c333497697041cb854190ec31c17b18, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:01:48 PM:new-PerfCounters -DefinitionFileName UMClientAccessCounters.xml
    # [ID = ClientAccessPerfCountersComponent___ba015b97cc0b4beba7b25b6cb297fcac, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:01:54 PM:new-PerfCounters -DefinitionFileName AutodiscoverPerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___3daffea50d5a4318aab4aa737e508146, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:01:59 PM:new-PerfCounters -DefinitionFileName OAuthCounters.xml
    # [ID = ClientAccessPerfCountersComponent___c71073d7f1ab4c119af83efb513b3a9d, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:02:04 PM:new-PerfCounters -DefinitionFileName InfoWorkerMessageTrackingPerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___abdaf0bf21f4473b88819ee85cada219, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:02:10 PM:new-PerfCounters -DefinitionFileName RpcClientAccessPerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___9f160f3e42984edfa25b62424ebc05b5, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:02:15 PM:new-PerfCounters -DefinitionFileName RpcClientAccessServerPerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___e55cb179521a4dacbeaa588c6948cf14, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:02:15 PM:new-PerfCounters -DefinitionFileName AddressBookServicePerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___064a7856cf7c4b0399c85cf4f3bc2f1c, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:02:20 PM:new-PerfCounters -DefinitionFileName RpcEntryPointsPerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___42325F33-A961-41FE-B6B5-5CFB3AA9820A, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:02:22 PM:new-PerfCounters -DefinitionFileName MapiHttpEmsmdbPerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___4C04D747-3B5C-400A-980F-45504324EF42, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:02:28 PM:new-PerfCounters -DefinitionFileName MapiHttpNspiPerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___5ab36fffacd04975bb1bc681a214bf71, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:02:33 PM:new-PerfCounters -DefinitionFileName ThrottlingServiceClientPerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___6ca23933132d44b39d6586cb3f9f8f21, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:02:39 PM:new-PerfCounters -DefinitionFileName MSExchMailboxReplicationServicePerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___6602c41b35254405bed412fab7d527fe, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:02:44 PM:new-PerfCounters -DefinitionFileName MSExchMailboxReplicationServicePerMdbPerformanceCounters.xml -FileMappingSize 2097152
    # [ID = ClientAccessPerfCountersComponent___74e45a45ea8c449092a10929ae24ba4b, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:02:50 PM:new-PerfCounters -DefinitionFileName MlbPerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___a3bcb686add64cf296c8616d387d0323, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:02:55 PM:new-PerfCounters -DefinitionFileName MlbMultiInstancePerformanceCounters.xml -FileMappingSize 2097152
    # [ID = ClientAccessPerfCountersComponent___c00c15c4ef6f479b9f5deb852d8eda7d, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:03:01 PM:new-PerfCounters -DefinitionFileName ProvisioningPerfCounters.xml
    # [ID = ClientAccessPerfCountersComponent___fe1a2a7c828f4b57abc2e50dc09baddf, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:03:06 PM:new-PerfCounters -DefinitionFileName GalsyncPerfCounters.xml
    # [ID = ClientAccessPerfCountersComponent___35D14CB8B01949818832943A391D77B9, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:03:11 PM:new-PerfCounters -DefinitionFileName BackSyncPerfCounters.xml
    # [ID = ClientAccessPerfCountersComponent___e69599d235234effb6d2740f3c52f7e1, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:03:11 PM:new-PerfCounters -DefinitionFileName AdminAuditPerfCounters.xml
    # [ID = ClientAccessPerfCountersComponent___09bd11b57f6445e890391a507262cf32, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:03:16 PM:new-PerfCounters -DefinitionFileName InfoworkerMultiMailboxSearchPerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___324687361E1C473A834C22A66104679f, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:03:16 PM:new-PerfCounters -DefinitionFileName ProvisioningCachePerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___98C36FFEC7944065889DB24067CFD3EE, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:03:21 PM:new-PerfCounters -DefinitionFileName OABRequestHandlerPerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___1F5A7B68C95B42568E02FAA15A05EF17, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:03:26 PM:new-PerfCounters -DefinitionFileName DlpPolicyTipsPerformanceCounters.xml
    # [ID = ClientAccessPerfCountersComponent___995DEA7A1AC5467C89939F5F8CE5F2AF, Wt = 1, isFatal = False] "Installing or removing Client Access performance counters."
    7/5/2014 11:03:31 PM:new-PerfCounters -DefinitionFileName ConfigurationCachePerformanceCounters.xml
    # Tasks for 'Client Access Configuration' component
    # [ID = ClientAccessComponent___d5119205104847bcb275cb63b65160b6, Wt = 5, isFatal = False] "Pre-compiling setup binaries."
    7/5/2014 11:03:35 PM:
              $fullPath = [System.IO.Path]::Combine($RoleInstallPath, "ClientAccess\Owa\Bin\Microsoft.Exchange.Clients.Owa.dll");
              $appBase = [System.IO.Path]::Combine($RoleInstallPath, "bin");
              precompile-ManagedBinary -BinaryName  $fullPath -AppBase $appBase;
    # [ID = ClientAccessComponent___954344d74d8849e9ae7123b91761ed9d, Wt = 5, isFatal = False] "Pre-compiling setup binaries."
    7/5/2014 11:03:57 PM:
              $fullPath = [System.IO.Path]::Combine($RoleInstallPath, "ClientAccess\Sync\Bin\Microsoft.Exchange.AirSyncHandler.dll");
              $appBase = [System.IO.Path]::Combine($RoleInstallPath, "bin");
              precompile-ManagedBinary -BinaryName  $fullPath -AppBase $appBase;
    # [ID = ClientAccessComponent___6632d6c1d5054563942db4f180976238, Wt = 5, isFatal = False] "Pre-compiling setup binaries."
    7/5/2014 11:04:01 PM:
              $fullPath = [System.IO.Path]::Combine($RoleInstallPath, "ClientAccess\AutoDiscover\Bin\Microsoft.Exchange.AutoDiscover.dll");
              $appBase = [System.IO.Path]::Combine($RoleInstallPath, "bin");
              precompile-ManagedBinary -BinaryName  $fullPath -AppBase $appBase;
    # [ID = ClientAccessComponent___390b4ffddd484dcb9edc01dd725e020a, Wt = 5, isFatal = False] "Pre-compiling setup binaries."
    7/5/2014 11:04:07 PM:
              $fullPath = [System.IO.Path]::Combine($RoleInstallPath, "ClientAccess\exchweb\ews\bin\Microsoft.Exchange.Services.dll");
              $appBase = [System.IO.Path]::Combine($RoleInstallPath, "bin");
              precompile-ManagedBinary -BinaryName  $fullPath -AppBase $appBase;
    # [ID = ClientAccessComponent___178a10624c88445093855c4ede7e9b9c, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:42 PM:
              . "$RoleInstallPath\Scripts\ConfigureNetworkProtocolParameters.ps1";
              Set-NtlmLoopbackCheck $false
    # [ID = ClientAccessComponent___14a6761e144e428b93c62249acc814fe, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:42 PM:install-ClientAccessIisWebServiceExtensions
    # [ID = ClientAccessComponent___28fdfe8bec984e809cdeef6d4d59bf4e, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:43 PM:
            if (get-service MSExchangeServiceHost* | where {$_.name -eq "MSExchangeServiceHost"})
                restart-service MSExchangeServiceHost
    # [ID = ClientAccessComponent___7816256880dc4be0baf5b005b2af8cd3, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:45 PM:
            if (get-service MSExchangeProtectedServiceHost* | where {$_.name -eq "MSExchangeProtectedServiceHost"})
                restart-service MSExchangeProtectedServiceHost
    # [ID = ClientAccessComponent___e95499b43bd1484dbc03098fb1b4e592, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:45 PM:set-ExchangeServerRole -Identity $RoleFqdnOrName -IsClientAccessServer:$true -DomainController $RoleDomainController
    # [ID = ClientAccessComponent___f4c48e196e374cf3af269b1cea0602c8, Wt = 1, isFatal = True] "Installing/Removing the WebReady Document Viewing service."
    7/5/2014 11:04:45 PM:Install-TranscodingServiceEx
    # [ID = ClientAccessComponent___f50fd59d231140eb9b2405bbed2b93d4, Wt = 1, isFatal = False] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:45 PM:
              if ($RoleIsDatacenter -eq $false)
                uninstall-FBAService
    # [ID = ClientAccessComponent___9fad9d51b3ec4ecdad567ab58e470be7, Wt = 1, isFatal = False] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:45 PM:
              if ($RoleIsDatacenter -eq $false)
                stop-setupservice -ServiceName MSExchangeFBA
    # [ID = ClientAccessComponent___1c7a7da2ab9d41bb8db75522ad28b9db, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:45 PM:
              $tpath = "$env:SystemRoot\system32\inetsrv\microsoft.web.administration.dll";
              add-type -Path $tpath;
              $sm = new-object Microsoft.Web.Administration.ServerManager;
              if ($sm.Sites["Exchange Back End"] -eq $null)
                $ppath = "$env:SystemDrive\inetpub\wwwroot";
                $s = $sm.Sites.Add("Exchange Back End","http", "*:81:", $ppath);
                $s.ServerAutoStart = $true;
                $sb =$s.Bindings;
                $b = $sb.Add("*:444:","https");
                $sm.CommitChanges();
    # [ID = ClientAccessComponent___a5f211d837784aea931b9ba55c39996d, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:45 PM:
              Get-ExchangeServer $RoleFqdnOrName | Add-AdPermission -User "S-1-5-20" -ExtendedRights "Exchange Web Services Token Serialization";
    # [ID = ClientAccessComponent__SetInstallPathInMrsAppConfig, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:45 PM:
              Set-InstallPathInAppConfig -ConfigFileRelativePath "Bin" -ConfigFileName "MsExchangeMailboxReplication.exe.config"
    # [ID = ClientAccessComponent___765cc444ba07411aa81d58397b0401fd, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:45 PM:
              if (!(get-service MSExchangeMailboxReplication* | where {$_.name -eq "MSExchangeMailboxReplication"}))
                install-MailboxReplicationService
    # [ID = ClientAccessComponent___151b722e327b42a69411df32afdbbcbb, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:46 PM:
               Add-FirewallException -FirewallRule (New-Object Microsoft.Exchange.Security.WindowsFirewall.MSExchangeMailboxReplicationFirewallRule)
    # [ID = ClientAccessComponent___7d69bb94f08245589e49eb569c6d5f4f, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:46 PM:
              if (!(get-service MSExchangeMigrationWorkflow* | where {$_.name -eq "MSExchangeMigrationWorkflow"}))
                install-MigrationWorkflowService
    # [ID = ClientAccessComponent___95f051d9dc5941c4b6014181b6e5ce93, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:47 PM:
               Add-FirewallException -FirewallRule (New-Object Microsoft.Exchange.Security.WindowsFirewall.MSExchangeABRPCFirewallRule)
    # [ID = ClientAccessComponent___959c2d6566984da6b8e0e3235c1c11c2, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:47 PM:
               Add-FirewallException -FirewallRule (New-Object Microsoft.Exchange.Security.WindowsFirewall.MSExchangePOPBeByPortRule)
    # [ID = ClientAccessComponent___29864e7462374fdb84fc75eec931d8e4, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:47 PM:
              Add-FirewallException -FirewallRule (New-Object Microsoft.Exchange.Security.WindowsFirewall.MSExchangeIMAP4BeFirewallRule)
    # [ID = ClientAccessComponent___052e1b794d0641ada4d6d417061af2a8, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:47 PM:
               Add-FirewallException -FirewallRule (New-Object Microsoft.Exchange.Security.WindowsFirewall.MSExchangeOWAByPortRule)
    # [ID = ClientAccessComponent___975efd8911fd41cca8b17462535d710e, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:47 PM:
               Add-FirewallException -FirewallRule (New-Object Microsoft.Exchange.Security.WindowsFirewall.MSExchangeMailboxReplicationByPort)
    # [ID = ClientAccessComponent___023036e43f004bda9f4f4e0b1e0d233f, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:47 PM:
              Install-ResourceHealthActiveFlags
    # [ID = ClientAccessComponent___3a51c2876e2c4643bc892d2665754228, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:47 PM:set-InstallPathInAppConfig -ConfigFileRelativePath "ClientAccess\PushNotifications\" -ConfigFileName web.config
    # [ID = ClientAccessComponent___FCC16AC1FFED43518F8292DBE770C621, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:47 PM:set-InstallPathInAppConfig -ConfigFileRelativePath "ClientAccess\mapi\emsmdb\" -ConfigFileName web.config
    # [ID = ClientAccessComponent___E9C71786D02E40CBB1403E2E1A4B0758, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:47 PM:set-InstallPathInAppConfig -ConfigFileRelativePath "ClientAccess\mapi\nspi\" -ConfigFileName web.config
    # [ID = ClientAccessComponent___abcab6b91ac844848c58b4ee66fcbea6, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:47 PM:
                ."$RoleInstallPath\Scripts\Install-OutlookServiceVirtualDirectory.ps1";
    # [ID = ClientAccessComponent___9D94915F-B12D-4579-93EE-36B6DF42CF4A, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:47 PM:
              $CommandAppCmd = join-path $env:SystemRoot System32\inetsrv\appcmd.exe;
              $MapiClientAccessPath = [System.IO.Path]::Combine($RoleInstallPath, "ClientAccess\mapi");
              $MapiMailboxClientAccessPath = [System.IO.Path]::Combine($RoleInstallPath, "ClientAccess\mapi\emsmdb");
              $clrConfigFilePath = [System.IO.Path]::Combine($RoleInstallPath, "bin", "MSExchangeMapiMailboxAppPool_CLRConfig.config");
              Start-SetupProcess -Name "$CommandAppCmd" -args "add apppool /name:MSExchangeMapiMailboxAppPool /autostart:true /managedRuntimeVersion:v4.0 /queueLength:65535 /CLRConfigFile:`"$clrConfigFilePath`" /managedRuntimeLoader:`"`"
    /processModel.identityType:LocalSystem /managedPipelineMode:Integrated /recycling.periodicRestart.time:00:00:00 /processModel.idleTimeout:00:00:00 /processModel.pingingEnabled:false /failure.rapidFailProtection:false" -IgnoreExitCode @(183);
              Start-SetupProcess -Name "$CommandAppCmd" -args "add vdir /app.name:`"Exchange Back End/`" /path:`"/mapi`" /physicalPath:`"$MapiClientAccessPath`"" -IgnoreExitCode @(183);
              Start-SetupProcess -Name "$CommandAppCmd" -args "add app /site.name:`"Exchange Back End`" /physicalPath:`"$MapiMailboxClientAccessPath`" /applicationPool:MSExchangeMapiMailboxAppPool /path:`"/mapi/emsmdb`""
    -IgnoreExitCode @(183);
              Start-SetupProcess -Name "$CommandAppCmd" -args "set config `"Exchange Back End/mapi/emsmdb`" /section:system.webServer/security/access /sslFlags:Ssl /commit:apphost";
              Start-SetupProcess -Name "$CommandAppCmd" -args "set config `"Exchange Back End/mapi/emsmdb`" /section:system.webServer/security/authentication/anonymousAuthentication /enabled:false /commit:apphost";
              Start-SetupProcess -Name "$CommandAppCmd" -args "set config `"Exchange Back End/mapi/emsmdb`" /section:system.webServer/security/authentication/basicAuthentication /enabled:false /commit:apphost";
              Start-SetupProcess -Name "$CommandAppCmd" -args "set config `"Exchange Back End/mapi/emsmdb`" /section:system.webServer/security/authentication/clientCertificateMappingAuthentication /enabled:false /commit:apphost";
              Start-SetupProcess -Name "$CommandAppCmd" -args "set config `"Exchange Back End/mapi/emsmdb`" /section:system.webServer/security/authentication/digestAuthentication /enabled:false /commit:apphost";
              Start-SetupProcess -Name "$CommandAppCmd" -args "set config `"Exchange Back End/mapi/emsmdb`" /section:system.webServer/security/authentication/iisClientCertificateMappingAuthentication /enabled:false /commit:apphost";
              Start-SetupProcess -Name "$CommandAppCmd" -args "set config `"Exchange Back End/mapi/emsmdb`" /section:system.webServer/security/authentication/windowsAuthentication /enabled:true /commit:apphost";
    # [ID = ClientAccessComponent___B551AAAC-0F36-428B-B1BB-3B9AFDC9EAEF, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:50 PM:
              $CommandAppCmd = join-path $env:SystemRoot System32\inetsrv\appcmd.exe;
              $MapiClientAccessPath = [System.IO.Path]::Combine($RoleInstallPath, "ClientAccess\mapi");
              $MapiAddressBookClientAccessPath = [System.IO.Path]::Combine($RoleInstallPath, "ClientAccess\mapi\nspi");
              $clrConfigFilePath = [System.IO.Path]::Combine($RoleInstallPath, "bin", "MSExchangeMapiAddressBookAppPool_CLRConfig.config");
              Start-SetupProcess -Name "$CommandAppCmd" -args "add apppool /name:MSExchangeMapiAddressBookAppPool /autostart:true /managedRuntimeVersion:v4.0 /queueLength:65535 /CLRConfigFile:`"$clrConfigFilePath`" /managedRuntimeLoader:`"`"
    /processModel.identityType:LocalSystem /managedPipelineMode:Integrated /recycling.periodicRestart.time:00:00:00 /processModel.idleTimeout:00:00:00 /processModel.pingingEnabled:false /failure.rapidFailProtection:false" -IgnoreExitCode @(183);
              Start-SetupProcess -Name "$CommandAppCmd" -args "add vdir /app.name:`"Exchange Back End/`" /path:`"/mapi`" /physicalPath:`"$MapiClientAccessPath`"" -IgnoreExitCode @(183);
              Start-SetupProcess -Name "$CommandAppCmd" -args "add app /site.name:`"Exchange Back End`" /physicalPath:`"$MapiAddressBookClientAccessPath`" /applicationPool:MSExchangeMapiAddressBookAppPool /path:`"/mapi/nspi`""
    -IgnoreExitCode @(183);
              Start-SetupProcess -Name "$CommandAppCmd" -args "set config `"Exchange Back End/mapi/nspi`" /section:system.webServer/security/access /sslFlags:Ssl /commit:apphost";
              Start-SetupProcess -Name "$CommandAppCmd" -args "set config `"Exchange Back End/mapi/nspi`" /section:system.webServer/security/authentication/anonymousAuthentication /enabled:false /commit:apphost";
              Start-SetupProcess -Name "$CommandAppCmd" -args "set config `"Exchange Back End/mapi/nspi`" /section:system.webServer/security/authentication/basicAuthentication /enabled:false /commit:apphost";
              Start-SetupProcess -Name "$CommandAppCmd" -args "set config `"Exchange Back End/mapi/nspi`" /section:system.webServer/security/authentication/clientCertificateMappingAuthentication /enabled:false /commit:apphost";
              Start-SetupProcess -Name "$CommandAppCmd" -args "set config `"Exchange Back End/mapi/nspi`" /section:system.webServer/security/authentication/digestAuthentication /enabled:false /commit:apphost";
              Start-SetupProcess -Name "$CommandAppCmd" -args "set config `"Exchange Back End/mapi/nspi`" /section:system.webServer/security/authentication/iisClientCertificateMappingAuthentication /enabled:false /commit:apphost";
              Start-SetupProcess -Name "$CommandAppCmd" -args "set config `"Exchange Back End/mapi/nspi`" /section:system.webServer/security/authentication/windowsAuthentication /enabled:true /commit:apphost";
    # [ID = ClientAccessComponent___178FD1A31B5949A0B4A819E39311B1FD, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:52 PM:
                $ExchangeLabsRegKey = 'HKLM:\SOFTWARE\Microsoft\ExchangeLabs'
                $E4eCertificateDistinguishedNameRegValueName = 'E4eCertificateDistinguishedName'
                if ($RoleDatacenterE4eCertificateDistinguishedName -ne $null)
                    New-ItemProperty -path "$ExchangeLabsRegKey" -Name $E4eCertificateDistinguishedNameRegValueName -Value $RoleDatacenterE4eCertificateDistinguishedName -Force
                    Write-ExchangeSetupLog -Info "Wrote registry key: $ExchangeLabsRegKey\$E4eCertificateDistinguishedNameRegValueName. value: $RoleDatacenterE4eCertificateDistinguishedName"
                else
                    Write-ExchangeSetupLog -Info "Could not write registry key: $ExchangeLabsRegKey\$E4eCertificateDistinguishedNameRegValueName. Value is null."
                $E4eServiceUrlRegValueName = 'E4eServiceUrl'
                if ($RoleDatacenterE4eServiceUrl -ne $null)
                    New-ItemProperty -path "$ExchangeLabsRegKey" -Name $E4eServiceUrlRegValueName -Value $RoleDatacenterE4eServiceUrl -Force
                    Write-ExchangeSetupLog -Info "Wrote registry key: $ExchangeLabsRegKey\$E4eServiceUrlRegValueName. value: $RoleDatacenterE4eServiceUrl"
                else
                    Write-ExchangeSetupLog -Info "Could not write registry key: $ExchangeLabsRegKey\$E4eServiceUrlRegValueName. Value is null."
    # [ID = ClientAccessComponent___240c7e5d07f941cfbe69a692dc33a31a, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:52 PM:
              ."$RoleInstallPath\Scripts\ConfigureCafeResponseHeaders.ps1";
              CreateCustomHeadersNodeForBackend 'autodiscover'
              CreateCustomHeadersNodeForBackend 'ecp'
              CreateCustomHeadersNodeForBackend 'ews'  
              CreateCustomHeadersNodeForBackend 'oab'
              CreateCustomHeadersNodeForBackend 'owa'
              CreateCustomHeadersNodeForBackend 'powershell'
              CreateCustomHeadersNodeForBackend 'pushnotifications'
              CreateCustomHeadersNodeForBackend 'rpcproxy'
              CreateCustomHeadersNodeForBackend 'sync'
              CreateCustomHeadersNodeForBackend 'mapi\emsmdb'
              CreateCustomHeadersNodeForBackend 'mapi\nspi'
              CreateCustomHeadersNodeForBackend 'outlookservice'
    # [ID = ClientAccessComponent___75f8c93d15314369983d33ec0742e189, Wt = 1, isFatal = True] "Configuring Mailbox role: Client Access service."
    7/5/2014 11:04:53 PM:
              New-PushNotificationsVirtualDirectory -Role Mailbox -DomainController $RoleDomainController;
    # Tasks for 'POP/IMAP Backend Configuration' component
    # [ID = PopImapBeComponent___d91be94d83bb4dc28e1fbdf7d94ca60e, Wt = 1, isFatal = True] "Configuring the server."
    7/5/2014 11:05:05 PM:
              if (!(get-service MSExchangeIMAP4BE* | where {$_.name -eq "MSExchangeIMAP4BE"}))
                install-Imap4BeService
    # [ID = PopImapBeComponent___e2debc6ecabf457eb6f278096ad5102c, Wt = 1, isFatal = True] "Configuring the server."
    7/5/2014 11:05:06 PM:
              if (!(get-service MSExchangePOP3BE* | where {$_.name -eq "MSExchangePOP3BE"}))
                install-Pop3BeService
    # [ID = PopImapBeComponent___7ee4dbb3fe884d26bb3e060ac68061ee, Wt = 1, isFatal = True] "Configuring the server."
    7/5/2014 11:05:06 PM:
              $file = 'Microsoft.Exchange.Pop3Service.exe.config';
              $template = $file + '.template';
              $relPath = 'ClientAccess\PopImap';
              $fullPath = [System.IO.Path]::Combine($RoleInstallPath, $relPath);
              $fullFilePath = [System.IO.Path]::Combine($fullPath, $file);
              Set-InstallPathInAppConfig -ConfigFileRelativePath $relPath -ConfigFileName $template;
              Preserve-AppSettings -RoleInstallPath $fullPath -ConfigFileName $file;
              set-appconfigvalue -ConfigFileFullPath:$fullFilePath -Element:configuration/runtime/generatePublisherEvidence -Attribute:enabled -NewValue:false
    # [ID = PopImapBeComponent___9b86c2af9f364990aa196cb6e69905b6, Wt = 1, isFatal = True] "Configuring the server."
    7/5/2014 11:05:06 PM:
              $file = 'Microsoft.Exchange.Pop3.exe.config';
              $template = $file + '.template';
              $relPath = 'ClientAccess\PopImap';
              $fullPath = [System.IO.Path]::Combine($RoleInstallPath, $relPath);
              Set-InstallPathInAppConfig -ConfigFileRelativePath $relPath -ConfigFileName $template;
              Preserve-AppSettings -RoleInstallPath $fullPath -ConfigFileName $file;
    # [ID = PopImapBeComponent___01c604c08fd6402e9de6b3c45e3431c8, Wt = 1, isFatal = True] "Configuring the server."
    7/5/2014 11:05:06 PM:
              $file = 'Microsoft.Exchange.Imap4Service.exe.config';
              $template = $file + '.template';
              $relPath = 'ClientAccess\PopImap';
              $fullPath = [System.IO.Path]::Combine($RoleInstallPath, $relPath);
              $fullFilePath = [System.IO.Path]::Combine($fullPath, $file);
              Set-InstallPathInAppConfig -ConfigFileRelativePath $relPath -ConfigFileName $template;
              Preserve-AppSettings -RoleInstallPath $fullPath -ConfigFileName $file;
              set-appconfigvalue -ConfigFileFullPath:$fullFilePath -Element:configuration/runtime/generatePublisherEvidence -Attribute:enabled -NewValue:false
    # [ID = PopImapBeComponent___2528980001a444fcb7097d123e879728, Wt = 1, isFatal = True] "Configuring the server."
    7/5/2014 11:05:06 PM:
              $file = 'Microsoft.Exchange.Imap4.exe.config';
              $template = $file + '.template';
              $relPath = 'ClientAccess\PopImap';
              $fullPath = [System.IO.Path]::Combine($RoleInstallPath, $relPath);
              Set-InstallPathInAppConfig -ConfigFileRelativePath $relPath -ConfigFileName $template;
              Preserve-AppSettings -RoleInstallPath $fullPath -ConfigFileName $file;
    # [ID = PopImapBeComponent___bbfdc492aaf748298977cb9b98e00029, Wt = 1, isFatal = True] "Configuring the server."
    7/5/2014 11:05:07 PM:install-Imap4Container -Name:"IMAP4" -DomainController $RoleDomainController
    # [ID = PopImapBeComponent___091c98cfe0f145189c0966717496795e, Wt = 1, isFatal = True] "Configuring the server."
    7/5/2014 11:05:07 PM:install-Pop3Container -Name:"POP3" -DomainController $RoleDomainController
    # [ID = PopImapBeComponent___42cb9f4ac2924c27b6ebf60b92a03628, Wt = 1, isFatal = True] "Configuring the server."
    7/5/2014 11:05:07 PM:new-ImapSettings -DomainController $RoleDomainController -ExchangePath $RoleInstallPath
    # [ID = PopImapBeComponent___181f5361a5df4e7ca009f21f26f8c0d5, Wt = 1, isFatal = True] "Configuring the server."
    7/5/2014 11:05:07 PM:new-PopSettings -DomainController $RoleDomainController -ExchangePath $RoleInstallPath
    # Tasks for 'ClientAccessExchangeCertificate' component
    # [ID = ClientAccessExchangeCertificate___fb5e9028e669404d94dba90aace8c2f9, Wt = 1, isFatal = True] "Installing Client Access server certificates."
    7/5/2014 11:05:07 PM:
              Install-ExchangeCertificate -WebSiteName "Exchange Back End" -services "IIS, POP, IMAP" -DomainController $RoleDomainController -InstallInTrustedRootCAIfSelfSigned $true
              if ($RoleIsDatacenter -ne $true -And $RoleIsPartnerHosted -ne $true)
                Install-AuthCertificate -DomainController $RoleDomainController

  • Exchange Server 2013 and Domain Controller

    Hello,
    I am planning to install domain controller and exchange server 2013 in same server hardware. Is that not recommended? If not, why is it no recommended?
    Thank you in advance,

    thanks for such a quick response.
    Just a small question about the link that you put. Does member server mean other server other than domain controller?
    Regards,
    Yes, Also the server on which you are installing Exchange should have exchange installed.
    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.

  • Microsoft Exchange Server 2003 and McAfee Email Gateway appliance

    I have been connecting to my company's exchange server without incident until the IT department installed a McAfee Email Gateway. Now I cannot connect and the IT department tells me there is nothing they can do. Has anyone encountered this issue?

    If server has enabled ActiveSync you can use Windows 8 Mail Client - works almost like Outlook.
    AFAIR Outlook 2013 can't work with Exchange 2003.
    Regards, Konrad Sagala, MCT, MCSE+M, MCITP: Exchange 2007/2010, Lync 2010, Office365, Windows 2008, Virtualization

  • Autodiscover Exchange Server 2007 and 2013 Coexistence

    Hello
    We are having some issues where some users are not being notified when their mailbox is being migrated to E2013.
    Before 2013, we never had a load balanced solution for CAS in Exchange Server 2007 or a single name space.
    Below is our current config
    AutoDiscoverServiceCN          : Server2K7CASpd
    AutoDiscoverServiceClassName   : ms-Exchange-AutoDiscover-Service
    AutoDiscoverServiceInternalUri : https://legacy.domain.int/Autodiscover/Autodiscover.xml
    AutoDiscoverServiceGuid        : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
    AutoDiscoverSiteScope          : {USChicago, UKLondon, SGSingapore}
    AutoDiscoverServiceCN          : Server2k7CASdr
    AutoDiscoverServiceClassName   : ms-Exchange-AutoDiscover-Service
    AutoDiscoverServiceInternalUri : https://legacy.domain.int/Autodiscover/Autodiscover.xml
    AutoDiscoverServiceGuid        : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
    AutoDiscoverSiteScope          : {USChicago, UKLondon, SGSingapore}
    AutoDiscoverServiceCN          : Server2013CASPD01
    AutoDiscoverServiceClassName   : ms-Exchange-AutoDiscover-Service
    AutoDiscoverServiceInternalUri : https://autodiscover.domain.int/autodiscover/autodiscover.xml
    AutoDiscoverServiceGuid        : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
    AutoDiscoverSiteScope          : {UKLondon}
    AutoDiscoverServiceCN          : Server2013CASPD02
    AutoDiscoverServiceClassName   : ms-Exchange-AutoDiscover-Service
    AutoDiscoverServiceInternalUri : https://autodiscover.domain.int/autodiscover/autodiscover.xml
    AutoDiscoverServiceGuid        : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
    AutoDiscoverSiteScope          : {UKLondon}
    AutoDiscoverServiceCN          : Server2013CASDR02
    AutoDiscoverServiceClassName   : ms-Exchange-AutoDiscover-Service
    AutoDiscoverServiceInternalUri : https://autodiscover.domain.int/autodiscover/autodiscover.xml
    AutoDiscoverServiceGuid        : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
    AutoDiscoverSiteScope          : {UKLondon}
    AutoDiscoverServiceCN          : Server2013CASDR01
    AutoDiscoverServiceClassName   : ms-Exchange-AutoDiscover-Service
    AutoDiscoverServiceInternalUri : https://autodiscover.domain.int/autodiscover/autodiscover.xml
    AutoDiscoverServiceGuid        : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
    AutoDiscoverSiteScope          : {UKLondon}
    I believe that we should change the AutoDiscoverServiceInternalUri on the two 2007 CAS to ALSO be the same as our 2013 CAS.
    We know that when Outlook is opened, Autodiscover will respond with any of the 6 available CAS, and we think that those Outlook clients that are misconfigured, are those that are not getting notified when their Mailbox is moved to E2013.
    Thanks

    We are also getting inconsistent results using the Test-OutlookWebServices PS
    Test 1
    Test-OutlookWebServices -Identity [email protected] | fl
    Id      : 1003
    Type    : Information
    Message : About to test AutoDiscover with the e-mail address [email protected].
    Id      : 1006
    Type    : Information
    Message : The Autodiscover service was contacted at https://legacy.domain.local/Autodiscover/Autodiscover.xml.
    Id      : 1016
    Type    : Success
    Message : [EXCH]-Successfully contacted the AS service at https://ServerCASpd05.domain.local/EWS/Exchange.asmx. The elapsed
              time was 76 milliseconds.
    Id      : 1015
    Type    : Success
    Message : [EXCH]-Successfully contacted the OAB service at https://ServerCASpd05.domain.local/EWS/Exchange.asmx. The elapsed
              time was 0 milliseconds.
    Id      : 1014
    Type    : Success
    Message : [EXCH]-Successfully contacted the UM service at https://ServerCASdr05.domain.local/UnifiedMessaging/Service.asmx.
              The elapsed time was 558 milliseconds.
    Id      : 1016
    Type    : Success
    Message : [EXPR]-Successfully contacted the AS service at https://legacy.domain.local/EWS/Exchange.asmx. The elapsed time
              was 46 milliseconds.
    Id      : 1015
    Type    : Information
    Message : [EXPR]-The OAB is not configured for this user.
    Id      : 1014
    Type    : Information
    Message : [EXPR]-The UM is not configured for this user.
    Id      : 1013
    Type    : Error
    Message : When contacting https://mail.domain.local/Rpc received the error The remote server returned an error: (404) Not
              Found.
    Id      : 1017
    Type    : Error
    Message : [EXPR]-Error when contacting the RPC/HTTP service at https://mail.domain.local/Rpc. The elapsed time was 93
              milliseconds.
    Id      : 1006
    Type    : Success
    Message : The Autodiscover service was tested successfully.
    Id      : 1021
    Type    : Information
    Message : The following web services generated errors.
                  Contacting server in EXPR
              Please use the prior output to diagnose and correct the errors.
    Test 2
    Test-OutlookWebServices -Identity [email protected] | fl
    Id      : 1003
    Type    : Information
    Message : About to test AutoDiscover with the e-mail address [email protected].
    Id      : 1006
    Type    : Information
    Message : The Autodiscover service was contacted at https://legacy.Domain.local/Autodiscover/Autodiscover.xml.
    Id      : 1016
    Type    : Success
    Message : [EXCH]-Successfully contacted the AS service at https://ServerCASpd05.Domain.local/EWS/Exchange.asmx. The elapsed
              time was 46 milliseconds.
    Id      : 1015
    Type    : Success
    Message : [EXCH]-Successfully contacted the OAB service at https://ServerCASpd05.Domain.local/EWS/Exchange.asmx. The elapsed
              time was 0 milliseconds.
    Id      : 1014
    Type    : Success
    Message : [EXCH]-Successfully contacted the UM service at https://ServerCASdr05.Domain.local/UnifiedMessaging/Service.asmx.
              The elapsed time was 15 milliseconds.
    Id      : 1016
    Type    : Success
    Message : [EXPR]-Successfully contacted the AS service at https://legacy.Domain.local/EWS/Exchange.asmx. The elapsed time
              was 78 milliseconds.
    Id      : 1015
    Type    : Information
    Message : [EXPR]-The OAB is not configured for this user.
    Id      : 1014
    Type    : Information
    Message : [EXPR]-The UM is not configured for this user.
    Id      : 1017
    Type    : Success
    Message : [EXPR]-Successfully contacted the RPC/HTTP service at https://legacy.Domain.local/Rpc. The elapsed time was 187
              milliseconds.
    Id      : 1006
    Type    : Success
    Message : The Autodiscover service was tested successfully.

  • Upgrading from SBS 2008 and Exchange Server 2007 and Adding Modest Failover Protection

    I haven't seen anyone describe this scenario, so maybe it can't be done, but it seems it should work. Can someone either confirm this is viable or set me straight and tell me it's not wise (and if not, why not).
    I currently have SBS 2008 (2008 Server + Exchange Server 2007 + some other components). I use redirected folders so all my user data is stored primarily on the server, and then sync'd with their local harddrives for roaming use and as an additional
    backup precaution. I want to upgrade to a modern version of Exchange (don't care too much about the underlying server OS, but seems like a good time to upgrade everything). I also want to improve the reliability for rapid recovery in the event of a system
    failure. I have always felt nervous with SBS because it only runs on a single server.
    My plan is:
    Install Windows Server 2012 Standard on a new server machine
    Join that new server to the existing SBS domain and sync the users, etc.
    Install Exchange Server 2013 on the new 2012 Server
    Migrate the existing Exchange data and account info to the new server
    Demote the SBS Server and promote the new server to primary DC
    Reformat the old SBS server and install Windows Server 2012 on it too, and join it to the domain as a second DC
    Set up DFS Replication and keep all my user data folders between the two servers (so if one server fails, the other can take over, just not automatically like with a cluster)
    Install Exchange Server 2013 on the reformatted 2012 Server box (so second instance on the domain) and set it up to sync with the first Exchange Server 2013 via DAG (so if either computer crashes, the other can take over for both Exchange Server and file
    services)
    Wouldn't that give me a complete slow-response failover system without the need for setting up a cluster (I know a cluster would provide instant failover protection, but I don't need that kind of speed - a manual switchover in the rare event of a server
    failure is acceptable for us)? I could do this using cheap hardware for each server, because unless both servers fail at the same time, clients can point to the other server. And because it's not a formal cluster, I don't need to buy anything for a shared
    SAN. This seems like such an obvious more cost-effective solution for a small network, I don't understand why this isn't a common approach, which makes me wonder if there is some reason it won't work.
    Any suggestions or feedback? Are Redirected Folders still recommended for users on a Server 2012-based domain?
    Thanks,
    Colin
    Colin

    Ed, thanks again for your help. OK, so here's my updated plan (I realize I should probably check on some of these pieces on the Server group, instead of this Exchange group).
    Constraints/objectives:
    None of the machines are truly server grade hardware, but only 5 people on the network, so performance is generally not an issue, unless a given server is just pegged on CPU or HD due to its own internal maintenance tasks and can't respond to user requests.
    Haven't seen any problems, since upgrading server from 4GB RAM to 8GB a few years ago.
    Not going to buy any new hardware at this time, but do have several unused consumer-grade computers I can deploy as wimpy or moderate servers.
    Main issue is to limit repair time in the event of a system failure (instant failover is not required, but want to be able to restore network functions within less than 24 hours in the event of a hardware failure) and minimize time spent on IT
    maintenance.
    Because of light IT maintenance (not anyone's primary job and we're too small to justify a dedicated IT person or to pay for outside help), almost every touch takes me research and time to re-learn what I haven't done in weeks, months, or years -- so also
    want to keep all IT tasks as simple as possible.
    We philosophically want to invest now for the next 5 years and avoid ongoing cloud fees (so zero interest in Windows Server Essentials with Exchange Online)
    A little nervous about using VM's, just because I never have before, but I do respect that's probably the right way to do many of these things...
    Currently I have SBS 2008 (Windows Server 2008 R2, Exchange Server 2007, WSUS 3, all with latest SP's, also includes SharePoint and other stuff, but I don't really care about most of it) on a single 8GB consumer grade system, which functions as a file
    server and Exchange server. We use Redirected Folders and Offline files for all users, which works great for us and provides additional file redundancy (if server goes down, all of each user's files are also on their own machine and they can even continue
    to work just fine w/o the server, losing only ability to send and receive e-mail). It has been sufficient, but I want to upgrade our version of Exchange and I am nervous that if that current one server fails, it would take me a long time to restore everything
    from backup, easily many days, especially if I need to buy any replacement hardware. It is RAID1, so a single drive failure is easy to handle, but that's the only hardware redundancy for the current server.
    New Plan:
    Install Windows Server 2012 R2 Standard on a new modest machine (16GBR RAM, Core i7, 1TB RAID1 (may upgrade to 3 or 4 TB), 256 GB SSD boot drive, this had been my old personal computer)
    Join that new server to the existing SBS domain (2008 R2/Exchange 2007), make it a DC, sync the users, etc.
    Install Windows Server 2012 R2 Standard on a wimpy computer (4GB RAM Core i3 processor), leave it as a member server
    Install Exchange Server 2013 on the wimpy new 2012 R2 Server (and nothing else, this will be dedicated to Exchange to make the most of such a wimpy machine)
    Migrate the existing Exchange data from the old SBS Exchange 2007 server and account info to the new server
    (or should I just create new accounts and copy the data from the user end through Outlook -- is that safer and cleaner than attempting any kind of server-level Exchange data migration?)
    Demote the old SBS Server and promote the new 16GB server to primary DC. Now it's OK to take the old SBS server off the network.
    Reformat the old SBS server and install Windows Server 2012 R2 on it too, and join it to the domain as a second DC (and possibly DCPROMO it to be the main server)
    Install Exchange Server 2013 in a VM on the reformatted 2012 R2 Server box (so second instance on the domain for Exchange redundancy) and set it up to sync with the first Exchange Server 2013 via DAG OR set up another physical wimpy member server and install
    it there. In any case, do NOT install Exchange directly on either DC.
    Set up DFS Replication or a Failover Cluster (still need to research this, but I had planned on DFS, thinking Cluster required shared drive, but Ed corrected me on this) between the two DC's for redirected files and keep all my user data folders between
    the two servers. We don't need automatic failover, like with a cluster, a manual switch would be acceptable, but if no additional cost or risk to clustering the two DC's, then the auto-failover protection that provides would be better than DFS.
    I think this incorporates all of your points, Ed. Does this sound right now? What's your advice on #5 (how to best migrate user data)?
    Thanks so much for all your help,
    Colin

  • Microsoft Exchange Server 2007 and iCal

    So at my new job they use Exchange Server 2007 for mail and calendars, and supposedly I should be able to view other people's calendars, but I can't find any way to do this in iCal.
    Do I have to install Entourage, or is there some other way to do this?

    Hello,
    I finally found the response : Grid control 11g cannot monitor Exchange Server 2007 or 2010 because they don't support WMI. The plugin uses WMI to connect to Exchange Server.
    Oracle have to create a new plugin based on PowerShell.
    Thanks Dominik.
    Edited by: Dominik on 19 nov. 2010 07:14

Maybe you are looking for

  • Subcontract Process with vendor supplied component

    Hi, We have a subcontracting process, when we send 3 components to the vendor, the vendor apply another component and return the semi finished to me. I have a BOM of this semi finished Good that includes all the 4 components. We sent the 3 components

  • Who left a file open?

    We have an Acrobat form posted at a shared server that must be viewed, stamped, then re-saved by a large number of people. This works fine until someone leaves the file open. Is there a way we can we learn who has the file open? Thanks in advance for

  • Receiving a fax on a shared voice/fax/answering machine configuration

    I have changed my phone service to Uverse and I no longer have a unique incoming fax number.  I share the same number with my incoming/outgoing voice and fax.  The "answering machine" is built into my service with AT&T.  I can send a fax without a pr

  • Between dates problem

    Hi everyone, We are trying to get a SQL sentence for our data model, and we have 2 date parameters like "dd-MM-yyyy". When we put them inside our SQL query, we have seen that it takes the date like "dd-MM-yyyy HH24:mi:ss", and the HH24:mi gets the va

  • Error   (0xE8000084) can you help?

    HELP!!  My ipad is showing that it is disabled and to connect to itunes.  It is saying that I have not entered a correct Passcode too many times.  I have followed the instructions in Itunes but does not work.  I have an unknown error (0xE8000084)  Ca