Okay, let's see if PSRumbagh can verify exactly what the target for
security is or if that is necessary, and whether either presented technique
provides what they need..
--
MEB
http://peoplescounsel.orgfree.com
--
_________
"Gary S. Terhune" <none> wrote in message
news:eaMssDjoIHA.5016@TK2MSFTNGP02.phx.gbl...
| I've proved the concept, just not actually written all the code, that
would
| provide individual and cumulative uptime notations added to the log at
| shutdown, but I think it might be better to leave the log alone and run a
| script on it whenever a report is desired. Depends on end use. You mention
| various scenarios. Perhaps the OP could help us pin down the target
| environment. Or, perhaps OP has used that code of Franc's and it works
just
| fine and he just hasn't bothered to report back.
|
| Locking down Windows 98 using Doug Knox's methods would be the only way I
| know to prevent meddling with the tracking system. Locking down would be
| required NO MATTER what tracking method was used if trust of the user(s)
is
| not complete. Perhaps a combination of POLEDIT and Doug's scripts.
|
http://www.dougknox.com/security/index.htm, which would be necessary under
| those conditions, anyway.
|
| --
| Gary S. Terhune
| MS-MVP Shell/User
|
www.grystmill.com
|
| "MEB" <meb@not
here@hotmail.com> wrote in message
| news:ujCQpyeoIHA.4760@TK2MSFTNGP06.phx.gbl...
| >
| > "Gary S. Terhune" <none> wrote in message
| > news:ueoHUCaoIHA.4760@TK2MSFTNGP06.phx.gbl...
| > | No, I'll post the code here, between lines of asterisks.
| > |
| > | "StartTime.vbs"
| > | ****************************
| > | Option Explicit
| > | Dim fso, f
| > | Set fso = CreateObject("Scripting.FileSystemObject")
| > | Set f = fs
penTextFile("C:\uptime.txt", 8, True)
| > | f.WriteLine "Start " & now
| > | f.Close
| > | WScript.Quit
| > | ******************************
| > |
| > | "Shutdown.vbs"
| > | *****************************
| > | Option Explicit
| > | Dim fso, f, wso
| > | Set wso = WScript.CreateObject("WScript.Shell")
| > | Set fso = CreateObject("Scripting.FileSystemObject")
| > | Set f = fs
penTextFile("C:\uptime.txt", 8, True)
| > | f.WriteLine now
| > | f.Close
| > | wso.run "C:\WINDOWS\RUNDLL32 SHELL32.DLL,SHExitWindowsEx 9"
| > | ********************************
| > |
| > | ""Restart.vbs"
| > | *******************************
| > | Option Explicit
| > | Dim fso, f, wso
| > | Set wso = WScript.CreateObject("WScript.Shell")
| > | Set fso = CreateObject("Scripting.FileSystemObject")
| > | Set f = fs
penTextFile("C:\uptime.txt", 8, True)
| > | f.WriteLine now
| > | f.Close
| > | wso.run "C:\WINDOWS\RUNDLL32 SHELL32.DLL,SHExitWindowsEx 2"
| > | ********************************
| > |
| > | "Logoff.vbs"
| > | *******************************
| > | Option Explicit
| > | Dim fso, f, wso
| > | Set wso = WScript.CreateObject("WScript.Shell")
| > | Set fso = CreateObject("Scripting.FileSystemObject")
| > | Set f = fs
penTextFile("C:\uptime.txt", 8, True)
| > | f.WriteLine now
| > | f.Close
| > | wso.run "C:\WINDOWS\RUNDLL32 SHELL32.DLL,SHExitWindowsEx 0"
| > | *********************************
| > |
| > | Place StartTime.vbs into the Startup folder. Place the other three
into
| > the
| > | C:\ root folder. "C:\Uptime.txt" is the log. I'd place shortcuts to
the
| > | shutdown scripts and the log onto the Desktop.
| > |
| > | --
| > | Gary S. Terhune
| > | MS-MVP Shell/User
| > |
www.grystmill.com
| > |
| >
| >
| >
| > Okay, tested shutdown and startup vbs. Not sure if this is accurate, but
| > apparently the desire is to monitor ALL log times [like in a networked
| > server/work station environment or multi-user environment {tracking
kids
| > usage}].
| > How do you intend to ensure that a user MUST use these to logoff or
| > shutdown, hence creating an accurate and complete log for usage tracking
| > purposes, and ensure that the Startup vbs is not removed from Startup?
| >
| > The poster also wished TOTAL runtime output logged [as in other apparent
| > users apparently for comparison to cumulative logged activity]. The
| > suggestion was to compare SMART values [hard drive runtime hours].
| >
| > --
| > MEB
http://peoplescounsel.orgfree.com
| > --
| > _________
| >
| >
| > |
| > | "MEB" <meb@not
here@hotmail.com> wrote in message
| > | news:%23Dqa0vXoIHA.5016@TK2MSFTNGP02.phx.gbl...
| > | > Okay, let me reply here. If you finished the scripts and other, is
| > there
| > a
| > | > link for testing these [no installer yet please]?
| > | >
| > | >
| > | > --
| > | > MEB
http://peoplescounsel.orgfree.com
| > | > --
| > | > _________
| > | >
| > | > "Gary S. Terhune" <none> wrote in message
| > | > news:eZeTrhWoIHA.3652@TK2MSFTNGP03.phx.gbl...
| > | > | Anyway, I just finished a whole set of scripts and shortcuts that
| > will
| > | > do
| > | > | what you want. I can even put them into an installer so you don't
| > have
| > | > to
| > | > | worry about mistakes. Or are you familiar enough with computers
to,
| > say,
| > | > put
| > | > | a couple of files into the C:\ folder, on into the Startup folder,
| > etc.?
| > | > |
| > | > | --
| > | > | Gary S. Terhune
| > | > | MS-MVP Shell/User
| > | > |
www.grystmill.com
| > | > |
| > | > | "PSRumbagh" <PSRumbagh@discussions.microsoft.com> wrote in message
| > | > | news:B4A5F84B-1891-4B49-8AE1-22E3E76FA7E2@microsoft.com...
| > | > | > Not being a computer whiz, I am a little reluctant to mess with
| > the
| > | > | > autoexec.bat file. What happens if I make a typo error when
| > modifying
| > | > the
| > | > | > autoexec.bat file? Will my PC fail to boot? Then what?
| > | > | >
| > | > | > "Gary S. Terhune" wrote:
| > | > | >
| > | > | >> It's difficult to pin down when boot up is "finished", but a
| > rough
| > | > | >> estimate
| > | > | >> is provided by a script in the Startup folder. For shutdown,
you
| > use
| > | > a
| > | > | >> script to initiate shutdown. Both scripts write the date/time
to
| > a
| > | > | >> single,
| > | > | >> mutual file.
| > | > | >>
| > | > | >> How's that for an idea? I even have most of the code written.
But
| > | > you've
| > | > | >> been given a lot of info already, with no seeming result.
What's
| > | > wrong
| > | > | >> with
| > | > | >> the solutions already provided in this forum?
| > | > | >>
| > | > | >> --
| > | > | >> Gary S. Terhune
| > | > | >> MS-MVP Shell/User
| > | > | >>
www.grystmill.com
| > | > | >>
| > | > | >> "PSRumbagh" <PSRumbagh@discussions.microsoft.com> wrote in
| > message
| > | > | >> news:6509B7DE-669E-423D-BA68-0715655A5F5D@microsoft.com...
| > | > | >> >I would like to produce a (text) file that shows when (date &
| > time)
| > | > | >> >bootup
| > | > | >> >is
| > | > | >> > completed and when shutdown is initiated. The file needs to
| > append
| > | > | >> > itself
| > | > | >> > everytime bootup and shutdown occurs, i.e the file grows
bigger
| > | > with
| > | > | >> > time.
| > | > | >> > For example, over a year period the file will probably have
| > many
| > | > | >> > hundreds
| > | > | >> > of
| > | > | >> > entries in it. The program must NOT delete previous entries.
| > Any
| > | > | >> > suggestions?
| > | > | >>
| > | > | >>
| > | > |
| > | >
| > | >
| > |
| >
| >
|