Migrating from 2010 windows nlb cas array to exchange 2013 using netscaler for HLB

i currently have exchange 2010 sp3 setup as follows
2 cas/ht using windows nlb for array.internal.com as the nlb name
2 mailbox servers using 1 dag for replication between them.
I would like to stand up 2 new CAS 2013 sp1 servers(2012 r2) and use our netscaler hlb to load balance and do ssl offloading.
id like to use the hlb to load balance and ssl offload all possible traffic not just owa, i.e. activesync etc.
the netscaler is running version 10.5.
does anyone have any thoughts on how to perform such a migration?
id like to make this as seamless as possible for the user, so no owa name change or anything like that.
thx in advance for any help.

Exchange 2013 CAS cannot be managed effectively without an Exchange 2013 mailbox server since the CAS won't run the Exchange 2013 management tools without it.  Your Exchange 2013 servers should simply have both roles.  There are few cases where
splitting the roles has any business value.
If what you're planning to do is within the same forest and organization, then it's a "transition", not a "migration".  What you are asking to do is easy.  Build the Exchange 2013 servers, configure load balancing, test
access, and then switch the DNS records to point to them.
Personally, I would skip the SSL offloading.  It's my opinion that it makes the solution more difficult to troubleshoot without providing any real benefit.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Similar Messages

  • Exchange 2010 CAS array with Exchange 2013 Mailbox Servers

    Here is our current scenario,
    Exchange 2007
    2 - Hub Transport Servers
    2 - CAS servers (cluster NLB)
    2 - Mailbox servers (clustered)
    Exchange 2010
    2 - Huib Transport Servers
    3 - CAS servers (array NLB)
    2 - Mailbox servers (1 DAG)
    We have not migrated any users to the Exchange 2010 environment yet. We're thinking that at this point we would rather go from 2007 to 2013. Does the 2013 mailbox server work with a 2010 CAS array?

    Hi,
    As far as I know, CAS array doesn' t exist in Exchange 2013. And OWA and other requests can be proxyed and redirected from Exchange 2013 to Exchange 2010.
    For more information, you can refer to the following article:
    http://blogs.technet.com/b/exchange/archive/2013/01/25/exchange-2013-client-access-server-role.aspx
    Thanks,
    Angela Shi
    TechNet Community Support

  • Exchange server name not changing in mail profile after migration from 2010 to 2013

    Following a migration from 2010 to 2013 we are finding that for a number of users the old exchange server address stays in the mail profile (control panel -> mail -> e-mail accounts) which causes Outlook not to load.
    We are able to go into control panel -> mail -> e-mail accounts and change this manually to the new exchange 2013 server address but we have quite a number of users and don't really want to do it manually.
    Shouldn't it be updating automatically and if so why is it?

    Hi,
    Yes, it should be changed by autodiscover. Does this issue occur to all the migrated users?
    I have seen this kind of issues before when migrating from Exchange 2003/2007 to Exchange 2010. The most efficient way is to rebuild the Outlook profile.
    Thanks,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Simon Wu
    TechNet Community Support

  • Issue with Excel Access Web Part, with sites that were migrated from 2010 SP to 2013 SP

    Hello, 
    If I try to add an Excel Access Web Part to a page I get the following:
    **Note: This only happens with sites that were migrated from 2010 SharePoint to SharePoint 2013. If I create a new site the feature works like it should and loads the workbook. I've tested this on several sites, our environment is enterprise as well. Being
    that the majority of our sites were migrated from 2010, I need this to work! 

    Can you try below fix and let me know
    http://blogs.technet.com/b/excel_services__powerpivot_for_sharepoint_support_blog/archive/2013/05/21/excel-services-the-workbook-cannot-be-opened.aspx

  • Migration from 2010 to Office 365

    I'm stumped on Office 365 Small Business Premium and the migration from 2010.
    I thought that migration would be simple but I can't find any tools mentioned in the articles I read. I thought that it was supposed to be a tool found within 365 where you pull the info from the PST you keep on your desktop.
    Do I need to uninstall 2010 and only use the 365 web based email. IF I can keep both, do they sync? Does this sync with the mobile app also?
    So right now I have both installed and the users setup for 365 (the login accounts), but I don't have any thing else setup because I don't want to lose any data. I want to make sure that I do this right before I go any further.
    No I don't have exchange. Every thing is hosted by Network Solutions and we use pop3 to pull the email.

    Hi,
    some options/suggestions are here:
    http://community.office365.com/en-us/f/158/p/230137/714965.aspx?ss=87fa5dc5-cfde-49c9-ab80-294fc73ccb85#714965
    http://community.office365.com/en-us/p/helpcenter.aspx?hcs=8b0e9324-aae1-4a96-a035-619cabe78397#ESKU-Admin-Mail
    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)
    OK. I downloaded those files and they didn't do me any good. The one which would run was asking for a central computer, I'm assuming an email server, which we don't use.
    We use pop3 through Network Solutions. We have Outlook on each desktop and the folders are local.
    I am reading up on some other stuff on migration. I'll let  you know how it goes.

  • Custom Auto Attendant Prompts through TUI not working for users who migrated from 2010 to 2013

    In Exchange 2010, we started using unified messaging and set up Auto Attendants. We setup a admin role/RBAC for people of a security group to be able to update the message on the auto attendants. They have the UMPrompts assigned role. All of this is working
    great in 2010. We have now migrated to 2013, and the users who were migrated from 2010 to 2013 can no longer update the messages through TUI. Newly created 2013 users can and are assigned the EXASCT same permission as the users who have been doing this for
    well over a year on 2010.  When they call the AA and press #,* they are asked to provide their extension, after doing so the system tells them that extension is not correct. and asks for the extension again.  Newly created users with the same permissions
    get prompted for their PIN and can log in and change the message just fine. 
    Confirmed Bug?  anybody else having this issue?
    What would be different for this process between a user who was migrated from a previous version like 2010 compared to a newer user who has only ever existed on 2013?

    What if the migrated 2010 users are in the same DB as the system mailbox? I had a similar issue during a migration; http://www.skypeadmin.com/2014/11/10/known-issue-um-automated-attendant-tui-editing-broken-migration/
    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
    SWC Unified Communications
    This forum post is based upon my personal experience and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

  • Journaling mailbox - Exchange 2013 Migrations from 2010

    hi guys
    i am about to start mailbox movement from Exchange 2010 to 2013. my setup is working fine. i have enabled journaling from Exchange 2010 and as ii found, automatically journaling rules will be reflected to exchange 2013. i had very big journaling mailbox
    and then newly created New Exchange 2010 journaling mailbox. now new journaling mailbox is configured for journaling and that also still on 2010(both Old and new journaling mailbox ), new mailx is couple of weeks old (6-8 GB) and old one is 2.6 TB. So i will
    move old one at the end .
    my questions is if i move new journaling mailbox to 2013 before start normal Mailboxes, it will cause some issues for journaling. i use premium journaling . is it okay to move journaling mailbox at the begin ?? 
    thank you
    Indunil

    Hi,
    Based on my test, journal rules will be synchronized in Exchange 2013 after you create in Exchange 2010. If you create in Exchange 2013, then the rule will be synchronized in Exchange 2010.
    And I did create a rule to send message to a Exchange 2013 jounal mailbox for Exchange 2010 users. It worked.
    So you can migrate journal mailbox to Exchange 2013 firstly based on this test.
    Best regards,
    Belinda Ma
    TechNet Community Support

  • Users with mailboxes on exchange 2010 cant proxy to OWA on exchange 2013

    We are in the process of migrating from 2010 to 2013.  Users with mailboxes on exchange 2010 can't proxy to the owa on Exchange 2013 - there is no error - just receiving a message "Still working on it"
    alex serdyukov

    Hi Alex,
    As the above suggestion mentioned, you can try to upgrade the Exchange 2013 to CU8 and check if any helps:
    Cumulative Update 8 for Exchange Server 2013
    Best regards,
    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]
    Niko Cheng
    TechNet Community Support

  • Migrating from 2010 (single) to 2013 HA

    Hello All;
    I'm doing my long research into my new project and found a lot of helpful links but thought i'd reach out to the forum and see if anyone has any inside links, steps, details I can review.
    We currently are running
    Exchange 2010 SP3 (All roles on single server)
    Windows Server 2008R2 Enterprise
    Virtual Machine (VMware 5.5 ESXi)
    I'm planning on migrating to
    Exchange 2013 (two instances)
    High Availability 
    Windows Server 2012 R2 Enterprise
    So migrating from 1 single exchange 2010 server to multiple Exchange 2013 mailbox servers.  The goal is if 1 physical goes down for maintenance of anything else that can happen in this crazy world, the other separate server would still pass mail through
    the environment which I believe is separating the DAGs.
    I'm sure I've missed a lot here. Please Help because afterwards I have to upgrade from Lync 2010 to Lync 2013.

    thank you all for the helpful info & awesome links for reading.
    but i'm still a little lost in the HA capability of exchange 2013. We have two physical servers (built Raid 5 in the array for each - both having 2 arrays.)  How do we implement HA in this configuration if 1 server goes down ? Would that be separate
    DAGs with a 3rd front end ?
    example:
    Current
    Server 1 
    Exchange 2010 
    4 Databases 
    --- Migrate/Upgrade to
    Future
    Server 2                              Server3
    Exchange 2013                     Exchange 2013
    4 Databases  <------------>   4 Databases
    so if Server 2 disappeared, Server 3 could keep running transporting all mail. I'm assuming i'm missing the front end part of exchange 2013 that would pass the mail along to server 2 and server 3.
    I apoligize if this is noobish question; I've never implemented anything HA for exchange. We've always run all roles on a single instance.

  • Exchange 2013 Migration from 2010 Test (Shared split DNS)

    Hi
    Im testing a migration from Exchange 2010 to 2013. I have tried to run a single DNS name to both servers, so externally mail.test.com resolves to the external IP and that NAT's to the new Exchange 2013. Then internally mail.test.com resolves both to EXC13
    and EXC10 ip adresses (Round Robin).
    I have moved some mailboxes to 2013. If the IP resolves to the new Exchange and i try to login to a mailbox on the old server i get redirected as im supposed to. If the IP resolves to the old Exchange and i try to login with a mailbox on the new server i
    get:
    A server configuration change is temporarily preventing access to your account. Please close all Web browser windows and try again in a few minutes. If the problem continues, contact your helpdesk.
    Should this be possible, or do i need to change the intarnal URL on all virtual directories on the old server to the local netbios name or what to do?

    You should never use the server name in any of the URLs.  You should use either a CNAME or a load-balanced VIP with a generic name like mail.company.com or webmail.company.com.  Then you just point this name to the new server.  If
    you're currently using a server name, it's about time to change that first before trying to switch to Exchange 2013.
    Curently im using a generic name, mail.test.com. But that's just a normal A record on the internal DNS. So i cannot use that on both?

  • Web-part issue after migrating from 2010 to 2013

    Hello all
    Correct me if I am posting this question in the wrong section.
    The background is: Migrating and Upgrading SP2010 to SP2013. I did it, and alot of it works, as it should, though I have one issue.
    I did deploy all the solutions to both the 14 and 15 hive, and activated all the propper features. Now, I have one web-part which breaks down. It is a Web-part that communicate with a SAP endpoint, to retrive some data and show dem. The Web-part work fine in
    the 2010 environment.
    As soon as I enter the site where the Web-part is placed in, I am being redirected to the "Maintanence Web-part, error message". If I delete the Web-part I can access the site with no errors. The code works fine in 2010. 
    The error I am getting is "value cannot be null".
    Unexpected System.ArgumentNullException: Value cannot be null. Parameter name: uriString at System.Uri..ctor(String uriString) at Microsoft.SharePoint.SPSite..ctor(String requestUrl) at MyWebPart.Core.ListConfiguration.<>c__DisplayClass1.<GetKeyValue>b__0()
    at Microsoft.SharePoint.SPSecurity.<>c__DisplayClass5.<RunWithElevatedPrivileges>b__3() at Microsoft.SharePoint.Utilities.SecurityContext.RunAsProcess(CodeToRunElevated secureCode) at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(WaitCallback
    secureCode, Object param) at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(CodeToRunElevated secureCode) at MyWebPart.Core.ListConfiguration.GetKeyValue(String key) at MyWebPart.OrderCatalog.OrderCatalogUserControl.FillFilterBoxes() ... 438bb29c-c202-3049-9aab-e895c85176d5
    Unexpected ...at MyWebPart.OrderCatalog.OrderCatalogControl.Page_Load(Object sender, EventArgs e) at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.AddedControl(Control control, Int32 index) at MyWebPart.OrderCatalog.OrderCatalog.CreateChildControls()
    at System.Web.UI.Control.EnsureChildControls() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal()
    at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesB... 438bb29c-c202-3049-9aab-e895c85176d5
    Unexpected ...eforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) 438bb29c-c202-3049-9aab-e895c85176d5

    No, I did not migrate the content from 2010 web-config to the 2013 server. This is something I will take a look at, to see if there are some missing points in the config-file of 2013.
    And just to be sure, when we are talking about the config file, it is the one who is associated with the Web-applikation? So, IIS --> WebApp --> Explorer --> and that web.config?

  • Migrate from Zenworks Windows Policies to AD Group Policies

    Untill now we have been using Zenworks Windows policies to configure some settings.
    We have now migrated to an AD Domain and start to use Domain Group Policies.
    We have recreated a few policies in the AD, but they are not getting applied to our clients.
    What is the correct way to migrate from the one to the other?

    This is likely due to a VERY DUMB default IE GPO settings.
    By Default, IE GPO settings never reapply.
    Try changing your AD IE GPO to tell it to always apply the IE settings.
    See - http://www.novell.com/support/kb/doc.php?id=7008026
    On 2/27/2013 3:56 AM, Quinky wrote:
    >
    > Okay, I understand that.
    > I've disabled one policy and recreated it in AD.
    > But this policy does not get applied.
    > It's a policy that sets some IE settings (Only User configuration).
    > But when I run a gpupdate /force and a gpresult on a workstation, it
    > only states that Local User Policies are applied (a.k.a. the zenworks
    > ones).
    >
    >
    Craig Wilson - MCNE, MCSE, CCNA
    Novell Knowledge Partner
    Novell does not officially monitor these forums.
    Suggestions/Opinions/Statements made by me are solely my own.
    These thoughts may not be shared by either Novell or any rational human.

  • How to migrate or transfer Windows Live email to OS X Yosemite, using Postbox

    I just got an iMac and it didn't migrate my emails from my Windows PC; only some of them.  I gave up on getting them into Apple Mail, but had Postbox (just Google it to find the download site) on my PC for another email account, so I was able to get Postbox on the Mac to accept emails from Postbox on Windows, which means you'll be using Postbox as your email client on your Mac.  Here's what finally worked, after LOTS of trial and error, which I hope you won't have to repeat:
    1. On the Windows 7 PC (? works with XP or Windows 8), rom Windows Live Mail (this was 2011 version), click on the blue square in the upper left corner and select Export email, and then select Email messages.
    2. Choose Windows Live Mail for the program, then click Next.
    3. Enter the name of folder where you want to export them to and click OK.  I suggest making a New Folder (empty) on Desktop, and name it something to describe the group of email folders you want to transfer.  I have a few groups of email master folders with subfolders, and so did this for each master folder.  If you have only one master folder that contains all your email folders, then you'll only have to do this once. Then click Next.
    4. In the next window that appears, select all the email folders within the master folder you want to transfer, then click Next.
    5. When it finishes exporting, it will say so, and then click Finish.  This can take many minutes or maybe an hour, depending on how many emails you are transferring. 
    6. Open Postbox on the Windows PC (free download for 30-day trial, and only $10 for license, so well worth it), and near the top on the left, highlight “Local Folders.”  Then from the File menu select New and then Subfolder to create an email master folder in Local Folder section of Postbox. Select that folder so it's highlighted.
    7.  Select Tools in Postbox, then "Import all messages from a directory," then "also from its subdirectories."  Then click on the master folder you created that contains all the email folders you just exported from Windows Live Mail.  You'll see that there is a subfolder named something (mine says "Live ([name]), and another subfolder within that that is the name of the master folder that just received your export.  Select this subfolder and click OK.  (Within that are the subfolders corresponding to your Windows Live email folders.)
    8. Within Postbox, right-click on the email master folder you created in step 6, then select Properties, and put your cursor inside the Location box.  You'll probably have to scroll to the right as it will be a long path.  (Mine is Users/[name]/AppData/Roaming/Postbox/Profiles/[long series of random letters and numbers]/Mail/Local Folders/[master email folder name]).
    9. Open Windows Explorer and go to the folder in the Location box, and it will have an “sbd” extension in the folder name.  Open that folder, select all the files in it and copy (ctrl-C) them.
    10.  Put an SD card or USB drive in your PC (formatted with exFAT, so the Mac can read it), and create a new folder with the same name as the master email folder.  Paste all the copied files into that folder.
    11.  Eject the SD/USB and insert into your Mac.
    12. Open Postbox on the Mac (free download, again).
    13. If you’ve set up an email account in Postbox, select & highlight that account on the top left, otherwise select Local Folders.  Maybe better to just select Local Folders as to not get into conflicts with your email account, especially if it’s IMAP, but I had problems with POP account, too.
    14. From the File menu, select New and then Subfolder, and create a Subfolder with the name of your email master folder.
    15.  Highlight your new email master folder and repeat step 14 to create a new subfolder named “test” or something like that, which you’ll later delete.  Then QUIT POSTBOX.
    16. Repeat step 8 with your master email folder to find the location of this folder on your Mac, then open Finder and open that folder.  There should be a subfolder there named “test”, which confirms that you’re in the right place.
    17. Open another Finder window and select the SD/USB drive and the folder in it with your Windows email folders inside it.  Highlight and copy (command-C) all the files within that folder, which will be named something like your Windows Live email folders, but maybe with random letters and numbers at the end.
    18.  Paste all those files into the master email folder in first Finder window.  (This is the actual step of moving all your emails from your Windows PC to your Mac.)
    19.  Reopen Postbox, and you should see all your email folders (possibly with the  random endings to their names) within the email master folder you created.  If there are a lot of them, it may take Postbox a while to index them all.
    20.  To confirm that all your emails transferred, go back to Windows Live Mail on your Windows PC and right click all the email folders you just transferred, and click on Properties, where it will tell you how many messages are in that folder. Write down the number of messages for each folder you transferred.
    21.  On your Mac, select each folder, then highlight all the messages in each folder (select the first, the press Shift and select the last message).  Then right-click on the highlighted messages and then click on Mark and then “Mark all as unread.”  Then a number will appear to the right of the folder telling you the number of unread emails, which should equal the numbers you got from Windows Live email folder properties.
    22.  If the numbers aren’t equal, then I’m sorry, and it’s time to try it again or do some trial and error.
    I tried many different approaches before arriving at this one, which consistently worked for me over and over.  I hope it saves you all the trial and error time it took me.  This is long and complicated, but not as long as trying a bunch of long and complicated methods that didn’t work.  Now you can use Postbox as your email client on your Mac.  Maybe there's a way to transfer them into Apple Mail, but Postbox is fine for me.

    PS:  The Mac folder where Postbox stores it's messages is inside the Library folder inside your User folder.  Normally, the Library folder is invisible.  To make it visible in Finder, I did what it said here: 
    http://osxdaily.com/2011/07/22/access-user-library-folder-in-os-x-lion/

  • Exchange 2010 CAS proxy to Exchange 2013 CAS: Use the following link to open this mailbox with the best performance:

    Hello,
    I've installed Exchange 2013 into Exchange 2010 infrastructure
    [ single Exchange 2010 server; single AD site; AD = 2003 ],
    and moved one mailbox [ Test user ] to Exchange 2013.
    When I login internally through 2013 OWA to access mailboxes on 2010, then proxy works fine.
    When I login internally through 2010 OWA to access mailboxes on 2013, then a message appears:
        Use the following link to open this mailbox with the best performance: with link to 2013 OWA...
    What is wrong ?
    I've checked and changed settings by:
    Get-OwaVirtualDirectory, Set-OwaVirtualDirectory
    [PS] C:\work>Get-OwaVirtualDirectory -Identity 'ex10\owa (Default Web Site)' | fl server,name, *auth*,*redir*,*url*
    Server                        : EX10
    Name                          : owa (Default Web Site)
    ClientAuthCleanupLevel        : High
    InternalAuthenticationMethods : {Basic, Fba, Ntlm, WindowsIntegrated}
    BasicAuthentication           : True
    WindowsAuthentication         : True
    DigestAuthentication          : False
    FormsAuthentication           : True
    LiveIdAuthentication          : False
    AdfsAuthentication            : False
    OAuthAuthentication           : False
    ExternalAuthenticationMethods : {Fba}
    RedirectToOptimalOWAServer    : True
    LegacyRedirectType            : Silent
    Url                           : {}
    SetPhotoURL                   :
    Exchange2003Url               :
    FailbackUrl                   :
    InternalUrl                   : https://ex10.contoso.com/owa
    ExternalUrl                   : https://ex10.contoso.com/owa
    [PS] C:\work>Get-OwaVirtualDirectory -Identity 'ex13\owa (Default Web Site)' | fl server,name, *auth*,*redir*,*url*
    Server                        : EX13
    Name                          : owa (Default Web Site)
    ClientAuthCleanupLevel        : High
    InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated}
    BasicAuthentication           : True
    WindowsAuthentication         : True
    DigestAuthentication          : False
    FormsAuthentication           : False
    LiveIdAuthentication          : False
    AdfsAuthentication            : False
    OAuthAuthentication           : False
    ExternalAuthenticationMethods : {Fba}
    RedirectToOptimalOWAServer    : True
    LegacyRedirectType            : Silent
    Url                           : {}
    SetPhotoURL                   :
    Exchange2003Url               :
    FailbackUrl                   :
    InternalUrl                   : https://ex13.contoso.com/owa
    ExternalUrl                   :
    best regards Janusz Such

    Hi Janusz Such,
    Based on my knowledge, CAS proxy can only from later version to previous version.
    Some like CAS2013 to CAS2010/2007, CAS2013 to CAS2013. 
    Thanks
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Mavis Huang
    TechNet Community Support

  • Migration from old to new iMac do you need to use set up on new or go straight to migration?

    Just got a new iMac and going to migrate from my old 2008 iMac, info from Apple Support is a bit confusing but I want to know if it is best to use the "Set Up" on new iMac before migration or go straight into migration.
    Also the support info says to connect both using ethernet as one option (which is my option) and connected to your network, how do you do this as there is only one ethernet port on each machine and if connected together it would not be possible to connect to a network, ie, the internet via my ISP. Suppot says no router etc needed.
    Somewhat confused so if there is anyone out there who has done this I would appreciate their comments.
    Thank you for any help forthcoming.
    Derek

    How to use Migration Assistant:
    http://support.apple.com/kb/HT4889?viewlocale=en_US
    http://support.apple.com/kb/HT4413?viewlocale=en_US
    http://support.apple.com/kb/TS1963
    Troubleshooting Firewire target disk mode:
    http://support.apple.com/kb/HT1661
    How to transfer data from a PC to a Macintosh:  http://support.apple.com/kb/HT1408

Maybe you are looking for