Programing4Us - Enterprise

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

Exchange Server 2010 : Outlook Integration (part 6) - Alert Integration

A SharePoint alert is a notification that will send you an email when some type of change occurs within a SharePoint list or library. This is quite helpful when you consider the vast amount of information that SharePoint can amass.

Exchange Server 2010 : Outlook Integration (part 5) - Task Integration

Tasks play an important role in SharePoint and can be used in a variety of ways. Tasks help project teams and business units centrally manage to-do items. They help ensure these items do not fall through the cracks, increasing accountability.

Exchange Server 2010 : Outlook Integration (part 4) - Contact Integration

SharePoint includes a built-in list template that allows you to create and manage contacts within a website. Columns that are part of this list are all the expected ones, such as First Name, Last Name, Email Address, Company, and Notes. In general, these are the same columns that you find for a contact record within Outlook.

Exchange Server 2010 : Outlook Integration (part 3) - Creating a Meeting Workspace

Related to calendar integration, Outlook also has the ability to create a SharePoint meeting workspace site when creating a meeting request. This makes it easy for a team to centralize agenda files, tasks, meeting attendees, and other details.

Exchange Server 2010 : Outlook Integration (part 2) - Calendar Integration

Shared calendars are a great way to schedule team meetings, reserve resources such as a projector, or just document milestones for a project. Shared calendars have been around for many years with Outlook and Exchange, but times have changed and many now store these shared calendars within SharePoint websites.

Exchange Server 2010 : Outlook Integration (part 1) - Integration Overview

When working with Outlook and SharePoint, you will mostly be connecting to SharePoint lists and libraries. Outlook will then cache a local copy of the list or library into a local PST file.

LINQ to Objects : How to Group Elements (part 6) - ow to Use Grouping Results in the Same Query

It is possible to use grouping results as a local variable within the same query by appending the into clause after the group when using the query expression syntax (when using extension method syntax, you just continue your query from the result of the GroupBy extension method).

LINQ to Objects : How to Group Elements (part 5) - Projecting Grouped Elements into a New Type

The general group by function when using query expression syntax returns the same element type as the source collection elements. If you would like the grouped elements to be in a different form, you must use the extension method syntax and specify your own “element selector” expression.

LINQ to Objects : How to Group Elements (part 4) - Specifying Your Own Key Comparison Function

The default behavior of grouping is to equate key equality using the normal equals comparison for the type being tested. This may not always suit your needs, and it is possible to override this behavior and specify your own grouping function.

LINQ to Objects : How to Group Elements (part 3) - Grouping by Composite Keys

To group using more than one value as the key (often referred to as a composite key), you specify the grouping selector clause as an anonymous type. Any number of key values can be specified in this anonymous type, and any element that contains identical values will dutifully be co-located in a group.

LINQ to Objects : How to Group Elements (part 2) - Specifying a Key to Group By

During evaluation, all elements that share common key values as evaluated by the keySelector expression will be grouped. Value equality is determined using the default Equals operator, although this behavior can be overridden by specifying a custom equality comparison function, as seen shortly.

LINQ to Objects : How to Group Elements (part 1) - Working with Groups

The only property you should rely on is the Key property. Most methods on the underlying Grouping collection type throw a NotSupportedException and should be avoided.

Moving into SAP Functional Development : Gaining Control of Change Control - Change Management Best Practices and Approaches (part 4)

As in testing, documentation, minimizing variables in the SAP landscape, and so on, the concept of workflow is another excellent change management facilitator. One of my SAP customers tells me they enjoy an exceptionally smooth change management process by employing the following “workflow-based” approach to implementing new changes.

Moving into SAP Functional Development : Gaining Control of Change Control - Change Management Best Practices and Approaches (part 3)

The difference between implementing changes correctly and implementing them otherwise can boil down to sound communication. According to the American Heritage Dictionary, 2nd ed. (Boston: Houghton Mifflin, 1982), communication is defined as “the exchange of ideas, messages, or information, as by speech, signals or writing” and represents another best practice for implementing change.

Moving into SAP Functional Development : Gaining Control of Change Control - Change Management Best Practices and Approaches (part 2)

For SAP implementations with multiple productive instances, a similar though more involved strategy is deployed. A “global” development system is recommended, and through a well-managed client strategy, this single development environment services multiple Test/QA, Staging, and production environments.

Moving into SAP Functional Development : Gaining Control of Change Control - Change Management Best Practices and Approaches (part 1)

For most companies, maintaining less of a variety of IT technology—whether this be a certain model of server, or type of disk drive, or version of software package—will cost less in the long run and prove easier to manage than maintaining a mix of products that might better fit each variance and niche-requirement within a particular SAP system landscape.

Moving into SAP Functional Development : Gaining Control of Change Control - An Overview of Change Management

At this point in your SAP implementation, your solution vision has materialized in front of you—the SAP Data Center and quite a number of SAP instances are finally running, and the development team is making solid progress by now.

Performing mySAP.com Component Installations : Addressing General mySAP Post-Installation Tasks

In many ways, completing a mySAP component installation is only the beginning of the installation process; to actually prepare a system to be configured by programmers for use by end users, a wealth of additional post-installation tasks must be addressed.

Programming .NET Components : Working with Threads (part 5) - Thread States, Thread Priority and Scheduling

Each thread is allocated a fixed time slot to run on the CPU and assigned a priority. In addition, each thread is either ready to run or waiting for some event to occur, such as a synchronization object being signaled or a sleep timeout elapsing.

Programming .NET Components : Working with Threads (part 4) - Aborting a Thread

The Thread class provides an Abort( ) method, which can forcefully try to terminate a .NET thread. Calling Abort( ) throws an exception of type ThreadAbortException in the thread being aborted.

Programming .NET Components : Working with Threads (part 3) - Blocking Threads

The Thread class provides a number of methods you can use to block the execution of a thread, similar in their effect to the native mechanisms available to Windows programmers.

Programming .NET Components : Working with Threads (part 2) - Creating Threads

To spawn a new thread, you need to create a new Thread object and associate it with a method that is referred to as the thread method. The new Thread object executes the method on a separate thread.

Programming .NET Components : Working with Threads (part 1)

In .NET, a thread is the basic unit of execution. .NET threads are managed code representations of the underlying threads of the operating system. Under the current version of .NET on Windows, .NET threads map one-to-one to Win32 native threads.

System Center Configuration Manager 2007 : Integrating Virtual Applications (part 3) - Creating Adobe Reader as a Virtual Application in ConfigMgr R2

Prior to creating a virtual application in Configuration Manager 2007 R2, you must activate Application Virtualization, as discussed in the previous section. The second requirement is to have an application sequenced with App-V 4.5.

System Center Configuration Manager 2007 : Integrating Virtual Applications (part 2) - Activating Application Virtualization in ConfigMgr 2007 R2

Although Microsoft Application Virtualization is integrated with ConfigMgr 2007 R2, ConfigMgr does not activate the application virtualization functionality by default.

System Center Configuration Manager 2007 : Integrating Virtual Applications (part 1) - What Is SoftGrid?

SoftGrid provides the ability to virtualize applications running on a desktop. The virtualized application does not install on the client system. These applications are streamed to the client, requiring only SoftGrid client installation to the client system.

Microsoft Lync Server 2010 : Planning for Internal Non-Voice Deployment - Planning for Archiving (part 2)

Many modern datacenters are moving toward virtualizing their workload as much as possible. Lync Server 2010 supports virtualizing all its roles, although it is supported with a lower-rated capacity when virtualization is involved.

Microsoft Lync Server 2010 : Planning for Internal Non-Voice Deployment - Planning for Archiving (part 1)

When planning a non-voice deployment of Lync Server 2010, determine whether archiving is required in the environment. Archiving, from the perspective of Lync Server 2010, is the behavior of capturing IM conversations and conference attachments and storing them in a dedicated database for long-term storage.

Microsoft Lync Server 2010 : Planning for Internal Non-Voice Deployment - Planning for Conferencing

Don’t underestimate the popularity of conferencing. After users know it’s available, it will become extremely popular. Management will love the potential of reducing costs around external conferencing services, too.

Microsoft Lync Server 2010 : Planning for Internal Non-Voice Deployment - Planning for IM

Although instant messaging (IM) is one of the simplest features offered by Lync Server 2010, it is nonetheless important to plan for the implications of supporting this feature. Decisions around remote users, public users, and federated users influence how the environment is architected and deployed.

Microsoft Lync Server 2010 : Planning for Internal Non-Voice Deployment - Planning for Capacity

One of the challenges that faces the new Lync Server 2010 administrator is the eternal question of “How big do I build it?” Luckily, Microsoft offers some guidance, in the following sections, around sizing servers to provide sufficient capacity for various types of deployments.

Microsoft Lync Server 2010 : Planning for Internal Non-Voice Deployment - Determining Your Infrastructure Needs

To build a successful Lync Server 2010 infrastructure to support basic functions such as instant messaging, web conferencing, and group chat, these services need to be built on a stable infrastructure.

Microsoft Lync Server 2010 : Determining the Scope of the Deployment

Lync Server 2010 contains such a wealth of features that planning a deployment, even one limited to internal non-voice features, can seem quite daunting at first. This section provides some guidance that can assist with the process and assist adminstrators in creating a well-thought-out and structured implementation plan.

System Center Configuration Manager 2007 : Creating a Package (part 5) - Forefront Client - Configuring the Package, Adding Programs

The majority of the packages needed for most organizations have existing package definition files, because most major packages now install from MSI files. For those packages that do not have package definition files but do have setup files, the Forefront client example illustrates that you can manually create packages by performing some additional steps. You can often install simple applications with a batch file or a script.

System Center Configuration Manager 2007 : Creating a Package (part 4) - Forefront Client - Using the New Package Wizard

Microsoft Forefront Client Security provides unified virus and spyware protection for Windows platforms. There are several prerequisites prior to deploying the Forefront client. These include a properly installed and configured Forefront Client Security (FCS) management server, an FCS policy for the clients, a Windows update policy for the clients, and access to the Forefront client for packaging.

System Center Configuration Manager 2007 : Creating a Package (part 3) - OpsMgr Client - Configuring the Package Used by the Package Definition File

Using a package definition file provides a solid configuration for building the program required to install the OpsMgr agent. This is just one of the configurations completed with the Create Package from Definition Wizard .

System Center Configuration Manager 2007 : Creating a Package (part 2) - OpsMgr Client - Configuring the Installation Program

You will want to make several changes to the program’s configuration on the General tab for the OpsMgr agent installation. First, add a comment explaining what the program will do

System Center Configuration Manager 2007 : Creating a Package (part 1) - OpsMgr Client - Using the Create Package from Definition Wizard

Operations Manager 2007 is another member of the System Center product family. It monitors the health of applications, servers, and services. OpsMgr requires an agent installation process, which can be accomplished using ConfigMgr. The next sections discuss this process.

Exchange Server 2007 Management and Maintenance Practices : Maintenance Tools for Exchange Server 2007 (part 2) - Active Directory Database Maintenance Using ntdsutil

Exchange Server 2007 uses Windows Server 2003 AD to store all its directory information. As a result, it is important to keep AD as healthy as possible to ensure that Exchange Server 2007 remains reliable and stable.

Exchange Server 2007 Management and Maintenance Practices : Maintenance Tools for Exchange Server 2007 (part 1)

Several new and improved tools are available to administer and manage an Exchange Server 2007 environment. There are Microsoft Management Console snap-ins, an automation and scripting shell, and several tools native to the Windows Server 2003 operating system and the Exchange Server 2007 application.