BizTalk Server, Exchange Server 2003, Exchange Server 2010, Sharepoint 2010, Microsoft Dynamics CRM, Microsoft Dynamics GP, Microsoft Dynamics AX, Microsoft Dynamics Sure Step, Microsoft Dynamics NAV Tutorials

Change page: < 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 ... > | Displaying page 4 of 27, items 91 to 120 of 799.

Administering Active Directory 2008 : Creating and Managing Active Directory Objects (part 3) - Understanding Groups, Filtering and Advanced Active Directory Features

Now that you know how to create user accounts, it's time to learn how to create group accounts. As instructors, we are always amazed when students (who work in the IT field) have no idea why they should use groups. This is something every organization should be using.

Administering Active Directory 2008 : Creating and Managing Active Directory Objects (part 2) - Managing Object Properties

Once you've created the necessary Active Directory objects, you'll probably need to make changes to their default properties. In addition to the settings you made when you were creating Active Directory objects, you can configure several more properties

Administering Active Directory 2008 : Creating and Managing Active Directory Objects (part 1) - Overview of Active Directory Objects

When you install and configure a domain controller, Active Directory sets up some organization for you, and you can create and manage several types of objects. This section describes these features.

Sharepoint 2010 : Windows PowerShell Remoting (part 2) - Entering a Remote Session, Running SharePoint 2010 Cmdlets Remotely

This starts an interactive session with a remote computer using CredSSP authentication. During the session, all commands that you type run on the remote host.

Sharepoint 2010 : Windows PowerShell Remoting (part 1)

To run Windows PowerShell remotely, you need to enable Windows Remote Management, which is included in Windows 7 and Windows Server 2008 Release 2. Enabling Windows Remote Management requires administrative privileges.

Sharepoint 2010 : Windows PowerShell Scripts (part 3) - Writing Comment-Based Help Topics in Scripts,Using Functions in Scripts , Customizing Windows PowerShell with Profile Scripts

Cmdlets in Windows PowerShell include a help topic that describes how to use the cmdlets in Windows PowerShell.

Sharepoint 2010 : Windows PowerShell Scripts (part 2) - Executing Scripts, Using Parameters in Scripts

The script starts with a comment, which is preceded by a # sign to indicate it is a comment. Next, it uses the automatic variable $args to display the arguments passed to the script.

Sharepoint 2010 : Windows PowerShell Scripts (part 1) - Setting the Execution Policy

Since there is no User Access Control (UAC) in Windows XP or Windows Server 2003, the Run as Administrator option does not apply to those operating systems.

Sharepoint 2010 : Windows PowerShell Functions

Functions are used in most programming and scripting languages. A function is a named block of code that can be referred to from within Windows PowerShell. When a function’s name is called, the list of statements contained in the function is executed.

Sharepoint 2013 : Security and Policy - SharePoint Users

Most security models assume the existence of users and groups of users. Different users require different sets of permissions to perform their work, depending on the level of access to data in the system.

Sharepoint 2013 : Security and Policy - Permissions and Permission Levels (part 2) - Creating Custom Permission Levels

SharePoint allows site administrators to create their own unique permission levels. For example, perhaps the content owner would like to allow contributor access to items in a list, but prevent deletion of any list item.

Sharepoint 2013 : Security and Policy - Permissions and Permission Levels (part 1)

A single permission in SharePoint is a specific action that a user may take on a securable object. For example—reading the value of a SharePoint list item is a specific permission, often granted to groups of users who need to read lists and their contained items.

Sharepoint 2013 : Security and Policy - Security Administration

The IT department typically played a large role in web site security administration in days of old. For its SharePoint collaboration tool, Microsoft wanted to break this dependency on IT and empower end users—content owners—to have control of the content they create and disseminate to their audience

Installing Exchange Server 2010 : Command-Line Setup (part 2) - Command-Line Server Recovery Options , Command-Line Delegated Server Installation , Installing Language Packs

There may come a time when you have to recover an Exchange server from a backup. This process will involve rebuilding the Windows server, then reinstalling Exchange Server using the Recover Server mode

Installing Exchange Server 2010 : Command-Line Setup (part 1) - Command-Line Installation Options

By and large, the server role installation options are probably the most useful for a typical person installing or configuring Exchange. They are certainly the most numerous.

Installing Exchange Server 2010 : Graphical User Interface Setup

The simplest way to install Exchange Server 2010 is to use the graphical user interface (GUI). The GUI will be sufficient for most Exchange Server installations.

Installing Exchange Server 2010 : Preparing for Exchange 2010 Ahead of Time (part 2) - Preparing the Active Directory Forest,Preparing Additional Domains

To run the forest preparation, you must be logged on with a user who is a member of the Enterprise Admins group. Further, you should run the forest preparation process from a server that is in the same Active Directory site and domain that holds the schema master flexible single master of operations (FSMO) role.

Installing Exchange Server 2010 : Preparing for Exchange 2010 Ahead of Time (part 1) - Existing Exchange Organizations , Preparing the Schema

If you have any Exchange 2003 servers in your organization, you must first prepare each domain so that Exchange Server 2010 can properly communicate with Exchange 2003 and so that Exchange 2003 can access certain newly created attribute sets in Active Directory.

Securing an Exchange Server 2007 Environment : Securing Outlook Web Access

Outlook Web Access (OWA) provides the interface for users to access their mail across the Internet utilizing a web browser. With the implementation of OWA 2003, Microsoft improved the features and performance of the product until it was almost as powerful as the actual Microsoft Outlook client.

Securing an Exchange Server 2007 Environment : Protecting Against Spam (part 2) - Filtering Junk Mail

Both Outlook 2003 and Outlook 2007 allow users to create and manage their own Safe Senders and Blocked Senders. As the name implies, the Safe Senders list is made up of user-defined addresses or domains, and messages from these addresses or domains will never be treated as junk email.

Securing an Exchange Server 2007 Environment : Protecting Against Spam (part 2) - Filtering Junk Mail

This feature has been improved with each new revision and is useful in minimizing the need for end users to configure junk mail filtering options. In fact, junk mail filtering is primarily controlled by Exchange administrators. However, some options can be configured by the users.

Securing an Exchange Server 2007 Environment : Protecting Against Spam (part 1) - Protecting Against Web Beaconing

A common and very popular format for email messages is Hypertext Markup Language, or HTML. This format is so popular because of the rich content that can be presented, including graphics, images, font formatting, and more

Securing an Exchange Server 2007 Environment : Securing Outlook 2007 (part 2) - Encrypting Communications Between Outlook and Exchange , Blocking Attachments

A common and often effective way for viruses and malicious scripts to spread from user to user is through email. When a user receives a message with an attachment, simply opening the attachment can allow the virus to activate and, if proper security measures are not in place, the virus can do damage to the system or spread to other users.

Securing an Exchange Server 2007 Environment : Securing Outlook 2007 (part 1) - Outlook Anywhere

Prior to Exchange Server 2003, Outlook users who needed to connect to Exchange over the Internet had to establish a virtual private network (VPN) connection prior to using Outlook.

Securing an Exchange Server 2007 Environment : Securing Your Windows Environment (part 3) - Keeping Up with Security Patches and Updates

With Windows Server 2003, Windows Vista, and Windows XP, utilities exist that allow you to automate this process and simplify the distribution of updates. Microsoft has provided several options: Windows Update, Microsoft Update, Microsoft Windows Server Update Services (WSUS), and Microsoft Systems Management Server (SMS)

Securing an Exchange Server 2007 Environment : Securing Your Windows Environment (part 2) - Utilizing Security Templates

Security templates are a practical and effective means to apply standardized security policies and configurations to multiple systems in an environment.

Securing an Exchange Server 2007 Environment : Securing Your Windows Environment (part 1) - Windows Server 2003 Security Improvements , Windows Vista Security Improvements

Windows Vista complements Windows Server 2003 from the client perspective by supporting the security features embedded in Windows Server 2003.

Securing an Exchange Server 2007 Environment : Client-Level Secured Messaging - Exchange Server 2007 Client-Level Security Enhancements

As mentioned earlier, Exchange Server 2007 has several improved security features—especially when combined with Outlook 2007.

Microsoft Exchange Server 2010 Requirements : Additional Requirements

In addition to making sure that the hardware and server software can support Exchange Server 2010, there are a few infrastructure requirements that you need to consider.

Microsoft Exchange Server 2010 Requirements : Software Requirements (part 2) - Windows Server Roles and Features

Windows Server 2008 breaks down the additional Windows components into roles and features. Depending on the Exchange 2010 roles, Windows Server 2008 will require additional Windows Server roles and features to be installed.