SOLUTION:
Shrink the data partition
Move any partitions after the data partition to the left (so unallocated space is all at the right)
Capture using Multiple Partition Image - Single Disk (Non resizable) (or all disks if that’s your setup obviously)
Deploy to the SSD
Move the previous partitions back to the right.
Expand the data partition
Recapture with Single Disk - Resizable
Deploy to the rest.

@p4cm4n OK now that you have the password parts worked out, you should be able to go into FOG Settings->FOG Kernel and from there you can downgrade to the 4.15.2 kernels, just download both bzImage and bzImage32 for the PC platform. From there it will download the kernels. You can check by going on the FOG server console to

cd /var/www/html/fog/service/ipxe file bzImage

That should print out version 4.15.2. If that is the case you are golden. FWIW, you CAN do this while you are imaging as long as you don’t currently have a system pxe booting.

@tom-elliott Image Manager Partclone Gzip

I was confused about what to choose. Because as you can see in the screen shot that the compression for basic image is Partclone Compressed. So I just went into that image definition and saw the Gzip.

With FOG installed you should go to FOG Configuration under settings and find the Proxy settings and fill those in if you haven’t already. Hopefully it will all be good with that.

@jemerson93 Have you already tried using kernel version 4.15.2 as opposed to 4.16.6 and 4.17.0?

@fogmania said in Can't do Quick Image After creating Users:

I’m using a storage node that is working well but it has not been updated to the last version. Should I do this too?

Absolutely - it’s required in most cases.

But the image history still shows that the user that is logged in is the one that made all imagings. Any idea?

Others have complained about this too, see this thread:

https://forums.fogproject.org/topic/11596/host-imaging-history-lists-the-current-image-name-on-every-line

Prompt time is the checkin time for the client. Anything below 60 seconds is invalid, and we won’t allow the client to go below that point. (Using Default = 60s)

Error code 2691 = The machine is already joined to the domain.

So this is likely true. When creating the master image, I would highly suggest disabling the “Join Domain” feature of the host. (Host Page->Edit relevant Host->Active Directory->Uncheck Join Domain) then disjoin that machine from the domain manually. Then capture your image. If you’re sysprepping your images, it’s also recommended to disable the fogservice from starting on the machine, and having a setupcomplete.cmd script that re-enables the service once sysprep process is complete.

@svalding What would be interesting to know is what is different between the two docks.

Please do the following

Schedule a debug deploy/capture (tick the check box for debug before you submit the task) for the nic of the working dock. It doesn’t matter if its a capture or deploy because we are not going to do either. PXE boot the target computer, after FOS boots you should see several screens of text press enter a few times until you get to the linux command prompt. Key in
lspci -nn | grep etwork Record what you see there for the network adapter. The hex codes are important. Repeat the same process with the non-working dock. You may get warning messages about not able to access the network, but it still should allow you to get to the linux command prompt. Collect the output of the lspci command from above. Please post the output of those two systems in this thread.

0_1530763109245_33e20c39-f273-4851-b3f1-fedd0e4bbeed-image.png

Got this working over the weekend with QNAP. The NFS shares are slightly different in v4.3.3 of the QNAP software on the TS-231. You don’t have to specify the full local path. Only the shared path location.

@p4cm4n Glad you figured out what the issue was and a way to resolve the problem. Glad to help program this for you, among others. I know how useful it is and how it has impacted jobs.

Now if only I could find a job that requires FOG as a part of it, I think I’d be a shoe in lol.

@plegrand UEFI implementations can be a real pain. It’s meant to be Kind of universal but everyone is just doing his/her own thing. So some UEFI clients work great while others just don’t want to play nicely. There is not much we can do about it. Well, you can try using rEFInd and start playing with the config file. If you are lucky it’s justa matter of finding the right options.

echo Installiere Acrobat Reader DC + Font Pack
“%source%\AcroRdrDC1801120035_de_DE.exe” /sAll /rs
msiexec /qn /i “%source%\FontPack1500720033_XtdAlf_Lang_DC.msi” REBOOT=ReallySuppress

i’ll write a quick tutorial as soon as i have everything working. I guess i can’t use -no–describe in uefi, but i can allways use wimbot to boot to an envoirment and then mount iscsi devices and go from there.
memdisk is a nice kernel but loading the ENTIRE iso into the ram is network consuming and big isos will eat up my ram at best.
running from iscsi is the way to go! it’s like a physical device , but mounted virtually, via a network, it’s like using a pen, but -no-describe ruins some of the feautres i want to use, well… if i want to use it in uefi mode anyway.

@george1421 Thank you for the help. Capture seems to be working properly now.
Tom

@tom-elliott @george1421 So it is taking forever to replicate just 1 Node drivers. We rsynced before but its almost copying every file again. What do we need to do to make the copies be the same and speed up replication? What does FOG use to check the file to see if it matches?

@howtogravity Just manually set it via SQL.

@vince-villarreal If your image contains the FOG Client, which is sounds like it does, simply disable the service, disjoin the domain, capture the image. In terms of SYSPREP, you would have your setupcomplete.cmd set to enable the fog service as the last thing it does. Then you can start the service or restart the machine.

So basic steps:

Create your layout of software/OS, etc… If machine is to be constant master image maker machine, don’t allow it to join the domain (can be setup in the GUI under Hosts->Edit->Active directory->Join Domain) Install FOG Client.
# If sysprepping Disable fog client service. Sysprep Machine. Fully shutdown machine.
# End sysprep steps Capture image.

Thanks and fixed.

Was this meant to be deleted/purged, or is this an issue?

@mattf You could separate the fog servers and the database - so that both servers use the same database on a dedicated VM for this purpose. In this scenario, the fog server would not be able to process queries as quickly because each query would need to traverse the network. Another option is you could use MariaDB 10.x Galera to create a database cluster between the two fog servers. Based on my own experiences with both of these things and considering how heavy FOG is on the database, I’d opt for a Galera database cluster to keep the database local to each server. Here is information on that: https://mariadb.com/kb/en/library/getting-started-with-mariadb-galera-cluster/