Latitude E5440 Win7 image issues



  • Hello,

    I am using FOG 1.2.0 on Elementary OS 0.2.1, which is built on Ubuntu 12.04 and I have the latest Tom Elliot kernels. I have FOG installed and it is working properly but I am having a problem when I capture and deploy an image FOG is resizing the hard drive. I know it is supposed to do that so that it can compress the image size but when I boot the master computer it has changed the OS Partition capacity size from 284.76GB to 34.65GB and the same thing happens when I boot an imaged computer. I am using two computers that have the same exact hardware. I have not been syspreping but I did run fogprep. I am trying to capture the hard drive as it comes from DELL and it has 3 partitons on it so, I had to capture the master image with Multiple Partition Image - Single Disk (Not Resizeable). Is there something that I am missing?

    Thanks,
    Reuben



  • When you Create A New Image within the Image Management, set image type to Multiple Partition Image - Single Disk (Not Resizable). This is my unattend.xml for Windows 7 Professional x86 and it does work with Dell Factory partition setup. What I did is registered the computer with the FOG server, booted the Dell factory install in win7, installed all the software I needed, put the unattend.xml in the C:\windows\system32\sysprep folder, syspreped, and started the image upload process.

    <?xml version=“1.0” encoding=“utf-8”?>
    <unattend xmlns=“urn:schemas-microsoft-com:unattend”>
    <settings pass=“windowsPE”>
    <component name=“Microsoft-Windows-Setup” processorArchitecture=“x86” publicKeyToken=“31bf3856ad364e35” language=“neutral” versionScope=“nonSxS” xmlns:wcm="[url]http://schemas.microsoft.com/WMIConfig/2002/State[/url]" xmlns:xsi="[url]http://www.w3.org/2001/XMLSchema-instance[/url]">
    <EnableFirewall>false</EnableFirewall>
    <EnableNetwork>true</EnableNetwork>
    <UseConfigurationSet>true</UseConfigurationSet>
    </component>
    </settings>
    <settings pass=“generalize”>
    <component name=“Microsoft-Windows-Security-SPP” processorArchitecture=“x86” publicKeyToken=“31bf3856ad364e35” language=“neutral” versionScope=“nonSxS” xmlns:wcm="[url]http://schemas.microsoft.com/WMIConfig/2002/State[/url]" xmlns:xsi="[url]http://www.w3.org/2001/XMLSchema-instance[/url]">
    <SkipRearm>1</SkipRearm>
    </component>
    <component name=“Microsoft-Windows-PnpSysprep” processorArchitecture=“x86” publicKeyToken=“31bf3856ad364e35” language=“neutral” versionScope=“nonSxS” xmlns:wcm="[url]http://schemas.microsoft.com/WMIConfig/2002/State[/url]" xmlns:xsi="[url]http://www.w3.org/2001/XMLSchema-instance[/url]">
    <PersistAllDeviceInstalls>true</PersistAllDeviceInstalls>
    </component>
    </settings>
    <settings pass=“specialize”>
    <component name=“Microsoft-Windows-Deployment” processorArchitecture=“x86” publicKeyToken=“31bf3856ad364e35” language=“neutral” versionScope=“nonSxS” xmlns:wcm="[url]http://schemas.microsoft.com/WMIConfig/2002/State[/url]" xmlns:xsi="[url]http://www.w3.org/2001/XMLSchema-instance[/url]">
    <ExtendOSPartition>
    <Extend>true</Extend>
    </ExtendOSPartition>
    </component>
    <component name=“Microsoft-Windows-Security-SPP-UX” processorArchitecture=“x86” publicKeyToken=“31bf3856ad364e35” language=“neutral” versionScope=“nonSxS” xmlns:wcm="[url]http://schemas.microsoft.com/WMIConfig/2002/State[/url]" xmlns:xsi="[url]http://www.w3.org/2001/XMLSchema-instance[/url]">
    <SkipAutoActivation>true</SkipAutoActivation>
    </component>
    <component name=“Microsoft-Windows-Shell-Setup” processorArchitecture=“x86” publicKeyToken=“31bf3856ad364e35” language=“neutral” versionScope=“nonSxS” xmlns:wcm="[url]http://schemas.microsoft.com/WMIConfig/2002/State[/url]" xmlns:xsi="[url]http://www.w3.org/2001/XMLSchema-instance[/url]">
    <ComputerName>Computer Name</ComputerName>
    <DisableAutoDaylightTimeSet>false</DisableAutoDaylightTimeSet>
    <ShowWindowsLive>false</ShowWindowsLive>
    <TimeZone>(GMT-06:00) Central Time (US and Canada)</TimeZone>
    </component>
    </settings>
    <settings pass=“oobeSystem”>
    <component name=“Microsoft-Windows-International-Core” processorArchitecture=“x86” publicKeyToken=“31bf3856ad364e35” language=“neutral” versionScope=“nonSxS” xmlns:wcm="[url]http://schemas.microsoft.com/WMIConfig/2002/State[/url]" xmlns:xsi="[url]http://www.w3.org/2001/XMLSchema-instance[/url]">
    <InputLocale>en-us</InputLocale>
    <SystemLocale>en-us</SystemLocale>
    <UILanguage>en-us</UILanguage>
    <UILanguageFallback>en-us</UILanguageFallback>
    <UserLocale>en-us</UserLocale>
    </component>
    <component name=“Microsoft-Windows-Shell-Setup” processorArchitecture=“x86” publicKeyToken=“31bf3856ad364e35” language=“neutral” versionScope=“nonSxS” xmlns:wcm="[url]http://schemas.microsoft.com/WMIConfig/2002/State[/url]" xmlns:xsi="[url]http://www.w3.org/2001/XMLSchema-instance[/url]">
    <OOBE>
    <HideEULAPage>true</HideEULAPage>
    <NetworkLocation>Work</NetworkLocation>
    <ProtectYourPC>3</ProtectYourPC>
    <SkipMachineOOBE>true</SkipMachineOOBE>
    <SkipUserOOBE>true</SkipUserOOBE>
    <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
    </OOBE>
    <TimeZone>(GMT-06:00) Central Time (US and Canada)</TimeZone>
    <ShowWindowsLive>false</ShowWindowsLive>
    </component>
    </settings>
    <cpi:OfflineImage cpi:source=“catalog:c:/images/install_windows 7 professional.clg” xmlns:cpi=“urn:schemas-microsoft-com:cpi” />
    </unattend>



  • I was able to resolve the issue I was having by creating a unattend.xml and using diskgenius on the Hiren’s BootCD. The diskgenius allowed me to see the empty space on the drive and it allowed the space to become unallocated. Once I did that I uploaded the image and then downloaded it to another computer with the same hardware without any problems.

    I followed this guide, [url]http://forums.overclockers.com.au/showthread.php?t=1016213[/url], to some degree. Plus I added the option to extend the OS partition and persistalldeviceinstalls.

    Hope this helps someone else in the future.



  • Ok. Is there a way to fix the issue so that I can us the factory image with the recovery partition?


  • Developer

    well, you said this was a factory image. we recommend NOT using factory images because they tend to do some pretty non-standard things that can cause funny behaviours



  • Yes. When I boot into Windows I am not given the option to extend the disk because it is seeing it as a 34.65gb hard drive. Even though, I can see 284.76gb capacity in disk managment.


  • Developer

    it resized the disk using Multiple Partition Image - Single Disk (Not Resizeable)?


 

423
Online

41.8k
Users

12.3k
Topics

115.9k
Posts