I am looking to gather some information on deploying a chrome extension file via batch script, or VBS.

I know I can use an ADM/ADMx to push extensions, but unfortunately we don’t roll out Active Directory until this summer.

My content provider has decided not to fix an extremely frustrating issue with Firefox where it does not load course material, so now I have to use Chrome, no complaints here, except it’s harder than hell to limit chrome instances and tabs.

Currently, I limit FireFox to only opening one instance, and limit tabs to 3 open tabs at a time. I need to do this because my students have figured out that if they open Internet Explorer and log in to the content, then they can log into Firefox/Chrome and load the test and use the lesson material to answer the test questions… smart little buggers I’ll give em that. So I removed the internet explorer from the machine, installed a lock down browser in place of IE and chose to roll out Firefox. The only reason this works is because they can’t flip tabs when the test it open but they can alt tab to the other browser. Well They could

Well now I need to fix an issue like last week, since gradpoint has no recommendation on fixing the issues with course content in Firefox.

So… does any one have documentation or experience in deploying chrome extensions to an entire lab at once?

I plan to spend my Friday night in the lab installing chrome and locking it to kiosk mode and a tab limiting extension, if I could use a batch script to install the extensions, half of my battle is already over.

This only opens the chrome web store and waits for the user to click the install button and the prompts that follow
[code]“C:\Users\UserNameGoesHere\AppData\Local\Google\Chrome\Application\chrome.exe” “url to extension” [/code]

I even tried installing by crx file

I also tried copying my Preferences file, but then chrome complains that the preferences file has been changed and wants to “fix” the issue and in doing so resets all my settings, counter productive. -.-

Did you set options 66 and 67 as instructed to do so by the installer?

option 66 (next-server) should be set at your dhcp scope as the fog server.
option 67 (bootfile) should be undionly.kpxe so that when machines are looking to pxe boot they can find your file and server.

As ch3i stated, please include your FOG Version number, there may be an issue with a revision and we can to resolve the issue.
Your OS is important too as different OS house the files in different areas.

If you are unable to change/set option 66 and 67, I would recommend using a proxy dhcp service to issue information to machines looking to pxe boot. [url]http://fogproject.org/wiki/index.php/Using_FOG_with_an_unmodifiable_DHCP_server/_Using_FOG_with_no_DHCP_server#DNSMASQ_settings_for_iPXE[/url]

The older files are still available on the Sourceforge page.

[url]http://sourceforge.net/projects/freeghost/files/FOG/fog_1.0.0/[/url]

There’s a link to 1.0.0, you can download the zip file and pull the ipxe files out of the packages\tftp\ folder, but I don’t think ipxe was included in 1.0.0 you will need to check the other versions, i know that 1.1.0 had ipxe files in the packages\tftp folder.

However, if you are looking for the undionly.kpxe file, it can be found in fog version 1.0.0 in packages\tftp

I assumed you were looking for ipxe.kpxe or some variant, please offer more information on the file you are looking for so we can help you to acquire it.

bzImage files can be found in packages\web\service\ipxe\

you just have to dig a little deeper.

[quote=“Glenn Wilson, post: 40626, member: 240”]Do any services need to be restarted after changing the ltsp.conf file?[/quote]

Yes you need to restart dnsmasq

[code]sudo service dnsmasq restart[/code]

[quote=“ch3i, post: 40595, member: 2513”]Hi,

Never test with LTS but i’ll test later

Regards,
Ch3i.[/quote]

LTS is the Preferred method when installing a linux OS. Its Long Time Support (woot!)

Ubuntu 12.04 is still on the LTS list

I only recommend a stable release if there is a fix that is needed, or they really bork the LTS.

Sometimes we developers don’t build in fixes in for stable releases at least not right out of the gate. It is NEVER recommended to use a recent release with FOG, unless you like troubleshooting and documenting and want a “fun” (I use this term loosely) experience in learning FOG all over again! We never know what is broken but then, sometimes canonical fixes it for us, not often enough though (such as with the upstart bug) Or the problems that are caused by using DNSMASQ-base by default for the network manager… sigh gone are the old days of the 10.04.

LTS would be a fine choice for FOG

The only issue FOG had with some versions of Ubuntu, was an upstart bug OF UBUNTU, that they really took some time to fix, then bring back, and fix, and bring back again. It’s hard to say what is going to be broken again because Ubuntu isn’t exactly following the Debian mold any more.

I would look into a pure Debian LTS.

What version of FOG and OS is installed for the FOG server?

[quote=“Ricardo Sanches, post: 40277, member: 25923”]Ok so I asked to change the bootfile to undionly.kpxe and it and passes that step and it goes to [FONT=arial][COLOR=#545454][SIZE=3]“iPXE [/SIZE][/COLOR][/FONT][FONT=arial][COLOR=#545454][B][SIZE=3]initializing devices” and the Pc just reboots without showing any menu. Now what am I doing wrong???[/SIZE][/B][/COLOR][/FONT][/quote]

I solved my PXE-T01 issues by using DNSMASQ

[url]http://fogproject.org/wiki/index.php/Using_FOG_with_an_unmodifiable_DHCP_server/_Using_FOG_with_no_DHCP_server#DNSMASQ_settings_for_iPXE[/url]

Personally, I would build a new server and set up from scratch.

Somethings to note.

In the newer versions of FOG we use a different boot file (undionly.kpxe) instead of pxelinux.0, you will need to make adjustments to your scope when you deploy a newer FOG server.

I know that FOG will upgrade form 0.32 to 1.2.0 without much of an issue, but I prefer to keep my old server alive someplace incase I hit a snag and need it.

The only advantage you would have on upgrading your current set up to 1.2.0, would be keeping your old images, and your old database.

If I were you, I’d grab a fresh debian download and set up a whole new FOG server

Hope this helps!

There aren’t standards in PXE for Wifi that make this feasible. I know apple offers some “wireless netboot” capabilities, but that won’t help you.

Even if it was possible, I question the performance, reliability, and efficiency of using this method. I don’t see how this would offer any significant advantages over wired connections.

I know you said that your nics are bad, in which case I would look into a usb option.

It would take a significant amount of time to image this way, it would probably be unreliable, and it would ruin the performance of the wireless network for everybody else at the same time.

I know it’s not the answer you’re looking for, but I felt is necessary to explain that it’s not FOG’s fault you can’t image wirelessly, its the PXE standards.

NOW iPXE is a whole different animal. It supports the capability… but… see my statements above.

We have started to work in some iPXE into FOG and we are ironing out the bugs, but I don’t really see the benefit to imaging wirelessly as I stated above.

We (the development team) are having enough trouble trying to serve all the possibilities of NIC there are, We’ve had to create multiple bootfiles just to serve some variants of NIC, and until we can get those issues resolved, I don’t see this being added to the plate anytime soon.

Now don’t let that deter you. FOG is opensource and you are welcome to tweak till your eyes bleed, and in doing so you may even create a document explaining the process, others may also benefit.

Most of the elements should be there, I know we are serving NFS, HTTP, HTTPS, iSCS, DNS, TFTP, AoE, VLAN, SRP, bzImage, MBOOT, ELF, PXE, XEXT

Just look at [url]http://www.fogproject.org/wiki/index.php/IPXE#What_is_iPXE.3F[/url]

The page above also states the differences in the boot files so you get a better understanding.

It’s just a matter of figuring out what would be necessary to complete your project

[QUOTE][B]Unlike a traditional PXE ROM, iPXE is able to boot over a wide area network such as the Internet. If the machine you are testing is connected to the Internet, you can boot the iPXE[/B][/QUOTE]

source: [url]http://ipxe.org/[/url]

This guy has a way of completing what you are asking, I’m sure it can be doctored to look at FOG
[url]http://www.rmprepusb.com/tutorials/ipxe[/url]

Best of luck, and Godspeed!

And just to clear up any confusion. FOG does not require Sysprep.

However Windows heavily recommends a sysprep.

Since it’s a VM, take a snapshot. Then issue the dnsmasq removal command:

[code]sudo apt-get remove dnsmasq[/code]

See if you can Ping internally, if so test the internet. Reboot the VM, turn off your dhcp service again and see if internet is still available. If any of this breaks your ability to connect to the network, then you need to restore your snapshot and disable both the dhcp and dnsmasq services on boot when you need to connect to your home network.

That’s a tough one. see in Ubuntu 12.04.4 and 12.04.5 and 14.04 and 14.10 they started including dnsmasq-base as a service and requiring it for network-manager. you can issue a command to remove the dnsmasq service, but it’s likely to break your entire ability to connect to a network, which makes it really hard to install services to fix your issues. I would issue the dnsmasq stop command when you are at home and leave the service installed.

When you say internet, you actually mean to World wide Web? or are you unable to connect to your home network?

I don’t see why not having internet to copy the file from one computer to another would cause you any grief.

If I were you, I would disable the dhcp server when I want to connect to my home network.

It sounds to me, your issues are stemming from two DHCP servers in the network and the laptop doesn’t have the correct nameserver entries for your network.

How are you setting your static IP address? What Linux OS have you installed fog on?

Sorry I read that you stopped the service but it didn’t solve the issue, have you used the resolvconf solutions yet?

yes there should be a password set, try updating the password to that of the FOG user, save settings and try again.

you can also use a ssh terminal such as putty to ftp into the fog server, if you can create folders in the command line using putty, your fog server should be able to move images without intervention.

[quote=“Chris Shanks, post: 39909, member: 27169”]Update: I think it is the image creation process as when I create a new image and save to default storage node (/images) it does not create a subdirectory for the upload to save in causing the previously posted error. Is this just my sql or the svn?
If it is just me, would you be able to help solve the problem please?
Thanks

Info:
in fog settings.
fog storage nod is: fogstorage
fog storage node pass: random password that i presume sql created, should this be the defined one I entered during installation?[/quote]

This is neither sql or the svn, it is your FTP settings. FTP is how fog moves the folder from /images/dev/macaddress to /images/imagename.

Please verify that your FTP username and password are correct in the settings.

you can manually create the folder and move the content in from /images/dev/macaddress, this would solve the issue until you can fix your FTP problems.

MMMMM Updater script

[quote=“Ashley Rimmington, post: 39862, member: 27226”]Sorry for the misunderstanding on my part! Glad to say it worked like a charm!
Thank you so much for your help guys.

Just a thought here:
Might I suggest making this a part of the default install for a windows environment install? I say this because my server is available for me to configure (which made me think that the link above didn’t apply since mine wasn’t “unmodifiable”) but when following default install procedure the system didn’t work in the end. With this dnsMASQ setup it works beautifully though!

It just feels to me that this may be a required step for a windows server based DHCP setup.

Thanks again![/quote]

You are quite welcome!

But not necessarily true. Every environment is different. Most have the ability to edit the DHCP scope and have their file delivered correctly. Sometimes users don’t have access to the DHCP Scope because it is managed by someone else, or a third party and this is where DNSMASQ shines. Sometimes the file is not delivered completely and DNSMASQ helps to resolve the issue (I suspect this is the issue you actually faced.)

A Further problem I see, is that Ubuntu 12.04.4, 12.04.5 and 14.04, 14.10 have started including dnsmasq-base in the installation to help with dns resolution. This is a poor decision by conical, IMHO, and has lead to issues with installing and starting DNSMASQ. This would lead to causing FOG installation to fail unless you render your internet useless and try to install FOG… no wait FOG needs the internet to download modules for installation, this sounds bad already

What I think was happening in your environment, is probably what is happening in mine. The file was not being passed entirely and DNSMASQ has helped to resolve this issue. I think DNSMASQ would be a good default module to install with FOG by asking a few questions and creating the file according to the responses, but having FOG install DNSMASQ and use it by default could be nasty and ugly.

I’m glad DNSMASQ worked for you though

Dnsmasq, as Tom stated, does not replace anything in your environment. It will act as a proxy DHCP server and offer ip address and network information to machines in the Pre eXecution Environment (PXE).

Dnsmasq will act as a “secretary” if you will for a lack of better terms, and it will point the hosts to the correct file and server.

Dnsmasq doesn’t replace any elements in the environment, it just helps to resolve your hosts to your correct boot information.

Dnsmasq is a simple install, then you edit the /etc/exports file and paste the ltsp.conf file contents from the wiki and go.