After you use the BIOS setup of a Windows 7-based computer or a Windows Vista-based computer to change the Serial Advanced Technology Attachment (SATA) mode of the boot drive to use either the Advanced Host Controller Interface (AHCI) specification or redundant array of independent disks (RAID) features, you receive the following error message when the computer is restarted:
STOP 0x0000007B INACCESSABLE_BOOT_DEVICE
Copy the following information into Notepad, and then save the file on a 3.5-inch disk. Name the file Mergeide.reg, without the .txt file name extension. Although Microsoft does not support this method, you can import or merge the required registry entries, and copy the drivers beforehand to support all IDE controllers that are natively supported by Windows XP. Note that although this method might enable the relocated system disk to start successfully, other hardware differences can lead to other problems.
This solution provides support for IDE controllers whose PnP-ID matches one of the PnP-IDs in the following list. However, if you want to determine beforehand the IDE controllers that are used in your current and backup computers, you can search the %SystemRoot%\Setupapi.log file for the PnP-ID that is detected while the Setup program is running.
After you determine the PnP-IDs that are used in your computers, you can choose to merge or to populate the registry with only the PnP-IDs that you need.
The following list shows the PnP-IDs of natively supported IDE controllers in Windows XP: ********** Start copy here **********
I thank you for your response. The OEM image where those entries appear is set to AHCI in the BIOS. My imaged computer is also set that way. Since that is the case, why do the entries appear on the OEM one if it is as you said (should only appear in ATA?)
The imaged system appears to be functioning fine. There are no errors about the drive when it boots. The entries simply don't appear in device manager and I want to make sure this won't be an issue.
Imaging is not supported by Dell or Microsoft. Sysprep scripted installs are Those entries are wrong and thats why they don't show up. You will have to have the same DRIVERS and INF files and Registry Entires.
I'm not sure what you mean by "not supported by" - I understand that officially from Dell I'm not getting help on imaging, but certainly Microsoft is supportive of imaging, I'm using their product to image the computers. Now if you are saying those entries are wrong, my question is why were they on the computers when they showed up for Dell. I'm perfectly fine with not getting them back on the imaged machine, as long as it doesn't negatively affect anything.
When you deploy a duplicated or imaged Windows installation, it is required that the System Preparation (Sysprep) tool is used before the capture of the image. Sysprep prepares an installation of Microsoft Windows for duplication, auditing, and customer delivery. For OLD Microsoft Windows Sysprep is included with the latest service pack Deploy.cab. For later versions of Windows, Sysprep is included with the operating system, and Sysprep is located in the following folder:
%windir%\system32\sysprep
Sysprep is responsible for removing system-specific data from Windows, such as the Computer SID. During installation of Windows, a computer SID is computed to contain a statistically unique 96-bit number. The computer SID is the prefix of the user account and group account SIDs that are created on the computer. The computer SID is concatenated together with the Relative ID (RID) of the account to create the account's unique identifier.
The following example displays the SIDs for four local user accounts. Notice that only the last four digits are incremented as new accounts are added.
HKEY_USERS on Local Machine
S-1-5-21-191058668-193157475-1542849698-500 Administrator S-1-5-21-191058668-193157475-1542849698-1000 User 1a S-1-5-21-191058668-193157475-1542849698-1001 User 2 S-1-5-21-191058668-193157475-1542849698-1002 User 3
Cloning or duplicating an installation without taking the recommended steps could lead to duplicate SIDs. For removable media, a duplicate SID might give an account access to files even though NTFS permissions for the account specifically deny access to those files. Because the SID identifies both the computer or domain and the user, unique SIDs are necessary to maintain support for current and future programs.
In addition to the computer SID, many other components and features must be cleaned up, generalized, or specialized in order to be imaged. Some examples include the following:
Event logs
Network settings
Windows Media player settings
Shell settings
Licensing
Note This is not a comprehensive list.
Microsoft support the following operating systems that are prepared by using the Sysprep utility and then imaged:
Windows NT Workstation 4.0
Windows NT Server 4.0 (stand-alone server, not primary domain controllers or backup domain controllers)
Windows 2000 Professional
Windows 2000 Server (must be imaged before you run DCPromo)
Windows 2000 Advanced Server
Windows XP Home Edition
Windows XP Professional
Windows Server 2003, Standard Edition
Windows Server 2003, Datacenter Edition
Windows Server 2003, Enterprise Edition
Windows Server 2003, Web Edition
All versions of Windows Vista
All versions of Windows Server 2008
All versions of Windows 7
All versions of Windows Server 2008 R2
All versions of Windows 8
All versions of Windows Server 2012
Neither Dell Nor Microsoft provide support for computers that are set up by using SID-duplicating tools other than the System Preparation tool. For example, this includes the following:
The Microsoft Deployment Toolkit (MDT) is not supported here by Dell. There is support available for this but its not free.
When you deploy a duplicated or imaged Windows installation, it is required that the System Preparation (Sysprep) tool is used before the capture of the image.
Cloning images and then running sysprep is not the same thing.
I'm not sure if you read my question. I'm not merely cloning an OEM image. I'm using Microsoft MDT to image a computer with an image that I previously had created. The systems ARE being sysprepped during the imaging process. What I was trying to do was make sure I had all the drivers that were necessary in my MDT OOB drivers for this model, the optiplex 3020. I thought I had them all, but then found that that the entries mentioned in my initial post were on the OEM image but not on my imaged computer as listed devices.
speedstep
9 Legend
•
47K Posts
1
January 23rd, 2015 09:00
Those are there or NOT depending on SATA Operation settings. When AHCI they are not there when ATA they are.
http://support.microsoft.com/kb/922976
After you use the BIOS setup of a Windows 7-based computer or a Windows Vista-based computer to change the Serial Advanced Technology Attachment (SATA) mode of the boot drive to use either the Advanced Host Controller Interface (AHCI) specification or redundant array of independent disks (RAID) features, you receive the following error message when the computer is restarted:
Although Microsoft does not support this method, you can import or merge the required registry entries, and copy the drivers beforehand to support all IDE controllers that are natively supported by Windows XP. Note that although this method might enable the relocated system disk to start successfully, other hardware differences can lead to other problems.
This solution provides support for IDE controllers whose PnP-ID matches one of the PnP-IDs in the following list. However, if you want to determine beforehand the IDE controllers that are used in your current and backup computers, you can search the %SystemRoot%\Setupapi.log file for the PnP-ID that is detected while the Setup program is running.
After you determine the PnP-IDs that are used in your computers, you can choose to merge or to populate the registry with only the PnP-IDs that you need.
The following list shows the PnP-IDs of natively supported IDE controllers in Windows XP:
********** Start copy here **********
Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\primary_ide_channel] "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" "Service"="atapi" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\secondary_ide_channel] "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" "Service"="atapi" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\*pnp0600] "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" "Service"="atapi" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\*azt0502] "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" "Service"="atapi" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\gendisk] "ClassGUID"="{4D36E967-E325-11CE-BFC1-08002BE10318}" "Service"="disk" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#cc_0101] "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" "Service"="pciide" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_0e11&dev_ae33] "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" "Service"="pciide" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1039&dev_0601] "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" "Service"="pciide" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1039&dev_5513] "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" "Service"="pciide" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1042&dev_1000] "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" "Service"="pciide" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_105a&dev_4d33] "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" "Service"="pciide" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1095&dev_0640] "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" "Service"="pciide" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1095&dev_0646] "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" "Service"="pciide" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1095&dev_0646&REV_05] "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" "Service"="pciide" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1095&dev_0646&REV_07] "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" "Service"="pciide" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1095&dev_0648] "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" "Service"="pciide" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1095&dev_0649] "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" "Service"="pciide" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1097&dev_0038] "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" "Service"="pciide" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_10ad&dev_0001] "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" "Service"="pciide" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_10ad&dev_0150] "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" "Service"="pciide" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_10b9&dev_5215] "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" "Service"="pciide" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_10b9&dev_5219] "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" "Service"="pciide" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_10b9&dev_5229] "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" "Service"="pciide" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1106&dev_0571] "Service"="pciide" "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_1222] "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" "Service"="intelide" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_1230] "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" "Service"="intelide" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_2411] "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" "Service"="intelide" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_2421] "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" "Service"="intelide" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_7010] "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" "Service"="intelide" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_7111] "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" "Service"="intelide" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_7199] "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" "Service"="intelide" ;Add driver for Atapi (requires Atapi.sys in Drivers directory) [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\atapi] "ErrorControl"=dword:00000001 "Group"="SCSI miniport" "Start"=dword:00000000 "Tag"=dword:00000019 "Type"=dword:00000001 "DisplayName"="Standard IDE/ESDI Hard Disk Controller" "ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\ 52,00,49,00,56,00,45,00,52,00,53,00,5c,00,61,00,74,00,61,00,70,00,69,00,2e,\ 00,73,00,79,00,73,00,00,00 ;Add driver for intelide (requires intelide.sys in drivers directory) [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\IntelIde] "ErrorControl"=dword:00000001 "Group"="System Bus Extender" "Start"=dword:00000000 "Tag"=dword:00000004 "Type"=dword:00000001 "ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\ 52,00,49,00,56,00,45,00,52,00,53,00,5c,00,69,00,6e,00,74,00,65,00,6c,00,69,\ 00,64,00,65,00,2e,00,73,00,79,00,73,00,00,00 ;Add driver for Pciide (requires Pciide.sys and Pciidex.sys in Drivers directory) [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PCIIde] "ErrorControl"=dword:00000001 "Group"="System Bus Extender" "Start"=dword:00000000 "Tag"=dword:00000003 "Type"=dword:00000001 "ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\ 52,00,49,00,56,00,45,00,52,00,53,00,5c,00,70,00,63,00,69,00,69,00,64,00,65,\ 00,2e,00,73,00,79,00,73,00,00,00hipsterdoofus
1 Rookie
•
20 Posts
0
January 23rd, 2015 10:00
I thank you for your response. The OEM image where those entries appear is set to AHCI in the BIOS. My imaged computer is also set that way. Since that is the case, why do the entries appear on the OEM one if it is as you said (should only appear in ATA?)
The imaged system appears to be functioning fine. There are no errors about the drive when it boots. The entries simply don't appear in device manager and I want to make sure this won't be an issue.
speedstep
9 Legend
•
47K Posts
0
January 24th, 2015 18:00
Imaging is not supported by Dell or Microsoft. Sysprep scripted installs are Those entries are wrong and thats why they don't show up. You will have to have the same DRIVERS and INF files and Registry Entires.
hipsterdoofus
1 Rookie
•
20 Posts
0
January 25th, 2015 13:00
I'm not sure what you mean by "not supported by" - I understand that officially from Dell I'm not getting help on imaging, but certainly Microsoft is supportive of imaging, I'm using their product to image the computers. Now if you are saying those entries are wrong, my question is why were they on the computers when they showed up for Dell. I'm perfectly fine with not getting them back on the imaged machine, as long as it doesn't negatively affect anything.
speedstep
9 Legend
•
47K Posts
0
January 28th, 2015 10:00
Ghost and other Cloning Tools are not supported.
When you deploy a duplicated or imaged Windows installation, it is required that the System Preparation (Sysprep) tool is used before the capture of the image. Sysprep prepares an installation of Microsoft Windows for duplication, auditing, and customer delivery. For OLD Microsoft Windows Sysprep is included with the latest service pack Deploy.cab. For later versions of Windows, Sysprep is included with the operating system, and Sysprep is located in the following folder:
Sysprep is responsible for removing system-specific data from Windows, such as the Computer SID. During installation of Windows, a computer SID is computed to contain a statistically unique 96-bit number. The computer SID is the prefix of the user account and group account SIDs that are created on the computer. The computer SID is concatenated together with the Relative ID (RID) of the account to create the account's unique identifier.
The following example displays the SIDs for four local user accounts. Notice that only the last four digits are incremented as new accounts are added.
S-1-5-21-191058668-193157475-1542849698-500 Administrator
S-1-5-21-191058668-193157475-1542849698-1000 User 1a
S-1-5-21-191058668-193157475-1542849698-1001 User 2
S-1-5-21-191058668-193157475-1542849698-1002 User 3
Cloning or duplicating an installation without taking the recommended steps could lead to duplicate SIDs. For removable media, a duplicate SID might give an account access to files even though NTFS permissions for the account specifically deny access to those files. Because the SID identifies both the computer or domain and the user, unique SIDs are necessary to maintain support for current and future programs.
For more information about issues that might occur if you clone an installation of Windows 8 or of Windows Server 2012, go to the "Windows 8 and Windows Server 2012 specific information" section.
In addition to the computer SID, many other components and features must be cleaned up, generalized, or specialized in order to be imaged. Some examples include the following:
Note This is not a comprehensive list.
Microsoft support the following operating systems that are prepared by using the Sysprep utility and then imaged:
Neither Dell Nor Microsoft provide support for computers that are set up by using SID-duplicating tools other than the System Preparation tool. For example, this includes the following:
speedstep
9 Legend
•
47K Posts
1
January 28th, 2015 11:00
The Microsoft Deployment Toolkit (MDT) is not supported here by Dell. There is support available for this but its not free.
When you deploy a duplicated or imaged Windows installation, it is required that the System Preparation (Sysprep) tool is used before the capture of the image.
Cloning images and then running sysprep is not the same thing.
hipsterdoofus
1 Rookie
•
20 Posts
0
January 28th, 2015 11:00
I'm not sure if you read my question. I'm not merely cloning an OEM image. I'm using Microsoft MDT to image a computer with an image that I previously had created. The systems ARE being sysprepped during the imaging process. What I was trying to do was make sure I had all the drivers that were necessary in my MDT OOB drivers for this model, the optiplex 3020. I thought I had them all, but then found that that the entries mentioned in my initial post were on the OEM image but not on my imaged computer as listed devices.
hipsterdoofus
1 Rookie
•
20 Posts
0
January 28th, 2015 13:00
Yes, that's exactly what I'm doing. Before I capture my image, it is sysprepped. When I deploy it, I Inject drivers.