@ty900000 Sorry, forgot to update this topic as well. We have added a fix. Please update to the latest dev-branch and it should be all good to go again,

@Sebastian-Roth

Yes, sir! My apologies for not doing this sooner.

https://forums.fogproject.org/topic/14116/development-fog-not-capturing-image-partclone-update

@Daniel-Miller said in LDAP Bind during Login:

Now, if you happen to know what the DN suffix will be, an alternative to the search and bind method would be a direct bind where the required static information is added to the username to create the DN that is proffered to LDAP for the bind request.

Right, this is something like I was thinking about, especially on a domain-joined machine. I suppose I didn’t phrase it properly or concisely - that’s my bad.

No particular reason for this functionality; just didn’t know if it would be something worth adding in or how difficult it would be to code into the plugin. No worries!

Thanks for the quick reply!

I figured it out - I forgot you cannot try to take a new image over an existing image. We already had taken an image with the exact same folder name and when FOS tried to move the files, it failed. When I deleted the old folder, the image capture worked perfectly. My bad!

While I don’t use IE, can you white list the FOG URL in your IE pop-up blocker? I would think there should be a way to allow pop-ups from specific web sites since many responsive web sites use these type of pop-ups.

@tiagoluz

Yes, you can manually rsync the images over. I’m doing the replication between nodes so my coworkers who know nothing of Linux can synchronize images across FOG installations without asking me to do it.

@junkhacker While we removed the settable feature from FOG, the database still relies on it I believe.

If anything there is still a hook that could be tied into to “authorize” against.

USER_TYPE_HOOK and USER_TYPE_VALID are the events to go against. This was part the reason why I went ahead with it, because there are ways around it anyway.

USER_TYPE_HOOK is typically used for just checking and changing the type, as in the case of LDAP users vs. normal fog gui users.

USER_TYPE_VALID is the simplest one with would allow you to hook against whether the user is valid for that particular are or not.

I just wanted to post to close this out.

I got a test environment working with better switches and FOG was able to pass 64-bit UEFI traffic correctly the first time, every time. Thanks all for the big help! I really appreciate it!

@george1421

I added a Cisco switch in the mix, but I couldn’t get it to pass any traffic, even from the switch itself. I don’t know if adding a layer 3 switch into the mix confused everything?

Anyway, I’ll wait until we get new equipment and then debug it from there, like you suggested. We’re going to be reimaging multiple machines at a time before we get new network equipment anyway, so I most likely need to get a RAID 10 set up.

Once we get new equipment in, I’ll give the Multicast a shot and then reply back to this thread. But, that’s way in the future. Probably several months or more.

I appreciate all the help you guys have put in to this! Thanks a bunch!

Sweet! That’s all I needed. Thanks for the info and the quick response!

10-4. Thanks for the info, the link, and the quick response! I’ll mark this as solved. Thanks again!