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 9 of 27, items 241 to 270 of 799.

Microsoft Exchange Server 2013 : Bypassing Exchange Admin Center and troubleshooting (part 1) - Bypassing Exchange Admin Center and Exchange Management Shell

The Exchange Management Shell uses remote sessions that run via the PowerShell application running on IIS. Because of this, you often need a way to work directly with Exchange Server, especially when you are trying to diagnose and resolve problems

Microsoft Exchange Server 2013 : Accessing and using Exchange Admin Center (part 4) - Configuring Exchange Admin Center

You can configure Exchange Admin Center for single-server and multiserver environments. In a single-server environment, you use one Client Access server for all of your remote management needs.

Microsoft Exchange Server 2013 : Accessing and using Exchange Admin Center (part 3) - Working with Exchange Server certificates

The services a certificate can be used with include Internet Message Access Protocol (IMAP), Post Office Protocol (POP), SMTP, Internet Information Services (IIS), and Unified Messaging (UM). The default self-signed certificates are assigned services automatically during setup based on the roles installed on the Exchange server.

Microsoft Exchange Server 2013 : Accessing and using Exchange Admin Center (part 2) - Authenticating and proxying connections

When you access Exchange Admin Center in a browser, a lot is happening in the background that you don’t see. Although you access the application using a specific Client Access server in your organization, Client Access servers themselves only act as front-end proxies.

Microsoft Exchange Server 2013 : Accessing and using Exchange Admin Center (part 1) - Accessing Exchange Admin Center

By default, you must use HTTPS to connect. If you don’t, you’ll see an error stating “Access is denied.” Using HTTPS ensures data transmitted between the client browser and the server is encrypted and secured.

Packaging and Deploying Sharepoint 2013 Apps : Deploying an App (part 3) - Autohosted App Deployment

Autohosted application deployment is almost as straightforward as SharePoint-hosted application deployment. This is because SharePoint Online takes care of all the heavy lifting deploying the code and database packages to Azure for you as well as creating and managing client IDs and secrets.

Packaging and Deploying Sharepoint 2013 Apps : Deploying an App (part 2) - Provider-Hosted App Deployment

Provider-hosted applications are the most complex of the three app types because hosting and running the application code is up to the developer, rather than allowing SharePoint and Azure do these things for you.

Packaging and Deploying Sharepoint 2013 Apps : Deploying an App (part 1) - SharePoint-Hosted App Deployment

SharePoint-hosted apps are the simplest of the three app types to package and deploy because of the lack of a code package and associated deployment steps. All that is required is to package the application using the Publish wizard in Visual Studio and then deploy the app to either the Marketplace or an app catalog.

Microsoft Lync Server 2013 Edge Server : Edge Server Administration (part 5) - Managing External Web Conferencing Features

Enabling remote access to the web conferencing features of Lync Server is actually performed with the remote access policies. As long as a user is associated with a policy that enables remote access, the user has web conferencing capabilities through the Edge Server from the Global conferencing policy.

Microsoft Lync Server 2013 Edge Server : Edge Server Administration (part 4) - Managing Public Providers

Similar to managing federation, the Public IM providers can be allowed or blocked when configuring an Edge Server. By default, all the included providers are disabled and must be enabled before users can communicate with contacts in these domains.

Microsoft Lync Server 2013 Edge Server : Edge Server Administration (part 3) - Managing XMPP Federation

Lync Server 2013 now includes an XMPP gateway on the Edge Server and on the Front End Server or Front End Pool. To allow federated connections to XMPP solutions, you must add an XMPP allowed domain.

Microsoft Lync Server 2013 Edge Server : Edge Server Administration (part 2) - Assigning External Access Policies, Managing Federation

After enabling user accounts for federation, administrators can manage the organizations with which they want to federate through Lync Server. If partner discovery lookups are allowed on the Access Edge configuration, all domains are automatically allowed.

Microsoft Lync Server 2013 Edge Server : Edge Server Administration (part 1) - Editing the Global External Access Policy, Creating a New External Access Policy

Even though the remote access services have been enabled on the Access Edge configuration, users must have their account enabled to use these features. This can be done at a global level so that it applies to all users, or it can be configured on a per-site or per-user basis.

Microsoft Lync Server 2013 Edge Server : Edge Server Configuration

This section outlines common configuration tasks for Edge Server pools. Major changes to the Edge Server configuration must be carried out using Lync Server Topology Builder.

Packaging and Deploying Sharepoint 2013 Apps : Packaging and Publishing an App

An app catalog is simply a SharePoint collection based on a particular template. In this exercise you created the catalog site collection via the SharePoint Online tenant admin site. This instructed SharePoint to create the site and configure it to be the catalog for your tenancy. It is now ready for apps to be deployed to it.

Packaging and Deploying Sharepoint 2013 Apps : Anatomy of an App (part 3) - Web Deploy Package, Database Package

If you are building an Autohosted application then the app package produced by Visual Studio will contain a Web deploy package containing your app code and pages.

Packaging and Deploying Sharepoint 2013 Apps : Anatomy of an App (part 2) - Manifest and Assets, SharePoint Solution Package

At the heart of an .app file is the app manifest file. This file is the central location that SharePoint reads from when interrogating an app. The manifest contains things such as the app name, product ID, version, security information, and information about the starting page of the app.

Packaging and Deploying Sharepoint 2013 Apps : Anatomy of an App (part 1)

The fundamental part of an app package is the app.manifest file. As you have seen in this example it is straightforward to open and look around inside an app package.

Exchange Server 2013 : Exchange Clients - Design Considerations (part 3) - Network Usage, Exchange 2013 User Throttling

Network usage for clients became a hot topic with Exchange Server 2010 and even more so with Microsoft Office 365. Exchange 2010 moved the client connection point to the Client Access Server, and that meant that, for the first time, most customers had to use a load balancer with Exchange Server.

Exchange Server 2013 : Exchange Clients - Design Considerations (part 2) - Client Performance

Design teams are typically concerned with two aspects of client performance. First, they are concerned with the performance of the client itself from the end-user perspective.

Exchange Server 2013 : Exchange Clients - Design Considerations (part 1) - Supportability, Security

Connection encryption is the use of encryption technology to secure communication between two or more computers. Typically, an encrypted connection will make use of Public Key Infrastructure (PKI) to issue certificates, which are used to encrypt and decrypt data.

Sharepoint 2013 : Community portals and sites - Managing your community settings

On the Community Settings page, SharePoint 2013 owners and moderators can specify the date the group was established. This date defaults to the date your site was created, but it is intended to define when your community first started as a formal entity.

Sharepoint 2013 : Community portals and sites - Adding users to community sites

Site users can access some of the content of your site when they first discover it. For example, they can discover an existing discussion on your site via a SharePoint search and choose to join the site after they determine the content is relevant to them.

Sharepoint 2013 : Community portals and sites - Adding moderators to community sites

After you have created a SharePoint 2013 community site site collection, you should then choose and assign an initial list of moderators to the site. Unless you are willing to undertake all moderation tasks, you should identify other moderators as early as possible.

Sharepoint 2013 : Community portals and sites - Creating a community site subsite

If you have a collection of similar SharePoint 2013 community sites that are managed by the same group of people, or if you don’t have administrative access to create site collections, you can also create a discussion site as a subsite.

Sharepoint 2013 : Community portals and sites - Creating a community site site collection

The first step for working with community sites is to create your own site. In many companies, there might already be a governance policy in place by which you can request a new site.

Microsoft Lync Server 2013 Edge Server : Edge Server Installation (part 5) - Creating Certificates

Like all other roles in Lync Server, the Edge Server communicates to other servers in the organization using Mutual Transport Layer Security (MTLS). The Edge Server requires two certificates.

Microsoft Lync Server 2013 Edge Server : Edge Server Installation (part 4) - Installing the Edge Server

The process for installing a local configuration store on an Edge Server varies depending on whether an Edge Server is part of the Active Directory domain and can access the configuration store directly.

Microsoft Lync Server 2013 Edge Server : Edge Server Installation (part 3) - Deploying a Load-Balanced Edge Server Pool, Publish the Topology

If you elected to use a single FQDN and IP address for your public edge services, you will be permitted to enter only a single FQDN, and the default ports will be set to 5061, 444, and 443.

Microsoft Lync Server 2013 Edge Server : Edge Server Installation (part 2) - Edit the Topology, Deploying a Single Edge Server Pool

Lync Server 2013 now supports IPv6 addressing for all Edge Server services. If you have configured IPv6 addresses on your Windows Server, you can now configure the Lync Server Topology to use these IPv6 addresses. All services, including the XMPP gateway, support IPv6.