Microsoft Infrastructure Planning and Design

The Infrastructure Planning and Design (IPD) guides are the next version of Windows Server System Reference Architecture. The guides in this series help clarify and streamline design processes for Microsoft infrastructure technologies, with each guide addressing a unique infrastructure technology or scenario.

Version:

1.0

Date published:

5/24/2012

Files in this download

The links in this section correspond to files available for this download. Download the files appropriate for you.

File name	Size
Active Directory Certificate Services.zip	1.9 MB	Download
Active Directory Domain Services.zip	2.2 MB	Download
DirectAccess.zip	2.0 MB	Download
Dynamic Datacenter.zip	3.1 MB	Download
Exchange Online - Evaluating Software-plus-Services.zip	1.6 MB	Download
Exchange Server.zip	2.9 MB	Download
File Services.zip	1.6 MB	Download
Forefront Identity Manager.zip	1.9 MB	Download
Forefront Unified Access Gateway.zip	1.8 MB	Download
Internet Information Services.zip	1.5 MB	Download
IPD - All.zip	62.5 MB	Download
IPD Series Introduction.zip	143 KB	Download
Malware Response.zip	2.2 MB	Download
MED-V.zip	1.9 MB	Download
Microsoft Application Virtualization 4.6.zip	3.0 MB	Download
Print Services.zip	1.5 MB	Download
Remote Desktop Services.zip	2.3 MB	Download
Selecting the Right NAP Architecture.zip	2.8 MB	Download
Selecting the Right Virtualization Technology.zip	1.5 MB	Download
SharePoint Online - Evaluating Software-plus-Services.zip	2.2 MB	Download
SharePoint Server.zip	2.4 MB	Download
SQL Server.zip	2.2 MB	Download
System Center 2012 - Service Manager.zip   New !	2.8 MB	Download
System Center Configuration Manager 2007.zip	1.9 MB	Download
System Center Data Protection Manager 2007.zip	2.1 MB	Download
System Center Operations Manager 2007.zip	2.3 MB	Download
System Center Service Manager 2010.zip	2.7 MB	Download
System Center Virtual Machine Manager 2008.zip	1.3 MB	Download
Terminal Services.zip	1.2 MB	Download
Windows Deployment Services.zip	1.7 MB	Download
Windows Server Virtualization.zip	1.8 MB	Download
Windows User State Virtualization.zip	1.7 MB	Download
Windows_Optimized_Desktop_Scenarios.zip	435 KB	Download

Overview

Infrastructure Planning and Design guides share a common structure, including:

• Definition of the technical decision flow through the planning process.
• Listing of decisions to be made and the commonly available options and considerations.
• Relating the decisions and options to the business in terms of cost, complexity, and other characteristics.
• Framing decisions in terms of additional questions to the business to ensure a comprehensive alignment with the appropriate business landscape.

These guides complement product documentation by focusing on infrastructure design options.

Each guide leads the reader through critical infrastructure design decisions, in the appropriate order, evaluating the available options for each decision against its impact on critical characteristics of the infrastructure. The IPD Series highlights when service and infrastructure goals should be validated with the organization and provides additional questions that should be asked of service stakeholders and decision makers.

IPD consists of the following downloadable packages:

• New! System Center 2012 - Service Manager
• Active Directory Certificate Services
• Active Directory Domain Services
• DirectAccess
• Dynamic Datacenter
• Exchange Online—Evaluating Software-plus-Services
• File Services
• Forefront Identity Manager 2010
• Forefront Unified Access Gateway
• Internet Information Services
• IPD Series Introduction
• Malware Response
• Microsoft Application Virtualization 4.6
• Microsoft Enterprise Desktop Virtualization (MED-V)
• Print Services
• Remote Desktop Services
• Selecting the Right NAP Architecture
• Selecting the Right Virtualization Technology
• SharePoint Online—Evaluating Software-plus-Services
• SharePoint Server 2010
• SQL Server
• System Center Configuration Manager 2007 R3 and Forefront Endpoint Protection
• System Center Data Protection Manager 2007 with SP1
• System Center Operations Manager 2007
• System Center Service Manager
• System Center Virtual Machine Manager 2008
• Terminal Services
• Windows Deployment Services
• Windows Optimized Desktop Scenarios
• Windows Server Virtualization
• Windows User State Virtualization

The guides are available as individual downloads or as a single all-in-one package.

For more information about Infrastructure Planning and Design, read the Frequently Asked Questions.

Send questions or feedback to us directly at mailto:ipdfdbk@microsoft.com?subject=Feedback%20on%20Infrastructure Planning and Design

This posting is provided "AS IS" with no warranties.

[Powershell] Creating your own Windows Powershell Profile - Part 1

---------- Go to Part 2 ----------

 What is the Windows Powershell Profile ? The Windows PowerShell profile is a script file that runs when Windows PowerShell starts up. You can put cmdlets, scripts, functions - any valid Windows PowerShell commands - into this script file. Each time you start Windows PowerShell, this script file will run. That means you can use the profile to set up your Windows PowerShell environment. Typically that would be custom console settings and aliases, but use your imagination and you can come up with other things you’d like to customize in PowerShell before you start working with it.

Where is the profile ? What makes the profile a profile and not a regular script file is the name and location of the file. Type this at your PowerShell command prompt:

1. $profile

In my case, the profile is store in my roaming profile

\\MyServer\folder\HOME02\XXXXX\My Documents\WindowsPowerShell\
but, that built-in variable will return something like this for Windows XP:

C:\Documents and Settings\Account\my documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1
Or this for Windows Vista and Windows Server 2008:

C:\Users\kenmyer\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1
This is the full path to the file that Windows PowerShell will try to run when it starts. Notice we said “try” to run. Here’s an interesting fact: just because you were able to find the profile doesn’t mean it actually exists. $profile is simply a built-in variable that contains the full path to where the profile will be if there is one; the file doesn’t actually have to exist, and, by default. it doesn’t. If you want a profile to run when you start Windows PowerShell, you need to create this file.

Checking if my profile exists:Just execute this at your PowerShell command prompt:

1. Test-Path $profile 

• It return "True" means the profile exist. You can edit it by executing at your PowerShell command prompt:

1. notepad $profile

• It return "False" means the profile doesn't exist. You can create it by executing at your PowerShell command prompt:

1. New-Item -path $profile -type file -force

-path $profile full path set to $profile variable
-type file This tells we’re creating a file.
-force to create the file at the path with no matter.

When done you will be able to edit it with the notepad $profile command. This will open the empty file you have just created in Notepad.

[Powershell] Creating your own Windows Powershell Profile - Part 2 will explain what you can put in your profile - it will be OpsMgr oriented but keep in mind that you can put cmdlets, scripts, functions and any command in powershell.

This posting is provided "AS IS" with no warranties.

[Orchestrator 2012] Technical Documentation Download for System Center 2012 - Orchestrator

This page lists the technical documentation downloads that are available for the Orchestrator component of System Center 2012.

Version:

1.0

Date published:

3/30/2012

Files in this download

The links in this section correspond to files available for this download. Download the files appropriate for you.

File name	Size
SC2012_Orch_Admin.docx	101 KB	Download
SC2012_Orch_Deploy.docx	133 KB	Download
SC2012_Orch_GetStarted.docx	240 KB	Download
SC2012_Orch_OrchConsole.docx	67 KB	Download
SC2012_Orch_RunbookRef.docx	188 KB	Download
SC2012_Orch_Runbooks.docx	147 KB	Download

Overview

The downloadable files listed on this page contain the product documentation for the Orchestrator component of System Center 2012. The available downloads include:

• Getting Started with System Center 2012 - Orchestrator - last updated April 1, 2012
• Deploying System Center 2012 - Orchestrator - last updated April 1, 2012
• Administering System Center 2012 - Orchestrator - last updated April 1, 2012
• Using the Orchestration Console in System Center 2012 - Orchestrator - last updated April 1, 2012
• Using Runbooks in System Center 2012 - Orchestrator - last updated April 1, 2012
• Runbook Activity Reference for System Center 2012 - Orchestrator - last updated April 1, 2012

This technical documentation is also available in the TechNet library.

This posting is provided "AS IS" with no warranties.

[OpsMgr 2012] Technical Documentation Download for System Center 2012 – Operations Manager

This page lists the technical documentation downloads that are available for the Operations Manager component of System Center 2012.

Version:

1.0

Date published:

3/30/2012

Files in this download

The links in this section correspond to files available for this download. Download the files appropriate for you.

File name	Size
SC2012_OpsMgr_Authoring.docx	3.7 MB	Download
SC2012_OpsMgr_Cmdlets.doc	5.0 MB	Download
SC2012_OpsMgr_Deployment.docx	549 KB	Download
SC2012_OpsMgr_Operations.docx	4.0 MB	Download

Overview

The downloadable files listed on this page contain the product documentation for the Operations Manager component of System Center 2012. The available downloads include:

• Authoring Guide for System Center 2012 - Operations Manager - last updated April 1, 2012
• Deployment Guide for System Center 2012 - Operations Manager - last updated April 1, 2012
• Operations Guide for System Center 2012 - Operations Manager - last updated April 1, 2012
• System Center 2012 – Operations Manager Cmdlet Reference - last updated April 1, 2012

This technical documentation is also available in the TechNet Library.

This posting is provided "AS IS" with no warranties.

[SCCM 2012] Technical Documentation Download for System Center 2012 Configuration Manager

This page lists the technical documentation downloads that are available for System Center 2012 Configuration Manager.

Version:

1.0

Date published:

5/29/2012

Files in this download

The links in this section correspond to files available for this download. Download the files appropriate for you.

File name	Size
ConfigMgr2012HelpUpdate.msi	5.1 MB	Download
SC2012_ConfigMgr_DocDownload.docx	2.2 MB	Download
SC2012_ConfigMgr_PDFDownload.pdf	13.7 MB	Download

Overview

The downloadable files listed on this page contain the product documentation for System Center 2012 Configuration Manager. The available file types include:

• CHM (as part of the Help Update Wizard msi) - last updated May 23, 2012
• DOCX - last updated May 23, 2012
• PDF - last updated May 23, 2012

System Center 2012 Configuration Manager Help Update Wizard (v2.0)

Use the help update wizard to install a local copy of the System Center 2012 Configuration Manager Documentation Library (CHM) which contains a copy of the guides in the TechNet documentation library. This is useful if a computer running the Configuration Manager console does not have Internet access or if you want a standalone copy of the documentation in CHM format. If you run the wizard on a computer running the Configuration Manager console, the wizard will install the local version of the help. If you run the wizard on a computer that does not run the Configuration Manager console, you have the option to save the help file (CHM) to a folder you specify. See the product read-me document for more details.

This technical documentation is also available in the TechNet library.

This posting is provided "AS IS" with no warranties.

[OpsMgr 2007R2][OpsMgr 2012] ReSearchThis Management Pack - developed by the Community and released

Release Date: 5/18/2012

Application Description

The ReSearchThis Management Pack is a free Management Pack that is developed by the Community and released, unsupported by Infront Consulting Group.

This management pack provides an easy way to investigate alerts in Operations Manager (and System Center Essentials, and MOM) and search for resolutions which the community has found when the alert occurs.

Updated version of the ReSearch This MP by Cameron Fuller to perform searches on the SystemCenterCentral website

This posting is provided "AS IS" with no warranties.

[Orchestrator 2012] The Orchestrator Runbook Service starts and then stops after 30-60 seconds

Article ID: 2702157 - Last Review: May 8, 2012 - Revision: 3.1


The Orchestrator Runbook Service (orunbook) on a System Center Orchestrator Runbook Server starts successfully but then terminates after 30-60 seconds.

In the System Event Log of the System Center Orchestrator Runbook Server, the following sequence of events will be seen:

Log Name: System
Source: Service Control Manager
Date:
Event ID: 7036
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: <Computer>
Description:
The Orchestrator Runbook Service service entered the running state.

Log Name: System
Source: Service Control Manager
Date:
Event ID: 7036
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: <Computer>
Description:
The Orchestrator Runbook Service service entered the stopped state.

Log Name: System
Source: Service Control Manager
Date:
Event ID: 7023
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: <Computer>
Description:
The Orchestrator Runbook Service service terminated with the following error:
%%-2147467259

Additionally the following may be observed.

When querying the status of the Orchestrator Runbook Service using SC.exe, the following output shows the last exit code when the service is in a stopped state:

C:\Windows\system32>sc query orunbook

SERVICE_NAME: orunbook
TYPE : 10 WIN32_OWN_PROCESS
STATE : 1 STOPPED
WIN32_EXIT_CODE : -2147467259 (0x80004005)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

One or more exceptions may be captured in the Orchestrator Runbook Service logging folder on the Orchestrator Runbook Server computer. The default path for these logs is "C:\ProgramData\Microsoft System Center 2012\Orchestrator\RunbookService.exe\Logs".
Cause :
The Orchestrator Runbook Service was not able to connect to the Orchestrator database. This could be due to any of the following reasons:

• The service for the Microsoft SQL Server database instance is not running.
• The hostname for the Microsoft SQL Server database instance does not resolve correctly.
• An incorrect database instance has been configured.
• An incorrect TCP/IP port may have been configured in Orchestrator or in Microsoft SQL Server for the database instance.
• TCP/IP may not be configured as an acceptable binding or an alternative protocol binding may be configured as higher priority causing connections to work from some locations but not others (e.g. local versus remote).
• The user account provided does not have appropriate permissions to the Orchestrator database.

Resolution :
Correct the problem that is preventing the Orchestrator Runbook Service from connecting to the Orchestrator database.

1. Verify the Microsoft SQL Server database instance that hosts the Orchestrator database is running.
2. Verify that the hostname for the Microsoft SQL Server instance is correct and resolves correctly in DNS.
3. Verify that the correct Microsoft SQL Server instance is configured in System Center Orchestrator.
4. Check that the TCP/IP port configured in Microsoft SQL Server for the instance that hosts the Orchestrator database matches the TCP/IP port defined in System Center Orchestrator.
5. Check the protocol configuration for the Microsoft SQL Server instance that hosts the Orchestrator database to ensure communication via TCP/IP is the default protocol.
6. Verify that the user account of the Orchestrator Runbook Service or the SQL User Account is a member of the Microsoft.SystemCenter.Orchestrator.Runtime user role in the Orchestrator database.

More Information :

The Orchestrator Runbook Service will only terminate due to failed connectivity to the Orchestrator database during the service start. Once the service has successfully started with full database connectivity, any future database issues will be captured and logged without the service terminating.

This issue occurs most frequently when the System Center Orchestrator environment is restarted and the Orchestrator Runbook Service starts before the Orchestrator database is fully online. In this case, configuring the Orchestrator Runbook Service Recovery Properties can often automatically remediate the problem by having the service wait a period of time and then attempt to start again.


Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use (http://go.microsoft.com/fwlink/?LinkId=151500) for other considerations.

This posting is provided "AS IS" with no warranties.