Do I need Active Directory?

Question

System administration

The task in a small network (up to 5-6 computers) is to organize access to 1C. I have already raised the terminal server, configured the VPN (for knocking through the Internet). The problem is the following - for half of the users only 1C is needed, respectively, I don’t need them to have other shortcuts on the remote desktop, as well as access to My Computer, its local drives, Network, Control Panel, Administrative Tools and so on. The other half will be allowed some of the above.
If I can also give the rights to folders to each user or group through the Security properties, then cleaning the Desktop and Start items is already more problematic. Googling the Internet shows that this is possible through the Group Policy snap-in, and this works, as I understand it (yes, I'm a programmer, but never a sysadmin =) only if the network is a domain.
So I need to understand whether I need to raise this domain, domain controller, for the sake of all this because of several users? Because I really don’t want to, it’s all difficult for sure ...

Answer 1

What do you need a domain for? For 5-6, I can only think of using centralized management of accounts and rights to shares, and then there are too few computers for the domain. Local policies for users and so can be configured through gpedit.msc and the registry. It is possible to prescribe a ban on viewing the file system and a forced launch of purely 1c, without the rest of the interface in the user property.

Answer 2

For 5-6 computers, I would not develop a domain - there will be more crap with deployment than profit, because. up to 10 computers and manually you can quickly adminit.
Yes, and the yellow program for 5-6 computers is still holding up normally even in network mode, but since the terminal has already been raised, it's good.
If some users only need a yellow program, then they, in principle, do not need Windows. You can install the "Thin Client" system on the same WinCE or whatever Linux. Task: When you turn it on, connect via RDP to a server, and then hide the slave table and assign yellowprog to autorun and you don’t need to administer anything on the spot.
The rest is either local policies or remote registries.

Answer 3

Firstly, a license for server Windows costs horse money (for 5-6 people), and secondly, 1C can be easily installed in client-server mode (server on a server computer, users have a client installation), or it’s important for you to do not put people's computers locally 1C?

Answer 4

www.oszone.net/11254/gpedit_part1

Answer 5

If you are not going to grow, then the domain is not needed. Expensive (we are honest people ^_^ ).
It is enough to add your account to the computer management in the Administrators group, and then through the start - Run - \\% computer_name% already see what the employees have on the workstation.
Well, immediately set up accounts on local machines.
But if you grow, then manually administering it will already be difficult, then yes, automation will be needed.

Answer 6

Group policies are also available locally on the server, without AD - gpedit.msc.
To restrict access, publish applications, and do not give access to the desktop. At the same time, do not enable web access, because. through web access, the client will be able to access all published applications - place applications on clients manually, this can be done either by providing an rdp application file, or by generating an msi package and giving it to the client.

Answer 7

If the server is 2008 and newer - try to export 1C as RemoteApp