Closed cnotin closed 3 years ago
Running NetSessionEnum against a DC will give you sessions for systems that aren't the DC for example. The ComputerID comes from resolving the computer name that comes back from NetSessionEnum.
Of course it makes sense! Perhaps I made a mistake when looking at the output, or I had an odd case, but I just confirmed that we have ComputerId != ObjectIdentifier in the output so it's all good Sorry @rvazarkar!
A computer object in computers.json looks like this:
The
ComputerId
attribute is repeated for each session and it is redundant with theobjectid
of the computer which we already know (except if I missed a specific case?). I suggest removing it then to have a smaller file :)