1. License
2. Documentation
2.1. Introduction
2.1.1. Thanks
2.1.2. About
2.2. Installation
2.2.1. Components
2.2.1.1. External components
2.2.1.1.1. Fileserver
2.2.1.1.2. Webserver
2.2.1.1.3. DHCP
2.2.1.1.4. DNS
2.2.1.1.5. PXE
2.2.1.1.6. TFTP
2.2.1.2. Internel components
2.2.1.2.1. Authentification
2.2.1.2.2. User/Group back-end
2.2.1.2.3. LDAP
2.2.1.2.4. DB
2.2.1.2.5. Modules
2.2.1.2.6. Connectors
2.2.1.2.7. Boot environment
2.2.1.2.7.1. Componets
2.2.1.2.7.2. Boot process
2.2.1.2.7.3. Profiles
2.2.1.2.7.4. z/etc/init.conf
2.2.2. Run the install script
2.2.2.1. Download
2.2.2.2. Install and preapare webserver
2.2.2.2.1. Extract files
2.2.2.2.2. Install minimum
2.2.2.2.3. Install optional
2.2.2.2.4. Configure apache
2.2.2.2.5. Configure php
2.2.2.2.6. Configure mysql
2.2.2.3. Configure networkshare
2.2.2.3.1. Configure samba
2.2.2.4. Run install.php
2.2.2.4.1. Install check
2.2.2.4.2. Step 1 Chooce language
2.2.2.4.3. Step 2 Read license
2.2.2.4.4. Step 3 Check config file
2.2.2.4.5. Step 4 Database settings
2.2.2.4.6. Step 5 Created tables
2.2.2.4.7. Step 6 Register functions
2.2.2.4.8. Step 7 Add initial group
2.2.2.4.9. Step 8 Add initial user
2.2.2.4.10. Step 9 Installation end
2.2.2.4.11. Step 10 Create laguages
2.2.2.4.12. Ready
2.10. Modules
2.10.1. ssh_client
2.10.1.1. Description
2.10.1.2. Installation
2.10.1.2.1. Configuration
2.10.1.2.2. Personal configuration
2.10.1.2.3. First connect to host
2.10.1.2.3.1. Host settings
2.10.1.3. SSH Shell
2.10.1.4. SSH Browser
2.10.2. ldapmgr
2.10.2.1. Description
2.10.2.2. Installation
2.10.2.2.1. Configuration
2.10.2.2.1.1. Add new Server
2.10.2.2.1.2. Base DNs
2.10.2.2.1.3. Templates
2.10.2.2.1.4. Search configuration
2.10.2.2.2. Personal configuration
2.10.2.3. Ldap Manager
2.10.2.3.1. The menu
2.10.2.3.2. Tree view
2.10.2.3.3. Search
2.10.2.3.4. New entry
2.10.2.3.5. Edit entry
2.10.2.3.6. View entry
2.10.2.3.7. Clear cache
2.10.3. licences
2.10.3.1. Description
2.10.3.2. Installation
2.10.3.2.1. Configuration
2.10.3.2.2. Licence types
2.10.3.3. Usage
2.10.3.3.1. Licence groups
2.10.3.3.1.1. Add new licencegroup
2.10.3.3.1.2. Show a single licencegroup
2.10.3.3.1.3. Assign operating system to licence
2.10.3.3.1.4. Assign software to licence
2.10.3.3.1.5. Assign licence to a user
2.10.3.3.1.6. show details on operating system matches
2.10.3.3.1.7. show details on software matches
2.10.3.3.2. Licences
2.10.3.3.2.1. Add new licence
2.10.3.3.2.2. Show licences
2.10.3.3.3. Mediums
2.10.3.3.3.1. Show mediums
2.10.4. Settings
2.10.4.1. Description
2.10.4.1.1. Installation
2.10.5. dns_ldap
2.10.5.1. Description
2.10.5.2. Installation
2.10.6. locations
2.10.6.1. Description
2.10.6.2. Installation
2.10.7. samhain
2.10.7.1. Description
2.10.7.2. Quick start:
2.10.7.2.1. Configure your Yule Server
2.10.7.2.2. Remote installation
2.10.8. switch
2.10.8.1. Description
2.10.8.2. Installation
2.10.9. PXE
2.10.9.1. Description
2.10.9.2. Installation
2.10.9.3. TFTP Server configuration
2.10.9.3.1. tftpd.remap
2.10.9.3.2. TFTP Server config example
2.10.10. cal
2.10.10.1. Description
2.10.10.2. Installation
2.10.11. Computer
2.10.11.1. Description
2.10.11.2. Installation
2.10.11.2.1. Configuration
2.10.11.2.2. Personal configuration
2.10.11.2.3. The menu
2.10.11.3. Computer view
2.10.11.3.1. Arp entries / automatic fetch network devices
2.10.11.3.2. Add a new computer
2.10.11.3.2.1. Import
2.10.11.3.2.1.1. Import LDAP
2.10.11.3.2.1.2. Import CSV
2.10.11.3.2.1.3. Import PING
2.10.11.3.2.1.4. Import NMAP
2.10.11.3.2.2. Add from arp entries
2.10.11.3.3. Single computer view
2.10.11.3.4. Operating systems
2.10.11.3.5. Partitioning
2.10.11.3.6. Software and packages
2.10.11.3.6.1. Packages
2.10.11.3.6.2. Software
2.10.11.3.7. PXE
2.10.11.3.8. Reset
2.10.11.3.9. Power on/off WOL
2.10.11.3.10. Clone a computer
2.10.11.4. Searchgroups
2.10.11.4.1. Add a new searchgroup
2.10.11.4.2. Add a new definition to a searchgroup
2.10.11.4.3. Overview of a searchgroup
2.10.12. Software
2.10.12.1. Description
2.10.12.2. Installation
2.10.12.2.1. Configuration
2.10.12.2.2. User configuration
2.10.12.3. Repositories
2.10.12.4. Software
2.10.12.4.1. Software versions
2.10.12.5. Packages
2.10.12.6. User
2.10.12.7. Groups
2.10.12.8. Winupdates
2.10.13. syslog_ng
2.10.13.1. Description
2.10.13.1.1. Syslog-ng Documentation
2.10.13.2. Installation
2.10.13.2.1. Configuration
2.10.13.2.2. Personal configuration
2.10.13.3. Layout
2.10.13.4. Syslog configuration
2.10.13.4.1. Add a new server
2.10.13.4.2. Add a new database
2.10.13.4.3. Add a new table (destination)
2.10.13.4.4. Create new config
2.10.13.4.4.1. Add new source
2.10.13.4.4.2. Add new filter
2.10.13.4.4.3. Add new destination
2.10.13.4.4.4. Combine config for a server
2.10.13.4.4.4.1. Add destination to log
2.10.13.4.4.4.2. Add source to log
2.10.13.4.4.4.3. Add filter to log
2.10.13.4.5. View and write config
2.10.13.4.6. Server commands
2.10.13.4.7. Logs
2.10.13.4.7.1. View the logs
2.10.13.4.7.2. Filter the logs
2.10.13.4.7.3. Global search around all tables and all databases
2.10.13.4.8. Statistic
2.10.13.4.9. Statistic Graph
2.10.13.5. Rotate the tables:
2.10.13.6. Clear old syslog entries
2.10.14. dhcp_ldap
2.10.14.1. Description
2.10.14.2. Installation
2.10.15. Inventory
2.10.15.1. Description
2.10.15.2. Installation
2.10.15.3. Usage
2.10.15.4. Settings
2.10.15.4.1. Global module settings
2.10.15.4.2. User settings
2.10.16. cron
2.10.16.1. Description
2.10.16.2. Installation
2.10.16.3. Install on clients
2.10.16.3.1. Run the container Script via scheduled task on Windows systems
2.10.17. Search
2.10.17.1. Description
2.10.17.2. Installation
2.10.18. Wiki
2.10.18.1. Description
2.10.18.2. Installation
2.10.19. radius_ldap
2.10.19.1. Description
2.10.19.2. Setup freeradius
2.10.19.2.1. radiusd.conf
2.10.19.2.2. Functions to rewrite mac-address
2.10.19.2.3. ldap configuration
2.10.19.2.4. log configuration
2.10.19.3. Deploy logs to database
2.10.20. Installation
2.10.20.1. Description
2.10.20.2. Installation
2.10.20.2.1. Get harddisk and os templates
2.10.20.2.2. Prepare Operating system
2.10.20.2.2.1. Create os
2.10.20.2.2.2. Configure os
2.10.20.2.3. info.txt
2.10.20.3. Operating systems
2.10.20.3.1. Install methods
2.10.20.3.1.1. Directly
2.10.20.3.1.2. Image
2.10.20.3.1.3. Transfermodes
2.10.20.3.2. Windows
2.10.20.3.2.1. Windows 2000/XP/2003
2.10.20.3.2.2. Windows Vista/2008/Windows7
2.10.20.3.2.2.1. Install method wim file
2.10.20.3.2.2.2. Install method ntfsclone
2.10.20.3.2.2.2.1. Save a ntfsclone
2.10.20.3.2.2.2.2. Save a partimage via dd
2.10.20.3.2.2.2.3. How it works:
2.10.20.3.2.2.3. Windows error codes
2.10.20.3.3. Kickstart
2.10.20.3.3.1. CentOS
2.10.20.3.3.2. Fedora
2.10.20.3.3.3. RHEL
2.10.20.3.3.4. ScientificLinux
2.10.20.3.3.5. ESX
2.10.20.3.4. Presseed
2.10.20.3.4.1. Debian
2.10.20.3.4.2. Ubuntu
2.10.20.3.5. openSuSE/SLES
2.11. Connectors
2.11.1.
2.11.1.1. Description
2.11.1.2. Installation
2.11.1.3. Configuration
2.11.1.4. Usage
2.11.2.
2.11.2.1. Description
2.11.2.2. Installation
2.11.2.3. Configuration
2.11.2.4. Usage
2.11.3.
2.11.3.1. Description
2.11.3.2. Installation
2.11.4.
2.11.4.1. Description
2.11.4.2. Installation
2.11.4.3. Configuration
2.11.4.3.1. Configure credentials
2.11.4.3.2. Configure commands
2.11.4.3.3. Logs
2.11.4.4. Usage
2.11.4.4.1. Run command from the connector
2.11.4.4.2. Run commands via cron / script
2.11.5.
2.11.5.1. Description
2.11.5.2. Installation
2.11.5.3. Configuration
2.11.5.4. Usage
2.11.6. Inventory
2.11.6.1. Description
2.11.6.2. Installation
2.11.6.3. Configuration
2.11.6.4. Usage
2.11.7.
2.11.7.1. Description
2.11.7.2. Installation
2.11.7.3. Configuration
2.11.7.4. Usage
2.11.8.
2.11.8.1. Description
2.11.8.2. Installation
2.11.8.3. Configuration
2.11.8.4. Usage
2.11.9.
2.11.9.1. Description
2.11.9.2. Installation
2.11.10.
2.11.10.1. Description
2.11.10.2. Installation
2.11.10.3. Configuration
2.11.10.4. Usage
2.11.11.
2.11.11.1. Description
2.11.11.2. Installation
2.11.11.3. Configuration
2.11.11.4. Usage
2.11.12.
2.11.12.1. Description
2.11.12.2. Installation
2.11.12.3. Configuration
2.11.12.4. Usage
2.11.13.
2.11.13.1. Description
2.11.13.2. Installation
2.11.13.3. Configuration
2.11.13.4. Usage
3. Changelog
3.1. Changelog
3.1.723. Computer Release: 723
3.1.728. Computer Ping and Memory Release: 728
3.1.751. LDAP / Software Release: 751
3.1.763. Computer Release: 763
3.1.777. Ldap Auth Computer Import Release: 777
3.1.793. Feature Requests/Bugs Release: 793
3.1.804. New Theme Release: 804
3.1.808. Computer Release: 808
3.1.809. HTML Release: 809
3.1.818. Switch Release: 818
3.1.830. Switch port management Release: 830
3.1.875. Software Bug Release: 875
3.1.892. PXE Release: 892
3.1.899. New release Release: 892
3.1.908. APIssh Feature Request #2355852 Release: 908
3.1.911. Feature Request #2256096 Release: 911
3.1.913. Feature Request #2355821 Release: 913
3.1.920. API shh Release: 920
3.1.927. Feature Request #2540495 Release: 927
3.1.931. Syslog Release: 931
3.1.1020. New modules Release: 1020
3.1.1030. Bugfixes and inventory profile Release: 1030
3.1.1088. Add support for Vista/2008/Windows7 and ubuntu Release: 1088
3.1.1116. New logo Release: 1116
3.1.1121. Multicast installations Release: 1121
3.1.1128. Documentation Release: 1128
3.1.1134. BUG fixes Release: 1134
3.1.1144. Feature requests Release: 1144
3.1.1216. BUG fix php 5.3 compatibiliy Release: 1216
3.1.1350. Release update Release: 1350
3.1.1357. Feature requests Release: 1357
3.1.1372. Feature requests Release: 1372
3.1.1378. BUG fixes Release: 1378
3.1.1382. Feature requests Release: 1382
3.1.1386. BUG fixes Release: 1386
3.1.1395. BUG fixes Release: 1395
3.1.1402. BUG fixes Release: 1402
3.1.1149. Feature requests Release: 1149
3.1.1151. BUG fix Release: 1151
3.1.1456. Fusioninventory Release: 1456
3.1.1675. first release of uranos
3.1.1689. BUG fixes
3.1.1721. BUG fixes, Feature Requests
3.1.1742. BUG fixes, documentation
3.1.1770. New Release
3.1.1777. New Theme
3.1.1786. BUG fixes
3.1.1799. Syslog-ng 3.x compatibility
3.1.1813. pChart
3.1.1824. System tables
3.1.1831. Ubuntu 11.04 Template
3.1.1913. Bug Fixing new Feature: Windows update scanning
3.1.1945. Bug Fix release
3.1.1953. Support for Advanced Disk Format
3.1.1960. Bug Fix release
3.1.2011. Cron module update
3.1.2025. Direct install from iso/wim
3.1.2034. BugFix
3.1.2073. fusioninventory deployment and esx inventory
3.1.2086. Bug Fixes / radius_ldap
3.2. Uranos-boot
3.2.0.8.7. boot-cd update Release: 0.8.7
3.2.1.1.2. boot-cd update Release: 1.1.2
3.2.1.2. boot-cd update Release: 1.2
3.2.1.2.1. boot-cd update Release: 1.2.1
3.2.1.2.2. boot-cd update Release: 1.2.2
3.2.1.2.3. boot-cd update Release: 1.2.3
3.2.1.2.4. boot-cd update Release: 1.2.4
3.2.1.3.0. boot-cd update Release: 1.3.0
3.2.1.3.1. boot-cd update Release: 1.3.1
3.2.1.3.2. boot-cd update Release: 1.3.2
3.2.1.3.3. boot-cd update Release: 1.3.3
3.2.1.4.0. boot-cd update Release: 1.4.0
3.2.1.4.1. boot-cd update Release: 1.4.1
3.2.1.4.2. boot-cd update Release: 1.4.2
3.2.1.4.3. boot-cd update Release: 1.4.3
3.2.1.4.4. boot-cd update Release: 1.4.4
3.2.1.4.5. boot-cd update Release: 1.4.5
3.2.1.4.7. boot-cd update Release: 1.4.7
3.2.1.4.8. boot-cd update Release: 1.4.8
3.2.1.4.9. boot-cd update Release: 1.4.9
3.2.1.5.0. boot-cd update - first uranos boot release Release: 1.5.0
3.2.1.5.1. boot-cd update
3.2.1.6.0. boot-cd update
3.2.1.6.1. boot-cd update
3.2.1.7.0. boot-cd update
3.2.2.0.0. boot-cd update
3.2.2.0.1. boot-cd update
3.2.2.0.2. boot-cd update
3.2.2.1.0. boot-cd update
3.2.2.1.1. boot-cd update
3.2.2.2.0. boot-cd update new option to access remotely and monitor the progress
3.2.3.2.21. boot-cd update new versioning
3.2.3.2.33. boot-cd update
3.2.3.6.9. new libs
3.2.3.8.3. boot-cd update
3.2.3.8.8. boot-cd update

1. License


                    GNU GENERAL PUBLIC LICENSE
                       Version 2, June 1991

 Copyright (C) 1989, 1991 Free Software Foundation, Inc.,
 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
 Everyone is permitted to copy and distribute verbatim copies
 of this license document, but changing it is not allowed.

                            Preamble

  The licenses for most software are designed to take away your
freedom to share and change it.  By contrast, the GNU General Public
License is intended to guarantee your freedom to share and change free
software--to make sure the software is free for all its users.  This
General Public License applies to most of the Free Software
Foundation's software and to any other program whose authors commit to
using it.  (Some other Free Software Foundation software is covered by
the GNU Lesser General Public License instead.)  You can apply it to
your programs, too.

  When we speak of free software, we are referring to freedom, not
price.  Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
this service if you wish), that you receive source code or can get it
if you want it, that you can change the software or use pieces of it
in new free programs; and that you know you can do these things.

  To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if you
distribute copies of the software, or if you modify it.

  For example, if you distribute copies of such a program, whether
gratis or for a fee, you must give the recipients all the rights that
you have.  You must make sure that they, too, receive or can get the
source code.  And you must show them these terms so they know their
rights.

  We protect your rights with two steps: (1) copyright the software, and
(2) offer you this license which gives you legal permission to copy,
distribute and/or modify the software.

  Also, for each author's protection and ours, we want to make certain
that everyone understands that there is no warranty for this free
software.  If the software is modified by someone else and passed on, we
want its recipients to know that what they have is not the original, so
that any problems introduced by others will not reflect on the original
authors' reputations.

  Finally, any free program is threatened constantly by software
patents.  We wish to avoid the danger that redistributors of a free
program will individually obtain patent licenses, in effect making the
program proprietary.  To prevent this, we have made it clear that any
patent must be licensed for everyone's free use or not licensed at all.

  The precise terms and conditions for copying, distribution and
modification follow.

                    GNU GENERAL PUBLIC LICENSE
   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

  0. This License applies to any program or other work which contains
a notice placed by the copyright holder saying it may be distributed
under the terms of this General Public License.  The \"Program\", below,
refers to any such program or work, and a \"work based on the Program\"
means either the Program or any derivative work under copyright law:
that is to say, a work containing the Program or a portion of it,
either verbatim or with modifications and/or translated into another
language.  (Hereinafter, translation is included without limitation in
the term \"modification\".)  Each licensee is addressed as \"you\".

Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope.  The act of
running the Program is not restricted, and the output from the Program
is covered only if its contents constitute a work based on the
Program (independent of having been made by running the Program).
Whether that is true depends on what the Program does.

  1. You may copy and distribute verbatim copies of the Program's
source code as you receive it, in any medium, provided that you
conspicuously and appropriately publish on each copy an appropriate
copyright notice and disclaimer of warranty; keep intact all the
notices that refer to this License and to the absence of any warranty;
and give any other recipients of the Program a copy of this License
along with the Program.

You may charge a fee for the physical act of transferring a copy, and
you may at your option offer warranty protection in exchange for a fee.

  2. You may modify your copy or copies of the Program or any portion
of it, thus forming a work based on the Program, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:

    a) You must cause the modified files to carry prominent notices
    stating that you changed the files and the date of any change.

    b) You must cause any work that you distribute or publish, that in
    whole or in part contains or is derived from the Program or any
    part thereof, to be licensed as a whole at no charge to all third
    parties under the terms of this License.

    c) If the modified program normally reads commands interactively
    when run, you must cause it, when started running for such
    interactive use in the most ordinary way, to print or display an
    announcement including an appropriate copyright notice and a
    notice that there is no warranty (or else, saying that you provide
    a warranty) and that users may redistribute the program under
    these conditions, and telling the user how to view a copy of this
    License.  (Exception: if the Program itself is interactive but
    does not normally print such an announcement, your work based on
    the Program is not required to print an announcement.)

These requirements apply to the modified work as a whole.  If
identifiable sections of that work are not derived from the Program,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works.  But when you
distribute the same sections as part of a whole which is a work based
on the Program, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote it.

Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Program.

In addition, mere aggregation of another work not based on the Program
with the Program (or with a work based on the Program) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.

  3. You may copy and distribute the Program (or a work based on it,
under Section 2) in object code or executable form under the terms of
Sections 1 and 2 above provided that you also do one of the following:

    a) Accompany it with the complete corresponding machine-readable
    source code, which must be distributed under the terms of Sections
    1 and 2 above on a medium customarily used for software interchange; or,

    b) Accompany it with a written offer, valid for at least three
    years, to give any third party, for a charge no more than your
    cost of physically performing source distribution, a complete
    machine-readable copy of the corresponding source code, to be
    distributed under the terms of Sections 1 and 2 above on a medium
    customarily used for software interchange; or,

    c) Accompany it with the information you received as to the offer
    to distribute corresponding source code.  (This alternative is
    allowed only for noncommercial distribution and only if you
    received the program in object code or executable form with such
    an offer, in accord with Subsection b above.)

The source code for a work means the preferred form of the work for
making modifications to it.  For an executable work, complete source
code means all the source code for all modules it contains, plus any
associated interface definition files, plus the scripts used to
control compilation and installation of the executable.  However, as a
special exception, the source code distributed need not include
anything that is normally distributed (in either source or binary
form) with the major components (compiler, kernel, and so on) of the
operating system on which the executable runs, unless that component
itself accompanies the executable.

If distribution of executable or object code is made by offering
access to copy from a designated place, then offering equivalent
access to copy the source code from the same place counts as
distribution of the source code, even though third parties are not
compelled to copy the source along with the object code.

  4. You may not copy, modify, sublicense, or distribute the Program
except as expressly provided under this License.  Any attempt
otherwise to copy, modify, sublicense or distribute the Program is
void, and will automatically terminate your rights under this License.
However, parties who have received copies, or rights, from you under
this License will not have their licenses terminated so long as such
parties remain in full compliance.

  5. You are not required to accept this License, since you have not
signed it.  However, nothing else grants you permission to modify or
distribute the Program or its derivative works.  These actions are
prohibited by law if you do not accept this License.  Therefore, by
modifying or distributing the Program (or any work based on the
Program), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Program or works based on it.

  6. Each time you redistribute the Program (or any work based on the
Program), the recipient automatically receives a license from the
original licensor to copy, distribute or modify the Program subject to
these terms and conditions.  You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties to
this License.

  7. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License.  If you cannot
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Program at all.  For example, if a patent
license would not permit royalty-free redistribution of the Program by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Program.

If any portion of this section is held invalid or unenforceable under
any particular circumstance, the balance of the section is intended to
apply and the section as a whole is intended to apply in other
circumstances.

It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system, which is
implemented by public license practices.  Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.

This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.

  8. If the distribution and/or use of the Program is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Program under this License
may add an explicit geographical distribution limitation excluding
those countries, so that distribution is permitted only in or among
countries not thus excluded.  In such case, this License incorporates
the limitation as if written in the body of this License.

  9. The Free Software Foundation may publish revised and/or new versions
of the General Public License from time to time.  Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.

Each version is given a distinguishing version number.  If the Program
specifies a version number of this License which applies to it and \"any
later version\", you have the option of following the terms and conditions
either of that version or of any later version published by the Free
Software Foundation.  If the Program does not specify a version number of
this License, you may choose any version ever published by the Free Software
Foundation.

  10. If you wish to incorporate parts of the Program into other free
programs whose distribution conditions are different, write to the author
to ask for permission.  For software which is copyrighted by the Free
Software Foundation, write to the Free Software Foundation; we sometimes
make exceptions for this.  Our decision will be guided by the two goals
of preserving the free status of all derivatives of our free software and
of promoting the sharing and reuse of software generally.

                            NO WARRANTY

  11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN
OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
PROVIDE THE PROGRAM \"AS IS\" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS
TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE
PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
REPAIR OR CORRECTION.

  12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.

                     END OF TERMS AND CONDITIONS

            How to Apply These Terms to Your New Programs

  If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.

  To do so, attach the following notices to the program.  It is safest
to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least
the \"copyright\" line and a pointer to where the full notice is found.

    
    Copyright (C)   

    This program is free software; you can redistribute it and/or modify
    it under the terms of the GNU General Public License as published by
    the Free Software Foundation; either version 2 of the License, or
    (at your option) any later version.

    This program is distributed in the hope that it will be useful,
    but WITHOUT ANY WARRANTY; without even the implied warranty of
    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
    GNU General Public License for more details.

    You should have received a copy of the GNU General Public License along
    with this program; if not, write to the Free Software Foundation, Inc.,
    51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.

Also add information on how to contact you by electronic and paper mail.

If the program is interactive, make it output a short notice like this
when it starts in an interactive mode:

    Gnomovision version 69, Copyright (C) year name of author
    Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
    This is free software, and you are welcome to redistribute it
    under certain conditions; type `show c' for details.

The hypothetical commands `show w' and `show c' should show the appropriate
parts of the General Public License.  Of course, the commands you use may
be called something other than `show w' and `show c'; they could even be
mouse-clicks or menu items--whatever suits your program.

You should also get your employer (if you work as a programmer) or your
school, if any, to sign a \"copyright disclaimer\" for the program, if
necessary.  Here is a sample; alter the names:

  Yoyodyne, Inc., hereby disclaims all copyright interest in the program
  `Gnomovision' (which makes passes at compilers) written by James Hacker.

  , 1 April 1989
  Ty Coon, President of Vice

This General Public License does not permit incorporating your program into
proprietary programs.  If your program is a subroutine library, you may
consider it more useful to permit linking proprietary applications with the
library.  If this is what you want to do, use the GNU Lesser General
Public License instead of this License.

2. Documentation

Documentation

2.1. Introduction

Uranos is not only a tool to install operating systems. It is a system/network management software.

2.1.1. Thanks

Special thanks to all people who helped to develop and test this software.
Thanks also to the pear people. Some functionality is based on the pear stuff.

2.1.2. About

The design of uranos is build to have an easy application framework. For each webapplication you have to ask the same questions again and again:

Authentification

Database

Securtity

Calendar

...

Uranos is built to give you an environment which includes this main functionality:

Permission management

Authentification to database, LDAP (also M$ Active Directory), IMAP, Radius

User[+Group]backend: database or LDAP

Different security checks (e.g. Prevent Session Hijacking, check POST,GET and FILE variables,....)

Templating for easy customize the views

Installing the webapplication

...

2.2. Installation

2.2.1. Components

2.2.1.1. External components

External components depends on your set up and your needs. This will give you an overview for what you need which component.

2.2.1.1.1. Fileserver

You will need a fileserver for different things. The first is for the boot-cd. The boot-cd can handle the following servers:

NFS Use your NFS Server to hold the environment.

SSH You can use a ssh server for mount your environment. This is supported through the sshfs project.

SMB/CIFS This can be a simple share from a Microsoft computer or a Samba share

Local (for local mount the environment, maybe on a usb-stick or a dvd)

See boot cd options how to configure the kernel for this features.
For the os installation the fileserver depends on the installation method of the os you want to install. For example you can install fedora through:

http

nfs

ftp

For the Microsoft Windows os-installation you can use the supported filesystems from the boot cd (see above).
For the software installation in Microsoft Windows through the tools postinst.js and wemerge.cmd you will need a SMB/CIFS share from a Microsoft computer or a Samba share.

2.2.1.1.2. Webserver

You need a webserver with php support to run the GUI. We preffer to use Linux as platform for running the Apache-Webserver.
But it is also possible to run the GUI in every other webserver with php support.

2.2.1.1.3. DHCP

A DHCP-Server is optional. A DHCP-Server gives you the possibility to assign an IP address automatically to your clients. Also it is a precondition to boot your clients via PXE. We prefer to use the DHCP-Server from Internet Systems Consortium. The ISC-DHCP-Server has the possibility to hold your configuration in a LDAP tree. The GUI gives you the availability to manage the DHCP configuration in your LDAP tree. It is also possible to use this LDAP configuration for other DHCP-Servers because the module is based on the Ldap-schema-draft for DHCP.

2.2.1.1.4. DNS

A DNS-Server is optional. A DNS-Server gives you the possibility to assign names to IP addresses. We prefer to use the ISC BIND DNS-Server from Internet Systems Consortium. This ISC BIND DNS-Server can get the configuration from a LDAP tree. The GUI gives you the availability to manage the DNS configuration in your LDAP tree.

2.2.1.1.5. PXE

The PXE (Preboot Execution Environment) is optional. You can boot your clients over the wired network in a PXE.
For the PXE you will need:

TFTP-Server

DHCP-Server

pxelinux.0 - from the SYSLINUX distribution

With the SYSLINUX distribution you are also able to build graphical menus:

The GUI gives you the availability to manage the global PXE configuration and the configuration for each client.

2.2.1.1.6. TFTP

A TFTP-Server is optional. You will need the TFTP-Server for your PXE boot. The server is used to provide the pxelinux file and configuration.

2.2.1.2. Internel components

The internal components will give you an overview about how you can use the GUI to manage the internal or external components.

2.2.1.2.1. Authentification

The user authentification is handled by an internal API.
Currently the API supports these storage drivers:

MDB2 Storage container using PEAR MDB2.

IMAP Storage container for use against IMAP servers.

LDAP Storage container for use against LDAP servers. - also Active Directory.

The GUI provides simple setup for these modules:

LDAP Use your LDAP Server or your Microsoft Active Directory Server.

IMAP Use your IMAP Server.

DB - Use every supported MDB2 (mssql, mysql, mysqli, pgsql,...) whith your own username/password table.

2.2.1.2.2. User/Group back-end

The User/Group back-end is different to your authentification settings. This means you can manage your users in the database (every supported database from the pear package DB) and authentificate them against your IMAP Server, or use the LDAP Server to manage the users but authentificate them against a database. The idea behind this is that you can use your internal user database. Currently the following back-ends are supported:

LDAP and through this also (but untested) Active Directory

Database in every supported DB (fbsql, ibase, informix, msql, mssql, mysql, mysqli, oci8, odbc, pgsql, sqlite and sybase)

2.2.1.2.3. LDAP

For the LDAP back-end you have to set up the parameters in the config file

Set this to "1" to enable the LDAP back-end:

//use ldap as user/groups backend
$u_cfg["useldap"] = 1;

set this to your needs, the ldapdb is used for read actions, the backupldapdb is used for write actions

//ldap database only need if u use ldap user/groups backend
$u_cfg["ldapdb"]=array(
"phptype" => "ldap",
"username" => "unattended",
"password" => "password",
"port" => "389",
"hostspec" => "localhost",
"database" => "dc=example,dc=de"
);

set this to you needs, the user you set up here needs write permissions on your user and groups in your LDAP tree

//ldap backupdatabase for write actions --> only need if u use ldap user/groups backend
 $u_cfg["backupldapdb"]=array(
"phptype" => "ldap",
"username" => "unattended",
"password" => "password",
"port" => "389",
"hostspec" => "localhost",
"database" => "dc=example,dc=de"
);

The settings are also used for the module Ldap Manager.

2.2.1.2.4. DB

The DB back-end is enabled if your are running through the install process from the GUI.
Parameters in the config file:

Set this to "0" to disable the LDAP back-end:

//use ldap as user/groups backend
$u_cfg["useldap"] = 0;

This are the connection settings for the database:

//database
$u_cfg["database"]=array(
"phptype" => "mysql",
"username" => "unattended",
"password" => "",
"hostspec" => "localhost",
"database" => "unattended"
);

2.2.1.2.5. Modules

The GUI is designed modular. This means that you can run the GUI for different setups, for example as a GUI to syslog-servers.
Through the modular system it is easy for you to write your own modules. You can use the API from the GUI which provides you with easy functions. For example to add a entry into a table in a database you can use:

db_insert($tablename,$fields,$dbd="");

db_insert('part_computerconfig',array('pid'=>$pid,'hdtype'=>$hdtype,'computername'=>$computername,'mbr'=>$mbr));

the $dbd can be your own database DSN.
There are core modules which you can not install or uninstall. The following core modules will be setup and installed through the installation:

User (core) The user module manages the users in your User/Group back-end.

Groups (core) The group module manages the groups in your User/Group back-end.

Settings (core) The settings module manages blocks, permissions, language, modules, connectors, sessions, update and authentification settings.

2.2.1.2.6. Connectors

The main idea behind the connectors is that you can bind easy functionality to your computers. It is a precondition that you install the module computer to use the connectors.
The internal connectors are:

Checklist

Comments

DHCP Ldap

DNS Ldap

Inventory (fusioninventory)

Status

One example how to bind other informations to a computer is:

Request Tracker http://bestpractical.com/

It is also possible to use other inventory-tools or databases to bind them to the GUI. For example there is a connector for

Open Computers and Software Inventory

which access the data via the SOAP interface of OCS.

2.2.1.2.7. Boot environment

The boot environment is used for different scenarios. You will need the boot environment for installing Microsoft Windows (2000/XP/2003/Vista/2008). But you can use the boot environment for other things like backup, restore, disk wipe out and so on...

2.2.1.2.7.1. Componets

kernel - linux kernel which is optimized for harddisk and network support

initrd - the root filesystem for the kernel, all programs except the profile scripts

/z - The directory structure which holds the profile environment

The components of the boot environment can be used in different ways:

kenel/initrd can be boot from cd,usb,pxe(network) or other bootable devices

/z can be mount from network (cifs,sshfs,nfs) or from a local device (cd,usb,harddisk,..)

2.2.1.2.7.2. Boot process

The kernel and initrd is loaded by the used boot manager. If you are using the cd the boot manager is syslinux.

The /init which is located in the initrd is loaded by the kernel. The init is a bash script.

init starts:

Mounting /proc and /sys

Mounting /dev for udev

Start udev

Fire up shells on virtual consoles 2 and 3

Start /etc/master on virtual console 1

-> /etc/master take control:

Sending log output to /dev/tty4

Starting syslog - logging to /dev/tty5

Setting umask

Disable kernelmessages

Load keyboard settings (if defined)

Setting up hardware

Force loading modules

configure network (DCHP or manually)

configure / mount /z (this can be from network (cifs,sshfs,nfs) or from a local device (cd,usb,harddisk,..))

gives controll to z/bin/init.sh

-> z/bin/init.sh:

source the z/etc/init.conf

init.sh control your profiles (defined in z/etc/init.conf or via the kernel command line)

init.sh starts the selected profile -> see next section for profile informations

/etc/init/profile/PROFILENAME/ is started

2.2.1.2.7.3. Profiles

The main idea behind the profiles is that you can use the same boot environment for different solutions. Profiles are simple directories which may have one ore more scripts inside. You can specify the profile you want to start via:

kernel command line (profile=PROFILENAME)

the file z/etc/init.conf

The profile directories can contain more than one script. All executable files in this directory will be run in alphabetical order.

2.2.1.2.7.4. z/etc/init.conf

This is the main configuration file for the boot environment.

2.2.2. Run the install script

2.2.2.1. Download

Main Download page:

http://sourceforge.net/projects/uranos/files/

2.2.2.2. Install and preapare webserver

For installing all needed packages you have to install at least (this is only an example, you are free to use other combinations):

apache

php

pear

mysql

2.2.2.2.1. Extract files

Extract the files, in this documentation /srv/ will be used.

#create src directory
mkdir /root/src
#change directory
cd /root/src
#get release
wget http://downloads.sourceforge.net/uranos/uranos-1.531.tar.gz
#change directory to /srv (need to create it or chooce your own)
cd /srv
#extract files
tar xzf /root/src/uranos-1.531.tar.gz
#move
mv /srv/uranos-1.531 /srv/uranos
#give all to the apache user (this is for ubuntu, change www-run to your needs):
chown -R www-data:www-data /srv/uranos

2.2.2.2.2. Install minimum

To install this in debian/ubuntu run the following:

apt-get install apache2 php-pear mysql-server subversion php5-ldap php5-mysql php5-mcrypt php5-gd samba

2.2.2.2.3. Install optional

apt-get install nmap tftpd-hpa syslog-ng slapd gcc dhcp3-server-ldap genisoimage

nmap is for auto discover your network

tftp-hpa if you want to use this host for pxe-boot

syslog-ng if you want to use this host as an syslog server

slapd if you want to managage your DHCP/DNS entries

genisoimage if you want to create auto-running installation cds

dhcp3-server-ldap if you want tio use this host as an dhcp server

2.2.2.2.4. Configure apache

Enable php:

a2enmod php5

This is an example virtual host configuration for the apache webserver.

<VirtualHost install.example.com>
    ServerName install.example.com
    DocumentRoot /srv/uranos
    <Directory "/srv/uranos">
		Options Indexes FollowSymLinks
		AllowOverride None
		Order allow,deny
		Allow from all
    </Directory>
</VirtualHost>

2.2.2.2.5. Configure php

You will need php support in your webserver and the folowing pear packages:

Calendar 0.5.3 beta (pear install Calendar-0.5.3)

HTTP_Download (pear install --alldeps HTTP_Download)

HTML_Template_Sigma (pear install --alldeps HTML_Template_Sigma)

Image_Canvas 0.3.1 alpha (pear install image_canvas-0.3.2)

Image_Graph 0.7.1 alpha (pear install --alldeps image_graph-0.7.1)

MDB2 2.5.0b2 beta (pear install mdb2-2.5.0b2)

MDB2_Driver_mysql 1.5.0b2 beta (pear install mdb2_Driver_mysql-1.5.0b2)

MDB2_Driver_mysqli 1.5.0b2 beta (pear install mdb2_Driver_mysqli-1.5.0b2)

Change memory limit in php:

vi /etc/php5/apache2/php.ini #change the value of the variable "memory_limit" to 128M

2.2.2.2.6. Configure mysql

Create a user and a database for mysql:

CREATE DATABASE unattended;

Remember this user and password because you will need it during the install process.

GRANT ALL PRIVILEGES ON unattended TO 'unattended'@'localhost' IDENTIFIED BY 'some_pass' WITH GRANT OPTION;

Optional you can do this steps also with a tool like phpmyadmin.

2.2.2.3. Configure networkshare

The networkshare holds the software, os and the environment for the boot-cd. The root of this share should be point to "uranos/z/".

2.2.2.3.1. Configure samba

If you have already a networkshare you can skip this and go on.
This is a short smb.conf

[global]
	workgroup = WORKGROUP
	server string = %h server (Deploy)
	wins support = no
	dns proxy = yes
	name resolve order = lmhosts host wins bcast
	log file = /var/log/samba/log.%m
	max log size = 1000
	syslog = 1
	security = user
	encrypt passwords = true
	passdb backend = tdbsam
	obey pam restrictions = yes
	guest account = nobody
	invalid users = root
	unix password sync = yes
	passwd program = /usr/bin/passwd %u
	passwd chat = *Entersnews*spassword:* %nn *Retypesnews*spassword:* %nn *passwordsupdatedssuccessfully* .
	pam password change = yes
	map to guest = bad user
	domain logons = no
	load printers = no
	socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
[install]
	comment = Installation Service
	path = /srv/uranos/z
	guest ok = yes
	read only = no

2.2.2.4. Run install.php

After setting up and starting apache and mysql you can call install.php. For that open your preffered browser and go to the address:

http://install.example.com/www/install.php

install.example.com is the name you have configured in your virtual host.
If you got the error:

Warning: touch() [function.touch]: Unable to create file include/config.php 
because Permission denied in /home/mario/public_html/ua-install/www/install.php on line 12
The config file is not writeable, pleace check the permissions on the file and try again!

Do the following:

touch include/config.php
chown YOURAPACHEUSER:YOURAPACHEGROUP include/config.php
chmod 600 include/config.php

then check the permissions for your webserver (described in 2.2.2.1. Extract files).

2.2.2.4.1. Install check

If you have installed all needed pear packages you should see someting simular to this. If not, read section 2.2.2.5. Configure php of this document. You can follow the link at the bottom to go on to step 1. On some systems it might be that the PEAR path is different, e.g on SLES11 use PEAR include path /usr/share/php5/PEAR.

2.2.2.4.2. Step 1 Chooce language

You can chooce the language. English and german are supported at this time.

2.2.2.4.3. Step 2 Read license

You can read the license. All code wich is shiped with this software is licensed under the GNU General Public License Version 2 (GNU GPL v2).

2.2.2.4.4. Step 3 Check config file

If the check runs ok you can go on to the next step.

2.2.2.4.5. Step 4 Database settings

Here you have to fill in the database settings of the allready created database (section "2.2.2.6. Configure mysql" of this document).

DB hostname: your database hostname, if it runs on the same host like the webserver leave that at localhost

DB user: the username to connect to the database

DB password: the password to connect to the database

DB name: the name of the database, the database have to be created before this step

DB type: The type of the database you want to connect

Tested databases:

MySQL

PostgreSQL

MS SQL

2.2.2.4.6. Step 5 Created tables

You see if all tables are created, if there are errors go back and check your database settings.

2.2.2.4.7. Step 6 Register functions

Functions registered. This is a security feature. You can go on.

2.2.2.4.8. Step 7 Add initial group

Add a initial group. Fields:

Name: The name of the group. This should not conatin whitespace or other special characters.

Comment: A short decription of the group.

2.2.2.4.9. Step 8 Add initial user

Add a initial user. Required fields:

Userid: The login-name of the user. This should not conatin whitespace or other special characters.

Username: The name of the user.

Main group: The main group of this user, only the group you have specified in step 7 should be available at this step.

Password: The password for the user.

Additional fields:

Phone: The users phone number.

Room: The users room number.

EMail: The users email.

2.2.2.4.10. Step 9 Installation end

If the user is created you can go on.

2.2.2.4.11. Step 10 Create laguages

All language settings are done, follow the white rabbit.

2.2.2.4.12. Ready

Installation done, you can proceed with login.

2.10. Modules

2.10.1. ssh_client

ssh_client

2.10.1.1. Description

This module manages your ssh hosts and give you the availability to acces the filesystem via ssh and run commands on the hosts. This is also used by some other modules to run commands on the specified hosts.

2.10.1.2. Installation

Simple install the module via settings->modules.

2.10.1.2.1. Configuration

Go to settings->modules->SSH Client->configuration:

SSH Libary: you can use the ssh commands or the phpseclib. The ssh commands are usable in linux and windows systems. The phpseclib is platform independent.

SSH paths: set the paths to the program files of the ssh, scp and ssh-keygen command, this is only needed if you use the setting "ssh commands" above. The webserver must be able to execute this commands.

2.10.1.2.2. Personal configuration

Go to usersettings->SSH:

Generate key: with this you can create a new private/public key pair.

Public key: this is your public key, you have to place this key into .ssh/authorized_keys of the users home directory on the host you want to connect to.

Secret key: this is your private key.

Shell background: the color of the shell background.

Shell font: the color of the shells font.

Stay connected for seconds: after this number of seconds you will be disconnected.

You can also upload you exsisting RSA private/public key pairs here. This will spend you the time if you ave allready deployed it to some hosts.

2.10.1.2.3. First connect to host

Use:

Name: the name of the remote host you want to connect to

IP address: the IP address of the remote host you want to connect to

Username: the Username on the remote host you want to connect to

to connect to a new host.

2.10.1.2.3.1. Host settings

After that you have to save the hosts public key:

You can manage your ssh hosts in this view.

2.10.1.3. SSH Shell

First connect with hostname (IP will be taken from the host table) and the username:

After connecting you can send commands to this host. This is not a comfortable shell like shellinabox but it is working for simple administrative tasks like restarting a service.

2.10.1.4. SSH Browser

First connect with hostname (IP will be taken from the host table) and the username:

In the ssh filebrowser you can:

Upload a file

Create a new Directory

Delete files and directories

Download files

Browse the entire tree

2.10.2. ldapmgr

ldapmgr

2.10.2.1. Description

The ldapmgr module is to manage your ldap server.

2.10.2.2. Installation

Simple install the module via settings->modules.

2.10.2.2.1. Configuration

2.10.2.2.1.1. Add new Server

Name: The name for your configuration. This should be a uniq name.

Hostname: The host name can be an IP, a DNS name or a LDAP URI.

Port: The port of the LDAP server.

Userattribute: The useratribute to search for the "Bind as user". The search will be run in each base DN with Userattribute=username. The username is taken from the login session.

Bind user DN: The user DN to bind to the LDAP server.

Bind user password : The password for the user DN to bind to the LDAP server.

Bind as user: If you want to bind as logged in user you have to choose this option. You also have to define the Userattribute.

LDAP referrals: Follow referrals.

Version: The LDAP version.

2.10.2.2.1.2. Base DNs

Set different Base DNs.

2.10.2.2.1.3. Templates

Define Templates to use for the specified LDAP server to add new entries.

2.10.2.2.1.4. Search configuration

Define the attributes for the global search.

2.10.2.2.2. Personal configuration

You have to install also the module usersettings ? to use this configuration.

start: Where to start if you access the ldapmgr module.

Base DN: The default base DN for the search. This can be configured for each server.

Search attribute: The default search attribute for the search.

Sort attribute: The default sort attribute for the search.

Search scope: The default scope for the search.

2.10.2.3. Ldap Manager

2.10.2.3.1. The menu

2.10.2.3.2. Tree view

The tree view. From here you can:

Enter the view entry

Enter the edit entry

Copy and move entries (with subentries) also from one server to an other

Delete entries (with subentries)

2.10.2.3.3. Search

Chooce the server you want to search. If you have set default variables for the choosen server in the usersettings ? you can directly start the search.

Base DN: The default base DN for the search.

Search attribute: The search attribute for the search.

Searchterm: The search term. You can use place holders in the search.

Sort attribute: The sort attribute for the search.

Search scope: The scope for the search.

On the right part of this view you will see the matched entries for your search.

2.10.2.3.4. New entry

First you have to choose a server. Then you can choose a template which you have defined in the configuration for this server.

2.10.2.3.5. Edit entry

2.10.2.3.6. View entry

2.10.2.3.7. Clear cache

The objectclasses and attributes will be cached in the current session. Accessing this link will clear the cache and force to read the attributes and objectclasses again.

2.10.3. licences

licences

2.10.3.1. Description

Controll and manage your liceces with this module.

2.10.3.2. Installation

Simple install the module via settings->modules.

2.10.3.2.1. Configuration

You can set if this module should:

Prevent installation of operating systems if assigned liceneces are expired/consumed

Prevent installation of software if assigned liceneces are expired/consumed

2.10.3.2.2. Licence types

This is for future use only. There are different rules which are currently only for informational use:

per user single licences per user

per client single licences per client

OEM ONE single licence per client

per processor single licences per processor

per core single licences per core

on demand licece single licences per use

network licece floating or concurrent licences

unlimited no limits

2.10.3.3. Usage

2.10.3.3.1. Licence groups

Licence groups are for grouping licences. You are able to add and remove licences to a group to extend or reduce the licence pool.

2.10.3.3.1.1. Add new licencegroup

First you have to add a licence group. Groups are needed for a licence. Every licence have to have a group.

Name The group name

Description A short description of the group

2.10.3.3.1.2. Show a single licencegroup

You can see the licence group and short description. From here you can edit this group, add operating systems and software versions to this group. You can also assign a single licence to a user.

2.10.3.3.1.3. Assign operating system to licence

Assign operating systems to a licence group:

Match assigned Select this to match this operating system to each assigned host

Match Inventory Select this to macth this operating system and version to each inventory set - search there for name and version or only the name

You have to define searchstrings into the fields name and version. Here some examples:

Search for Microsoft Office 2003 Professional: Use Name: "Microsoft Office Professional Edition 2003" and let the version empty

Search for every Acrobat Reader installation: use name: "%Adobe Reader%" and let the version empty

Use the fusioninventory module to find out the searchstings which best fit your needs.

2.10.3.3.1.4. Assign software to licence

Assign software to a licence group:

Match assigned Select this to match this software version to each assigned host

Match Inventory Select this to match this software version to each inventory set - search there for name and version or only the name

You have to define searchstrings into the fields name and version. Here some examples:

Search for Windows 2008R2: Use Name: "Microsoft Windows Server 2008 R2 Enterprise" and let the version empty (or use "6.1.7601")

Search for every SUSE Linux Enterprise Server installation: use name: "SUSE Linux Enterprise Server %" and let the version empty

Search for every SUSE Linux Enterprise Server 11 installation: use name: "SUSE Linux Enterprise Server 11%" and let the version empty

Search for every SUSE Linux Enterprise Server 11 SP1 installation: use name: "SUSE Linux Enterprise Server 11%" and use version: "2.6.32.%"

Use the fusioninventory module to find out the searchstings which best fit your needs.

2.10.3.3.1.5. Assign licence to a user

Assign a licence to a user is a manually entry. There is no automatic counter behind this.

2.10.3.3.1.6. show details on operating system matches

From here you can jump directly to the entry which matches this operating system.

2.10.3.3.1.7. show details on software matches

From here you can jump directly to the entry which matches this software.

2.10.3.3.2. Licences

2.10.3.3.2.1. Add new licence

A licence should at least have a expire date and the licence count. The licence will be assigned to a group. The group can be assigned to operating systems and to softwareversions.

Name The name

Description A short description

Producer The producer of this software/licence

Supplier The supplier

Supplydate The date the licence have been supplied

Account info Account informations if you have an account to manage this licence

Account date The date the account was added

Licence info Additional licence informations

Licence count Licence count

Type The type of the licence

Groups The licence group this licence should belong to

Licence expiration When the licence will expire

Comment A comment

Contact info A name who can be asked in context with this licence

Operating system The operating system this licence is for

Product key The product key associated with this licence

2.10.3.3.2.2. Show licences

List your licences here. You can filer, group and sort the entries.

2.10.3.3.3. Mediums

Mediums are optional. You can use this to manage all your CDs, DVDs, isos and so on.

2.10.3.3.3.1. Show mediums

Name The name

Description A short description

Medium type The type of the medium e.g. iso, CD or other

Operating system The operating system this medium is for

Language The language of the software on this medium

Mediumcount The medium count

Location Where the medium is located

Licences Assign licences to this medium

Contact A name who can be asked in context with this medium

Archived Select to mark this medium as archived

List your mediums here. You can filer, group and sort the entries.

2.10.4. Settings

Settings

2.10.4.1. Description

This module gives you the availability to modify your userdefined settings. So each user can have its own language, theme and so on. There are also some module specified settings which can be controlled from here. It is highly recommended to install this module.

2.10.4.1.1. Installation

Simple install the module via settings->modules.

2.10.5. dns_ldap

dns_ldap

2.10.5.1. Description

The dns_ldap module is to manage your DNS entries in your ldap database.

2.10.5.2. Installation

Simple install the module via settings->modules.

2.10.6. locations

locations

2.10.6.1. Description

The locations module is to manage your locations.

2.10.6.2. Installation

Simple install the module via settings->modules.

2.10.7. samhain

samhain

2.10.7.1. Description

This module manages the main yule database and configuration for samhain. Also it is possible to deploy samhain to each host.

2.10.7.2. Quick start:

For the functionality of remote installation, database update and commands you need the ssh module installed. At this time only ssh-key authentification is supported.

2.10.7.2.1. Configure your Yule Server

This is only an example!

./configure \
--enable-static \
--enable-network=server \
--with-database=mysql \
--enable-xml-log \
--with-sender= \
--with-recipient=  \
--enable-udp \
--with-trusted=

You should use --with-trusted= if you want to use this module to send messages through yulectl and if you want remote installation.

2.10.7.2.2. Remote installation

!!!THE FOLLOWING STEPS ARE ONLY NEEDED IF YOU WANT TO DO REMOTE UPDATE/INSTALLATION!!! Be sure you do the following after the "make"-stuff:

create a group for yule

be sure the daemon (or the user which runs yule) and the webserver-user is member of this group

chown daemon:yule /etc/yulerc

chmod 660 /etc/yulerc

chown -R daemon:yule /var/lib/yule/

chmod 770 /var/lib/yule/

chmod 660 /varlib/yule/[f|r]*

Configure your Samhain Packages:

./configure \
--enable-login-watch \
--enable-mounts-check \
--enable-static  \
--enable-suidcheck  \
--with-config-file=REQ_FROM_SERVER/etc/samhainrc \
--with-data-file=REQ_FROM_SERVER/var/lib/samhain/samhain_file \
--with-logserver= \
--enable-network=client \
--enable-xml-log \
--enable-userfiles

Now you can build several packages with make run|rpm|.... At this time only the linux packages run, rpm and deb (untested) are supported. Make a directory "install" in your yule data dir e.g: /var/lib/yule/install/ and take care that the webserver has read access to this directory and the files. Here you have to place your packages.

2.10.8. switch

switch

2.10.8.1. Description

This module manages your switches. You can use it to document your network topologie.

2.10.8.2. Installation

Simple install the module via settings->modules.

2.10.9. PXE

PXE

2.10.9.1. Description

The PXE module is to manage your PXE entries and control which image a computer has to boot.

2.10.9.2. Installation

Simple install the module via settings->modules.

2.10.9.3. TFTP Server configuration

DHCP options to get use of the pxe files: * filename pxelinux.0 * next-server IP.OF.THE.TFTP-SERVER
Use the path /PATH/TO/URANOS/www/modules/pxe/pxeroot as the root of your tftp server.

2.10.9.3.1. tftpd.remap

The file /PATH/TO/URANOS/www/modules/pxe/pxeroot/tftpd.remap (shipped with uranos) is only needed if you want to start WinPE over PXE.

2.10.9.3.2. TFTP Server config example

apt-get install tftpd-hpa

Here is an example for ubuntu /etc/default/tftpd-hpa:

-l -s /PATH/TO/URANOS/www/modules/pxe/pxeroot -m /PATH/TO/URANOS/www/modules/pxe/pxeroot/tftpd.remap

2.10.10. cal

cal

2.10.10.1. Description

Controll and manage your calendars and events, submitted by the modules, with this module.

2.10.10.2. Installation

Simple install the module via settings->modules.

2.10.11. Computer

Computer

2.10.11.1. Description

The computer module is to manage computer inventory and configuration for software, partitioning and os. Also its the main entry point for the connectors.

2.10.11.2. Installation

Simple install the module via settings->modules.

2.10.11.2.1. Configuration

Path to ping: The full path to the ping command.

Options for ping before HOST: The options for ping to use before the hostname.

Options for ping after HOST: The options for ping to use after the hostname.

Path to nmap: The full path to nmap. This should be used with root permissions: /usr/bin/sudo /usr/bin/nmap. (e.g. /etc/sudoers: www-data ALL=(ALL) NOPASSWD: /usr/bin/nmap) See the sudo man page for more information how to run a command without a password. This command is used to import hosts.

Path to net (on windows path to psexec.exe): The full path to the net command (from the samba suite). On windows you can use psexec for that. This command is used to shut down a host.

Use psexec.exe: Check this option if you want to use psexec.exe on windows.

2.10.11.2.2. Personal configuration

You have to install also the module usersettings to use this configuration.

Show software versions: If you check this option you are able to see the software versions in the software configuration tab for the computer.

Show contents from packages: If you check this option you are able to see the contents of the packages in the software configuration tab for the computer.

Enable ping: If you check this option the host will be checked via ping (see settings above).

Enable ping in overview: If you check this option all hosts in the overview will be checked via ping (see settings above).

Expiration of the ping-validity in seconds: After this count of seconds the validity of the ping will expire and the host will be pinged again.

Configuration CSV: The configuration for the export to csv.

Columns enclosed by: This option defines the enclosure sign for the single columns.

Columns seperated by: This option defines the seperate sign for the columns.

Columns escaped by: This option defines the escape sign for the columns.

Newline: The newline seperator.

First line is descriptor: Check this option if you want to have a descriptor in the first line of the csv export.

2.10.11.2.3. The menu

start search: You can use this to submit your entered search condition. Your search will be stored in your session and you will have your last search available each time you go back to the computer module.

delete search: This will delete your search from your session.

Systems: Use this to go the computer view.

New systems: Use this to go to the arp entries / automatic fetch network devices view.

New system: Use this link to add a new host.

Searchgroups: Here you can manage your searchgroups.

New searchgroup: Use this link to add a new searchgroup.

Import: Here you can access the different import methods.

2.10.11.3. Computer view

Filter: In this view you are able to make a short filter of the hosts. Chooce "all" to display all hosts. Or use a-z to display only the hosts which begins with the letter you chooce.

Ping: If you have enabled ping in overview (see Personal configuration) you are able to see if the host is reachable (green) via the ping command.

Name, Virtuell machine on host, Macadress, IP adress, Inventorynumber, Main group, Main user, Room: Inventory Informations.

Options: From here you are able to edit, clone and delete a host. Also you can access the print view from here.

Entries found: / Export: You can see the entries you have found via the filter or the search in the menu. You can export this list by clicking the link "Export". See CSV configuration in the personal configuration.

Search: From the menu you can search. You will get this view only if there are more than one entries found. Else you will be redirected to the single computer view.

2.10.11.3.1. Arp entries / automatic fetch network devices

To get the arp entries into your databases you have to run arpwatch on one [or more] host[s].

Start arpwatch on each of your networks: arpwatch -N -n 192.168.0.0/24 -n 10.0.0.0/8 (for options see the arpwatch man page)

To automatic add the entries you have the option to install the cron module and activate the arp-to-db cron. See more on the help page of the cron module.

The other option is to add the cron script (www/modules/cron/defaultcrons/arp_to_db.txt) directly to your crontab. Simple copy the file and make it executeable.

In both cases you have to set the following variables:

$arpwatchfile="/var/lib/arpwatch/arp.dat";
$stripdomain_from_dnsname=".example.com";
$INCexternal="/PATH/TO/uranos/www/include/INCexternal.php";

$arpwatchfile is the full path to the arpwatch database.

$stripdomain_from_dnsname is your domain name - normaly arpwatch add the hosts FQDN to the database, but you might want to only see the names.

$INCexternal is the full path to the INCexternal.php.

after runnning the cron_to_db script you will see the entries like shown in this example:

Search: From the top menu you can search.

Filter: In this view you are able to make a short filter of the hosts. Chooce "all" to display all hosts. Or use a-z to display only the hosts which begins with the letter you chooce.

Options: From here you are able to add the host to your inventory.

Name, Macadress, IP adress, Time, Options are the informations which are added into the database from the arp database.

2.10.11.3.2. Add a new computer

To add a new computer you can use the "New system" link in the menu, the above described method from arp entries, the later described import methods or the inventory profile from the boot stuff.
If you use the "New system" link you will get this form:

Name: This is the name of the machine. You should use dns confirm names here.

Virtuell machine on host: The name of the virtual machine which host this machine.

Macadress: The main mac address. Enter a valid mac address in the form 00:11:22:33:44:55.

Macadress 2: 2. mac address. Enter a valid mac address in the form 00:11:22:33:44:55.

Macadress 3: 3. mac address. Enter a valid mac address in the form 00:11:22:33:44:55.

Macadress 4: 4. mac address. Enter a valid mac address in the form 00:11:22:33:44:55.

Macadress WLAN: Wlan mac address. Enter a valid mac address in the form 00:11:22:33:44:55.

Macadress WLAN2: Wlan 2. mac address. Enter a valid mac address in the form 00:11:22:33:44:55.

Macadress BLUETOOTH: Bluetoth mac address. Enter a valid mac address in the form 00:11:22:33:44:55.

IP adress: IP Address

IP adress 2: 2. IP Address

Description: A short description for the machine.

Serialnumber: Serial number.

Servicetag: Service TAG.

Inventorynumber: Inventory number.

Producer: Producer.

Supplier: Supplier.

Supplydate: Supplydate (day.month.year)

Warrenty: Warrenty till (day.month.year)

Group: The main group where the machine belongs to.

Main user: The main user where the machine belongs to.

Room: A room number (helpful with the locations module).

Comment: A comment.

You have to provide at least the macaddress and the name.

2.10.11.3.2.1. Import

You can import from the following sources. The clear cache means that the entries which were read from the specified source will be removed from cache and you can run the import again.
On every import you will get an overview and you can decide what to do:

adding new entries

modify entries

delete entries

2.10.11.3.2.1.1. Import LDAP

Base DN The base DN, the search will be started from there.

Bind DN The full bind DN - if you need a user to bind to the LDAP.

Bind password The password for the bind DN - if you need a user to bind to the LDAP.

Hostname The hostname of the ldap server. This can also be an IP address.

Port The port of the ldap server (normaly 389).

Objectclass The objectclass to search for.

You can define which ldap attribute has to be assigned to which field in the database after saving the above settings. After defining the attributes you can run the update and go to the next step.
2.10.11.3.2.1.2. Import CSV

Columns enclosed by The character which enclose each data colmun.

Columns seperated by The character which seperates each data colmun.

First line is descriptor Check this option if the first line of your file is only a description.

Filename The csv file you want to import.

You can define which field from the file has to be assigned to which field in the database after saving the above settings. After defining the filename and the fields you can run the update and go to the next step.
2.10.11.3.2.1.3. Import PING

Path to ping The full path to the ping command.

Options for ping before HOST Options for bing before the hostname.

Options for ping after HOST Options for bing after the hostname.

Network The network address.

Networkmask The networkmask in CIDR. E.g. 24 (255.255.255.0) or 28 (255.255.255.128)

After defining the network and networkmask you can run the update and go to the next step.
2.10.11.3.2.1.4. Import NMAP

Path to nmap Full path to nmap. You should use sudo (%www ALL=NOPASSWD:/usr/bin/nmap) to run nmap. If you use sudo you should set this to: "/usr/bin/sudo /usr/bin/nmap".

Network The network address.

Networkmask The networkmask in CIDR. E.g. 24 (255.255.255.0) or 28 (255.255.255.128)

After defining the network and networkmask you can run the update and go to the next step.

2.10.11.3.2.2. Add from arp entries

You can add entries directly from the arp table.

Use the link from Options to add the host to the systems database.

2.10.11.3.3. Single computer view

This is the main view of a computer. Splitted into 3 sections. The main entry point for the connectors on the left side (green) is only displayed if you chooce Inventory informations from the main menu on the top (blue). The 3. Section is the content of the specified connector. If you configure the computer you will not see the connector entry points.

In the red section are the same options you have in the computer view.

Options: From here you are able to edit, clone and delete a host. Also you can access the print view from here.

2.10.11.3.4. Operating systems

To add a new operating system you have to configure the operating systems in the unattended module. After that you can chooce one os from the list:

After you have add an os, you can make special settings to this os which only affects this host. You are able to override the default settings from the unattended module. You can access this settings by clicking on the Content button right of the os.

After you have set up the partitioning you can see the produced answer file by clicking the link to view output.

2.10.11.3.5. Partitioning

To add a new harddisk layout you have to configure the layouts in the unattended module. After that you can chooce one layout from the list:

Harddisk configuration The reference layout you have configured in the unattended module.

Harddisk type The type of the hard disk. For ATA/IDE devices this will be hdX and for SCSI/SATA devices you have to chooce sdX.

Replace mbr If you check this option the mbr will be replaced by your layout.

By clicking on the Content button you are able to configure the main parts of the layout, e.g. format partition or the mount points.

Type Primary, extended or locical partition.

Number The number of the device.

Boot The boot flag.

Size The Size of the partition.

Filesystem The filesystem of the partition.

Mount point The mount point, this is only needed if you install a linux distribution.

mount point OS The mount pint operating system, this is only needed if you install one or more linux distribution[s].

root OS The root operating system. This is the / (root) for linux or the %SystemDrive% for windows. Chooce here your configured operating system.

format Check this option if you want to format this partition.

2.10.11.3.6. Software and packages

To set up software to a computer you are able to assign packages, software and software versions in this section. If you want to see the versions and/or the contents of the packages you may set the options in the computer section of the usersettings module.

2.10.11.3.6.1. Packages

To add a package you only have to check the add option right of the package name.

The package will not assign the software, you will see the installed software only after the software is installed. You will get this result:

2.10.11.3.6.2. Software

To add a software you only have to check the add option right of the software name. You can also add a specified version if you dont want to add the latest stable version. In each time you specify only the software - the latest stable version of the os language will be installed.

Here is an example how it looks if a software is installed. This software is inherit from the userinstallation, see more in the documentation of the software module.

You can also chooce that the installed version will not be affected by the updates:

2.10.11.3.7. PXE

If you have assigned the operating system to a PXE menuentry the pxe entry will be set automaticly for each defined mac address from this host. See more in the documentation of the pxe module.

2.10.11.3.8. Reset

You can easy reset the hosts configuration, for example you want to reinstall it (e.g. after a hard disk crash) or if you want to replay the installation to a clear state.

Packages You can delete all assigned packages from the configuration.

Software Reset means that the install status will be set to install. If you chooce delete all assigned software will be removed from the configuration.

Software versions Reset means that the install status will be set to install. If you chooce delete all assigned software versions will be removed from the configuration. This is recommended because in the next install the latest stable version will be installed.

Partitioning Reset means that all partitions becomes the format flag and the replace mbr will be set to true again. Delete will remove each assigned partition layout from the configuration.

Operating system Reset the status of each installed operating system. Delete will remove each assigned operating system from the configuration.

2.10.11.3.9. Power on/off WOL

You can send a WOL package to your broadcast address to the selected mac address:

Macaddress The mac address you want to set the WOL package.

Broadcast address The broadcast address of your network.

You can also sht down the host over the network. You have to set up the correct paths to the net (from the samba suite) command or on windows hosts to the psexec.exe. See more in the main computer configuration above.

Timeout A timeout after this count of seconds the host will be shut down.

Comment A comment which is displayed to a looged in user.

Username The username which is allowed to shut down this host.

Password The password of the username which is allowed to shut down this host.

Reboot Check this option if you want a reboot insted of a shutdown.

2.10.11.3.10. Clone a computer

To clone a computer means that you make an exact copy of the configuration and the inventory informations from a computer. If you clone a computer you will have the same operating system, partitioning and software configuration on the new host, so you only need to update the inventory informations and then you can start the installation.

2.10.11.4. Searchgroups

The power of the searchgroups is that you are able to automate the operating system and software installations to a specified set of hosts. You can assign a reference system which is preconfigured.

2.10.11.4.1. Add a new searchgroup

To add a new searchgroup you have to click the link new searchgroup from the main menu.

Searchgroup The name of the searchgroup. Only use charachters from a-Z and _ because a view will be generated with this name.

Reference system Chooce a preconfigured reference system. This configuration will be assigned to each host of this searchgroup after the host will fetch the configuration.

2.10.11.4.2. Add a new definition to a searchgroup

To add a new definition use the add new definition under options.

You can build up your definition as you want. Use % as a search term from mysql. For example:

%apple% will find: pineapple, Applejuice and also pineapplejuise

apple% will find: all terms beginning with apple, e.g. Applejuice but also only apple

%apple will find: all terms ending with apple, e.g. pineapple but also only apple

If you use place holders you have to define LIKE. Each term you can connect to the next term via and or or.
You can also define more than one definition to a search group. The different definitions can be combined with and or or.

2.10.11.4.3. Overview of a searchgroup

If you take a look into a searchgroup you will see all affected hosts on the left side. If the host has no configuration you will see a green ok. If there is a red attention on a column, this host has allready a configuration. You can click the red attention to see the configuration. On the right side you see the configuration of the reference system.

2.10.12. Software

Software

2.10.12.1. Description

The software module is to manage software descriptions/installations.

2.10.12.2. Installation

Simple install the module via settings->modules.

2.10.12.2.1. Configuration

Temporary directory for creating the iso files. This directory will be used to generate the iso files.

Package directory (your z-mount directory). This directory is the base for your packages. Normaly this should point to ....z/packages.

Directory to store the iso files. This directory will be used to store the produced iso files.

2.10.12.2.2. User configuration

You need to have the usersettings module installed to see this options.

Direct copy versions. If you set this the software versions will be copied directly without the string replace question.

Default repository. This is the default repository which is choosen to add new software.

Default filter. Here you can set the ID, Repository and Software for your default filter. If you access the softwarelist this is the default filter.

2.10.12.3. Repositories

Repositories are to manage logical and global definitions of software. Here you can set:

Repository: This is the name of the repository, this should be uniq to avoid problems with external repositories.

Repository location: The location of the repository is only needed when you want to synchronize this from an external repository. The name of the repository have to be the same like the external repository.

Location of repository distfiles: This is for future use. This will be needed if you want to do http/ftp installations.

Location of local repository distfiles: This is for future use. This will be needed if you want to do http/ftp installations and synchronize the files to your local storage.

Type: External means that this is an external repository (you can synchronize software from the defined "Repository location"). Internal is only for internal use, this repository will not be able to get synchornized from other locations. Export is for marking a repository as exportable. You will be able to provide this repository for other users to synchonize if you set this to export.

Example to sychronize the repository "win-non-oss" from uranos.sourceforge.net:

2.10.12.4. Software

Software is the main name for the software you want to add. Here you can only define metadata:

Software: The name of the software.

URL: The link to the software provider.

Priority: Priority defines the order to install this software. Higher values will be installed later.

Comment: Here you can add additionally informations.

Repository: Define in which repository the software should be listed.

Example for the acrobat reader:

2.10.12.4.1. Software versions

Software versions define the different versions of a software. Here you can specify all the needed informations for install, check, download, uninstall and so on.

2.10.12.5. Packages

A package is to group software for a special language.

2.10.12.6. User

Here you can assign software to a user.

2.10.12.7. Groups

Here you can assign software to a group.

2.10.12.8. Winupdates

Here you can upload a scan from z/bin/scanwinupdates.js. This script will check if there are new updates are available and output them. You can redirect the output to a file:

cscript /nologo z:binscanwinupdates.js > z:updatesupdatescan-%COMPUTERNAME%.xml

After that you can upload the file in this GUI. Set the vars which will affect the newly generated software and versions.

2.10.13. syslog_ng

syslog_ng

2.10.13.1. Description

This module manages your syslog-ng servers, including configuration and databases.

2.10.13.1.1. Syslog-ng Documentation

Syslog-ng admin guide

2.10.13.2. Installation

Simple install the module via settings->modules. You will also need at least one database and one syslog-ng server (all can run on the same host).

2.10.13.2.1. Configuration

Go to settings->modules->Syslog-ng->configuration:

color: you can set the color for each priority.

live search: Time in miliseconds after the live search will be send after a key is pressed.

2.10.13.2.2. Personal configuration

Go to usersettings->Syslog-ng:

Activate live search: activate this if you want to use the live filter.

Show entries: how much entries should be displayed per page.

2.10.13.3. Layout

This module is designed to manage different databases on differnt hosts and provide a search over all tables on each database. It is also possible to manage and configure more than one syslog-ng server. In the basic setup you can run the database, the syslog server and also uranos on the same host. But you can also run it on different hosts. Some examples following.

A simple layout with 1 syslog server and 1 database:

A simple layout with 1 syslog server and 2 databases:

A simple layout with 2 syslog server and 2 databases:

2.10.13.4. Syslog configuration

2.10.13.4.1. Add a new server

First you have to add a new server:

You have to configure this server, with the same name and IP setting in the SSH client module because the configuration is transfered via ssh to the server. Also the reload (or restart, stop and start) commands are sended via ssh.

2.10.13.4.2. Add a new database

You need at least one database to add tables as destination for syslog messages:

2.10.13.4.3. Add a new table (destination)

Add a table to a database to hav a new destination for syslog messages.

After creating a table you have a new destionation configured to use:

2.10.13.4.4. Create new config

Please reffer to the syslog-ng documentation to get more information about the configuration.

2.10.13.4.4.1. Add new source

Chooce a name and Source:

After create a new source you can edit it.

Example for external source:

udp(); tcp(max-connections(100));

Example for internal source:

internal(); unix-stream("/dev/log"); file("/proc/kmsg" log_prefix("kernel: "));

2.10.13.4.4.2. Add new filter

After create a new filter you can edit it.

2.10.13.4.4.3. Add new destination

After create a new destination you can edit it.

2.10.13.4.4.4. Combine config for a server

The global options have to be defined per server:

Chooce a name to add a new log entry:

2.10.13.4.4.4.1. Add destination to log A destination is required for a log entry:

2.10.13.4.4.4.2. Add source to log A source is required for a log entry:

2.10.13.4.4.4.3. Add filter to log A filter is not required but should also be added to a log entry:

2.10.13.4.5. View and write config

View the config for this server:

Write config:

Restart syslog: chooce this option if you want to send a reload to the syslog-ng after writing the config.

2.10.13.4.6. Server commands

You can send the following commands to the server:

Reload

Stop

Start

Restart

2.10.13.4.7. Logs

The logs are stored in tables. You can view and search each table.

2.10.13.4.7.1. View the logs

Show table: chooce the table to view.

Sorting: sort the entries by clicking on the fieldname.

Pagelinks: go to special page.

Entries found: count entries matching the current filter.

Group entries: group the entries to dont show the same massage more than one time.

2.10.13.4.7.2. Filter the logs

Positive Filter: match the [sub]string.

Negative Filter: starting with "!" will show all entries which do not match the [sub]string.

2.10.13.4.7.3. Global search around all tables and all databases

2.10.13.4.8. Statistic

2.10.13.4.9. Statistic Graph

2.10.13.5. Rotate the tables:

When you have more than one table it will be better to use an own database for the old logs and rotate them every ... create a database (eg. syslog_old) crate a user which has access to write to he database: GRANT ALL PRIVILEGES ON syslog_old.* TO USERNAME@'localhost' IDENTIFIED BY 'PASSWORD';
If you want to rotate the tables you can use this script (example):

#!/bin/bash
# ATTANTION THIS SCRIPT WILL ROTATE ALL TABLES IN THE GIVEN DB
SQLHOST=localhost
SQLUSER=USERNAME
SQLPASS=PASSWORD
SQLDB=syslog
SQLOLDDB=syslog_old
TIMESTAMP=`date +%Y-%m-%d-%H%M`
TEMPNAME=_tmp_table

mysql -h $SQLHOST -u $SQLUSER --password=$SQLPASS $SQLDB -e "SHOW TABLES;" > /tmp/.tablelist
if [ "$?" -eq "0" ]
        then
        for TABLE in `cat /tmp/.tablelist`
        do
                mysql -h $SQLHOST -u $SQLUSER --password=$SQLPASS $SQLDB -e "DESCRIBE $TABLE;" > /dev/null 2>&1
                if [ "$?" -eq "0" ]
                        then
                        #if describe runs fine the table exists
                        # first we create the new table
                        mysql -h $SQLHOST -u $SQLUSER --password=$SQLPASS $SQLDB -e "CREATE TABLE 
                         `$SQLDB`.`$TABLE$TEMPNAME`(`host` varchar(32) default NULL,`source_ip` 
                          varchar(32) default NULL, `facility` varchar(10) default NULL,`priority` 
                          varchar(10) default NULL,`tag` varchar(10) default NULL,`unixtime` 
                          varchar(20) default NULL, `program` varchar(15) default NULL, 
                          `msg` text,`seq` bigint(20) unsigned NOT NULL auto_increment, 
                          PRIMARY KEY  (`seq`),KEY `host` (`host`), KEY `program` 
                          (`program`),KEY `priority` (`priority`),KEY `facility` (`facility`));"
                        if [ "$?" -eq 0 ]
                                then
                                # now we have the new table and can start renaming
                                mysql -h $SQLHOST -u $SQLUSER --password=$SQLPASS $SQLDB 
                                -e "ALTER TABLE `$TABLE` RENAME `$TABLE$TEMPNAME$TIMESTAMP`; 
                                ALTER TABLE `$TABLE$TEMPNAME` RENAME `$TABLE`;"
                                if [ "$?" -eq 0 ]
                                        then
                                        #all renaming runs fine now we can safely work with the data
                                        mysql -h $SQLHOST -u $SQLUSER --password=$SQLPASS $SQLOLDDB 
                                        -e "CREATE TABLE `$SQLOLDDB`.`$TABLE$TIMESTAMP`( 
                                        `host` varchar(32) default NULL, 
                                        `source_ip` varchar(32) default NULL, 
                                        `facility` varchar(10) default NULL, 
                                        `priority` varchar(10) default NULL, 
                                        `tag` varchar(10) default NULL, 
                                        `unixtime` varchar(20) default NULL, 
                                        `program` varchar(15) default NULL, 
                                        `msg` text, 
                                        `seq` bigint(20) unsigned NOT NULL auto_increment, 
                                        PRIMARY KEY  (`seq`),KEY `host` (`host`), 
                                        KEY `program` (`program`), 
                                        KEY `priority` (`priority`), 
                                        KEY `facility` (`facility`));"
                                        mysql -h $SQLHOST -u $SQLUSER --password=$SQLPASS  $SQLOLDDB 
                                        -e "INSERT INTO `$SQLOLDDB`.`$TABLE$TIMESTAMP` 
                                        SELECT * FROM `$SQLDB`.`$TABLE$TEMPNAME$TIMESTAMP`;"
                                        mysql -h $SQLHOST -u $SQLUSER --password=$SQLPASS $SQLDB 
                                        -e "DROP TABLE `$TABLE$TEMPNAME$TIMESTAMP`;"
                                else
                                        echo "error renaming tables from $TABLE"
                                        exit 3
                                fi
                        else
                                echo "error creating $TABLE$TEMPNAME"
                                exit 2
                        fi
                fi
        done
else
        echo "error in db connection"
        exit 1
fi

2.10.13.6. Clear old syslog entries

If you want to delete old entries (e.g. older than 1 week) you can use this script (example):

#!/bin/bash
# ATTANTION THIS SCRIPT WILL CLEAR ALL TABLES IN THE GIVEN DB
SQLHOST=localhost
SQLUSER=USERNAME
SQLPASS=PASSWORD
SQLDB=syslog
TIMESTAMP=`date +%s`
DELETESPAN=604800
DELETETIMESTSAMP=$((TIMESTAMP-DELETESPAN))

mysql -h $SQLHOST -u $SQLUSER --password=$SQLPASS $SQLDB -e "SHOW TABLES;" > /tmp/.tablelist
if [ "$?" -eq "0" ]
                then
                for TABLE in `cat /tmp/.tablelist`
                do
                                mysql -h $SQLHOST -u $SQLUSER --password=$SQLPASS $SQLDB -e "DESCRIBE $TABLE;" > /dev/null 2>&1
                                if [ "$?" -eq "0" ]
                                                then
                                                #if describe runs fine the table exists
                                                # first we create the new table
                                                mysql -h $SQLHOST -u $SQLUSER --password=$SQLPASS $SQLDB -e "DELETE FROM 
                                                 `${SQLDB}`.`${TABLE}` WHERE unixtime<${DELETETIMESTSAMP};"
                                                if [ "$?" -eq 0 ]
                                                then
                                                        echo "${SQLDB} ${TABLE} cleared"
                                                        mysql -h $SQLHOST -u $SQLUSER --password=$SQLPASS $SQLDB -e "OPTIMIZE TABLE `${SQLDB}`.`${TABLE}`;"
                                                else
                                                        echo "${SQLDB} ${TABLE} failed"
                                                fi
                                fi
                done
else
                echo "error in db connection"
                exit 1
fi

2.10.14. dhcp_ldap

dhcp_ldap

2.10.14.1. Description

The dhcp_ldap module is to manage your DHCP entries in your ldap database.

2.10.14.2. Installation

Simple install the module via settings->modules.

2.10.15. Inventory

Inventory

2.10.15.1. Description

The fusioninventory module is the server part of the fusioninventory agent.

2.10.15.2. Installation

Simple install the module via settings->modules.

2.10.15.3. Usage

If you install the fusioninventory agent you have to specify the following:

Username / Password

Realm

URI

You have to set up a user which should be specified during the installation / configuration part of the agent. You can set the realm in the configuration page in settings->modules->fusioninventory. The URI has to be in this form:

http[s]://YOURSERVER/PATH/www/modules/fusioninventory/controller.php

It is recommended to use the https protocol to protect your username/password.

2.10.15.4. Settings

2.10.15.4.1. Global module settings

Number of hours between two runs of the agent.

Add host to database if no entry exist

Delete old inventory sets from older clients

Automatic assign inventory to host

Save xml files

Path to save XML files

Realm

Time in miliseconds after the live search will be send

2.10.15.4.2. User settings

Activate live search

Entries per page

2.10.16. cron

cron

2.10.16.1. Description

The cron module is to manage cron scripts in one database.

2.10.16.2. Installation

Simple install the module via settings->modules. After that you have a set of default crons in the database.

2.10.16.3. Install on clients

2.10.16.3.1. Run the container Script via scheduled task on Windows systems

Simple add the curl files and the container.cmd into the %WINDIR% directory and add a scheduled task (in this case it runs every 5 minutes):

schtasks /create /sc minute /mo 5 /ru "System" /tn "container-script uranos" /tr "%WINDIR%container.cmd"

2.10.17. Search

2.10.17.1. Description

The search module is the main entry point for each module and connector search. With the help of this module you are able to search each module and connector which provides a search interface.

2.10.17.2. Installation

Simple install the module via settings->modules.

2.10.18. Wiki

Wiki

2.10.18.1. Description

The quwiki module is to manage the documentation of this software and your own documentation in an easy to use format.

2.10.18.2. Installation

Simple install the module via settings->modules.
Use the "Generate documentation" to regenerate the documentation of this software.

2.10.19. radius_ldap

radius_ldap

2.10.19.1. Description

With this module you can manage different VLANs for mac-based-vlan from LDAP.

2.10.19.2. Setup freeradius

2.10.19.2.1. radiusd.conf

authorize {
        attr_filter
        #auth_log
        #set AUTH Type
        #rewrite to normal mac address with no delimiter to compare with username
        rewrite_calling_station_id_no
        if(User-Name =~ /^%{Calling-Station-ID}$/i){
                #rewrite to normal : mac address
                rewrite_calling_station_id_normal
                update control {
                        Auth-Type = 'LDAPMAC'
                }
                update request {
                        User-Name := "%{Calling-Station-ID}"
                        }
                ldap-macaddress {
                        notfound = reject
                }
        }
}
authenticate {
        Auth-Type LDAPMAC {
                #return ok no bind as user is required
                ok
        }
}
#this section is to post the logs into a file which will be parsed to the database
post-auth {
        #sqlok
        Post-Auth-Type REJECT {
                attr_filter.access_reject
                #sqlfailed
        }
}

2.10.19.2.2. Functions to rewrite mac-address

Include the file via $INCLUDE rewritemac.conf in your radiusd.conf:

#
# Rewrite called station id attribute into a standard format.
#
policy {
	rewrite_calling_station_id_no {
		if(request:Calling-Station-Id =~ 
			/([0-9a-f]{2})[-:]?([0-9a-f]{2})[-:]?([0-9a-f]{2})[-:]?([0-9a-f]{2})[-:]?([0-9a-f]{2})[-:]?([0-9a-f]{2})/i){
			update request {
				Calling-Station-Id := "%{1}%{2}%{3}%{4}%{5}%{6}"
			}
		}
		else {
			noop
		}
	}
	rewrite_calling_station_id_normal {
		if(request:Calling-Station-Id =~ 
			/([0-9a-f]{2})[-:]?([0-9a-f]{2})[-:]?([0-9a-f]{2})[-:]?([0-9a-f]{2})[-:]?([0-9a-f]{2})[-:]?([0-9a-f]{2})/i){
			update request {
				Calling-Station-Id := "%{1}:%{2}:%{3}:%{4}:%{5}:%{6}"
			}
		}
		else {
			noop
		}
	}
}

2.10.19.2.3. ldap configuration

contents of file: modules/ldap

ldap ldap-macaddress {
        server = "ldap.example.com"
        #ldap_debug = 0x0028
        identity = "cn=radius,ou=DSN,dc=example,dc=com"
        password = verysecret
        basedn = "o=radius,dc=example,dc=com"
        base_filter = "(objectclass=radiusObjectProfile)"
        filter = "(radiuscallingstationid=%u)"
        access_attr_used_for_allow = yes
        access_attr = "radiusTunnelPrivateGroupId"
        port = 636
        set_auth_type = no
        tls_require_cert = "never"
        dictionary_mapping = ${raddbdir}/ldap.attrmap
        ldap_connections_number = 5
        timeout = 5
        timelimit = 3
        net_timeout = 2
}

2.10.19.2.4. log configuration

The modules/sql_log should contain 2 sections, one for failed and one for ok:

sql_log sqlfailed {
	path = "${radacctdir}/sql-relay"
	postlog_table = radiuslog
	utf8 = yes
	Post-Auth = "INSERT INTO ${postlog_table} 
				(callingstationid,nasipaddress,logtime,nasipport,username,failed) 
				VALUES ('%{Calling-Station-Id}','%{NAS-IP-Address}','%S','%{NAS-Port}',
				'%{User-Name}',1) ON DUPLICATE KEY UPDATE nasipaddress=VALUES(nasipaddress), 
				nasipport=VALUES(nasipport), logtime=VALUES(logtime), failed=VALUES(failed);"
}
sql_log sqlok {
	path = "${radacctdir}/sql-relay"
	postlog_table = radiuslog
	utf8 = yes
	Post-Auth = "INSERT INTO ${postlog_table} 
				(callingstationid,nasipaddress,logtime,nasipport,username,failed) 
				VALUES ('%{Calling-Station-Id}','%{NAS-IP-Address}','%S','%{NAS-Port}',
				'%{User-Name}',0) ON DUPLICATE KEY UPDATE nasipaddress=VALUES(nasipaddress), 
				nasipport=VALUES(nasipport), logtime=VALUES(logtime), failed=VALUES(failed);"
}

After that you could add the log entries to the post-auth section of radiusd.conf:

post-auth {
        sqlok
        Post-Auth-Type REJECT {
                attr_filter.access_reject
                sqlfailed
        }
}

2.10.19.3. Deploy logs to database

After you have installed the module you have a table called radiuslog Here is the script which deploy the log to the database:

#!/bin/bash
#Main settings
LOGFILE=/var/log/freeradius/radacct/sql-relay
DB_TABLE=radiuslog
DB=uranos
DB_USER=uranos-dbuser
DB_PASS=verysecret
DB_FILE=/tmp/radiussql.$$
DB_HOST=mysql.example.com

#copy logfile
cp $LOGFILE $DB_FILE
#empty log
cat /dev/null > $LOGFILE

mysql -u $DB_USER -h $DB_HOST --password=$DB_PASS $DB < $DB_FILE

#at last remove logfile
rm $DB_FILE

You can run this script via a cron job.
Altenativ you can run the radsqlrelay perl script which is deployed with freeradius.

radsqlrelay -d mysql -b uranos -h mysql.example.com -u uranos-dbuser -p verysecret /var/log/freeradius/radacct/sql-relay

2.10.20. Installation

Installation

2.10.20.1. Description

The unattended module is to manage harddisks and os installations through templates.

2.10.20.2. Installation

Simple install the module via settings->modules.

2.10.20.2.1. Get harddisk and os templates

You can import the os templates and harddisk templates from a local file, or from the sourceforge.net side.
Local import:

Remote import:

2.10.20.2.2. Prepare Operating system

After importing the templates you can configure the operating systems you want:

2.10.20.2.2.1. Create os

Name: The name of the operating system.

OS temapltes: The template you want to use (e.g for windows XP chooce "Windows - XP")

Comment: An optional comment to identify the configured tempalte.

2.10.20.2.2.2. Configure os

After you have create an os you can configure it and make your settings. The settings you made here will override the default settings from the template.

Press Content to get to the settings of this os.

On the left side you can go to each section. On the right side you can set the values of the differnt keys. If you chooce Dont use this key via the checkbox right of the key value this key will not be used. If all keys from one section will be disabled the section will not appear in later settings. You can use the following placeholders which will be replaced by the specified key from the inventory information of a system:

###MAC### first macaddress

###MAC2### second macaddress

###MAC3### third macaddress

###MAC4### fourth macaddress

###WLAN### first wlan macaddress

###WLAN2### second wlan macaddress

###BLUETOOTH### bluetooth macaddress

###IP### first IP address

###IP2### second IP address

###COMPUTERNAME### the computer name

###MAIN_USER### the uid from the main user

###SUPPLIER### the supplier

###SUPPLYDATE### the supplydate

###SERIAL### the serial number

###PRODUCER### the producer

###DESCRIPTION### the desription

###SERVICETAG### the servicetag

###INVENTORY### the inventory number

###WARRENTY### the warrentydate

###ROOM### the room number

###COMMENT### the comment

2.10.20.2.3. info.txt

In each folder in z/os/ you should hold an info.txt:

PRODUCT: The name of the product (e.g. Windows7|Vista|XP|...)
SERVICEPACK: The servcie pack (e.g. 2)
PRODUCTLANG: The main language of the product (e.g. en-EN)
ARCH: The architekture (x86 or x86_64)
ISO: If you want to use an iso file (only valid for FILETYPE=0 and FILETYPE=wim) set the filename here.
You have to create an iso directory in the same directory where the iso file is located, e.g. /z/os/winxp/iso.
You also have to set the FILE to the correct filename - e.g. iso/sources/install.wim.
ISOTYPE: udf|iso9660 the filesystem on the ISO file, normaly udf for DVDs and iso9660 for CDs
FILE: The complete path to the file, or if FILETYPE=0 you can leave this empty or if FILELOC=0
only the filename (e.g. xp.tar.bz2 or vista.dd.bz2 or http://example.com/file.bz2)
FILELOC: Filelocation can be 0 for this directory or 1 for http/ftp 2 for multicast
FILESIZE: The original size of the Disk/Partition, this is only (optional) needed for images,
clones and partimages. A suffix of "k", "m", "g", or "t" can be added to denote kilobytes (*1024),
megabytes, and so on.
FILETYPE: Filetype can be:
0 = standard installation files
tar.gz = tar.gz compressed install files
tar.bz2 = tar.bz2 compressed install files
tar.7z = tar install files compressed with 7z
7z = install files packed and compressed with 7z
wim = default windows image format
image = uncompressed dd image
image.gz = gzipped dd image
image.bz2 = bziped dd image
image.7z = dd image compressed with 7z
partimage = partition dd image
partimage.gz = gzipped partition dd image
partimage.bz2 = bziped partition dd image
partimage.7z = partition dd image compressed with 7z
clone.TYPE = filesystem-clone
clone.TYPE.gz = gzipped filesystem-clone
clone.TYPE.bz2 = bziped filesystem-clone
clone.TYPE.7z = filesystem-clone compressed with 7z
DRIVERDIR: The directory which holds the dirvers for the os. This directory will be copied
to the root of the operating system. This only affect to Windows operating systems.
DRIVERDIR_SCANDRIVERS: Scan DRIVERDIR for *.inf files which contain the following:
-> if DRIVERDIR_SCANDRIVERS: VENDORID -> copy only directories which contains *.inf files
that matches the vendorid
-> if DRIVERDIR_SCANDRIVERS: DEVICEID -> copy only directories which contains *.inf files
that matches the vendorid and the deviceid
For Windows XP the OEM_PNP_DRIVERPATH will be set automatically via the script.
In Windows Vista, 7 and 2008 you have to set the DRIVERPATH to %SystemDrive%drv_s
DRIVERDIR_SCANDRIVERS_COPY_SUBDIRS: If this option is set also the Subdirectories from a matched DRIVERDIR
is copied. This can be helpful if the inf files are not in the same directory like the driver files.
DRIVERPACKSDIR: (normaly /z/drivers/driverpacks/) The directory which holds the compressed
(currently only 7z is implemented) dirvers for the os.
This files will be extract to the root of the operating system to the directory D/.
This only affect to Windows operating systems.
You can place your own files there with the following limitations:
Directory: /z/drivers/driverpacks/xp is for os W2000,W2003 and XP
/z/drivers/driverpacks/vista ist for Vista, 2008 and 7 (each ARCH)
ARCH: The files in the directory must conatin the ARCH e.g. DP_Chipset_wnt6-x64_10071.7z
(here the x64 will match)
For Windows XP the OEM_PNP_DRIVERPATH will be set automatically via the script and are extracted
to %SystemDrive%D.
In Windows Vista, 7 and 2008 you have to set the DRIVERPATH to %SystemDrive%Driverpacks see:
http://technet.microsoft.com/en-us/library/cc766485%28WS.10%29.aspx.
DRIVER_PATH_TO_LONG_QUESTION: Specify the answer to the question when the path of the OEM_PNP_DRIVER_PATH
is to long when installing W2K, XP or 2003
UDPRECEIVEROPTS: The options passed to udp-reciever, you can specify:
log file
Logs some stuff into file.
nokbd
Do not read start signal from keyboard, and do not display any
message telling the user to press any key to start.
start-timeout sec
receiver aborts at start if it doesn't see a sender within this
many seconds. Furthermore, the sender needs to start transmission
of data within this delay. Once transmission is started, the timeout
no longer applies.
portbase portbase
Default ports to use for udpcast. Two ports are used: portbase and
portbase+1 . Thus, Portbase must be even. Default is 9000. The same
portbase must be specified for both udp-sender and udp-receiver.
ttl ttl
Time to live for connection request packet (by default connection
request is broadcast to the LAN's broadcast address. If ttl is set,
the connection request is multicast instead to 224.0.0.1 with the given
ttl, which should enable udpcast to work between LANs. Not tested though.
mcast-rdv-address address
Uses a non-standard multicast address for the control connection
(which is used by the sender and receivers to "find" each other).
This is not the address that is used to transfer the data. By default
mcast-rdv-address is the Ethernet broadcast address if ttl is 1, and
224.0.0.1 otherwise. This setting should not be used except in very
special situations, such as when 224.0.0.1 cannot be used for policy reasons.
exit-wait milliseconds
When transmission is over, receiver will wait for this time after
receiving the final REQACK. This is done in order to guard against
loss of the final ACK. Is 500 milliseconds by default.
nosync
Do not open target in synchronous mode. This is the default when
writing to a file or a pipe.
sync
Write to target in synchronous mode. This is the default when
writing to a device (character or block)

2.10.20.3. Operating systems

2.10.20.3.1. Install methods

2.10.20.3.1.1. Directly

Installing directly from source you only have to copy the install files to z/os.
You should have there always an info.txt in the directory. For example here is one for windows XP:

PRODUCT: XP
SERVICEPACK: 3
PRODUCTLANG: en-EN 
ARCH: x86
FILELOC: 0

For all linux distributions you can use your own mirror or an mirror outside. This depends on the distribution. In most cases you can specify the location of your source in the answer file.
If you have problems to mount the z share case insensitiv you have to rename all the files in i386/ to lowercase.
Here is an example for an folder structure:

z/os/xpdesp3/i386 <- this is the directory which contains the contents of the installation CD

z/os/xpdesp3/info.txt <- the info file

z/os/xpdesp3-packed/xpdesp3.tar.bz2 <- this is the file which contains the contents of the installation CD

z/os/xpdesp3-packed/info.txt <- the info file

z/os/xpensp1x64/amd64 <- this is the directory which contains the contents of the installation CD

z/os/xpensp1x64/i386 <- this is the directory which contains the contents of the installation CD

z/os/xpensp1x64/info.txt <- the info file

It is possible to hold the contents of the cd in a compressed form. The following archives are supported:

tar.gz = tar.gz compressed install files

tar.bz2 = tar.bz2 compressed install files

2.10.20.3.1.2. Image

Installing/publish an image gives you the possibility to install/restore nearly all operating systems you want. Simple place the image in an extra folder in z/os. See the section info.txt for setting up the info.txt file.

2.10.20.3.1.3. Transfermodes

There are different transfer modes for the installationfiles which are specified by "FILELOC". FILELOC can be 0 for standard installation files, these files will be transfered directly from the mounted volume (normaly cifs).

Example:

FILE: file.tar.bz2
FILELOC: 0

If you want to transfer the files from ftp/http you have to set FILELOC: 1 and give the url in FILE parameter.

Example:

FILE: http://example.com/file.tar.bz2
FILELOC: 1

If you set FILELOC to 2, multicast is used to transfer the file. If you have specified more than one sender, you have to set the correct UDPRECEIVEROPTS.

Example:

FILE: file.tar.bz2
FILELOC: 2
UDPRECEIVEROPTS: --log /var/log/udp-receiver.log --portbase 8500 --nokbd --sync

On the server side the udp-sender have to run. For more informations take a look into the command line description of udpcast.

2.10.20.3.2. Windows

You can access the unattended.[txt|xml] file via this http://YOURSERVER/external.php?function=install_os&computer=COMPUTERNAME side with the browser, or:

wget -O unattend.txt http://YOURSERVER/external.php?function=install_os&computer=COMPUTERNAME

to save the informations to a file. The boot-cd contains a script which controls the complete setup for windows include getting this file.

2.10.20.3.2.1. Windows 2000/XP/2003

For this versions you can use both install methods. Simple copy the content of your installation CD into an folder in z/os:

z/os/xpdesp3/i386 <- this is the directory which contains the contents of the installation CD

z/os/xpdesp3/info.txt <- the info file

You can also pack the i386 [and amd64 for XP-64bit] directory to speed up the installation over slow networks:

z/os/xpdesp3-packed/xpdesp3.tar.bz2 <- this is the file which contains the contents of the installation CD

z/os/xpdesp3-packed/info.txt <- the info file

This can be done by running the command:

tar cjpf xpdesp3.tar.bz2 i386/

2.10.20.3.2.2. Windows Vista/2008/Windows7

2.10.20.3.2.2.1. Install method wim file You can use your prepared install file or the original from the install DVD. Simple place the file into a subdirectory in z/os:

z/os/win7-de-x86/install.wim <- this is the wim file from the DVD

z/os/win7-de-x86/info.txt <- the info file

The info file should contain at least:

PRODUCT: Windows7
SERVICEPACK: 0
PRODUCTLANG: de-DE
ARCH: x86
FILE: install.wim
FILELOC: 0
FILETYPE: wim

set the wim_index in your answer file (_meta section).

The wim_index will indicate what product you want to install from the wim.
You dont need to add drivers to the wim, check out the info.txt how to add drivers during the installation. If you have an audit section in your answer file (uranos default) the audit mode (with is searching for and install drivers) will run first. Read more here: http://technet.microsoft.com/en-us/library/hh824920.aspx#bkmk_4
Here are some links to add drivers to the wim (if you want to do so):

http://technet.microsoft.com/en-us/library/cc766141%28WS.10%29.aspx

http://superuser.com/questions/63773/how-to-add-drivers-to-windows-7-installation-dvd

You can also build a new wim file from a pre configured machine. See section 3.2.2.2. for prepartion and run after that (from the boot environment)

 imagex capture /dev/hda1 (chooce the right partition where your installation is located) /z/os/MYWINXXX/install.wim IMAGE_NAME DESCRIPTION --compress=maximum

2.10.20.3.2.2.2. Install method ntfscloneThe installation proccess of this versions is always an image installation. For installing this versions via unattended and the ntfsclone method you have to prepare it in the following way:

Make a clean vista/7/2008 installation (we suggest to use a 15-20GB partition) - install servicepacks and / or updates if you want.

Activate the administrator account.

Log off if you are not in the administartor account.

Delete the files from the user and the user account itself.

Install ServicePacks (optional). (USE c:\Windows\System32\vsp1cln.exe /verbose for cleaning up SP1 installation backup files and c:\Windows\System32\compcln.exe for cleaning up SP2 installation backup files and DISM.exe /online /Cleanup-Image /spsuperseded /hidesp on W2k8 R2 SP1)

Install software (optional). This is not recommended because of to stay up to date with the programs.

Personalize the administrators desktop (optional).

Install your MAK (optional).

Set the IDE controller driver to \"Standard IDE Controller\" - this is normaly done by the /generalize pass, but we need the generalize pass later (see "How it works")

Check if the Start Reg_Word in HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Msahci is set to 0 http://support.microsoft.com/kb/922976/en-us

At last run the command: %WINDIR%\system32\sysprep\sysprep.exe /audit /shutdown

2.10.20.3.2.2.2.1. Save a ntfsclone

Boot into boot-cd

Save the image to an mounted volume:

 ntfsclone -s -o /z/os/vista-x86-SP2/vista-x86-SP2-de.clone.ntfs /dev/hda1

Optional you can zip or bzip it

bzip2 /z/os/vista-x86-SP2/vista-x86-SP2-de.clone.ntfs

At last create the info.txt. For this example:

PRODUCT: Vista
SERVICEPACK: 1
PRODUCTLANG: de-DE
ARCH: x86
FILE: vista-x86-SP2-de.clone.ntfs.bz2
FILELOC: 0
FILETYPE: clone.ntfs.bz2
FILESIZE: 11000m

2.10.20.3.2.2.2.2. Save a partimage via dd

Boot into boot-cd

Save the image to an mounted volume:

dd if=/dev/hda1 of=/z/os/vista-x86-SP2/vista-x86-SP2-de.partimage

Optional you can zip or bzip it

bzip2 /z/os/vista-x86-SP2/vista-x86-SP2-de.partimage

or run it as one command:

dd if=/dev/hda1 | bzip2 - > /z/os/vista-x86-SP2/vista-x86-SP2-de.partimage.bz2

At last create the info.txt. For this example:

PRODUCT: Vista
SERVICEPACK: 1
PRODUCTLANG: de-DE
ARCH: x86
FILE: vista-x86-SP2-de.partimage.bz2
FILELOC: 0
FILETYPE: partimage.bz2
FILESIZE: 15000m

2.10.20.3.2.2.2.3. How it works:

next time the machine boots into the auditSystem pass of windows setup to set the admin password, enable autologon and to add drivers

after that the auditUser pass runs sysprep /generalize /oobe /reboot command to go to the specialize and oobe part of the answer file

the specialize part is to activate the admin account, set computer name, ProductKey and JoinDomain or JoinWorkgroup

at last the oobeSystem part sets all other infos, install software via postinst.js and activate Windows

2.10.20.3.2.2.3. Windows error codeshttp://msdn.microsoft.com/en-us/library/ms681381%28v=VS.85%29.aspx

2.10.20.3.3. Kickstart

Uranos can also produce kickstart files. The following distribution use kickstart and there is a template for each. To use the answer file you can add this line to the kernel append to boot the installation:

ks=http://YOURSERVER/external.php?function=install_os

You should add also the ksdevice and ip:

ksdevice=eth0 ip=dhcp ks=http://YOURSERVER/external.php?function=install_os

You could also specify a static ip configuration: [[code#:mem=512M quiet ksdevice=eth0 ip=10.0.0.10 netmask=255.255.255.0 gateway=10.0.0.1 nameserver=10.10.0.2]]

2.10.20.3.4. Presseed

Uranos can also produce presseed files. The following distribution use presseeding and there is a template for each. To use the answer file you can add this line to the kernel append to boot the installation:

auto=true priority=critical console-setup/layoutcode=de  locale=de_DE url=http://YOURSERVER/external.php?function=install_os --

2.10.20.3.4.1. Debian

Web: http://www.debian.org/

2.10.20.3.4.2. Ubuntu

Web: http://www.ubuntu.com/

To get use of the partition settings you have to disable the following entries in the template:

Auto partitioning

Auto partitioning device

Auto partitioning recipes

Auto partitioning own recipes

If you use a stitic ip configuration you have to add:

killall.sh; netcfg

in the early script.

2.10.20.3.5. openSuSE/SLES

Web (SLES): http://www.novell.com/de-de/products/server/

Web (openSuSE): http://opensuse.org/

Uranos can also produce xml files for SLES and OpenSuSE. To use the answer file you can add this line to the kernel append to boot the installation:

autoyast=http://YOURSERVER/external.php?function=install_os

2.11. Connectors

2.11.1.

doc:connectors:ocsinventory_ng:help

2.11.1.1. Description

This connector will search your OCS database for the computername and display the results.

2.11.1.2. Installation

Simple install the connector via settings->connectors.

2.11.1.3. Configuration

You can reach the configuration in the main settings module in the connectors section. There is a "Configuration" link behind the conncetor if the connector is installed.

Hostname the hostname where ocsinventory server is located.

Username the user to access the ocsinventory server.

Password the password for the user to access the ocsinventory server.

The hostname will be used to generate the links to access the soap interface:

http://HOSTNAME/Apache/Ocsinventory/Interface

http://HOSTNAME/ocsinterface

For more informations check the documentation of OCS:

http://wiki.ocsinventory-ng.org/index.php/Developers:Web_services

http://www.ocsinventory-ng.org/index.php?mact=News,cntnt01,detail,0&cntnt01articleid=98&cntnt01returnid=80

2.11.1.4. Usage

After configure your os inventory server will be searched for this hostname.

2.11.2.

doc:connectors:rt:help

2.11.2.1. Description

Connect your RT http://bestpractical.com/rt/ database. This connector will search your RT database for the current computername to display all requests.

2.11.2.2. Installation

Simple install the connector via settings->connectors.

2.11.2.3. Configuration

You can reach the configuration in the main settings module in the connectors section. There is a "Configuration" link behind the conncetor if the connector is installed.

Database user the user to access the rt database.

Database password the password for the database user to access the rt database.

Database host the hostname where the rt database is located.

Link to rt host link to your request tracker host. This link will be used to generate links to the tickets.

2.11.2.4. Usage

After configure you should see all tickets found in the rt database:

You can click on the Ticket ID or the Subject to go directly to the ticket.

2.11.3.

doc:connectors:dns_ldap:help

2.11.3.1. Description

Manage DNS entries for the systems.

2.11.3.2. Installation

Simple install the connector via settings->connectors. You will need also the dns_ldap module installed.

2.11.4.

doc:connectors:remotecmd:help

2.11.4.1. Description

Specify and run remote commands. You can run remote commands on ssh enabled hosts (module ssh_client needed) and on windows machines.

2.11.4.2. Installation

Simple install the connector via settings->connectors. You will need also the ssh_client and computer module installed.

2.11.4.3. Configuration

In the main configuration you have to set the path to psexec.exe on windows systems. On Linux set the path to winexe.

Path to winexe (on windows path to psexec.exe): Full path to winexe/psexec

winexe/psexec options: Options for the command psexec: use -s to run it on the system account winexe: --interactive=0 --system to run it on the system account --uninstall to remove the service after execution

2.11.4.3.1. Configure credentials

Name: Uniq name of the credentials

Username: The remote username to run the command

Password: The password for the remote user - for ssh you have to provide the username which ssh keys should be used

You can view, edit and delete the credentials from this view:

2.11.4.3.2. Configure commands

Name: Uniq name of the command

Type: Choose if this is a ssh or winexe/psexec command

Default credentilas: Choose the default credentials to use with this command

Command: The contents of the command

Here is an example to use the scanwinupdates.js to scan hosts for updates:

@echo off
IF EXIST z: net use z: /DELETE
net use z: \\ntinstall\install secretpassword /USER:DOMAIN\user
cscript /nologo z:\bin\scanwinupdates.js > z:\updates\scans\%COMPUTERNAME%.xml
net use z: /DELETE

You can view, edit and delete the commands from this view:

2.11.4.3.3. Logs

You can view and delete the logs from this view.

2.11.4.4. Usage

2.11.4.4.1. Run command from the connector

Simple choose the command and press "run". This will execute the selected command with the default credentials for this command. If you want to use your own credentials choose the entry "Use own credentials" and set your username and your password. If you want to run an ssh command with your own credentials you have to set the username to the remote users name (e.g. root) - you dont need to specify a password because the ssh command will use your ssh_keys.

2.11.4.4.2. Run commands via cron / script

Here is an example script which runs commandid 3 with the default credentials on host: host.example.com

#!/usr/bin/php5 -f
<?php
//global settings
$INCexternal="/var/www/install/uranos-svnroot/www/include/INCexternal.php";
//require system
require_once ($INCexternal);

ini_set ('display_errors',true);
ini_set ('display_startup_errors',true);
error_reporting(E_ALL^E_NOTICE);

if (!require_connector_file('remotecmd','connector.php'))
                {
                exit;
                }
$host='host.example.com';
$out=remotecmd_run($host,3);
echo "* command executed on host $host:n";
echo $out['command'];
echo "n";
if ($ret['stat']==0)
        {
        echo "* command run with exit state 0n";
        }
else
        {
        echo "* command failed with exit state ".$ret['stat']."n";
        }
echo "* Output:n";
if (is_array($out['out']))
        {
        foreach ($out['out'] as $o)
                {
                echo $o."n";
                }
        }
?>

Here is an example to run a command on each host in group "example" with username and password:

#!/usr/bin/php5 -f
<?php
//global settings
$INCexternal="/var/www/install/uranos-svnroot/www/include/INCexternal.php";
//require system
require_once ($INCexternal);
//required for the getGROUPCOMPUTERS
$INCuser="/var/www/install/uranos-svnroot/www/include/APIuser.php";
require_once ($INCuser);
ini_set ('display_errors',true);
ini_set ('display_startup_errors',true);
error_reporting(E_ALL^E_NOTICE);

if (!require_connector_file('remotecmd','connector.php'))
                {
                exit;
                }
//Select hosts the groupid is the id of the group
$groupid=2;
$examplehosts=getGROUPCOMPUTERS($groupid);
if (is_array($examplehosts['entries']))
	{
	foreach ($examplehosts['entries'] as $h)
		{
		$host=$h['computername'];
		$out=remotecmd_run($host,3,"Adminsitrator","seCret");
		echo "* command executed on host $host:n";
		echo $out['command'];
		echo "n";
		if ($ret['stat']==0)
		        {
		        echo "* command run with exit state 0n";
		        }
		else
		        {
		        echo "* command failed with exit state ".$ret['stat']."n";
		        }
		echo "* Output:n";
		if (is_array($out['out']))
		        {
		        foreach ($out['out'] as $o)
		                {
		                echo $o."n";
		                }
		        }
		}
	}
?>

2.11.5.

doc:connectors:dhcp_ldap:help

2.11.5.1. Description

Manage IP addresses for each macaddress from the system.

2.11.5.2. Installation

Simple install the connector via settings->connectors. You will need also the dhcp_ldap module installed.

2.11.5.3. Configuration

Please check the settings of the dhcp_ldap module.

2.11.5.4. Usage

You can add an IP address for each macaddress - if you need also with specified options:

2.11.6. Inventory

Inventory

2.11.6.1. Description

View your inventory for this system.

2.11.6.2. Installation

Simple install the connector via settings->connectors. You will need also the fusioninventory module installed.

2.11.6.3. Configuration

Please check the settings of the fusioninventory module.

2.11.6.4. Usage

If the hostname is found you can assign one or more fusioninventory hardware-id[s] to this host. You have a link to each section on the top of this connector:

In the sections you see the keys and values:

2.11.7.

doc:connectors:cron:help

2.11.7.1. Description

If you install this connector you will be able to add cron scripts to each system.

2.11.7.2. Installation

Simple install the connector via settings->connectors. This connector requires the cron module.

2.11.7.3. Configuration

See the cron module configuration.

2.11.7.4. Usage

2.11.8.

doc:connectors:systemnetwork:help

2.11.8.1. Description

If you install this connector you will be able to see the arp entries and network infos from the switch.

2.11.8.2. Installation

Simple install the connector via settings->connectors. You also need the cron and the switch module to view all infos.

2.11.8.3. Configuration

You can reach the configuration for cron via the module configuration. The cron module is used to add the entries from the arpwatch database. The switch module will give you the availability to locate this host on the switchport and if configured you will see the room where this host is currently attatched.

2.11.8.4. Usage

After configure should view the last entries from the arp. This view will be generated by searching the systems_arp table for each mac address assigned to this host:

This is the view of a network port where one macaddress is found:

2.11.9.

doc:connectors:radius_ldap:help

2.11.9.1. Description

Assign a VLAN to each mac address from each system.

2.11.9.2. Installation

Simple install the connector via settings->connectors. You will need also the radius_ldap module installed.

2.11.10.

doc:connectors:bugzilla:help

2.11.10.1. Description

Connect your BUGZilla database. This connector will search your bugzilla database for the current computername to display all requests.

2.11.10.2. Installation

Simple install the connector via settings->connectors.

2.11.10.3. Configuration

You can reach the configuration in the main settings module in the connectors section. There is a "Configuration" link behind the conncetor if the connector is installed.

Database user the user to access the bugzilla database.

Database password the password for the database user to access the bugzilla database.

Database host the hostname where the bugzilla database is located.

Link to bugzilla host link to your bugzilla host. This link will be used to generate links to the tickets.

Comma seperated list of fields to search define which fileds should be searched for the computer name.

2.11.10.4. Usage

After configure you should see all tickets matching defined searchfileds:

You can click on the Ticket ID or the Subject to go directly to the ticket.

2.11.11.

doc:connectors:checklist:help

2.11.11.1. Description

Generate your own checklists. This can be assigned to each system and be processed from different users.

2.11.11.2. Installation

Simple install the connector via settings->connectors.

2.11.11.3. Configuration

You can reach the configuration in the main settings module in the connectors section. There is a "Configuration" link behind the conncetor if the connector is installed.
Add a new check-list:

Name: Chooce a name for the check-list.

Comment: Add a comment for the check-list.

Edit content to edit and add parts to the check-list.

Add new ckeckfield to add a new part to the check-list.

You can also edit single parts of the check-list:

2.11.11.4. Usage

In the computer view you have to chooce the Checklists connnector:

You can add more than one checklist to an computer. You only can delete the already assigned check-list if you have the permissions to do that. After adding a check list you can run the checks by clicking the *edit* button behind the assigned check-list.

Add your comments and check the part of the check-list behind the comment field to approve this part of the check-list.

After that you see the user and the time when this part of the check-list was approved:

2.11.12.

doc:connectors:comments:help

2.11.12.1. Description

If you install this connector you will be able to add comments to each system.

2.11.12.2. Installation

Simple install the connector via settings->connectors.

2.11.12.3. Configuration

There is no need for a configuration.

2.11.12.4. Usage

In the computer view you have to chooce the Comments connnector. After that you can add a new comment:

You see all comments and comments of comments in a date ordered view:

You can comment, edit and delete a comment.

2.11.13.

doc:connectors:ldaphosts:help

2.11.13.1. Description

This connector will search your LDAP database for the computername and display the results.

2.11.13.2. Installation

Simple install the connector via settings->connectors.

2.11.13.3. Configuration

You can reach the configuration in the main settings module in the connectors section. There is a "Configuration" link behind the conncetor if the connector is installed.

User the user DN to connect to the ldapserver, leave empty if anonymouse bind is wanted.

Password the password for the user DN.

Host the hostname of the ldap server.

BaseDN the base DN, the search will be performed in the base of this DN.

Port the port of the ldap server.

Entry name the attr name for the DN to search, e.g. cn.

Search samba host the base DN for search samba host entries.

2.11.13.4. Usage

After configure your ldap server will be searched for the hostname.
Here is an example of an ipHost:

Here is an example of an Samba host:

3. Changelog

Changelog

3.1. Changelog

3.1.723. Computer Release: 723

start to realize import

oid vendors update

3.1.728. Computer Ping and Memory Release: 728

Options for check if computer is alive (ping)

Correct wrong display of memory in connector memory

3.1.751. LDAP / Software Release: 751

Improve LDAP, works now also with SunONE

fixed bug #1958618

fixed software to install more than 1 version from a software

software configuration for default filter and default repository

3.1.763. Computer Release: 763

Added new cfg to computer

added feature Request #1960939

3.1.777. Ldap Auth Computer Import Release: 777

LDAP Auth change option to search for user before bind # need for MSAD

added feature to sync computer from cvs,ldap,pingscan or nmapscan

added feature request #1955324 Templates: turn off sections and keys

added feature request #1948582 configure config.php through webserver

3.1.793. Feature Requests/Bugs Release: 793

added feature request #1955324 Templates: turn off sections and keys

solved bug 2077978

3.1.804. New Theme Release: 804

improved ajax / js theme -> panther-improved

3.1.808. Computer Release: 808

Resolved BUG computer import -> delete failed

Alter table unattended_systems -> add second ip field

3.1.809. HTML Release: 809

error in html page

3.1.818. Switch Release: 818

Switch uplink dedection

Feature request #2189970

3.1.830. Switch port management Release: 830

Alter table unattended_patch_panel_ports -> add x and y coordinates for the image

Alter table unattended_switch_ports -> add x and y coordinates for the image + add uplink_switch_id to define uplink ports

Alter table unattended_switch -> add portsize for the image removed portoffset

Alter table unattended_switch_slots -> add portoffset

Alter table unattended_patch_panel -> add portsize

3.1.875. Software Bug Release: 875

resolved bug with installing packages

3.1.892. PXE Release: 892

PXE bugs resolved

3.1.899. New release Release: 892

Jump to release 1.892

3.1.908. APIssh Feature Request #2355852 Release: 908

new API ssh -> based on ssh command

Search for samba hosts Feature Requests 2355852

3.1.911. Feature Request #2256096 Release: 911

Deployment of one or more software-packages to a group of computers at the same time

3.1.913. Feature Request #2355821 Release: 913

Feature Request 2355821 Deployment of one or more software-packages to a group of computers at the same time

3.1.920. API shh Release: 920

new API ssh -> based on ssh command

3.1.927. Feature Request #2540495 Release: 927

Feature Requests 2540495 -> use proxy

3.1.931. Syslog Release: 931

update syslog to use new ssh API

3.1.1020. New modules Release: 1020

new module dns_ldap to manage dns entries for ISC bind

new connector dns_ldap

new API for wiki and new module quwiki (needed also to view documentation)

update networkinfo

new connector for bugzilla Feature Requests #2595396

Added feature to send WoL packages (testet) in local networks via the braodcast address - Feature Requests #2633043

3.1.1030. Bugfixes and inventory profile Release: 1030

Bug #2694842 and #2697842 DHCP backup broken because of update to client

added new table for module computer to display the lspci output

added new inventory profile to auto add machines and add some basic info to the database

3.1.1088. Add support for Vista/2008/Windows7 and ubuntu Release: 1088

Major changes:

added support installation for Vista/2008/Windows7

added support for installation of ubuntu (at this time there is only a template for ubuntu-server)

new profiles for easy backup and restore machines

Bug Fixes:

2733850 Error in external/functions.php

2711475 multiple default hard disks

2711466 mesage_start function doesn't line up

2709080 initial OEP partion of 4gb no loonger enough

2697948 7za binary on boot disk is not statcally compiled

2697842 DHCP kill line doesn't specify interface in /etc/master

2694842 DHCP backup broken because of update to client

3.1.1116. New logo Release: 1116

update boot stuff to 1.2

added new logo to each theme

correct script errors, this could lead into non booting systems

3.1.1121. Multicast installations Release: 1121

added feature request:2057160 multicast of installation files

3.1.1128. Documentation Release: 1128

added feature request 2801177 copy os definitions

added feature request 2807603 7z for install files (untestet)

added ubuntu 9.04 desktop template

updated documentation

3.1.1134. BUG fixes Release: 1134

minor BUG fixes

added feature request:2805462 new status for failed installations

3.1.1144. Feature requests Release: 1144

added feature request:debug of software installation - ID: 2802880

added feature request:chooce software from boot environment ID: 2818017

3.1.1216. BUG fix php 5.3 compatibiliy Release: 1216

BUG ID: 2824292 import compares now the mac address -> namp options --system-dns

move forward to compatibility with php 5.3.0

FR:2821683 and 2840071 2545037 installations based on userconfig

BUG in computer vhost management

3.1.1350. Release update Release: 1350

Fixed several BUGS

Added several Feature Requests

added multiside support -> simple add an alias to your apache configuration (you will need a default installation which controls the update):

Alias /anotherside /var/www/uranos After adding the alias you can access the install.php on the alias directory

Improved LDAP Manager: added support for multi server, multi base configuration, copy entries (with subentries) from one server to an other

Improved switch management

updated panther-improved theme for better view

update syslog-ng module - now the programm /usr/bin/mysql is used to insert logs

3.1.1357. Feature requests Release: 1357

Settings port FR #2944688

Add packages direct as software FR #2937257

Displayversion as check condition FR #2937257

3.1.1372. Feature requests Release: 1372

Show rollout status for computers FR #2882162

Add software to computergroups FR #2882152

FR 2907442 install only software from packages which reqires no userlogon if the service is running

3.1.1378. BUG fixes Release: 1378

Software download via GUI is now possible

Making isos of software - now supports Windows and DVDs by size greater than 800MB

3.1.1382. Feature requests Release: 1382

FR #2952375 Specifying the unattended file on the kernel cmdline

fixed BUG in external_check_all_sw_command

3.1.1386. BUG fixes Release: 1386

use wget.exe instead wget.js

BUG in filter status - fixed

readded radius auth

3.1.1395. BUG fixes Release: 1395

check shouldnt run if there is no one - but it should be send the installed to the server

replaced contact in each module/connector

Fixed BUG #2953790

3.1.1402. BUG fixes Release: 1402

FR #2958631 show versions only with -a or -A

added xml2array function

Fixed BUG with wemerge --check

3.1.1149. Feature requests Release: 1149

added feature request:shutdown ID: 2818017

bootcd update

3.1.1151. BUG fix Release: 1151

BUG ID: 2824292 import compares now the mac address -> namp options --system-dns

3.1.1456. Fusioninventory Release: 1456

Now install Vista/7/2008 can be done direcly. See the docs for more information

New module and conncetor fusioninventory

added Licencemanagement but it is not ready!!!

3.1.1675. first release of uranos

Fusioninventory: auto delete old entries, auto add to database, auto assign entries

Software is now able to handle also other os like linux and osx

Software versions can now depend on arch, os and os version

Licencemanagement usable

Added free text parser

Quwiki possible to generate Latex code for pdflatex

3.1.1689. BUG fixes

fixed BUG with licence count

fixed BUG #3140598 Delete a license

moved copy PXE entries to the correct place

fixed driverpacks download page

fixed BUG installing unattended module

3.1.1721. BUG fixes, Feature Requests

added DRIVER_PATH_TO_LONG_QUESTION -> #FR 3147476 Driverpacks: Path to long question

FR #3134122 add ip address in answer file for all windows templates

Added Localboot 0 to PXE -> PLEASE UPDATE your settings to use -1 or 0!!!

#FR 3160114 -> add placeholders to the answer files which replace values from the systems table

3.1.1742. BUG fixes, documentation

fixed BUG #3236747 wemerge mlultiple problems

Resolved BUG add new language

Resolved BUG 3234551 computergroups

xml2array moved to API.php (BUG in ocsinventory_ng)

update docs

3.1.1770. New Release

DRIVERSCAN: Scan also alsa devices in /proc for vendor and device. This will only work with boot cd version greater or equal than 1.6.0.

Feature requests: #3141184 Licence groups

Feature requests: #3140725 Add Hostnames on Licensepage

Feature requests: #3138017 Copy Licenses and Medias

added new theme: uranos

new logo

Driverpacks download fixed

3.1.1777. New Theme

Fixed REGEDIT64 BUG

Added new theme

3.1.1786. BUG fixes

Connector network: removed old table from search

BUG deleting module unattended

Fixed APIssh BUG, userkeys not used

3.1.1799. Syslog-ng 3.x compatibility

Better Support for Active Directory in ldap Manager

Make syslog-ng compatible with 3.x

Boot cd 1.7.0 release

fixed AUTHLdap BUG

3.1.1813. pChart

Build switch dependencies with the help of LLDP(Link Layer Discovery Protocol) via SNMP

Show switch dependencies in a map

replaced SLES/OpenSuse parser

Added Template for SLES 11

replaced APIGraph with pChart

added dir for tmp ssh files

resolved BUG with empty space in %TEMP% var

Added interface to sync repositories via cron script

3.1.1824. System tables

renamed tables user to x_user and groups to x_groups

solved #FR3285112 Add licence files

only update LLDP dependencies in switch module if there is some info on snmp

3.1.1831. Ubuntu 11.04 Template

added template for ubuntu 11.04

better pgsql compatibility (not 100% ready yet)

well form macadress function update

resolved BUG: STRING and HEX-STRING difference in som MIBs

3.1.1913. Bug Fixing new Feature: Windows update scanning

Add new connector to run remote commands

Add licence files #FR3285112

Added scan for windows updates

Solved BUG 3378467 Missing essential PXE options, mistype in PXE menuentry

Solved BUG 3288811 add harddisk without replace mbr

Solved BUG 3288812 HDD string not given without replace mbr

Added nslookup and gethostbyaddr to find the hostname from the bootenvironment

Added ip searching from uranos to find the name with the help of an ip from the database

Removed old connectors from cli inventory profile

Solved FR 3378549 Use windows arp cache on an uranos host to find the asking host mac address

Solved BUG 3380867 Unable to delete group

Patch LVM for ubuntu 10.04 Patch#3428707

make the licence module more flexible

solved BUG #3441405 unattend.xml placement

solved BUG #3288839 replace mbr / partition disk -> add new option in partition config

solved FR #3441562 added more infos in pxe menu view

solved FR #3441021 FR #3439282 moved inventory profile to use fusioninventory - see docs for more information

3.1.1945. Bug Fix release

Added new columns for fusioninventory

Solved #FR3441500 added proxy config to svn update

Solved #FR3289629 sync repositories

Solved BUG #3531197

Solved BUG #3533962

solved BUG in inventory profile

delete multi computer

3.1.1953. Support for Advanced Disk Format

new bootcd 3.2.21

new partition alignment

Solved #FR3378541

3.1.1960. Bug Fix release

Only BUG fixing release

3.1.2011. Cron module update

fixed BUG with partitioning

add option to drop to shell after profile is done

add new profile to simple bail out to shell

BUG in parsing dm-0 device partitions

fixed BUG in display old entries in Hook

kernel 3.2.33, Fixed BUG with dmraid, bootcd release 3.2.33

added DNS to get hostname

solved BUG #3543513 Problems with fusioninventory on the uranos-boot-kernel

added servername in view and edit entry

ldapmgr: make input fields larger

chooce server javascript

removed wrong line breaks

fusioninvenotry: give availability for the injector to upload data # add virtual hosts to machine

fusioninvenotry: network interfaces from esx

ldapmgr: correct BUG parsing must and may attrs

solved FR3565274

prevent double sessions from same IP / Browser during login

added module config link

Fixed some other small BUGs

added software logging with logger and eventcreate for cmd scripts

added cron config

reworked cron module

cron container for windows systems

added curl

correct BUG3576453 Unattend parser will not take into account disabled keys

Feature Request #2999181 Run Software every time

add new API mail and settings mail

added support for 2003 R2 install sources (auto install R2) and correct some variable errors

import updates from scanwinupdates update

add blacklist + disablechecks possibility for import the winupdate xml file

add optional dependency for pear mail

FR# 3579137 Make backup unattended

added cron connector

3.1.2025. Direct install from iso/wim

Now it is possible to place the windows isos directly on /z/os/ and install from there

added wimlib (since bootcd release 3.6.9) to install win VISTA/7/8/2008/2012 directly from the install.wim (can be combined with the iso option above)

new fields and table for fusioninventory

some small BUG fixes

update pxelinux module with syslinux 4.06

new templates for win 8 and 2012

new template for ubuntu 12.04 LTS

3.1.2034. BugFix

fixed bug when deleting software from computer

fixed bug with wrong column sizes, add constraints to table part_computerconfig_detail

3.1.2073. fusioninventory deployment and esx inventory

update radius_ldap

delete multiple entries #FR3285109

add firewall groups

Solved FR#3285110 add comment to licence media

Dependency now on global_uniq_identifier, prepare to sync dependencies to other locations

Fixed BUG #3607879 tables were not created in fusioninventory

#FR 3608890 show only last versions

sync dependencies #FR3578292

boot-cd release 3.8.8

Solved BUG #3610300 User deletion not possible

resoveld bug with double quotes in logger

add db_dropCONSTRAINT

fusioninventory module can now install/update software (docs needed currently only for testing! use with care! feel free to ask via the ML for usage)

fusioninventory module can now run task inventory esx

3.1.2086. Bug Fixes / radius_ldap

fixed layout for submenues

windows updates for scanwinupdates manualy to type 2 (use /Q) configurable

freeradius ldap module and connnector available for use

3.2. Uranos-boot

3.2.0.8.7. boot-cd update Release: 0.8.7

New e1000 and e1000e drivers.

Added drivers from the staging kernel (http://www.kroah.com/log/linux/linux-staging.html)

at76_usb

et131x

go7007

me4000

usbip

winbond

wlan-ng

3.2.1.1.2. boot-cd update Release: 1.1.2

Makefile for the boot stuff

supports: make download; make iso; make tftpboot; make all;

kernel 2.6.29.4

3.2.1.2. boot-cd update Release: 1.2

update kernel to 2.6.30

update glibc to 2.6.10

update ntfs-3g to 2009.4.4

update dosfstools to 3.0.3

update e2fsprogs to 1.41.6

update file to5.03

update jfsutils to 1.1.14

update module-init-tools to 3.8

udpdate p7zip to 9.04

update syslinux to 3.82

update rsync to 3.0.6

update udev to 142

added testdisk

added udpcast

3.2.1.2.1. boot-cd update Release: 1.2.1

update kernel to 2.6.30.1

3.2.1.2.2. boot-cd update Release: 1.2.2

update samba to 3.4.0

added wget

3.2.1.2.3. boot-cd update Release: 1.2.3

update udev to 144

updat busybox 1.14.2

updated busybox config

3.2.1.2.4. boot-cd update Release: 1.2.4

update kernel 2.6.30.4

update dhcp 4.1.0p1

updated e1000e 1.0.2.5

updated e1000 8.0.13

updated parted to 1.9.0

3.2.1.3.0. boot-cd update Release: 1.3.0

update kernel 2.6.31

update xfsprogs to 3.0.3

3.2.1.3.1. boot-cd update Release: 1.3.1

update dosfstools to 3.0.5

update samba 3.4.1

3.2.1.3.2. boot-cd update Release: 1.3.2

update kernel 2.6.31.1

update samba 3.4.2

added clamscan and freshclam

3.2.1.3.3. boot-cd update Release: 1.3.3

update kernel 2.6.31.3

add logo to iso

add http://boot.kernel.org/ to iso (Booting your machine over HTTP)

3.2.1.4.0. boot-cd update Release: 1.4.0

update kernel 2.6.32

udpate e1000 to e1000-8.0.18

update e1000e to e1000e-1.0.15

3.2.1.4.1. boot-cd update Release: 1.4.1

update kernel 2.6.32.4

update clamav 0.95.3

update rsync 3.0.7

update samba 3.4.5

update busybox 1.15.3

update e2fsprogs 1.41.9

update dhcp 4.1.1

update findutils 4.4.2

update fuse 2.8.1

update ethtool 2.6.33-pre1

update gawk 3.1.7

update glibc 2.11.1

update LVM 2.2.02.58g

update memtester 4.1.2

update msmtp 1.4.19

update nano 2.2.2

update ntfs-3g 2010.1.16

update openssh 5.3p1

update openssl 0.9.8l

update pciutils 3.1.5

update stress 1.0.2

update syslinux 3.84

update udev 150

update udpcast 20091230

update wireless_tools 30.pre9

update xfsprogs 3.1.0

update dosfstools 3.0.7

update parted 2.1

update e1000e 1.1.2

3.2.1.4.2. boot-cd update Release: 1.4.2

update bash 4.1

added parted 1.6.22 to /usr/local/sbin

new kerneloption oldparted=1 for profile unattended

3.2.1.4.3. boot-cd update Release: 1.4.3

kernel 2.6.32.7

added shhfs (mount SSHFS now working)

Fixed BUG with install XP (switched back to parted 1.9.0)

added ms-sys (http://ms-sys.sourceforge.net/)

3.2.1.4.4. boot-cd update Release: 1.4.4

kernel 2.6.32.9

udev 151

e1000 8.0.19

dosfstools 3.0.9

dialog 1.1-20100119

3.2.1.4.5. boot-cd update Release: 1.4.5

busybox 1.16.1

clamavversion 0.96

e2fsprogs 1.41.11

file 5.04

fuse 2.8.3

glib 2.22.5

linux 2.6.33.3

memtester 4.1.3

nano 2.2.3

syslinux 3.86

stress 1.0.4

samba 3.5.2

3.2.1.4.7. boot-cd update Release: 1.4.7

kernel 2.6.34

BUG Fixes from versions 1.4.x

3.2.1.4.8. boot-cd update Release: 1.4.8

kernel 2.6.35.4

3.2.1.4.9. boot-cd update Release: 1.4.9

kernel 2.6.36

e1000e-1.2.17

nfs-utils-1.2.3

openssh-5.5p1

openssl-0.9.8o

ntfs-3g-2010.10.2

dhcp-4.2.0

3.2.1.5.0. boot-cd update - first uranos boot release Release: 1.5.0

The iso version contains a isolinux.cfg which is not compatible with unattended-gui, because it points to an other profile. Please update your build environment to lucid (see Boot cd docs)

deactivated external e1000 and e1000e

renamed it to uranos

busybox-1.17.3

clamav-0.96.4

dosfstools-3.0.10

dhcp-4.2.0-P1

e2fsprogs-1.41.12

ethtool-2.6.35

fuse-2.8.5

gawk-3.1.8

glib-2.26.0

memtester-4.2.1

ms-sys-2.2.0

msmtp-1.4.21

nano-2.2.5

ncurses-5.7

xfsprogs-3.1.3

udev-164

kernel 2.6.36

3.2.1.5.1. boot-cd update

kernel 2.6.36.2

ethtool 2.6.36

zlib 1.2.5

resolved BUG with freshclam

added httpfs to mount files (iso files) over http[s] version 0.1.4

added davfs to mount webdav over http[s]

added option z_fs=HTTPFS

added option z_fs=DAVFS

glibc 2.11.3

udev 165

3.2.1.6.0. boot-cd update

samba-3.5.8

kernel 2.6.38.2

busybox 1.18.4

dosfstools 3.0.11

pmtools 20110323

udev 166

Support DRIVERSCAN now also for alsa devices

3.2.1.6.1. boot-cd update

kernel 2.6.38.3

clamav 0.97

testdisk 6.12-WIP

testdisk support ntfs

udev 167

3.2.1.7.0. boot-cd update

kernel 2.6.39.1

udev 171

testdisk 6.12

ca-certificates 20110421

syslinux 4.04

chntpw 110511

usbutils 0.90

xfsprogs 3.1.4

3.2.2.0.0. boot-cd update

kernel 3.0

parted 3.0

3.2.2.0.1. boot-cd update

kernel 3.0.1

parted downgrade back to 1.9.0

3.2.2.0.2. boot-cd update

kernel 3.0.8

3.2.2.1.0. boot-cd update

kernel 3.1.4

busybox 1.19.3

3.2.2.1.1. boot-cd update

kernel 3.1.10

clamav 0.97.3

removed pmtools

ca-certificates 20111211

3.2.2.2.0. boot-cd update new option to access remotely and monitor the progress

openssh 5.9p1

openssl 0.9.8t

kernel 3.2.2

new option: ss=1 (start screen session)

new option: pw=secretpassword (set root password)

new option: epw=TTlTrEKV4Wg5M (set root password in encrypted format)

3.2.3.2.21. boot-cd update new versioning

version of boot-cd reflects now the kernel version

wget-1.13.4

xfsprogs-3.1.8

added util-linux-2.21

udpcast-20110710

testdisk-6.13

sshfs-fuse-2.3

syslinux-4.05

removed samba, added cifs helper from http://linux-cifs.samba.org/cifs_download.html

rsync-3.0.9

pv-1.3.1

pciutils-3.1.9

parted-3.1, oldparted is now parted 1.9.0

p7zip_9.20.1

openssl-1.0.1c

openssh-6.0p1

nfs-utils-1.2.5

neon-0.29.6

ncurses-5.9

nano-2.2.6

msmtp-1.4.27

module-init-tools-3.15

memtester-4.2.2

LVM2.2.02.96

jfsutils-1.1.15

glibc-2.15

glib-2.30.0

gawk-4.0.0

fuse-2.9.0

file-5.10

e2fsprogs-1.42.4

dhcp-4.2.4

dmidecode-2.11

dialog_1.1-20120215

removed device-mapper (included into LVM)

clamav-0.97.5

ca-certificates_20120212

busybox-1.20.2

bash-4.2

kernel 3.2.21

3.2.3.2.33. boot-cd update

new kernel 3.2.33

clamav-0.97.6

chntpw-110511

libevent-2.0.20

partclone 0.2.55-1

3.2.3.6.9. new libs

new kernel 3.6.9

added wimlib (imagex to extract wim files directly)

added wpa_supplicant

added uranos logo

3.2.3.8.3. boot-cd update

switched from module-init-tools to kmod

kernel 3.8.3

ca-certificates_20130119

clamav-0.97.7

dosfstools-3.0.16

dhcp_4.2.5

e2fsprogs-1.42.7

expat-2.1.0

file-5.13

fsarchiverver-0.6.17

fuse-2.9.2

gawk-4.0.2

glib-2.35.9

glibc-2.17

kmod-12

libevent-2.0.21-stable

memtester-4.3.0

msmtp-1.4.30

ntfs-3g_ntfsprogs-2013.1.13

openssh-6.1p1

openssl-1.0.1e

partclone-0.2.59-1

pv-1.4.6

syslinux-5.01

sshfs-fuse-2.4

udpcast-20120424

wget-1.14

wimlib-1.2.6

3.2.3.8.8. boot-cd update

kernel 3.8.8

wimlib 1.3.2