@mr626 said in How to upgrade to 1.4.x?:

I normally checkout the trunk, which would always get me the latest 1.3.x release. Has this changed?

That hasn’t changed. But I would recommend that you use git instead of svn. FOG’s git repository is in github. FOG’s subversion repository is in SourceForge - and sourceforge is less than reliable and is getting a pretty bad reputation.

In the upgrade to trunk article in the wiki here I’ve completely removed the svn steps to discourage people from using the sourceforge repo.

@jloke said:

Looks like we’ll use the realtek file to take care of this laptop, then change back to undionly for our general use.

@george1421 said:

But the idea is that you will use the system’s guid to dictate what kpxe file the dhcp server will reply to the client.

If the Vendor Class identifier is unique from other models, it’d be easier to use a vendor class identifier in ISC-DHCP. We already have an extensive article detailing how to do this:
https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence#Building_custom_DHCP_Classes_for_co-existence_with_FOG

Sounds like you now need to troubleshoot FTP.

Take a look at this: https://wiki.fogproject.org/wiki/index.php/Troubleshoot_FTP

Let us know if you figure it out, or if you need more help.

Here’s a hint… Credentials

I disagree. I like it exactly how it is.

If I set a setting on my “ALL BUILDING COMPUTERS” group for joining to AD, That’s cool, because at that moment, I want to make sure all building computers are set to join to AD using whatever credentials I put in.

However, later on, when I’m updating an image and I disable domain joining for a particular computer - so that it does not join the domain when I deploy an image to it, and so I can update and re-upload without mucking up my image, I definitely do not want groups to just automatically re-tick the join domain checkbox.

There are other examples, too. I don’t want any changes made to the group functionality.

You’re most likely going to need to do this differently. Look through this article - there are several examples: https://wiki.fogproject.org/wiki/index.php?title=Include_any_ISO_in_the_FOG_Bootmenu

@Matthieu-Jacquart Don’t give up. Guys like you are exactly what FOG needs to move forward. Your work with Sebastian is VERY appreciated by the whole fog community!

@afmrick

That’s very interesting. Another guy is having the exact same issue (I think), but he’s found another work around (equally unacceptable in nature though).

Try making a simbolic link to /images/780/d1p2.img.001, pointing at the actual files… I bet it’d work.

[CODE]ln -s /images/780/d1p2.img /images/780/d1p2.img.001[/CODE]

Then ensure the sym-link has the right permissions:
[CODE]chmod 777 /images/780/d1p2.img.001[/CODE]

If that works for you, we can build a script that can do this for all of your images in mere seconds.

Let us know, I’m very interested.

@Arrowhead-IT said:

What if you forget the automation part of my feature request and focus on the persistent part. As I’m utilizing groups more and more I would really like it if I didn’t have to manually select snapins and printers everytime. It is convenient to be able to add the same things but I’d like to have a static template type of thing. Every host in this group needs these snapins type of thing. Maybe I’ll just make it a plugin at some point if I ever get any extra time

That’s a much better approach.

But I’d say that “templates” should be a special kind of group - it’s just a group that you can actually save settings to. Then - when you want those applied you’d just go to that group and click an “Apply” button with the settings you previously put in already there for each of the settings areas.

I suppose we could create a fake host for each template - and have the template groups auto-load settings from the fake hosts - just as the regular hosts auto-load their own settings from the DB.

Still a far cry from being done though.

Future readers - and @fmslick - please bear in mind I am recommending in this particular instance to use DRAC instead of FOG because these are servers that already have DRAC and the ability to boot from an ISO using their DRAC card. If the case was with an end-user’s workstation, we would go the FOG route.

@Sebastian-Roth Doing my best.

Oh and 1.2.0 might be the “stable” release, but it’s probably got more bugs than the Trunk version at this point.

1.2.0 is quite aged when you compare it to the Trunk version. You’ll also find increased performance in Trunk, and a wider range of supported hardware.

And, everyone that hangs here has seen time and time again how fast Tom (the senior developer) can squash a bug. Most of the time though, it’s user error and not bugs.

And if you want to do any Win8 imaging, you’ll need the Trunk version.

I don’t know what Mobscene is. Could you share a link?
I did try googling it, a bunch of Marilyn Manson stuff is returned in the search.

@Sebastian-Roth I’ve not heard a thing from that building’s techs about this issue. If they try to get this model working with FOG in the future, I’m sure they will Google search it and find this thread, wouldn’t that be humorous?

I’m working with one of them tomorrow, I’ll ask about it.

@ITBOYS said:

Just looking back and the image size on the server still displays zero.

The server size would display zero if the images are stuck in /images/dev

Did you look at the credentials section of that article?

@george1421 said:

We can script it - I’m confident we can.

@tandersb said in Cannot capture image- fails at 'Saving original partition table':

Is there a mailing list I should be on to get notified of new releases?

Release Candidates and Releases are in the Announcements area:
https://forums.fogproject.org/category/22/announcements

But currently news.fogproject.org is not working.

Latest version is also shown right on the FOG login screen, and in FOG Configuration area too.

@george1421 fixparts /dev/sda

However, this only affects uploads.

I think something else is going on.

is it an SSD?

Try single disk - resizeable. and under “partitions”, choose “everything”.

Also - a photo of the error you’re seeing would help greatly.

Moved to feature requests.