Note: Sample below may appear distorted but all corresponding word document files contain proper formattingExcerpt from Term Paper:
(an in-depth look at WMI and Instrumentation)
After this is achieved, a 'ManagementPath is created, wherein it will be bound to the WMI class or the '_ namespace class'. The third step is the creation of the 'ManagementClass' object that is achieved by using the scope as well as the path objects that have already been created, or by creating the ManagementClass object and then directly passing along the path specified as '//. / root: namespace.' The WMI class allows the user to avail of an entire list of all class instances for that particular class by calling 'GetInstnaces ()'. When this is a _namespace, then this will be the list of all child namespaces. After this step, the paths and the names of all the namespaces are added together to form the 'tree view'. Since the ManagementClass and ManagementObject classes utilize unmanaged COM objects, 'Dispose' will be used to relieve them. Another advantage of using the WMI script is that adequate security can be applied to each and every namespace. For example, when the user wants to do this, he can open the 'Computer Management' tool in Windows, and go on to the 'Service and Applications', and then to the 'WMI control'.
Herein lies the 'Security' tag of the WMI script, and this can be used to steer through the hierarchy of the namespaces and select the one for which security is required. The several different rights that are available within this framework of working are the execute methods that define the ways in which the user can execute the methods specified by the classes, the full write access that allows the user to read write and delete the access to the WMI classes, the provider write that enables the user to access write rights to dynamic classes, the enable account that grants the user the right to read WMI classes, the remote enable right that enables the user to remotely access the namespace, the remote security that allows the user to have an access to the 'read only' security files and information, and the edit security that permits the user to have a write right to security information. (an in-depth look at WMI and Instrumentation)
What are the advantages, if any, of the Microsoft Windows Management Instrumentation scripting language when it is used in an it corporate department? It is indeed a well-known and accepted fact that all organizations, especially it, are always under constant and permanent pressure to do more with the fewer resources available to them. The company of today is expected to be streamlined and also stripped down to the bare essentials so that there is more cost efficiency and a fewer number of employees doing the same job that many more employees would have had to do in the past, just a few years ago. Automation is a phenomenon that is still in the process of being implemented in quite a few establishments everywhere, and when the it sector is also faced with the lack of automation and also the necessity of making do with less, it is in fact very difficult for it to cope.
The several business demands placed on the corporate developers of the it sector will eventually end up in overpowering them, and this would lead to limited functioning capabilities on their part, wherein the different departmental applications would become postponed in favor of the several core enterprise processes present within the organization, resulting in the inevitable logjam. What can be done to break out of this sort of jam? Microsoft Access can be one of the means of achieving a breakthrough, even though it is a fact that several organizations have prohibited it, stating that if centralized development is possible with the use of one programming language, wherein the data will be stored on the corporate SQL servers, then there is no need for including Microsoft Access in the organization, whereas it will always remain in control. However, the backlog and logjam within the organizations prevent it from actually maintaining steady control, and there is a general consensus that the time has arrived for it to give up at least part of the control.
Today, the end users seem to want immediate completion of their applications, regardless of whether it maintains control or whether there is a lack of resources; this is where Microsoft Access makes it easier. Access provides its clients with a tough and strong department level database engine that will not bind the user into a certain specific technology, especially if the application would have to grow in future. A user of Microsoft Access would have to just track a few thousands of rows of data that have been spread over a few tables. It is a fact that nothing remains in a state of rest or is static in it, and access is possible through quite a few standard interfaces like OLE DB, and ODBC, and it can even be designed in such a manner that it would match the individual user's specific needs. Since the designing and the creation and the implementation of the database application would consume quite a lot of time, it is better if the entire project is handled jointly by the it department as well as the other individual departments of the organization. (Tech Republic Tutorial)
Since the Microsoft Windows Management Instrumentation Technology is actually an implementation of the WBEM proposal for the DMTF's development of the Windows platforms that would extend the DMTF CIM to represent the various objects that exist in the management environments of Windows. The CIM in turn is used to represent both physical as well as logical objects in a unified way within the managed environment of Windows. The Windows Management Instrumentation Technology was created as the implementation of WBEM technologies in order to provide a 'fully integrated operating system support' for the various applications based on the CIM. The basic method of achieving this is by the WMI providing a dependable and constant and consistent expressive and descriptive model of the configuration and the operational and the status levels of the Windows NT® based systems.
This model will not only reduce costs but will also save resources by implementing various management applications that would decrease both the maintenance costs as well as the entire cost of the lifecycle of the Windows NT systems. When the WMI is used in combination with other Windows NT managed services such as the Microsoft Management Console, also known as MMC, it would ultimately serve to simplify the creation of well-integrated management applications, thereby permitting vendors to offer customers extremely efficient and capable management solutions for various enterprises and organizations needing them. In addition, the combination of both local as well as remote processing with the advantage of the SQL-based query language in the information model allows the user to access and find solutions to highly complex management problems within the working environment. Sometimes developers utilize the Visual Basic® or the Windows Scripts to find the similar sort of solutions that are offered by the WMI scripts. (Microsoft Windows Management Instrumentation, advantages to Developers)
It can be stated that the WMI can and does offer a standard uniform model of working for the purpose of both representing and accessing all management information in a manner that developers would find useful in their development of associations between the several different applications and the drivers and the systems and the devices and the management information in the network system. The WMI technology supports the management infrastructure that is needed for the syntax of the CIM, and the Managed Object Format, also known as the MOF, a programming interface. MOF can defines clearly the structure and the contents of the CIM data in machine-readable as well as humanly readable formats, and the WMI is capable of offering a whole range of extremely useful and powerful services such as query-based retrieval of desired information, and the accurate notification of events.
The developer can use the WMI to write out management applications in WMI scripting so that when it is used in an it Corporate Department, it will not only provide access to certain varied machine resources such as 'system memory', available hard disk space, etc., but will also allow the access to application information such as the several different current application installations on a client computer. It will also allow the user to administer information, remotely, as an application. It will be able to process events such as SNMP traps, and the events related to the Windows NT Event Viewer Log. The developer can also create WMI Providers, and this would allow such management information as required, to be exposed to the user from either a source from the network, or from any software application. It will become possible for these forms of WMI enabled resources to be managed by different management applications. (Microsoft Windows Management Instrumentation, advantages to Developers)
The Windows Management Instrumentation Technology will…[continue]
"Microsoft Management Instrumentation Scripting Language" (2004, November 23) Retrieved December 10, 2016, from http://www.paperdue.com/essay/microsoft-management-instrumentation-scripting-59406
"Microsoft Management Instrumentation Scripting Language" 23 November 2004. Web.10 December. 2016. <http://www.paperdue.com/essay/microsoft-management-instrumentation-scripting-59406>
"Microsoft Management Instrumentation Scripting Language", 23 November 2004, Accessed.10 December. 2016, http://www.paperdue.com/essay/microsoft-management-instrumentation-scripting-59406
82). Both desktop and Web widgets have the same basic components. Fundamentally, they use Web compatible formats, even if intended to run in a desktop environment. This means that the core of the widget is HTML and CSS code which contains the actual content of the widget, namely text, linked images/video or content pulled from a server of Web service. Alternatively, the widget content can be created using Flash, although