Posts made by m144

Hello,

Fog Version = 1.5.5

Wondering if anyone else on 1.5.5 is seeing this or there is already a post about this I have missed?

When looking at a hosts image History the “Engineer” section reports all imaging history has been done by the current logged in user.

I have tested this by logging in as another user viewing the same host image history and receive the same results.

However, the actual user that imaged the computer is listed correctly under Report Managment> Imaging Log.

Thoughts?

Thanks,
M144

@plegrand

Hello,

If for some reason you do not get redirected you may already be joined to #fog, if not just type the below line into your irc client.

/join #fog

#fogimaging and #fogproject are both set to +i and redirect to #fog so all FOG users end up in one channel instead of 3.

Thanks,
M144

@dahrell I know the pain!

The same thing happened to me when trying to use that docking station for the Surface Pro. The thing I don’t understand is that docking station will work for me when imaging a Surface Book but not a Surface Pro.

I ended up just using this surface docking station and it works every time with the newest kernel… Even tho it says it is for the Surface Pro 3 it did work with our 4’s.

Good luck,
-M144

@wayne-workman Sounds good… I’ll see what I can do when I find some free time.

@george1421 @Wayne-Workman Thanks guys… Been using FOG since back in the 0.32 days! It has saved me so much time, words can not describe how much I appreciate this project.

I hope to create some more documentation as I have some time. Would love to help with anything I can, just let me know.

Thanks,

• 1 - Go to >Fog Configuration> Fog Settings>Plugin System - check the box for “PLUGINSYS ENABLED”

• 2 - In the menu, you should now see a gear icon called “Plugins”

• 3 - Once on the Plugins page select “LDAP” then navigate to “Install plugins” then install the LDAP plugin. You should now see the LDAP plugin listed under “Installed Plugins”

• 4 - SSH to your FOG server and install the latest php-ldap module through your distro package manager

• 5 - In the menu, you should now see a key icon called “LDAP Servers”

• 6 - Click “Create New LDAP”

• 7 - Now for the fun part…

LDAP Connection Name - (This is whatever you want it to be… it’s just a name)
LDAP Server Description - (Again… whatever you want… it’s just a Description)
LDAP Server Address - MANDATORY - (The name of the server to check logins against)
LDAP Server Port - MANDATORY - (Pick 389 or 636 from the drop down… if you are not sure what one will work for you start with 389 or Google it)
Use Group Matching - recommended - (you are most likely going to want to leave this checked)
Search Base DN - MANDATORY - (This is the organizational unit within Active directory that you would like to start your search for users)
Group Search DN - MANDATORY - (This is the organizational unit within Active directory that you would like to start your search for Group Matching)
Admin Group - MANDATORY - (This is the name of the security/distribution group that admins need to be a part of in AD in order to login with LDAP) Note: Just the group name… not the whole CN as you already provided that information above.
Mobile Group - recommended - (You probably just want to make this the same as above unless you use this for things… idk)
Initial Template - (Since this tutorial is for Microsoft AD lets select Microsoft AD)
User Name Attribute - MANDATORY - (Not sure if the case is important for this setting within in FOG, but for others I know it is… thus I changed the “User Name Attribute” from “samAccountName” to “sAMAccountName”)
Group Member Attribute - MANDATORY - (Default setting here is good - “member”)
Search Scope - (Depends on how your organizational units are set up within AD )
Bind DN - MANDATORY - (This is the full path to the location of the user account you will be using to talk with LDAP this should start with “cn=”)(This user should have somewhat elevated permissions in AD the level of which is at your discretion)
Bind Password - MANDATORY - (The password for the user account above)
Once done click “create”

• 8 - Read the “Some things to keep in mind section below - Then test logging into FOG with an AD account”

Some things to keep in mind:

• The LDAP user you want to log in with should not already have a local account within FOG.
• Once you get it working don’t just go and delete all your local FOG accounts… Leave one with a nice long and random password - keep that password somewhere safe, if the plugin stops working for some reason it would be nice to still have access to your FOG server GUI without having to go and add a user into the database manually.
• Please once working use a test AD account or create one and make sure you did not just give every user in your AD the ability to log into your FOG server and image every computer.
• The apache error log is a great tool to use when troubleshooting why your LDAP is not working on FOG
• Below is an example of LDAP settings within FOG
• As always if you are not sure about something feel free to ask the fourms… Thats what they are there for

Disclaimer: All of the above information is a summary of my experience getting this plugin to work within our environment. I am only providing an example/tutorial. Please be careful with LDAP and TEST USER ACCESS as much as you can. only you will be at fault if for some unfortunate reason someone that should not have access to your FOG server gets it and images all your computers

With that said, I hope I have stressed the importance of securing your LDAP setting and this example/tutorial has helped you in some way…

Happy Fogging!

@sebastian-roth Sorry for the late reply, Looks like it is “045e:07c6”

The first lsusb is with no doc the second lsusb is with doc.

@george1421 Attached is a picture of the current setup with a:

TP-Link TL-0SG1008D switch (Not the new model they have out rn, also the dumbest switch I could find in the office… works about 90% of the time now)
A Surface Book Dock (Model 1661)
A Surface Book 4 (Model 1703 according to the Surface UEFI about page)
The white cable coming into the TP-Link switch is the uplink from a Cisco Meraki MS-22 switch
The blue cable just goes from the TP-Link to the Surface Book dock.
Then Dock to Surface Book through Microsofts proprietary connector

As for: @george1421 said in UEFI booting with Surface book 4:

But at the same time I’m confused why the wireless adapter is being displayed, unless the wireless and ethernet adapter are one and the same.

I feel the same about this… Not sure why only the wireless adapter is being displayed! The only LAN connection that I know of is coming from the Surface Dock. Also, I have not seen anything saying that the surface has a passthrough NIC built into it like a lot of newer Lenovos have. So for some reason lspci -nn|grep net is not showing the NIC for the Surface Dock.

I think at this point we are going to purchase and test a few dumb switches along with this usb 3.0 gigabit ethernet adapter that “Supports Legacy PXE (eHCI and xHCI) & UEFI PXE” (we will see about that! :))

Anyways, Those new toys should be in some time next week… I will test things out and let you know what I come up with. Let me know if you have any other suggestions in the meantime.

Thanks for all the help

@george1421 Attached is the requested screenshots.

I repeated steps 4 & 5 a few times over and it was a 50/50 on getting an IP address. (is it just me or is that a bit odd?)

Note: This is through the dumb switch + spanning tree & auto-negotiation off. I could not find any EEE settings in the Cisco Meraki dashboard… I wish we had just normal Cisco switches!

(Image 1 No-IP addr)

(Image 2 Yes-IP addr)

(Image 3 Surface Book 4 Dock Model 1661)

@george1421 Its right after “Initializing random number generator…”

@george1421 I went ahead and updated to kernel Version: 4.12.3 and switched back to ipxe7156.efi.

I am still getting the same message (altho the keyboard works now)… I have tried the kernel parameter has_usb_nic=1 and adding an old, dumb, unmanaged switch that @Sebastian-Roth mentioned but NOT with the new kernel.

I will give it a go this morning and report back.

Hello,

I have been following a few posts on UEFI booting Surface books / Lenovo laptops…

I have successfully gotten a Surface book 4 to PXE boot and take an image, boot windows, etc using one of the ipxe.efi files that are in the FOG repository.

My current problem is it only gets past “Starting eth0 interface and waiting for the link to come up” about 10-20% of the time(This is only happening on UEFI devices) Is there a different .efi file somewhere that I should be using instead… is the ipxe.efi file even the problem?

Please let me know whatever needs testing… I will test whatever I can to the best of my ability. I have been using FOG since back in the 0.32 days. FOG has saved me so much time and I appreciate all that the FOG team does. We have many different devices I can test for you devs and would love to do whatever I can to get FOG & UEFI playing nicely with each other

Background Information:

FOG Server:
OS = Debian 9.1
FOG Version = 1.4.4
bzImage Version: 4.11.0
bzImage32 Version: 4.11.0

Surface Book 4:
Surface dock being used to PXE boot
Image is Win 10 Pro 64bit UEFI
Secure Boot = off

Network: (Note… I am not a network person, just systems)
Cisco Meraki everything
We have a separate DHCP scope setup just for FOG UEFI testing so we can change the Bootfile Name whenever without affecting others.

Not sure if I am forgetting anything? Please let me know if you have any suggestions or would like some testing done.

Thanks,

@avaryan I have not messed around with FOG Snapins that much at all… I guess now is a good time to start!

Thanks for all your help on this, much appreciated.

@avaryan WOW that was quick… Did you just make this!

So, I have a firstboot.bat that runs on the first autologin that does some stuff like delete the unattend.xml, start the fog service, etc.

I think I am just going to have my firstboot.bat file throw another .bat (secondboot.bat) into the startup folder for the administrator account. Who knows maybe we will find something we can add to the secondboot.bat that is useful.

Below is the list of the basic things we do excludes any extra stuff we are doing. Just want to list out how we are doing things in case anyone else wants a super basic process.

*Note: This is the code we use if “CopyProfile” in the unattend.xml is set to false and we are using the DefProf tool.

#win_10-generalize.bat

sc config "FOGService" start= disabled
net stop "FOGService"

cd C:\Tools\firstboot
copy firstboot-shortcut.lnk "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup"

#more stuff goes on here

cd C:\Windows\System32\Sysprep
sysprep /generalize /oobe /shutdown /unattend:c:\Windows\System32\Sysprep\unattend.xml

Upload to FOG server… Then send out to what ever.

#firstboot.bat

del C:\Windows\System32\Sysprep\*.xml

sc config "FOGService" start= auto
net start "FOGService"

#more stuff goes on here

cd C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup
del firstboot-shortcut.lnk

cd C:\Tools\secondboot
copy secondboot-Shortcut.lnk "C:\Users\Administrator\AppData\Roaming\Microsoft\Windows\Startup"

del C:\Tools\firstboot\*.bat

#at this point FOG reboots and joins the computer to the domain

# fix my auto log in twice problem

shutdown -r -t 60

cd C:\Users\Administrator\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup
del secondboot-shortcut.lnk

del C:\Tools\secondboot\*.bat

Probably not the best way to fix this whole logging into the administrator account twice for no reason problem… But it is a quick way to fix it lol.

@avaryan Thanks, That’s not a half bad idea… As of now, defprof is doing the job. The only problems I have left to fix on this windows 10 img is:

1. The fact that after Sysprep it auto logs into the pc as administrator twice but we only have it set to do so once in the unattend.xml (Not sure how I am going to fix this one!)

2. Chrome profile settings are not being copied over to the default profile. (Not that big of a problem can live with out it)

Other than that I should be able to push this out to a few computers today, give it a good test run before our first go around with a few hundred computers… to start with.

@x23piracy That’s what I ended up using… I used defprof back in the XP days. Happy to see that it is still around.

So… After a few days of messing with this, it turns out to be the CopyProfile = true bit in the unattend.xml that is messing with the desktop icons.

I set CopyProfile = false and just threw the links into default profile myself and now the links and everything else that was being odd work just fine. Other customizations like start menu etc are gone but I can work around that.

Has anyone else had any problems with CopyProfile = true in their unattend.xml? Its a shame to not be able to use that.

@x23piracy When I check the settings, yes it is still pointing to the correct ico location.

As for the icon cache… I have wiped it out a few times now(and before upload), I still end up with the white boxes every time.

Here are the settings on one of the shortcuts when opened with notepad.
[InternetShortcut]
URL=http://mail.google.com/
IconIndex=0
HotKey=0
IDList=
IconFile=C:\Tools\gmail.ico

@sudburr I will take a look at the permissions for the shortcut… Seems a bit odd, and have also never had to do that but at this point, I will try anything. (I will get back to you with the outcome)

@quazz We just got our win 10 licensing so we were going to start rolling out win 10(1703) this summer but we don’t want to push it out with this problem.

So I guess the answer to your question is yes. I am going to test it on win 10 pro(1703) today, I don’t expect anything different but can’t think of any solution rn. (I will post an update when done testing today)

Also fun fact, We do have one shortcut that is pushed out to everyone with GPO and the same thing happens to it on the win 10 img. The same GPO shortcut has been working on win 7 for years.