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 5 of 27, items 121 to 150 of 799.

Microsoft Exchange Server 2010 Requirements : Software Requirements (part 1) - Additional Software

There are a few additional pieces of software that you will need to ensure are installed on Windows Server 2008 SP2 or R2 in addition to Exchange Server 2010:

Microsoft Exchange Server 2010 Requirements : Getting the Right Server Hardware (part 3) - Disk Requirements

When calculating disk requirements for some applications, it is easy to decide that a single 500 GB hard disk will solve your storage needs. You might be tempted to think the same thing about Exchange Server.

Microsoft Exchange Server 2010 Requirements : Getting the Right Server Hardware (part 2) - Memory Recommendations, Network Requirements

As mentioned previously, the advantage that Exchange Server gets out of the x64 architecture is the ability to access more physical memory. Additional physical memory improves caching, reduces the disk I/O profile, and allows for the addition of more features.

Microsoft Exchange Server 2010 Requirements : Getting the Right Server Hardware (part 1) - The Typical User , CPU Recommendations

Exchange Server 2010 only runs on Windows Server 2008 x64 and therefore only on hardware (physical or virtualized hardware) that is capable of supporting the x64 processor extensions.

Upgrading to Sharepoint 2013 : Upgrading Service Applications

In each of these cases the upgrade method is the same. Restore a copy of your SharePoint 2010 database into your SharePoint 2013’s SQL instance and start the service instance.

Upgrading to Sharepoint 2013 : Upgrading Site Collections

After restoring your content database in SQL, testing it against your SharePoint 2013 web application, and mounting it in SharePoint, you’re in the home stretch. You’re so close you can almost smell that newly upgraded SharePoint 2013 site collection.

Upgrading to Sharepoint 2013 : Upgrading Content (part 4) - Attaching the Content Database

To satisfy your curiosity about what happened during the upgrade, SharePoint 2013 does a thorough job documenting the process. Each time a database is upgraded it creates two log files.

Upgrading to Sharepoint 2013 : Upgrading Content (part 3) - Fixing the Issues, Additional Parameters

When you’re looking at the output of Test-SPContentDatabase you should start at the top, because fixing issues there will oftentimes fix issues downstream.

Upgrading to Sharepoint 2013 : Upgrading Content (part 2) - Running Test-SPContentDatabase

Now that the databases are restored and configured correctly, you can start testing them to see how nicely they’ll play with SharePoint 2013.

Upgrading to Sharepoint 2013 : Upgrading Content - Creating the Web Application, Testing the Content Database

While there are several steps to successfully upgrade content from SharePoint 2010 to SharePoint 2013, the process is relatively straightforward. This section describes the steps necessary to attach a SharePoint 2010 database to a SharePoint 2013 farm and upgrade it.

Sharepoint 2013 : Developing Integrated Apps for Office and Sharepoint Solutions - The New App Model for Office

In this exercise you first created a network share as a trusted catalog location for storing Apps for Office manifest files. This is essentially an easy way for an enterprise to make Apps for Office available to employees, although it is not the only way.

Overview of Oauth in Sharepoint 2013 : Application Authorization - On-Premises App Authentication with S2S

In some situations an organization might need its SharePoint environment and solutions to be purely on-premises. This could be for security reasons, technical reasons such as in disconnected network situations, or simply because on-premises solutions are the company policy.

Overview of Oauth in Sharepoint 2013 : Application Authorization - Requesting Permissions Dynamically

After an application call to a SharePoint API has been authenticated, the next step in the chain of security processing is to check whether the app and user have the appropriate rights to the resources they are attempting to access.

Overview of Oauth in Sharepoint 2013 : Application Authentication (part 2) - Managing Tokens in Your Application

When an application is launched by a user a context token is passed to it. After this has happened it is up to the application to handle the tokens and potentially store them for future use or pass between app pages.

Overview of Oauth in Sharepoint 2013 : Application Authentication (part 1) - Using TokenHelper

Now that you understand what application identities are and how to create and set them up in SharePoint, you can take a look at how those identities are used as part of the authentication between applications and SharePoint.

Overview of Oauth in Sharepoint 2013 : Creating and Managing Application Identities

In the previous section you saw how applications have an identity as well as users. When an app takes an action in the context of a user, SharePoint records this information.

Overview of Oauth in Sharepoint 2013 : Introduction to OAuth

OAuth is an open standard managed by the Internet Engineering Task Force and is designed to allow applications to access services in a Web-friendly manner on behalf of an application or user.

Sharepoint 2013 : Upgrading to Sharepoint 2013 - Upgrade Considerations (part 3) - Don’t Upgrade Crap

The upgrade process in SharePoint has always been very robust, and that continues with SharePoint 2013. However, there are a few things you can do before your upgrade that will make it go more smoothly and quickly. This section provides some guidance on things you can do to prepare for your upgrade to SharePoint 2013

Sharepoint 2013 : Upgrading to Sharepoint 2013 - Upgrade Considerations (part 2) - What You Can’t Upgrade

Reading the preceding pages, it’s tough to imagine that there isn’t anything that can’t be upgraded to SharePoint 2013. Although the upgrade options are very good, there are a few things that cannot be upgraded.

Sharepoint 2013 : Upgrading to Sharepoint 2013 - Upgrade Considerations (part 1) - What You Can Upgrade

There are many pieces of SharePoint 2010 you may need to upgrade. It’s not all about getting those PowerPoint presentations into your new farm. Here are some different things you can upgrade.

Active Directory 2008 : Managing OUs (part 3) - Delegating Control of OUs

In simple environments, one or a few systems administrators may be responsible for managing all of the settings within Active Directory. For example, a single systems administrator could manage all users within all OUs in the environment.

Active Directory 2008 : Managing OUs (part 2) - Administering Properties of OUs

Although OUs are primarily created for organizational purposes within the Active Directory environment, they have several settings that you can modify.

Active Directory 2008 : Managing OUs (part 1) - Moving, Deleting, and Renaming OUs

The process of moving, deleting, and renaming OUs is a simple one. Exercise7.2 shows how you can easily change and reorganize OUs to reflect changes in the business organization.

Microsoft Lync Server 2013 : Installing the Director Role (part 3) - Install Server

After you’ve browsed to the setup folder using Windows Explorer, the install window might appear behind the current Explorer window. It can be easy to miss this fact, so check the taskbar for the Lync install icon if some time has passed without any screen activity.

Microsoft Lync Server 2013 : Installing the Director Role (part 2) - Creating a Director Pool - Edit Topology, Publish Topology

After the server has been fully prepared for installation, the topology must be edited and published to reflect the new Director pool. This involves both editing the existing topology and then republishing the updated topology so that the Director role can be installed.

Microsoft Lync Server 2013 : Installing the Director Role (part 1) - Prerequisites

Installing the Director role is similar to deploying any other role in Lync Server 2013. Much of the installation process is actually spent completing the prerequisite work, and installing the actual server can be done fairly quickly.

Microsoft Exchange Server 2013 : Creating special-purpose mailboxes (part 10) - Creating public folder mailboxes

Public folders are used to share messages and files in an organization. Public folder trees define the structure of an organization’s public folders. You can make the default public folder tree accessible to users based on criteria you set, and then users can create folders and manage their content.

Microsoft Exchange Server 2013 : Creating special-purpose mailboxes (part 9) - Creating shared mailboxes

Shared mailboxes are mailboxes that are shared by multiple users. Although shared mailboxes must have an associated user account, this account is not used for logon in the domain and is disabled by default. Users who access the shared mailbox do so using access permissions.

Microsoft Exchange Server 2013 : Creating special-purpose mailboxes (part 8) - Creating arbitration mailboxes, Creating Discovery mailboxes

Exchange moderated transport requires all email messages sent to specific recipients to be approved by moderators. You can configure any type of recipient as a moderated recipient, and Exchange will ensure that all messages sent to those recipients go through an approval process.

Microsoft Exchange Server 2013 : Creating special-purpose mailboxes (part 7) - Creating and using archive mailboxes - Creating online archives, Managing archive settings

For bulk editing, you can use Get-Mailbox to retrieve the user mailboxes you want to work with and then apply the changes by piping the results to Set-Mailbox. If you do so, ensure that you filter the results appropriately.