Exchange 2010 Std. on Esxi 5.0 (suggestions for deployment)

Dear Experts,
Soon we will be starting process of moving from E2k3 to E2k10 and it is going to be on Esxi 5.0. In this regard, I have concerns are there some guidelines to follow for it exchange 2010 virtualization?
- How much size HDD when server holding , HUB, CAS and mailbox role?
- The above three roles on one virtual server are OK?
- Memory assignment for the virtual server
- The exchange DB should be where, on a RDM or as a second HDD to the virtual machine like a D:\ drive
- Edge transport should be on seperate virtual server?
- Backup is possible of exchange DB is on a RDM ?
Any other aspects since it is first time for us going for Exchange virtualization. I found vmware document for this E2k10, but any resource with easy understanding steps and to follow.
If more details are needed from my side, please let me know
Appreciate your responses for this.
Regards,

Hi Wajeeh,
Glad to see you're going down the path to virtualize Exchange 2010 on vSphere.  You'll find that VMware has a ton of great resources to help you on this journey right here:  http://www.vmware.com/go/exchange
It's very difficult to answer your questions without some context about your environment.  When it comes to Exchange 2010 there really are no "generic" sizing guidelines.  For example, there really isn't any rule of thumb to say that for 5,000 users you need xx amount of vCPU and yy amount of memory per server.  You'll need to do some math from your environment to figure that out.
Thankfully Microsoft provides all of the numbers you'll need to figure out how much CPU and memory you'll need to size your servers.  This link does a good job of taking you through some of the math you'll need to understand:
http://technet.microsoft.com/en-us/library/ee712771.aspx
In addition, Microsoft makes a calculator that you can use to plug in your requirements and it will produce the required amount of CPU and memory for your Exchange environment.  Take a look here:
http://blogs.technet.com/b/exchange/archive/2009/11/09/3408737.aspx
To answer your other questions:
- Yes, you can combine the Hub Transport, Client Access, and Mailbox Server roles on the same virtual machine.  You'll need to size for it so that you can ensure proper performance.  See here for more info: http://technet.microsoft.com/en-us/library/dd298121.aspx
- The Exchange databases can either be on an RDM or on a VMDK attached to the virtual machine.  It comes down to your requirements and if you're using a SAN based snapshot, backup, or replication tool. If you're not then I would stick wtih VMDK files.
- The Edge Transport server is designed to be at the network perimeter and not joined to your domain.  You cannot combine it with other Exchange roles so you'll need to deploy it on a separate virtual machine.
I hope this helps.  Read the Microsoft links to get an idea of how to size your environment based on your organization's requirements and that should give you a good start.
Matt
http://www.thelowercasew.com

Similar Messages

  • Migrating Exchange 2007 to Exchange 2010 at a different physical location - Suggestions??

    Hello! I have a domain in Canada that is running Exchange 2007. My company wants to consolidate this Exchange and migrate the mail to the USA based Exchange 2010 in NYC. Not only is it migrating from 2007 to 2010, it's also moving locations physically. 
    Does anyone have any thoughts on how to best approach such a situation?

    ok... in addition to sarvesh comments i would also add a checklist based approach .. please follow below link
    http://blogs.technet.com/b/mspfe/archive/2014/03/20/checklist-upgrading-to-exchange-2010-from-exchange-2007.aspx  this would help you not to miss anything in terms to critical or non-critical aspects.
    after checklist i would suggest you give a shot at exchange server deployment assistant which will help you putting your scenario and suggesting the best practices. http://technet.microsoft.com/en-us/office/dn756393.aspx
    this guide for planning of migrations also shows the full scenario step by step : http://exchangeserverpro.com/wp-content/uploads/Exchange%20Server%202007%20to%202010%20Migration%20Guide%20V1.0%20-%20Planning%20Chapter.pdf
    this is also a step by step graphical representation for the process. THIRD PARTY LINK though.. http://www.petenetlive.com/KB/Article/0000236.htm
    Let me know if this helps.
    MARK AS USEFUL/ANSWER IF IT DID
    Thanks
    Happiness Always
    Jatin

  • Exchange 2010 - Error setting a new transport rule for email disclaimer

    Hi
    Trying to setup some additional email disclaimer rules on Hub transport under Org Config on exchange 2010. We allready have a few and they work ok, however we are trying to replace this woth some alternate ones and are getting the error
    The length of the property is too long. the maximum length is 8192 and the length of the value provided is 8522.
    Most of this length comes from the html code we are inserting into the disclaimer. I've reduced it by about as much as i can but it's still too large. Does anybody have any suggestions or know if it;s possible to increase the 8192 sixze limit ?
    Regards
    Roger

    Hi Roger,
    For AD replication packet the ideal size is 8K. Or the above error may occur due to build/design issues.
    You can eliminate this size related issue by splitting the large rule into multiple rules. This size limit is Per Rule and does not add up for all rules. 

  • Exchange 2010 Sharing a calendar using OWA prompts for Credentials

    Hi,
    We have a mixed Exchange 2003/Exchange 2010 environment while we migrate our mailboxes over to Exchange 2010.
    We use code that is used to connect to meeting room calendars still on Exchange 2003and then display the information on big tv screen at the entrance to the building.
    An example of the code is:
    R1calURL = "http://www.msexchange.org/articles-tutorials/exchange-server-2010/management-administration/managing-internet-calendar-sharing-exchange-server-2010-service-pack-1-part1.html to
    try and get it working.
    The code then gets various other pieces of information from the calendar which is used to display the correct information.
    I have a couple of questions:
    1) Is this method still valid or should we be using a different way of acheiving this (EWS or Internet Calendar Sharing?)
    2) We use forms based authentication for OWA.  I have had a look at Internet Calendar Sharing but when I enter the URL for the shared mailbox I am always being asked to enter credentials.  I have configured the mailbox I am connecting to so default
    has reviewer and anonymous has reviewer permissions.  I have also configured the OWA external URL the same as the Internal URL and created a new anonymous sharing policy in the EMC and applied this to the shared mailbox.  I used the following link
    http://www.msexchange.org/articles-tutorials/exchange-server-2010/management-administration/managing-internet-calendar-sharing-exchange-server-2010-service-pack-1-part1.html to try and get it working.
    Any help would be greatly appreciated.
    Matt

    Hi Matt,
    If the shared calendar is opened from OWA directly from a URL, please configure the Outlook Web App virtual directory to use Integrated Windows authentication. Integrated Windows authentication lets users who've already logged on by using
    their Active Directory account use Outlook Web App without having to enter their credentials again. For more information about it, please refer to:
    http://technet.microsoft.com/en-us/library/bb232199(v=exchg.141).aspx
    To configure it, please do the following steps:
    1. Open EMC, expand Microsoft Exchange On-Premises (<ServerName>).
    2. Expand Server Configuration, and click on
    Client Access.
    3. Select the desired Client Access server on the right panel, and double click on
    owa (Default Web Site) on the Outlook Web App tab.
    4. In Authentication tab, select Use one or more standard authentication methods and check Integrated Windows authentication.
    5. Click Apply.
    Please note the warning to restart IIS service and change the corresponding configuration for ECP virtual directory in the same web site.
    Regards,
    Winnie Liang
    TechNet Community Support

  • Exchange 2010 SP3 upgrade fails at stopping services for Management tools station

    Attempting to upgrade a Windows 7 SP1 64bit virtual machine from Exchange 2010 SP2 management tools to SP3 fails with the following error:
    Summary: 11 item(s). 1 succeeded, 1 failed.
    Elapsed time: 00:15:19
    Preparing Setup
    Completed
    Elapsed Time: 00:00:00
    Stopping Services
    Failed
    Error:
    The following error was generated when "$error.Clear();
              & $RoleBinPath\ServiceControl.ps1 -Operation:DisableServices -Roles:($RoleRoles.Replace('Role','').Split(',')) -SetupScriptsDirectory:$RoleBinPath;
              & $RoleBinPath\ServiceControl.ps1 Stop $RoleRoles.Replace('Role','').Split(',')
            " was run: "Service 'NetBT' failed to reach status 'Stopped' on this server.".
    Service 'NetBT' failed to reach status 'Stopped' on this server.
    Click here for help...
    http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.123.3&e=ms.exch.err.Ex88D115&l=0&cl=cp
    Elapsed Time: 00:15:19
    Here is the powershell execute policy:
    PS C:\> Get-ExecutionPolicy -list
    Scope                                            
    ExecutionPolicy
    MachinePolicy                                               
    Unrestricted
    UserPolicy                                               
    Unrestricted
    Process                                                  
    Undefined
    CurrentUser                                               
    RemoteSigned
    LocalMachine                                               
    RemoteSigned

    Hi Bad Dos,
    Any updates?
    You can also try to uninstall sp2 Management Tool first, then install SP3 directly. 
    Frank Wang
    TechNet Community Support

  • Internal outlook client connectivity in exchange 2010 when coexist with exchange 2013

    Hi all ,
    on my side i would like to clarify few queries.
    Say for instance i am coexisting exchange 2010 with exchange 2013 .Unfortunately if all of my exchange 2013 servers goes down .
    Q1 .On that time will the internal outlook users having their mailboxes on exchange 2010 can be able to connect mailboxes without any issues ? In case if they face any issues what kind of issues will they be? Because why i am asking is we should have pointed
    the autodiscover service to exchange 2013 during coexistence.
    When an user closes and reopens the outlook after whole exchange 2013 environment failure ,outlook will first query the autodiscover service for the profile changes to get it updated on users outlook profile.In such case autodiscover service will not be
    reachable and i wanted to know will that affects the internal client connectivity for outlook users having their mailboxes on exchange 2010.
    Q2. Apart from outlook internal users connectivity ,what kind of exchange services(i.e owa,active sync,pop,external OA and imap) will get affected when whole exchange 2013 environment goes down during coexistence ?
    I have read the below mentioned statement on this awesome blog but still i wanted to clarify with you all on my scenario.
    http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx<o:p></o:p>
    Internal Outlook Connectivity
    For internal Outlook clients using RPC/TCP connectivity whose mailboxes exist on Exchange 2010, they will still connect to the Exchange 2010 RPC Client Access array endpoint.
    For internal Outlook clients using RPC/TCP connectivity whose mailboxes exist on Exchange 2007, they will still connect directly to the Exchange 2007 Mailbox server instance hosting the mailbox.
    Please share me your suggestions and that would help me a lot .
    Regards
    S.Nithyanandham

    Hi Winnie Liang ,
    Thanks a lot for your reply.
    Scenario  1 : for internal outlook connectivity 
    We have below settings for exchange 2010 autodiscover.
    mail.domain.com - will be the namespace for internal autodiscover URI for all the exchange 2010 cas serves
    We are going to have below settings for exchange 2013 autodiscover.
    mail.domain.com - will be the namespace for internal autodiscover URI for all the exchange 2013 cas serves
    During coexistence mail.domain.com will be pointed to exchange 2013 cas servers . I mean to say if we try to resolve the mail.domain.com it will get resolved in to the exchange 2013 cas servers.
    So on such case if anything happened wrong to the new environment or else if entire environment goes down .Do we face any issues while outlook users connect to existing mailboxes in exchange 2010 ?
    Because why i am asking is ,on the below mentioned article i have read all the autodiscover request will go via exchange 2013 cas servers during coexistence.That means all the existing mailboxes in exchange 2010 will also have to query exchange 2013 cas
    servers for autodiscover request.During the whole exchange 2013 environemnt failure whenever the user tries to close and open outlook .Outlook will first queries the autodiscover service for any changes happened on that particular mailbox and it will try to
    get it updated on user profile.
    http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
    Would it be possible to make the exchange 2010 mailbox users to query only the scp points which belongs to the exchange 2010 cas servers for autodiscover request ?
    Scenario 2: For exchange services
    mail.domain.com - will be the namespace for all the exchange 2010 services (i.e owa,activesync,external outlook anywhere,pop,imap)
    mail.domain.com - will be the namespace for all the exchange 2013 services (i.e owa,activesync,external outlook anywhere,pop,imap)
    What about the above services will it get affected during whole exchange 2013 environment failure ?
    Note : We are not facing this issue , i hope everything goes well in my environment while doing coexistence i am just asking this question on my own interest?
    Regards
    S.Nithyanandham
    Thanks S.Nithyanandham

  • Exchange 2010 coexist with exchange 2013

    Hi All ,
    Planning to have a coexistence scenario in my environment which is mentioned below
    Exchange 2010 - ambiguous url in place - OA enabled 
    For mapi/rpc traffic - mail.domain.in -  exchange 2010
    For https traffic - mail.domain.in - exchange 2010
    mail.domain.in will get resolved in to cas array in exchange 2010 .
    After coexistence On our side we are not going to move the mail.domain.in namespace to exchange 2013 , Instead of that we are going to use a new namespace in exchange 2013 for internal outlook anywhere and it will be outlookmail.domain.in and for the remaining
    exchange 2013 services like pop,imap,owa,active sync url's,external OA will be having mail.domain.in as same as exchange 2010 namespace.
    just consider outlookmail.domain.in is available on the san certificate installed in exchange 2013.
    Note : 
    On my ide I would assume Internal outlook 2010 mapi users will connect directly to exchange 2010 servers on the namespace mail.domain.in
    Likewise i would assume Internal outlook anywhere 2013 users will connect directly to exchange 2013 servers on the namespace outlookmail.domain.in
    Services like pop,imap,owa,active sync ,external OA connections for both exchange 2010 and exchange 2013 from the external world will be routed from firewall to exchange 2013 servers .Then https traffic for exchange 2010 mailbox users will be proxied to 2010
    exchange server via exchange 2013 server.
    question : I would like to know above mentioned scenario is possible or not ?
    On my side I know in my environment i am having ambiguous url's in place and at the same time i don't want the exchange 2010 internal outlook users to connect via exchange 2013 rpc over http even though OA is enabled on exchange 2010.
    So simply i can say i need my internal exchange 2010 mailbox users has to connect via tcp/ip.
    All of you tell me your valuable suggestions.
    Regards
    S.Nithyanandham

    Hi,
    Going Straight to the point... and answering your question...
    The scenario above IS possible For a while... But going ahead in the migration process, You'd face problems once the Exch2013 doesn't know how to handle MAPI connections:
    As per Exchange Team...
    In this scenario where both the MAPI/RPC and HTTP workloads are using the same FQDN you cannot successfully move the FQDN to CAS 2013 without
    breaking your MAPI/RPC client connectivity entirely. I repeat, your MAPI/RPC clients will start failing to connect via MAPI/RPC once
    their DNS cache expires after the shared FQDN is moved to CAS 2013.
    As their recommendation, and I would tell you too by experience, the best option is to really use different internal and external URLs for the clients to connect to.
    change your design to use a specific internal-only FQDN for MAPI/RPC clients. If you are in the middle of a 2010 deployment using an Ambiguous
    URL I recommend you change your ClientAccessArray FQDN to a unique name and update the mailbox database RpcClientAccessServer values
    on all Exchange 2010 mailbox databases accordingly. Fixing this item mid-migration to Exchange 2010 or even in your fully migrated environment will ensure any newly created or manually repaired Outlook profiles are protected, but it will not automatically
    fix existing Outlook clients with the old value in the server field. 
    So the overall for this first point is to enable the OA for all internal users, so as to ease the migration process in the future, even if for the time being its not necessary.
    Also another point you should take into consideration is the version of yours OLK versions, as the minimum supported are as per below:
    Outlook 2007: 12.0.6665.5000 (SP3 + the November 2012 Public Update or any later PU)
    Outlook 2010: 14.0.6126.5000 (SP1 + the November 2012 Public Update or any later PU)
    Outlook 2013: 15.0.4420.1017 (RTM or later)
    I don't know the size of you network, but it might be necessary for you to use an inventory tool in order to identify that.
    As advised, its really worthy to have a look at the following article, thus to clarify your view about this issue.
    Ambiguous URLs and their effect on Exchange 2010 to Exchange 2013 Migrations
    From <http://blogs.technet.com/b/exchange/archive/2013/07/17/3574451.aspx> 
    Hope it can help you!
    Cheers,
    Think before you ask, give detail as much as possible, then ask and you will get help! Always have in mind, people do not guess! :)

  • Exchange 2010 to office 365 migration lab

    I am looking out for free migration lab if any available online from Microsoft or any vendor related to migrate from exchange 2010 to office 365 . Please suggest ? 
    Aditya Mediratta

    Hi,
    Unfortunately, there’s no related lab for use.
    We can Microsoft Exchange Server Deployment Assistant to generates a custom step-by-step checklist that will help you deploy different versions of Exchange Server for different types of scenarios. For your reference:
    https://technet.microsoft.com/en-us/office/dn756393.aspx
    Thanks
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Allen Wang
    TechNet Community Support

  • Outlook 2010 "The server is unavailable" using smart card Exchange 2010

    I have a XenApp 6.5 environment, that uses smart card authenication for login. All the office applications will open except for outlook. Outlook opens up and shows a prompt saying "Connecting" ...."Then server is unavailable".
    If I removed the smart card authenication from the XenApp environment, User are able to open Outlook with no problem.
    My question, is there something with exchange 2010 that needs to be turned on for smart card authenication?

    Hi,
    I suggest you remove any existing certificate-based credentials from the Credential Manager and use the
    EnableSmartCard registry setting to check the result. The Outlook client may not be properly configured to work with saved smart card credentials.
    Important
    Follow the steps in this section carefully. Serious problems might occur if you modify the registry incorrectly. Before you modify it,
    back up the registry for restoration in
    case problems occur.
    Remove existing certificate based credentials
    The first step to prevent a PIN lockout is to delete any existing certificate based credentials that were saved by Outlook.
    Open Control Panel.
    Double-click Credential Manager.
    See whether there is a Certificate-Based credential similar to the following:
    @@BSUgiZQZ54Pf6cEtxKflWHH
    Also, see whether there is a Generic credential similar to one of the following:
    MS.Outlook.14:[email protected]:PUT
    MS.Outlook.15:[email protected]:PUT
    Note 14 indicates Outlook 2010 saved the credential and 15 indicates Outlook 2013.
    If these are both present and were created or changed at the same time, they are likely smart card credentials saved from Outlook. Click the first credential to expand it and to show the details. Then, click Remove to delete the
    credential from Credential Manager.
    Repeat step 4 for each one of the credentials listed in step 3.
    When you are finished, close Credential Manager.
    Configure the EnableSmartCard registry setting
    The second step to prevent a PIN lockout is to create the EnableSmartCard registry setting.
    Outlook 2010
    For Outlook 2010, the EnableSmartCard registry setting was introduced with the Microsoft Outlook 2010 hotfix package dated December 13, 2011 (KB2597028). We recommend that you install the most recent build of Outlook 2010. For more information
    about the latest applicable updates for Outlook, click the following article number to view the article in the Microsoft Knowledge Base:
    2625547 How to install the latest applicable updates for Microsoft Outlook (US English only)
    To create the EnableSmartCard registry value, follow these steps:
    Exit Outlook.
    Start Registry Editor.
    Create the following registry values at the specified locations:
    Note Manually create any registry keys or values if they do not exist.
    Key: HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\RPC
    DWORD: EnableSmartCard
    Value: 1
    Exit Registry Editor.
    For this question, if you need to get more information about Exchange 2010, I suggest you post the question in Exchange forum:
    https://social.technet.microsoft.com/Forums/exchange/en-US/home?category=exchangeserver
    Regards,
    Melon Chen
    TechNet Community Support
    It's recommended to download and install
    Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
    programs.

  • Install a temporary Exchange 2010 in an existing environment

    I have an existing production environment with 3 Exchange 2010 servers in a DAG configuration working well.I would now like to verify the backups by restoring databases to a new Exchange 2010 server which I will only keep for a limited time.When installing Exchange 2010 I get "You must be member of the 'Organization Management' role group or 'Enterprise Admin' to continue"I assume this is because I need some specific permissions in Active Directory I don't normally have. I could very well use a different account which I'm fairly sure has these permissions, but I want to make sure I'm not introducing instability in our production environment by adding a fourth Exchange 2010 server which will then be deleted again.I have no intention of configuring the fourth server as a DAG member, but I'm not really an Exchange person and I'm looking...
    This topic first appeared in the Spiceworks Community

    Hi FriendzKnight
    II,
    Try to perform exchange 2010 recovery using the recovery switch. Build new exchange 2010 server and restore the exchange 2010 from the backup using recovery switch.
    This will work to get back exchange 2010 in your existing exchange 2013 enivornment
    Exchange Queries

  • Exchange 2010 : Doubt with recipient type and problem with disappearance of the original recipient in the mail relay

    Hello. First of all, thank you very much for your attention.
    After that, I will expose the problem:
    I have a user domain called "comercial" with a corresponding mailbox "[email protected]"
    . This user
    has assigned multiple emails such as "[email protected]", "[email protected]", "[email protected]" , having as default   email "[email protected] ".
    On
    the other hand,
    another domain user
    called
    "menganito" with it's mailbox  "[email protected]" account, also has a few mail accounts "[email protected]", "[email protected]", " [email protected]"
    ...having
    as default   email "[email protected]
    The user "Comercial" is forwarding
    all of it's mails to the user "menganito".
    The problem is that "menganito" is not receiving the exact
    "comercial"
    sender email, but the email which appears by default ("[email protected]").
    "Menganito" would like to know
    from which email exactly the mails he is receiving have been sent ("[email protected]",
    or "[email protected]"
    or "[email protected]"). 
    Also, he would like to knowthe email of the original sender (from the outside of the domain) whom the user "Comercial"
    have received the email from.
    In another type of email servers (Kerio,...)
    this is not a problem, because forwarding by
    defaultis always showing
    the original sender and original receiver.
    Maybe the problem comes from the recipient type I'm using.
    Should I use another type of recipient? should I use a transport rule?
    Any idea ? Thanks again in advance.

    Hi Simon. First of all thanks for your answer.
    This happens with all accounts. I tried with news accounts and different browsers for OWA and Outlook anywhere and happens the same. Is not a cache problem
    The problem is
    when "[email protected]"(default
    and set as default answer
    account by
    exchange)
    receives
    a message in  "[email protected]" when
    forwards to "Menganito"
    this message will appear from"[email protected]"
    instead of "[email protected]".
    This happens with all accounts.
    I can understand that i can't avoid
    default reply address on the same
    domain, but also with different domains happens
    the same?
    The platform is only one clean and updated server 2012 as dc and another clean and updated server 2012 with exchange 2010 sp3 directly and after rollup 4 for exchange SP3, no previous versions and servicepacks of exchange 2010 was installed before. Before
    install exchange 2010 sp3, i installed all the filterpacks (3) and .net 3.5 and all updates that i finded for 2012 server (i tried for 2 days): No more updates for sure.  After, in powershell, i put this:
    Add-WindowsFeature NET-Framework-Core,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,Web-Mgmt-Tools,Web-ISAPI-Ext,Web-Digest-Auth,Web-Dyn-Compression,NET-HTTP-Activation,Web-Asp-Net,Web-Client-Auth,Web-Dir-Browsing,Web-Http-Errors,Web-Http-Logging,Web-Http-Redirect,Web-Http-Tracing,Web-ISAPI-Filter,Web-Request-Monitor,Web-Static-Content,Web-WMI,RPC-Over-HTTP-Proxy
    -Restart
    The machine and exchange works good (i3 with 4gb ram, and raid 1 1tb of HD) and the organization only has 15 mailboxes. No problems with even viewer and all is correct.
    Thanks again.

  • Exchange 2010 - Method to send e-mail when the WAN IP is dynamic

    Hello,
    I am writing due to the fact that I cannot send e-mail from my Exchange 2010 Server to my Yahoo! address for testing. When trying to do so, I get the following error message:
    mta1106.mail.gq1.yahoo.com gave this error:
    Mail from xxx.xxx.xxx.xxx not allowed - 5.7.1 [BL21] Connections not accepted from IP addresses on Spamhaus PBL; see
    http://postmaster.yahoo.com/errors/550-bl21.html [550]
    As one can see, because my IP address is residential, I cannot send e-mail to all addresses on the web. I really would like to use this as my primary contact, and thought of using a proxy. Can someone recommend a good proxy, or workaround for this? I am
    sorry for posting in Exchange 2013, but I couldn't find the 2010 forum. Thank you to all who reply.
    Mike

    Thank you for your reply,
    I have set up DynDNS, and I am currently using my own domain name. The problem was I needed to configure a smart SMTP host, or relay server on my send connector. I decided to go with SMTP2GO, as they are cheap, and allow you to send 20 e-mails a day for
    free. When the money is right, I plan to upgrade.
    Thank you for your help.
    Mike

  • Exchange 2007 and exchange 2010 Federation

    Hi all I am trying to federate between Three organisations
    org A exchange 2007 with exchange 2010 cas
    org B exchange 2010.
    org C exchange 2010.
    I cannot share my calendar from org A to Org B
    I can share Org B to Org A and Org B to Org C.
    when I try from Org A to Org B or Org C
    When I try to share free/busy fro the exchange 2007 with exchange 2010 cas. The user gets an error
    "calendar sharing is not available with the following entries because of permission settings on your network."
    -availabilityaddressspace. Autodiscover works TXT works. I have added a user from Org B as a contact in exchange.
    The exchange 2010 server is not the CAS server for the exchange environment and I is not a proxy for exchange 2007. Is this where I am failing ?
    Heeeelp

    Hi Nigel,
    How is the impact, just one user or all users, Outlook or OWA?
    If just one user, it seems like an issue on the Outlook Client side.
    Please trying to re-create new profile to fresh the caches.
    Please runing Outlook under safe mode to avoid some AVs, add-ins and firewall.
    Found a similar thread for your reference:
    Calendar Sharing not available error message
    http://social.technet.microsoft.com/Forums/exchange/en-US/d9b33281-d7bb-4608-8025-16fb26643d0d/calendar-sharing-not-available-error-message?forum=exchangesvrclientslegacy
    Hope it is helpful
    Thanks
    Mavis
    Mavis Huang
    TechNet Community Support

  • Forefront protection for exchange 2010 - updates?

    Installed Exchange EDGE server with Forefront Protection for Exchange 2010.
    Installed hotfix update rollup 4 for forefront (I think it's the latest because I haven't found any newer).
    We have basically left everything on default in forefront, and if we take a look on dashboard in gui we see this error message:
    not all the antimalware engines selected in the forefront adminstration console for scanning have been enabled for updates.
    where should we take a look whats not being updated. Please a little help.
    with best regards,
    bostjanc

    Hi.
    Meanwhile I have also found information that it has been retired
    https://social.technet.microsoft.com/Forums/forefront/en-US/400fa485-edc9-499f-8294-c196496437d8/not-all-of-the-antimalware-engines-enabled-for-updates-successfully-updated-at-the-last-attempt?forum=FSENext
    bostjanc

  • Exchange 2010 Service Pack 1 and Unity 7.0(2)

    We are in the process of migrating from Exchange 2003 to Exchange 2010. We had everything working with 2010, but wanted to install SP1 prior to migrating users over to the new Exchange server.
    After installing SP1, messages are no longer being transfered to the Exchange server. We've re-run the permissions wizard, thinking that the update may have undone some permission setting. This succeeded, but we still get nothing.
    Has anyone else installed SP1 for Exchange 2010? If so, any issues?

    For those with Unity 7.0(2) integration with Exchange 2010, please refer to this defect CSCti70702 and you may find your answer to the multiple issues you are experienced. It has to do with MS/CDO library.
    https://supportforums.cisco.com/docs/DOC-12848
    http://support.microsoft.com/kb/2405611

Maybe you are looking for