Latest Development FOG

[Wayne Workman]

[quote=“Tom Elliott, post: 45656, member: 7271”]SVN 3262 released.

This release adds a new feature an new FOG Setting category called Non-registered Host Image. In this option comes a FOG_NONREG_DEVICE field that you simply place like you would the kernelDevice on a host. This will then be read during imaging and target that specific device as long as it exists. I believe it fails if that device does not exist. This is a global value, so if it’s set, any Non-registered host regardless of image chosen will attempt to choose this disk. It’s simple enough to fix though in that all you need to do is delete the setting in order to have it choose the device for you.

Hopefully you enjoy,[/quote]

Are the OS disks normally all named the same thing, like sda or something?

[Tom Elliott]

Normally, in a perfect world, they would be. However, this is not a perfect world. Even if everything did come up with /dev/sd{[a-z],[A-Z]{2}} every time, there may be a case you want /dev/sdc to be the drive that’s imaged to, over /dev/sda everytime. People have different setups for their environments all the time.

[Tom Elliott]

SVN 3275 released.

This isn’t anything overly special just wanted to keep you informed. Basically it has a slightly better way to handle disks. Hopefully it works slightly better, but just know it is an every growing in-progress thing.

[Ray Zuchowski]

Tom,

Just went to 3275 and I cant update my database or pull up the gui. : (

Ray Z

[Ray Zuchowski]

Tom,

Fog Gui loads to the schemeupdater URL page but the screen is blank.

[need2]

Got apache logs?

[Tom Elliott]

We fixed the issue on the backend. Basically it was the checking. Ubuntu (what a surprise) didn’t like the way it was being checked. It should work across the board now.

[Ben Warfield]

Found a little quirk in SVN 3275. When I boot to fog and choose full registration and do a question mark to get the image list, the list is all over the place. It used to be formatted in a nice column and press enter to go to the next page.

[Tom Elliott]

Update to SVN 3281 and this should be fixed for you.

[Bill Rice]

Ok i found a few things maybe nothing but noted in new client log files…

--------------------------------Authentication--------------------------------

4/22/2015 8:51 AM Client-Info Version: 0.7.2
4/22/2015 8:51 AM CommunicationHandler URL: [url]http://ROXMINTFOG/fog/management/other/ssl/srvpublic.key[/url]
4/22/2015 8:51 AM CommunicationHandler URL: [url]http://ROXMINTFOG/fog/management/index.php?sub=authorize&sym_key=51ae36a8493bbb916bf910fb23dfc3712077d22ea12d9b574be21ef46497ad4e95824274124b8c631c5d3cbf3d415819faa2cbc17a0bfb87ba0b02543bb68ee4520e58c4c78684778e281329055bfd3d0d00fc4c97e1b0568a38d6f5e7c55e36e12bbf25251ba864e419a373f1c8ea39ba2ddc9e3303c7aa7777bbcca3d41241a299d709ee0821836302ef5368d9b716d02c81dfd95aab82ccacd13ed37c85eb4b3cddfabbdbacb55e10fe8bdaf45c2f5253e43595341be9ed5212b00bdaf18abe3e0f7ca5819fc2e789202d3c704191215a2922eb803ea48a16b98d808433a538085829315c0d701f586754fd0a46cfd615c0cca1c826668accccd765f79a434d3d7556b9befda6a6a65e5203c765a0279529de7d6d27606cce6730f3bf650f8254178d31c8011f05caedaf6b7666a89b9e83b4314be3cb35d4b24f26951c1cec1c77046b4af34f0c78f1d86737b12e932ac421989c4a7928a56e90b9c9a8db1673b9891820bb1a202d395b2e6865d1ae680a6b26827f4372b5fd6e2ff27db81b87fcfa688ed6a76350710b3b7c51b56b4834c273c6421bd4fc501c89112eb882c52ff62b4ca9086efd7f1ed94ebe5c83436434c5e27d2520d0f19d8c232f103c01ecd26bbb8c62a92fa29c64fb095467e5f712cc4c1a80c86c74188fc656aef96088f662add3259b58fb3c3c2ada93124154109cd92a06017707071ad764e5&mac=CC:3D:82:94:79:F0|CE:3D:82:94:79:ED|CE:3D:82:94:79:EC|CC:3D:82:94:79:EC|54:EE:75:49:30:B4||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0&newService=1[/url]
4/22/2015 8:51 AM CommunicationHandler Unknown Response: Failed to decrypt data
4/22/2015 8:51 AM CommunicationHandler Failed to authenticate
_

Also latest SVN 3284 updates, however in FOG and under settings it still shows version of 3283 doesn’t update the info…

Noticed this as well for host name changer…
-------------------------------HostnameChanger-------------------------------

4/22/2015 9:02 AM Client-Info Version: 0.7.2
4/22/2015 9:02 AM HostnameChanger Running…
4/22/2015 9:02 AM CommunicationHandler URL: [url]http://ROXMINTFOG/fog/service/servicemodule-active.php?moduleid=hostnamechanger&mac=CC:3D:82:94:79:F0|CE:3D:82:94:79:ED|CE:3D:82:94:79:EC|CC:3D:82:94:79:EC|54:EE:75:49:30:B4||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0&newService=1[/url]
4/22/2015 9:02 AM CommunicationHandler Response: Success
4/22/2015 9:02 AM CommunicationHandler URL: [url]http://ROXMINTFOG/fog/service/hostname.php?moduleid=hostnamechanger&mac=CC:3D:82:94:79:F0|CE:3D:82:94:79:ED|CE:3D:82:94:79:EC|CC:3D:82:94:79:EC|54:EE:75:49:30:B4||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0&newService=1[/url]
4/22/2015 9:02 AM CommunicationHandler Response: Invalid host certificate

I see invalid host cert. Is this something to concern myself with? Im going to see if the renaming function is working I’ll report back on that shortly.

[Bill Rice]

Ok after attempting to force a host name change it appears it still isnt working correctly. I am going to change it back to the legecy client and test again.
report back in a few with update.

[Ben Warfield]

[QUOTE]Update to SVN 3281 and this should be fixed for you.[/QUOTE]

Yep, looks good.

[GregorS]

Hello,

I have updated FOG to the SVN Version 3293 and after I’can’t add PC to a domain.
I assume that error [I][B]Unknown return code: 1326[/B][/I] in text below means ERROR_LOGON_FAILURE,1326 (0x52E),The user name or password is incorrect. [url]https://msdn.microsoft.com/en-us/library/windows/desktop/ms681385(v=vs.85).aspx[/url]

I have tried to recreate the domain password with new FOGcrypt but the result is the same.
Normally through windows I can add PC to a domain with the same username&password as used in FOGcrypt

In FOG Settings -> Fog Service -> FOG_NEW_CLIENT is enabled. It doesn’t make a difference if I disable it.

-------------------------------HostnameChanger-------------------------------

24.4.2015 9:46 Client-Info Version: 0.7.2
24.4.2015 9:46 HostnameChanger Running…
24.4.2015 9:46 CommunicationHandler URL: [url]http://10.241.231.11/fog/service/servicemodule-active.php?moduleid=hostnamechanger&mac=6C:0B:84:09:CB:44||00:00:00:00:00:00:00:E0&newService=1[/url]
24.4.2015 9:46 CommunicationHandler Response: Success
24.4.2015 9:46 CommunicationHandler URL: [url]http://10.241.231.11/fog/service/hostname.php?moduleid=hostnamechanger&mac=6C:0B:84:09:CB:44||00:00:00:00:00:00:00:E0&newService=1[/url]
24.4.2015 9:46 CommunicationHandler Response: Success
24.4.2015 9:46 HostnameChanger xyz1:XYZ1
24.4.2015 9:46 HostnameChanger Hostname is correct
24.4.2015 9:46 HostnameChanger Adding host to active directory
24.4.2015 9:46 HostnameChanger Unknown return code: 1326
24.4.2015 9:46 HostnameChanger Windows activation disabled

[Tom Elliott]

Which password field did you set? Is this the new client or legacy?

[GregorS]

New client.

[Tom Elliott]

Then the pass field needs to be set in active directory defaults under the password field not labeled with legacy. You don’t put the encrypted password. You type the plaintext password and save. The field will automatically encrypt the pass word for you

[GregorS]

Ok. That solved the problem.
I had to disable [I]Join Domain after image task[/I] and clear all the fields in Host management AD section and re-enable Join Domain. After that host was automatically joined to AD and restarted.

Thank you very much for your help and keep up the good work.

[Wayne Workman]

[quote=“GregorS, post: 46135, member: 29372”]Ok. That solved the problem.
I had to disable [I]Join Domain after image task[/I] and clear all the fields in Host management AD section and re-enable Join Domain. After that host was automatically joined to AD and restarted.

Thank you very much for your help and keep up the good work.[/quote]

DO TELL us how the new client is treating you!

[Bill Rice]

Gotta say the support on this project is awesome! you can’t beat this program. and Thanks to all the hard work from all Developers especially Tom. man you have worked miracles resolving the issues i was experiencing. Got both legacy and new clients working/resolved issues with error 2 and error 1326. New OS installed and re-install FOG with all the new tricks and works like a charm now. now i can get the information about the clients and able to rename/re-join systems in the proper OU’s as well … adding multiple ou containers to the image process is going to be invaluable.

[Wayne Workman]

[url]http://fogproject.org/wiki/index.php/Support_FOG[/url]