Dear developers,
Please check the new one from
https://github.com/pakdel/fusioninventory-agent-gui
It was tested on the following Linuxes:
PCLinuxOS i686, Qt 4.7.3 32-bit
Ubuntu 10.04.1 LTS i686, Qt 4.6.2 32-bit
Ubuntu 11.04 x86_64, Qt 4.7.2 32-bit
Slackware 13.37 x86_64, Qt 4.7.0 64-bit
Since fusioninventory-agent_windows-i386_2.1.8-2.exe is 13MB, it cannot
be embedded as a Qt resource in windows as a big chunk! I have even
tried compiling it without optimization (with -O0 option of the
compiler) on a 64bit version of Windows 7 with 6GB of RAM an I got the
following error:
cc1plus.exe: out of memory allocating 65536 bytes.
Any idea? any suggestion?
IMO fusioninventory-agent_windows-i386_2.1.8-2.exe needs a command-line
parameter to set the installation folder.
If installation path of the agent can not be specified during
installation via command line, the "Files and Folders" tab can be
removed However, if the option of local agent execution on Linux systems
is kept, this tab might
come in handy).
Le 06/04/2011 09:03 PM, Amir Pakdel a écrit :
On Wed, Jun 1, 2011 at 2:40 PM, Gonéri Le Bouder <[email protected]
<mailto:[email protected]>> wrote:
2011/5/31 Amir Pakdel <[email protected]
<mailto:[email protected]>>:
> Dear developers,
>
> Please check the new version. Here is a summary of changes:
>
> "Remote Unix / Linux Host" radio button is disabled (but still
there). IMHO
> it would inform the user that this is not supported.
> Embedded "fusioninventory-agent_windows-i386_2.1.8-2.exe",
> "winexe-static-081123" and "PsExec.exe" into the agentWizard
executable.
> They can be easily replaced by any other executable: merely need
to be
> aliased as "inst-win.exe", "winexe" and "psexec.exe" in the
> "FusionInventory.qrc" resource.
>
> This version does installation on a remote Windows Host from a
Linux (when
> executed on a Linux, it can install FusionInventory on a remote
Windows
> host) without requiring any files other than the "agentWizard"
itself.
Here, on my Linux, I get "Could not copy the embedded winexe file
into a
regular file".
The process failed to start. Either the invoked program is
missing, or you
may have insufficient permissions to invoke the program.
I was on vacation. I will look into the source code again tomorrow and
I will
try to generate better error messages.
I also think the "Local Host" option should be turned off since I
run Linux.
It can be easily done but IMHO keeping the option of local agent execution
on Linux systems might be beneficial.
Is it possible to declare a network range of machine? Is it possible
to use nmap to find the Windows host on the network? It's maybe
over complicated.
I would keep a TODO list :)
This one accepts the following forms of remote windows host(s):
* Single host name: test.mycompany.com
* Single host IP: 192.168.1.17
* IP list: 192.168.1.16, 192.168.1.17, 192.168.1.18
* IP range: 192.168.1.16 - 192.168.1.18
* Network specified by subnet: 192.168.1.0 / 255.255.255.0
* Network specified by CIDR: 192.168.1.0 / 24
As result, the following is a valid value for "Host(s)" in "Remote host
to be inventoried":
test.mycompany.com, 10.10.2.26, 10.10.3.167, 192.168.1.0 /
255.255.255.0, 192.168.3.0 / 24
Or even you can leave it to the application to sweep your entire subnet
by selecting "Try the entire network subnet". If you have these network
interfaces:
eth0 inet addr:10.10.1.37 Bcast:10.10.1.255 Mask:255.255.255.0
eth0:1 inet addr:10.10.2.37 Bcast:10.10.2.255 Mask:255.255.255.0
eth1 inet addr:10.10.3.37 Bcast:10.10.3.255 Mask:255.255.255.0
lo inet addr:127.0.0.1 Mask:255.0.0.0
It would be the same as specifying the following as "Host(s)":
10.10.1.37/24, 10.10.2.37/24, 10.10.3.37/24,
The trailing "," would be ignored.
> As a result, installation tab is removed completely.
> Now I am going to implement installation on a remote Windows
Host from a
> windows.
I think the "Files and Filders" tab can be removed too since we
don't use
it.
If installation path of the agent can not be specified during
installation via
command line, this "Files and Filders" tab can be removed. Moreover, if
the option of local agent execution on Linux systems is kept, this tab
might
come in handy.
Some of the messages need to be clarified. I suggest these changes:
"Server" tab → "Installation target"
"Local Host" → Install the agent on this system
"Remote Windows Host" → Install the agent on a remote Windows Host
using the RPC Service interface and the $Admin share (PsExec).
"Cancel" and "Perform Inventory" button location should be
switched and
"Perform Inventory" should be in bold
Changes on the "FusionInventory Server" should only used during
the installation
and not be stored locally.
Do you mean that the agent should be run with default settings, without
command line arguments?
Any opinion?
What you are doing here is just great and will quickly be a much
better alternative to
the NSIS installer interface.
I would be glad to do useful things :)
Best regards,
Amir Pakdel
_______________________________________________
Fusioninventory-devel mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/fusioninventory-devel
