Accessing Windows registry from samba wmic utility

Andrey Kondakov andreykondakov at
Mon Jul 30 05:21:37 MDT 2012

I guess I've heard the story in form which i similar to what you wrote.
I had extensive experience with samba smbclient and net utilities for
Windows monitoring
but the things got changed and IT dep started to enforce restrictive
policies to access hosts remotely including registry.
I discovered wmic fork and have to say this is quite good to start with and
move my inspection agent to WMI-bound since
Samba WMI client is almost ready for production use. It runs WQL queries
and is capable to start process on remote host.
The one thing I needed to fix was the registry access and finally the
solution is quite similar to process running.
The only thing that you need is just to verify method arguments of
StdRegProv and you are done.
Now I have everything implemented in single monitoring client and it makes
the things easier.

Anyway, a lot of thanks for people who were writing wmic.


On Fri, Jul 27, 2012 at 11:16 AM, Andrew Bartlett <abartlet at>wrote:

> On Thu, 2012-07-26 at 12:37 +0300, Andrey Kondakov wrote:
> > Hi,
> >
> > That was my original intention but it turned out that several network
> > segments (read domains) have pretty restrictive
> > settings in terms of network access availability. For example, remote
> > registry service is stopped or port 445 is firewalled.
> > In fact, wmic is the only mean to access WMI repository and read both
> > conventional Win32_ classes and registry.
> The reason Jelmer asked about this is that wmic is a fork of a very old
> development version of Samba 4.0, and for a number of reasons it just
> isn't practical to merge it back in (the supporting code was removed as
> a development dead-end at the time when wnic was developed without
> communication with the Samba team).
> Andrew Bartlett
> --
> Andrew Bartlett                      
> Authentication Developer, Samba Team 

More information about the samba-technical mailing list