Feature: Group policy configuration

[OgreTransporter]

In most local area networks (companies, universities, schools, etc.) with a domain controller and Windows, computers are configured by group policies. Establishing npacked as a packet manager for Windows in such groups is much more comfortable if a configuration by a group policy is available.

This is pretty easy, because group policies can create registry keys on target machines.

[tim-lebedkov]

I have no idea how this works. Is this some kind of file that is installed on the domain server?

[OgreTransporter]

There are multiple ways to handle group policies. The fastest way is implementing a registry-based policy (see https://msdn.microsoft.com/en-us/library/aa374292(v=vs.85).aspx). This method will also reduce the effort on npacked, because it's only required to search the corresponding registry key:

HKEY_CURRENT_USER\Software\Policies (preferred location)

or

HKEY_LOCAL_MACHINE\Software\Policies (preferred location)

The server will create and set registry keys and values on all client computers.

[tim-lebedkov]

thank you

[OgreTransporter]

I'll start with #11 and add functions for group policies in the end.

[OgreTransporter]

I've tested it in a local environment with the following group policy:

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Npackd]
"path"="C:\\ProgramData\\Npacked"
"closeProcessType"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Npackd\Reps]
"size"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Npackd\Reps\1]
"repository"="file://horch/Software-Rollout/MyRepository.xml"

This settings have been provided by the central server for all users.

[tim-lebedkov]

Hi,

I would like to add your name to the window that is shown on F1, e.g. "with significant contributions from: OgreTransporter (https://github.com/OgreTransporter)".

Is this OK? Should I add your real name?

[OgreTransporter]

Feel free to add what do you want ;-)