Looking for script to measure start-up timings across network.

[Jhutch9923]

So at my company, we have 3500 users who use both PC's and Laptops running Windows 7. My current challenge is finding a way to accurately map the following:

1. Power-on kernel to windows login screen
2. Login screen to desktop initialization (when desktop shows up)
3. Desktop to Internet Explorer's first open (we have it open as part of a script as the last start-up process)
4. Shutdown request to power off kernel.

Currently, we try to time things within event viewer, using splunk to accurately gain point a to point b among the timings. But we have no way to accurately measure #2 and #3 at all. Does anyone have any ideas what i could do to monitor this more accurately?


Thanks!

 

[HarriePateman]

Can i ask why you would want to do this, Coding it would be extremely complex.

And where would you store the output from this?

I mean if you have 2500 people logging on thats 2500 lines of data, then if they all go on the internet that another 2500 lines of data?

Thats a lot of data!

 

[Jhutch9923]

Can i ask why you would want to do this, Coding it would be extremely complex.

And where would you store the output from this?

I mean if you have 2500 people logging on thats 2500 lines of data, then if they all go on the internet that another 2500 lines of data?

Thats a lot of data!

So the data as it stands would get uploaded to an event log manager known as Splunk. Splunk will pull data every 15 minutes or so and sync it with the server for every single machine we have within our network.

As it stands, we have an individual group who does this with a stopwatch, and it could be better to use their time for different things.

 

[HarriePateman]

Thats still a lot of data, you would need more then a script to handle that amount of traffic

Why do you need all this information?

if i was going to script an application to do this, i would still use Timers.

 

[Jhutch9923]

Thats still a lot of data, you would need more then a script to handle that amount of traffic

Why do you need all this information?

if i was going to script an application to do this, i would still use Timers.

This information is key because when we rollout updates into production, we want to make sure we are still within the desired performance times. That traffic won't be hard at all, the event logs are incredibly small in size so it isn't a problem. We have been using splunk like this for years now o_o...