Hello,
I went out and checked queried broadly on this and I can find references to
this exact error message even when using Ghost and not using sysprep. The
answer is to use sysprep or to change the mounteddevices registry entries
that are pointing to the wrong drive letter. You can use mountvol.exe to
list the volume guids on each drive, if the guids are different as they
should be, then they are assigned different drive letters in Windows.
Thanks,
Darrell Gorter[MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights
--------------------
| X-Tomcat-ID: 22975525
| References: <
[email protected]>
<
[email protected]>
<
[email protected]>
| MIME-Version: 1.0
| Content-Type: text/plain
| Content-Transfer-Encoding: 7bit
| From: (e-mail address removed) ("Darrell Gorter[MSFT]")
| Organization: Microsoft
| Date: Sat, 14 Feb 2004 00:56:55 GMT
| Subject: RE: Ghost from Slow IDE to SCSI caused License problem
| X-Tomcat-NG: microsoft.public.windowsxp.setup_deployment
| Message-ID: <
[email protected]>
| Newsgroups: microsoft.public.windowsxp.setup_deployment
| Lines: 84
| Path: cpmsftngxa07.phx.gbl
| Xref: cpmsftngxa07.phx.gbl
microsoft.public.windowsxp.setup_deployment:102367
| NNTP-Posting-Host: tomcatimport2.phx.gbl 10.201.218.182
|
| Hello,
| So does Ghost copy over the drive guid and replace it on the new drive
| after you add it back in? Guids should never be duplicated in a system
or
| you will have other problems. The drive letter is based off the registry
| entries, they determine what the drive letter is The drive letter isn't
| stored anywhere on the drive only the guid could be on the drive. I have
| seen other people run Ghost and have this exact problem and it was thte
| drive letter.
| If you run sysprep, we strip out the registry entries for the drive
letters
| and the guids, so we do not have this issue, then the new guid is
assigned
| to the drive on first boot and since the registry does not contain any
| guids, the drive letters are re-enumerated by the OS on first boot.
Since
| the guid is removed the first available drive letter for hard drives is
C,
| the first drive is given the drive of C and it works.
|
| This is the exact error code(0x80090006) that is given if the drive
letter
| is incorrect after a reboot. Licensing is only the messenger in these
| cases, the dlls needed to read the licensing info from the drive are not
| loaded because they are not at the expected location.. This isn't a
| controller error.
|
| Open the registry key under mounteddevices what is there? How many
drives
| are listed and how many are in your system?
|
| Thanks,
| Darrell Gorter[MSFT]
|
| This posting is provided "AS IS" with no warranties, and confers no rights
| --------------------
| | Thread-Topic: Ghost from Slow IDE to SCSI caused License problem
| | thread-index: AcPyaVSg0D9cb85bR4+xYhi2n53f1A==
| | X-Tomcat-NG: microsoft.public.windowsxp.setup_deployment
| | From: =?Utf-8?B?SG9vdGFu?= <
[email protected]>
| | References: <
[email protected]>
| <
[email protected]>
| | Subject: RE: Ghost from Slow IDE to SCSI caused License problem
| | Date: Fri, 13 Feb 2004 11:41:10 -0800
| | Lines: 5
| | Message-ID: <
[email protected]>
| | MIME-Version: 1.0
| | Content-Type: text/plain;
| | charset="Utf-8"
| | Content-Transfer-Encoding: 7bit
| | X-Newsreader: Microsoft CDO for Windows 2000
| | Content-Class: urn:content-classes:message
| | Importance: normal
| | Priority: normal
| | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| | Newsgroups: microsoft.public.windowsxp.setup_deployment
| | Path: cpmsftngxa07.phx.gbl
| | Xref: cpmsftngxa07.phx.gbl
| microsoft.public.windowsxp.setup_deployment:102335
| | NNTP-Posting-Host: tk2msftcmty1.phx.gbl 10.40.1.180
| | X-Tomcat-NG: microsoft.public.windowsxp.setup_deployment
| |
| | Darrell,
|
| Thanks for the input. I have done it a lot before when we upgraded our
| systems that had Windows2000 pro and windows 2000 server. But somehow
the
| licensing engine in WindowsXP is creating this problem. So I'm pretty
sure
| it's not the controller being recognized. When we use ghost it keeps that
| drive letter intact, if you take the old drive out before turning on the
| machine.
|
| I had ghosted this same machinea month ago, when the OS was on a slower
| SCSI drive and I moved the OS onto an SATA (serial ATA) drive thinking it
| would be fast. But it wasn't fast enough. So now I'm trying to ghost it
| onto a fast SCSI drive, but it gives me this error. I wonder if it's
| because of the SerialATA.
| |
|
|