Posts made by Joseph Hales

Updated to SVN 3365 seems to have fixed the issue.

Maybe not I downloaded this one on 4/24/15 also could we add .log to the allowed extensions for file uploads to the forums.

After upgrade to SVN 3364 same issue.

[url=“/_imported_xf_attachments/1/1973_FOGtroubleshoot.log.txt?:”]FOGtroubleshoot.log.txt[/url]

Seems to be certain systems but they do pass on the FOG compatibility test. I am upgrading now.

Here is a sample I am seeing; SVN 3363, Kernel 4.0, on Ubuntu 12.04 also tried the two previous kernels it is a Dell Latitude E5420.

[url]https://dl.dropboxusercontent.com/u/24177483/2015-05-06 15.23.53.3gp[/url]

I’m a fan there can be teething issues but a lot of improvements.
[url]http://www.fogproject.org/wiki/index.php/SVN[/url]

Works SVN 3353.

The answer depends on which version of FOG you are running. For example SVN in its latest build wouldn’t require sysprep or fog prep with your setup as described and the fog client would register windows for you as well.

I forgot about the mountcheck file create it with this command.
[FONT=Calibri]sudo touch /images/.mntcheck[/FONT]

Reset permissions and ownership with the following commands.
sudo chown -R fog.root /images
sudo chmod 777 -R /images

Confirmed I see the same issue even after a forced refresh on SVN 3352.

Install FOG client for everyone you no longer need to run fog prep for fog 1.2 and up.

Windows 7 ultimate and Enterprise include bitlocker as well as windows 8 and 10.

I think need2 may be on the better track here especially if it is an AD environment you should be able to control everything via policy and still use re-sizable images or even syspreped universal images. You will want to limit encryption to home directory’s because there is a performance hit whenever you access encrypted data.

The main concern now is the resizing of images that you reported at the beginning. I am testing weather or not re uploading the images will solve the inconsistencies.

Repeat after me the mantra Logs are our friends, Logs are our friends.

What is the output of the fog.log when it fails to join. Also double check under the host record in Service Settings that hostname changer, and host registration are both checked when this was added to the host records all service settings defaulted to unchecked.

AD join has been working reliably for me almost all the issues in the forums have related to the encrypted password in the config being corrupt in some manner and re encoding and pasting it back in has fixed it. The other issue is generally that the account has been locked for some reason be sure to manually join one machine with the same account to make sure its not something simple like expired account or locked due to failed password attempts.

I am using the legacy client so I have [SIZE=13px][FONT=Ubuntu][COLOR=#555555]FOG_NEW_CLIENT unchecked and the password filled in for [/COLOR][/FONT][/SIZE][SIZE=13px][FONT=Ubuntu][COLOR=#555555]FOG_AD_DEFAULT_PASSWORD_LEGACY.[/COLOR][/FONT][/SIZE]

Let me know if you still see the resizing issue I am fighting the same bug here [url]http://fogproject.org/forum/threads/images-not-expanding.12811/page-2[/url] as of SVN 3348 which I updated to at 7:30 am but of course an hour later and we already have 2 more releases.