@alh The mobile flag isn’t displayed on the list/search pages, though it’s certainly something that can be added.

Fixed in working thanks.

@george1421

https://forums.fogproject.org/topic/9888/remove-your-webroot-redirect-to-fog-when-going-to-rc4/9

This post seems to solve the issue.

@Tom-Elliott will you please slow down!! I was just spinning up a new FOG install to prove out the error!! I guess all I have left to do is go get a beer now and relax.

Dev-branch is back to RC-3 now, thanks.

@Matthieu-Jacquart Working branch will become dev-branch when I push up RC-4. RC-4 hopefully will be out by the end of the week (to address xp deployment issue).

@Matthieu-Jacquart I thought I remember being asked about language packs during installation… if it’s not asking anymore, that needs fixed - could you make a new thread about it please?

@Tom-Elliott should have said, it’s with both

@Tom-Elliott Perfect! Thank you very much!

@Tom-Elliott Understood 😉 I will probably do a custom report to have the information about the images and their partition layout. Thank you again!

@Tom-Elliott You’re welcome. Here are the results after the last modifications you have uploaded. Seems like there are no more errors. Now I’m making the whole deployment to see the final partition sizes in Windows enviroment.

Thank you very much!
0_1489705889913_Captura de pantalla 2017-03-16 a las 23.09.10.png
0_1489705897537_Captura de pantalla 2017-03-16 a las 23.09.32.png

@Tom-Elliott Applied the fix and restarted and working perfect. Thank you very much!

@Tom-Elliott Thank you very much. Updated to RC14 and working perfect.

@Tom-Elliott So will you start including those? I don’t understand.

Sorry! It’s ok!
Agent was stopped for some reason. Now log seems ok.
Thanks a lot!

Thank you very match!

@Tom-Elliott Yep, that was my issue. I’ve updated to RC12 and from what testing that I have done, it seems that everything is working. I’m able to go from a 160GB to a 256GB and also 500GB drive and boot into Windows as well. The resizing seems to be correct as well.

The developers found this issue to why the log file grew so big (after almost a year of log file collection). The log file will now be capped at the log file maximum set by the fog configuration settings. This was just a fluke case that caused this file to grow to an abnormal size.

The fix / log file limiting code will be in 1.3.5RC11 when its released.

Those wanting to see the fix sooner than later please run:

wget -O /var/www/fog/lib/pages/reportmanagementpage.class.php https://raw.githubusercontent.com/FOGProject/fogproject/fee45cb8efe1d783f358589286f78c4cee82a5c5/packages/web/lib/pages/reportmanagementpage.class.php

So the reason the date selector was not being seen was because I am grabbing the minimal date.

Some entries, for this field, might have ‘0000-00-00 00:00:00’ as the date time stamp, which is invalid.

So the original way it worked, if the date was invalid (start time will always be earlier than end time) it would present “invalid”.

The updated method should work for this for all of you having this problem. I’m correcting this behaviour by adjusting the start date to 2 years before the current date.

Hopefully this is sufficient. The reason I don’t want to go back further is the amount of time it would take to generate the selector. (I’m not guessing the selector based on max end date any more. I’m just giving a date range based on the earliest time found and forward (as it’s not really a selector otherwise right?))

I’m also changing the way things are displayed a little bit.

Instead of showing logs of tasks that have either an invalid start OR end date, both start AND end must be invalid to no longer show. It may make some strange readings for things, but shouldn’t hurt anything otherwise.