@bobsobol You are more than welcome to add to the wiki whatever you can. There is no one around the FOG team who knows everything (except maybe Tom! ) and it’s not necessary. I myself have learned so much by joining in and getting to know things step by step. @Wayne-Workman will add an account for you soon I am sure.
@msi Sorry maybe I wasn’t clear. Your batch file route can be saved as a .bat (but is probably better saved as a .cmd). You can deploy that as a snapin just as I had outlined.
The second part of my comment was to the reason why you are doing this. If you have to fix 100 computers that have already been deployed then the snap in route is the correct one. If you are doing this because you will deploy 100 computers in the future, then there may be another path you can take. One example is if you sysprep your reference image, then you can place batch commands in the c:\windows\setup\scripts directory. After windows setup is done, and before the login screen is presented to the user, windows setup looks in that path for a batch file called setupcomplete.cmd. If it finds that file it will run it before the user can login. There is also a way to have the windows unattend.xml file run commands or add users during its execution. Which can do the same things you are doing in your batch file.
These are all different ways to get the same results. The simplest is to create a batch file snapin like you talked about.
I’m having a problem where my Ubuntu desktop freezes and I restore it from a back up. When I do that it does not sync with my /images/ folder where all of my images are. I’ve created my own CSV file to upload into fog, however, I’m running into the problem of figuring out the size and server size, so what goes into column G and R. If someone can help me figure out those two pieces of information from the images I already have I would appreciate it. Thank you.
I’d say adjust the /opt/fog/.fogsettings file and let the fog installer handle configuring DHCP (It is solid, I’ve done a lot of work on that part of the installer). You’ll probably need to install dhcp-server before hand though.
I feel I must add the primary reason you won’t see a “central repository” for OS images lies down with the very simplistic case of licensing.
If there were a “central” repository, um, can you imagine the legal issues that would no doubt-ably ensue? Managing a repository itself would be extremely difficult, but licensing - especially in commercial OS’s - would be a nightmare.
Ultimately, while it would - from a purely technical standpoint - be possible to create a (very very very) generic set of OS’s that could be used by many, this would not come with your organizations set of software. (Admittedly vague in that you could automate some of the software layout with snapins.) This again is purely technical. Yes, it “could” be done. No, it most likely will not be done.
I could, however, understand central repo for OS’s that don’t require licensing (only one I can think of would be linux though) but even then you’re dealing with one person’s preferences for the layout of the OS vs. what might actually be required and/or more suitable to your environment.
OS-Images - generally available and upgradable with snapins (kinda) is the idea behind docker.com…
@jjcjr With your concerns then the remote site will need to have a stand alone storage node, just for the reason you cited. If the master node is unreachable then imaging isn’t possible.
What you are asking for is not currently available in fog (what I’ve been calling a multi master node setup. I’ve personally had a feature request in for this for over 2 years). The developers have just added a restful api interface that was on the roadmap to provide what you are asking. But its not there just yet.
With your current setup, you only need to export from the master node and import into the remote node when you have a new image definition. If you update an existing image definition, the new files will be replicated to the remote fog server and nothing else is needed. This is how I run my multi-master fog setup.