Posts made by Matthieu Jacquart

@corentin Bonjour Corentin, je suppose que tu es français ^^
Effectivement il faut toujours faire un sysprep avant de remonter l’image, ça permet de générer un nouvel SSID pour les postes déployés. Si besoin d’aide je te laisse m’envoyer un message privé avec ton adresse mail pour qu’on puisse échanger plus facilement
Matthieu

OMG shame on me, it was just a chkdsk problem, never thought to that…
sorry for this, I’ll tried to keep in mind for next time !

@sebastian-roth Hi, result for first trial :

And after chkdsk /F

@sebastian-roth Hi, That’s a bad photomontage of debug capture task, I think “Not shrinking (/dev/nvme0n1p4) trying fixed size” is interesting :

@sebastian-roth Hi, OK thanks I’ll try it tomorrow. I found another image with these 5 partitions but this time d1.fixed_size_partitions

1:2:3:5

so Windows partition is shrunk for this one, any way to force it for the bad one ?

Matthieu

Hi,

I have a weird partitioning problem on an image which prevents me from deploying it on a smaller disk :

On this image, windows shows 4 partition (as always) but there are 5 partitions on my Fog image (d1p1 to d1p5.img) and the 3 d1.partitions files are strictly identical :

d1.fixed_size_partitions

1:2:3:5:4

d1.minimum.partitions

label: gpt
label-id: C02F8167-B511-4E11-A662-38C514DE2003
device: /dev/nvme0n1
unit: sectors
first-lba: 34
last-lba: 250069646
sector-size: 512

/dev/nvme0n1p1 : start=        2048, size=     1021952, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=1A290936-33CC-4F05-8D8E-3E92521F07C2, name="Basic data partition", attrs="RequiredPartition GUID:63"
/dev/nvme0n1p2 : start=     1024000, size=      204800, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=FE60AE84-7CD7-4C13-A3E4-3DC6F929153A, name="EFI system partition", attrs="GUID:63"
/dev/nvme0n1p3 : start=     1228800, size=       32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=DE00D172-008C-4725-A3E7-AD8039CC5376, name="Microsoft reserved partition", attrs="GUID:63"
/dev/nvme0n1p4 : start=     1261568, size=   247618048, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=36EAFD7B-F30E-4225-9C8A-1DC8C1092A48, name="Basic data partition"
/dev/nvme0n1p5 : start=   248879616, size=     1189888, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=39BC0E02-4429-49D5-80D1-F989B4A929A7, attrs="RequiredPartition GUID:63"

d1.partitions :

label: gpt
label-id: C02F8167-B511-4E11-A662-38C514DE2003
device: /dev/nvme0n1
unit: sectors
first-lba: 34
last-lba: 250069646
sector-size: 512

/dev/nvme0n1p1 : start=        2048, size=     1021952, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=1A290936-33CC-4F05-8D8E-3E92521F07C2, name="Basic data partition", attrs="RequiredPartition GUID:63"
/dev/nvme0n1p2 : start=     1024000, size=      204800, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=FE60AE84-7CD7-4C13-A3E4-3DC6F929153A, name="EFI system partition", attrs="GUID:63"
/dev/nvme0n1p3 : start=     1228800, size=       32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=DE00D172-008C-4725-A3E7-AD8039CC5376, name="Microsoft reserved partition", attrs="GUID:63"
/dev/nvme0n1p4 : start=     1261568, size=   247618048, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=36EAFD7B-F30E-4225-9C8A-1DC8C1092A48, name="Basic data partition"
/dev/nvme0n1p5 : start=   248879616, size=     1189888, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=39BC0E02-4429-49D5-80D1-F989B4A929A7, attrs="RequiredPartition GUID:63"

d1.shrunken.partitions

label: gpt
label-id: C02F8167-B511-4E11-A662-38C514DE2003
device: /dev/nvme0n1
unit: sectors
first-lba: 34
last-lba: 250069646
sector-size: 512

/dev/nvme0n1p1 : start=        2048, size=     1021952, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=1A290936-33CC-4F05-8D8E-3E92521F07C2, name="Basic data partition", attrs="RequiredPartition GUID:63"
/dev/nvme0n1p2 : start=     1024000, size=      204800, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=FE60AE84-7CD7-4C13-A3E4-3DC6F929153A, name="EFI system partition", attrs="GUID:63"
/dev/nvme0n1p3 : start=     1228800, size=       32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=DE00D172-008C-4725-A3E7-AD8039CC5376, name="Microsoft reserved partition", attrs="GUID:63"
/dev/nvme0n1p4 : start=     1261568, size=   247618048, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=36EAFD7B-F30E-4225-9C8A-1DC8C1092A48, name="Basic data partition"
/dev/nvme0n1p5 : start=   248879616, size=     1189888, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=39BC0E02-4429-49D5-80D1-F989B4A929A7, attrs="RequiredPartition GUID:63"

Create on a 128GB SSD, i can deploy on larger disk but not smaller, how can I modify d1 partitions files ton remove this 5th partition and adapt d1.minimum.partitions ?

Thanks
Matthieu

@sebastian-roth A fourth colleague had the same problem today so I restarted fog service, it takes a while but photocop_rgi printer has been connected after that :

------------------------------------------------------------------------------
--------------------------------PrinterManager--------------------------------
------------------------------------------------------------------------------
 18/02/2021 15:37:55 Client-Info Client Version: 0.12.0
 18/02/2021 15:37:55 Client-Info Client OS:      Windows
 18/02/2021 15:37:55 Client-Info Server Version: 1.5.9.60
 18/02/2021 15:37:55 Middleware::Response Success
 18/02/2021 15:37:55 PrinterManager Adding printers
 18/02/2021 15:37:55 PrinterManager \\impression\Compta already exists
 18/02/2021 15:37:55 Printer Adding: \\impression\Photocop_RGI
 18/02/2021 15:37:55 PrinterManager PrintUI return code = 0
 18/02/2021 15:37:56 PrinterManager Invoking add \\impression\Compta for all users
 18/02/2021 15:37:56 PrinterManager PrintUI return code = 0
 18/02/2021 15:37:56 PrinterManager Invoking add \\impression\Photocop_RGI for all users
 18/02/2021 15:38:26 PrinterManager PrintUI has not finished in a timely fashion, abandoning process
 18/02/2021 15:38:26 PrinterManager Restarting spooler
------------------------------------------------------------------------------

I’m just unable to explain this problem…

@sebastian-roth I can’t tell you, it only happen on dedicated computers.
I’ve juste been called by a colleague which has 2 configured printers by fog, one is ok (“compta”) but not the other one (“Photocop_RGI”, as you mentionned “already exists”)

------------------------------------------------------------------------------
--------------------------------PrinterManager--------------------------------
------------------------------------------------------------------------------
 18/02/2021 10:14:13 Client-Info Client Version: 0.12.0
 18/02/2021 10:14:13 Client-Info Client OS:      Windows
 18/02/2021 10:14:13 Client-Info Server Version: 1.5.9.60
 18/02/2021 10:14:13 Middleware::Response Success
 18/02/2021 10:14:14 PrinterManager Adding printers
 18/02/2021 10:14:14 PrinterManager \\impression\Compta already exists
 18/02/2021 10:14:14 PrinterManager \\impression\Photocop_RGI has already been configured
------------------------------------------------------------------------------

Is there a way to force it to re-add printer ?

@sebastian-roth Hi Seb, It’s maybe related to a windows bug but it began before last tuesday patch, and I made no change on GPO.
Very strange, according to fog.log printer is mapped but didn’t appear on printer control panel or office documents, I have to map it manually to work.

Hi,

It’s maybe a coincidence but I had no problem with 1.5.9.58 (so why did have made an upgrade isn’t it ?) and since upgrade to 1.5.9.60 several users called me (some of them every day) because their printer is no longer connected, while fog.log seems ok :

------------------------------------------------------------------------------
--------------------------------PrinterManager--------------------------------
------------------------------------------------------------------------------
 18/02/2021 06:55:47 Client-Info Client Version: 0.12.0
 18/02/2021 06:55:47 Client-Info Client OS:      Windows
 18/02/2021 06:55:47 Client-Info Server Version: 1.5.9.60
 18/02/2021 06:55:47 Middleware::Response Success
 18/02/2021 06:55:47 PrinterManager Adding printers
 18/02/2021 06:55:47 PrinterManager \\impression\Photocop_RGI already exists
------------------------------------------------------------------------------

Is it a bug of 1.5.9.60 or something else ?
Can you refresh my memory and tell me how to revert to 1.5.9.58 ?

Thanks,
Matthieu

@sebastian-roth Hi, I didn’t made other tests since end of October but I was able to deploy image to 80 PC at this moment so for me it’s ok

Hi,

I had same problem 2 days ago to upgrade from 1.5.9.35 to 1.5.9.37

@Sebastian-Roth Ok I think yo can close this topic, it was a bug in my image due to Windows partitions… When I upgraded Win 10 from 1909 to 2004 this summer, I found a 600MB recovery partition at the end of the disk, after C partition, while there was already a 500MB recovery partition at the beginning of the disk.
So I deleted this final partition and as everything seemed to work fine I left like that. Except that now, for a reason I can’t explain, sysprep + fog capture crash my image.
Likely I found one Pc which has not been erased this summer so I was able to update and capture it, now I’m saved !

Here is the partitioning of my image, it seems strange to me with the first 500MB partition with 10MB used and 0 unsused (where are the missing 480 MB ?), and another recovery partition at the end. It’s working like a charm for now but I think I will have to start a fresh install soon…

Thanks,
Matthieu

another strange behaviour, this one worked fine 10 minutes and supports few reboot, but then failed with “NTFS file system” error.
Gparted return this :

If I boot with win 10 installation USB key, I’ve got a message disk is GPT…

So I continue tests and update fog to last dev-branch (1.5.9-29), which gave me same results that last stable 1.5.9 :

• if I upload image without sysprep, everything is ok, I can deploy this image.
• if I sysprep image without capturing it with fog, behouviour is normal and I can sysprep image 2 or 3 times without any bug.
• BUT if I sysprep image AND capture it, this time windows can’t boot, and Gparted give this :

Windows partition C seems not recognised and empty, so of course it can’t boot ! But why this behaviour occurs only after sysprep + fog capture ?
Thank you for your lights !
Matthieu

@Sebastian-Roth
Yes sometimes after fog deployment PC didn’t crash immediately but reboot 3 or 4 times with fog hostname changer and AD integration (made by fog client) and then I’ve got the exact screen you post.
I’ll continue some tests tomorrow with last dev-branch version and just trying to deploy and then upload my master image (without any update or new software)

@george1421 Indeed I didn’t use this method but I think it will be good idea to use a VM with snapshot to update my master…

@Sebastian-Roth Yes deployed on another machine, same model and another different model.
But this behaviour occurs regardless the machine I use to prepare image (Dell 3020, 3060, 3070, same final result)

Hi, I test your tips (sysprep and upload a new image "Multiple Partition Image - Single Disk (Not Resizable) ZSTD Compressed) but same problem, immediately after deployment Pc crash with NTFS file system blue screen…

Hi,

I’m going crazy because I spent days trying to update image and deploy it, but it always failed !
Last image was built in August after Win10 2004 upgrade, everything worked fine and I’m still able to deploy it to different model.
But now I need to update it with some new software, machine works perfectly until I sysprep it and upload image (after that sometimes master failed to boot too, but not always), and each machine I deploy (same model, or not) crash either just after deployment with error 0xc0000225, or after AD integration with “NTFS file system” error…

I made tons of tests but I really don’t undestand what happened, could it be a windows bug (update, software, driver, sysprep…) or a Fog bug (update 1.5.9) ? I test last v4 and v5 kernel, same behaviour.
It’s very frustrating, thanks for help !
Matthieu

@george1421 Works great, thanks !