Posts made by grungeman

@george1421 This fixed my problem, thank you!

You seem to be on track. http://192.168.2.2/fog/service/ipxe/boot.php?mac=00:00:00:00:00:00

Gives me “A valid database connection could not be made”

But mysql is atleast active

Seems like we got some similiar issues today. I didnt have time to investigate it yet. I got a call that its no longer working to boot with iPXE. IP loan is issued but PXE seem to fail.
If anyone else seen this and have a solution some input would be appreciated.

/Peter

@george1421 Thanks, it works !

But always one more question.
Would it be possible to add the Deploy Image option, where you can quick deploy image from the database without register them?
Now it works fine to deploy an image if i first register it, connect it to an image for deploy and reboot with first Deploy/capture option. Which is a acceptable as a alternativ solution but not optimal if it comes to larger deployments.

@george1421 alright, sounds like a good advice. I’m sorry for my bad knowledge about this. But im not really sure how to set the ip in the grub config file. Where should it be.
It currently looks like this, no ip in there at all atm.

set timeout=10
set default=0

#insmod efi_gop
#insmod efi_uga
insmod all_video
#insmod font

menuentry “FOG 32-bit Debug Kernel” {
linux /boot/bzImage32 loglevel=7 boot_delay=2000 debug init=/sbin/init root=/dev/ram0 rw ramdisk_size=127000 pcie_aspm=off consoleblank=0 isdebug=yes
initrd /boot/init_32.xz
}

menuentry “FOG 64-bit Debug Kernel” {
linux /boot/bzImage loglevel=7 printk.time=1 init=/sbin/init root=/dev/ram0 rw ramdisk_size=127000 pcie_aspm=off consoleblank=0 isdebug=yes
initrd /boot/init.xz
}

I followed the guide to create a bootable USB stick https://forums.fogproject.org/topic/6532/usb-boot-target-device-into-fog-os-live-fosl-for-debugging
Seems to be a potentially good solution, but i run into another issue.

The USB stick boots fine, the NIC is found and IP aquired but after that DHCP request or what else to call it start to loop.

I get an ip from the DHCP 192.168.2.16 , so there is a communication with the DHCP server. But still its ends No with DHCP respons on interface eth0.

See attached photo of the screen
https://drive.google.com/open?id=0B4jg25N5LsOTVEFueUh5cG1WUTQ

Any ideas what would be wrong?

/Peter

Server

• FOG Version: 1.4.2
• OS: Ubuntu 16.04

Client

• Service Version:
• OS:

Description

I’m been searching all over to find answer if there is any workable solution to boot USB dongel NICs so they can connect to my fog server. I found several advice but cant say I found anyone that confirmed its working or any good guide how to make it work.
I know this worked well with PXE and WDS , were you could easly create a USB stick containing the pxe boot image. But seems a lot diffrent with iPXE.

It’s a problem that needs solving as there is a lot of laptops nowdays without a integrated NIC.

Would be greatfull for any help!
Thanks!

@Sebastian-Roth Would it be possible for me to change which labels FOG looks for when setting fixed partitions?

@Sebastian-Roth Thanks , this looks very promissing, just tested it on one computer and it looks just right. Fog now recongnized the system partition as a fixed partition and set the The d1.fixed_size_partition :1:3 .
I will need to do some more testing to evaluate this, but looks good atm. This could in other words just be a OS language “bug” , I think swedish windows 10 version by default name the “System Reserved” partition just “System” Which would make fog miss the fixed partition and cause me all the trouble.

It is however very doable to manuallt rename a partition prior capturing it.

thanks for the good advices, I hope this turn out to be great.

Well with a lot of testing the last few days, changing the d1.fixed_size_partitions to 1:3 is the only way to create a resizable working image of a none syspreped Windows 10. But again if there is no solution for the usable space on the system partition I think it is not usable.
Our goal is to be able to create a clone of working windows 10 without the need of using sysprep before its captured. Seems to work better with non resizable images, but that has its own issues. Like the need or resize partition post installation.

One question a side from the main subject, is it normal that i create a new fog image choosing Partimage, but when the capture is done and i view the image it now say Partclone Gzip?

@Quazz
Added two chkdsk screens, one from Source PC before capture and one from destination PC after deployment. No errors as far as I can see.
https://drive.google.com/open?id=0B4jg25N5LsOTUUViOUNwdGVReXM

Sorry for the swedish in the screenshot. The new link below should include Source_PC Disk management screenshot, the way it should look and the destintation_PC disk management screenshot after the deployment.
I also included some of the partition config files, not sure if its usefull.
New hopfully working link

https://drive.google.com/drive/folders/0B4jg25N5LsOTUUViOUNwdGVReXM

Server

• FOG Version: 1.4.2
• OS: Ubuntu 16.04

Client

• Service Version: 1703
• OS: Windows 10 Pro

Description

At first almost every Windows 10 image captured failed when deploying them back to another computer with another disk. The cloning itself was succesfully completed but windows would always stop at startup with an error message. However changing the fd1.fixed_size_patitions from :3 to 1:3 we can now succesfully deploy windows 10 on diffrent sized hard drives.
So far so good, but now i noticed that the system partition seems a bit corrupt, the partition size say 1000MB as it should , but it also say 30mb in use 1mb free.
See attached picture.
I tried change the d1:minimum_partitions as well but still same.
The computer seem to run ok but it doesn’t feel right to leave it like that. Anyone got any ideas how to fix this?

/Peter
All shared files should be here now
https://drive.google.com/open?id=0B4jg25N5LsOTUUViOUNwdGVReXM