Upgrading .Net 4.0 from 2.0 on server housing IIS - Vmware Vcenter

I have a need for a Web Server to test platform upgrades and architecture changes for the Report Center application.

We currently have a production web server that hosts Report Center  running IIS 7/.Net v2.0 and I want to explore upgrading to .Net 4.0 as well as other infrastructure changes but don't want to risk changing anything on the existing server which could potentially lead to the site going down.

The server can be bare bones as far as CPU/RAM but I would like it set up similar to current so we can do complete end to end testing.

I am open to the option of using our existing server if there is someone (an IIS expert) that could guide me through how to accomplishing what I want to do without disrupting the end user experience.

We use VMWare VCenter here with option to clone (which I've done) but I've been asked to assign another IP on the same VLAN as the original. I'm hesitant to power it up as I don't want to run into any conflicts. Any suggestions?
LVL 16
Raymond PengSystems EngineerAsked:
Who is Participating?
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.

gheistCommented:
You must upgrade .net every month. Test what? There is no way back.
0
Raymond PengSystems EngineerAuthor Commented:
What would be the best way to test the upgrade? I have a clone of the original and what I've done within vcenter is disable the connect network card on power.

Removed clone from domain and added to workgroup
Disabled IIS
Enabled nic and assigned a new IP to clone
Reboot
Gave clone a new name and added to domain.

Would this be ok to test on? Install .net 4.0 on this clone and test? This leaves the production one in place.
0
gheistCommented:
1) prepare good test plan that covers at least a call for each involved library
1a) make sure no changes go to site while testing/upgrading
2) make a clone and keep it off
3) Upgrade original, execute test plan, if it fails power off original machine and power on clone, if it succeeds delete clone

Probably you want to shut down machine and create snapshots before upgrade, after all upgrades installed and machine rebooted and keep them for a while (a week or so)
0

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
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Your procedure is correct.
0
Seth SimmonsSr. Systems AdministratorCommented:
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
0
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.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.