Found this article: [COLOR=#0000ff][U][url]http://www.fogproject.org/wiki/index.php/FOGCrypt[/url][/U][/COLOR]

[COLOR=#000000]Suggestions are being taken on how to improve all parts of the WIKI.[/COLOR]

Nevermind me. I figured out what the different parts being recompiled actually do. Maybe next time I’ll wait until after my morning caffeine has kicked in to ask questions like this :rolleyes:

extract the FogCrypt.zip file to a Windows computer running .Net Framework 2.0 or better.

Open the command line and “cd” to the FogCrypt folder you made. Then do this:

[CODE]c:\FogCrypt>FOGCrypt.exe password

Input string: password
Passkey: FOG-OpenSource-Imaging
Output: 52498fbfb2bba2c02ec81c17036949b9
[/CODE]

try this from a terminal:
[CODE]user@fog:~$ mysql -u root[/CODE]

If you get a prompt like: “mysql>” then your root user has no password.

If you get an error saying “ERROR 1045 (28000): Access denied for user ‘root’@‘localhost’ (using password: NO)” then your MySQL root user now has a password. Remember what you set it to, or figure it out. Then update /var/www/fog/commons/config.php and /opt/fog/service/etc/config.php with the MySQL root user password.

Check your apache log for errors.

Did you upgrade mysql as part of the Ubuntu upgrade? If so, you may have given it a root password, which means you need to update your fog config files.

Most of this in in the wiki. You’ll have to piece it together though. Install Fog on Ubuntu 10.04 LTS as it’s the most supported and easiest to use right now. Then look at the articles and forum posts explaining how to image, upload, and deploy.

If you create a tutorial covering all this, post it in the tutorials section. We’d be glad to have it.

Anyone care to translate to english? I tried google translate and it didn’t make things any clearer.

If the passkey is specified in the ini file, why do you have to change it in source and recompile the DLL when you want to change it? Cryptography is not my strong point, but it seems that the ini file is meant to allow you to update your passkey for securing AD integration without have to recompile the client.

Did you try the Express version of 2008?

I don’t know if the Express version will work, but it’s worth a try. I think you’ll need the C# package.

If you have another NFS server (linux or other OS that can export NFS volumes) then you just need to export the folder and then mount it on the Fog server as /images.

It will have to be read and write, and you’ll need to create your .mntcheck files in the root and dev folders.

Where does it fail? Does it deploy successfully but not boot, or does it fail during the deploy. If it deploys but won’t boot, you might try to AHCI settings in the bios on the Win7 machines. More than likely, it is set for Win7, but not for WinXP.

If it fails during the deploy, you might try to schedule a Fast Disk Wipe task, then a deploy of the WinXP image and see if that helps. Test it on one machine, and if it works, group the remaining Win7 machines together and run a fast wipe task, then deploy.

If none of that works, we’ll continue to dig to see if we can find the issue.

I think we’ve moved the troubleshooting to the thread over in the Technical Help forums and abandoned this one in the Developer forums.

I will try to rephrase your questions to make sure I know the details of the issue:

1. You had Fog working fine a month ago
2. Fog quit working for some unknown reason
3. You restored your images from backup
4. Fog still does not working properly

Is this the correct series of events or am I misunderstanding anything?

Is this error in the WebUI?

cool ideas. I hadn’t thought about moving the upload to advanced tasks, but that would prevent some people that are either click-happy or just not paying attention from wiping out their images with junk.

Being that Fog is meant for system admins and technicians, I think the hope is that the users would be careful enough to read and make sure they are clicking the correct button and would learn from the first mistake the high cost of being click happy.

The groups in Fog are for applying settings 1 time, to many hosts. The groups do NOT retain any of the settings. If you put 20 hosts into a group, you then set the options for the group 1 time, and it applies to all 20 hosts. The “group” has no properties other than the hosts that are in the group.

Basically, groups are a way to change settings on multiple hosts at one time, but they do not retain or enforce any of those settings after that. They only remember what hosts are in the group.

If your clients are using DCHP to get their IP address leases, then you should be able to use Fog. DHCP with static lease information is still DHCP, and that enables you to use Fog. You can update your DHCP to use Option 66 & 67 (windows dhcp) or next-server and filename (linux).

If you can’t modify your DHCP server, or don’t want to mess with it, you can use ProxyDHCP to handle the PXE Boot requests, and your regular DHCP can handle the IP address leasing.

the only passwords encrypted with FogCrypt are those you setup for Active Directory integration. I think the rest of the passwords are random strings.

Also, there is a fog user for the WebUI and a fog user in the OS used for a couple of things including TFTP I think. Make sure you are looking/change the correct one.

I don’t think it’s a something with the fog server. This may be a problem with the PXE boot rom of the motherboard/nic. Try booting using gPXE boot disk/flash drive and see if you get the same error.