Biz© rrrrrrrrrrСам использую, у меня сервис, установленный на клиентских машинах, скидывает инфу на серверный ресурс, к которому доступ имеют только админы домена и NT AUTHORITY\SYSTEM клиентов.
вы про NullSessionShares ? ага. Вообще сама Local System (NT AUTHORITY\SYSTEM) имхо не особо так и ущербная, просто в ее отношении завинчены кое-какие гайки

rrrrrrrrrr Biz© rrrrrrrrrrСам использую, у меня сервис, установленный на клиентских машинах, скидывает инфу на серверный ресурс, к которому доступ имеют только админы домена и NT AUTHORITY\SYSTEM клиентов.
вы про NullSessionShares ? ага. Вообще сама Local System (NT AUTHORITY\SYSTEM) имхо не особо так и ущербная, просто в ее отношении завинчены кое-какие гайки
сорри, не врубился. Нет, это не NullSessionShares, а любые шары вообще:
Resource Kit 2kSrvany Notes

--------------------------------------------------------------------------------
Interactivity versus Network Access
Due to a restriction enforced by Windows on services, the application can either be interactive (for example, it might read keyboard input) or have network access, but not both at the same time. If you know which servers your interactive service application needs to connect to, it is possible to configure these servers (or selected shares on them) to allow your service (running under the LocalSystem account) to gain access to them.
To allow LocalSystem services on any computer in the domain to connect to a specific share on a server, use a registry editor to add the name of that share in the following registry location:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
LanmanServer\Parameters\NullSessionShares
If LocalSystem services also need to gain access to named pipes on that server, add the named pipes in the following registry location:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
LanmanServer\Parameters\NullSessionPipes
To allow access to all shares and pipes on the server by LocalSystem services, add the following RestrictNullSessAccess entry, with a data type of DWORD and a value of 0:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
LanmanServer\Parameters\RestrictNullSessAccess



Note

Adding this entry to the registry allows everyone in the domain to gain access to the server.

Programming Considerations
With Win32 graphical applications, all top-level windows receive the WM_QUERYENDSESSION and WM_ENDSESSION messages when the user logs off. Some Win32 applications quit when they receive these messages. In order for a Win32 application to keep running when a user logs off, the default Windows procedure should be called when these messages are received.

Win32 character-based applications receive a CTRL_LOGOFF_EVENT event from the console when the user logs off. If your character-based application registers a console event handler (using SetConsoleCtrlHandler), it must ignore CTRL_LOGOFF_EVENT in order to keep running.

Presentation Manager Applications
When you use Srvany with Presentation Manager applications, special configuration instructions apply. Consult the Readme.wri file shipped on Disk#1 of the Windows NT Add-On Subsystem for Presentation Manager, version 3.51. Presentation Manager is a Microsoft add-on product that allows you to run 16-bit Presentation Manager 1.x applications in addition to the OS/2 character-mode applications supported by the Windows OS/2 subsystem.

Там есть возможность все это открыть не для всех шар, а для конкретных (давно пользовал для отдельностоящего сервера, куда инфа складывается, сейчас просто расшарено для Domain Computers на доменном сервере). Если надо, ковырну как, по памяти тяжело.