Assessing Migration Scenario's

Dear all,
I am currently working on a migration study for NW2004s. We have 3 scenario's:
1. Install NW2004s next to BW3.1:
a. Use BW3.1 as a datamart for NW2004s
b. Extract all data from source systems to NW2004s and phase out BW3.1 later
2. Migrate BW3.1 to NW2004s
I would like to know:
- What scoring categories (like f.e. costs, risks) to use for assessing these Scenario's?
- Where to find information on these scoring categories?
Thanks in advance,
Ralph

Hello:
Please be aware that 3.1 is out of maintenance at the end of this year (2006). 
Thus, the only recommendation is to upgrade to BI in NetWeaver 2004s.
Besides, the amount of work required to replicate models, data, etc is certainly much higher than the cost of upgrading.  Note that it is not supported to transport between releases. 
Thanks for any points you choose to assign
Ron Silberstein
SAP

Similar Messages

  • Migrating Scenarios from XI 3.0 to PI7.1

    Hi Experts,
                    Can anyone who has done the migration of scenarios from XI 3.0 to PI 7.1 throw light on the process of doing it?
    What precaution needs to be taken in order to see there is a seamless migration and that all the scenarios are working properly? Also what steps needs to be taken in new PI 7.1 to see scenarios using ABAP Server proxies , JDBC Adapter or RFC Adapter?
    Thanks
    Regards
    Suhas

    Hi,
    Kindly go through following docs:
    http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/8085e299-718c-2a10-de94-928f62b763ce
    http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/40328fc8-4844-2b10-b7a2-8930c16df2ba
    http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/90baf3dd-dbf9-2b10-47aa-ac5f56bb5030
    /people/michal.krawczyk2/blog/2009/03/04/pixi-pi-71-upgrademigration--message-mappings
    /people/michal.krawczyk2/blog/2010/03/11/pixi-upgrade-to-pi-71-checks--db-entries
    regards,
    BJagdishwar

  • Lync 2013 multitenant hosting pack and lync 2010 on-prem - coexistence options, alternative migration scenarios

    In post http://social.technet.microsoft.com/Forums/lync/en-US/8a22eed7-cc63-4f9e-b422-3c5a57fb32b0/lync-2013-multitenant-pack-and-lync-2010?forum=lyncdeploy , which was already answered, the answer is no, you cannot migrate from 2010 on-prem. to lync 2013
    hosted pack.
    Trying to get my head around #1 -why, and #2 -what other alternatives are available.
    Lisa answered that there can only be 1 CMS per forest.  Is it one CMS per forest, or
    one CMS per front end pool in a forest? Meaning you can have different CMS pools. If that were true, we could migrate users to a different front end pool in a coexistence scenario between 2010 on-prem to 2013 hosted pack.
    Has anyone done this? 
    This is tough. I guess a cutover then from 2010 to 2013 multitenant hosted pack would be what?
    1. Uninstall 2010, decommission users, decom environment/servers.
    2. Fresh install in same AD environment of 2013 hosted pack.
    That's tough for our users to make such a transition and have potentially days of downtime.
    Is there no other way to do this?
    Josh

    It is one CMS per forest.
    There is no official guide to move from Microsoft Lync Server to Microsoft Lync Server Multitenant Hosting Pack.
    This topic has been discussed several times before:
    http://social.technet.microsoft.com/Forums/lync/en-US/9d438b55-ec53-478a-9247-6d355abedb78/started-installing-lync-2010-enterprise-discovered-multitenant-hosting-pack-do-i-need-to-uninstall?forum=ocsplanningdeployment
    http://social.technet.microsoft.com/Forums/lync/en-US/ad0b77ca-d47e-457b-8f77-33f84409a119/schema-update-lync-hosting-pack?forum=ocsplanningdeployment
    Lisa Zheng
    TechNet Community Support

  • Migration scenario from 3rd party mail server to GW12?

    Hi
    We need to migrate from existing e-mail server (Axigen ) to GW12.
    The main concern is how to do that as quickly as possible or step by step without disrupting mail traffic and users.
    Here is the situation:
    In local network there is mentioned Axigen mail server serving aprox 70 users at single location.
    Our official domain is hosted outside by Hosting provider where their mail server forwards all mail to our DDNS address where is ported to local mail server. Forwarding is performed discrete on user base. Each [email protected] is forwarded to [email protected]. where local server taking over.
    This setting is harder to maintain because it is necessary to maintain users and aliases on outside server manually. However, this setting has some advantages. First of all, forwarding is happened immediately. If for some reason , local server is unreachable, outside server will keep on trying for two more days.
    Second advantage is that we can use anti spam and virus blocking at the providers side.
    Both functionality we could'nt achieve with simple global forwarding of all mail to local server.
    This comment is digresion from main topic.
    Outgoing mail is relayed by local server over our Internet Connection provider's SMPT host.
    Local mail is delivered locally.
    We maintain local DNS server too.
    Most users are using POP service, while IMAP is used by few only. All users are using Thunderbird so far.
    All users in the future should use full GW capabilities with regular GW client, mobile clients and so on.
    GW12 server is installed and up already. It is tested locally and tested for remote sending. So, only remote receiving is not tested yet, so neither correct domain is set yet.
    Present users authentication is performed by Axigen server and LDAP connection to eDir. STARTTLS is used between clients and server.
    Our plan is simple to change local DNS record point to new GW server, to change NAT/routing point to new server and set correct domain for the GW server.
    We expect that this will be transparent for users while they will continue to use Thunderbird (certificate mismatch will be issued by first connection and first mail sending. But we plan to warn users in advance together with instructions what to do. My phone will ring that morning many times, I am sure). Few IMAP accounts we can prepare in advance by move mail manually to local folders and back to GW server later.
    Latest step should be migrate users from Thunderbird to GW client. This need to be perfomed manually at each user seat. Each Thunderbird client need to be switched to IMAP and then mail need to move to GW server.
    Here is concern about old mail volume. Many users have their old mail archived in local folders by years. Some of them has quite huge amount of archived mails with heavy attachments. However old mail can be moved gradually later.
    So, this is our plan. Does anybody has any suggestion, comment or wish to point some problem we didn't aware of?
    Thank you.
    Drazen

    On 9/24/2012 3:56 AM, dzuvela wrote:
    >
    > Hi
    > We need to migrate from existing e-mail server ('Axigen '
    > (http://www.axigen.com/)) to GW12.
    > The main concern is how to do that as quickly as possible or step by
    > step without disrupting mail traffic and users.
    >
    > Here is the situation:
    > In local network there is mentioned Axigen mail server serving aprox 70
    > users at single location.
    > Our official domain is hosted outside by Hosting provider where their
    > mail server forwards all mail to our DDNS address where is ported to
    > local mail server. Forwarding is performed discrete on user base. Each
    > [email protected] is forwarded to [email protected]. where local
    > server taking over.
    >
    > This setting is harder to maintain because it is necessary to
    > maintain users and aliases on outside server manually. However, this
    > setting has some advantages. First of all, forwarding is happened
    > immediately. If for some reason , local server is unreachable, outside
    > server will keep on trying for two more days.
    > Second advantage is that we can use anti spam and virus blocking at the
    > providers side.
    > Both functionality we could'nt achieve with simple global forwarding of
    > all mail to local server.
    > This comment is digresion from main topic.
    >
    > Outgoing mail is relayed by local server over our Internet Connection
    > provider's SMPT host.
    > Local mail is delivered locally.
    >
    > We maintain local DNS server too.
    >
    > Most users are using POP service, while IMAP is used by few only. All
    > users are using Thunderbird so far.
    >
    > All users in the future should use full GW capabilities with regular GW
    > client, mobile clients and so on.
    >
    > GW12 server is installed and up already. It is tested locally and
    > tested for remote sending. So, only remote receiving is not tested yet,
    > so neither correct domain is set yet.
    >
    > Present users authentication is performed by Axigen server and LDAP
    > connection to eDir. STARTTLS is used between clients and server.
    >
    >
    > Our plan is simple to change local DNS record point to new GW server,
    > to change NAT/routing point to new server and set correct domain for the
    > GW server.
    > We expect that this will be transparent for users while they will
    > continue to use Thunderbird (certificate mismatch will be issued by
    > first connection and first mail sending. But we plan to warn users in
    > advance together with instructions what to do. My phone will ring that
    > morning many times, I am sure). Few IMAP accounts we can
    > prepare in advance by move mail manually to local folders and back to GW
    > server later.
    >
    > Latest step should be migrate users from Thunderbird to GW client. This
    > need to be perfomed manually at each user seat. Each Thunderbird client
    > need to be switched to IMAP and then mail need to move to GW server.
    > Here is concern about old mail volume. Many users have their old mail
    > archived in local folders by years. Some of them has quite huge amount
    > of archived mails with heavy attachments. However old mail can be moved
    > gradually later.
    >
    >
    > So, this is our plan. Does anybody has any suggestion, comment or wish
    > to point some problem we didn't aware of?
    >
    > Thank you.
    > Drazen
    >
    >
    most of this sounds good. With such heavy imap/pop usage, you MIGHT
    want to consider installing a temporary dedicated gwia just for that
    separate from the smtp handling gwia. But that might not be necessary at
    all. 70 people isn't THAT much.

  • Migration for BW 7.0..

    Hi all,
    Please suggest the best approach for migrating the transfer rules,update rules into the transformations and migrating the data sources in BI7.0
    During the migration system going to migrate the routines(start/update routines) as well or we have to write the routines in transformations?
    Thanks in advance.

    You may wish to get some Insights from below.
    Assessing Migration Scenario's
    Transformation Rules
    Strategy toward new and 3.x datasource / infosource
    Re: Few questions on BC activation..
    Replicate NEW/3.x datasource - Methodology
    Replicate NEW/3.x datasource - Change back to 3.x datasource Methodology
    Re: Datasource Identification
    Hope it Helps
    Chetan
    @CP..

  • Clarifications to migrate to transformations

    Dear Team,
    I want some clarifications.
    I am doing upgradation project. (BW 3.1 to BI7).
    Customer is asking me to migrate all existing transferrules/updaterules to transformations. what needs to do ?. Is it possible to migrate all existing transfer rules/update rules at a time?. Is there any programs to achieve this?.
    Best Regards,
    SG

    Hi SG,
    some of the useful links from SDN related to migrations
    Re: Datasource Identification
    Strategy toward new and 3.x datasource / infosource
    Replicate NEW/3.x datasource - Methodology
    Replicate NEW/3.x datasource - Change back to 3.x datasource Methodology
    Assessing Migration Scenario's
    Re: Few questions on BC activation..
    Transformation Rules
    hope they help

  • How-to get transformations from transfer/update rules

    Hi all,
    we did an upgrade to BI 7.0 frm BW 3.5, how shall we get the new things like transformations,DTP for tha already existing cubes/ODS. is there any procedure to convert transfer and update rules to transformation.
    Thanks all,
    Regards

    Migration - Yu may wish to read below steps
    Transformation Rules
    automatic mapping without the use of an Infosource.
    steps are listed below.
    On the InfoSource Tab (Note- Ensure DataSource and Infosource have not been migrated)
    1. Right Click > Additional Functions > Create Transfer Rules
    2. Activate Transfer Rules
    3. Right Click > Additional Functions > Transformation erzeugen
    On the DataSource Tab
    4. Create Transformation (Map to DSO, should map automatically)
    5. Migrate DataSource
    6. Create InfoPackage
    7. Create DTP
    Assessing Migration Scenario's
    Transformation Rules
    Strategy toward new and 3.x datasource / infosource
    Re: Few questions on BC activation..
    Replicate NEW/3.x datasource - Methodology
    Replicate NEW/3.x datasource - Change back to 3.x datasource Methodology
    Re: Datasource Identification
    Hope it Helps
    Chetan
    @CP..

  • Open PO migration advice

    Hi all,
    Can someone advise me on the migration scenarios?
    1)Open PO
    Eg: PO qty: 10, GR qty 4, Outstanding 6 qty not GR, and LIV not done at all
    2)Partially open PO
    Eg: PO qty: 10, GR & LIV qty 4, Outstanding 6 qty not GR and LIV not done
    For scenario 1), Is this the appropriate method to migrate the PO?
    ->Upload the PO ordered qty with 10 and upoad the GR data for the 4 qty?
    For scenario 2), which is the appropriate method to migrate the PO?
    a)Upload the PO ordered qty with 10, upoad the GR data for the 4 qty, upload the invoice data for 6 qty
    b)Upload the PO ordered qty with the open quantities(6 qty)
    Thanks.

    Hi
    Normally PO upload is done only for pending to delivery, because stock is getting uploaded via 561.
    Payments outstanding is dealt in FI posting directly for pending payments to do this vendor G/L account is updated for pending payments value.
    Regards
    Rang

  • Migration to new G/L

    Hi gurus;
    Does anyone have a clear idea about migration? Does Migration from classic G/L to new G/L mean that
    transferring of only open items and the balance carry forward for prior years from migration date
    and all items for the migration year to new G/L ? Or does it depend on the migration scenario you purchase?
    We are at a test stage of migration for the time being and I hope we have done something wrong to achieve this result. What is in our hands is merely frustration. I would have hoped that I can see the balance of all G/L accounts for the prior years from migration just like the view FS10N especially after paying (the cost is not nuts) for this service.
    I would like to hear from someone else that this is the case after migration or I would have been very pleased to hear that I can see the balance of all G/L accounts for prior years from migration and thus have done something wrong in the migration cockpit.
    Thanks and regards,
    Gökçen.

    Hi,
    There are some link avaiable in the forum,
    plz check those,
    http://help.sap.com/saphelp_erp2005vp/helpdata/en/43/6880cbb88f297ee10000000a422035/frameset.htm
    http://download.sap.com/SMIGlobal/download.epd?context=10E4E88D9B24D6431C7BEB361BD56B4D969C101C256CB7CB69EE6B0504E2D5066DC143E3304DCB7F6543A472784CCBA693250777F73FC80B
    http://download.sap.com/SMIGlobal/download.epd?context=C17F14F27A6B3CF14454326057B25CBB975E1CCF10332671BE66F4A974078B06DE6D6CA852CBEAEDAB2ED88AFBE7EB2C85C9FDA87F34A9AF
    And there is a reply also from the earlier one,
    I would however pass one bit of advice to you and that is to review OSS note 1070629
    This is the FAQ's about the new GL migration.
    There are some very useful questions and answers, and this should help you with the planning of your project.
    https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1070629&nlang=EN&smpsrv=https%3a%2f%2fwebsmp101%2esap-ag%2ede
    Here are some useful Q & A's
    17. Is it possible to upgrade to ECC5.0 or ECC6.0 and migrate from the classic General Ledger to the new General Ledger in the same fiscal year?
    If you intend to use document splitting in the new General Ledger, activate the function for validating the document splitting in your productive system before the migration date. This means that you should upgrade to ECC 6.0 in one fiscal year, activate document split validation before the end of that fiscal year and migrate to the new General Ledger in the next fiscal year.
    If you do not plan to use document splitting in the new General Ledger, you can upgrade to ECC5.0 or ECC6.0 and migrate to the new General Ledger in the same fiscal year.
    Keep in mind that the function for validating document splitting is not available in ECC5.0.
    24. How should I check data consistency in the classic General Ledger before the beginning of the first test migration?
    To check data consistency in the classic General Ledger before the beginning of the first test migration, proceed as follows:
    1) Program RFINDEX
    Execute the program RFINDEX twice.
    In the first run, choose "Documents vs Indexes" in the selection screen.
    In the second run, choose "Indexes vs Documents" in the selection screen.
    For more information, see the program documentation.
    If the program finds any differences, create a message on SAP Service Marketplace under the component FI-GL-GL-X.
    2) Program SAPF190
    Run program SAPF190 for the fiscal year prior to the migration and for the fiscal year in which the migration takes place.
    If the program finds any differences, create a message on SAP Service Marketplace under the component FI-GL-GL-X.
    3) Program RAABST02
    If you use Asset Accounting, run program RAABST02.
    If the program finds any differences, create a message on SAP Service Marketplace under the component FI-AA-AA-B.
    4) Program RCOPCA44
    If you use Profit Center Accounting, run program RCOPCA44.
    If the program finds any differences, see SAP Note 81374.
    Remove all inconsistencies before you start the first test migration
    29. Which parts of Customizing must already exist in the production system on the migration date?
    If you use document splitting in ECC 6.0, we recommend that you activate the validation of document splitting in the production system at the latest on the migration date. This means that the new General Ledger including document splitting must be completely configured in the production system on the migration date and that all interfaces and ALE scenarios must be adjusted accordingly.
    This does not apply to ECC 5.0 because the validation of document splitting is not available in ECC 5.0.
    If you do not intend to use document splitting or if you use Release ECC 5.0, you can transport Customizing of the new General Ledger to the productive system after the migration date.
    The indicator "New General Ledger Accounting Is Active" is transported with other basic settings of the new General Ledger in table FAGL_ACTIVEC. Ensure that the indictor "New General Ledger Accounting Is Active" is not set when you transport it to the production system.
    30. When drawing up the project plan, what must I consider if I want to use document splitting?
    We recommend that you activate document splitting validation at the latest on the migration date.
    The new General Ledger including document splitting must be completely and finally configured before you activate document
    Hope everything helps in migration new GL functionality
    Saravanan.A

  • Events 1863 and 2093 post 2003 Migration to 2008 R2

    I have migrated AD from a 2003 SBS SP2 server to a 2008 R2 SP1 server using the following article: http://technet.microsoft.com/en-us/library/dd379526.aspx
    That was 2 days ago, this morning I noticed the following events in the 2008 error log: Error 1863 and Warning 2093
    There appears to be no issue with the domain currently, everyone was able to login in without issue this morning. Both servers are continuing to run, although I plan to demote the 2003 and decommission the hardware if there are no issues (as advised by the
    post-migration instructions of the above article). I can provide full text of the events, but I have removed identifying information:
    Log Name:      Directory Service
    Source:        Microsoft-Windows-ActiveDirectory_DomainService
    Date:          2/17/2014 4:18:14 AM
    Event ID:      1863
    Task Category: Replication
    Level:         Error
    Keywords:      Classic
    User:          ANONYMOUS LOGON
    Computer:     SERVERNEW.generic.local
    Description:
    This is the replication status for the following directory partition on this directory server.
    Directory partition:
    CN=Schema,CN=Configuration,DC=generic,DC=local
    This directory server has not received replication information from a number of directory servers within the configured latency interval.
    Latency Interval (Hours):
    24
    Number of directory servers in all sites:
    1
    Number of directory servers in this site:
    1
    The latency interval can be modified with the following registry key.
    Registry Key:
    HKLM\System\CurrentControlSet\Services\NTDS\Parameters\Replicator latency error interval (hours)
    To identify the directory servers by name, use the dcdiag.exe tool.
    You can also use the support tool repadmin.exe to display the replication latencies of the directory servers.   The command is "repadmin /showvector /latency <partition-dn>".
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-ActiveDirectory_DomainService" Guid="{0e8478c5-3605-4e8c-8497-1e730c959516}" EventSourceName="NTDS KCC" />
        <EventID Qualifiers="49152">1863</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>5</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8080000000000000</Keywords>
        <TimeCreated SystemTime="2014-02-17T09:18:14.599176800Z" />
        <EventRecordID>243</EventRecordID>
        <Correlation />
        <Execution ProcessID="504" ThreadID="660" />
        <Channel>Directory Service</Channel>
        <Computer>SERVERNEW.generic.local</Computer>
        <Security UserID="S-1-5-7" />
      </System>
      <EventData>
        <Data>CN=Schema,CN=Configuration,DC=generic,DC=local</Data>
        <Data>1</Data>
        <Data>1</Data>
        <Data>24</Data>
        <Data>System\CurrentControlSet\Services\NTDS\Parameters</Data>
      </EventData>
    </Event>
    Log Name:      Directory Service
    Source:        Microsoft-Windows-ActiveDirectory_DomainService
    Date:          2/17/2014 4:18:14 AM
    Event ID:      2093
    Task Category: Replication
    Level:         Warning
    Keywords:      Classic
    User:          ANONYMOUS LOGON
    Computer:      SERVERNEW.generic.local
    Description:
    The remote server which is the owner of a FSMO role is not responding.  This server has not replicated with the FSMO role owner recently.
    Operations which require contacting a FSMO operation master will fail until this condition is corrected.
    FSMO Role: CN=Schema,CN=Configuration,DC=generic,DC=local
    FSMO Server DN: CN=NTDS Settings,CN=SERVEROLD,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=generic,DC=local
    Latency threshold (hours): 24
    Elapsed time since last successful replication (hours): 25
    User Action:
    This server has not replicated successfully with the FSMO role holder server.
    1. The FSMO role holder server may be down or not responding. Please address the problem with this server.
    2. Determine whether the role is set properly on the FSMO role holder server. If the role needs to be adjusted, utilize NTDSUTIL.EXE to transfer or seize the role. This may be done using the steps provided in KB articles 255504 and 324801 on http://support.microsoft.com.
    3. If the FSMO role holder server used to be a domain controller, but was not demoted successfully, then the objects representing that server are still in the forest. This can occur if a domain controller has its operating system reinstalled or if a forced
    removal is performed.  These lingering state objects should be removed using the NTDSUTIL.EXE metadata cleanup function.
    4. The FSMO role holder may not be a direct replication partner. If it is an indirect or transitive partner, then there are one or more intermediate replication partners through which replication data must flow. The total end to end replication latency should
    be smaller than the replication latency threshold, or else this warning may be reported prematurely.
    5. Replication is blocked somewhere along the path of servers between the FSMO role holder server and this server.  Consult your forest topology plan to determine the likely route for replication between these servers. Check the status of replication using
    repadmin /showrepl at each of these servers.
    The following operations may be impacted:
    Schema: You will no longer be able to modify the schema for this forest.
    Domain Naming: You will no longer be able to add or remove domains from this forest.
    PDC: You will no longer be able to perform primary domain controller operations, such as Group Policy updates and password resets for non-Active Directory Domain Services accounts.
    RID: You will not be able to allocation new security identifiers for new user accounts, computer accounts or security groups.
    Infrastructure: Cross-domain name references, such as universal group memberships, will not be updated properly if their target object is moved or renamed.

    Hi,
    The guide you are using is not for SBS. If you look at the detailed supported migration scenarios you will see this matrix:
    Source server   processor
    Source server operating system
    Destination server operating system
    Destination server processor
    x86- or x64-based
    Windows Server 2003 with Service Pack 2 (SP2)
    Windows Server 2008 R2, both full and Server Core installation   options
    x64-based
    x86- or x64-based
    Windows Server 2003 R2
    Windows Server 2008 R2, both full and Server Core installation   options
    x64-based
    x86- or x64-based
    Windows Server 2008, both full and Server Core   installation options
    Windows Server 2008 R2, both full and Server Core installation   options
    x64-based
    x64-based
    Windows Server 2008 R2
    Windows Server 2008 R2, both full and Server Core installation   options
    x64-based
    x64-based
    Server Core installation option of Windows Server 2008 R2
    Windows Server 2008 R2, both full and Server Core installation   options
    x64-based
    There is no Small Business Server specified.
    This forum is not really for SBS migrations and you can also ask on the SBS forums
    for better advice about SBS.
    And yes, if you want to decommission the SBS server, running as a DC, you will at some point have to transfer the FSMO roles to the destination server. Please follow the steps in the guide I posted earlier to migrate the roles or applications that you need.
    And also ask more details on the SBS forums.
    Marius
    http://mariusene.wordpress.com/

  • Migrate to Windows 2012 R2 and Exchange 2013 SP1 using database portability

    Hi, I'm planning to migrate from Exchange 2013 SP1 running on Windows 2012 to Exchange 2013 SP1 on Windows 2012 R2.
    Is it possible to use database portability to move the databases from the exchange installation on win 2012 to the new installation on Win 2012 R2? This would save a great deal of time not doing the mailbox moves.
    I've searched similar cases but couldn't find any, all speak about disaster recovery and database portability but I've found no articles that uses the migration scenario.
    Would it be possible to do and if so, what would the steps be? Do I need to delete the database from the source server, move the database files to the new server and mount them and relocate the mailboxes? Or should I dismount the database on the source server,
    move them to the new server and mount them and relocate the mailboxes?
    Frank.

    Hi,
    According to your description, I recommend you consider using DAG to achieve your requirement.
    The following steps for your reference:
    1.Prepare a new server which installed windows 2012 R2 for Exchange 2013 mailbox server.
    2.After you deploy Exchange 2013 Mailbox servers, you can create a DAG, add Mailbox servers to the DAG, and then replicate mailbox databases between the DAG members.
    3.After replication, you can mount all the databases on the new server.
    Hope this helps!
    Thanks.
    Niko Cheng
    TechNet Community Support
    This no way a resolution. This won't work at all as Both OS will be different and you can't form the Cluster.
    Please Unmark it!
    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.

  • Open items migration for document splitting

    Hi,
    We have done document splitting in 2011, Now all open items before 2011 to be migrated into the new fiscal year (2011).
    Please suggest us how to migrate all the open items into new GL with document splitting activated?
    Eagerly waiting for the reply.
    Thanking you in Adavnce,
    Raghuvir

    Hi Raghuvir,
    There were critical reasons why the split of the open line items of prior years has not provided within the standard migration scenarios.
    The structure and the account assignment information of the already posted documents from the prior years is probably does not satisfy the new document splitting. Therefore it is not possible to split the documents form phase 0 (migration cockpit) based on the new the splitting rules set in the customizing.
    It is also too critical to allow a customer based split in the BAdI since it cannot be garanteed if the sum of split amounts in all the
    currencies still equal the old amount. Furthermore it cannot be traced any more where the split amounts are coming from which would lead to a problems regarding the auditability of the new g/l migration.
    The only possiblity that SAP can offer to the customers is to take over the split amounts from the already existing SL ledgers which have been used before the migration to new g/l.
    I believe that this answer your inquiry. I am sorry that I cannot give you a more positive answer regarding your issue.
    Kind Regards,
    Vanessa.

  • New-GL Migration and Upgrade together is possible??

    Dear NewGL gurus.
    Currently, our customer who uses SAP Enterprise version is
    considering to do the upgrade from Enterprise to 6.0
    and migration to New-GL at the same time with migration scenario 4.
    I knew that "SAP strongly recommends the migration as independent project".
    But, as long as I read the documents, it seems possible technically.
    So, my questions are
    1. If this customer does the upgrade and migration at the same time,
      can they take SAP Migration Service from SAP AG properly?
    2. SAP mentioned the reasons for this strong recommendation
    such as
    - 'migration is not only technical transfer'
    - 'migration is conceptual change'.
    However, I think the same thing can be said for upgrade project as well.
    So, is there any other reasons for this recommendation?
    BR
    Yoshitada Kaneko

    Dear Yoshitada Kaneko
    Please also go through with below notes for more information.
    Please also refer the FAQ note and below links
    1070629
    812919    SAP ERP new general ledger: Migration
    1337521   safety delta in incremental work list update for phase 1
    1171402   Compatibility IS-M/SD with General Ledger Accounting (new)
    1072121   New general ledger migration: What is covered by Support?
    1039752   New G/L migration: Restrictions and important information
    1014369   NewGL migration: Availability of Development Support
    1014364   New G/L migration: Information, prerequisites, performance
    824995    LCC: Gen. questions/answers about local currency changeover
    Please refer the more information at "/glmig" at service market place
    http://wiki.sdn.sap.com/wiki/x/JghNCw
    Reg
    Madhu M

  • JDI : DTR / CBS - Moving components from one scenario to another.

    Hi all,
    I have a series of Development Components that fall under the scenario 2 description of the DTR / CBS scenarios.
    I am trying to move our projects into a scenario 2+, and have created the CONS and DEV projects in our SLD. I moved the development components from the old scenario into the DEV workspace through a propagation list, but I don't see the Development Components appear in the CBS BuildSpace, even after refresh.
    Is it possible to migrate existing DCs from scenario 2 to 2+ and 3? Or do I need to manually create each DC and add all the components in it?

    Hi,
    It is stated in help.sap.com that there is no migration scenario from 2 to 2+ or 3.
    So, it seems you should do it manually.
    Sorry for non constructive ansewer.
    Victor.

  • Migrate to new domain and new SCCM

    The migration scenario is this:
    All Clients are in Domain1 and are managed through SCCM 2012 with System Center Endpoint Protection 2012.
    Some of the clients need to join a new domain and be managed through a new SCCM 2012 R2 server with System Center Endpoint Protection 2012 R2.
    There are no trusts between the forests. Do we need to uninstall the SCCM 2012 Agent and SCEP 2012 and then install the new SCCM 2012 R2 Agent and SCEP 2012 R2?
    Or can we just uninstall SCCM 2012 Agent only and keep SCEP 2012 and later install.

    There are multiple ways to go about it.
    Assuming that the AD forest is properly extended and the new site's info is properly published, then you can simply run a script:
    http://msdn.microsoft.com/en-us/library/cc146558.aspx
    http://gallery.technet.microsoft.com/scriptcenter/Change-sccm-configmgr-cf6e0327/view/Discussions
    If the two assumptions above aren't correct, then the client has no way of getting the trusted root key gracefully for the new site and running ccmsetup  is the best way.
    The ccmsetup bootstrapper will download files as needed from the closest DP but (from memory) won't redownload files if they are already present in the ccmsetup folder.
    A client push is probably the easiest method to initiate ccmsetup because it can be managed from a central location -- just make sure you select the checkbox for always reinstall. Of course, as mentioned above, if someone has previously used the "group
    policy" to assign the site to your clients, you'll need to clean up that mess first otherwise the clients will always try to assign to the old site.
    Jason | http://blog.configmgrftw.com

Maybe you are looking for