Inherited entire IT environment as dept of 1. Never heard of FOG but place has one running live. Have questions/need help please.



  • FOG server living on a Win Server 2016 host as a Hyper-V VM
    VM is running Ubuntu 16.04.2
    FOG is on version 1.4.4

    As I’ve been observing and wrapping my head around the environment I’ve been having some weird issues crop up in ways where I eventually had to blame the back-end instead of the end-users. After glancing at the FOG server on a surface level and seeing what it’s purpose was I’m assuming its the cause of issues. Bumped it up the priority list of things I need to get under control…Where should I start learning this application? What would be the best plan of attack to start reverse engineering it?? Seems like it can be a very powerful tool so would like to learn…and…if anybody is able to vouch on some of these problems too that would be 10/10 help.

    1. NIC drivers breaking to the point where it must have been done so w/ admin privilege even though these users don’t have admin…and consistently every morning then they boot up its broken again as if being reverted…?

    2. AD naming convention here sucks. Want to change it. Names keep reverting back sometimes, but sometimes they don’t?

    3. Can’t iPXE boot from the HP 620 laptops to it to upgrade to Win 10. Hangs on ‘initiating devices’ on network boot. (This was the final straw for me and tes these laptops are garbage buuuut this place is in ruins haha)

    Any advice or info would be appreciated! Thanks everybody!


  • Moderator

    @TammyTinkleToes90

    1. It’s possible the previous admin scheduled a daily image deployment that contains a broken NIC driver. (check scheduled tasks)
      The second possibility is a snapin that is done every day. (check snapins)

    2. Check fog client hostname settings

    3. Some devices have somewhat buggy UEFI firmware, especially with network boot. BIOS update might help.



  • @Sebastian-Roth said in Inherited entire IT environment as dept of 1. Never heard of FOG but place has one running live. Have questions/need help please.:
    @TammyTinkleToes90 Welcome to the forums. Sounds like there are many things o your list even within the FOG sub topic. So I am wondering where to start as neither you nor we do know your environment.

    NIC drivers breaking to the point where it must have been done so w/ admin privilege even though these users don’t have admin…and consistently every morning then they boot up its broken again as if being reverted…?

    Can you be more specific on why you think this is happening? The best way is you take a picture of the issue as you see it on screen and post here. Most often this is helping a lot more than explaining things in many words!

    @Sebastian-Roth I’ll see if I can grab logs out of event viewer or something. 3 mornings in a row user turns PC on(Win 10), looks at the bottom right corner before even logging in, sees the Red X over the NIC, calls. I go over there, check device manager, the NIC has a yellow triangle on it again. Uninstall, let Windows reinstall, see you tomorrow morning…Was wondering if FOG had capabilities kind of like Deep Freeze.

    AD naming convention here sucks. Want to change it. Names keep reverting back sometimes, but sometimes they don’t?

    FOG can do host renaming if the fog-client software is installed. One way to get around this would be to uninstall the software from the host and manually rename it. But way easier you’d just rename the host in the FOG web UI and let the fog-client software do the rename for you. Are you aware of FOG having a web UI? Do you know FOG server IP address and login credentials? As you know it’s running in a Hyper-V, you are probably able to login to that machine on the console, right?

    Yes, I’ve logged into the GUI. Just haven’t had time to deep dive. Have experience with Kace k1000/k2000 though. The FOG client is on every machine. Thinking about it now I bet if I rip it off those machines those anomalies will go away too. The old IT guy seemed to use the methodology of ‘If you just barricade the front door who cares if you just let the rest of the house deteriorate and look like garbage’…

    Can’t iPXE boot from the HP 620 laptops to it to upgrade to Win 10. Hangs on ‘initiating devices’ on network boot.

    Probably something specific with this particular model. I myself would put that point way down the priority list. As a quick fix you can just enter BIOS settings and set it to boot from hard drive first instead of network/PXE. That way you should be able to do what you want.

    Wanted to upgrade these to Windows 10 from 7. Last IT person probably had same issue which is why they are basically the only machines left on 7. Will just end up using Redo Backup/Recovery as a last resort.


  • Senior Developer

    @TammyTinkleToes90 Welcome to the forums. Sounds like there are many things o your list even within the FOG sub topic. So I am wondering where to start as neither you nor we do know your environment.

    NIC drivers breaking to the point where it must have been done so w/ admin privilege even though these users don’t have admin…and consistently every morning then they boot up its broken again as if being reverted…?

    Can you be more specific on why you think this is happening? The best way is you take a picture of the issue as you see it on screen and post here. Most often this is helping a lot more than explaining things in many words!

    AD naming convention here sucks. Want to change it. Names keep reverting back sometimes, but sometimes they don’t?

    FOG can do host renaming if the fog-client software is installed. One way to get around this would be to uninstall the software from the host and manually rename it. But way easier you’d just rename the host in the FOG web UI and let the fog-client software do the rename for you. Are you aware of FOG having a web UI? Do you know FOG server IP address and login credentials? As you know it’s running in a Hyper-V, you are probably able to login to that machine on the console, right?

    Can’t iPXE boot from the HP 620 laptops to it to upgrade to Win 10. Hangs on ‘initiating devices’ on network boot.

    Probably something specific with this particular model. I myself would put that point way down the priority list. As a quick fix you can just enter BIOS settings and set it to boot from hard drive first instead of network/PXE. That way you should be able to do what you want.


Log in to reply
 

385
Online

7.4k
Users

14.5k
Topics

136.8k
Posts