@Sebastian-Roth said in Deploy one Linux Mint image to computers of different manufacturers?:

I am not sure if Mint does some fancy things like LVM partitioning, home partition encryption or similar stuff FOG cannot handle. Make sure you choose a simple plain partition layout when installing the master image machine and you should be fine.

My daily driver (not in the office) is a Linux Mint system (ubuntu based). It just has standard partitions not lvm.

As Sebastian said, you can get near windows like deployments with most linux distros if you want to do it manually through post install scripts or via the FOG client. I can say I’ve never used the fog client as part of a FOG linux deployment.

One other comment, I have a how-to on netbooting your favorite distros to where you can live boot linux mint on hardware without installing it first for testing purposes here: https://forums.fogproject.org/topic/10944/using-fog-to-pxe-boot-into-your-favorite-installer-images

Well, The cron syntax wouldn’t “disappear” unless your web front end translates the date/schedule to a Cron style system automatically.

Yes the idea should be possible, though I don’t know how best to help except to help provide basic syntax of the API so you can process and parse the data that’s returned.

I guess, though, I don’t fully understand the why. Everything (with exception of the scheduled cron tasks) is already available via the GUI we provide as a part of our software. “viewing said Scheduled tasks, view active tasks, and when a system is added to the host list that host will be added to the web page” are already done with the provided interface. Why create a new hen-house when the one you got with the land is also a hen house that does everything you need it to do.

@huatrongkhang Currently FOG is not able to deploy WIM images. But we are an Open Source Project and everyone is welcome to add features as needed. Can’t remember exactly but I think this has been discussed in the forums at some point already. Use the forum search.

@george1421 ok i Don’t Think about that. I Will do the corrections tomorrow. What about the rest of mounts?

Because the image is extracted and compressed it would be more than difficult to make that a live image where you can patch it and then reseal the image. It would be faster to deploy it to a VM patch and then recapture. But with this method you will run into a limit on the number of times you can sysprep an image. There are workarounds but its just one more hoop to jump through.

I can tell you how my company handles this (which may not be the best way for you), we use Microsoft’s Deployment Toolkit to build our reference image using the lite touch method. So every time we need to update the golden image we make the adjustments in MDT and then have MDT rebuild the golden image, we then sysprep it and capture with FOG. MDT gives us a consistent golden image each time we run the task sequence so we don’t need to validate the image each time its rebuilt. That single captured image is then deployed to our fleet of 14 different dell models. One image for all. (truth be told its 2 images for all, one is for bios based computers and the other is for uefi based computer. MDT builds them both the same way for us).

@george1421 @THEMCV Wiki is online again. Thanks for letting us know!

@astrugatch said in See last time a computer checked into FOG:

----------------------------------UserTracker--------------------------------- ------------------------------------------------------------------------------ 9/17/2019 3:06 PM Client-Info Client Version: 0.11.16 9/17/2019 3:06 PM Client-Info Client OS: Windows 9/17/2019 3:06 PM Client-Info Server Version: 1.5.7 9/17/2019 3:06 PM Middleware::Response Success ------------------------------------------------------------------------------

This is all perfectly fine - Response Success as you see.

@TammyTinkleToes90

It’s possible the previous admin scheduled a daily image deployment that contains a broken NIC driver. (check scheduled tasks)
The second possibility is a snapin that is done every day. (check snapins)

Check fog client hostname settings

Some devices have somewhat buggy UEFI firmware, especially with network boot. BIOS update might help.

Oh… I didnt even think about it that way. Especially that we have the “locked” state for the same purpose, prevent accidental deletion. Actually it is a double of the double protection. Not truly bad, but… strange design.

@zaboxmaster Lets switch over to IM chat because there are a few questions I have. Look at the chat bubble and the top-right of the forum tool bar

@Sebastian-Roth i understand the reasoning for not updating it. i’m hoping to have a chance to help with testing by the end of the week.

Hello,

I have now configured the samba and now is the setup starting.
But it takes nearly 8 minutes until the setup prompt is shown.

Because I am not a linux expert there can be one or two little mistakes. I trie to discribe my samba setup.

Debian 10

first installed the samba

sudo apt-get install samba -y

then save the config

sudo mv /etc/samba/smb.conf /etc/samba/smb.orig

create a new config

sudo gedit /etc/samba/smb.conf

(yes I need a little bit gui support)

then I created a smbuser and gave him a password

sudo useradd -s /bin/false smbuser sudo smbpasswd -a smbuser

my smb.conf file

[global] workgroup = smb security = user map to guest = never [homes] comment = Home Directories browsable = no read only = no create mode = 0750 [Windows10] valid users = smbuser #Wir beschränken den Zugriff auf den User ''smbuser'' #valid users = @smbusers #Alternativ kann auch auf eine Benutzergruppe eingeschränkt werden path = /images/os/mswindows/10Pro-x64/ public = no writable = yes comment = Windows 10 Setup-Ordner printable = no guest ok = no create mask = 0600 directory mask = 0700

then I assigned the smbuser to my directory and gave him rights

sudo chown -R smbuser:smbuser /images/os/mswindows/10Pro-x64/ sudo chmod 700 /images/os/mswindows/10Pro-x64/

and at least I restarted the smb

sudo systemctl restart smbd.service

I customized the startnet.cmd(WinPE) for my smbuser and thats it.

I have run a test installation on my old client and it completed successfully.
But the start of my setup takes realy long…

Did anybody see a mistake or has a optimization for me?

(I found the discription for the samba in the german Thomas-Krenn-Wiki: https://www.thomas-krenn.com/de/wiki/Einfache_Samba_Freigabe_unter_Debian and https://www.thomas-krenn.com/de/wiki/Samba_Freigabe_mit_Authentifizierung )

MfG
Tsche

@khanhvd21 Take a look at the apache and php-fpm logs (see my signature) and post those here.

Which version of FOG do you have and how many clients are in your network with fog-client software installed? Is this a single master node setup or do you have one or more storage nodes?

@gaelds Any news on this?

Thinking a bit more about your request I wonder about something. Where have those 700 PCs being used before? They seem to have Windows and the fog-client software installed. So my guess is they were in use maybe in a different department. Were they connected to that exactly same FOG server ever before?

I have found a bit of time to test this myself and I cannot replicate your issue as described. What I did is: Imported a single host via CSV, started the client and watched the fog.log and saw that it connected and renamed perfectly well.

So I guess Quazz is on the right track here. Please let us know what you find.

Thank you. This will help answering some questions on my end.

No, no, sorry for not clarifying. It’s just an open question, because I’ll do it, but we don’t know if it would work or not. 😄

Thanks for clarifying George. I will do and test and if we encounter any error or problem, i will ask here for support. Thanks again!!! 🙂

Regards.

@astrugatch Good to hear! Thanks.

@toanns35 FOG 0.32 is more than 8 years old (!!) and shouldn’t be used anymore. Ask yourself, would you choose to install Windows 98 on current hardware? If you still want to use version 0.32 it’s up to you but we won’t give you any support on this. We are trying to improve FOG working on the most current version and help people to upgrade to recently new version.

FOG (1.5.7 as of now) definitely runs in VM. Though there are different technologies and I can’t speak for all of them. I use VirtualBox for testing, I know people running it in VMware while others have XenServer and Hyper-V. Search the forums or ask here if you have specific questions.

@toanns35 Welcome to the forums! Great you find this helpful. The search definitely does a great job.

FOG including the forums, wiki and so on are just as good as people help organizing it. We highly appreciate people engaging and actually need help to keep it all up to date. It might look like there are many people involved but at the moment it’s just a handful and way too less. See my signature… 🙂

@george1421 said in FAQ page in WIKI should be updated:

@Luc-Novales So let me understand even with the 486 kernel it does not boot, I would expect an error message as in the picture provided.

I made a report of actions in initial thread more adapted…
Black screen and blinking cursor after vesamenu

Thx,
Luc.