I've done it without problem with a tricky sequence:
1. install w2k (no domain!). it would complain for same name so set it to
different (temp)
2. open network connection properties and remove bindings to netbios
client/sharing. open tcp/ip properties and disable netbios/ip. now you
have bare tcp/ip!
3. (optional) stop all unnecessary netbios-related serverces
4. rename the server to original name. it is now netbios blind and will
not complain :-)
5. perform restore as usual - files, system object and reboot
6. upon restart the system will complain about name conflict and/or
ip-address conflict but will do no harm to live server
7. change ip, computer name, etc.
enjoy.

Zlatko Krastev
IT Consultant






"Rushforth, Tim" <TRushforth AT WINNIPEG DOT CA>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
28.03.2003 23:13
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: Restore of System Object


Any plans for removing this restriction?

We have a few users that want to "clone" a production machine to do
testing.
And they want to use TSM to do it.  Becuasue of this limitation we use MS
Backup to backup system state to disk.

Then the restore process is similar to documented Bare Metal Restore
procedure from redbook except using a different computer name.

So install W2K (different computer name, IP).
Restore data from TSM (to different node name - either using virtualnode
or
logging in with source name).
Restore MS system state from disk.
Reboot and bring up online on separate stand-alone test network or change
computer specific information.

Thanks,

Tim Rushforth
City of Winnipeg
...