• State Suggested Answer
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 15 subscribers
  • Views 4104 views
  • Users 0 members are here
Options
Related

DA Server Windows 2008 R2 to 2012 R2 in place upgrade

sauerk
over 4 years ago

Our DA server is on Windows Server 2008 R2 which is EOL 1/14/2019.

I tested an in place upgrade and while we've had success with other servers and even other services on this same server, DA does not cooperate.  The web page says there was an error with the Desktop Authority Manager service.  We check and the service is running.

Here is the test scenero.

The VM is cloaned.

The clone network is started disconnected (to not interfere with the live system).

The Server 2012 R2 ISO is mounted, and the in place upgrade is installed.

Upon reboot we mount an iso to install the .NET 4.7 Full offline package (this resolves .net issues when doing a server 2008 > 2012 in place upgrade).

We attach the NIC to the DMZ, which is not the same network as our domain.  This is just to get internet access to do windows updates.

I edit the hosts file to put our DMZ temporary IP to match the name da.  In IE I go to da/DesktopAuthorityCopnsole and I get this error message
An error occurred when attempting to communicate with the Desktop Authority Manager service. Please ensure that the service is started and running. 

I checked all the services, everything specified as Automatic is started.  I double checked and I can connect to the SQL instance on this box where the DAConfiguration database is.

I cannot move this to the domain network until I can confirm it works.  What is the next step?

Parents
  • 0 over 4 years ago

    Nevermind, it just has so much tie in with the domain that the service will never work unless you put it on the same network as the domain.

    I took the chance and disconnected the virtual nic of the live 2008 R2 version of DA server.  I connected and IP;d the virtual nic with the same configuration as the old server in the new 2012 R2 server.  Rebooted it.  The new server appears to be functioning normally.

    So the in place upgrade appears to have worked.  As with all of our other 2008 R2 to 2012 R2 in place upgrades, make sure you have the .NET 4.7 full offline installer on hand to repair .NET after the upgrade and ensure all programs that depend it, like Server Manager, IIS, or anything else... can run.   NDP47-KB3186497-x86-x64-AllOS-ENU.exe

Reply
  • 0 over 4 years ago

    Nevermind, it just has so much tie in with the domain that the service will never work unless you put it on the same network as the domain.

    I took the chance and disconnected the virtual nic of the live 2008 R2 version of DA server.  I connected and IP;d the virtual nic with the same configuration as the old server in the new 2012 R2 server.  Rebooted it.  The new server appears to be functioning normally.

    So the in place upgrade appears to have worked.  As with all of our other 2008 R2 to 2012 R2 in place upgrades, make sure you have the .NET 4.7 full offline installer on hand to repair .NET after the upgrade and ensure all programs that depend it, like Server Manager, IIS, or anything else... can run.   NDP47-KB3186497-x86-x64-AllOS-ENU.exe

Children
No Data