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 18 of 56, items 511 to 540 of 1656.

Windows 7 : Understanding DirectAccess Client Connections (part 2) - Understanding DirectAccess Infrastructure Features

These features include general network infrastructure requirements such as a PKI (including a certification authority and CRL distribution points), domain controllers, IPv6 transition technologies, and DNS servers. A DirectAccess infrastructure also has the elements that form the core of the DirectAccess solution, including DirectAccess clients, DirectAccess servers, and a network location server.

Windows 7 : Understanding DirectAccess Client Connections (part 1) - Understanding DirectAccess and IPv6 Transition Technologies

DirectAccess clients must have globally routable IPv6 addresses. For organizations that are already using a native IPv6 infrastructure, DirectAccess can easily extend this existing infrastructure to DirectAccess client computers. These client computers can also still access Internet resources by using IPv4.

Windows Server 2011 : Managing Remote Access - Fixing Network Problems

In a perfect world, networks would never fail, no one would ever have to change a network card, IP addresses would be automatically assigned and never change, and no one would ever have to try to troubleshoot a network connectivity problem.

Windows Server 2011 : Virtual Private Networks (part 2) - Configure VPN Permissions

By default, only users with the Network Administrator role are enabled for VPN access. To add users, you need to add them to the Windows SBS Virtual Private Network Users security group.

Windows Server 2011 : Virtual Private Networks (part 1) - Enabling VPNs

Enabling VPNs to your SBS network is a simple process. You run the Set Up Virtual Private Networking Wizard from the Windows SBS Console, and you configure your router or firewall for VPN passthrough.

LINQ to SharePoint and SPMetal : Querying Data Using LINQ to SharePoint (part 4) - Joining Tables Using LINQ

Within the LINQ query, the lookup field is of the same type as the item to which it refers. In this case, the ContractReference lookup field is implemented as a property of type HireContract.

LINQ to SharePoint and SPMetal : Querying Data Using LINQ to SharePoint (part 3) - Result Shaping Using LINQ

One of the benefits of LINQ is its ability to shape result sets while still retaining a type-safe output. We can explore this functionality by adding another button to our sample application; this time, label it Basic Result Shaping .

LINQ to SharePoint and SPMetal : Querying Data Using LINQ to SharePoint (part 2) - Performing a Simple Query

Notice a few interesting things about this code sample. First, notice the use of the Log property on the DataContext object. When a TextWriter object is assigned to this property, the CAML that is generated by the LINQ provider will be output to the TextWriter when it is executed.

LINQ to SharePoint and SPMetal : Querying Data Using LINQ to SharePoint (part 1) - Query Limitations

There is one major difference between LINQ to Objects and LINQ to SharePoint, however, and that is the location of the data being queried. For LINQ to SharePoint, the data exists not in memory—as is the case for LINQ to Objects—but in the SharePoint content database.

System Center Configuration Manager 2007 : Client Deployment (part 4) - Client Installation in Image Deployment

Pre-installing the ConfigMgr client into an operating system allows you to get your ConfigMgr client up and running as soon as the image is deployed.

System Center Configuration Manager 2007 : Client Deployment (part 3) - Client Push Installation Wizard

The Client Push Installation Wizard uses the same process as Client Push Installation. The title makes it obvious that the only difference is the wizard itself. It is highly recommended you test deployments using the Client Push Installation Wizard prior to enabling Client Push Installation, because you have more control.

System Center Configuration Manager 2007 : Client Deployment (part 2) - Manual Installation, Client Push Installation

Enable Client Push Installation to deploy the client agent automatically to those systems discovered and assigned to the site. Before enabling Client Push Installation, it is highly recommended you use the Client Push Installation Wizard for testing individual systems and individual collections.

System Center Configuration Manager 2007 : Client Deployment (part 1) - Command-Line Properties

In almost all scenarios, you will call CCMSetup.exe with the appropriate command-line options. CCMSetup.exe then downloads and installs the required components and launches CCMSetup.msi with the proper command-line options.

Troubleshooting Exchange Server 2010 : Troubleshooting Client Connectivity (part 2)

One of the most fundamental changes in Exchange Server 2010 sees the final shift of mailbox access away from the Mailbox server role over to the Client Access server role.

Troubleshooting Exchange Server 2010 : Troubleshooting Client Connectivity (part 1) - Troubleshooting Autodiscover

The most important initial consideration for Outlook client connectivity (specifically Outlook 2007 and the upcoming Outlook 2010) is the Autodiscover service.

Troubleshooting Exchange Server 2010 : Troubleshooting Mail Flow (part 3) - Exchange Mail Flow Troubleshooter

The Mail Flow Troubleshooter section of the Troubleshooting Assistant is shown in Figure 3; yet another handy tool found in the Toolbox, it is a close cousin of the Exchange Best Practices Analyzer and is part of the Exchange Troubleshooting Assistant.

Troubleshooting Exchange Server 2010 : Troubleshooting Mail Flow (part 2) - Message Tracking

Although the title of the message tracking pane seems to indicate that it's processing delivery reports, don't worry: Exchange hasn't been secretly appending delivery reports to every email your users have been sending!

Troubleshooting Exchange Server 2010 : Troubleshooting Mail Flow (part 1) - Queue Viewer in the EMC

The Queue Viewer is located in the Toolbox of the EMC, alongside a number of other useful tools (some of which we'll cover later in this section). A big believer in truth in advertising, the Queue Viewer allows you to, yes, view the contents of the various delivery queues.

SQL Server 2012 : SQL Server Developer Tools (part 2) - Working with SSDT in Offline Mode, Application Versioning

A lot of power from SSDT comes in the offline mode. This is where developers can create projects that are source-code driven as opposed to database driven. To start, let’s create a project based on our UsedCar database.

SQL Server 2012 : SQL Server Developer Tools (part 1) - Working with SSDT in Connected Mode

Once you install SSDT, launch it from the Start Menu. To create a new project, click File, followed by New, and then Project from the main menu bar. Select SQL Server Database Project, and name it UsedCar Application.

Windows Server 2012 : Using the Task Manager for Logging and Debugging - Monitoring Details, Monitoring Services, Related PowerShell Functionality

From the Details tab, shown in Figure 1, you can handle many of the requests available in earlier versions of Task Manager, including ending a task, ending a process tree, setting priority, setting affinity, creating a dump file, opening the file location, or going to the services.

Windows Server 2012 : Using the Task Manager for Logging and Debugging - Monitoring Performance

The Performance tab enables you to view the CPU, memory, and Ethernet usage in graphical form. This information is especially useful when you need a quick view of a CPU or memory performance bottleneck.

Windows Server 2012 : Using the Task Manager for Logging and Debugging - Monitoring Processes

The first tab on the Task Manager, in the detailed view, is the Processes tab. It provides a list of running processes, or image names, on the server. It also measures the performance in simple data format. This information includes CPU percent used and memory allocated to each process.

Microsoft Lync Server 2010 : Virtual Machine Server Configuration

All virtual machines that run a Lync Server 2010 role must have four virtual processors assigned. This is because processing media requires many CPU cycles, so Microsoft recommends dedicating logical cores to each virtual machine.

Microsoft Lync Server 2010 : Host Server Configuration

To avoid Lync Servers being affected by these contention issues, Microsoft recommends providing a dedicated physical adapter for each Lync virtual machine. This ensures that each Lync Server has a direct connection to a switch that can help eliminate jitter or delay problems encountered when sharing adapters.

Microsoft Lync Server 2010 : Lync Server Virtual Topologies (part 2) - Additional Topologies

This section builds on the guidance suggested by Microsoft and offers some additional sample topologies. These have not been performance tested by Microsoft and are only a suggested starting point. Each topology should be thoroughly tested for performance by an organization before being placed into production.

Microsoft Lync Server 2010 : Lync Server Virtual Topologies (part 1) - Standard Edition Example, Enterprise Edition Example

The other topology Microsoft tested is an expanded Enterprise Edition deployment designed for very large organizations. This topology is scaled to support 40,000 users and used seven different virtual hosts. The logical layout of the Enterprise Edition topology is displayed in Figure 2.

LINQ to SharePoint and SPMetal : Deleting Data Using LINQ (part 2) - Ensuring Referential Integrity

In SharePoint, applying referential integrity constraints on a lookup field is optional. Where no constraints are applied, it is possible to delete parent objects without cascading deletes to child objects or even raising an error to indicate that such a delete would invalidate the data structure.

LINQ to SharePoint and SPMetal : Deleting Data Using LINQ (part 1) - Deleting Sample Data

It should be apparent from the comments that this code will delete all the sample data that we created in the preceding code examples. It uses three nested loops to ensure that referential integrity is maintained, and all associated child data is deleted before the parent element is deleted.

LINQ to SharePoint and SPMetal : Adding Data Using LINQ (part 2) - Add On-Hire Assets,Add AssetNotes

You should now have a Windows Forms application with three buttons that can be used to generate some sample data. Run the application, clicking each of the three buttons in turn to add some sample data.