Blog: Windows 2003 Server

When creating or using a custom ADM file in group policies, some options may not be visible.  This is because the setting is considered a "preference" and the settings will not revert if the group policy is removed.  You must uncheck "Only show policy settings that can be fully managed" under the group policy editor's context menu.  (View->Filters).


 
 

  1. From the Start menu, select Programs, Administrative Tools, then Computer Management to start the Computer Management snap-in.
  2. Right-click the root of the tree (Computer Management), and select Properties from the context menu.
  3. Select the Advanced tab.
  4. Click the Startup and Recovery button.
  5. Click the Shut Down button. (Don't worry. You won’t shut anything down at this point.)
  6. From the dialog box, you can select to shut down, reboot, log off, or power down (if supported). You can also choose how to handle hung applications.
  7. Make your selections, and click OK.

If you select Log off Current User from a terminal services session, the application logs off the user at the console, not your session, so choose this option with care.


 

If you are running out of space on the "C" drive on a system, one way to avoid the hassles of rebuilding the system just to gain space is to use the junction point feature of Windows. This will allow you to move entire folders from the C drive to another drive, thus freeing physical space.

There is a Microsoft KB article on how to create and manipulate NTFS junction points and another article with the best practices for Sysvol maintenance.

Windows does not come with a tool for creating junctions.  The Win2K Resource kit includes the linkd program for creating junctions, but if you don't want to purchase that there is a free Sysinternals tool called Junction that can be used to create junction points in Windows.


 

In Active Directory Users and Computers there is an Email Addresses tab that lists email addresses for the user.  One of these (for each protocol) is selected as the Primary.  The primary address will be the one that a user's outgoing email appears to come from.  But there is also a General tab where one can enter an email address for the user. This also causes that user's outgoing email to appear to come from that address.  Normally, changing one also changes the other.  But if you are running Active Directory Users and Computers from a machine that does not have the Exchange Server tools installed, the Email Addresses tab is not there and changing the email address on the General tab will not change the primary.  Actually, anything can be entered in that field on the General tab, even invalid domains.  So it is recommend to always make user account changes on the Exchange server, or at least on a system that has the Exchange server tools installed.  And use the Email Addresses tab to change user's email addresses.

Some email servers perform some verification on the sender's email address and may reject it if the domain is invalid.  Nothing can send a bounce message either because the email address does not work, so the sender will not know the email was not delivered.


 

When installing an application on a terminal server it is necessary to change the server to install mode by running “change user /install” from a command prompt or by performing the install through “Add/Remove Programs.”  After the installation you must run “change user /execute” to bring it out of install mode.  This ensures that the .ini files for the installed application are stored in the Terminal Server system directory.  These files are used as the master copies for the user-specific .ini files. 

Why is this important?  [more]When a user runs an application for the first time, the application looks in the home directory for its .ini files.  If it does not find them in the home directory it will look in the Terminal Server system directory and copy them to the user’s home directory.  If an application is installed while the server is not in install mode, the .ini files will be saved to the home directory.  New users will therefore be unable to pull down the .ini files from the Terminal Server system directory, and the application will not run.