It was adding the * that helped get these going, thanks Deastrom!

I get it. It’s just that there are some new features in Fog that many of us can’t use because they don’t have that stamp of approval.

[quote=“George Stewart, post: 47485, member: 29650”]Thank you for the responses.

I am using the location plugin, but I have only one location. I’ve named this “main”. I have a dedicated 10 gig connection between my sites ( fiber ). One site can see the fog menu, register a device but fails (just reboots) once the image starts to pull down. My other site can’t boot to the fog system at all. I’ve ruled out the patch cables or switches being a problem as they are the same at all of my locations (gigabit switches). Should I setup additional locations at these other two sites and push the location\replicate the images down to these other sites? Just don’t want to go that route if my dedicated fog server here at the main location can handle this for me already.[/quote]

You only have one PHYSICAL location, but do you have V-Lans, or seperate broadcast domains configured? Is your location sub-netted?

The location plugin only needs to be used if you have logically separated networks segments.

If everything in your organization is all in one nice-simple network and on the same broadcast domain, you can just configure storage nodes if you like, or just have 1 FOG server, and nothing more.

We managed to fix this. We had to go into the FOGClient config.ini which is located in the etc folder of the FOGClient installation folder. We had to change forcerestart under the taskreboot from 0 to 1. That’s all. If anyone has wiki access to change the Client setup page, please be sure to include this.

The new clients will need to reboot to cycle their encryption keys, but other than that should shouldn’t be an issue.

[quote=“Julianh, post: 47352, member: 24986”]Thank you Tom, I’ve been imaging 2008 & 2012 servers, using windows 7 as the OS. I was a bit puzzeled as to why it was working! All installs should be MBR.

Is there a way of taking a raw image of the BCD data?

The OS I’m Imaging is, not windows, and am prepared to “pay” in storage such that, I take an image of the server, then send that same image down to the same machine. I’ll repeat that for each server. I know it’ll be heavy on the storage. Some of the OS partitions are fat16, so I want to use the features of fog for,these partitions, rather than use a “raw” image

Thanks for your help

Yours

Julian[/quote]
OS “other” and non-resizable is what you’re looking for, by the sound of it.
out of curiosity, what OS is it?
fyi: fog has built in detection and support for ext 2, 3, and 4, ntfs, fat, hfsplus, and uses raw for what it can’t detect. so, you’ll probably find that the image takes up less space then you think.

Thanks, I will test this out incase this issue comes up again. My colleague was able to get a license from a reseller of the old application.

[quote=“Trevelyan, post: 47309, member: 7471”]Is it just avoiding possible data corruption, or certain data corruption? I haven’t seen any ill effects of not changing, to be honest. I’ll keep going without changing it but keep it in mind anyway. Thanks for explaining it! :)[/quote]

potential.

If the syntax is similar to yum, we could make a temporary alias to change out yum to dnf. I don’t imagine the installation of packages would change too much.

I’ve never used the reporting functionality in FOG…

I’d personally just fire up an SQL client, connect to FOG, do the query for the data I want, dump that into a Google Doc, and format it up nice and pretty.

Also, are you able to boot to a recovery partition by pressing F8? If so, Windows 8 has some recovery tools in there for startup issues.

I still have alot of testing and configuration to do but as soon as my documentation is done I will post it here. I am having issues with NIC bonding right now, it works great on the FOG servers, CentOS 6.6, but I applied the same settings to the Red Hat 6.6 servers and the connection keeps dropping. The fun of IT!!

Actually it would still be allowed because fog does not install software or printers as the logged in user. It installs using the system user which is essentially the root user of system level activities allowing printers and software to be installed but maintaining user level permissions.

We put it on our images too. But if you choose Fog printer management to Add/Delete it deletes the Smart Printer. I either need to know how to push it out or how to keep from from deleting it.

[quote=“Wayne Workman, post: 46752, member: 28155”]Also, if you used user-based enumeration shares (windows server 12 and up), you can specify encryption of the redirected user data on the server itself, and have the user files NOT EVEN EXIST on the local machines. That’s how my environment is set up. It’s done through GPOs.[/quote]

That too is how we have ours set up. I really, really love not worrying about someone’s files when a drive dies anymore.

[quote=“Wayne Workman, post: 46660, member: 28155”]Does FOG use FTP to delete images?[/quote]

yes

It shouldn’t be too hard to have a method to chain to WDS. Its just a matter of triggering the right file. It does matter what version of Windows Server you are running. When I get to that part, I will be making a connection to a Windows Server 2012. The same methods should also work on 2008r2 and 2012r2.

Any/all results and documentation on my UEFI/BIOS coexistence will be going into a new thread. Since that will use DnsMasq it will be off topic for this thread.

Ok i see. Thank you 🙂

I’m game to hear what you’ve implemented. Message sent…

I need to remove some categories and rename some categories to match my needs. I expect that i have to change a lot of files.