I'm afraid the "Star Trek" era has not yet arrived. :-)
Firewall devices typically keep logs of the internet access. But getting the
data out of the logs in a quick, convienient, and usable format is another
story. There are special products (read $$$$) that are designed for that
type of stuff that work as "add-ons" to firewalls and/or proxy servers.
Internal accesses can be audited by turning on auditing for the resource,...
but keep in mind that you are auditing the resources being accessed not the
user accessing them. You can't very well turn on auditing for every
possible resource,...there isn't anything large and powerful enough to
manage that ammount of data.
Then there are logs within Applications.....
Then there are logs produced by database systems like MS SQL Server,....
Then there are Web Server logs....
Then there are.....,and then......, and then......
In otherwords the answer is,..... I'm afraid the "Star Trek" era has not yet
arrived where you just ask the computer what the little brat has been doing
and it tells you all of it in a nice pleasant voice. :-)
--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
"SteveP" <(E-Mail Removed)> wrote in message
news:7F5A51DF-EF0E-4678-B5F5-(E-Mail Removed)...
> Hi Philip:
>
> Sounds good.
>
> Any idea hw I can monitor what the young person is up to as in
downloading,
> etc.?
> --
> Thanks, Steve
>
>
> "Phillip Windell" wrote:
>
> > "SteveP" <(E-Mail Removed)> wrote in message
> > news:C4664C00-0320-46B3-B146-(E-Mail Removed)...
> > > Hi Vincent:
> > >
> > > The second question deals with something else. I have been ordered to
> > allow
> > > a 12 year old child onto my network for the summer. With all the
> > priviledges
> > > of a regular user. So, I set up a user account, internet, e-mail,
> > printers,
> > > everything just like a regular user. But this is not a regular user.
> > > Accidental damage could be done to important data on the network by
this
> > > youngster.
> >
> > 1. Don't have him in the normal Domain Users Group.
> > 2. Make a new Group. Call it "Little Brats" or something creative :-)
> > 3. Add the kid to the Group
> > 4. Make the Group "Little Brats" the Primary group of the account.
> > 5. Remove the kid from the Domain Users Group
> > 6. Now he can only access whatever the Little Brats Group (and the group
> > "Authenticated Users") is given permission to access,....which
initially,
> > starting out,..is pretty much nothing.
> >
> > --
> > Phillip Windell [MCP, MVP, CCNA]
> > www.wandtv.com
> >
> >
> >