Let me rephrase the question.

Does IE *have* to be the rendering engine?

If yes, why?  Are you testing IE's (a client's) ability to render a server
response correctly, or are you really trying to monitor the server itself?
 There's likely a big difference here in terms of what is easy to do and
what is not.


On Thu, Oct 31, 2013 at 9:49 PM, Jimmy Tran <[email protected]> wrote:

>  Yes
>
>
> Sent from my Samsung Galaxy S4
>
> -----Original Message-----
> *From:* Richard Stovall [[email protected]]
> *Received:* Thursday, 31 Oct 2013, 6:45pm
> *To:* [email protected] [[email protected]]
> *Subject:* Re: [NTSysADM] RE: test IE uptime?
>
>  Does IE have to be the rendering engine?
>
>
> On Thu, Oct 31, 2013 at 9:05 PM, Jimmy Tran <[email protected]> wrote:
>
>> If there's a cost associated, that may be ok. There really isn't a budget
>> allocated for this but if it's cheaper to buy a software than me writing
>> some scripts that might be a better way to go.
>>
>> You provide some great keywords to do some searching on thanks!
>>
>>
>> Sent from my Samsung Galaxy S4
>>
>> -----Original Message-----
>> *From:* Ken Schaefer [[email protected]]
>> *Received:* Thursday, 31 Oct 2013, 5:56pm
>> *To:* [email protected] [[email protected]]
>> *Subject:* RE: [NTSysADM] RE: test IE uptime?
>>
>>   Well, the basic concept you are looking at is “end user experience
>> monitoring”, as opposed to “component monitoring” (e.g. a server or hard
>> disk) or “service monitoring” (e.g. is a website up)
>>
>>
>>
>> There’s plenty of third party products out there that can simulate client
>> actions – usually via an agent installed on the remote machine. Or you do a
>> “poor man’s” job and do this yourself with a bit of scripting. I assumed
>> you wanted the latter since you didn’t mention any existing tools you have
>> or any budget.
>>
>>
>>
>> Cheers
>>
>> Ken
>>
>>
>>
>> *From:* [email protected] [mailto:
>> [email protected]] *On Behalf Of *Jimmy Tran
>> *Sent:* Friday, 1 November 2013 11:45 AM
>> *To:* [email protected]
>> *Subject:* RE: [NTSysADM] RE: test IE uptime?
>>
>>
>>
>> I will look in to that. Any other ideas?
>>
>> Sent from my Samsung Galaxy S4
>>
>> -----Original Message-----
>> *From:* Ken Schaefer [[email protected]]
>> *Received:* Thursday, 31 Oct 2013, 5:30pm
>> *To:* [email protected] [[email protected]]
>> *Subject:* [NTSysADM] RE: test IE uptime?
>>
>>  Write a little script (e.g. using VBScript and ServerXMLHTTP object)
>> that makes the same HTTP request? You can then log the details to a log
>> file to later analyse.
>>
>>
>>
>> Cheers
>>
>> Ken
>>
>>
>>
>> *From:* [email protected] [
>> mailto:[email protected] <[email protected]>] *On
>> Behalf Of *Jimmy Tran
>> *Sent:* Friday, 1 November 2013 11:21 AM
>> *To:* [email protected]
>> *Subject:* [NTSysADM] test IE uptime?
>>
>>
>>
>> I’ve been tasked with determining a way to document if a web page in IE
>> errors out.  Basically, the page will refresh every 10 seconds with updated
>> data.  I need to find a way to see if the page comes back with a page error
>> or not.  Any ideas out there?  These tests will be performed at kiosks that
>> have no management that have poor internet connectivity.
>>
>>
>>
>> All I can currently measure is system up time, not internet connectivity
>> uptime or page errors in IE.
>>
>>
>>
>> TIA
>>
>>
>>
>> Jimmy
>>
>>
>>
>
>

Reply via email to