You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: INSTALL.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,10 +18,10 @@ That's all for now!
18
18
* Go to one of your computers.
19
19
* It should have at least one unique identifier availalble: Serial (might not be unique), Mac address, GUID.
20
20
* Go to sub-item "auto-install" in the computer page.
21
-
* Set your desired values, mainly "Automatic Install" to YES. Choose the proper task sequence and application (yes just one for now)
21
+
* Set your desired values, mainly "Automatic Install" to YES. Choose the proper task sequence and application(s) and role(s) as you would from MDT's interface
22
22
* Save
23
23
24
-
The computer is now created into MDT with those settings. Pressing F12 for PXE boot should fire the install.
24
+
The computer is now created or updated in MDT with those settings. Pressing F12 for PXE boot should fire the install.
Copy file name to clipboardExpand all lines: README.md
+7-5Lines changed: 7 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,25 +31,27 @@ It is developed and tested in this environment only. If you experience problem w
31
31
* MDT must be installed in a MS-SQL database accessible from the GLPI server
32
32
* MDT must be fully operationnal by itself. The plugin will not fix a faulty MDT installation, it is only remote-controlling it.
33
33
* (MSSQL or ODBC) and SimpleXML PHP modules must be installed
34
-
* The "Control" directory in your MDT deployment share contains part of the MDT configuration (the other part is in the MS-SQL database). It needs to be mounted (read-only is OK) somewhere on your GLPI server and accessible to PHP scripts.
34
+
* The "Control" directory in your MDT deployment share contains part of the MDT configuration (the other part is in the MS-SQL database). It needs to be mounted (read-only is OK) somewhere on your GLPI server and accessible to PHP scripts. Pay specific attention to files ownership and SELinux settings which can prevent proper functionning.
35
35
* Fusion inventory, though not mandatory is really very very nice to have.
36
36
37
-
As of version 0.0.1 this plugin is just a little more than a proof of concept. I hope to improve it with time but some feedback on this
37
+
Starting with version 0.1.0 this plugin is now fully functionnal and in use at our premises. I hope to improve it with time but some feedback on this
38
38
version is welcome in order to direct my efforts in the right direction.
39
39
Still, it works for us, in our specific environment!
40
40
41
41
The plugin is available in French and English, other translators welcome.
42
42
43
43
44
44
## TODOs
45
-
* Manage groups (this is mainly UI interface stuff, the code can already handle it. My main question is how many applications are avalaible on average MDT servers? Our has only 5, but in a previous company we had hundreds. The gui would not be the same....)
46
-
* Handle roles, models, packages in the same way applications are handled (but are you using those features in MDT)?
45
+
* Manage ranks in applications (this is mainly UI interface stuff, the code can already handle it. My main question is "is it really needded? We don't as we don't have dependencies between applications (and no so many applications to install anyway).
46
+
* Handle models, packages in the same way applications are handled (but are you using those features in MDT)? Models are an issue because of a limitatio in Fusion Inventory. It may be aleviated with GLPI 9.2.x. More to come...
47
47
* Automate some actions based on information available in GLPI and not managed by MDT (location, entity....)
48
48
* Be multi-MDT-server, multi-deployment-share, multi-domain aware. Currently the plugin is not domain aware and is connected to only one MDT database. This raises quite a few questions as to how it should work then.
49
-
* Several coupling modes are proposed in the config page.... but only one is really implemented. There too I wonder what user want. For me the "Strict Master-Slave is fine" as I want everything to be done in GLPI.
49
+
* Several coupling modes are proposed in the config page.... The strict and loose coupling are there, master-master is not for the time being. Is ithis mode desirable anyway? For me the "Strict Master-Slave is fine" as I want everything to be done in GLPI. Feedback is welcome.
50
50
* Fix Bugs!!!!! There most probably are many, this is the first release.
51
51
52
52
53
53
Please test and send feedback if you (dis)like my work.
54
54
55
+
For more information, please consult the Wiki on gitHub
0 commit comments