I uninstalled the legacy client

@ITSolutions I Have Upgraded to 7116 checked and double checked and changed the AD data and it still is not working.

@ITSolutions I have re entered all relevant data and double checked for spelling. I will update fog in a little bit.

I am on Win7 32b Pro.

@ITSolutions I was using the old client with the 1326 error the new client is giving the code = 100.
I have tried three different AD accounts, all of which will add hosts manually.
I have tried different OU settings as well.
Thank you for your suggestions.

I am running Fog Trunk 6677 on Ubuntu 14.??(sorry i can’t recall what release)

I just updated the client to the most recent release from the server and when it gets to the part to join the domain this is what the log says:

4/8/2016 11:50 AM Middleware::Communication Response: Success
4/8/2016 11:50 AM HostnameChanger Checking Hostname
4/8/2016 11:50 AM HostnameChanger Hostname is correct
4/8/2016 11:50 AM HostnameChanger Registering host with active directory
4/8/2016 11:50 AM HostnameChanger The system cannot open the specified object, code = 110

Previously i got a different error (1326)

Joining Active Directory has never worked for us and I’m trying to figure out why.
Thanks for any and all assistance

0_1460135941986_fog.log

SOLVED! Here is what worked for me:

Original Problem: I am updating FOG 1.1.1 to 1.2.0 and when it got to the part of the installation where the installer

Setting up and Installing Apache Web Server... failed 

I fixed this by updateing Ubuntu to 12.04 and running:

apt-get install libapache2-mod-php5

That got me past the Apache initialization.

The next issue I had was the Database Schema Installer failed and threw HUNDREDS of errors at me. this was fixed by reseting the mySQL password. I found instructions to do so here: http://www.rackspace.com/knowledge_center/article/mysql-resetting-a-lost-mysql-root-password

@Wayne-Workman

Okay I got it started using

apt-get install libapache2-mod-php5 

I got past that part and went to the fog management part and got about a thousand errors.

but hey one step close right?

Mod edited to use code box (click edit to see how I did it).

@Wayne-Workman

That’s good to hear! Thank you for your assistance.
I’ve looked up “Setting up and Starting Apache Web server…failed” and a suggestion i found was to “/etc/init.d/apache2 restart”

Which I did and it returned that it could not find “libphp5.so” so i am looking into that now.

@Wayne-Workman

I tried and that did what it was supposed to do successfully, however, when the install gets to

“Setting up and Starting Apache Web server…failed” it tells me where the log is and kills it.

Please tell me I didn’t kill our imaging system haha

@Wayne-Workman
I upgraded to 12.04 and reran the upgrade and still am having the same issues

@Wayne-Workman

Doing this now thank you!

I am trying to upgrade from 1.1.1 to 1.2.0 and everytime the process gets to the Apache Web Server set up it fails and stops the upgrade. We are running Ubuntu 10.XX.

Is there a way around this or am I doing something wrong?
Thank you for your assistance

@Wayne-Workman

Thank you for the response! They are the same models and same image all over unicast. It works on some of them. For example, we have a lab with 20 PCs it works on 18/20 of them but on two of them it goes into the Error Recovery loop. So, it is working on MOST of the 4000s but some it is not.

We are upgrading our current inferstructure so we will look into upgrading the fog server as well. I assume it is pretty simple and straightforward? I haven’t researched it at all but will do so when I get some time today!

Thank you for your assistance!

@Wayne-Workman

We are running 1.1.1
Deploying 32-bit Windows 7 Professional
HP 4000 Pro Small form factor
MBR i beleive, BIOS

And we have an image dedicated to each machine

In preparation for the upcoming school year we have been reimaging all of our lab machines. Some of the machines accept the image just fine and there are no issues. However, there are a few random ones that go to windows error recovery and there is nothing we can do to keep it out.

Is this an error with that particular machines hardware or is it a problem with the fog server? Does anyone have any ideas? Thank you.