Changing computer name
There are two desktops and a laptop on my local network, and I just added a new notebook. I was unhappy with the operating system on the new notebook, so I over-wrote the system disc with a saved image of the system disc from one of the desktops. The new notebook will now have the O.S. which I want, along with all the software and configuration which could have taken weeks to re-establish. However, the new notebook will also have the name of that desktop, which will result in a conflict on the network. I'd like some guidance on how to change the name of the new notebook, in order to avoid that conflict. To my understanding, it is not as simple as changing the computer name in System Properties. Every reference to the conflicting name must be replaced, including in user profile and in the registry. Please advise.
ASKER
Thank you. I didn't think the user profile was renamed when the computer was renamed in 'Properties'. Is the user profile renamed automatically?
The user's profile should simply be at:
c:\documents and settings\username
You can take a look at the profile folder after the rename for any issues which you can easily resolve by manual copies to the new user folder (if one is needed/created).
c:\documents and settings\username
You can take a look at the profile folder after the rename for any issues which you can easily resolve by manual copies to the new user folder (if one is needed/created).
ASKER
Thank you. I'll post again after renaming the computer...
you will have windows problems though - since you are violating windows EULA
the windows versions are tied to 1 system for OEM versions, and will complain about activation
in some countries, you can install windows on another pc - if you uninstall it from the old one
the windows versions are tied to 1 system for OEM versions, and will complain about activation
in some countries, you can install windows on another pc - if you uninstall it from the old one
ASKER
Thanks for reminding me about that.
Renaming your computer WILL NOT invalidate EULA.
Hardware changes etc will require a activation, a simple rename is handled by the OS, there is NO EULA violation in renaming a computer. It is a daily action performed for security purposes etc. The only issue will be if windows detects it is being run somewhere other than on the hardware it was activated on.
Hardware changes etc will require a activation, a simple rename is handled by the OS, there is NO EULA violation in renaming a computer. It is a daily action performed for security purposes etc. The only issue will be if windows detects it is being run somewhere other than on the hardware it was activated on.
becraig, it's not because of the renaming, but because of the imaging he did
Hi,
This is one of those cases where yes you can do it and changing the machine name will work fine but there are deeper issues afoot.
When you clone a machine you duplicate the OS license and the license keys of all the other software you have installed on the original machine. Violating software licenses is not something your employer or the software vendors will be happy about.
There is also a privacy issue of the original user's data, and all the other people who may have logged onto the machine. This will need to be cleaned up.
Normally to remove any machine identity you would use sysprep. Unfortunately running sysprep on a built machine is a bad idea so don't do it.
Frankly, the better option is to flatten the notebook and install the OS and apps clean. It will probably be quicker in the long run and have no nasty surprises of "cloned machine syndrome" you may face.
Mike
This is one of those cases where yes you can do it and changing the machine name will work fine but there are deeper issues afoot.
When you clone a machine you duplicate the OS license and the license keys of all the other software you have installed on the original machine. Violating software licenses is not something your employer or the software vendors will be happy about.
There is also a privacy issue of the original user's data, and all the other people who may have logged onto the machine. This will need to be cleaned up.
Normally to remove any machine identity you would use sysprep. Unfortunately running sysprep on a built machine is a bad idea so don't do it.
Frankly, the better option is to flatten the notebook and install the OS and apps clean. It will probably be quicker in the long run and have no nasty surprises of "cloned machine syndrome" you may face.
Mike
ASKER
Mike, thank you. You may be right. I am the only user of the old and new notebook. The old notebook will be out of commission when the new notebook is populated with operating systems and software. The Windows O.S. on the old notebook was not OEM, but a purchased installation disc. All software is licensed in my name. So I'm not going to be violating any license agreements. If it turns out to be too much trouble to clone the machine, I'll start with a fresh install of the O.S. and applications.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I'm definitely open to considering this.
ASKER
I'm going to install all the software and perform all the configuration on the 64-bit system. I did install Windows 7 32-bit on another partition, but there are no 32-bit drivers for many of the notebook's devices. Thanks to all experts for commenting.
Just simply go into system properties and change the name of the notebook.
As you indicated you just completed a rebuild of the notebook so there should be very little to be concerned about.
DNS will update with the new name and most if not all system references will get cleaned up at the system restart.