ITP - Business IT Power and Customers use Dotnetnuke also as Presentation Front-End for Inventory-Informations from many different Windows-Clients. ITP use here Custom-Scripts in Windows Startup-Scripts. The Custom Scripts query many Informations (CPU,RAM,Mainboard,Display,Network,Software, Harddisk, Space,...) from the System and send this via XML-HTTP Request to a XML-HTTP-Receiver from ITP.

The XML-HTTP-Receiver put the received Informations in a MS-SQL based Database for further Processes. In Dotnetnuke we can display requested Informations with different Presentations (Tables,Search-Forms, Grafics,..)

Central Scripts:

We publish and set the needed Startup-Scripts with different Group-Policies to the Clients. All Scripts worked with VB-Script and can get with WMI many different Informations from the specified Client.

Scripts Content:

Each Script query the System-Name and all other needed informations via WMI from the Client and create an Strign with a XML-Structure. After completing of the Query the Script send the XML-Structured Information via XML-HTTP-Request to a XML-HTTP-Reciver-Page on a Webserver behind a Firewall.

XML-HTTP-Receiver:

The XML-HTTP-Receiver-Page is a ASP-Page was include many Procedures and Functions. In each Request is also the Type of Data included that the Receiver can interprete the received Informations right. Is all Data from the XML-HTTP-Request received the Receiver-Page query all Informations from the XML-Structure and fill all Data via SQL Stored Procedures in a central Management Database.

Management Database:

The Management Database is seperated from Dotnetnuke Database  to prevent grow of the Dotnetnuke Database. ITP and Customers have a great Datavolume in the Management-Database, when you save your data in the Dotnetnuke your CMS-Database grows fast and your Dotnetnuke-System will work every slower.

We use on the Management-Database Stored Procedures and Jobs to create Statistics from the Real-Time-Data and put this in own Static-Tables, so we have every a fast Performance wenn the Informatiosn is displayed in Dotnetnuke and we save so many System-Resources on the Database-System.   

Presentation:

ITP and Customers use in Dotnetnuke different Modules to get and display the Informations from the Management in Tables, Masks, Search-Forms or Grafics.

Inventory Informations:

Below you see a part of the Inventory-Informations.

• Client-System-Name
• Inventory-Date
• Mainboard
• Bios
• CPU
• Physical Ram
• Free physical RAM
• Virtual Ram
• Free virtual Ram
• HDD
• HDD used Space
• HDD free Space
• Display Adapter
• Dispaly Driver Version
• Display Resolution
• Display Colors
• Network-Card
• Network IP-Adress, Subnet Mask , Gateway, DNS-Servers, Wins-Servers, DHCP-Active or inactive
• Printer with Name, Version and Default-Printer State
• All registered Software-Applications with Name, Manufacturer, Version,..
• and many more

ITP - Business have create a Custom Dotnetnuke Module to view, edit and extend the centralized Antispam-Whitelist for the GFI-Mailessentials Antispam-System. With the own Interface all users with the right Rights can extend the Antispam-Whitelist over the central Portal-Solution from Dotnetnuke.

 

GFI Mailessentials:

The GFI-Software use a simple Access-Database to save Configuration-Values and also the Values for the White-List. GFI offers a own Config Replication-Feature with a own Interface to manage this. Users will not have for each Feature or Service a own Interface or Webapp! The Additional needed Feature is that Users can manage the Whitelist for 2 different Active-Directory domains and 4 different Anti-Span-Sytem with on simple Web-App.

Backend:

We create in the central Management-SQL-Server a new table called AntiSpam_Whitelist, this table holds only the Email-Adress and the Informations abotu the Creation and Creator of each Entry. Each hour runs a Job was replace the data in the GFI-Access-Database with the Data from the central SQL-Table. The hourly Job create for each Antispam-System a own Access-Database because each System have also own Entries about the specified System-Config in the Database.

The Frontent:

We create here an Custom Dotnetnuke-Module was list all Values from a AntiSpam-SQL-Table in the central Management SQL-System  with the additional Creationdate and the Creator-Informations. The users becoms an additional Add-New-Record-Form to add new Entries in the Whitelist. For a faster usability the user have by the creation of new Entries 3 available Actions "Save", "Save and add next", "Cancel". With the Option "Save and add next" is the Entry saved and the User becomes a new clean Form to add the next Entry without a Redirection to the Overview-List.

The End-Result:

User with the right Permissions see the White-List Maintenance-Site in the central Dotnetnuke Portal, add here new needed Entries or better Email-Adresses and see what exist already in the Whitelist. Latest after one hour the Config is replaced on all existing AntiSpam-Systems in the different Active-Directory Domains and different Network-Locations.

A ITP - Customer needs for a simpler Maintenance and Controlling a central Overview of all used Mailbox-Resources in 2 different Active-Directory Domains.

Backend:

We create in the existing central Management-SQL-System a new Table to hold here the Informations about User, Mailbox-Size, Mailbox-Store, Last Logon, Last Logoff and further Informations. We place on each DC in the seperated Active Directory Domains a Job was get the needed Informations via WMI and send this via XML-HTTP-Request to the central Inventory-System. Each sent XML-Structure holds also a Value for the specified AD-Domain, so we can use one Table for more Active-Directories and display this with simple Filter in the Intranet.

Front-End:

Users with the right Permissions can see the Exchange-Mailbox-Overview Site in the existing Dotnetnuke Intranet Portal. The Entries in the displayed Table is sorted based on the used Space in Mailbox. We have extend the displayed List that all Entries was over the allowed Size are RED displayed.

Result:

All Users with the needed Permissions see fast and simple in the Dotnetnuke Intranet all Mailboxes with the used Space and what Users use more Space than allowed  

A ITP Customer needs for the existing Infrastructure with many Switches, Routers, Firewalls, Proxies and other Devices was support Syslog a simple Overview and searchable Interface.

Backend:

In the Infrastrure exist a running Syslog-Services an the zentral Management-System and all Devices are configured to log to this Syslog-Service. The Syslog-Service supports also the Writing in a SQL-Database-Table, so we have change the Config to log in the SQL-Database-Table. We have the Database extend with different Stored-Procedures for Statistic, Query and Archiv-Functions.

Frontent:

We extend the existing Dotnetnuke-Intranet with a Custom Module to display the Syslog-Informations with Date-Sorting, Record-Paging and Search-Forms.

Result:

All Users with the needed Permissions can see all Entries from each Device in the Syslog in the existing Intranet Dotnetnuke Portal. The Users can easy choice the needed Date with a Drop-Down and receive all specified Entries fast in the List. Records was older than one Year is in the same Interface available via Archiv-Display. 

Database-Stats:

Currently the Syslog-Database have 308816694 Records and daily comes 22600 new Records. The Archiv-Features was we have create move Records was older than one Year in the Archiv-Table, so we reduce a extreme grow of the Production-Table.