Posts made by george1421

@sgwk So do you have success or no joy after you made the change?

@matthieu-jacquart Ah ok, now I understand.

Just be aware the developers are taking a short holiday for the rest of the month. So their response will be a bit slower. Just be aware so you can adjust your schedule.

@matthieu-jacquart Has there been any movement on HP’s part to update the uefi firmware on this hardware?

Is there a compatibility issue with the kernel your have vs the current release of FOG? Or is it just old and you want it updated? I’m just trying to understand the context.

@wayne-workman Yeah, I was trying to address an issue I was seeing the wrong way. It would be much cleaner to just do a split horizon dns to address the issue.

@george1421 This may be a question for the @Developers Is there a way to change the port used by the clients to connect to the fog server. Lets say we would want to use a non-standard port for client to fog server communications. Is that possible?

@bob-henderson With that many hosts at the remote locations why not add a local fog server for snapin management? That would avoid having each client reach out to the master fog server at HQ for tasks?

Oh and one thing i missed, was how many locations are you talking about?

Is this for some type of MSP business model?

@bob-henderson How may systems at each remote location(s) are you talking about?
I’m not sure I would want to expose the FOG server directly to the internet without some kind of access controls. Possibly using a reverse proxy with a screening router to help.

These are just some incoherent questions (ramblings) I have:

1. I think we need to consider what protocols are involved here. The client check into the fog server. That is done via http(s). Is http also used to transfer the snapin to the remote system?
2. What happens if the client is connected via a slow Internet connection? Are there timeouts involved here?
3. Is there a way that a reverse proxy running at the remote sites (nginx + raspberry Pi + openvpn) could be utilized to provide a secure channel back to HQ?
4. Depending on the client density at the remote sites, would/could a FOG-Pi or FOG-NUC server running as a storage node be practical for snapin deployments? (this would also give you a footprint for Chocolaty or FusionInventory at the remote locations)
5. How would you manage IP address range eclipses/duplications?

@doubleailes [Moderator note] Please start your own thread because this thread is over 8 months old and I’m sure your computing environment is not the same as the OP of this thread. In your thread, please include what version of FOG you are using on both the master node and storage node as well as what OS is used on the master node and storage node(s)

@msi Once you have the fog dhcp server disabled and the service stopped, then you can use your cisco dhcp server, no problem. You will need to configure it to send dhcp option 66 {next-server} which is the IP address of your fog server. And then configure dhcp option 67 {boot-file} to either undionly.kpxe for bios (legacy) systems or ipxe.efi for uefi based systems. If you have a mixed environment (uefi and bios) systems then you will need to configure the cisco dhcp server to send the correct {boot-file} based on the pxe booting client. This is done by the dhcp server watching the Arch type that is sent in the dhcp discover packet.

If your dhcp server isn’t capable of dynamically sending the right pxe boot-file, then you still have some luck, you can install dnsmasq on the fog server and have it supply only the {next-server} and {boot-file} dhcp options for the pxe booting clients. The main dhcp server is still responsible for IP address assignments and the fog server is responsible for sending the pxe information.

@m-fitzgerald If you capture from your reference image (swap the hard drive with a blank one) and deploy back to the same hardware does it boot correctly?

Now when you deploy to these 52 other systems, if you are using single disk non-resizable the target computers must have a hard drive the same or larger than the source disk. If you use single disk resizable, the target must have a hard drive larger than the data size on the disk.

In my company I deploy a single image to 15 different models. So I know the process works correctly.

@m-fitzgerald Ok so the focus is deploying Win7 OEM to these 53 systems (if we close one eye and squint with the other we can bypass the OEM EULA). But for the sake of argument lets talk totally technical here.

Now on these 53 systems, I assume you took one of them and installed Win7 OEM on it right? It loads correctly and boots fine. Now for the other 52 systems. Are they all the same make and model? If not, did you load all of the possible drivers needed for the 53 systems into your reference image? Is the bios settings configured similarly? And maybe a more proper question would be, are they all configured for uefi or bios mode? The boot loop is not common.

@m-fitzgerald If I understand the upgrade process, once your system has been upgraded then activated with win10, you can install win10 directly without going through the upgrade process each time. The MS clearing house should have your system’s activation on file already.

I remember when win10 first came out there were bugs in the upgrade process from win7 so people would go through the upgrade then wipe the system and load win10 on it clean. It should activate no problem. You should be able to test this with just one system. Load it clean from a cd/dvd.

@espynn said in Computers slow to a crawl after domain join:

There isn’t a GPO template for “make imaged computers run slowly"

This is my thought too. Instead of turbo mode, you found snail mode.

If you have the capabilities, move that computer to an OU where you are blocking all GPO policies. So the computer will be connected to AD, but no gpo policies will be applied.

It could be something silly like if you had AV installed in the golden image and when connected to AD its trying to do something and timing out causing the delay. AV is typically installed post imaging because (depending on the AV solution) a guid is created which needs to be system unique.

It would be also interesting to know if the slowness is observed when disconnected from the network.

SCCM is a good solution if you can support the infrastructure requirements. It is more than just imaging so not really in the same class as fog.

@espynn So if you disconnect the computer from the domain, does it return to normal?

If you never connect the computer to the domain does it remain normal?

If while on the domain and running slow, what happens if you disconnect the computer from the network?

I’ve failing to see a connection between imaging, connecting to the domain and the slowness you are seeing. There has to be something going on here that is unseen now.

Was the original (master) image ever connected to the domain?

Before you captured the image, did you run sysprep and have sysprep power off the computer?

This doesn’t sound like a FOG problem, but more of a windows problem. I can tell you I use fog to image win10 systems quite a bit. I haven’t run across this issue before. But I use MDT to build my golden image, capture and deploy with FOG. I let the unattend.xml file connect the target computer to AD, so I too don’t use the fog service much for imaging.

@herb said in FOG, what can and can't it do?:

Q2: Can Images be deployed that I did not capture?

The short answer is No. You must capture the image from FOG to deploy it.

There is no central repository for OS images. You must create your own, based on your own requirements from DVD. In my company’s case we use MDT to build our golden image then capture and deploy with FOG. A hardware agnostic design is surely possible. We have a single image that we deploy to 15 different models in our fleet of computers. The key/trick is to use a FOG post install script to copy the correct drivers to a defined location on the target computer just after deployment, but before the first OS boot. Once the drivers are at the precise location then windows will detect them and load them. Sometimes we find that we need to use dism in the the setupcomplete.cmd to finish injecting the drivers after oobe but before first login. It does take time to setup your environment but once done you can regenerate your golden image at any time with the latest windows updates if you use MDT.

@merilious Do you already have a fogproject directory? If you are on an RC release I might say yes.

It might be in /root/fogproject or /opt/fogproject depending on who’s instructions you followed. If you can find that fogproject directory, then the update process is simple.

cd /root/fogproject
git pull
git checkout master
cd bin
./installfog.sh

You will need to do a checkout master because you were on a rc branch.

@merilious OK I just wanted to make sure that the password was blank. Then the instructions in the thread are spot on. Go ahead and follow the steps. Then you probably should update to current 1.4.0 had several issues with single disk resizable that was fixed in 1.4.1. But for now you need to get control of your fog server.

@merilious I want you to open a linux command prompt and review the settings in /opt/fog/.fogsettings especially the field snmysqlpass what is the value currently?

@merilious Since it WAS working and magically, IS NOT working AND you are running ubuntu this thread probably applies: https://forums.fogproject.org/topic/10006/ubuntu-is-fog-s-enemy

But before you go and follow this thread blindly lets get some background information.