Windows server 2012: migration from 2012 standard evaluation version to 2012R2

Hello.
Is it possible то migrate
FROM: windows server 2012 standard evaluation
TO: windows server 2012R2 standard
And if it is possible then "how to"?
Activation product key for 2012 is NOT available. 
Activation product key (MAK, "open licence") for 2012R2 is available. 
The key for 2012R2 does not "open" 2012 evaluation version.
Thanks.

Upgrade means moving from your existing operating system release to a more recent release, while staying on the same hardware. For example, if your server is running Windows Server 2012, you can upgrade it to Windows Server 2012 R2. You
can upgrade from an evaluation version of the operating system to a retail version, from an older retail version to a newer version, or, in some cases, from a volume-licensed edition of the operating system to an ordinary retail edition.
ref : http://technet.microsoft.com/en-us/library/dn303416.aspx
Arnav Sharma | Facebook |
Twitter Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members
reading the thread.

Similar Messages

  • Can i upgrade to windows 8.1 enterprise from 90 day evaluation version

    can i upgrade to windows 8.1 enterprise from 90 day evaluation version? as our company has volume license key for win 8.1 enterprise purchased

    yes you can.
    Skip Product Key Input in Windows 8.1 Setup
    To achieve our objective, we need to edit the ei.cfg (edition configuration) file present inside the
    /sources folder of the ISO image. All we need to do is to provide the version details inside this file so that Windows Setup is not needed to ask for a product key to install the appropriate version relevant to that product key.
    If you are going to install Windows 8.1 using a USB drive, transfer the installation files to the USB and then proceed to step 2. On the other hand if you need to create a DVD, open the ISO using a utility such as MagicISO so that the structure is not affected.
    Browse to the /sources folder.
    Look for the ei.cfg file and open it in a text editor such as Notepad or Notepad++ (preferred). If the file doesn’t already exist, create a new text document and rename it as ei.cfg
    Now amend the file depending on the version which is included in your particular copy and the version which you want to install. For Professional edition which will be the best bet for most of the users, paste the following context into the
    ei.cfg file. Make sure that anything that already exists in the file should be cleared first.
    [EditionID]
    Professional
    [Channel]
    Retail
    [VL]
    0
    Save the file and run the Windows 8.1 setup again. The setup will not ask for the Product Key anymore.
    This is not a hack or anything illegal. The configuration above is supported by Windows installer and is well documented by Microsoft and can also be used on some other versions of Windows as well.

  • ¿Is it possible to upgrade from SCCM 2012 a domain controller in Windows Server 2008 R2 TO 2012 R2?

    Hi all.
    I want to know if is it possible to upgrade a domain controller from Windows Server 2008 r2 to 2012 r2 installing from SCCM 2012.
    Thanks.
    Regards.

    Hi all.
    I want to know if is it possible to upgrade a domain controller from Windows Server 2008 r2 to 2012 r2 installing from SCCM 2012.
    Thanks.
    Regards.
    Anything is possible if you can script it. You could create a task sequence to do the following (with scripts):
    1. Demote 2008R2 DC to member server
    2. Remove 2008R2 member server from domain
    3. Build new 2012R2 member server and join to domain
    4. Promote 2012R2 member server to DC
    You can do this. However, why would you? Just because you can doesn't mean you should. In my opinion it's more trouble and testing than it's worth. How many times would you need to do this?
    Gerry Hampson | Blog:
    www.gerryhampsoncm.blogspot.ie | LinkedIn:
    Gerry Hampson | Twitter:
    @gerryhampson

  • Migrate from 2012 rtm to 2012 R2

    I am a bit confused, if you read the migration hierarchy scenarios (http://technet.microsoft.com/en-us/library/gg682006.aspx) you can migrate from 2007 to 2012 rtm or SP1 or R2.
    you can migrate from 2012 SP1/R2 to another 2012 SP1/R2
    yesterday I was investigating the possibility to migrate a pilot 2012 RTM environment to a new 2012 R2 environment we just setup.  as a test I was able to migrate a driverpackage, so hey: it seems to work, but why is this scenario not covered in the
    technet online doc?
    so: if object migration from 2012 RTM to 2012 R2 is supported, are there limitations to that scenario?

    I haven't done it either but know of several cases where this has successfully been done. However, as with any migration, there are niggling issues. Unfortunately you won't be able to get any assistance with these - as you are in an "unsupported"
    scenario.
    I would have preferred for this to be tested properly and deemed to be "supported".
    Gerry Hampson | Blog:
    www.gerryhampsoncm.blogspot.ie | LinkedIn:
    Gerry Hampson | Twitter:
    @gerryhampson

  • How to migrate from a standard store setup in a splitted store (msg - idx) setup

    How can I migrate from a standard store setup in a splitted setup described in
    https://wikis.oracle.com/display/CommSuite/Best+Practices+for+Messaging+Server+and+ZFS
    can a 'reconstruct' run do the migration or have I do a
    imsbackup - imsrestore ?

    If your new setup would use the same filesystem layout as the old one (i.e. directory paths to the files would be the same when your migration is complete) you can just copy the existing store into the new structure, rename the old store directory into some other name, and mount the new hierarchy instead of it (zfs set mountpoint=...). The CommSuite Wiki also includes pages on more complex migrations, such as splitting the user populace into several stores (on different storage) and/or separate mailhosts. That generally requires that you lock the user in LDAP (perhaps deferring his incoming mail for later processing into the new location), migrate his mailbox, rewrite the pointers from LDAP, reenable account. The devil is in the details, for both methods. For the latter, see Wiki; for the former I'll elaborate a bit here
    1) To avoid any surprises, you should stop the messaging services before making the filesystem switch, finalize the data migration (probably with prepared data already mostly correct in the new hierarchy before you shut down the server, just resync'ing the recent changes into new structure), make the switch and reenable the server. If this is a lightly-used server which can tolerate some downtime - good for you If it is a production server, you should schedule some time when it is not very used so you can shut it down, and try to be fast - so perhaps practice on a test system or a clone first.
    I'd strongly recommend taking this adventure in small reversible steps, using snapshots and backups, and renaming old files and directories instead of removing them - until you're sure it all works, at least.
    2) If your current setup already includes a message store on ZFS, and it is large enough for size to be a problem, you can save some time and space by tricks that lead to direct re-use of existing files as if they are the dataset with a prepopulated message store.
    * If this is a single dataset with lots of irrelevant data (i.e. one dataset for the messaging local zone root with everything in it, from OS to mailboxes) you can try zfs-cloning a snapshot of the existing filesystem and moving the message files to that clone's root (eradicating all irrelevant directories and files on the clone). Likewise, you'd remove the mailbox files on the original system (when the time is right, and after sync-ing).
    * If this is already a dedicated store dataset which contains the directories like dbdata/    mboxlist/  partition/ session/   and which you want to split further to store just some files (indices, databases) separately, you might find it easier to just make new filesystem datasets with proper recordsizes and relocate these files there, and move the partition/primary to the remaining dataset's root, as above. In our setups, the other directories only take up a few megabytes and are not worth the hassle of cloning - which you can also do for larger setups (i.e. make 4 clones and make different data at each one's root). Either way, when you're done, you can and should make sure that these datasets can mount properly into the hierarchy, yielding the pathnames you need.
    3) You might also look into separating the various log-file directories into datasets, perhaps with gzip-9 compression. In fact, to reduce needed IOPS and disk space at expense of available CPU-time, you might use lightweight compression (lzjb) on all messaging data, and gzip on WORM data sets - local zone, but not global OS, roots; logs; etc. Structured databases might better be left without compression, especially if you use reduced record sizes - they might just not compress enough to make a difference, just burning CPU cycles. Though you could look into "zle" compression which would eliminate strings of null bytes only - there's lots of these in fresh database files.
    4) If you need to recompress the data as suggested in point (3), or if you migrate from some other storage to ZFS, rsync may be your friend (at least, if your systems don't rely on ZFS/NFSv4 ACLs - in that case you're limited to Solaris tar or cpio, or perhaps to very recent rsync versions which claim ACL support). Namely, I'd suggest "rsync -acvPHK --delete-after $SRC/ $DST/" with maybe some more flags added for your needs. This would retain the hardlink structure which Messaging server uses a lot, and with "-c" it verifies file contents to make sure you've copied everything over (i.e. if a file changes without touching the timestamp).
    Also, if you were busy preparing the new data hierarchy with a running server, you'd need to rsync old data to new while the services are down. Note that reading and comparing the two structures can take considerable time - translating to downtime for the services.
    Note that if you migrate from ZFS to ZFS (splitting as described in (2)), you might benefit from "zfs diff" if your ZFS version supports it - this *should* report all ofjects that changes since the named snapshot, and you can try to parse and feed this to rsync or some other migration tool.
    Hope this helps and you don't nuke your system,
    //Jim Klimov

  • Rebuilding a total new server and migrate WS 2012 R2 Essentials

    I want to build a whole new Server system , from AMD to Intel, motherboard, CPU and some HDD's.
    What kind of trouble will I get to do this? And how about my license key?
    Will I loose that as well? Is it possible to migrate most of my software?
    Regards, Martin

    If it was me, I would just make a backup of my old box to a USB drive using windows server backup and restore it to my new box.  2012 and up is very hardware forgiving.  Cost you nothing to try it and the original server is still original if
    it does not work.  You will probably have to activate windows again.
    Grey

  • Do we need CALS for windows server 2008 R2 and 2012 R2 if 2008 R2 is just a stepping stone?

    We currently have a server on Windows Server 2008 RC SP2 64-bit with approximately 20 clients.
    We want to upgrade to Windows server 2012 R2 but first need to upgrade to Windows 2008 R2 to allow us to do a straight upgrade.
    Is it possible to upgrade to Windows Server 2008 R2 with the 5 CAL's included and then upgradeto 2012 R2 and install 20 new CAL's and keep all users accounts and domain PC's the same? 

    Ok sorry for using the wrong terminology... I was under the impression for each client (Computer) connecting to the server we will need a CAL (Client Activation License) in order for the computer to be a domain PC on the server. Do I need 20 CALS's
    for Windows Server 2008 R2 and then another for Windows Server 2012 R2 if we are only upgrading to 2008 R2 to be able to upgrade to 2012 R2 without having to do a clean install.
    For WindowsServer (Standard edition or Enterprise edition or DataCenter edition), a Client Access License (CAL) is required for each device (if you're using the per-Device CAL licensing method), or, is required for each user (if you're using the per-User
    CAL licensing method).
    (whether you use per-Device, or per-User, is up to you, it comes down to cost).
    CALs are version-specific (to a point) - i.e. if you purchased WS2008 CALs for your 20 devices, for use with your WS2008 server, and you are now upgrading that server to WS2012, you need to upgrade your CALs.
    If you are adding a second server which is WS2012, and you are keeping your WS2008 server, you need to upgrade your CALs (because you only purchased WS2008 CALs which don't grant you the rights to connect to the newer server).
    If you were to install your second server as WS2008, you wouldn't need to purchase additional CALs, because as long as the version is the same, a single CAL grant you access to unlimited server (of the same version).
    CALs can be tricky to correctly license.
    Here's some introductory reading:
    http://www.microsoft.com/licensing/about-licensing/client-access-license.aspx#tab=1
    And, none of this relates to the technical aspects of product installation/configuration at all (e.g. clean install vs. upgrade).
    Windows Server CALs are not license keys/tokens/files which you install/load/download - Windows Server CALs are quite literally paper-based (just like a drivers license or car registration). You are required to have them, to be correctly licensed, but, you
    don't physically do anything with them to own/drive a car.
    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!)

  • How to upgrade windows server RDS / TS / RDP 2012 to windows server RDS / TS / RDP 2012 r2 ?

    Hi,
    i am planing to upgrade my current windows RDS 2012 to RDS 2012 r2. 
    Any suggestions or any hints would be GREATLY appreciated.

    the safest and cleanest way will be a new environment being built with 2012 R2 alongside your current deployment - you would then test and once happy move clients over to the new environment
    Regards,
    Denis Cooper
    MCITP EA - MCT
    Help keep the forums tidy, if this has helped please mark it as an answer
    My Blog
    LinkedIn:

  • Building New SQL Server To Migrate from Old one and need to figure out how I need to license it.

    So my head is spinning on setting up a New SQL Server.
    Current setup is Microsoft Server 2003 Standard and Microsoft SQL Server 2000 Standard. Nothing was maintained with Software assurance.
    Environment:
    Database is Limited to 2008 R2 Standard as Highest release I can use with it. So I know I need to do a Downgrade.
    New Server can Be either Microsoft Server standard 2008 or 2012 x64.
    The Domain Controller for right now is going to remain a Machine with Server 2003 Standard x86. It is Licensed with 30 Cals.
    The office Environment:
    The Office has any where from 5-7 employees.
    They have 3 Office locations and employees are in 1 of the three locations depending on the day.
    Between all 3 Offices they have 27 computers.
    Employees also can access multiple machines through out the day.
    Reception, Checkout and Third employee will be at their own machine.
    3 Employees will be accessing their main machine but also float to at the most 6 other machines located in the office these machines are logged in in the morning using their own user name Employees don't login or logout on them throughout the day.
    If they are in The Main Office they access the SQL server machine directly.
    If they are in one of the two satellite offices the Employees will access the SQL server through the front end running on Terminal Services running on the SQL server.
    My New Server will be Either a 4 or 6 core Xeon Processor.
    So the Questions.
    Lets say the scenario is I am buying Windows 2012 Server and Cals and Buying SQL 2012 Server and Cals and will be downgrading both to 2008.
    How do I need to license Windows Server? How many Cals do I need and what way should they be setup?
    How do I need to license SQL Server? By Server? By Core? How Many Cals do I need?
    Thank You.

    Hi,
    In addition, basically a downgrade is possible in case the SQL Server editions are the same. Downgrade is only supported in case a downgrade of e.g. SQL2012 Enterprise to SQL2008R2 Enterprise is done.
    I have attached a link to the SQL Server 2012 Licensing Reference Guide. Look at “Upgrades, Downgrades and Step-Ups” section of the document and check which version and editions are supported for the downgrade.
    SQL_Server_2012_Licensing_Reference_Guide
    Hope it helps.
    Tracy Cai
    TechNet Community Support

  • Unable to do Bare Metal Restore on Windows Server 2008R2 Backup from USB Seagate Backup Plus Harddrive

    I have done a windows full server backup on to an external Seagate HDD on a Dell PowerEdge T110 II Server running Windows Server 2008 R2
    I want to clone this and do a Bare Metal Restore on an identical server at home which has Windows Server 2008 R2 on it.
    I boot from the Windows DVD provided, select repair however windows Server 2008 R2 will not find the image of the Seagate drive. The Seagate drive can be seen on the server otherwise. I guess there are options to load the driver, but I don't see them.
    Please help. Kind of stuck here
    Thanks

    I am using a windows server 2008R2 disk to boot up. Both the servers have windows server 2008R2 on them. I have two licenses for each of the servers. I want to use the server at home as a backup server in case the server in office  goes down. I used
    windows server backup to backup the server at work to a portable USB hard drive. I bought the hard drive home and want to clone the server at work. I heard bare metal restore is the best way to do this. So I booted the server at home with the windows server
    2008 r2 disk that I have and clicked repair. I had attached my seagate portable drive to the usb port so that the server could find the image of the server at work, however the server cant find the hard drive or the server image. Is it a problem with my usb
    hard drive? Do I need a specific type of usb hard drive to do server image backups?
    If I let my server at home boot regularly and it comes up, it can see the image on the hard drive so I dont know how to do the bare metal restore. I know it can be done becuase my IT guy did it when he set up both the servers. I just want to periodically
    clone them so make sure the server at home is updated with the settings of the server at work.
    Thanks for any help here

  • Bulk Project Site option isn't working in project server 2010 migrated from PS 2007.

    Hi,
    I am doing a test migration from epm 2007 to epm 2013. 
    So first, i need to migrate the project server 2007 to project server 2010. i have 2 separate environments for EPM 2007 and EPM 2010).
    there is no problem in migration process and i successfully migrate entire PWA 2007 to 2010, except Workspaces (Project sites).
    Bulk project site option is not helping. I have tried 4-5 times with different PWA 2007 databases (PWA1, PWA2...) but this option did not work. and errors in queue are WSSWebDoesNotExist(16405) and GeneralQueueJobFailed(26000).
    Then next time while migrating all over again i kept the same port and same PWA name then bulk project site option worked.
    Question is, Do i need to keep the same PWA name and same port for the new upgraded PWA??,  one more issue regarding this is that if don't keep the same PWA name and i open the project site and click on the "Project web app" back link, it
    redirects me to old PWA site which doesn't exist and give me page not found error (Obviously).
    Below, you can see the both scenarios.
    my previous PWA 2007 site, say  - http://epm2007:2222/PWA
    When  -  migrated PWA 2010 site, say  - http://epm2010:3000/NewPWA    (Bulk project site update just doesn't work)
    When -  migrated PWA 2010 site, say  - http://epm2010:2222/PWA    (Bulk project site update worked)
    Whats the solution of this problem. is there any utility or query to link all project sites correctly?
    Will i face the same problem while migrating PS 2010 to PS 2013??
    Thank you.
    sandeep

    Hi,
    I would say it is easier to keep the same PWA name between 2007 and 2010 (no need to have the same port).
    If you want to move to a new PWA URL maybe you can use stsadm backup/restore as detailed in this article?
    http://technet.microsoft.com/en-gb/library/ee662500(v=office.14).aspx
    Hope this helps
    Paul

  • Windows Server 2008 Migration

    Hi,
    Which will be easier, migrating from SBS 2008 to a new SBS 2008 or migration from 2008 to SBS 2011? or should I say less complicated migration?
    Thank You

    I'd ask the experts over here.
    https://social.technet.microsoft.com/Forums/en-US/home?category=sbsserver&filter=alltypes&sort=lastpostdesc
    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]
    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

  • Migration from 2007 to Latest version

    Hi,
    We have a developed site in SharePoint 2007 with custom Webparts and also with existing features. Now we want to upgrade this site to latest version. Do we need to follow any specific steps for upgrade because of having Custom webparts? Please provide the
    steps how to upgrade from 2007 to higher version.
    Thanks,

    Take a look at the following sites.  They provide guidance on the upgrade process.  Please Note that without a third party product you will need to first upgrade to SharePoint 2010 and then from there to 2013.  And yes, you will need to make
    sure that all custom code migrations are installed on the new farm.  The code may also need to be re-factored to work in 2013.  Its mostly backwards compatible, but there is no guarantee.
    Upgrade from SharePoint 2010 to 2013 - http://technet.microsoft.com/en-us/library/cc303420(v=office.15).aspx
    Upgrade from SharePoint 2007 to 2010 - http://www.microsoft.com/en-us/download/details.aspx?id=3837
    Paul Stork SharePoint Server MVP
    Principal Architect: Blue Chip Consulting Group
    Blog: http://dontpapanic.com/blog
    Twitter: Follow @pstork
    Please remember to mark your question as "answered" if this solves your problem.

  • File Server Migration from 2008 Standard to 2012 Standard accross different subnet

    Hi
    Im going to migrate File server from Windows 2008 Standard server to Windows 2012 Standard . Source and Destination Servers are on different subnets . According to this
    http://technet.microsoft.com/en-us/library/jj863566.aspx I cannot use Server migrations tool in-built into 2012 .  Im not sure if I can use file server migration toolkit 1.2?.  
    Also my Domain controllers are mixture of Windows 2003, 2008 , 2008 R2 and I've upgraded the schema level to 2012 R2 . Is there anything else I need to be aware of ?
    Can anyone please recommended best way to go about doing this migration . Is file server migration toolkit 1.2 is compatible ?  .
    Only reason I don't want to use Robocopy to this is because If I miss a small setting etc then I will face unwanted downtime.
    I presume Migration toolkit will also create all the Quotas etc on the destination server .
    Thanks
    mumtaz

    Hi mumtaz, 
    We could use file server migration toolkit 1.2 to migrate file server between the two subnets. In order to maintain security settings after the migration, please ensure the security of files and folders after they are migrated to a target file server, the File
    Server Migration Wizard applies permissions that are the same as or more restrictive than they were on the source files and folders, depending on the option you select.
    In the meantime, quota cannot migrate by this tool but we can export and import the quota using dirquota command. Export the templates as xml and then import to new server:
    dirquota template export /file:C:\test.xml
    dirquota template import /file:C:\test.xml
    For more detailed information, please see:
    Template Export and Import Scenarios
    http://technet.microsoft.com/en-us/library/cc730873(WS.10).aspx
    Regards,
    Mandy
    If you have any feedback on our support, please click
    here
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Server Assistant - Migrating from old to new

    Newbie question:
    If I have an XServe with an XRAID, and I setup a new Mac Pro with another RAID (looking at Promise), can I use the Server Assistant to migrate everything?
    In other words, does it work like the Migration Assistant and once it's done, I turn off the old, turn on the new and as far as the end user is concerned, everything works as it did before? I would assume that if there is more than one volume, it would ask me to verify where I am copying it to and calculate the sizes on the new volume to ensure it would fit. Haven't seen it work in practice, so I am asking for anyone who has, or who can direct me to screenshots in another manual.
    I've been reading the Upgradingand_Migratingv10.6.pdf document and they use the words "volume" and "data", but I am really hoping this means stuff that is connected externally, like the XRAID, and managed by the OS X Server.
    Also, they have FireWire drives. Could those just be unplugged and plugged into this newly migrated server without reconfiguration as they will be found and used as they are now Time Machine backups.
    Thanks for any insight.

    If you have Firewire 800 on both machines, that might be the easiest way to go. Then you can use Setup Assistant as soon as you first start up the new Mac. It will tell you to hook up the cables to your old Mac, put it in Target Disk mode and away you go. If you have 400 on one and 800 on the other, just use a FW 400 to FW 800 converter cable.
    Good luck!

Maybe you are looking for