@george1421 said in Wrong Image Size indicated in the image manager.:
I’ve never seen a windows install with just a single partition (after Windows NT)
…but that was the standard for xp and 2000 pro. it was also easy to configure with windows 7, even though it wasn’t the default.
@daguilar if you no longer have the option of exporting from the old server, you’re probably best off just creating each one manually though the interface. just make sure the “Image Path” field and format info matches the info that goes to the files.
@daguilar it’s all of the info needed to recreate the image profiles. you still have to transfer the image files yourself
@daguilar import/export buttons on the menu of the image management screen
@george1421 i would think it would be sufficient to have a hash of ${serial} ${asset} ${manufacturer} ${product} ${uuid} would be unique (i’ve never seen a manufacturer leave them all blank, and others like MAC can potentially change)
one option is, we could use them all, in a way
we could store them like we store multiple mac addresses, but have fog check the database on new host registration for duplicate identifier data in the database and invalidate those values as “unique” identifiers
@george1421 why rely on a single field? why not take a number of them (asset, serial, uuid, etc) pass them to fog via http request. fog can create a hash from the combined values, and that’s the unique identifier. manufacturers can be very inconsistent as to what they put in each field, but what matters is that we have something unique to associate with the hosts. the hash of a set of the info would be unique.
here’s a demo video using standard 1GbE, a server with a hard disk RAID array (no SSDs), to a Dell Optiplex 3020 with a cheap SSD. https://youtu.be/gHNPTmlrccM
@george1421 it doesn’t sound like they’re using fog elsewhere, so it doesn’t sound like this would be needed
another note, the deploy times when using fog should be similar to what you’re seeing now, if you put those SSD drives in the fog server instead of as a second SSD in the PCs
alternatively, if the current system is working for you and your difficulty in maintaining the current system is in part updating the “imaging” drive of the systems, fog could be used to push out update images to the first drive of the systems.
@george1421 it sounds like the fog server would be exclusively for the lab, so the list of images available shouldn’t be an issue, and they could even set the default iPXE menu item to “deploy image”
@ducarios in “Fog configuration” > “iPXE Menu Item Settings” > “Menu colors, pairings, settings” set
“Menu Background File” to blank
@PITSKing fog pulls that information from the database, not the files. if you recreate the “profiles” for the images and point them to the existing files, they should work.
@Fernando-Gietz We use icinga for all of our servers, but for monitoring a single server in detail like this i like monitorix. you just choose what services you want to monitor and you get feedback screens like this https://www.monitorix.org/imgs/mysql.png and https://www.monitorix.org/imgs/apache.png
@Qyjong FOG image capture and deploy are multi-step processes. each are several commands that rely on scripts and programs in the FOG OS (FOS) and change based on what options you have selected. FOG images are not designed to be used stand alone. Using FOG images without a FOG server will require steps that were expected to be automated and there really isn’t a quick way around it.
@Qyjong FOG uses partclone, just like Clonezilla. but FOG does a lot of stuff that Clonezilla doesn’t. our images are technically compatible though.
FOG automatically resizes partitions and makes sure that data needed to boot is set correctly. but if you want, you can:
manually create/size your destination partitions
pipe your image through the appropriate decompressor (gzip or zstd) into partclone to deploy them
resize the filesystems if needed.
with any luck, it will boot without any extra steps.
@sjensen if it doesn’t exactly match, it should work at least as a rough guide on what you need to do to expand your LVM
@NivMizzet i can’t say i’ve ever tried using fog with Windows CE, but in theory there’s no reason it shouldn’t work. what kinds of errors are you seeing?
@anhphuong all assigned to that host. i agree that being able to select what snapins you want at the time of deploy would be nice, but the logic is tricky and there hasn’t been a lot of demand for it.