Hi there, I'm setting up an small network for our university-workgroup and am running into some problems right now.
The network is quite simple: We have a few Windows XP clients in a Domain controlled by a SME 7.3, an IPCop Machine acts as a router to our universities network.
Now everything works quite fine, but this new network is our first one to deploy software deployment.
We decided to use
OPSI [link] as it is OpenSource and a debian based VM is available.
Setting up vmware-server on the SME was very easy as well as loading & configuring OPSI-Server which creates his own domain.
So serverside is ok, until now; But on the clientside we have some problems:
The OPSI-System uses a service on the clientside to fetch installationinformations by http from the server.
This works well, but the OPSI developers decided to distribute the packages containing the actual installationfiles by smb instead of http, and this is where the trouble begins:
Because the Windowsmachines are connected to the SME domain they can't access the Samba-Share on the OPSI-Server before a user is logged in and has mapped a network drive - which is very absurd because softwaredeployment should be done *before* the user loggs in
To circumvent this there are (afaik) only two options:
1. Mirror the packages to SME and tell the clientsservices to access those (might be possible, but not as nice as 2...)
2. Connect the OPSI Server as a BDC into the Domain (right now it has its own domain)
As I would like to use solution 2 I found out that
I could use OpenLDAP as a backend [link], but the
corresponding New Feature Request at the Bugtracker [link] has been inactive since 4 month and it doesn't seem as this could be used in SME 7.3?
(Well, we have some SME 7.2 disk images, so downgrading SME would be no problem
)
Or should I simply give up and try to configure the clients to use solution 1?
Sebastian
1 Replies
1374 Views