Posts made by Kiweegie

Hey Falko

thanks for that. The host report gives me the majority of what I need however at work I’ve just completed an audit of 300+ machines all grouped by the bank of desks they’re sitting at. I’d like to be able to export a report showing all the hosts per a host report but have an extra column listing the group they are assigned to. Can then match up with AD which also has the same host in a group setup to ensure all machines are in AD and non-live machines can be removed from AD (but optionally still kept in the Fog Server database and added to a “spares” group).

I was hoping I could just edit the existing fog host report.php file somewhere to add the relevant code to include the group column.

Access may be a path forward but Access and SQL is a somewhat closed book to me…

Apologies for hijacking the thread - I’d like to create a report also (to export a list of hosts in groups) but can’t seem to find any information on how I create or copy an existing report and edit it. I know it has to be uploaded in php format but that’s it. Are there any primers anywhere online to nudge me in the right direction? I’ve searched the forums to no avail

cheers,

I too would be keen to know if this is possible. I’ve seen the upload new report link but haven;t seen anywhere on line outlining how to create your own custom report.

Just in case anyone else gets this error, one thing I’ve found is that the image file names are case sensitive. Adding the name manually in the wrong case will result in the above error - so check the actual name of the file in /images/ and ensure the file name matches exactly in the fog web interface.

Glasgow, UK

Hi Chad I’ve just checked my side (win7 pro 32bit with chrome version 19.0.1084.52) and the kill task shows fine for me. I checked both an image deploy and a single snapin - both showed the red cross under kill task.

Is it perhaps a version issue?

Tom

Hi all

Not sure whether this is a bug or not. I’ve added hosts to an existing group via the GUI and it has duplicated entries where the host already existed in the group. I know if I upload hosts via a csv file the system only adds NEW hosts - any others on the hostlist.csv file which already exist are ignored. But there does not seem to be any validation when adding hosts to groups.

Can anyone else confirm if this is happening for them and if so where is the correct place to log this as a bug/feature request with the devs?

cheers.

Hi Robin

I take it you’ve created your new Win7 image and have uploaded it to the server correct? And you’ve associated that new image to the host you’re trying to image and also updated the host os entry to win7 too. If you open the host from the GUI and deploy the image from there what happens?

Tom

Hey Kansuke, I had posted this in the other thread but thought best to update this one now I see it…

How are you adding hosts into fog then? I take it you mean you’ve got the mac address in both host name and mac address fields of the UI? Presumably this is through quick association at boot? Given the number of pcs you’re supporting I understand a visit to each to perform full host registration would be time consuming in the extreme. The only other way I can think of doing this (others here may have better/more clever ideas however) is to use the hostimport.csv. You’d still need to marry up the mac address to the asset tag though. Is the asset tag one you’ve applied yourself or one from the pc manufacturer which could be picked up via WMI or similar?

Tom

@Kansuke

how are you adding hosts into fog then? I take it you mean you’ve got the mac address in both host name and mac address fields of the UI? Presumably this is through quick association at boot? Given the number of pcs you’re supporting I understand a visit to each to perform full host registration would be time consuming in the extreme. The only other way I can think of doing this (others here may have better/more clever ideas however) is to use the hostimport.csv. You’d still need to marry up the mac address to the asset tag though. Is the asset tag one you’ve applied yourself or one from the pc manufacturer which could be picked up via WMI or similar?

Tom

I don’t know of a way to do this from Windows to Fog as like was said above Fogs hostname changer dictates that side of things.

@Kansuke, it sounds like the way you’re using the hostname within fog is not quite right. You mention
[QUOTE]I can join the domain automatically but I need to use the asset tag as the computer name instead of the mac address. [/QUOTE]

The mac address is how fog identifies an individual machine but the hostname can be anything you like so theres nothing stopping you from naming the machine based on asset tag. You can do this when you first associate the machine with fog either at the pc when doing full host name and registration or via the web gui.

@Jmacavali: If you do need to rename again once the pc is imaged say once you’ve deployed to a specific room, a simple way might be to maintain the host list in a csv file in the format required by fog to import and export hosts. You can get an example from wiithin fog itself. Put that csv file on a share accessible by all involved and have them update the hostname based on the room they put the machines in and then import the host.csv file back into fog once done

Still a manual process but quicker than doing within the GUI one by one.

Another alternative which would avoid the need to rename the machines at all would be to use fogs groups function. Just name the pcs as normal via asset tag and once you know what room they’re in put them in a group by that name. Doesn’t help you if you want the names to show up in AD or something with the room name appended but if you need a quick way to determine location its a simple workaround.

I’ve found with fairly regular kit moves even in a site of only 300 odd machines that a naming convention based on location is a pain in the rear end. Much better to name based on serial number or asset tags (which don’t change) and use fog or OU’s within AD to group the machines logically. Just my tuppence worth.

Tom

Another issue may be disk space. I ran into that only today. Check that you have enough free space on the server to upload a new image to.

Tom

I used to freak out too when I saw that - started around Fog 0.30 I think from memory but doesn’t seem to stop anything from working. And when I asked similar question some time ago was told by those more in the know than myself that its not something to worry about. Wish it would get sorted though!

Tom

Quickest way I can think of is to go to the hosts section in web GUI select all and create a new group called “All Hosts” then open that group and apply the new OS to the whole group. Job done,

Tom

Also check out the tutorials link theres some good stuff in there including an instlalling fog in ubtuntu which you may also find useful.

Tom

ok just found the tutorials section which handles the knowledge base question.

Hey Alan

yeah for a Windows or Mac oriented user the no GUI on linux servers by default can throw you. But its done that way for a reason - the GUI adds a significant performance hit on a server, which typically you want as streamlined as possible. Another reason I always recommend adding OpenSSH to a server so once you have that setup you can use PutTy or other client to SSH into the server. Allows you to copy and paste commands from forums like this if needed…

So initially you will have downloaded the installer in .gz format to somewhere on the server. I typically use /etc/opt but it could be anywhere within reason. For the sake of instructions here assume the above and alter as needed for your environment.

First you need to extract the archive.

[CODE]cd /etc/opt
tar -xvzf fog_0.32.tar.gz[/CODE]

Using the [I][B]ls[/B][/I] command you should now see the archive and extracted contents

[CODE]ls
fog_0.32 fog_0.32.tar.gz[/CODE]

cd into the extracted folder and then to the [I][B]bin[/B][/I] folder within that folder

[CODE]cd /fog_0.32/bin[/CODE]

Run the installer from there (using sudo to elevate privileges, assume you’re not running as root)

[CODE]sudo ./installfog.sh[/CODE]

rest of the instructions should keep you covered.

regards, Tom

Hi Sami is the VM running in bridged or NAT mode? Are you trying to access the management interface by DNS name or IP address? Can you ping the hostname or IP?

Hi Alan up to you really but all the versions of Ubuntu server from 9.10 should be fine. We use 10.10 at work which is why the how to mentions that but you might want to try the latest version (12.04). Any of the .04 editions of Ubuntu are their Long Term Support (LTS) releases so should be most stable versions and obviously get updates and love from the devs for longer. Newer versions include the most recent security patches too but this is probably not as much of a concern if you’re only using it in a lab environment.

Hope all goes well. Post back if you have any problems. Regards, Tom

Hi Alan try these links from my public dropbox.

[URL=‘https://dl.dropbox.com/u/9458832/Ubuntu install guide.pdf’]Ubuntu guide[/URL]
[URL=‘https://dl.dropbox.com/u/9458832/Fog server set up and configuration.pdf’]Basic fog install guide[/URL]

Both are basic and may not cover everything you need. If you have questions post back and I’ll do what I can to help.

Regards, Tom