Knallert: January 2013

Wednesday, January 30, 2013

Orchestrator: Building a log for your runbooks

Great article from Anders Begntsson on creating a database for Runbook logs.

http://contoso.se/blog/?p=2488

Tuesday, January 15, 2013

Orchestrator: Orchestrator Web console automatic logon

If your browser is configured for automatic logon, you are not prompted for a name and password. Your browser supplies this information automatically each time you connect to the Orchestration console.

To configure Internet Explorer for automatic logon

1.   In Internet Explorer, click Tools, and then click Internet Options. The Internet Options dialog box opens.

2.   On the Security tab, select Local intranet, and then click Custom Level.

3.   Scroll down to User Authentication, and under Logon, select Automatic logon only in Intranet zone. Click OK.

4.   In the Internet Options dialog box on the Security Settings tab, with Local intranet still selected, click Sites.

5.   Click Advanced.

6.   Type the URL of the Orchestration console server (for example, http://OrchSrv.contoso.com) in the Add this Web site to the zone box, and then click Add.

If the Require server verification (https:) for all sites in this zone is selected, you have to specify https for the address, and your web server has to be configured to support Secure Sockets Layer (SSL).

7.   Click OK for this and the remaining dialog boxes.

Orchestrator: Using System Center 2012 Orchestrator to create a new user in Office 365 from a Service Manager Service Request

http://seethruthecloud.com/using-system-center-2012-orchestrator-to-create-a-new-user-in-office-365-from-a-service-manager-service-request

Orchestrator: Upgrade to System Center SP1

http://technet.microsoft.com/en-us/library/jj900231.aspx

Warning
If you are planning to upgrade two or more System Center components, it is important to start by reading the guide Upgrade Sequencing for System Center 2012 SP1. The order in which you perform component upgrades is important. Failure to follow the correct upgrade sequence might result in component failure for which no recovery options exist. The affected System Center components are: Orchestrator Service Manager Data Protection Manager (DPM) Operations Manager Configuration Manager Virtual Machine Manager App Controller

Warning

If you are planning to upgrade two or more System Center components, it is important to start by reading the guide Upgrade Sequencing for System Center 2012 SP1. The order in which you perform component upgrades is important. Failure to follow the correct upgrade sequence might result in component failure for which no recovery options exist. The affected System Center components are: