Error running VMWare Convertor on Win 2K server

Do you have SP4's Update Rollup 1 installed?

I've seen the "update rollup 1" cause weird issues.  Try uninstalling it, P2V it, then install it again.

To clarify, you do not need to uninstall SP4, just the Update Rollup 1.

yes - have just seen that 'update rollup 1 for windows 2000 SP4 ' installed

what implications does removing this have?

thanks

Actually - Have jsut clicked on remove 'update rollup 1' in add/remove programs and it said 'this has already been uninstalled - do you want to remove from add/remove control panel?'

any other ideas?

it does come up with the below part way through but looks like it skips them:

    06:50:39 PM                        Cloning source volume c: into target virtual machine...
    07:12:42 PM                                WARNING: Detected bad blocks on the source volume, not copying them to the target

so from an image off Symantec Backup Exec System Recovery Server we can open in VMware?

yes.  When you make an image it will create V2i files for your disks and a SV2I file (an index file for the machine).  When using the converter chose the "other" option for images and browse to the sv2i file.  VMWare Converter is compatible with converterting the image to a virtual machine

hi,

in the symantec sofware i have created a .V2i file. then in the symnatec software i managed to convert that to .vmdk

How do i open this as our vmware server / console doesnt like that file extension?

Create a backup job instead of one time backup, this way it will create a v2i file and sv2i file.  One completed it is best use the vmware converter and not the symantec tool (we will use the symantec tool if vmware converter doesn't work correctly).

Let me know if the vmware converter does the job.  If not we'll use the Symantec converter method.

Hi,

It has created the Vmware image fine - I have tried to open it using VMware player on my PC but as it boots it gets a blue screen. Will this be caused by the bad blocks we skipped or to the physical machine im running it on now or the fact it needs runing in vmware server/

I wuld not use vmware player it is not a good test.  Convert the image with vmware converter and we'll test it this way.  If you have bad blocks it can cause some issues but we'll see what we can do.

Are you running vmware server or ESX?

If you're runnign vmware server you can take the vmdk file you've already converted with Symantec tool and create a virtual machine.  In this case you would choose "use existing virtual disk" and browse to the vmdk file.  Now run the virtual machine and see what happens

neither at the moment - The situation is as follows. we have an old Windows2K web server that is on its last legs. we want to create a VMWARE image of it and run on a new bit of kit so we do not have to rebuild the server.

I now have .vmdk, vmx, .vmsd files

Whats the best way to run this - VMWARE server? If so is it free?

thanks

its seems to blue screen running in player and vmware workstation....

Have you used the vmware converter or are you trying to run the image directly from vmware player or vmware vmware workstation?

If you dont' have the most current vmware converter it can be found here

http://www.vmware.com/download/converter/

i used VMWARE convertor to convert the symantec sv2i file to a VMWARE file

If you're still having problems it may be a windows 2000 issue or bad blocks.  What type of error are you getting at the BSOD prompt? Can you boot into safe mode?

the usual blue screen of death - stating reboot if its the first time you have seen it or remove any newly installed drivers etc...

does the same in safe mode

Is it worth trying the image using Vmware SERVER?

vmware server will do the same. few things I would try.

1.  Do a chkdsk /f on the windows 2000 server before you do an image
2.  Try to do a repair on the virtual machine with a windows 2000 server CD

will a check disk run ok on a VMWARE image?

We need to run  chkdsk /f on the current windows 2000 server to see if we can fix any bad sectors/blocks

hmmmm try a defrag too.