I believe you should be able to use single partition with Windows 7, if you choose OS type Vista. Both when uploading your image and deploying. This way, FOG does not expect to find the system partition, and you can still choose resizable, as you want.

did you find a soluvtion to this problem im getting the same error in windows 7

I am doing the same thing. I actually have modified the SAD2 script to determine the make and model of the machine and use custom driver packs for each machine. I am finishing up the script and testing it on a few more of our models. When I get it complete I can post, along with a howto on the way I have it set up and running. I found that you do not need to have the machine logged into run it, I have it so that in case it reboots during the middle it will even resume the install so that you make sure all the drives get installed.

[quote=“Fatikis, post: 13011, member: 7852”]I’m having the same problem with the exact same model of computer, and I’m newish to FOG. We recently ordered these computers all with windows7 preinstalled.

This may be a silly question, but if I do a fresh install of windows 7 on the computer and upload a new image will I be able to image the computers with the 3 partitions?[/quote]

I am assuming you mean that with a fresh install and default 2 partitions created by windows 7 install, can you the take the image up and deploy it to a computer of the same make and model that currently has 3 partitions?

If that is so, then yes you can. The partitions on the client computer will be deleted and you will end up with the same number of partitions that are on your image.

Have you used sysprep, and what version of fog are you using?

Imaged over 250 desktops with Fog this summer (HP - Win 7 Pro 64bit) without any issues. We skip fogprep but user sysprep with an unattend.xml.

[quote=“madeyem, post: 12683, member: 797”]If you want to use Sysprep with an unattend.xml, you have to run a batch script, in which you specify the location of the unattend.xml. Starting Sysprep via the GUI will always run the default Sysprep process.

For example, create a batch file with the following content:

[CODE]@echo off
cd c:\windows\system32\sysprep
sysprep /oobe /generalize /shutdown /unattend:C:*path to the unattend.xml*\unattend.xml[/CODE][/quote]

I don’t use a .bat file I just call it from command prompt and I point to the unattend but it is still not working right.

Didn’t look like it was running, but this lovely thread:

[url]http://fogproject.org/forum/threads/tftp-issues-but-fixable.779/[/url]

fixed the problem! Thanks for your help 🙂

[quote=“Steve Dearman, post: 10452, member: 3124”]This is similar to the problem I have 50 oem machines with label keys on top so I created a script to read the serial number from the bios and change the key and activate.

[CODE]’ Use “wmic bios get serialnumber” to get the serial number if its not documented elsewhere.
Dim sSerial
Dim sKey
set cnn = createobject(“adodb.connection”)
set rs = createobject(“adodb.recordset”)
Set objWMIService = GetObject(“winmgmts:” _
& “{impersonationLevel=impersonate}!\.\root\cimv2”)
Set colBIOS = objWMIService.ExecQuery _
(“Select * from Win32_BIOS”)
For each objBIOS in colBIOS
sSerial = objBIOS.SerialNumber
Next
cnn.open “Provider=Microsoft.Jet.OLEDB.4.0; Data Source=.; Extended Properties=”“text;HDR=Yes;”“”
rs.open “select * from serials.csv where Serial='” & sSerial & “'”, cnn, 3, 3

Do until rs.eof
sKey = rs.fields.item(“key”).value
rs.MoveNext
loop
If Not IsEmpty(sKey) Then
Dim objShell
Set objShell = Wscript.CreateObject(“WScript.Shell”)
objShell.Run "c:\windows\system32\cscript c:\windows\system32\slmgr.vbs /ipk " & sKey,1,TRUE
objShell.Run “c:\windows\system32\cscript c:\windows\system32\slmgr.vbs /ato”,1,TRUE
Set objShell = Nothing
End If

[/CODE]

This reads a csv file called serials so its easy to update.

[CODE]Serial,Key
HKCF91LC102731,abcde-fghij-klmno-pqrst-uvwxy
[/CODE]

I call this from the setupcomplete.cmd as outlined in the main windows 7 fog guide so everything is activated with the correct key right from the word go[/quote]

Hi Steve,
Question on your script:

Do you save your script as .cmd or .vbs?
2.What path do you placed your script and cvs file? ( Is it the same location as setupcomplete.cmd?)
thanks in advanced

Didn’t get much help with this, but should this happen to someone else the chkdsk did restore all my files. so happy happy joy joy (Ren and Stimpy style)
😄

[LEFT]When Kyle fully explains this you will see it is an amazing and complete setup!![/LEFT]
[LEFT] [/LEFT]
[LEFT]Have been using it for quite a while now, cheers buddy!![/LEFT]

i was talking about GPO in windows.

We have over 100 printers and FOG we felt would be fine for smaller installations.

[url]http://blog.ibuddy.info/index.php/2011/05/fog-29-my-windows-7-guide-3264-bit-docv1/[/url]
is an A-Z manual

The only thing I can think of then is that maybe you don’t have the generic KMS key on your windows 8 host. Try changing it:-

[url]http://technet.microsoft.com/en-us/library/jj612867.aspx[/url]

Well I’m glad to hear it, have a good day!

See if this helps, [url]http://answers.microsoft.com/en-us/windows/forum/windows_vista-performance/disable-the-interactive-services-dialog-detection/ca139ba9-c96c-49af-bc09-83abc26f3f5d[/url]

Seems like they are done using this and you can disable the service that makes them pop up.

Here is the code for my 64 bit windows 7 XML
[CODE]<?xml version=“1.0” encoding=“utf-8”?>
<unattend xmlns=“urn:schemas-microsoft-com:unattend”>
<settings pass=“generalize”>
<component name=“Microsoft-Windows-Security-SPP” processorArchitecture=“amd64” publicKeyToken=“31bf3856ad364e35” language=“neutral” versionScope=“nonSxS” xmlns:wcm=“http://schemas.microsoft.com/WMIConfig/2002/State” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”>
<SkipRearm>1</SkipRearm>
</component>
</settings>
<settings pass=“specialize”>
<component name=“Microsoft-Windows-Deployment” processorArchitecture=“amd64” publicKeyToken=“31bf3856ad364e35” language=“neutral” versionScope=“nonSxS” xmlns:wcm=“http://schemas.microsoft.com/WMIConfig/2002/State” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”>
<ExtendOSPartition>
<Extend>true</Extend>
</ExtendOSPartition>
</component>
<component name=“Microsoft-Windows-Security-SPP-UX” processorArchitecture=“amd64” publicKeyToken=“31bf3856ad364e35” language=“neutral” versionScope=“nonSxS” xmlns:wcm=“http://schemas.microsoft.com/WMIConfig/2002/State” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”>
<SkipAutoActivation>true</SkipAutoActivation>
</component>
<component name=“Microsoft-Windows-Shell-Setup” processorArchitecture=“amd64” publicKeyToken=“31bf3856ad364e35” language=“neutral” versionScope=“nonSxS” xmlns:wcm=“http://schemas.microsoft.com/WMIConfig/2002/State” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”>
<ComputerName>*</ComputerName>
<CopyProfile>true</CopyProfile>
<ShowWindowsLive>false</ShowWindowsLive>
</component>
</settings>
<settings pass=“oobeSystem”>
<component name=“Microsoft-Windows-International-Core” processorArchitecture=“amd64” publicKeyToken=“31bf3856ad364e35” language=“neutral” versionScope=“nonSxS” xmlns:wcm=“http://schemas.microsoft.com/WMIConfig/2002/State” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”>
<InputLocale>en-us</InputLocale>
<SystemLocale>en-us</SystemLocale>
<UILanguage>en-us</UILanguage>
<UserLocale>en-us</UserLocale>
</component>
<component name=“Microsoft-Windows-Shell-Setup” processorArchitecture=“amd64” publicKeyToken=“31bf3856ad364e35” language=“neutral” versionScope=“nonSxS” xmlns:wcm=“http://schemas.microsoft.com/WMIConfig/2002/State” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”>
<AutoLogon>
<Password>
<Value>bQBwAHMAdABlAGMAaABzAFAAYQBzAHMAdwBvAHIAZAA=</Value>
<PlainText>false</PlainText>
</Password>
<Enabled>true</Enabled>
<LogonCount>2</LogonCount>
<Username>user</Username>
</AutoLogon>
<FirstLogonCommands>
<SynchronousCommand wcm:action=“add”>
<CommandLine>cscript //b c:\windows\system32\slmgr.vbs /ato</CommandLine>
<Order>1</Order>
<RequiresUserInput>false</RequiresUserInput>
</SynchronousCommand>
<SynchronousCommand wcm:action=“add”>
<CommandLine>cscript.exe //b “C:\Program Files (x86)\Microsoft Office\Office14\OSPP.VBS” /act</CommandLine>
<Order>2</Order>
<RequiresUserInput>false</RequiresUserInput>
</SynchronousCommand>
</FirstLogonCommands>
<OOBE>
<HideEULAPage>true</HideEULAPage>
<NetworkLocation>Work</NetworkLocation>
<ProtectYourPC>1</ProtectYourPC>
<SkipMachineOOBE>true</SkipMachineOOBE>
<SkipUserOOBE>true</SkipUserOOBE>
</OOBE>
<UserAccounts>
<AdministratorPassword>
<Value>bQBwAHMAdABlAGMAaABzAEEAZABtAGkAbgBpAHMAdAByAGEAdABvAHIAUABhAHMAcwB3AG8AcgBkAA==</Value>
<PlainText>false</PlainText>
</AdministratorPassword>
</UserAccounts>
<RegisteredOrganization>Organization</RegisteredOrganization>
<RegisteredOwner>Name</RegisteredOwner>
</component>
</settings>
<cpi:offlineImage cpi:source=“wim:c:/users/cgalati/desktop/win7/sources/install.wim#Windows 7 Enterprise” xmlns:cpi=“urn:schemas-microsoft-com:cpi” />
</unattend>
[/CODE]

hmmm, i will give a try to your proposition as soon as possible. Thanks for the trick christopher 🙂

You create three separate winnt.sif files for each of the PC’s and feed them into each deployment. They need to be copied to the image before the MININT setup after sysprep.

[quote=“Alan Reeves, post: 11442, member: 3679”]Hi,
I am brand new to FOG. I have installed a test system under Ubuntu 10.04, uploaded an XP SP3 image and successfully deployed to three machines. FOG looks superb, thanks and well done to all who have contributed.
I have a question about regular, unattended deployment to multiple machines.

First, some background. I am a volunteer IT administrator for an independent school in the UK. I’m retired now, but in my professional career I was an IBM mainframe systems and assenbler programmer. That is by way of explaining that my knowlege of the Linux and pc world is limited (but I can learn quickly!).

The school has about 25 Dell pc’s, running XP PRO SP3. These are all second-hand, donated from businesses, so all the machines have unique product licences and COA stickers (ie there’s no Volume Licence key). Up to now I have been manually deploying a single image from a master machine, by removing the hard drives and cloning them (with Clonezilla and other tools). This is hard work but generally I don’t have problems, as the machines are identical. However, occasionally I have been prompted to re-active the XP licence, and I don’t really understand the circumstances in which this happens I’m looking to using FOG to do regular network deployments.

Now, my question. Everything I have read makes me understand that I should use SYSPREP to prepare my common image. But, if I understand correctly, I can only set a single product licence in Sysprep? I want to achieve completely unattended deployment, so don’t want the deployed systems prompting for licence activation - or, if it does, I want some automated way of replying to the prompts with the correct (unique) licence key (side question - could I use “AutoIt” for this?).

It might help to know that I am not using a domain controller, the pc’s are simply in a workgroup, with a login script to map to a shared NAS drive for student folder access.

Thanks for bearing with me. I hope I have correctly explained the issue I have, and thanks in advance for your assistance.

Regards
Alan Reeves[/quote]