Thanks Tom.
3557 works like a charm. My Fog server is back up and running.

I’m updated to 4367 now.

I thought that something was wrong because after imaging my computers, a specific group of them did not join the domain. I checked the log file on several of them and found an active directory error 8557. Google tells me this means the account reached its max number of computer joins to the domain. This prompted me to create a dedicated account that would not have this limitation.
So then I created the dedicated computer-joining account. I went into every one of the group AD settings (I have seven groups at present), and updated the user name and both password fields in all of them. I restarted the Fog service on all of these computers and received the same AD error 8557 on all, but one (which joined the domain) in the problem group of computers. I went back to the group AD settings to make sure I didn’t miss anything. They looked right, so I checked the AD settings for the individual computers. All but one still had the old user name and password that wouldn’t join any more computers to the domain.

I should’ve wrote this before sleeping on it, but I think I’ve got all the details in there. They might even be mostly in order. HA!

Also, I was changing AD settings **after ** the computers were imaged. Should the Fog service recognize that change and attempt to join them?

Matt.

Guys,
I noticed something after updating to SVN 4337 yesterday.

When I changed the AD details for a group of computers, it did not propagate to the individuals in the group.
I was having trouble with joining computers to the domain (self inflicted problem), so I created a dedicated user for the task. I changed the user name and password, in the default AD settings and also in the group, but noticed that my newly imaged machines were not joining the domain automatically.

Is this a bug, or did I miss a step?

I’m in the process of updating a few of them manually to see if they will join the domain.

Matt.

Thanks Tom.
3557 works like a charm. My Fog server is back up and running.

Should I give 3557 a shot? Thoughts?

@Tom-Elliott Nope, no proxy here.

Done.
I got exactly the same result.

It just sits there.

 wget http://127.0.0.1/fog/service/getclient.php
--2015-06-12 15:12:13--  http://127.0.0.1/fog/service/getclient.php
Connecting to 127.0.0.1:80... connected.
HTTP request sent, awaiting response... 

What’s the url for the client download?
I can try a manual wget and see what happens.

Oh I see.

Ubuntu Server 12.04.2 LTS

@cspence said:

Well, at least it didn’t hang.

@Matt-Rozema: What distribution and version are you running? I think whatever you are using is using an older wget…

Yeah, I’m glad it didn’t hang too.
I’m at revision 3543.