Posts made by Fernando Gietz

@Lenain I think that you find a bug XD.
Well, I think that we can apply a workaround.

Go to the database:
select * from roleUserAssoc;
±------±--------±----------±----------+
| ruaID | ruaName | ruaRoleID | ruaUserID |
±------±--------±----------±----------+
| 27 | | 2 | 180 |
| 96 | | 1 | 216 |

Is your user in this table?
Do you use the LDAP plugin?

Hola @linuxba :
el uso mayoritario de FOG es para clonar discos completos, no por particiones.

¿Se puede hacer?
Si, se puede hacer. La limitación es que se descarga una sola partición por tarea.

¿Cómo?
Creando una imagen de una partición

Creando varias definiciones de una partición
Crear nueva partición:

• Nombre de la imagen: mi_disco_part1
• Tipo de imagen: One disk / no resizable
• Particionado: Partition 1 only
  Creamos tantas imágenes como particiones tenga el disco.
  Subimos las particiones una a una.
  Luego desplegamos la particion que queramos. Esto tiene una limitación: el tamaño del disco de origen y que hay que clonar completamente el disco previamente.

====================
Google traductor

Hello @linuxba:
the majority use of FOG is to clone complete discs, not by partitions.

Can be done?
It can be done. The limitation is that only one partition is downloaded per task.

How?
Creating an image of a partition

Creating several definitions of a partition
Create new partition:

• Name of the image: my_disco_part1
• Image type: One disk / non-resizable
• Partitioning: Partition 1 only
  We create as many images as partitions have the disk.
  We upload the partitions one by one.
  Then we deploy the partition that we want. This has a limitation: the size of the source disk and that you have to completely clone the disk previously.

The user, is local? Do you create it from web user interface?

Hello @Lenain ,

Do you assign rules to the role?

By default are two roles: Administrator and technician. And when you install the plugin, the plugin creates some default rules. These rules can be to config the main menu, the top tool bar, and to config the access to the submenus.

First assign users to the role
Second assign rules to the role.

@quinniedid I don know but is easy to check it don t use spaces in one role. You can see the entries in the database in the rule* and role* tables

Hi @j_d ,
I have FOG 1.5.5 under RHEL 7, now runs well and the performance is normal, but I had troubles with it in the past.

Some questions:

• FOG version in the new centOS 7 server?
• How many clients are in the host table of fog database?
• How many clients are power on simultaneously?
• PHP version?
• Is a virtual server?

Hi,

I am testing the FOG 1.6 test version and I detect a bug in the LDAP plugin. When you try to add a new LDAP server, the WEBUI says to you that the server exists.

I saw the code and the problem is in ldapmanagement.page.php line 660 :

if ($ldap) {
                throw new Exception(
                    _('An LDAP server already exists with this name!')
                );
            }

Change to

if ($exists) {
                throw new Exception(
                    _('An LDAP server already exists with this name!')
                );
            }

Well

First thing: update your php version to php7 and mariaDB to last version.

After do this, Did the your performance increase?

Hi,

Which version of PHP do you have installed?
Is a virtual server?

Hi @quinniedid ,
I have this plugin installed in 1.5.5 and works fine.
The users, are local? Did you create them?
Are you ussing LDAP plugin too?
Which rules are you using?

Some recomendations about this plugin:

• Don’t asociate the “fog” user to one role. This user is special, like a system user, in this way you can use it to roll back of changes.
• Test the role and their rules first with one local test user.

Hi @quinniedid ,

You can disable this plugin erasing one registry in the database. In the database:

MariaDB [fog]> select * from plugins;
±----±--------------±-------±-----------±---------±-------±-------±-------±-------±-------+
| pID | pName | pState | pInstalled | pVersion | pAnon1 | pAnon2 | pAnon3 | pAnon4 | pAnon5 |
±----±--------------±-------±-----------±---------±-------±-------±-------±-------±-------+
| 48 | accesscontrol | 1 | 1 | 1 | | | | | |
| 44 | xixare | 1 | 1 | 1 | | | | | |
| 53 | LDAP | 1 | 1 | 1 | | | | | |
| 41 | wolbroadcast | 1 | 1 | 1 | | | | | |
±----±--------------±-------±-----------±---------±-------±-------±-------±-------±-------+
4 rows in set (0.00 sec)

And now delete it:

MariaDB [fog]> delete from plugins where pID = pDI_of_your_AccessControlPlugin;

In my case pID=48.

With this you will have the control back.

UPDATE: TAke in account that this process do a “dirty” unsintall of the plugin. To uninstall correctly the plugin, use the FOG User Interface and unstall it from Plugins menu.

Hi @NT_Tech ,
The access control Plugin works, but is possible that you need to do some changes manually in the code.

I need to know to help you some things about your server.

Do you use LDAP plugin to validate your students?

Hi @Lenain ,

FOG can not do the thing that you say. You can control the access to the main menus using the controlAccess Plugin, with this plugin you can “erase” the icons in the menu bar, in this way you can enable the access to some users to Dashboard, Hosts, Groups and Logout entries in the menu bar.

Hi,
I want to add that I have done some changes in the reports, imaging log report too, to make pre-filters and not shows all the registries.

For example, in the imaging log report you can do a a prefilter by image name, user name or hostname. In this way, the result is more small and you don’t need erase registries in the database.

The new version of the reports are available in the “working” branch

Hi,

I have created some new reports with filters because my FOG servers has a lot of computers and users and when I run a report (for example imaging log or snapin log), the server can not show it because the memory reaches to the limit. Appying some filter I have solved the problem.

Really these new reports are a new version of the old ones.

@Tom-Elliott if you want I can push them to the git repository.

In the hook file:

    public function setTypeFilter($arguments)
    {
//        $arguments['types'] = array(990,991);
        $arguments['types'] = explode(',', self::getSetting('FOG_USER_FILTER'));
    }

Hi Tom,

I was thinking that, maybe, is better create a new globalStting when you install the plugin, in this way, you can setup it dinamically.

insert into globalSettings (settingKey,settingDesc,settingValue,settingCategory) VALUES ('FOG_USER_FILTER','Esto es una prueba de configuración', '990,991','General Settings');

The insert will be done by the plugin, this is an example.

And the hook can read this filter info to show the users.

@Sebastian-Roth thanks for the info. I will see what do now

Hi,
This question is for the developers.

I am trying to make some changes in the AccessControl Plugin, the problem with this plugin is that only can assign users that are local (uType = 0 or uType = 1) because the users that LDAP plugin creates are uType = 990 or 991, and those ones don’t appear in the list.

I want to know who or where the code decides not shows the uType 990 or 991 users

accesscontrolmanagementpage.class.php

Route::listem('user');
        $items = json_decode(
            Route::getData()
        );
        $items = $items->users;
        $getter = 'usersnotinme';
        $returnData = function(&$item) use (&$getter) {
            $this->obj->get($getter);
            if (!in_array($item->id, (array)$this->obj->get($getter))) {
                return;
            }
            $this->data[] = array(
                'user_id' => $item->id,
                'user_name' => $item->name,
                'friendly' => $item->display
            );
        };
        array_walk($items, $returnData);