Thanks, I got 2 images uploaded to the server yesterday. I used a sample unattend.xml file for the sysprep image for now until I can work on designing my own unattend.xml file for imaging the systems.

2cool4me4 is correct; this is the design of the service and won’t cause any issues. The new service that is in development will most likely check if the computer is already joined to the domain first before attempting.

Have you changed DHCP options 66 and 67 to point to your FOG server? [url]http://www.fogproject.org/wiki/index.php/Modifying_existing_DHCP_server_to_work_with_FOG[/url]

Ok, sorry for delay, here is what we use to make win7 join Samba NT4 domain (maybe it helps somebody):

after sysprep, fog automatically renames host (it’s done fairly early after sysprep, so there is little or perhaps no chance that computer will join domain with bad name), then it restarts and downloads associated snapin - I named it setup_complete_snapin - which contains 2 scripts:
[LIST=1]
[]setupcomplete.cmd
[]join_domain.ps1 (powershell script)
[/LIST]
SETUPCOMPLETE.CMD:
[CODE]
@echo off

rem delete unattend files
del /Q /F c:\windows\system32\sysprep\unattend.xml
del /Q /F c:\windows\panther\unattend.xml

rem delete dir with additional drivers (those which win didn’t install automatically - needs registry update for win to look here)
rd /S /Q c:\Drivers

rem win activation
cscript //b c:\windows\system32\slmgr.vbs /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
cscript //b C:\windows\system32\slmgr.vbs -ato

rem office 2010 activation
cscript “c:\Program Files\Microsoft Office\Office14\ospp.vbs” /act

rem registry changes
:: enable self deffense (registry protection) for NOD Endpoint Antivirus 5.0 - disabled before sysprep, because of sysprep crashes with this enabled
REG ADD “HKLM\SOFTWARE\ESET\ESET Security\CurrentVersion\Plugins\01000001\Profiles@My profile” /v selfdefense /t REG_DWORD /d 0x1 /f
:: for win7 to join Samba NT4 domain
REG ADD “HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanManWorkstation\Parameters” /v DomainCompatibilityMode /t REG_DWORD /d 0x1 /f
REG ADD “HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanManWorkstation\Parameters” /v DNSNameResolutionRequired /t REG_DWORD /d 0x0 /f
:: fixes problems with login (source: https://lists.samba.org/archive/samba/2010-October/158591.html)
REG ADD “HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Netlogon\Parameters” /v DisablePasswordChange /t REG_DWORD /d 0x1 /f

rem domain join
:: didn’t work without cd
cd \windows\temp\setup_complete_snapin
powershell set-executionpolicy remotesigned
powershell .\join_domain.ps1
powershell set-executionpolicy allsigned

rem extends partition to whole disk
diskpart /s .\diskpart.txt

:: sleep a la MS Windows 🙂
::ping -n 10 1.1.1.1

rem restart
shutdown -r -f -t 120

Exit
[/CODE]
For domain join, really needed are only sections: domain join, registry changes (for win7 to join Samba NT4 domain) and perhaps restart.

JOIN_DOMAIN.PS1:
[CODE]

user and pass - pass has to be in apostrophes, quotation marks didn’t work

$User = “DOMAIN\USER”
$Pass = ConvertTo-SecureString ‘PASSWORD’ -AsPlainText -Force

create credentials

$Credentials = New-Object -TypeName System.Management.Automation.PSCredential -ArgumentList $User,$Pass

join domain with loggin to file

#add-computer -domain DOMAIN -credential $Credentials 2>&1 > join_domain.log

join domain

add-computer -domain DOMAIN -credential $Credentials
[/CODE]

When you created your image, did you create it as a single disk resizable or a Multipartition image?

It sounds, to me, like you created a multipartition image and the mbr file is overwriting your disk. The partitions being generated on the new 790 system are telling me this?

Why you ask?

Because in 0.32 and even all the way thru 1.2.0, Windows 7 resizable would create one of two possible partitions on the disk, it never would have created a 3rd partition.

The first partition (if rec.img.000 exists) would be: 100MB starting at sector 2048 and ending at sector 208647.

The second partition (if both rec.img.000 and sys.img.000 exists) would be starting at sector 208648 until the end of the disk. There would never have been three partitions generated on the disk.

My guess, your 790 hard drive size is smaller than the 7010 hard drive size, and it’s because of this that you’re seeing the problems you are.

Sysprep is pulling the driver package on generalize. So I am still screwed.

[quote=“Frode Woldsund, post: 36206, member: 19014”]We finaly found a solution to our problem:
[url]http://fogproject.org/forum/threads/stuck-on-dev-sda.11105/[/url]

In Summary
Step 1: WebGui: Basic tasks -> Advanced tasks -> Upload - Debug
Step 2: run “fixparts” in the command prompt and type in “/dev/sda”(my harddisk) “y”(confirm) “w”(write mbr)
Step 3: Shutdown computer
Step 4: WebGui: Basic tasks -> Upload
Step 5: Restart pc and watch the magic happand

Hope this will help any other with same problem.
And to you developers; Isn’t this something that automaticly could be detected by FOG, and user could be prompted to delete the “GPT” stuff?[/quote]

Frode,

It isn’t something that could automatically be detected. Yes, we can detect whether or not a drive contain’s GPT information, and Yes, we could prompt users that this is occurring. That said, the reason we can’t automatically detect if GPT is in use is because we actually do support GPT disks as well. One of the re-occurring issues with GPT is that it’s not very friendly when switching from GPT to MBR style partitioning. I can’t make any guesses that all disks are SUPPOSED to be MBR because this may not be the case.

NVM. It appears I’m not the only one with issues with the latest Gandalf. At least I got to share my iPXE Advanced Boot Menu configuration. 🙂

Hey,

I finally worked it out. The network card driver was slow to negotiate it’s connection when the machine booted meaning the FOG Service had no time to do it’s business. Upgraded the driver and now it’s working 🙂

Thanks,

Dan

[quote=“G0dzilla, post: 35535, member: 1692”]Did the one machine that work have the SSD and HDD connected, or JUST the SSD?

Did the machines that failed have the SSD and HDD connected, or JUST the SSD?[/quote]

Try to turn off AHCI in BIOS (normally found under SATA settings, harddisks. Choose Compatibility mode.

Few possible ideas;

Was the image uploaded from a VM or a physical computer ?
Maybe try changing SATA mode to IDE/Compatibility from AHCI if that is available, or - not already set in BIOS.

chkdsk /f [or /R]
sfc /scannow

Okay, I found a solution that works for me, although it is not in a state to use is as a patch. My solution is ONLY for the download task, it does NOT fix the upload task and you have to do some manual steps everytime you create a new image (and only for mps images). I did the following:

Edit fog.download:

204 if [ -f $tmpMBR ]; then
205 if [ “$mbrsize” != “32256” -a “$has_GRUB” != “1” ] && [ “$mbrsize” != “512” ] && [ “$mbrsize” != “2048” ]; then
206 dots “Restoring Partition Tables”;
207 sgdisk -gel $tmpMBR $hd 2>&1 >/dev/null;
208 gptcheck=“yes”;
209 elif [ “$mbrsize” == “32256” -o “$has_GRUB” == “1” ] && [ “$osid” == “50” ]; then
210 dots “Restoring MBR and GRUB”;
211 restoreGRUB “${hd}” “1” “${imagePath}”;
212 if [ -e “${imagePath}/d1.partitions” ]; then
213 echo “Done”;
214 dots “Extended partitions”;
215 sfdisk $hd < ${imagePath}/d1.partitions &>/dev/null;
216 else
217 echo “Done”;
218 dots “No extended partitions”;
219 fi
220 elif [ “$mbrsize” == “2048” ]; then
221 dots “Restoring Lenovo Specific MBR”;
222 dd if=$tmpMBR of=$hd bs=512 count=4 &>/dev/null;
223 echo “Done”;
224 else
225 dots “Restoring MBR”;
226 dd if=$tmpMBR of=$hd bs=512 count=1 &>/dev/null;
227 if [ -e “${imagePath}/d1.partitions” ]; then
228 echo “Done”;
229 dots “Extended partitions”;
230 sfdisk $hd < ${imagePath}/d1.partitions &>/dev/null;
231 else
232 echo “Done”;
233 dots “No extended partitions”;
234 fi
235 fi

Create an image via uploading from master workstation. Boot master workstation with linux live image. Backup MBR
dd if=/dev/sdX of=backup.mbr bs=512 count=4 Save backup.mbr in your image folder, name it d1.mbr and set permissions like the original d1.mbr file

After these steps your workstations should boot to windows 7 again after running a deployment task - well, at least mine do.

Might want to check partions with gparted (boot disc) and check to see if you have any extra partions left from resizing. I would also do a checkdisk if not already done.

Try post 6 and later in [url]http://fogproject.org/forum/threads/stuck-on-dev-sda.11105/[/url]

fixparts removes erroneous GPT data. What causes the pausing is the image truly believes it’s MBR based, but the disk has false GPT information still on it. This freezes the system until a key is pressed as the data can’t be found. It finds a bad first partition (GPT usually has 3 or more) and can’t process the partition table.

Hi,

you can also integrate office updates into the installation,
download needed update files, extract them and place the msu file in the office updates folder:

[IMG]http://i.imgur.com/7WbPihg.png[/IMG]

To automate office installtion use config.xml

[CODE]<Configuration Product=“ProPlusr”>
<Display Level=“basic” CompletionNotice=“no” SuppressModal=“yes” AcceptEula=“yes” />
<USERNAME Value=“Bla” />
<COMPANYNAME Value=“Bla2” />
<!-- <INSTALLLOCATION Value=“%programfiles%\Microsoft Office” /> -->
<!-- <LIS CACHEACTION=“CacheOnly” /> -->
<!-- <LIS SOURCELIST=“\server1\share\Office;\server2\share\Office” /> -->
<!-- <DistributionPoint Location=“\server\share\Office” /> -->
<!-- <OptionState Id=“OptionID” State=“absent” Children=“force” /> -->
<!-- <Setting Id=“SETUP_REBOOT” Value=“IfNeeded” /> -->
<!-- <Command Path=“%windir%\system32\msiexec.exe” Args=“/i \server\share\my.msi” QuietArg=“/q” ChainPosition=“after” Execute=“install” /> -->
</Configuration>[/CODE]

It can happen that your office doesn’t have the admin folder then you cannot run setup.exe /admin,
then you will need to download adm templates for the desired office version, extract them and place
the admin folder in the office install folder, after that setup.exe /admin will work.

[IMG]http://i.imgur.com/3JO0yyD.png[/IMG]

[IMG]http://i.imgur.com/rQlRDnb.png[/IMG]

[url]http://www.microsoft.com/en-us/download/details.aspx?id=35554[/url]

[IMG]http://i.imgur.com/9lY72l2.png[/IMG]

Regards X23

I like your idea of booting into a pre-boot environment to do minor changes; however it seems like you are taking are hard approach at doing this when you could be creating your image with virtual box using snapshots at each major step so if you miss something or mess something up you can just revert the snapshot. Its still a timely and daunting process to create an image this way but it takes out the headaches of having to start from scratch each time. Then each time you think you have it right or after each modification you simply upload your new image over your old one.

I agree with adding UEFI support. something I’ve really been needing a full dd should work so I’m thinking if it’s possible to check where partition nr 3 starts (win7 / 8.x) then make a dd image from zero to the start of partition nr 3, then treat partition 3 as a “multi partition disk, no resize”

Not to confuse anyone i will start a new thread as i go because they are different threads

please see [url]http://fogproject.org/forum/threads/uefi-vs-legacy-bios-gpt-vs-mbr-single-partition-resizable-vs-multiple-partition-notresizable.11124/[/url]

Since FOG does not fully support UEFI i suggest just to disable this feature in the Bios before even installing the OS. If someone can * make it work with no issues with UEFI please share it so that i/we can understand it better.

[quote=“need2, post: 25853, member: 21891”]Are you sure the user data isn’t just in a deprecated user folder? Such as C:\Users\gobbledegook[/quote]

Late reply sorry, bu yes the files would have been under Mrs. Gobbledegook’s user files, however not all users save to just that location so I like to run full backups.