Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>This solution works in my environment. We have login scripts that map network drives for every user. If I need to know who's logged in, I just go look at the "shared folders" snap-in on the server that hosts the share(s). Hit the "Sessions" tab; it shows all the logged in users right there.</p> <p>You sound like you need something recorded maybe. Part of our login script is a command that writes the login/logoff date and time to a file on a network share. This is an append and each user has a file. Still probably not what your looking for, but it works great on my small network of ~25 users. Here's my script:</p> <pre><code>net time \\server1 /set /yes ECHO %USERNAME% logged on %COMPUTERNAME% on %DATE% at %TIME% &gt;&gt;\\apvdbs03\Public\Users\%USERNAME%.txt 2&gt;&amp;1 echo %USERNAME% logged on %COMPUTERNAME% on %DATE% at %TIME% &gt;&gt;\\apvdbs03\Public\Computers\%COMPUTERNAME%_Users.txt 2&gt;&amp;1 echo This syncs time to server 1 and maps the drives:&gt;&gt;\\apvdbs03\Public\Users\%USERNAME%.txt 2&gt;&amp;1 echo In order: U, S, T and V are now deleted:&gt;&gt;\\apvdbs03\Public\Users\%USERNAME%.txt 2&gt;&amp;1 net use U: /delete /y&gt;&gt;\\apvdbs03\Public\Users\%USERNAME%.txt 2&gt;&amp;1 net use S: /delete /y&gt;&gt;\\apvdbs03\Public\Users\%USERNAME%.txt 2&gt;&amp;1 net use T: /delete /y&gt;&gt;\\apvdbs03\Public\Users\%USERNAME%.txt 2&gt;&amp;1 net use V: /delete /y&gt;&gt;\\apvdbs03\Public\Users\%USERNAME%.txt 2&gt;&amp;1 echo In order: U, S, T and V are now mapped:&gt;&gt;\\apvdbs03\Public\Users\%USERNAME%.txt 2&gt;&amp;1 net use U: \\server1\users$\%username% /persistent:no&gt;&gt;\\apvdbs03\Public\Users\%USERNAME%.txt 2&gt;&amp;1 net use S: \\server1\Operations /persistent:no&gt;&gt;\\apvdbs03\Public\Users\%USERNAME%.txt 2&gt;&amp;1 net use T: \\server1\CommonFiles /persistent:no&gt;&gt;\\apvdbs03\Public\Users\%USERNAME%.txt 2&gt;&amp;1 net use V: \\server1\LM2001$ /persistent:no&gt;&gt;\\apvdbs03\Public\Users\%USERNAME%.txt 2&gt;&amp;1 echo *****************************************END OF LOG ENTRY*********************************************&gt;&gt;\\apvdbs03\Public\Users\%USERNAME%.txt 2&gt;&amp;1 </code></pre>
    singulars
    1. This table or related slice is empty.
    1. PODomain Users logged in details for Windows Server 2003
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USCaptain Claptrap
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload