Hi,

Any ideas ?
I saw in DB that even if task manager is empty in web UI, the 2 tabels “tasks” and “snapins tasks” are still containing data…
And if I launch several deployment tasks with the associated snapins, either the snapins do not appear at all (empty web ui), or they are offset (see picture)
snapin.jpg

If my database is broken, is it possible to recreate a new empty one and import some important tables ?

Thans,
Matthieu

@george1421 Exactly ! I changed server +.fogsettings ip (+ 4 ip in database by hand…) and everything is fine (ip in default.ipxe changed automatically)

@sebastian-roth for information :

ca.cnf (with new ip) [v3_ca] subjectAltName = @alt_names [alt_names] IP.1 = 192.168.10.52 DNS.1 = FOG.lycee.nd req.cnf (kept old ip) : [req] distinguished_name = req_distinguished_name req_extensions = v3_req prompt = yes [req_distinguished_name] CN = 192.168.10.60 [v3_req] subjectAltName = @alt_names [alt_names] IP.1 = 192.168.10.60 DNS.1 = FOG.lycee.nd

@sebastian-roth Hi, just tested, works like a charm 🙂

There’s also this article:
https://wiki.fogproject.org/wiki/index.php?title=Windows_Dirty_Bit

@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 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 😉

@george1421 Works great, thanks !

@Matthieu-Jacquart Sure right. If one client was pinned to the re-newed server CA cert then it can’t connect to the old original one. I missed that point! Good you figured it out!!!

Great we got that worked out.

@Sebastian-Roth Hi, thanks so much for your work and help, I’ll test as soon as I came back to work, after 19th August.

Ok all seems fine now, thanks you Quazz 😉
Except than when I execute sysprep, all metro appx are gone after reboot, no more calculator or store…
Seems to be a Windows 10 1803 upgrade problem, one more thing I’m trying to resolve… 😞

Binary files have been updated.

Rerun installer after running:
cd /path/to/fogproject/git
rm binaries1.5.0-RC-12.zip
cd bin
./installfog.sh -y

Hi,

Everything is now fine with RC-12, thread can be closed 😉

Thanks !
Matthieu

@joe-schmitt Perfect ! 😉

Hello,

excuse-me for awakening a quite old post, I’m not asking for help but adding some contribution in case of someone else has same problem. I also had yesterday the same message when trying to capture a syspreped Windows 10 pro 1709 image (with Virtual Box)

0_1524123955382_Capture6.PNG

I tried several basic steps suggested in this post, but the thing that simply worked for me was tu upgrade fog server… (It was not updated since two or three months)

I can’t reproduce the issue, but it can be a step to try before recreating a new Windows sysprep image 🙂

@quazz Ah ok I understood.
It’s ok for now, fingers crossed !

@tom-elliott Yes, I just test it on RC5, perfect 😉

Fixed the Reboot/Shutdown/None item. Sorry, it was just a missed code logic. I was always setting shutdown or reboot, forgot about the “none” availability. This is now addressed in working.

@Quazz said in Deployement failed on smaller drive (message "Target partition size smaller"):

I’ve made it a habit to just start over every time.

We also find the same thing and create new every time.
FWIW: We use MDT to build the reference image, that way we have a consistent way to “start over every time”.

@x23piracy It works great ! Thanks a lot 😉