Hello,
If possible, we'd prefer not have a server in each location.
Is it possible to host an opsi server in AWS, and configure it to use a DFS share, distributed to each location, for storing the OS and driver files?
Or, is it possible to be able to use opsi as a standalone live CD/USB like clonezilla live, with locally attached or SMB storage for OS and driver files? Maybe opsi could be forked to do this?
Cloud hosted opsi server, or live CD system?
Re: Cloud hosted opsi server, or live CD system?
It seems like an unattended opsi Windows install consists of these steps:
1. PXE boot into Linux environment
2. WinPE image is generated on the fly, all needed drivers are included in the generated image
3. System reboots into WinPE, then begins an unattended Windows install (using OS installation files from the configured depot share)
4. Newly installed Windows system boots, and opsi-client-agent starts to install deployed software
Is it possible to take a Clonezilla image of the generated WinPE image, and deploy it later without the opsi server being online (assuming the same depot share were accessible)?
1. PXE boot into Linux environment
2. WinPE image is generated on the fly, all needed drivers are included in the generated image
3. System reboots into WinPE, then begins an unattended Windows install (using OS installation files from the configured depot share)
4. Newly installed Windows system boots, and opsi-client-agent starts to install deployed software
Is it possible to take a Clonezilla image of the generated WinPE image, and deploy it later without the opsi server being online (assuming the same depot share were accessible)?
- n.wenselowski
- Ex-uib-Team
- Beiträge: 3194
- Registriert: 04 Apr 2013, 12:15
Re: Cloud hosted opsi server, or live CD system?
Hi,
depending on what you want to do with your opsi server you may could get rid of some by using things like the WAN extension or dynamic depot.
Also how the clients may access the network or your opsi server can play a role here.
Maybe even opsi on something like a Raspberry Pi or the like is all that you need if you do not want to invest in new servers for multiple locations.
If you don't want to deploy with opsi you may do without an opsi server but you then probably need some other deployment server.
I'd suggest getting in touch through our professional services and then discuss what requirements and limitations you have so that we can find a solution that works best for you. If there is a way that requires custom parts this is also probably the easiest way of having them created and integrated.
Kind regards
Niko
depending on what you want to do with your opsi server you may could get rid of some by using things like the WAN extension or dynamic depot.
Also how the clients may access the network or your opsi server can play a role here.
Maybe even opsi on something like a Raspberry Pi or the like is all that you need if you do not want to invest in new servers for multiple locations.
I haven't done that before. Working with virtual depots may work for presenting different shares depending on the location.ttblum hat geschrieben:Is it possible to host an opsi server in AWS, and configure it to use a DFS share, distributed to each location, for storing the OS and driver files?
Running opsi through a prepared live medium should be possible. I don't think this would require any fork but instead should be a matter of proper configuration.ttblum hat geschrieben:Or, is it possible to be able to use opsi as a standalone live CD/USB like clonezilla live, with locally attached or SMB storage for OS and driver files? Maybe opsi could be forked to do this?
You will need to have an opsi server online for authentication of the client and retrieval of configuration aswell as installation data. Getting rid of the config server isn't so easy as this is a central part.ttblum hat geschrieben:It seems like an unattended opsi Windows install consists of these steps:
1. PXE boot into Linux environment
2. WinPE image is generated on the fly, all needed drivers are included in the generated image
3. System reboots into WinPE, then begins an unattended Windows install (using OS installation files from the configured depot share)
4. Newly installed Windows system boots, and opsi-client-agent starts to install deployed software
Is it possible to take a Clonezilla image of the generated WinPE image, and deploy it later without the opsi server being online (assuming the same depot share were accessible)?
If you don't want to deploy with opsi you may do without an opsi server but you then probably need some other deployment server.
I'd suggest getting in touch through our professional services and then discuss what requirements and limitations you have so that we can find a solution that works best for you. If there is a way that requires custom parts this is also probably the easiest way of having them created and integrated.
Kind regards
Niko
Code: Alles auswählen
import OPSI
Re: Cloud hosted opsi server, or live CD system?
OK, thanks.
In this scenario we would use PQDDeploy to deploy software instead of opsi.
Does the WinPE contact the opsi server during installation in any way other than reading and writing to the opsi_depot fileshare?
Is it possible to have the WinPE access opsi_depot share directly off of a NAS, such as FreeNAS, instead of on the opsi server? If so, how would I configure the authentication of the opsi_depot share on FreeNAS, username/password/permissions, etc.?
In this scenario we would use PQDDeploy to deploy software instead of opsi.
Does the WinPE contact the opsi server during installation in any way other than reading and writing to the opsi_depot fileshare?
Is it possible to have the WinPE access opsi_depot share directly off of a NAS, such as FreeNAS, instead of on the opsi server? If so, how would I configure the authentication of the opsi_depot share on FreeNAS, username/password/permissions, etc.?
- n.wenselowski
- Ex-uib-Team
- Beiträge: 3194
- Registriert: 04 Apr 2013, 12:15
Re: Cloud hosted opsi server, or live CD system?
Hi,
opsi-linux-bootimage will always contact the server on the other hand.
This can point to different server but you will have to make sure that username / password / permissions are set correctly on that share. User used for access is usually pcpatch.
Kind regards
Niko
WinPE can be configured to not access the depot (product property winpenetworkmode set to false).ttblum hat geschrieben:Does the WinPE contact the opsi server during installation in any way other than reading and writing to the opsi_depot fileshare?
opsi-linux-bootimage will always contact the server on the other hand.
You can configure what location the clients use for accessing the depot share (see settings for your depot in the configed).ttblum hat geschrieben:Is it possible to have the WinPE access opsi_depot share directly off of a NAS, such as FreeNAS, instead of on the opsi server? If so, how would I configure the authentication of the opsi_depot share on FreeNAS, username/password/permissions, etc.?
This can point to different server but you will have to make sure that username / password / permissions are set correctly on that share. User used for access is usually pcpatch.
Kind regards
Niko
Code: Alles auswählen
import OPSI