First off, I was very impressed on the server as well as docu. Unfortunately, there as some errors in it, as described below;
- In my experience, Java 7 wasn't able to run the configed, but Java 8 was - unlike it was stated in the guide (p. 14).
- In the requirements it isn't super clear whether a DNS server is necessary (it is not).
- If dialogues doesn't pop up during server installation, dpkg-reconfigure might help (p. 13), esp. aftpd. I am not sure how necessary this is, or if the configuration simply happens at a later time else.
- p13 samba & pcpatch: Are there some warnings (for instance, about missing modules) etc. mentioned to early in the guide? It seemed these are relevant only later in the installation process (such as p. 27). Leaving meaningless warnings (for that time) too early in the docu might create some confusion, as it did to me.
- Same might be said about describing the backend config @ p26/27.
- PXE booting: Consider stating that the error "SIOCDELRT: No such process" doesn't affect functionality.
- There are people (like me) who aren't very experienced with DHCP. Please state whether IP or MAC/both are necessary for entries @ configed if booting via PXE or for which other options
- It would be more helpful and comfortable for orientation to have the chapter/subchapter and page number shown at the page header so it is more clear to the reader at which position on the document he is right now.
- Didn't re-check yet, but the script create_driver_links.py is mentionend in the guide, but I think I couldn't find out where it is located nor was it described there.
- The guide in the docu regarding opsi-scripts and how to install new opsi-products is too detailed. It was, to say the least, overwhelming to read when you just want to create a simple opsi package. I think it might be beneficial to reduce it to something like this simple Firefox setup code:
- Creating WinPE by opsi doesn't seem to work for Win 7, only for 8 and above. The document doesn't really state this, so I had to figure it out for quite some time and was left outin the dark.
- Maybe describe how the SSL cert should look like (opsiconf SSL cert), for instance, what a common name etc. is
http://download.uib.de/opsi_stable/doc/ ... ble-en.pdf
Outside of docu:
- With the pxe boot image I used, I only had ONE (!) second to select a device before it went it autoboot mode and booted from HDD (after opsi boot image was found). Prob was the x86 boot image, can check if it helps.
- When installing the opsi client, I had the issue that there was some window popping up (or not) in which the user is asked about some authentification information. Unfortunately, for me the window didn't seem to appear on the fore-, but rather the background - with no task bar entry either. There was no clear indication that there is some input required if there is nothing to see for the user. I suggest to at minimum create a task bar entry for that window. To find out about this did cost me roughly eight working hours. For the time being, it might prove helpful as a workaround to include a hint in the documentation.
- This was in a VM in virtualBox, so it might be related to that, but I think whenever the fields from the opsi boot image were auto filled via DHCP (screen with blue background) the input stopped working and I had to reboot until they weren't automatically filled out.
Hopefully this proves as a vulnerable and helpful feedback to you!