IT Tutorials, IT step by step, Product reviews and prices

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

SQL Server 2012 Security : SQL Server Instance Security (part 2) - Server Permissions, Endpoints, User-Defined Server Roles

An endpoint is a point of entry into SQL Server. Prior to SQL Server 2005, if you had a valid SQL Server login, you could connect via TCP/IP, shared memory, or any other protocol that was enabled on the server.

SQL Server 2012 Security : SQL Server Instance Security (part 1) - Creating a SQL Server Login, Server Roles

To create a new SQL Server login from SQL Server Management Studio (SSMS), navigate down the Object Explorer tree to the Logins node, which is a child of the Security node. Right-click, and select the New Login context menu item. This will launch the Login – New dialog box, shown in Figure 1.

SQL Server 2012 Security : Terminology

Safety deposit boxes, if you’re not familiar, are metal boxes of different sizes that store valuables and are located in a vault at a bank. They usually require a key to open them. In addition, a bank will often ask for identification before allowing you to get your box.

Sharepoint 2013 : SharePoint App Security - Establishing app identity by using S2S trusts (part 3) - Developing provider-hosted apps by using S2S trusts

While you are working in a development environment, it is common to use test certificates as opposed to production-grade certificates. The TokenHelper class provides a static method named TrustAllCertificates which can be called if you need to relax the rules used in the certificate verification process.

Sharepoint 2013 : SharePoint App Security - Establishing app identity by using S2S trusts (part 2) - Configuring an S2S trust

The first step in configuring an S2S trust for a provider-hosted app is generating a public/private key pair by creating an X.509 certificate. To obtain an X.509 certificate for use on production servers, it is recommended that you go through an established certification authority (CA) that has experience creating professional-grade certificates.

Sharepoint 2013 : SharePoint App Security - Establishing app identity by using S2S trusts (part 1) - Architecture of an S2S trust

The architecture of an S2S trust is based on a X.509 certificate which contains a public/private key pair. The public and private keys are used to perform asymmetric encryption.

Sharepoint 2013 : SharePoint App Security - Establishing app identity by using OAuth (part 3) - Developing with OAuth - Working with access tokens

In the majority of scenarios, an access token will carry the identity of the current user in addition to the identity of the app itself. However, there are scenarios for which it makes sense to create an access token that contains app identity but not user identity. This type of security token is known as an app-only access token.

Sharepoint 2013 : SharePoint App Security - Establishing app identity by using OAuth (part 2) - Developing with OAuth - Programming with the TokenHelper class

If you plan on developing cloud-hosted apps, you must learn to work with the TokenHelper class. The TokenHelper class provides a public set of static methods for working with several different types of security tokens including context tokens, refresh tokens, and, most importantly, the access tokens.

Sharepoint 2013 : SharePoint App Security - Establishing app identity by using OAuth (part 1) - Understanding app principals

The SharePoint 2013 implementation of the OAuth protocol requires any app using external authentication to have an associated security principal known as an app principal.

Sharepoint 2013 : SharePoint App Security - Managing app permissions

SharePoint 2013 uses app identifiers that are made by combining a GUID that identifies the app instance together with the unique identifier for the hosting tenancy. Each time the SharePoint host environment creates an app permission, it must tag this permission with an app identifier to map it back to an installed instance of an app.

InfoPath with SharePoint 2010 : Dynamically Populate a Repeating Table - Clear Previous Entries

When all the code has been entered into the method properly, previewing the form populates the repeating table based on the selection in the drop-down, as shown in Figure 1.

InfoPath with SharePoint 2010 : Dynamically Populate a Repeating Table - Loop Through the Secondary Data Source , Populate the Repeating Table

The loop is the main component of populating the repeating table. You loop through the secondary data source through the XPathNodeIterator collection (rows) that you defined in the previous section, retrieving the values from each row.

InfoPath with SharePoint 2010 : Dynamically Populate a Repeating Table - Create a Namespace Variable, Access the Secondary Data Source

Coding with InfoPath involves using XML/XPath objects and methods as well as XPath expressions. A key element in using the XML/XPath methods is the namespace that is used for the XML data retrieval

InfoPath with SharePoint 2010 : Dynamically Populate a Repeating Table - Create a Changed Event Method

Creating any methods produces code-behind in your form. For the overall scenario of this chapter, you need to generate a changed event method and place the code within that method.

InfoPath with SharePoint 2010 : Dynamically Populate a Repeating Table - Set Up the Initial Form

The initial form contains at least a selection field and a repeating group of fields to populate. The selection field can be populated by a data source if required. A secondary data source exists to populate the repeating table.

Windows 7 : Managing Application Compatibility (part 6) - Installing and Configuring the Application Compatibility Toolkit

ACT is the primary tool for administrators seeking to research compatibility problems in preparation for a large-scale Windows 7 workstation deployment. Version 5.6 of the package now includes a sample Stock Viewer application that you can use to test some of the included tools.

Windows 7 : Managing Application Compatibility (part 5) - Using the Application Compatibility Toolkit - Compatibility Administrator , Internet Explorer Compatibility Test Tool

The Microsoft Compatibility Exchange is a source for information on application compatibility problems and their possible solutions, which Microsoft maintains and updates on a regular basis.

Windows 7 : Managing Application Compatibility (part 4) - Using the Application Compatibility Toolkit - Application Compatibility Manager

Application Compatibility Manager, shown in Figure 6, is the primary tool for enterprise administrators planning a large-scale deployment. This application enables you to gather information from your workstations and research potential compatibility issues, using Microsoft online resources.

Windows 7 : Managing Application Compatibility (part 3) - Using the Program Compatibility Troubleshooter , Suppressing Compatibility Controls Using Group Policy

For end users that are not conversant with compatibility and emulation issues, Windows 7 includes the Program Compatibility Troubleshooter, which is a wizard-based tool that steps users through the process of identifying the compatibility problems affecting an application.

Windows 7 : Managing Application Compatibility (part 2) - Evaluating Application Incompatibility Solutions - Using Compatibility Modes

It is not unusual for older, legacy applications to have difficulty running on Windows 7. This is especially true for applications designed for Windows XP and earlier versions.

Windows 7 : Managing Application Compatibility (part 1) - Creating an Application Inventory

In an enterprise environment, the most important compatibility issue is identifying the applications that have problems long before the workstation deployment occurs.

Windows 7 : Designing an Application Deployment Strategy (part 3) - Deploying Applications - Selecting an Application Deployment Method

All of the factors discussed in this article so far should contribute to the final decision of how you are going to deploy your selected applications to your workstations. The following sections discuss the options that Windows 7 and Windows Server 2008 R2 make available to you.

Windows 7 : Designing an Application Deployment Strategy (part 2) - Deploying Applications - Using Server-Based Versus Client-Based Applications

The area with the most flexibility in the planning of your application deployment is the method by which you are going to install and run your workstation applications. Windows 7 and Windows Server 2008 R2 provide a variety of application deployment options, and selecting one is in most cases not a decision you want to leave to the end of the workstation deployment project.

Windows 7 : Designing an Application Deployment Strategy (part 1) - Selecting Applications

The first and most obvious step in devising an application deployment strategy is to decide what applications your users need. This is an essential part of the workstation configuration planning that you perform in the early stages of the Windows 7 deployment project.

Sharepoint 2013 : Creating List Views - Modify a View, Delete a View

The easiest way to change a view is to switch to the view that you want to modify, click the three dots next to the view names, and then choose Modify This View

Sharepoint 2013 : Creating List Views - Enable or Disable Selecting Multiple Items in a View, Create Mobile Views

Creating special views that show information in a more compact way is often a good idea to enable mobile device users to see that information more clearly and to more comfortably navigate in it.

Sharepoint 2013 : Creating List Views - Specify the Item Limit for a View

You can specify an item limit on a view. An item limit on a view enables you to either specify the maximum number of items that are displayed in the view or specify the maximum number of items that are displayed in each page in a view.

Exchange Server 2010 : Services Provided by the Client Access Server (part 5) - The Availability Service, Offline Address List Distribution

The Availability service is installed by default as part of the Client Access server role. The primary job of the Availability service is to retrieve free/busy information about other users. Back in Exchange Server 2003, free/busy information was published in a public folder.

Exchange Server 2010 : Services Provided by the Client Access Server (part 4) - Outlook Anywhere , The Autodiscover Service

The Autodiscover service was introduced in Exchange Server 2007. This valuable service, which runs on Client Access servers, provides automatic configuration of Outlook profiles for Outlook 2007 and newer versions.

Exchange Server 2010 : Services Provided by the Client Access Server (part 3) - Exchange Control Panel

The Exchange Control Panel (ECP) is a new virtual directory added in Exchange Server 2010 that provides access to the configuration data for users. The ECP works in conjunction with OWA to provide full browser-based functionality to users and administrators.