|
NTSet, v1.15b
Soon after beginning to program with Delphi you discover, that with the help of the standard component palette you can create standard applications as similar as two peas. But what if you'd like to use Windows features not included in the Delphi libraries?
Certainly, it is possible to study the documentation on Windows API functions make use of them, but how much time, efforts and money will it take away!
Choose more effecient ways! A constantly extending collection of components — Component Set for Windows NT/2000 — can be a perfect solution for Delphi and C++ Builder programmers. Our component library can help you avoid reinventing the wheel.
Do you need an access control function?
Would't it be better to use the security system of Windows NT, which corresponds to the C2 standard of protection ? The TNTUserMan component enables you to manage groups and single users on the local or remote computer, or in the domain.
Is there a need to keep the program's activity log?
A simple and effective solution will be a use of Windows NT event log. It allows analyzing the log records, categorizing them, timely reacting to any events occurring on the local or network computer. Use the TNTEventLog component to work with Windows NT/2000 event log as simple as with standard TStringList class.
Control of shared resources of computers in the network?
The TNTShare component will solve this task easier than ever before. Shared disks, printers, open files, users who opened them — all this information is available for view and administration. Moreover, you can control the security attributes of the shares, restricting access only to the users or groups you want.
Need an integration with Windows NT services?
Start, stop, configure, services, change their load order, to check out a current state of service, change service access privileges – do it with the TNTServiceManager component. You will be amazed when you discover how much more precisely you can configure services, compared with the standard task Control Panel/Services.
Never before in the field of Windows NT Security so much could have been done so easily…
Please have a look at our TNTFileSecurity component. It can assign “access allowed”, “access denied” and “system audit” attributes to the files on NTFS partitions. The component supports propagation of attributes down the directory hierarchy. It has equal functionality at both design and run time and operates with files on the local and remote disks. It’s just fun to program, when you can play with things at design time!
Have you ever wondered on how vulnerable your Windows NT workstation is?
Having tested our Windows network we discovered that half of all workstations had their registry open for everyone! The system registry has some vital keys which, if tampered with, can undermine security. You can easily monitor the registry on the local or remote computer with our handy TNTRegSecurity component. It is another descendant of the common ancestor of all components which deal with different aspects of Windows NT security.
The privileges issue has always been acute. We have arrived at the solution.
Microsoft Windows NT/2000™ allows you to establish a full range of security levels, from no security at all to the C2 level of security. However, the default configuration is highly relaxed. You may want to change these default settings to protect against accidental or deliberate changes in the way the computer is set up. The TNTPrivilege component allows you to set a desirable configuration of security privileges on a local or remote computer.
Verifying user's credentials against Windows NT domain has always been a pain.
TNTVerifyLogon does exactly what its name suggests: it verifies user's name and password. It uses native Windows technology: The Security Support Provider Interface (SSPI). The beauty of this solution is that it works under Windows 95/98, Windows NT/2000 and does not require any resources to be shared on the server. Easy and effective!
Have you ever wondered how Windows NT Server Manager can find all those servers out there on the networks? Or how to change the minimum length of the password on the remote computer?
Look at the example supplied with the TNTServerInfo component. This is a good framework for an enterprise-scale network administration utility. You can browse domains and servers, you will learn how to enable audit on a local or remote computer, how to reboot an arbitrary computer on the network, how to do a whole lot more of other amazing things. With TNTServerInfo all this is just a few lines of code away.
Communication becomes easier! There are hundreds of reasons why you may want to send a message to a user:
- "Server is coming down for maintenance in 5 minutes".
- "Your logon time is about to expire in 3 minutes. Save your work now."
The TNTMessage component is intended for sending messages over the network. The user of the destination computer will see a message in a pop-up window. This component makes use of Messenger service, which comes with the standard installation of Windows NT and Windows 2000. Additionally, the component allows the management of aliases, so one computer can have more than one "message inbox".
The ability to browse networks, any LAN networks, not
only those from Microsoft, is a nice addition to the collection.
Utilize TNTNetBrowser component to browse network resources: domains, workgroups, Novell servers, network disks and printers.
Make and drop network connections, monitor connection
performance as easily as everything with NTSet: drop and use!
If your organization utilizes Windows 2000 Terminal Services as a centralized application server, TNTerminalAdmin component is right for you.
Use this component to manage terminal services. The component functions start from enumerating user sessions on a local host and embrace all the aspects of Terminal Services API. You may build sophisticated agents that simultaneously control many network servers and react to server events in real time. Make sure to have a look at provided example project: it is an invaluable resource for quick start.
Do you need to start an application on remote computer? Need to do it periodically, or on flexible schedule? Now you can do it in Delphi, even at design time!
TNTaskScheduler component schedules tasks to run on a daily, weekly, monthly schedules. You may run the task once, every time computer boots up, or on every user’s logon. Or, you may use any combination of these options. As with every component in NTSet collection, TNTaskScheduler works against local or remote computers.
Security is everything. Nowadays no one can afford to ignore the network
security.
Use TNTFirewall component to configure firewalls on the Internet enabled
computers. This component allows for easily blocking the undesired network
traffic on Windows XP, Server 20003 or higher operating system. Just don’t
give the hackers a chance.
Do you need to configure group policies on standalone computers or in Active Directory?
Use the TNTGroupPolicy component that provides the following capabilities:
Open a Group Policy on a local or remote computer, or in Active Directory;
Open a Group Policy in read-write or read-only mode;
Read *.adm template files to find the defined registry policies;
List available registry policy settings;
Disable parts of group policy objects: user- or computer-related settings;
Set the status of a registry based policy to "Enabled", "Disabled", or "Not configured";
Modify values of policy's parts;
Rename Group policy objects;
Save the modified policies;
Fire events when local computer detects changes in the group policy;
Create new Group Policy objects in Active Directory;
Delete existing Group Policy objects in Active Directory;
Link Group Policy objects to domains, sites, or organizations units;
Modify properties of GPO links.
The component relies on Windows API interface IGroupPolicyObject to perform its functions.
Take advantage of the component approach when creating applications!
The NT Component Set won't leave any unsolvable tasks for you under Windows NT/2000!
|





Latest Update

Apr, 05 2006
New version supports C++Builder 2006;
Implemented installation procedure for Delphi 2006;
Minor bug fixes.
Previous update (Mar, 02 2006):
Delphi 2006 support.
Minor bug fixes.
Previous update (Oct, 18 2005):
The collection has now 3 new components:
TNTGroupPolicy: configures group policies on standalone computers or in Active Directory; TNTGroupPolicyBrowseDialog browses for existing group policy objects; TNTDirectoryContainer BrowseDialog browses for Active Directory containers.
This version supports Delphi 2005; C++Builder 5.0 is no longer supported.
TNTRegSecurity component got a new property Win64Redirect. When under WOW64, it allows to read either 32- or 64- bit registry.
Help system is redesigned to support both Delphi 2005, and previous Delphi versions.
Minor bug fixes.
Previous update (Jul, 21 2003):
The collection has got new component: TNTFirewall. The component configures the firewalls on the network connections. It works under Windows XP and Windows 2003.
The TNTVerifyLogon component has been completely rewritten. It now allows impersonating as the user whose credentials where successfully verified.
The TNTFileSecurity component has been modified to work under the non-administrative accounts. Now you can use it under regular user accounts to manage the files and folders of that user.
Minor bug fixes.
Previous update (Nov, 19 2002):
The collection has got its 13th component: TNTaskScheduler. The component schedules tasks to run at certain time in the future. Scheduling may be carried out for both local or remote computers.
The source code is Delphi 7 compatible.
TNTService component has been renamed, as discussed in the Support Forums. The new name is TNTServiceManager. The component is located in NTServiceMan.pas unit. The reason for renaming is a name conflict with a component from SvCom collection. Look at "TNTService renamed" section for more information.
TNTServerInfo component has got a new "Disks" property. This property returns list of drives installed on the remote computer.
Support for Delphi 4, C++Builder 4 has been dropped. If you are still using these versions, you may download version 1.12.
Minor bug fixes.
TNTService renamed
TNTService component has been renamed to TNTServiceManager. If you are using this component in your project, you may migrate by following these steps:
1) Make backup copy of your source files.
2) Change Uses section of you *.pas files by replacing "NTService" with "NTServiceMan". It's best to do this operation in notepad, since Delphi may complain about components not found.
3) Open DFM files of the forms that you had TNTservice component on. It is safe to do this operation in Delphi. Search for "TNTService" string and replace it with "TNTServiceManager".
4) Try to compile your project. Delphi compiler will find rest of the places where you have to change TNTService to TNTServiceManager.
If you wish to view the information concerning previous updates
click here.
You may find additional information about the product at the FAQ page.
|