Monitor system

[Guest]

I am working on a monitor system - web page that will show what processes 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
Am I way of a target? Will appreciate ay idea

Thank

 

[Eric Lawrence [MSFT]]

The System.Diagnostics.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.

I am working on a monitor system - web page that will show what processes

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.

 

[Tommy]

I don't think the System.Diagnostics.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,

 

[Mark Goldin]

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

I don't think the System.Diagnostics.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]" <[email protected]> wrote in message

The System.Diagnostics.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.

processes
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.

 

[Eric Lawrence [MSFT]]

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.

I don't think the System.Diagnostics.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]" <[email protected]> wrote in message

The System.Diagnostics.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.

processes
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.

 

[Mark Goldin]

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

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.

I don't think the System.Diagnostics.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]" <[email protected]> wrote in message

The System.Diagnostics.Process class is your friend, but you'll need

to

make

 

[Tommy]

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,

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

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.

I don't think the System.Diagnostics.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]" <[email protected]> wrote in message

The System.Diagnostics.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.

I am working on a monitor system - web page that will show what processes
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.
Am I way of a target? Will appreciate ay idea.

Thanks

 

[Mark Goldin]

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

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" <[email protected]> wrote in message

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

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.

I don't think the System.Diagnostics.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]" <[email protected]> wrote in message

The System.Diagnostics.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.

I am working on a monitor system - web page that will show what processes
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.
Am I way of a target? Will appreciate ay idea.

Thanks

 

[Eric Lawrence [MSFT]]

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.

 

[Tommy]

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,

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.

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

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" <[email protected]> wrote in message

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

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.

I don't think the System.Diagnostics.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]" <[email protected]> wrote in message

The System.Diagnostics.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.

I am working on a monitor system - web page that will show

what
processes

are running on different computers. How would I get such

information?
All I

whether
it's

 

[Eric Lawrence [MSFT]]

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.

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]" <[email protected]> wrote in message

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.

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

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" <[email protected]> wrote in message

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

aspx
page?

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.

I don't think the System.Diagnostics.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]" <[email protected]> wrote in

message

The System.Diagnostics.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.

I am working on a monitor system - web page that will show what
processes
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.
Am I way of a target? Will appreciate ay idea.

Thanks