Changing disk signature for Windows 2003 64bit OS.

chongbenkee, no one seems to have any answers
can this very basic help assist you.
I donot have the expertise either so am only offering some sourced information.
Converting Partition Table Styles
Using the CONVERT command, DiskPart can help you change partition table styles from MSR to GPT or from GPT to MSR. Changing partition table styles is useful when you
Move disks between X86-based computers and IA64-based computers
http://book.itzero.com/read/microsoft/Microsoft.Press.Microsoft.Windows.Command-Line.Administrators.Pocket.Consultant.Apr.2004.eBook-DDU_html/8411/DDU0044.html
--------------------------------------------
operating system; for native EFI boot,. A 64-bit operating system .... Windows Boot Environment uses disk signatures to identify partitions on disks
http://download.microsoft.com/download/5/b/9/5b97017b-e28a-4bae-ba48-174cf47d23cd/CPA051_WH06.ppt

Thanks but seen like the article is not really helping me. We faced the Disk Signature issue even after rebuild the cluster. From google also I can't find a way to change the disk signature for 64bit OS.

Sorry I have no other suggestions to do that.
It sounds to me something that is not possible under the circumstances.
Migrating from 32 to 64.
(1)
Q (quorum) drive for our cluster services need to be migrated as well.
(2)
We have no probelem with 32bit OS as we can use dumpcfg.exe to change the disk signature once quorum drive migrate
(3)
but this tool can't be used with 64bit OS.
(4)
Kindly advise how should we can the disk sign for 64bit ver OS< ???

Hi,

I think you has missunderstood me. Not migrating from 32 to 64 bit but only with 64 bit OS. No changes on OS, we only change the SAN (from EVA6000 to EVA8000) so all the SAN drive on that server need to be reconfigured/remap. Problem faced when it come to migrate the Q (quarom) drive. It still detected the old drive (which is on EVA6000) as the cluster is referring to the disk signature. We need to change the disk singnature. We have a solution for 32 bit OS which is using dumpcfg.exe but not for 64bit OS.

Hi all,

We managed to fix it by updating the registry to point to new disk signature. TQ.

HI chongbenkee - we're about to migrate our (32-bit) 4-node MS Cluster from our EVA 6000 to an 8100 - please could you outline the process you used?  Did you use CA (Continuous Access) to replicate the data on your LUN's to the new EVA?  Were you running Exchange on your cluster at all?  In my mind, the process would be:-

Create new groups/LUN's etc. on EVA 8100
Configure CA to replicate the data across
Take all cluster resources offline, and move them to one of the nodes, shutting down the other 3 nodes
Shut down the fourth node, and let CA finish replicating so data is consistent
Unpresent the old LUN's, and present the new ones, to all cluster nodes
Boot up the cluster node again that has all the resources currently on it
Use Microsoft Cluster Recovery Tool or dumpcfg.exe, to change the disk signatures on the new disks to match the old ones
Rename drive letters where necessary
Bring the resources online
Move the resources back to their original nodes

What do you think?  Any suggestions/corrections would be really appreciated!

Hi there

My comment was really another question in itself... sorry for hijacking the thread.

Anyway if anyone was interested - we had no issues with disk signatures with our EVA upgrade.  CA replicates at block level, so all disk signatures were carried across, so the migration onto the new disks was straightforward.  We did all of our clusters LUN's at the same time, with no issues.

thanks
Raymond

Hi Raymond,

We have no problem with 32bit OS as well but unfortunately its not running fine with 64 bit. But we managed to do it by changing the registry.