Since you asked, the circumstance warranting registry editing is cloning a running system to create a new instance for a different purpose while bringing it up on the same subnet. Yes, it's a little messy but it works. And thanks for the pointer about virt-sysprep.
________________________________
From: CentOS <centos-bounces@xxxxxxxxxx> on behalf of Charles Polisher via CentOS <centos@xxxxxxxxxx>
Sent: Saturday, February 8, 2020 11:58 AM
To: Leon Fauster <leonfauster@xxxxxxxxxxxxxx>; CentOS mailing list <centos@xxxxxxxxxx>
Harriscomputer
Leroy Tennison
Network Information/Cyber Security Specialist
E: leroy@xxxxxxxxxxxxxxxx
[cid:Data-Voice-International-LOGO_aa3d1c6e-5cfb-451f-ba2c-af8059e69609.PNG]
2220 Bush Dr
McKinney, Texas
75070
www.datavoiceint.com<http://www..com>
This message has been sent on behalf of a company that is part of the Harris Operating Group of Constellation Software Inc.
If you prefer not to be contacted by Harris Operating Group please notify us<http://subscribe.harriscomputer.com/>.
This message is intended exclusively for the individual or entity to which it is addressed. This communication may contain information that is proprietary, privileged or confidential or otherwise legally exempt from disclosure. If you are not the named addressee, you are not authorized to read, print, retain, copy or disseminate this message or any part of it. If you have received this message in error, please notify the sender immediately by e-mail and delete all copies of the message.
Subject: [EXTERNAL] Re: KVM clone
On 2020-02-07 20:14, Leon Fauster via CentOS wrote:
> Am 07.02.20 um 17:43 schrieb Leroy Tennison:
> > Yes, have done it a few times. If you need it to have a different IP address/name/license then bring up a new definition without a NIC, login via virt-manager. For the IP address, search the registry for the current IP address and change the appropriate entries. Use standard Windows utilities to change the description/name. For the license, search for "Product" and select "View your Product ID", in that dialog there should be an option to change the product key. Once done add the same NIC as the other definition had and restart. This has worked all but once for me. The one time it didn't, Windows discerned a network problem (IP address) and provided a way to fix it.
> I remember that for a cloned win system the SID should be also changed.
> https://en.wikipedia.org/wiki/Security_Identifier
I have successfully cloned many versions of Windows OS, then
booted the clone and changed static IP using Network Connections
widget -> Change Adaptor Settings, without incident, where my
intent is never to run both systems at the same time. Not clear
to me what circumstance would warrent editing the registry to
obtain this result, but everything has a good use case I
suppose?
For completeness, as OP might know, Microsoft provides the
'sysprep' utility to prepare a system for cloning. In RHEL6 / C6
and more recent, Linux guests can be similarly prepared with
'virt-sysprep'.
--
Charles Polisher
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
https://lists.centos.org/mailman/listinfo/centos
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
https://lists.centos.org/mailman/listinfo/centos
