none
In-place upgrade of Windows Server 2012 RDS to R2 fails

    Question

  • Hi All

    I have a Server 2012 Standard RDS virtual machine (vmware) on which I have tried doing an in-place upgrade to 2012 R2 but it constantly fails.

    It sits at the "Collecting files, settings and applications" process for quite a while - always on 0% and then says: Installing Windows was Canceled "Setup can't continue. Restart the computer and restart Setup. When prompted, try getting the latest updates."

    I have tried combinations of all the settings during setup to look for updates, not look for updates, etc., rebooted several times, even disabled the RDS services and still the same result.

    As a test, I tried doing an in-place upgrade on the base OS installation that was used to create this VM and it works perfectly. The only difference between the servers is that the live has RDS role installed.

    Is there any Microsoft documentation on the 2012 RDS in-place upgrade process to R2?

    Can anyone offer any suggestion as to why the in-place upgrade might be failing with the RDS role installed?

    Thanks heaps

    Friday, January 24, 2014 3:01 AM

Answers

  • As I stated I have already tried an in-place upgrade on the base 2012 vm that I used to create the production RDP server and it worked.

    It seems that the RDS role may be preventing the upgrade?

    Ideally I want to go down the in-place upgrade on the production server as we have alot of users using this machine. I would rather not have to build an R2 RDS server from scratch.

    if you really think the RDS is preventing the upgrade, how about stopping the RDS service then do an in place upgrade.

    check how it goes.. :)


    Every second counts..make use of it. Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.

    Tuesday, January 28, 2014 6:37 AM

All replies

  • I would suggest, create a new VM with Server 2012..after successful installation do an in place upgrade to 2012 R2

    check if you will have same issue...


    Every second counts..make use of it. Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.

    Friday, January 24, 2014 9:37 AM
  • Hi,

    Additionally, please check this similar thread:

    RDS 2012 to 2012 R2 in-place upgrade

    http://social.technet.microsoft.com/Forums/en-US/89002286-fec3-4974-bc0f-c9fb45b2de3a/rds-2012-to-2012-r2-inplace-upgrade?forum=winserverTS

    Regards.


    Vivian Wang

    Monday, January 27, 2014 9:33 AM
    Moderator
  • As I stated I have already tried an in-place upgrade on the base 2012 vm that I used to create the production RDP server and it worked.

    It seems that the RDS role may be preventing the upgrade?

    Ideally I want to go down the in-place upgrade on the production server as we have alot of users using this machine. I would rather not have to build an R2 RDS server from scratch.

    Monday, January 27, 2014 11:38 PM
  • Hi Vivian I have seen this post and this doesn't work for me.

    Any other ideas?

    Monday, January 27, 2014 11:38 PM
  • As I stated I have already tried an in-place upgrade on the base 2012 vm that I used to create the production RDP server and it worked.

    It seems that the RDS role may be preventing the upgrade?

    Ideally I want to go down the in-place upgrade on the production server as we have alot of users using this machine. I would rather not have to build an R2 RDS server from scratch.

    if you really think the RDS is preventing the upgrade, how about stopping the RDS service then do an in place upgrade.

    check how it goes.. :)


    Every second counts..make use of it. Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.

    Tuesday, January 28, 2014 6:37 AM
  • Any more definite resolution to this?  I'm having the exact same issue.

    Thursday, May 08, 2014 8:19 PM
  • 1. Check c:\$windows.~bt\sources\panther\setuperr.log - you will likely find the problem listed there.

    2. I had the same issue with an RDS environment, it was reporting problems accessing the user profile logged in to do the upgrade itself - most likely because we are using User Profile Disks and it couldnt get a 'lock' on the profile. Fix for me was to log on using a dummy local admin account and ensure this dummy user profile was removed from registry (from hklm\software\microsoft\windows nt\currrent version\profilelist) before attempting the upgrade.

    hth,

    David

    • Proposed as answer by dsvir Thursday, June 12, 2014 12:51 PM
    Tuesday, June 10, 2014 2:32 PM