Tranquil IT Forum

• - Multi-site Active Directory domain (One OU per site; the OU contains the computer/user objects of the site concerned)

• - Limited bandwidth on some sites

• - Each site has its own IP address

• - The sites communicate with each other

• - Each site has at least one file server running Windows Server (generally version 2012)

• - Users are "regular users" (no administrator rights)

• - Client workstations running Windows 7 Pro, and soon some will be running Windows 10

• - We are studying the possibility of remaking our master images for Windows 10. We would like to take this opportunity to lighten the load (which includes a large part of the client software (but is up to date on the master date...)) by installing third-party software (Firefox, various plugins, etc...) after installation on a workstation; the idea comes in part from the website https://ninite.com/.

• - We would like to take this opportunity to offer users the possibility of installing validated software on their workstations via a portal. Several private and secure repositories are planned (users, technicians, etc.).

• - an AD 2012 domain controller which also has the role of DHCP and DNS server

• - another 2012 server with WAPT server and Microsoft Deployment Toolkit

• - a client workstation running Windows 10 with the WAPT client installed manually.

• - created a waptselfservice group in AD and added a user "simple power"

• - Installation when the station is shut down: OK

• - Installation via the portal from a single-user AD account on the workstation: OK

• - Adding a public repository to the user's machine (to test the functionality of having multiple repositories): OK

• - Multi-depots

• - Multi Site

• - Is the communication port between the agent and the server configurable?

• - Addition of new software

Bill wrote:Hello,

Bill wrote:Good morning,
While searching for information on a self-service portal solution for users, we came across the WAPT software.

Existing structure:

• - Multi-site Active Directory domain (One OU per site; the OU contains the computer/user objects of the site concerned)

• - Limited bandwidth on some sites

• - Each site has its own IP address

• - The sites communicate with each other

• - Each site has at least one file server running Windows Server (generally version 2012)

• - Users are "regular users" (no administrator rights)

• - Client workstations running Windows 7 Pro, and soon some will be running Windows 10

What we would like to do:

• - We are studying the possibility of remaking our master images for Windows 10. We would like to take this opportunity to lighten the load (which includes a large part of the client software (but is up to date on the master date...)) by installing third-party software (Firefox, various plugins, etc...) after installation on a workstation; the idea comes in part from the website https://ninite.com/.

• - We would like to take this opportunity to offer users the possibility of installing validated software on their workstations via a portal. Several private and secure repositories are planned (users, technicians, etc.).

Tests carried out to date:
We installed it on an isolated test environment

• - an AD 2012 domain controller which also has the role of DHCP and DNS server

• - another 2012 server with WAPT server and Microsoft Deployment Toolkit

• - a client workstation running Windows 10 with the WAPT client installed manually.

• - created a waptselfservice group in AD and added a user "simple power"

Test results:
We retrieved three "ready-made" packages from the tranquil.it repository and made them available via the central interface on the Windows 10 machine.

• - Installation when the station is shut down: OK

• - Installation via the portal from a single-user AD account on the workstation: OK

• - Adding a public repository to the user's machine (to test the functionality of having multiple repositories): OK

Questions :

• - Multi-depots

-- Can we offer several repositories on the same server (for example, one for users, one for technicians, etc.)? If so, how do we do it?
-- Can we secure different repositories on the same server (for example, technicians could access software via the portal that regular users wouldn't have access to)? We understood that groups were named identically to AD groups, and a link could be established; does this mean that if we have, for example, an AD group named "Tech DSI" containing only technicians, if we create a "Tech DSI" group in WAPT, only technicians will be able to install the software available in that group?

• - Multi Site

-- We consulted the wiki web ants ; it seems possible to set up replications on "client" servers; the explanations given apply to a Linux server; would this be possible under Windows (as a reminder, we have local file servers at the sites under Windows Server and the sites have limited bandwidth)?
-- Depending on the answer to the question above, how can we easily detect which servers to consult (create a DFS, filter based on IP, rely on AD, etc.)?

• - Is the communication port between the agent and the server configurable?

• - Addition of new software

-- Is there a graphical interface to create a new deployment package from an EXE? (For now, we have very quickly tested the creation via command line, which resulted in failure (package created but unusable))


Thank you in advance for your answers.