Thursday, May 31, 2012

[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.0Date 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 nameSize
SC2012_Orch_Admin.docx101 KBDownload
SC2012_Orch_Deploy.docx133 KBDownload
SC2012_Orch_GetStarted.docx240 KBDownload
SC2012_Orch_OrchConsole.docx67 KBDownload
SC2012_Orch_RunbookRef.docx188 KBDownload
SC2012_Orch_Runbooks.docx147 KBDownload


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.0Date 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 nameSize
SC2012_OpsMgr_Authoring.docx3.7 MBDownload
SC2012_OpsMgr_Cmdlets.doc5.0 MBDownload
SC2012_OpsMgr_Deployment.docx549 KBDownload
SC2012_OpsMgr_Operations.docx4.0 MBDownload


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.0Date 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 nameSize
ConfigMgr2012HelpUpdate.msi5.1 MBDownload
SC2012_ConfigMgr_DocDownload.docx2.2 MBDownload
SC2012_ConfigMgr_PDFDownload.pdf13.7 MBDownload

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.



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

Wednesday, May 30, 2012

[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.

[OpsMgr 2007R2][OpsMgr 2012] Upgrading from OpsMgr2007R2 to OpsMgr2012 - Process Flow Diagrams

Updated: April 1, 2012

Applies To: System Center 2012 - Operations Manager

Before you upgrade to System Center 2012 – Operations Manager, you must first determine whether all servers in your System Center Operations Manager 2007 R2 management group meet the minimum supported configurations for System Center 2012 – Operations Manager. For more information, see Supported Configurations for System Center 2012 – Operations Manager. You can use a set of process flow diagrams to determine your upgrade path and visualize the process.


The following table lists the process flow diagrams available, along with a description of when each upgrade path should be used.


Condition
Process flow diagramChecklist
When you have a single-server or distributed management group that already meets the minimum supported configuration requirements for System Center 2012 – Operations Manager.Single-Server and Distributed Upgrade (Simple) Process Flow Diagram
Distributed Upgrade (Simple)
When your single-server management group does not yet meet the minimum supported configuration requirements for System Center 2012 – Operations Manager, and requires new hardware.Single-Server Upgrade (Complex) Process Flow DiagramChecklist: Single-Server Upgrade (Complex)
When your distributed management group has one or more servers that do not meet the minimum supported configuration requirements for System Center 2012 – Operations Manager, and might require new hardware.Distributed Upgrade (Complex) Process Flow Diagram
Checklist: Distributed Upgrade (Complex)

Single-Server and Distributed Upgrade (Simple) Process Flow Diagram


Single-Server Upgrade (Complex) Process Flow Diagram



Distributed Upgrade (Complex) Process Flow Diagram



Checklists

Single-Server Upgrade (Simple)
 
TaskReferences
 Import the Upgrade Helper management pack.Import the Upgrade Helper Management Pack
 Review the Operations Manager 2007 R2 event logs.Review the Operations Manager 2007 R2 Event Logs
 Remove agents from Pending Management.Remove Agents from Pending Management
 Check for any active connected consoles to the root management server.Check the Operations Manager 2007 R2 RMS for Active Connected Consoles
 Back up the RMS encryption key (SecureStorageBackup.exe).Back Up the RMS Encryption Key
 Disable all notification subscriptions.Disable Notification Subscriptions
 Stop services or disable any connectors that are installed.Stop Services for Connectors
 Verify that your operational database has enough free space.Verify that the Operational Database Has More than 50 Percent of Free Space
 Verify that you have a supported SQL Server collation on all databases and instances of databases.Verify the SQL Server Collation
 Back up the databases.Back up the Operations Manager Databases
 Upgrade the manually installed agents.Upgrading Manually Installed Agents
 Run the management group upgrade on the root management server.How to Upgrade an Operations Manager 2007 R2 Single-Server Management Group
 Upgrade the push-installed agents.Upgrading Push-Installed Agents
 Re-enable the notification subscriptions.Re-enable the Notification Subscriptions.
 Restart or re-enable the service for any connectors that are installed.Restart the Connector Services
 Update overrides.Update Overrides
 Verify the success of the upgrade.Verify upgrade success


Distributed Upgrade (Simple)
 
TaskReferences
 Import the Upgrade Helper management pack.Import the Upgrade Helper Management Pack
 Move agents that report to the RMS to a secondary management server.How to Move Agents to an Operations Manager 2007 R2 Secondary Management Server (Operations Manager Upgrade)
 Back up the encryption key.Back Up the Encryption Key
 Review the Operations Manager 2007 R2 event logs.Review the Operations Manager 2007 R2 Event Logs
 Remove agents from pending management.Remove Agents from Pending Management
 Verify that you have a supported SQL Server collation on all databases and instances of databases.Verify the SQL Collation
 Upgrade the manually installed agents.Upgrading Manually Installed Agents
 Upgrade the secondary management servers.How to Upgrade a Secondary Management Server from Operations Manager 2007 R2
 Upgrade gateways, if present.How to Upgrade a Gateway Server from Operations Manager 2007 R2
 Upgrade the push-installed agents.Upgrading Push-Installed Agents
 Check for any active, connected consoles to the root management server.Check the Operations Manager 2007 R2 RMS for Active, Connected Consoles
 Disable all notification subscriptions.Disable the Notification Subscriptions
 Stop services or disable any connectors that are installed.Stop the Services for Connectors
 Verify that your operational database has enough free space.Verify that the Operational Database Has More than 50 Percent of Free Space
 Back up the databases.Back Up the Operations Manager Databases
 Restore the encryption key on secondary management server.Restore the Encryption Key on the Secondary Management Server
 Run management group upgrade on the root management server.How to Upgrade a Management Group from an Operations Manager 2007 R2 RMS
 Upgrade or install the optional features, such as the web consoles and Reporting server.Upgrading or Installing Optional Features
 Re-enable notification subscriptions.Re-enable the Notification Subscriptions
 Restart or re-enable the service for any connectors that are installed.Restart the Connector Services
 Update overrides.Update Overrides
 Verify the success of the upgrade.Verify the Upgrade Success


Single-Server Upgrade (Complex)
 
TaskReferences
 Add a secondary management server and install System Center Operations Manager 2007 R2.How to Add an Operations Manager 2007 R2 Secondary Management Server (Operations Manager Upgrade)
 Move agents that report to the root management (RMS) server to the secondary management server.How to Move Agents to an Operations Manager 2007 R2 Secondary Management Server (Operations Manager Upgrade)
 If SQL Server does not meet the supported configuration requirements, upgrade SQL Server.Upgrading SQL Server (Operations Manager Upgrade)
 Back up the encryption key.Back Up the Encryption Key
 Review the Operations Manager 2007 R2 event logs.Review the Operations Manager 2007 R2 Event Logs
 Remove agents from Pending Management.Remove Agents from Pending Management
 Verify that you have a supported SQL Server collation on all databases and instances of databases.Verify the SQL Collation
 Upgrade the manually installed agents.Upgrading Manually Installed Agents
 Upgrade the secondary management server.How to Upgrade a Secondary Management Server from Operations Manager 2007 R2
 Upgrade the push-installed agents.Upgrading Push-Installed Agents
 Check for any active connected consoles to the root management server.Check the Operations Manager 2007 R2 RMS for Active Connected Consoles
 Disable all notification subscriptions.Disable the Notification Subscriptions
 Stop services or disable any connectors that are installed.Stop the Services for Connectors
 Verify that your operational database has enough free space.Verify that the Operational Database Has More than 50 Percent of Free Space
 Back up the databases.Back Up the Operations Manager Databases
 Restore the encryption key on secondary management server.Restore the Encryption Key on the Secondary Management Server
 Run management group upgrade on the secondary management server.How to Upgrade a Management Group from an Operations Manager 2007 R2 Secondary Management Server
 Re-enable the notification subscriptions.Re-enable the Notification Subscriptions.
 Restart or re-enable the service for any connectors that are installed.Restart the Connector Services
 Uninstall the old root management server.Uninstall the Old RMS
 Update overrides.Update Overrides
 Verify the success of the upgrade.Verify the Upgrade Success

Distributed Upgrade (Complex)

Import the Upgrade Helper Management Pack
 
TaskReferences
 
Import the Upgrade Helper Management Pack
Upgrade Helper Management Pack

Replacing Secondary Management Servers
 
TaskReferences
 If operating system is 32-bit, add a secondary management server.How to Add an Operations Manager 2007 R2 Secondary Management Server (Operations Manager Upgrade)
 Move the Operations Manager 2007 R2 agents to a secondary management server, and remove the old secondary management server.How to Move Agents to an Operations Manager 2007 R2 Secondary Management Server (Operations Manager Upgrade)
 Ensure that the secondary management server meets the supported configuration requirements for System Center 2012 – Operations Manager.Supported Configurations for System Center 2012 - Operations Manager
Replacing Gateways
 
TaskReferences
 If gateway server does not have a 64-bit operating system, build a new gateway server.How to Replace an Operations Manager 2007 R2 Gateway that Has an Unsupported Configuration (Operations Manager Upgrade)
 Remove the old gateway server.How to Remove an Operations Manager 2007 R2 Gateway (Operations Manager Upgrade)
 Ensure that the gateway server meets the supported configuration requirements for System Center 2012 – Operations Manager.Supported Configurations for System Center 2012 - Operations Manager
Secondary Management Server Upgrade
 
TaskReferences
 If RMS does not meet supported configuration requirements for System Center 2012 – Operations Manager, move agents that report to root management server to the secondary management server.How to Move Agents to an Operations Manager 2007 R2 Secondary Management Server (Operations Manager Upgrade)
 If Microsoft SQL Server does not meet the supported configuration requirements, upgrade SQL Server.Upgrading SQL Server (Operations Manager Upgrade)
 Back up the encryption key.Back Up the Encryption Key
 Review the Operations Manager 2007 R2 event logs.Review the Operations Manager 2007 R2 Event Logs
 Check if any gateway servers report to an unsupported RMS.Check for Gateway Servers Reporting to the RMS
 Remove agents from Pending Management.Remove Agents from Pending Management
 Verify that you have a supported SQL Server collation on all databases and instances of databases.Verify the SQL Server Collation
 Upgrade the manually installed agents.Upgrading Manually Installed Agents
 Upgrade the secondary management servers.How to Upgrade a Secondary Management Server from Operations Manager 2007 R2
 Upgrade gateway servers, if present.How to Upgrade a Gateway Server from Operations Manager 2007 R2
 Upgrade the push-installed agents.Upgrading Push-Installed Agents
Management Group Upgrade from RMS
 
TaskReferences
 Check for any active, connected consoles to the root management server.Check the Operations Manager 2007 R2 RMS for Active Connected Consoles
 Disable all notification subscriptions.Disable the Notification Subscriptions
 Stop services or disable any connectors that are installed.Stop the Services for Connectors
 Verify that your operational database has sufficient free space.Verify that the Operational Database has More than 50 Percent of Free Space
 Back up all databases.Back Up the Operations Manager Databases
 Run management group upgrade on the root management server.How to Upgrade a Management Group from an Operations Manager 2007 R2 RMS
 Upgrade optional features.Upgrading or Installing Optional Features
 Re-enable the notification subscriptions.Re-enable the Notification Subscriptions.
 Restart or re-enable the service for any connectors that are installed.Restart the Connector Services
 Update overrides.Update Overrides
 Verify the success of the upgrade.Verify the Upgrade Success

Management Group Upgrade from Secondary Management Server
 
TaskReferences
 Check for any active, connected consoles to the root management server.Check the Operations Manager 2007 R2 RMS for Active, Connected Consoles
 Disable all notification subscriptions.Disable the Notification Subscriptions
 Stop services or disable any connectors that are installed.Stop the Services for Connectors
 Verify that your operational database has sufficient free space.Verify that the Operational Database has More than 50 Percent of Free Space
 Back up all databases.Back Up the Operations Manager Databases
 Restore the encryption key.Restore the Encryption Key on the Secondary Management Server
 Run the management group upgrade on the secondary management server.How to Upgrade a Management Group from an Operations Manager 2007 R2 Secondary Management Server
 If required, install the optional features, such as the consoles and Reporting.Upgrading or Installing Optional Features
 Re-enable the notification subscriptions.Re-enable the Notification Subscriptions.
 Restart or re-enable the service for any connectors that are installed.Restart the Connector Services
 Uninstall the old root management server.Uninstall the Old RMS
 Update overrides.Update Overrides
 Verify the success of the upgrade.Verify the Upgrade Success




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