• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 433
  • Last Modified:

change vmware settings

Hi Experts,
I have some vm's running.
But it is not sufficient memory and CPU set.
When I change memory and CPU, do I have to activate again my windows ?
Because the hardware changed.
You remember, after conversion you have to re activate.
0
Eprs_Admin
Asked:
Eprs_Admin
  • 5
  • 3
  • 2
  • +2
2 Solutions
 
considerscsCommented:
What version of windows?
0
 
Eprs_AdminSystem ArchitectAuthor Commented:
now our vm's are running win2003.
0
 
considerscsCommented:
From my experience with VMware, I have never been asked to reactivate windows after changing the memory specs. However, I am not sure about activation and changing the CPU specs. I do not it can sometimes cause problems if you change the CPU specs after install of OS in VM.
0
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

 
FastSiCommented:
I believe its only OEM versions that are restricted to hardware and may require reactivating
0
 
coolsport00Commented:
Nope...no reactivation is needed. OEM licenses are the ones tied to it's host (hardware).

~coolsport00
0
 
Eprs_AdminSystem ArchitectAuthor Commented:
I forget, my win2003 os is an oem.
after conversion I reactivated one time.
I don't want to do it again.
0
 
FastSiCommented:
maybe snapshot before trying but since the orginal vitrual "hardware" is still there just increased will probably be ok. But if you snapshot the activated VM you should be able to roll back if it dont work.
0
 
FastSiCommented:
actually sorry read it as increasing the virtual memory and cpus for the vm. if its the physical tin it will likely effect it.
0
 
Eprs_AdminSystem ArchitectAuthor Commented:
is no one here to give me an 100% answer ?
When I change memory on my win2003 oem vm, do I have to reactivate or not ?
The same question for the CPU.
0
 
Eprs_AdminSystem ArchitectAuthor Commented:
Hi coolsport00:
Thanks for the answer.
So when I do not change the host hardware, I don't have to worry.
I can change my CPU's and Memory in the vm's , right ?
0
 
bgoeringCommented:
For OEM you are probably not in compliance for license because that license is irrevokably tied to the original hardware it was installed on. If you change processor count and/or memory in your virtual machine Windows would be highly likely to require activation again.

If it was a retail (as opposed to OEM) windows you can transfer it a few times to different hardware, but there are limits as to how often.

In a virtual environment you are much better off setting up a volume licensing arrangement.

On the other hand - if you are changing processors and/or memory in your host (be it ESX, Workstation, Player, etc.) the virtual machine will not see that and will not require reactivation for your virtualized Windows.

Good Luck
0
 
coolsport00Commented:
Correct; and, as "bgoering" mentions for OEM in more detail. If you have the capability for volume licensing, you're better off.

Regards,
~coolsport00
0
 
Eprs_AdminSystem ArchitectAuthor Commented:
yes of course, a volume license is always better.
Thanks.
0
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.

Join & Write a Comment

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 5
  • 3
  • 2
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now