Posts made by Joe Schmitt

Uploading an image to FOG will not harm the computer being ‘captured’. All data will still be intact. Just make sure the image type is Re-sizable so that FOG can handle the change is storage size.

We switched to iPXE for several reasons. Primarily for the speed increase by using faster/more secure protocols. It also allows for dynamic boot menu creation. Just because ‘pxe worked’ doesn’t mean it was ideal. A lot of things ‘work’ but shouldn’t be used.

My guess to the solution? Try a different boot file. There’s a reason we included several of them. Some may work with certain hardware and others may not. (See [url]http://www.fogproject.org/wiki/index.php/IPXE#What_are_the_differences_between_the_different_PXE_files.3F[/url] )

Is the computer auto logging into the administrator account after imaging? If so see
[url]http://fogproject.org/forum/threads/auto-logon.12456/#post-42410[/url]

Its a problem with your AD settings in FOG.

A quick search of that error code reveals:
[url]http://fogproject.org/forum/threads/join-domain-unknown-error-code-2.11827/[/url]

It sounds like you want CloneZilla for local imaging

[url]http://clonezilla.org/[/url]

Just burn a live iso onto a cd or usb and boot into it on your computer.

This would indicate your image has auto logon enabled.

See [url]http://superuser.com/a/21619[/url] for how to disable it on your computer. You will need to re-upload.

Per-request a patched version of the HostNameChanger dll with the default pass key. Please ensure the file name is correct (it may be wrong).

[url]https://dl.dropboxusercontent.com/u/18664328/HostNameChanger.dll[/url]

Sorry about that, I didn’t see you included that info. It would seem that you did not build with the patched version. SVN no longer includes our legacy client and the source file in fog_1.2.0.tar.gz is not patched. Please use this version instead:
[url]https://github.com/FOGProject/fogproject/tree/4b6a98a5a5ab552fbe066e062af857b33a17a15f/FOGService/src/FOG_HostNameChanger[/url]

Please do the following:

[quote=“Jbob, post: 36278, member: 21733”]It would seem some incompatible data is being retrieved by the Client. In order to help your further I would need to see the data the client receives (you may asterisk out any information you feel should remain private such as your AD password. If you still feel uncomfortable with posting the information you may PM me with it). To see what data is being sent, get the MAC address of one of the clients that is failing. Then open a browser tab, and go to the url (change the bolded parts as needed):
[B]FOG_SERVER_ADDRESS[/B]/fog/service/hostname.php?mac=[B]XX[/B][B]:XX:XX:XX:XX:XX[/B]

And then post/pm me the output shown (remember to asterisk any private info)

I also need to know if you are using the prebuilt HostnameChanger.dll or you compiled your own version.[/quote]

Just to pipe in, Junkhacker is spot on. The old client breaks in quite a few places when you wander past Windows XP. The new client [B]does[/B] support Green FOG on xp+, in fact its already been developed and will be available in the initial beta release of the new client.

Glad someone noticed the new site ^^. We wanted to make a new one for awhile now, but the opportunity never really presented itself. What you see is the result of one hectic weekend with Tom and I playing a balancing act between our normal work routines, constant work on finding a color scheme the whole development team liked, and trying to throw together something presentable. It was a busy weekend.

Assuming the title is correct, and you are running 0.32, please upgrade. It is very difficult for us to support old versions, especially all the way back to 0.32 as many things have changed since then. (We are on 1.2.0 as our latest stable release)

It sounds like you’re encountering the update where we switched to base64 encoding the product keys. You’re seeing this problem because you entered the product keys on a version that did not encode them, and the version you upgraded to is expecting encoded keys. You can either re-enter them OR go through the SQL database and base64 encode all of the keys.

Ubuntu 12.04 should work perfectly fine, in fact I recommend using it over the newest version of Ubuntu. That “package” is the only one you need. Just follow the instructions you copied and you should be good to go. Let us know if you have any issues.

To reinforce what Hales is saying, downgrading is a very tricky business. The SQL database that FOG uses evolves with some of our SVN updates, that’s why when you upgrade you have the “Schema upgrader” web page. In order to downgrade you would either need to start form scratch or manually revert the db to its prior state, which without backups would be quite an accomplishment. You’re best bet is to keep trying the latest svn (we release new builds daily), and keep debugging, this sounds like a network configuration issue.

Inline with what Lee said, AutoIT is a fantastic scripting language. I would actually recommend checking out singleinstance, its a free application (built on AutoHotKey), that does exactly what you want. The source code is available for viewing so you can customize it as needed.

This site includes a download link and the usage of the program
[url]http://www.freewaregenius.com/singleinstance-allow-only-one-running-instance-of-a-program/[/url]

Could you upload c:\fog.log on a machine that isn’t joining the domain?

With the current setup the computer always tries to rename & join itself every boot-up. The only case where renaming doesn’t happen is if the service detects the name is already correct. What situation are you encountering which provides the issue?

Could you provide more details? What version of FOG are you running and could you upload the fog.log file?