站内搜索
分类列表
本类阅读排行
本类推荐文章
广告
Online CPU Console using a Web Control Library with .NET Security(1)
作者： 来源： 点击： 日期：2007-7-5 0:53:32
ABSTRACT
Administering applications and servers when not connected to the network can be a nightmare, especially when only a few people manage the application. Just imagine going out for an evening on the town and then you’re paged at one o’clock in the morning with an alarming message that your application has gone down. For companies without Virtual Private Networks (VPN) the task is even more difficult because now you must come to the office to rescue your application. Microsoft’s .NET framework provides easily accessible assemblies to read and modify imperative information about any given machine, and most importantly it also provides backwards compatibility to read and modify machines, which are not .NET framework enabled. In this article, Eric Rockenbach shows us how to create a CPU Console administration tool and appropriate secuirty scheme for any machine on our network.
ARTICLE
When not connected to the network, administering applications and servers can be a nightmare, especially when only a few people manage the application. Just imagine going out for an evening on the town and then you're paged at one o'clock in the morning with an alarming message that your application has gone down. For companies without Virtual Private Networks (VPN) the task is even more difficult because now you must come to the office to rescue your application (VPN allows remote access of machines when both machines have the correct software installed). Microsoft's .NET framework provides easily accessible assemblies to read and modify imperative information about any given machine, and most importantly, it also provides backwards compatibility to read and modify machines which are not .NET framework enabled. In this article we see how to create a CPU Console administration tool and appropriate security scheme for any machine on our network.
System Requirements
• Server: Windows 2000, IIS 5.0, .NET Framework, (Server Hosting the CPU Console application)
• Machine to be checked: Windows 2000, NT
• User's workstation: IE 5.0+, Admin Group of Machine, Admin Group of Server, Win 2000 Login account
Assumptions
This article is designed to combine different elements of the .NET framework to meet an important business challenge. We do not assume exposure to the assemblies mentioned, but having exposure to the .NET framework will be helpful, especially when expanding on this article's functionality.
Administering applications and servers when not connected to the network can be a nightmare, especially when only a few people manage the application. Just imagine going out for an evening on the town and then you’re paged at one o’clock in the morning with an alarming message that your application has gone down. For companies without Virtual Private Networks (VPN) the task is even more difficult because now you must come to the office to rescue your application. Microsoft’s .NET framework provides easily accessible assemblies to read and modify imperative information about any given machine, and most importantly it also provides backwards compatibility to read and modify machines, which are not .NET framework enabled. In this article, Eric Rockenbach shows us how to create a CPU Console administration tool and appropriate secuirty scheme for any machine on our network.
ARTICLE
When not connected to the network, administering applications and servers can be a nightmare, especially when only a few people manage the application. Just imagine going out for an evening on the town and then you're paged at one o'clock in the morning with an alarming message that your application has gone down. For companies without Virtual Private Networks (VPN) the task is even more difficult because now you must come to the office to rescue your application (VPN allows remote access of machines when both machines have the correct software installed). Microsoft's .NET framework provides easily accessible assemblies to read and modify imperative information about any given machine, and most importantly, it also provides backwards compatibility to read and modify machines which are not .NET framework enabled. In this article we see how to create a CPU Console administration tool and appropriate security scheme for any machine on our network.
System Requirements
• Server: Windows 2000, IIS 5.0, .NET Framework, (Server Hosting the CPU Console application)
• Machine to be checked: Windows 2000, NT
• User's workstation: IE 5.0+, Admin Group of Machine, Admin Group of Server, Win 2000 Login account
Assumptions
This article is designed to combine different elements of the .NET framework to meet an important business challenge. We do not assume exposure to the assemblies mentioned, but having exposure to the .NET framework will be helpful, especially when expanding on this article's functionality.
Online CPU Console using a Web Control Library with .NET Security(1) 评论