Posts made by need2

I’ll look about some more.

That should work, but definitely read the wiki article on how to upgrade.

No… I’m really not sure what is happening to you. Do you maybe have some sort of different firewall or weird AV that may be stripping out some of the FOG files?

If you’re wanting a newer OS that still runs smoothly and lacks bloat then I’ll toss in another shout out to using Debian 7.5 . But yes, with any system its best to get major OS work out of the way before trying to set up software that you want to be stable. Dependencies change, folder locations change, kernels change… it can be a mess for software to go through OS upgrades.

I’ll give that a shot. This may not be completely ideal but it should work. The main thing I am wanting to do is to assign the server name/ip so the fog service actually knows where to point.

I hope to have experiment results today.

Hello

I have tried hacking my way through creating an MST for the Fog Service MSI, but completely broke the install in the process. I would greatly appreciate either documentation on which areas of the MSI are safely modified, or have support added for creating an MST to accompany the MSI. This would allow for installation through an Active Directory or any other managed software solution that uses MSTs.

Easily go back and forth? Eh… well you should be able to start and stop the dhcp service in your Linux flavor of choice.

So you are saying that this does not work?
[url]http://msdn.microsoft.com/en-us/library/ff720058.aspx[/url]

You should be able to just copy the Images folder.

Unless you need to do a fresh install, I would also copy over the DB.

I would suggest a different firewall. I hate to be that guy but honestly you will need to either manage the Windows Firewall settings with a GPO or just use a centrally managed AV software.

I would follow the upgrade wiki article for the software its self, but yes, I would upgrade the central server first, then each ‘storage node’ server. It shouldn’t really impact anything, but best to have the controller knowing of the new features before the nodes.

In 1.0.1 Fog requires a Host to have an image associated in order to perform a WOL task.

What specifically is not there?

Are you accessing the fog UI from the same subnet as the server?

The only way they could have had Fog working on a UEFI system with the UEFI stack would be if they did some intensive customization and replaced a lot of the kernel and boot structure of the Fog network boot. The other option is if there was some odd mix of UEFI and legacy boot set up, at which point you need to go back into the BIOS and re-specify the UEFI Windows Boot Loader after deploying an image.

How are you getting the Fog server to support UEFI boot?

You can just sudo ./installfog.sh just fine. It keeps settings automatically, and just upgrades your installation. I’ve never had a problem that was Fog’s fault with this.

[IMG]https://dl.dropboxusercontent.com/u/7798420/threadnecromancerji6.jpg[/IMG]

Perhaps I miscommunicated a bit. Typically an MSI is deployed through a domain rather than an EXE. This allows the domain to control what is done with the installer a bit more, including the use of an MST. The MST is a transform file that feeds the MSI commands and/or fills in options that the MSI usually contains. By default all domain managed MSI installs are silent, so in addition to not wanting to rely on the end user to know what buttons to push on an installer, an MST is necessary for anything other than a completely default install. I COULD replace the .ini files, but I would have to do this with another script, and I don’t know of a way to do this that is smart enough to run once per install, but also run again later if the install is marked as damaged or is somehow removed.

I’ve dug into the MSI a bit, and I have found a section under _Validation where I can modify a Table AppID with Column RemoteServerName. I will do some testing and report back.

I’ve seen some manufacturers use weird practices such as intentionally broken partition information to lock down their recovery partitions. I’ve never been a fan of this, and it becomes quite a pain when a rootkit finds its way in there and you can’t. If you have installation media for your OS, and have the keys you use recorded somewhere, then you really are safe to nuke those partitions. All they do for you is what Fog can do better.