Posts made by TomcatKZN

WebGui not available, so I reran the installer.
Everything appears to be working except reports.
Fog Version 1.5.2 on Ubuntu
Tried running Alter User in MySQL
No change.
Where to look next?

Hi Guys
Ran the install with -KY on FOG server. Completed Successfully.
Uninstalled the client on the Presysprepped image Virtual Machine.
Rebooted
Reinstalled the client pointing to FQDN of FOG server.
Rebooted
First iteration of authentication failed as before. A few minutes later when I checked the log again it had successfully authenticated and the client appears to be working correctly.
I have sysprepped this image and am busy capturing it. (For some reason the capture process always drops to about 300Mb/s, while Deploy always runs at full speed), will report back once I have done an install, in the morning.

Thanks for the response guys. I was at training workshop all day so haven’t been able to try this yet. Will do so first thing. Thank you.

Please can someone help. am going nuts.
On my presysprep image of win10 1709, I installed the client 0.11.12. (Fog server 1.5.0 RC10)
First off, I got the could not inatall Ca Certificate.
I changed the fogserver address to use the FQDN, and then the install worked.
Then I rebooted the client.
Fog log:

--------------------------------Authentication--------------------------------
------------------------------------------------------------------------------
 2018/01/22 21:08 Client-Info Version: 0.11.12
 2018/01/22 21:08 Client-Info OS:      Windows
 2018/01/22 21:08 Middleware::Authentication Waiting for authentication timeout to pass
 2018/01/22 21:10 Middleware::Communication Download: http://fogserver2.ehs.local/fog/management/other/ssl/srvpublic.crt
 2018/01/22 21:10 Data::RSA FOG Server CA cert found
 2018/01/22 21:10 Middleware::Authentication Cert OK
 2018/01/22 21:10 Middleware::Authentication ERROR: Could not get security token
 2018/01/22 21:10 Middleware::Authentication ERROR: Could not find file 'C:\Program Files (x86)\FOG\token.dat'.
 2018/01/22 21:10 Middleware::Communication POST URL: http://fogserver2.ehs.local/fog/management/index.php?sub=requestClientInfo&authorize&newService
 2018/01/22 21:10 Middleware::Response Private key path not found


 2018/01/22 21:10 Middleware::Communication URL: http://fogserver2.ehs.local/fog/management/index.php?sub=requestClientInfo&configure&newService&json
 2018/01/22 21:10 Middleware::Response Success
 2018/01/22 21:10 Middleware::Communication URL: http://fogserver2.ehs.local/fog/management/index.php?sub=requestClientInfo&mac=00:15:5D:67:1F:1D|00:15:5D:67:1F:1E||00:00:00:00:00:00:00:E0&newService&json
 2018/01/22 21:10 Middleware::Authentication Waiting for authentication timeout to pass
 2018/01/22 21:12 Middleware::Communication Download: http://fogserver2.ehs.local/fog/management/other/ssl/srvpublic.crt
 2018/01/22 21:12 Data::RSA FOG Server CA cert found
 2018/01/22 21:12 Middleware::Authentication Cert OK
 2018/01/22 21:12 Middleware::Authentication ERROR: Could not get security token
 2018/01/22 21:12 Middleware::Authentication ERROR: Could not find file 'C:\Program Files (x86)\FOG\token.dat'.
 2018/01/22 21:12 Middleware::Communication POST URL: http://fogserver2.ehs.local/fog/management/index.php?sub=requestClientInfo&authorize&newService
 2018/01/22 21:12 Middleware::Response Private key path not found
 2018/01/22 21:12 Middleware::Response Success
 2018/01/22 21:12 Middleware::Communication URL: http://fogserver2.ehs.local/fog/service/getversion.php?clientver&newService&json
 2018/01/22 21:12 Middleware::Communication URL: http://fogserver2.ehs.local/fog/service/getversion.php?newService&json

 2018/01/22 21:12 Service Creating user agent cache
 2018/01/22 21:12 Middleware::Response ERROR: Unable to get subsection
 2018/01/22 21:12 Middleware::Response ERROR: Object reference not set to an instance of an object.
 2018/01/22 21:12 Middleware::Response ERROR: Unable to get subsection
 2018/01/22 21:12 Middleware::Response ERROR: Object reference not set to an instance of an object.
 2018/01/22 21:12 Middleware::Response ERROR: Unable to get subsection
 2018/01/22 21:12 Middleware::Response ERROR: Object reference not set to an instance of an object.
 2018/01/22 21:12 Service Initializing modules

Mod edited to use code block.

Okay. You have a point about backing up the original disk.
I’ll give that a bash and check if it works.

Understood. Thank you.

@sebastian-roth said in Deployed image boot loop - black screen & Press Ctrl Alt Delete:

@TomcatKZN Ok thanks, I think Ich found what’s causing this. Just need a little more time to fix. Will get back to you soon.

Awesome. Much appreciated.

I also ran Easus partition manager and posted the output.
Seems the 1st partition is fat16. perhaps thats the problem.
Wonder if I can change it to fat32 if it will still work.
What do you think?

@Sebastian-Roth

GDisk -PreImage:

FDisk-PreImage:

Does this help identify the problem with capturing this image?

@sebastian-roth said in Deployed image boot loop - black screen & Press Ctrl Alt Delete:

@TomcatKZN Thanks for the pictures. Although I am sure we have found the issue we still need to figure out what exactly is causing this. I need more information on where those pictures were taken. I’ve tried to replicate this in a test VM but was not successful yet. So I guess my assumptions are wrong.

Please let me know where and when exactly those gdisk and fdisk output pictures were taken. I surely see this is a FOG debug task but was this on a fresh untouched client before capture, after capture or on another machine before / after deployment?

What I am sure is that the partition start positions are moved at some point. And because of that Windows cannot boot. Though I am still not sure if the initial partition layout is crappy or if this is something FOG is causing.

The Gdisk and FDisk output is from a freshly deployed Client which failed.
The same client from which the image was taken.
The picture from windows is before the capture and deploy.
I will install an untouched disk and generate the same output from before the capture.

Disk partitions in Windows:

Output from GDisk -l:

Output from FDisk -l:

Any help greatly appreciated.

@sebastian-roth said in Deployed image boot loop - black screen & Press Ctrl Alt Delete:

@tomcatkzn said in Deployed image boot loop - black screen & Press Ctrl Alt Delete:

d1.fixed_size_partitions = :1:2:3
d1.minimum.partitions = same as d1.partitions

Ok so this has essentially been more or less like “Multiple partitions - Single Disk” because our logic of detecting resizable partitions wasn’t able to figure yours as such and marked them all to be fixed size. Then again I wonder why you are seeing the “Press Control Alt Delete to boot” message on boot after deploying the image to another machine. Sure the Windows version and OS ID set in FOG do match?

Please schedule a debug deploy task for one of your client. Boot it up and start the deployment by running the fog command. After it finished run fdisk -l /dev/sda and post a picture of the output on screen.

Yes. Op sys is win7 and image type is set to Win7
I watched the end of the deploy task and it said “Sync Successful” for each partition
I restored it back to the exact same machine and still get "Press Ctrl-Alt-Del to Restart
immediately after bios boot.

Am running a debug task now.

@sebastian-roth said in Deployed image boot loop - black screen & Press Ctrl Alt Delete:

@tomcatkzn said in Deployed image boot loop - black screen & Press Ctrl Alt Delete:

… Win7-Single disk -multiple partitions-all default settings …

From what we see in the picture this was not captured as “Single disk -multiple partitions” but as “Single disk - Resizable”. So please post the contents of d1.fixed_size_partitions, d1.minimum.partitions and d1.original.fstypes as well.

We had some issues with type=de partitions a while ago but I think those should be all fixed in RC version. By the way, do you use working or dev-branch?
Not sure about the type=27 yet. Possibly this is causing the issue. Why is the boot partition type set to be a “Hidden HTFS partition”? I know this is what you got from Dell…

So I’d suggest to actually create a fresh image in the web UI, set it so “Multiple partitions - Single Disk” and try capturing again from an original machine that hasn’t been touched yet. I am fairly sure this will work when deploying to another machine.
Thank you again for the help. Sorry for delay. Needed to Eat :]
I last used FOG 0.32 in 2012 - worked great, but I became ill and job went to someone else. That person switched to WDS and left without documentation. I’m a fan of FOG but see I have a lot to catch up on. The work youve done is awesome.

Yes - my bad memory: it is indeed Single Disk-Resizeable
I installed from dev-branch to get the latest build, as I am happy to give feedback.
d1.fixed_size_partitions = :1:2:3
d1.minimum.partitions = same as d1.partitions
d1.original.fstypes = NTFS
Am in the process of recapturing the image. Will post progress shortly.

@sebastian-roth said in Deployed image boot loop - black screen & Press Ctrl Alt Delete:

@tomcatkzn said in Deployed image boot loop - black screen & Press Ctrl Alt Delete:

backup the factory image from a single Dell machine

To me this kind of sounds like a weird partition layout issue. Can you please boot one of the original machines into a debug capture task, hit ENTER twice to get to the shell. Then run gdisk -l /dev/sda, take a picture of the screen and post here. As well take a look at the image information stored on the FOG server in /images/<IMAGENAME>. Post the contents of the text file called d1.partitions here as well.

Thank you for the helpful diagnostic comments. Just waiting for another install to finish and I’ll do the “debug” task.
Here are the two pictures of/images/DellMaster and d1.partitions

@george1421 said in Deployed image boot loop - black screen & Press Ctrl Alt Delete:

@tomcatkzn Ok that is what I wanted to be sure of, you were deploying back to the same computer as where the image came from.

So to collect a bit more info on this:

1. Did the 3020 come with Win7 on it??
2. Is the 3020 in UEFI or legacy mode.
3. Is it possible to get a clear picture taken with a mobile phone and post it here?

I’d like to see this error screen. I can only think of where this error might be, is during OOBE. But you are just capturing and deploying to the same hardware, so you aren’t running sysprep here. It should “just work”
Hi George, Thanks for the response:

1. Yes
2. Legacy mode
3. Nothing else is displayed before the black screen. Just the black screen and the white writing top left corner directly after bios post. I will try deploy the image again shortly and post the picture.

I agree I am stuck. In the past a capture and deploy back to the same machine “just worked”

Perhaps I try the capture again in case it is corrupted somehow.

Hi George
In this instance I am using fog to backup the factory image from a single Dell machine which I tried to restore back to the same machine, so that I can restore it to factory image if necessary.
Once I have the factory image saved I plan to deploy our own custom image to the machines. They are all the same Dell-3020 spec.

Hi Guys
Am running RC1.5.0-RC-9 on Centos 7.
I captured an image of a Dell 3020 factory image by way of a backup so I could restore it if required. Captured with no problem (Win7-Single disk -multiple partitions-all default settings).
I tried to deploy the image back to the same computer but on reboot I get a black screen with “Press Control Alt Delete to boot” when I do that it reboots back to the same screen.
I’d really appreciate any insight into this. Thank you.

@george1421
That is gold. Thank you.

@george1421 Awesome! Thank you.

@george1421 said in Setting up the right FOG Environment:

@tomcatkzn said in Setting up the right FOG Environment:

Any idea what the size of a basic win7 and win10 image is with the new compression code?

We’ve been rolling out fat images lately, but I think our thin Win7 image is about 8GB on the target disk.

When setting up the VM I would create 2 vmdk files. One for the OS and one for images. If you are comfortable with the linux installer you can do it when you manually partition the disk. Create an OS disk of about 20GB in size and then create the image disk as a single disk, with a standard partition (not lvm) formated with ext4. Then for your mount point make it /images. That way when you install fog everything is setup.

The other option is to install linux first on that single 20GB disk and then after the OS is installed then add in the imaging disk and mount it to /images BEFORE fog is installed. Again you will want to make it a single vmdk, with a standard partition (not lvm) formatted with ext4. The reason why I say a standard partition is that if you need to you can expand that vmdk later and then the partition, and file system. Its a bit harder if lvm is involved.

Thank you for this very helpful feedback.
So a vhdx of about a 250Gb for /Images should be a good starting point then.