Implication of cloning an IIS web server & change hostname/IP addr
Posted on 2013-01-17
I have a pair of Win 2008 R2 Std x64 servers (IBM x3650 M3) which
are in an NLB cluster (& in same domain). They run IIS 7.5 & has
Tivoli agent, NBU agent & Symantec Endpoint Security installed currently.
The servers have yet to go live & there's no backup.
For some reason, Web2's Task Scheduler can't start & under "Local Users
& Groups", the users are completely blank : when I tried to add a local
administrator id, it flags out as the id is there (but really I can't see it
nor could I login using the last known administrator password).
Too much of an effort to reinstall Win 2008 R2, so I thought of doing a
clone over (by moving one of web01's HDD over), boot it up, then insert
one of web2's HDD to do 'hardware mirror sync (if this is not advisable,
I thought of doing Acronis backup of the good web1 & clone it over to web2)
Any precaution to take & will I run into any issue? I recall years ago,
a Win2000 Domain Controller when cloned to another will cause problem
unless we demote the cloned server first, rename its hostname & IP
addr & do 'dcpromo'.
What about Win 2008 licence? Need to reactivate on the cloned server?
Would Tivoli agent & Symantec EP/NBU agent need to be reinstalled?
Some sort of corruption may have happened but nobody acknowledge
any changes was done. A few Wintel sysadmin took a look & can't fix it
There's no hardware amber LED