Server 2008 R2 Enterpise Roles fail after DISM in place upgrade from Server 2008 R2 Standard

Have a Server 2008 R2 Standard 64bit with remote desktop services, 32Gb RAM.  We needed to increase RAM prior to upgrading network app.  Installed 192 Gb RAM, showed 32 Gb usable.
We ran in place upgrade using DISM, completed successfully.  Server showed all available memory, remote desktop working fine.
Following day, remote desktop user reported that they are unable to print.  All installed printers failed to print.  Restarted print spooler did not help.  Installed a new printer, install completed but failed to print.  After rebooting the server, users could no longer establish RDP connection, as if RDP was disabled.  

I removed the print server and RDP roles and was able to rdp into server.  Reinstalled the roles and RDP is now disabled again, still cannot print. I attempted to RDP to localhost, failed.  Moreover, system now shows 192GB (4.00 GB usable).  

System and Application logs are clean, as if everything is working fine.

Any help will be greatly appreciated.

Uval Lubarsky
Keith WoodAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Randy DownsOWNERCommented:
Maybe this will help.

While I don't have a "here is your problem" answer, I do have a method of helping identify what may be the problem. Based off of what I'm reading here and what I can see on my own servers, Device Manager should be able to help you identify what's going on.

If you open Device Manager, change the view to "Resources by Connection" (not "Devices by connection"). The "Memory" node in there will give you a list of memory reservations by your hardware. Hopefully, the thing that's eating all but 4GB of your RAM will be listed in there. You'll have to convert the hex to RAM sizes, but it can be done.

Start with the server upgraded to Enterprise using the KMS Key. This for me is unlicensed.

Use the MSDN installation media (i.e., the burned ISO) and run the installer from within the current Windows instance. You can then reinstall Windows - make sure you pick the correct option so that you preserve existing files, application, settings etc.

After half an hour or so Windows will have finished installing. When you activate Windows, use the MSDN key, and all will work.

So, it looks like you can't switch keys between OEM/KMS/MSDN - you need to install Windows (or reinstall/update) from the appropriate installation media for the key to "take" correctly.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.