Don’t mess up system backup and data backup!

Why you want to backup entire machine daily?

If you have important data in the PC, backup this data only!

Even better - build your infrastructure in this way, that the important data is not in the users PC. Set up network fileserver/NAS or other storage, cloud etc and keep your important files there - via automatic script or other method!
Of course the fileserver/NAS should be backup’ed as well - but most likely those will already include some failsafe methods (RAID etc.) in case of disk fail.

If PC fails, then replace the PC, deploy ready-to-use system image (with all your important software) and reconnect to the fileserver/data source. Thats it!

This way you have the flexibility (to restore even single file only - not entire PC) and it is also cost effective.

Hello!

/var/www/html/fog/management/index.php

Please include following code in the end of the file - to make the fog menu buttons provide better UX. So that if clicked on menu item, lets say hosts, then all hosts will be shown, instead of clicking on menu button and then list all hosts.

if (isset($_REQUEST[‘node’]) && $_REQUEST[‘node’] === ‘host’ && empty($_REQUEST[‘sub’])) {
header(‘Location: index.php?node=host&sub=list’);
exit;
}

if (isset($_REQUEST[‘node’]) && $_REQUEST[‘node’] === ‘image’ && empty($_REQUEST[‘sub’])) {
header(‘Location: index.php?node=image&sub=list’);
exit;
}

if (isset($_REQUEST[‘node’]) && $_REQUEST[‘node’] === ‘user’ && empty($_REQUEST[‘sub’])) {
header(‘Location: index.php?node=user&sub=list’);
exit;
}

if (isset($_REQUEST[‘node’]) && $_REQUEST[‘node’] === ‘group’ && empty($_REQUEST[‘sub’])) {
header(‘Location: index.php?node=group&sub=list’);
exit;
}

@hariskar

I didn’t really catch the described use case…
But anyway, if application stores something in the database, then the database need to be backed up, of course. Fully and incrementally also (separate logic).

If you use application that stores data in the same machine where it is installed, better would be to configure it to store data on the remote database, e.g on specific database server or some other way.
You can create network drive or other remote storage and point your database files there - if needed to be separate (for each PC).

This way you have all the data in the same place, and you can make backups of this server or drive more easilly.

Backuping entire PC with database in it - this can be done, but why?
It feels strange.

Example:
Lets say, employees in your company are working with important documents.
Do you really want to backup of entire PC (with os and applications and data), instead of storing those documents on secure and reliable remote storage?
Better solution is to simply make network location (local or in cloud) and let the users to store documents there - so the documents would not be lost if some pc dies.
If PC dies, then you simply replace the pc and deploy ready to use system image.

Don’t mess up system backup and data backup!

Why you want to backup entire machine daily?

If you have important data in the PC, backup this data only!

Even better - build your infrastructure in this way, that the important data is not in the users PC. Set up network fileserver/NAS or other storage, cloud etc and keep your important files there - via automatic script or other method!
Of course the fileserver/NAS should be backup’ed as well - but most likely those will already include some failsafe methods (RAID etc.) in case of disk fail.

If PC fails, then replace the PC, deploy ready-to-use system image (with all your important software) and reconnect to the fileserver/data source. Thats it!

This way you have the flexibility (to restore even single file only - not entire PC) and it is also cost effective.

Yes, you are right!
I can confirm that it is still functional.
Install clean Windows 11 + drivers + all the updates -> configure windows as you like it -> sysprep -> shutdown -> Image -> Deploy.

Although, I have searched the answer for the main question, to sysprep or not, for years!
What I mean, is that if you sysprep, some of the Windows settings and configuration will be wiped out during the sysprep, so you cannot configure image 100% ready and need some manual steps after the cloned pc (deployed) boots up.
Of course those manual configurations can be automated (by a script or some other way), but still, it would be nice that image can be setup without sysprepping if it is not needed anymore in Win10/11.

I have tested hundreds of PC-s in domain environment without sysprepping - they work flawlessly, no issues with Domain, WSUS or other things, but I am little bit worried, that if some issues arise, e.g some weird errors then I must reinstall all the deployed pc-s with sysprepped images…

Can somebody confirm?

Yes, I understand, that without sysprep, all the PC-s deployed from the same image will be using same SID, but is it bad somehow?
Can someone confirm that for Intune it is also OK?
Domain doesn’t care, WSUS either, but what else might break?

@rodluz yes, directly from 1.5.10.1754 to 1.5.10.1763 when I saw the prompt in the FOG gui that I’m not using the latest version - it was up to date before.

in 1.5.10.1754 recapture didn’t added up, just updated the image size to the latest one.

After updating fog to latest stable, when capturing an image, it doesn’t calculate the image size on client correctly.

E.g old image was around 40G, when recaptured onto same image, it ended up around 80G and now third attempt made it around 120G.