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

Implication of cloning an IIS web server & change hostname/IP addr

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
  • 4
1 Solution
sunhuxAuthor Commented:

The url above give some clue but can someone give me the
exact instructions I need to do with sysprep as never used it
before.  I suppose the cloned web2 should be disconnected
from LAN/domain till its hostname, Sid, IP is fully sysprep'ed ?
sunhuxAuthor Commented:
Do I need to note down the problem web2's Sid first
to be able to enter into the newly cloned server later?
sunhuxAuthor Commented:
Ok, figured it out with IBM's help:

a) shut down & power down the good web1
    & remove its HDD (I used the 2nd HDD,
    ie Disk1)

b) take out all HDDs from the bad web2, insert
     the HDD from web1, boot up & select "C"
     for Configure

c) In WebBIOS, select "All Configuratn" not
    "Configuratn 1" & Import & then reboot

d) After it's up, run c:\windows\system32\sysprep\sysprep
    & select the default COOE ..... option & check (ie tick)
    the Generate box & reboot

e) Redetect the NIC port & change hostname (as it's still in
     Workgroup) & reboot
sunhuxAuthor Commented:
Oh, after all's done, insert one of the former (ie with bad
OS) HDD of Web2 while Web2 is up for it to "Rebuild" to
sync the RAID1
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

Get 10% Off Your First Squarespace Website

Ready to showcase your work, publish content or promote your business online? With Squarespace’s award-winning templates and 24/7 customer service, getting started is simple. Head to Squarespace.com and use offer code ‘EXPERTS’ to get 10% off your first purchase.

  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now