Posts made by Baite

@Wayne-Workman I just removed all the values and filled them all again, and now it started working in the new client (didn’t test the legacy one).

@Wayne-Workman
I just need a quick help (I hope). I am having trouble with Renaming computers with the legacy client since I upgraded to latestes version (git). My older version had almost a year. Now I get “FOG::HostnameChanger Failed: Incomplete server response; got: 2; wanted: 6” and “FOG::HostnameChanger Host name was not found in the database”. Now I am trying with the new client. Installed it (downloaded from Fog WebUI) but am getting error at Hostname Changer again:
--------------------------------HostnameChanger-------------------------------

02-09-2015 18:28 Client-Info Version: 0.9.4
02-09-2015 18:28 HostnameChanger Running…
02-09-2015 18:28 Middleware::Communication URL:
http://10.114.187.14/fog/service/servicemodule-active.php?moduleid=hostnamechanger&mac=00:23:7D:51:86:68|0A:00:27:00:00:00||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0&newService=1

02-09-2015 18:28 Middleware::Communication Response: Success
02-09-2015 18:28 Middleware::Communication URL:
http://10.114.187.14/fog/service/hostname.php?moduleid=hostnamechanger&mac=00:23:7D:51:86:68|0A:00:27:00:00:00||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0&newService=1

02-09-2015 18:28 Middleware::Communication Response: Success
02-09-2015 18:28 HostnameChanger Checking Hostname
02-09-2015 18:28 HostnameChanger Renaming host to 2015-HP-nVidia
02-09-2015 18:28 HostnameChanger Unregistering computer
02-09-2015 18:28 HostnameChanger Removing host from active directory
02-09-2015 18:28 HostnameChanger ERROR: Required Domain information is missing
02-09-2015 18:28 HostnameChanger Updating registry
02-09-2015 18:28 RegistryHandler ERROR: Could not set SYSTEM\CurrentControlSet\Control\ComputerName\ActiveComputerNameComputerName
02-09-2015 18:28 RegistryHandler ERROR: Impossível criar uma subchave estável sob uma chave ascendente volátil.

What might be the “Required Domain information”?

@Wayne-Workman In my case, I always use an image WITHOUT sysprep. When the image is deployed to clients, the first thing FOG used to do is to rename the computer accordingly to the definitions and only then it was joined to the domain. Can I still use it like that?
Another thing, is the Printers Management working in the new version?

@Wayne-Workman - Thank you so much for helping me try to fix this out.
Just a question: what is the error “FOG::HostnameChanger Failed: Incomplete server response; got: 2; wanted: 6.”. I never saw it “gotting” 2 - so what does the 2 stand for?

@Wayne-Workman It’s running Windows 7 Enterprise x64 with System Center Endpoint Protection.

All was working fine before upgrading to latest version.

One question: should I try to use the new client? Is it stable enough? Can I have some hosts (older) with the legacy client and all the new with the up-to-date client?

@Wayne-Workman I made what you asked for. All Service Settings were checked, either in the UI and during the installation.

Then I tried something else. Went to Web UI for that host and, in the AD Aettings, pressed the Clear Fields button and then the Update button. Then restarted the client. Still nothing happened.

Went again to the web UI for that host, checked the “Join Domain after image task” checkbox so that the domain textboxes got filled with the default settings and then unchecek the “Join Domain after image task” checkbox. Clicked the update button and restarted the client again.

Then I got some strange info in the log (need to update some client dll).
02-09-2015 17:00 FOG::ClientUpdater File: TaskReboot.dll requires an update.
02-09-2015 17:00 FOG::ClientUpdater File: C:\Program Files (x86)\FOG\tmp\TaskReboot.dll hash doesn’t match server hash!
02-09-2015 17:00 FOG::ClientUpdater Checking Status : UserCleanup.dll
02-09-2015 17:00 FOG::ClientUpdater File: UserCleanup.dll requires an update.
02-09-2015 17:00 FOG::ClientUpdater File: C:\Program Files (x86)\FOG\tmp\UserCleanup.dll hash doesn’t match server hash!
02-09-2015 17:00 FOG::ClientUpdater Checking Status : UserTracker.dll
02-09-2015 17:00 FOG::ClientUpdater File: UserTracker.dll requires an update.
02-09-2015 17:00 FOG::ClientUpdater File: C:\Program Files (x86)\FOG\tmp\UserTracker.dll hash doesn’t match server hash!
02-09-2015 17:00 FOG::ClientUpdater Checking Status : config.ini
02-09-2015 17:00 FOG::ClientUpdater File: config.ini requires an update.
02-09-2015 17:00 FOG::ClientUpdater File: C:\Program Files (x86)\FOG\tmp\config.ini hash doesn’t match server hash!
02-09-2015 17:00 FOG::ClientUpdater 1 new modules found!
02-09-2015 17:00 FOG::ClientUpdater Checking Status :
02-09-2015 17:00 FOG::ClientUpdater File: requires an update.
02-09-2015 17:00 FOG::ClientUpdater Excepção durante um pedido WebClient.
02-09-2015 17:00 FOG::ClientUpdater em System.Net.WebClient.DownloadFile(Uri address, String fileName)
em FOG.SnapinClient.downloadAndDeploy(String localFile)
02-09-2015 17:00 FOG::ClientUpdater Client update will be applied during next service startup.
02-09-2015 17:00 FOG::ClientUpdater Client update process complete, exiting…
02-09-2015 17:05 FOG::SnapinClient Attempting to connect to fog server…
02-09-2015 17:05 FOG::SnapinClient Module is active…
02-09-2015 17:05 FOG::SnapinClient No Tasks found for: 00:23:7D:51:86:68|0A:00:27:00:00:00

Restarted the client again. New error in fog.log:
02-09-2015 17:17 FOG::ClientUpdater File: C:\Program Files (x86)\FOG\tmp\config.ini hash doesn’t match server hash!

Here are 4 versions of fog.ini

1-fog_before_uncheck_and_check.log

2-fog_after_uncheck.log

3-fog_after_check.log

4-fog_final.log

@Wayne-Workman I just uninstalled the client (yes, I used one from a USB pen - but I thought the legacy client was not changed), rebooted and then instaled the one I got from Fog Server.
Rebooted three times.
Still nothing.

The client IS NOT currently bound to a domain.

In the boot menu, the name appears correctly (with the message saying it is regiistered with the new name), but the computer (Windows 7 Enterprise x64) still has the old name and this message.

I forgot to mention that I’m using the legacy client in the computers (clients)

I’ve just updated from an old 1.2.0 installation to version 4557.
Whenever I change the hostname in the FOG Web Interface, computer names are not changed at all, giving this error:
02-09-2015 15:13 FOG::HostnameChanger Failed: Incomplete server response; got: 2; wanted: 6.
02-09-2015 15:13 FOG::HostnameChanger Host name was not found in the database.
What should I do to fix this?
In FOG Configuration > FOG Settings > Active Directory Defaults, in the field “FOG_AD_DEFAULT_PASSWORD” I placed the fog user real passwrd (plain text) and in the “FOG_AD_DEFAULT_PASSWORD_LEGACY” I placed the result of the FOGCrypt with that same password.
Is it normal that both content of those two fields are different? My older 1.2.0 version did not have anyu reference to these two fields - was only one, the legacy.

Well… can you access /tftpboot? [#cd /tftpboot]
What do you see when you type [#ls -alh]? Can you see severall files, including undionly.kpxe and undionly.kkpxe?
Copy commands from what Elliot typed, one by one, and paste them in Linux shell…

Just go to /tftpboot [#cd /tftpboot]
Then rename undionly.kpxe to undionly.kpxe.ORIGINAL (for backup purposes only) [#mv undionly.kpxe undionly.kpxe.ORIGINAL]
Then copy undionly.kkpxe to undionly.kpxe [#cp undionly.kkpxe undionly.kpxe]

I have SVN 1808 and my faulty Multicast started workin… had the same problem as snoopsean stated at beginnig of this thread

[quote=“Meitar Ronen, post: 29681, member: 24536”]Hi,
Yes I think I know how to change the files in the /tftp folder but where can I get the undionly.kkpxe from?

thanks[/quote]
You can download the latest versions from [url]https://svn.code.sf.net/p/freeghost/code/trunk/packages/tftp/[/url] and put them in your /tftboot/ directory.
Remember to backup your actual files, just in case…

[quote=“Meitar Ronen, post: 29667, member: 24536”][IMG]http://fogproject.org/forum/c:\users\meitar\desktop\caputre.png[/IMG]
FOG_PXE_MENU_TIMEOUT= 3
FOG_PXE_MENU_HIDDEN= not checked
FOG_NO_MENU= not checked

I’ve added a print screen…

Thanks[/quote]

THe best thing is to narrow possibilities. You should try, if possible, in a similar PC with idential (equal) hardware and see if that also happens.
If it happens in severall machines, then it might be something related wit the kpxe file not fully supporting your system.
For example, in my case, had to use undionly.kkpxe in place of undionly.kpxe. Do you know how to change this files in /tftpboot/ ?

(using latest undionly.kkpxe - with 2 ‘k’ as my undionly.kpxe file since the original does not work in this system - keeps restarting machine)

Other thing… updated to last SVN and now cannot upload image in this UEFI machine… stays showing errors (all the steps in the image files)

[url=“/_imported_xf_attachments/0/937_2014-06-09 16.27.44.jpg?:”]2014-06-09 16.27.44.jpg[/url][url=“/_imported_xf_attachments/0/938_2014-06-09 16.28.54.jpg?:”]2014-06-09 16.28.54.jpg[/url][url=“/_imported_xf_attachments/0/939_2014-06-09 16.29.11.jpg?:”]2014-06-09 16.29.11.jpg[/url][url=“/_imported_xf_attachments/0/940_2014-06-09 16.29.59.jpg?:”]2014-06-09 16.29.59.jpg[/url][url=“/_imported_xf_attachments/0/941_2014-06-09 16.30.16.jpg?:”]2014-06-09 16.30.16.jpg[/url][url=“/_imported_xf_attachments/0/942_2014-06-09 16.30.57.jpg?:”]2014-06-09 16.30.57.jpg[/url][url=“/_imported_xf_attachments/0/943_2014-06-09 16.31.19.jpg?:”]2014-06-09 16.31.19.jpg[/url]

Trying to upload the image gives some warnings:
(…)
[INDENT=1][B][I]* Preparing backup location…Done[/I][/B][/INDENT]
[INDENT=1][B][I]* Looking for Hard Disks…Done[/I][/B][/INDENT]
[INDENT=1][B][I]* Using Hard Disk: /dev/sda[/I][/B][/INDENT]
[INDENT=1][B][I]Caution: invalid main GPT header, but valid bckup; regenerating main header from backup![/I][/B][/INDENT]
[INDENT=1][B][I]Warning! Main partition table CRC mismatch! Loaded backup partition table instead of main partition table![/I][/B][/INDENT]
[INDENT=1][B][I]Warning! One or more CRC’s don’t match. You should repair the disk[/I][/B][/INDENT]

In [URL=‘http://msdn.microsoft.com/en-us/library/windows/hardware/dn640535(v=vs.85).aspx’]http://msdn.microsoft.com/en-us/library/windows/hardware/dn640535(v=vs.85).aspx[/URL], we can read:
"The protective MBR area exists on a GPT partition table for backward compatibility with disk management utilities that operate on MBR. The GPT header defines the range of logical block addresses that are usable by partition entries. The GPT header also defines its location on the disk, its GUID, and a 32-bit cyclic redundancy check (CRC32) checksum that is used to verify the integrity of the GPT header. Each entry in the GUID partition table begins with a partition type GUID. The 16-byte partition type GUID, which is similar to a System ID in the partition table of an MBR disk, identifies the type of data that the partition contains and identifies how the partition is used, for example, whether it is a basic disk or a dynamic disk. Note that each GUID partition entry has a backup copy. "

Can this be related to CRC testing not being properly executed due to this 32-bit / 16-bit ambiguity between GPT and MBR?

In Fog 0.32 I used MPI type of imaging to upload images and all went fine. I used that same configuration to upload an image to Fog 1.1.0.
In Fog 0.32 deployment worked fine… in Fog 1.1.0 does not work.
I repeat… it’s the same system, the same configuration, the same partitions.

Tom:
Thank you for all your explanations through chat. Decided topost here in case someone else is interested.

In MPI (“Multiple Partition Image - Single Disk (not resizable)”) type, d1.mbr is 18k in size (meaning is a GPT partition information, as you said).
In SD (“Single Disk (NTFS only, Resizable)”), there are no d1.mbr files, only rec.img.000 (8.0 or 8.1M) and sys.img.000 (varies according to image) files.

You understood that I uploaded each type of computer image from the EXACTLY same computer and configuration, once as “Multiple Partition Image - Single Disk (not resizable)” and once as “Single Disk (NTFS only, Resizable)”. And when I deploy this images, MPI does not work and SD works.

My guess is that Fog does not read the disk information the same way in SD as it does in MPI and somehow it manages SD well but not MPI, regardless it is GPT or MB.