Yes, you can use the %username% variable in either the Home Folder path, the Profile path, the Terminal Services Home Folder path, or the Terminal Services Profile path. When included in any of these settings, this variable will be replaced with the current user's Netbios name (a.k.a. the Pre-Win2K Logon Name). For example, if a user’s Netbios name is JoanToohey12 and the Home Folder path is set to \\server1\HomeDirShare\%username%, then the resulting Home Folder for that user will become: \\server1\HomeDir Share\JoanToohey12. Also note that if the Home Folder directory does not already exist, ADtoolkit will also create the new Home Directory and will set either default security settings or alternatively whatever settings you specify.

Yes, ADtoolkit is capable of changing all the various name types by changing the appropriate AD attribute using the Modify Users tool. For example, suppose you wish to change the name which shows up in the MMC Users and Computers tool to match the user's Netbios name (a.k.a. the Pre-Win2K logon name). To do so you will need to change the CN portion of their Distinguished name. You can do this by using either the ADtoolkit Common Property called Full name or the AD attribute cn. They both modify the same attribute called cn. Follow the steps below to change a group of users' Full names (or cn) to match the users' Netbios names:

• Run a report on the user's Distinguished Name & Netbios names and save the output to a file.
• Open the output file and change the column called Netbios to either Full Name or cn.
• Import this file into the Modify User tool. Make sure that you have unchecked the box labeled "Import Distinguished Name Only' in the import dialog box.
• Click on Run Simulation, and examine the output. If all went well, then click on Run Now.

This same method can be used to change any of the other user names: Display, Netbios, Logon, First, or Last.

Check the file you’re using to import. To import into the Modify Users tool, you must create a comma separated value (CSV) file, which, at a minimum, must contain the distinguished names of the users to be imported. The CSV file is simply a text file, where the first line of the file contains a comma separated list of field names, and each subsequent line is a record containing the fields specified in the first line.
A sample CSV file would look like:

Distinguished Name, Home Phone, Business Phone
‘CN=Joe Doe,OU=Users,DC=MyDomain,DC=com’, 410-555-1212, 410-555-1213
‘CN=Jane Doe,OU=Users,DC=MyDomain,DC=com’, 410-555-1214, 410-555-1215

This might happen for one of two reasons. First, if you are using a version prior to 2.5 of ADtoolkit or one of its Elements, then whenever the actual attribute for a particular user is empty (i.e. not set) then the report will leave the cell blank for that user. Starting with 2.5, however, the cell will contain the text: <Not Set>.

The second possibility is that the syntax of the attribute is one that ADtoolkit is unable to print, for example, the Logon Hours attribute is not yet handled by ADtoolkit and therefore it prints a blank space. Note that this second possibility rarely happens as most unsupported attributes are clearly marked as unsupported and you will be unable to add them to the report.

Below are step by step directions for executing a pre-existing report. Although the Reporting Engine can work on users, contacts, computers or groups, the directions below are specific to users. The process, however, is identical for the other objects. For instance, to create group reports, simply replace step one with selecting the Group Reports Tool. Or, to create contact reports, replace step one with selecting the Contact Reports Tool.

1. Open the User Reports Tool by selecting the Tools | Users | Reports menu command or shortcut bar icon.
2. Proceed to the Select Domains/OUs tab and click on the Add Domains/OUs button. Browse through the list of Domains and OUs in your network and select one or more container you wish to report on. When you have finished selecting containers click on the OK button.
3. Proceed to the Report Type tab and select a report from the list of existing reports.
4. To write the report out to a CSV file for future reference, proceed to the Report Output File box on the Output tab page and select the Create an Output File checkbox.
5. Since there really is no simulation mode when executing reports, you may now click on the Run Now button or select it from the Run Menu. The Report Users tool will be launched and the report will be created.

ADtoolkit provides a way for administrators to deliver customized tools to other licensed admins within the organization. Below are some of the things you can do with custom tools:

1. Require Data Entry– Allows admins in charge to require users to enter data (without these settings filled, the custom tool will not operate at runtime),
2. Pre-set data - allows admins in charge to pre-fill information that shows up in the distributed version of the custom tool, this information can be changed by the end user,
3. Fill and Disable Data – allows admins in charge to pre-fill information that shows up in the distributed version of the custom tool, this information can not be changed by the end user,
4. Hide Tabs and Group settings – allows admins in charge to hide settings and tabs so that the user will not be able to see options or settings. This will benefit other parts of the organization who may only need to perform specific tasks and need not be bothered by extra information and fields not necessary to perform their tasks.

Once created Custom Tools can be delivered via email or distribution. To distribute the tools, go to the Tools Menu and select Custom Tools | Distribute.