Monitor system

**Eric Lawrence [MSFT]** · Nov 18 '05, 05:56 AM

Re: Monitor system

The System.Diagnost ics.Process class is your friend, but you'll need to make
sure your ASP.NET worker thread has permissions to enumerate the processes
on the system.

--
Thanks,

Eric Lawrence
Program Manager
Assistance and Worldwide Services

This posting is provided "AS IS" with no warranties, and confers no rights.

"Mark" <anonymous@disc ussions.microso ft.com> wrote in message
news:DDAE4E9E-5FD5-44FE-85BE-1A30314CB5A0@mi crosoft.com...[color=blue]
> I am working on a monitor system - web page that will show what processes[/color]
are running on different computers. How would I get such information? All I
need is a name of a process (title on a taskbar is fine) and whether it's
running or not.[color=blue]
> Am I way of a target? Will appreciate ay idea.
>
> Thanks
>[/color]

**Tommy** · Nov 18 '05, 06:06 AM

Re: Monitor system

I don't think the System.Diagnost ics.Process class will work for Mark
because this is a .NET framework class, and it'll only work on the
server-side. This means it can only enumerate process on the server,
not on the client PC.

I don't think you can enumerate the processes on a PC using a webpage
unless the user downloads some components that can access these
Windows API or .NET API. However, this will defeat the purpose of
using a webpage.

These are just one of those things that cannot be done using webpages
alone. HTML and scripting languages are designed to not have this
capability to protect a user's machine from being compromised.

Tommy,

"Eric Lawrence [MSFT]" <e_lawrence@hot mail.com> wrote in message news:<#IDVa48$D HA.212@TK2MSFTN GP12.phx.gbl>.. .[color=blue]
> The System.Diagnost ics.Process class is your friend, but you'll need to make
> sure your ASP.NET worker thread has permissions to enumerate the processes
> on the system.
>
> --
> Thanks,
>
> Eric Lawrence
> Program Manager
> Assistance and Worldwide Services
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Mark" <anonymous@disc ussions.microso ft.com> wrote in message
> news:DDAE4E9E-5FD5-44FE-85BE-1A30314CB5A0@mi crosoft.com...[color=green]
> > I am working on a monitor system - web page that will show what processes[/color]
> are running on different computers. How would I get such information? All I
> need is a name of a process (title on a taskbar is fine) and whether it's
> running or not.[color=green]
> > Am I way of a target? Will appreciate ay idea.
> >
> > Thanks
> >[/color][/color]

**Mark Goldin** · Nov 18 '05, 06:08 AM

Re: Monitor system

Well, server side will have to acees other servers on the network but not
client computers.

"Tommy" <Websoftwares@H otmail.com> wrote in message
news:a85edaaf.0 403021115.73166 292@posting.goo gle.com...[color=blue]
> I don't think the System.Diagnost ics.Process class will work for Mark
> because this is a .NET framework class, and it'll only work on the
> server-side. This means it can only enumerate process on the server,
> not on the client PC.
>
> I don't think you can enumerate the processes on a PC using a webpage
> unless the user downloads some components that can access these
> Windows API or .NET API. However, this will defeat the purpose of
> using a webpage.
>
> These are just one of those things that cannot be done using webpages
> alone. HTML and scripting languages are designed to not have this
> capability to protect a user's machine from being compromised.
>
> Tommy,
>
> "Eric Lawrence [MSFT]" <e_lawrence@hot mail.com> wrote in message[/color]
news:<#IDVa48$D HA.212@TK2MSFTN GP12.phx.gbl>.. .[color=blue][color=green]
> > The System.Diagnost ics.Process class is your friend, but you'll need to[/color][/color]
make[color=blue][color=green]
> > sure your ASP.NET worker thread has permissions to enumerate the[/color][/color]
processes[color=blue][color=green]
> > on the system.
> >
> > --
> > Thanks,
> >
> > Eric Lawrence
> > Program Manager
> > Assistance and Worldwide Services
> >
> > This posting is provided "AS IS" with no warranties, and confers no[/color][/color]
rights.[color=blue][color=green]
> >
> > "Mark" <anonymous@disc ussions.microso ft.com> wrote in message
> > news:DDAE4E9E-5FD5-44FE-85BE-1A30314CB5A0@mi crosoft.com...[color=darkred]
> > > I am working on a monitor system - web page that will show what[/color][/color][/color]
processes[color=blue][color=green]
> > are running on different computers. How would I get such information?[/color][/color]
All I[color=blue][color=green]
> > need is a name of a process (title on a taskbar is fine) and whether[/color][/color]
it's[color=blue][color=green]
> > running or not.[color=darkred]
> > > Am I way of a target? Will appreciate ay idea.
> > >
> > > Thanks
> > >[/color][/color][/color]

**Eric Lawrence [MSFT]** · Nov 18 '05, 06:09 AM

Re: Monitor system

I suppose his original post was unclear; I assumed from his post that he
wished to create a server monitoring page.

Thanks,

Eric Lawrence
Program Manager
Assistance and Worldwide Services

This posting is provided "AS IS" with no warranties, and confers no rights.

"Tommy" <Websoftwares@H otmail.com> wrote in message
news:a85edaaf.0 403021115.73166 292@posting.goo gle.com...[color=blue]
> I don't think the System.Diagnost ics.Process class will work for Mark
> because this is a .NET framework class, and it'll only work on the
> server-side. This means it can only enumerate process on the server,
> not on the client PC.
>
> I don't think you can enumerate the processes on a PC using a webpage
> unless the user downloads some components that can access these
> Windows API or .NET API. However, this will defeat the purpose of
> using a webpage.
>
> These are just one of those things that cannot be done using webpages
> alone. HTML and scripting languages are designed to not have this
> capability to protect a user's machine from being compromised.
>
> Tommy,
>
> "Eric Lawrence [MSFT]" <e_lawrence@hot mail.com> wrote in message[/color]
news:<#IDVa48$D HA.212@TK2MSFTN GP12.phx.gbl>.. .[color=blue][color=green]
> > The System.Diagnost ics.Process class is your friend, but you'll need to[/color][/color]
make[color=blue][color=green]
> > sure your ASP.NET worker thread has permissions to enumerate the[/color][/color]
processes[color=blue][color=green]
> > on the system.
> >
> > --
> > Thanks,
> >
> > Eric Lawrence
> > Program Manager
> > Assistance and Worldwide Services
> >
> > This posting is provided "AS IS" with no warranties, and confers no[/color][/color]
rights.[color=blue][color=green]
> >
> > "Mark" <anonymous@disc ussions.microso ft.com> wrote in message
> > news:DDAE4E9E-5FD5-44FE-85BE-1A30314CB5A0@mi crosoft.com...[color=darkred]
> > > I am working on a monitor system - web page that will show what[/color][/color][/color]
processes[color=blue][color=green]
> > are running on different computers. How would I get such information?[/color][/color]
All I[color=blue][color=green]
> > need is a name of a process (title on a taskbar is fine) and whether[/color][/color]
it's[color=blue][color=green]
> > running or not.[color=darkred]
> > > Am I way of a target? Will appreciate ay idea.
> > >
> > > Thanks
> > >[/color][/color][/color]

**Mark Goldin** · Nov 18 '05, 06:10 AM

Re: Monitor system

Does that mean I won't be able to access other computers from an aspx page?

"Eric Lawrence [MSFT]" <e_lawrence@hot mail.com> wrote in message
news:O3dyNfMAEH A.1600@tk2msftn gp13.phx.gbl...[color=blue]
> I suppose his original post was unclear; I assumed from his post that he
> wished to create a server monitoring page.
>
> Thanks,
>
> Eric Lawrence
> Program Manager
> Assistance and Worldwide Services
>
> This posting is provided "AS IS" with no warranties, and confers no[/color]
rights.[color=blue]
>
> "Tommy" <Websoftwares@H otmail.com> wrote in message
> news:a85edaaf.0 403021115.73166 292@posting.goo gle.com...[color=green]
> > I don't think the System.Diagnost ics.Process class will work for Mark
> > because this is a .NET framework class, and it'll only work on the
> > server-side. This means it can only enumerate process on the server,
> > not on the client PC.
> >
> > I don't think you can enumerate the processes on a PC using a webpage
> > unless the user downloads some components that can access these
> > Windows API or .NET API. However, this will defeat the purpose of
> > using a webpage.
> >
> > These are just one of those things that cannot be done using webpages
> > alone. HTML and scripting languages are designed to not have this
> > capability to protect a user's machine from being compromised.
> >
> > Tommy,
> >
> > "Eric Lawrence [MSFT]" <e_lawrence@hot mail.com> wrote in message[/color]
> news:<#IDVa48$D HA.212@TK2MSFTN GP12.phx.gbl>.. .[color=green][color=darkred]
> > > The System.Diagnost ics.Process class is your friend, but you'll need[/color][/color][/color]
to[color=blue]
> make[color=green][color=darkred]
> > > sure your ASP.NET worker thread has permissions to enumerate the[/color][/color]
> processes[color=green][color=darkred]
> > > on the system.
> > >
> > > --
> > > Thanks,
> > >
> > > Eric Lawrence
> > > Program Manager
> > > Assistance and Worldwide Services
> > >
> > > This posting is provided "AS IS" with no warranties, and confers no[/color][/color]
> rights.[color=green][color=darkred]
> > >
> > > "Mark" <anonymous@disc ussions.microso ft.com> wrote in message
> > > news:DDAE4E9E-5FD5-44FE-85BE-1A30314CB5A0@mi crosoft.com...
> > > > I am working on a monitor system - web page that will show what[/color][/color]
> processes[color=green][color=darkred]
> > > are running on different computers. How would I get such information?[/color][/color]
> All I[color=green][color=darkred]
> > > need is a name of a process (title on a taskbar is fine) and whether[/color][/color]
> it's[color=green][color=darkred]
> > > running or not.
> > > > Am I way of a target? Will appreciate ay idea.
> > > >
> > > > Thanks
> > > >[/color][/color]
>
>[/color]

**Tommy** · Nov 18 '05, 06:13 AM

Re: Monitor system

I think I was a little confused as well.

An aspx page can only enumerate the process of a machine that is
hosting the web application. That means for every machine that you
want to access, you will need to install the web application on that
machine.

I was assuming that you are trying to host a web application on a
central server, and have each client navigate to an aspx page on the
central server to determine the processes running on each client
machine. As I have mentioned in my earlier post, this is not possible
when the web application is hosted in a central server.

You could, however, determine the processes running on a central
server (not the client) by navigating to an aspx page from a client
machine. Is that what you wanted to do?

I hope this could clarify this.

Tommy,

"Mark Goldin" <markgoldin@com cast.net> wrote in message news:<eIfGouQAE HA.3284@TK2MSFT NGP09.phx.gbl>. ..[color=blue]
> Does that mean I won't be able to access other computers from an aspx page?
>
> "Eric Lawrence [MSFT]" <e_lawrence@hot mail.com> wrote in message
> news:O3dyNfMAEH A.1600@tk2msftn gp13.phx.gbl...[color=green]
> > I suppose his original post was unclear; I assumed from his post that he
> > wished to create a server monitoring page.
> >
> > Thanks,
> >
> > Eric Lawrence
> > Program Manager
> > Assistance and Worldwide Services
> >
> > This posting is provided "AS IS" with no warranties, and confers no[/color]
> rights.[color=green]
> >
> > "Tommy" <Websoftwares@H otmail.com> wrote in message
> > news:a85edaaf.0 403021115.73166 292@posting.goo gle.com...[color=darkred]
> > > I don't think the System.Diagnost ics.Process class will work for Mark
> > > because this is a .NET framework class, and it'll only work on the
> > > server-side. This means it can only enumerate process on the server,
> > > not on the client PC.
> > >
> > > I don't think you can enumerate the processes on a PC using a webpage
> > > unless the user downloads some components that can access these
> > > Windows API or .NET API. However, this will defeat the purpose of
> > > using a webpage.
> > >
> > > These are just one of those things that cannot be done using webpages
> > > alone. HTML and scripting languages are designed to not have this
> > > capability to protect a user's machine from being compromised.
> > >
> > > Tommy,
> > >
> > > "Eric Lawrence [MSFT]" <e_lawrence@hot mail.com> wrote in message[/color][/color]
> news:<#IDVa48$D HA.212@TK2MSFTN GP12.phx.gbl>.. .[color=green][color=darkred]
> > > > The System.Diagnost ics.Process class is your friend, but you'll need[/color][/color]
> to
> make[color=green][color=darkred]
> > > > sure your ASP.NET worker thread has permissions to enumerate the[/color][/color]
> processes[color=green][color=darkred]
> > > > on the system.
> > > >
> > > > --
> > > > Thanks,
> > > >
> > > > Eric Lawrence
> > > > Program Manager
> > > > Assistance and Worldwide Services
> > > >
> > > > This posting is provided "AS IS" with no warranties, and confers no[/color][/color]
> rights.[color=green][color=darkred]
> > > >
> > > > "Mark" <anonymous@disc ussions.microso ft.com> wrote in message
> > > > news:DDAE4E9E-5FD5-44FE-85BE-1A30314CB5A0@mi crosoft.com...
> > > > > I am working on a monitor system - web page that will show what[/color][/color]
> processes[color=green][color=darkred]
> > > > are running on different computers. How would I get such information?[/color][/color]
> All I[color=green][color=darkred]
> > > > need is a name of a process (title on a taskbar is fine) and whether[/color][/color]
> it's[color=green][color=darkred]
> > > > running or not.
> > > > > Am I way of a target? Will appreciate ay idea.
> > > > >
> > > > > Thanks
> > > > >[/color]
> >
> >[/color][/color]

**Mark Goldin** · Nov 18 '05, 06:14 AM

Re: Monitor system

What I want is to have web based monitor that will show some statistics
about processes running on various network servers.

"Tommy" <Websoftwares@H otmail.com> wrote in message
news:a85edaaf.0 403031031.db51d 2d@posting.goog le.com...[color=blue]
> I think I was a little confused as well.
>
> An aspx page can only enumerate the process of a machine that is
> hosting the web application. That means for every machine that you
> want to access, you will need to install the web application on that
> machine.
>
> I was assuming that you are trying to host a web application on a
> central server, and have each client navigate to an aspx page on the
> central server to determine the processes running on each client
> machine. As I have mentioned in my earlier post, this is not possible
> when the web application is hosted in a central server.
>
> You could, however, determine the processes running on a central
> server (not the client) by navigating to an aspx page from a client
> machine. Is that what you wanted to do?
>
> I hope this could clarify this.
>
> Tommy,
>
> "Mark Goldin" <markgoldin@com cast.net> wrote in message[/color]
news:<eIfGouQAE HA.3284@TK2MSFT NGP09.phx.gbl>. ..[color=blue][color=green]
> > Does that mean I won't be able to access other computers from an aspx[/color][/color]
page?[color=blue][color=green]
> >
> > "Eric Lawrence [MSFT]" <e_lawrence@hot mail.com> wrote in message
> > news:O3dyNfMAEH A.1600@tk2msftn gp13.phx.gbl...[color=darkred]
> > > I suppose his original post was unclear; I assumed from his post that[/color][/color][/color]
he[color=blue][color=green][color=darkred]
> > > wished to create a server monitoring page.
> > >
> > > Thanks,
> > >
> > > Eric Lawrence
> > > Program Manager
> > > Assistance and Worldwide Services
> > >
> > > This posting is provided "AS IS" with no warranties, and confers no[/color]
> > rights.[color=darkred]
> > >
> > > "Tommy" <Websoftwares@H otmail.com> wrote in message
> > > news:a85edaaf.0 403021115.73166 292@posting.goo gle.com...
> > > > I don't think the System.Diagnost ics.Process class will work for[/color][/color][/color]
Mark[color=blue][color=green][color=darkred]
> > > > because this is a .NET framework class, and it'll only work on the
> > > > server-side. This means it can only enumerate process on the[/color][/color][/color]
server,[color=blue][color=green][color=darkred]
> > > > not on the client PC.
> > > >
> > > > I don't think you can enumerate the processes on a PC using a[/color][/color][/color]
webpage[color=blue][color=green][color=darkred]
> > > > unless the user downloads some components that can access these
> > > > Windows API or .NET API. However, this will defeat the purpose of
> > > > using a webpage.
> > > >
> > > > These are just one of those things that cannot be done using[/color][/color][/color]
webpages[color=blue][color=green][color=darkred]
> > > > alone. HTML and scripting languages are designed to not have this
> > > > capability to protect a user's machine from being compromised.
> > > >
> > > > Tommy,
> > > >
> > > > "Eric Lawrence [MSFT]" <e_lawrence@hot mail.com> wrote in message[/color]
> > news:<#IDVa48$D HA.212@TK2MSFTN GP12.phx.gbl>.. .[color=darkred]
> > > > > The System.Diagnost ics.Process class is your friend, but you'll[/color][/color][/color]
need[color=blue][color=green]
> > to
> > make[color=darkred]
> > > > > sure your ASP.NET worker thread has permissions to enumerate the[/color]
> > processes[color=darkred]
> > > > > on the system.
> > > > >
> > > > > --
> > > > > Thanks,
> > > > >
> > > > > Eric Lawrence
> > > > > Program Manager
> > > > > Assistance and Worldwide Services
> > > > >
> > > > > This posting is provided "AS IS" with no warranties, and confers[/color][/color][/color]
no[color=blue][color=green]
> > rights.[color=darkred]
> > > > >
> > > > > "Mark" <anonymous@disc ussions.microso ft.com> wrote in message
> > > > > news:DDAE4E9E-5FD5-44FE-85BE-1A30314CB5A0@mi crosoft.com...
> > > > > > I am working on a monitor system - web page that will show what[/color]
> > processes[color=darkred]
> > > > > are running on different computers. How would I get such[/color][/color][/color]
information?[color=blue][color=green]
> > All I[color=darkred]
> > > > > need is a name of a process (title on a taskbar is fine) and[/color][/color][/color]
whether[color=blue][color=green]
> > it's[color=darkred]
> > > > > running or not.
> > > > > > Am I way of a target? Will appreciate ay idea.
> > > > > >
> > > > > > Thanks
> > > > > >
> > >
> > >[/color][/color][/color]

**Eric Lawrence [MSFT]** · Nov 18 '05, 06:15 AM

Re: Monitor system

If each network server exposed its status via a webservice, the ASP.NET page
could call those services and build a status page from them.

If the servers were configured to expose their status via WMI and the
ASP.NET page had permissions to run the query, this would work.

--
Thanks,

Eric Lawrence
Program Manager
Assistance and Worldwide Services

This posting is provided "AS IS" with no warranties, and confers no rights.

"Mark Goldin" <markgoldin@com cast.net> wrote in message
news:O5lbGxXAEH A.3804@TK2MSFTN GP09.phx.gbl...[color=blue]
> What I want is to have web based monitor that will show some statistics
> about processes running on various network servers.
>
> "Tommy" <Websoftwares@H otmail.com> wrote in message
> news:a85edaaf.0 403031031.db51d 2d@posting.goog le.com...[color=green]
> > I think I was a little confused as well.
> >
> > An aspx page can only enumerate the process of a machine that is
> > hosting the web application. That means for every machine that you
> > want to access, you will need to install the web application on that
> > machine.
> >
> > I was assuming that you are trying to host a web application on a
> > central server, and have each client navigate to an aspx page on the
> > central server to determine the processes running on each client
> > machine. As I have mentioned in my earlier post, this is not possible
> > when the web application is hosted in a central server.
> >
> > You could, however, determine the processes running on a central
> > server (not the client) by navigating to an aspx page from a client
> > machine. Is that what you wanted to do?
> >
> > I hope this could clarify this.
> >
> > Tommy,
> >
> > "Mark Goldin" <markgoldin@com cast.net> wrote in message[/color]
> news:<eIfGouQAE HA.3284@TK2MSFT NGP09.phx.gbl>. ..[color=green][color=darkred]
> > > Does that mean I won't be able to access other computers from an aspx[/color][/color]
> page?[color=green][color=darkred]
> > >
> > > "Eric Lawrence [MSFT]" <e_lawrence@hot mail.com> wrote in message
> > > news:O3dyNfMAEH A.1600@tk2msftn gp13.phx.gbl...
> > > > I suppose his original post was unclear; I assumed from his post[/color][/color][/color]
that[color=blue]
> he[color=green][color=darkred]
> > > > wished to create a server monitoring page.
> > > >
> > > > Thanks,
> > > >
> > > > Eric Lawrence
> > > > Program Manager
> > > > Assistance and Worldwide Services
> > > >
> > > > This posting is provided "AS IS" with no warranties, and confers no
> > > rights.
> > > >
> > > > "Tommy" <Websoftwares@H otmail.com> wrote in message
> > > > news:a85edaaf.0 403021115.73166 292@posting.goo gle.com...
> > > > > I don't think the System.Diagnost ics.Process class will work for[/color][/color]
> Mark[color=green][color=darkred]
> > > > > because this is a .NET framework class, and it'll only work on the
> > > > > server-side. This means it can only enumerate process on the[/color][/color]
> server,[color=green][color=darkred]
> > > > > not on the client PC.
> > > > >
> > > > > I don't think you can enumerate the processes on a PC using a[/color][/color]
> webpage[color=green][color=darkred]
> > > > > unless the user downloads some components that can access these
> > > > > Windows API or .NET API. However, this will defeat the purpose of
> > > > > using a webpage.
> > > > >
> > > > > These are just one of those things that cannot be done using[/color][/color]
> webpages[color=green][color=darkred]
> > > > > alone. HTML and scripting languages are designed to not have this
> > > > > capability to protect a user's machine from being compromised.
> > > > >
> > > > > Tommy,
> > > > >
> > > > > "Eric Lawrence [MSFT]" <e_lawrence@hot mail.com> wrote in message
> > > news:<#IDVa48$D HA.212@TK2MSFTN GP12.phx.gbl>.. .
> > > > > > The System.Diagnost ics.Process class is your friend, but you'll[/color][/color]
> need[color=green][color=darkred]
> > > to
> > > make
> > > > > > sure your ASP.NET worker thread has permissions to enumerate the
> > > processes
> > > > > > on the system.
> > > > > >
> > > > > > --
> > > > > > Thanks,
> > > > > >
> > > > > > Eric Lawrence
> > > > > > Program Manager
> > > > > > Assistance and Worldwide Services
> > > > > >
> > > > > > This posting is provided "AS IS" with no warranties, and confers[/color][/color]
> no[color=green][color=darkred]
> > > rights.
> > > > > >
> > > > > > "Mark" <anonymous@disc ussions.microso ft.com> wrote in message
> > > > > > news:DDAE4E9E-5FD5-44FE-85BE-1A30314CB5A0@mi crosoft.com...
> > > > > > > I am working on a monitor system - web page that will show[/color][/color][/color]
what[color=blue][color=green][color=darkred]
> > > processes
> > > > > > are running on different computers. How would I get such[/color][/color]
> information?[color=green][color=darkred]
> > > All I
> > > > > > need is a name of a process (title on a taskbar is fine) and[/color][/color]
> whether[color=green][color=darkred]
> > > it's
> > > > > > running or not.
> > > > > > > Am I way of a target? Will appreciate ay idea.
> > > > > > >
> > > > > > > Thanks
> > > > > > >
> > > >
> > > >[/color][/color]
>
>[/color]

**Tommy** · Nov 18 '05, 06:17 AM

Re: Monitor system

Eric, the WMI solution is very interesting. By using WMI, does that
mean we won't need to install a component on a server to query its
processes?

I had plans to build a component that will monitor my servers at home
as well, so maybe I can just use WMI.

Tommy,

"Eric Lawrence [MSFT]" <e_lawrence@hot mail.com> wrote in message news:<#B6JgnYAE HA.2036@TK2MSFT NGP12.phx.gbl>. ..[color=blue]
> If each network server exposed its status via a webservice, the ASP.NET page
> could call those services and build a status page from them.
>
> If the servers were configured to expose their status via WMI and the
> ASP.NET page had permissions to run the query, this would work.
>
> --
> Thanks,
>
> Eric Lawrence
> Program Manager
> Assistance and Worldwide Services
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
> "Mark Goldin" <markgoldin@com cast.net> wrote in message
> news:O5lbGxXAEH A.3804@TK2MSFTN GP09.phx.gbl...[color=green]
> > What I want is to have web based monitor that will show some statistics
> > about processes running on various network servers.
> >
> > "Tommy" <Websoftwares@H otmail.com> wrote in message
> > news:a85edaaf.0 403031031.db51d 2d@posting.goog le.com...[color=darkred]
> > > I think I was a little confused as well.
> > >
> > > An aspx page can only enumerate the process of a machine that is
> > > hosting the web application. That means for every machine that you
> > > want to access, you will need to install the web application on that
> > > machine.
> > >
> > > I was assuming that you are trying to host a web application on a
> > > central server, and have each client navigate to an aspx page on the
> > > central server to determine the processes running on each client
> > > machine. As I have mentioned in my earlier post, this is not possible
> > > when the web application is hosted in a central server.
> > >
> > > You could, however, determine the processes running on a central
> > > server (not the client) by navigating to an aspx page from a client
> > > machine. Is that what you wanted to do?
> > >
> > > I hope this could clarify this.
> > >
> > > Tommy,
> > >
> > > "Mark Goldin" <markgoldin@com cast.net> wrote in message[/color][/color]
> news:<eIfGouQAE HA.3284@TK2MSFT NGP09.phx.gbl>. ..[color=green][color=darkred]
> > > > Does that mean I won't be able to access other computers from an aspx[/color][/color]
> page?[color=green][color=darkred]
> > > >
> > > > "Eric Lawrence [MSFT]" <e_lawrence@hot mail.com> wrote in message
> > > > news:O3dyNfMAEH A.1600@tk2msftn gp13.phx.gbl...
> > > > > I suppose his original post was unclear; I assumed from his post[/color][/color]
> that
> he[color=green][color=darkred]
> > > > > wished to create a server monitoring page.
> > > > >
> > > > > Thanks,
> > > > >
> > > > > Eric Lawrence
> > > > > Program Manager
> > > > > Assistance and Worldwide Services
> > > > >
> > > > > This posting is provided "AS IS" with no warranties, and confers no[/color][/color]
> rights.[color=green][color=darkred]
> > > > >
> > > > > "Tommy" <Websoftwares@H otmail.com> wrote in message
> > > > > news:a85edaaf.0 403021115.73166 292@posting.goo gle.com...
> > > > > > I don't think the System.Diagnost ics.Process class will work for[/color][/color]
> Mark[color=green][color=darkred]
> > > > > > because this is a .NET framework class, and it'll only work on the
> > > > > > server-side. This means it can only enumerate process on the[/color][/color]
> server,[color=green][color=darkred]
> > > > > > not on the client PC.
> > > > > >
> > > > > > I don't think you can enumerate the processes on a PC using a[/color][/color]
> webpage[color=green][color=darkred]
> > > > > > unless the user downloads some components that can access these
> > > > > > Windows API or .NET API. However, this will defeat the purpose of
> > > > > > using a webpage.
> > > > > >
> > > > > > These are just one of those things that cannot be done using[/color][/color]
> webpages[color=green][color=darkred]
> > > > > > alone. HTML and scripting languages are designed to not have this
> > > > > > capability to protect a user's machine from being compromised.
> > > > > >
> > > > > > Tommy,
> > > > > >
> > > > > > "Eric Lawrence [MSFT]" <e_lawrence@hot mail.com> wrote in message[/color][/color]
> news:<#IDVa48$D HA.212@TK2MSFTN GP12.phx.gbl>.. .[color=green][color=darkred]
> > > > > > > The System.Diagnost ics.Process class is your friend, but you'll[/color][/color]
> need[color=green][color=darkred]
> > > > to
> > > > make
> > > > > > > sure your ASP.NET worker thread has permissions to enumerate the[/color][/color]
> processes[color=green][color=darkred]
> > > > > > > on the system.
> > > > > > >
> > > > > > > --
> > > > > > > Thanks,
> > > > > > >
> > > > > > > Eric Lawrence
> > > > > > > Program Manager
> > > > > > > Assistance and Worldwide Services
> > > > > > >
> > > > > > > This posting is provided "AS IS" with no warranties, and confers[/color][/color]
> no
> rights.[color=green][color=darkred]
> > > > > > >
> > > > > > > "Mark" <anonymous@disc ussions.microso ft.com> wrote in message
> > > > > > > news:DDAE4E9E-5FD5-44FE-85BE-1A30314CB5A0@mi crosoft.com...
> > > > > > > > I am working on a monitor system - web page that will show[/color][/color]
> what
> processes[color=green][color=darkred]
> > > > > > > are running on different computers. How would I get such[/color][/color]
> information?
> All I[color=green][color=darkred]
> > > > > > > need is a name of a process (title on a taskbar is fine) and[/color][/color]
> whether
> it's[color=green][color=darkred]
> > > > > > > running or not.
> > > > > > > > Am I way of a target? Will appreciate ay idea.
> > > > > > > >
> > > > > > > > Thanks
> > > > > > > >
> > > > >
> > > > >[/color]
> >
> >[/color][/color]

**Eric Lawrence [MSFT]** · Nov 18 '05, 06:20 AM

Re: Monitor system

I believe that WMI will enable you to do what you need without additional
components, although you'll have to set up trust between your machines such
that WMI counters are available to your ASP worker process. (Unfortunately,
I have no idea how this is done).

--
Thanks,

Eric Lawrence
Program Manager
Assistance and Worldwide Services

This posting is provided "AS IS" with no warranties, and confers no rights.

"Tommy" <Websoftwares@H otmail.com> wrote in message
news:a85edaaf.0 403040455.52dd5 3d3@posting.goo gle.com...[color=blue]
> Eric, the WMI solution is very interesting. By using WMI, does that
> mean we won't need to install a component on a server to query its
> processes?
>
> I had plans to build a component that will monitor my servers at home
> as well, so maybe I can just use WMI.
>
> Tommy,
>
> "Eric Lawrence [MSFT]" <e_lawrence@hot mail.com> wrote in message[/color]
news:<#B6JgnYAE HA.2036@TK2MSFT NGP12.phx.gbl>. ..[color=blue][color=green]
> > If each network server exposed its status via a webservice, the ASP.NET[/color][/color]
page[color=blue][color=green]
> > could call those services and build a status page from them.
> >
> > If the servers were configured to expose their status via WMI and the
> > ASP.NET page had permissions to run the query, this would work.
> >
> > --
> > Thanks,
> >
> > Eric Lawrence
> > Program Manager
> > Assistance and Worldwide Services
> >
> > This posting is provided "AS IS" with no warranties, and confers no[/color][/color]
rights.[color=blue][color=green]
> >
> >
> > "Mark Goldin" <markgoldin@com cast.net> wrote in message
> > news:O5lbGxXAEH A.3804@TK2MSFTN GP09.phx.gbl...[color=darkred]
> > > What I want is to have web based monitor that will show some[/color][/color][/color]
statistics[color=blue][color=green][color=darkred]
> > > about processes running on various network servers.
> > >
> > > "Tommy" <Websoftwares@H otmail.com> wrote in message
> > > news:a85edaaf.0 403031031.db51d 2d@posting.goog le.com...
> > > > I think I was a little confused as well.
> > > >
> > > > An aspx page can only enumerate the process of a machine that is
> > > > hosting the web application. That means for every machine that you
> > > > want to access, you will need to install the web application on that
> > > > machine.
> > > >
> > > > I was assuming that you are trying to host a web application on a
> > > > central server, and have each client navigate to an aspx page on the
> > > > central server to determine the processes running on each client
> > > > machine. As I have mentioned in my earlier post, this is not[/color][/color][/color]
possible[color=blue][color=green][color=darkred]
> > > > when the web application is hosted in a central server.
> > > >
> > > > You could, however, determine the processes running on a central
> > > > server (not the client) by navigating to an aspx page from a client
> > > > machine. Is that what you wanted to do?
> > > >
> > > > I hope this could clarify this.
> > > >
> > > > Tommy,
> > > >
> > > > "Mark Goldin" <markgoldin@com cast.net> wrote in message[/color]
> > news:<eIfGouQAE HA.3284@TK2MSFT NGP09.phx.gbl>. ..[color=darkred]
> > > > > Does that mean I won't be able to access other computers from an[/color][/color][/color]
aspx[color=blue][color=green]
> > page?[color=darkred]
> > > > >
> > > > > "Eric Lawrence [MSFT]" <e_lawrence@hot mail.com> wrote in message
> > > > > news:O3dyNfMAEH A.1600@tk2msftn gp13.phx.gbl...
> > > > > > I suppose his original post was unclear; I assumed from his post[/color]
> > that
> > he[color=darkred]
> > > > > > wished to create a server monitoring page.
> > > > > >
> > > > > > Thanks,
> > > > > >
> > > > > > Eric Lawrence
> > > > > > Program Manager
> > > > > > Assistance and Worldwide Services
> > > > > >
> > > > > > This posting is provided "AS IS" with no warranties, and confers[/color][/color][/color]
no[color=blue][color=green]
> > rights.[color=darkred]
> > > > > >
> > > > > > "Tommy" <Websoftwares@H otmail.com> wrote in message
> > > > > > news:a85edaaf.0 403021115.73166 292@posting.goo gle.com...
> > > > > > > I don't think the System.Diagnost ics.Process class will work[/color][/color][/color]
for[color=blue][color=green]
> > Mark[color=darkred]
> > > > > > > because this is a .NET framework class, and it'll only work on[/color][/color][/color]
the[color=blue][color=green][color=darkred]
> > > > > > > server-side. This means it can only enumerate process on the[/color]
> > server,[color=darkred]
> > > > > > > not on the client PC.
> > > > > > >
> > > > > > > I don't think you can enumerate the processes on a PC using a[/color]
> > webpage[color=darkred]
> > > > > > > unless the user downloads some components that can access[/color][/color][/color]
these[color=blue][color=green][color=darkred]
> > > > > > > Windows API or .NET API. However, this will defeat the[/color][/color][/color]
purpose of[color=blue][color=green][color=darkred]
> > > > > > > using a webpage.
> > > > > > >
> > > > > > > These are just one of those things that cannot be done using[/color]
> > webpages[color=darkred]
> > > > > > > alone. HTML and scripting languages are designed to not have[/color][/color][/color]
this[color=blue][color=green][color=darkred]
> > > > > > > capability to protect a user's machine from being compromised.
> > > > > > >
> > > > > > > Tommy,
> > > > > > >
> > > > > > > "Eric Lawrence [MSFT]" <e_lawrence@hot mail.com> wrote in[/color][/color][/color]
message[color=blue][color=green]
> > news:<#IDVa48$D HA.212@TK2MSFTN GP12.phx.gbl>.. .[color=darkred]
> > > > > > > > The System.Diagnost ics.Process class is your friend, but[/color][/color][/color]
you'll[color=blue][color=green]
> > need[color=darkred]
> > > > > to
> > > > > make
> > > > > > > > sure your ASP.NET worker thread has permissions to enumerate[/color][/color][/color]
the[color=blue][color=green]
> > processes[color=darkred]
> > > > > > > > on the system.
> > > > > > > >
> > > > > > > > --
> > > > > > > > Thanks,
> > > > > > > >
> > > > > > > > Eric Lawrence
> > > > > > > > Program Manager
> > > > > > > > Assistance and Worldwide Services
> > > > > > > >
> > > > > > > > This posting is provided "AS IS" with no warranties, and[/color][/color][/color]
confers[color=blue][color=green]
> > no
> > rights.[color=darkred]
> > > > > > > >
> > > > > > > > "Mark" <anonymous@disc ussions.microso ft.com> wrote in[/color][/color][/color]
message[color=blue][color=green][color=darkred]
> > > > > > > > news:DDAE4E9E-5FD5-44FE-85BE-1A30314CB5A0@mi crosoft.com...
> > > > > > > > > I am working on a monitor system - web page that will show[/color]
> > what
> > processes[color=darkred]
> > > > > > > > are running on different computers. How would I get such[/color]
> > information?
> > All I[color=darkred]
> > > > > > > > need is a name of a process (title on a taskbar is fine) and[/color]
> > whether
> > it's[color=darkred]
> > > > > > > > running or not.
> > > > > > > > > Am I way of a target? Will appreciate ay idea.
> > > > > > > > >
> > > > > > > > > Thanks
> > > > > > > > >
> > > > > >
> > > > > >
> > >
> > >[/color][/color][/color]

Monitor system

Monitor system

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment