My IT Blog

Recipient Objects Overview Active Directory objects such as user accounts, contacts and groups become recipient objects when e-mail address information is added to the object. The public folder is another type of recipient object. A public folder does not however usually have its own an email address. Exchange Server 2003 supports the following types of recipient objects: User recipient objects: This recipient object type is created and managed using the Active Directory Users And Computers management console. User recipient objects are associated with the user accounts in the Active Directory domain. Contact recipient objects: This recipient object type is created and managed using the Active Directory Users And Computers management console. Group recipient objects: This recipient object type is created and managed using the Active Directory Users And Computers management console. Public folder recipient objects: This recipient object type is created and managed using

When Active Directory was launched in Windows 2000, one of its key design features was to ease the process of deploying software within an organization. To this end, Microsoft included the ability to deploy and distribute software with Group Policy. IntelliMirror technologies include Group Policy software installation to simplify the management necessary for large quantities of users and computers. The Software Installation and Maintenance component of the IntelliMirror technologies can be used to publish applications over the network. Publishing is the terminology used to make applications available for installation from over the network. The Software Installation and Maintenance component can also automatically install applications based on certain predefined criteria on computers. For instance, applications can be automatically installed on computers based on specific users or groups or it can be automatically installed on specified computers. The Software Installation and Mainte

Domain and forest functional levels provide a means of enabling additional domain and forest-wide Active Directory features, remove outdated backward compatibility in an environment, and improve Active Directory performance and security. In Windows 2000, the terminology for domain functional levels was domain modes. Forests in Windows 2000 have one mode and domains can have the domain mode set as either mixed mode or native mode. With Windows Server 2003 Active Directory came the introduction of the Windows Server 2003 interim functional level and Windows Server 2003 functional level for both domains and forests. The four domain functional levels that can be set for domain controllers are Windows 2000 mixed, Windows 2000 native, Windows Server 2003 interim, and Windows Server 2003. The default domain functional level is Windows 2000 mixed. The three forest functional levels are Windows 2000, Windows Server 2003 interim, and Windows Server 2003. The default forest functional level is

On Overview on Group Policy Before you can consider to even begin planning a Group Policy implementation in your organization, you have to understand a few important aspects of Group Policy. Microsoft initially introduced group policies in Windows NT to assist administrators in managing the desktop configuration settings of users and computers. Windows Server 2000 included hundreds of Group Policy settings which you could configure. Windows Server 2003 offers all the group policies included with Windows 2000 as well as more group policies, which enable you to use new Windows Server 2003 features. Group Policies can be defined as the groupings of user configuration settings and computer configuration settings which can be linked to container type objects in Active Directory, so that they are applied to users and computers. Group Policy is extremely flexible. It contains options for numerous user and computer configuration settings. This includes options for: Computer startup and shu

Authentication in IIS Authentication in IIS verifies whether a user attempting to access a particular website, can indeed access it. Authentication is the process that verifies whether the user can access the site which he/she is attempting to access. The authentication methods which can be used to authenticate users in IIS 6 are listed below. Each authentication method can be used to authenticate users attempting to access Web sites. However, only Anonymous access and Basic Authentication can be used as an authentication method for FTP sites. Anonymous access:  This authentication method is enabled by default for both the Default Web Site and Default FTP Site. Anonymous access allows all anonymous users to access the content of the Web site. Anonymous access is typically utilized for public Web sites which are connected to the Internet. Basic Authentication:  This is the weakest authentication method available for IIS, and should be utilized when you cannot use any other authentica