Wednesday, February 13, 2013

Orchestrator: Export Runbooks!

 
 I came across one thing the other day, when I was working on a runbook in my lab environment.
When I was finished with my runbook (very pleased with the result btw...:) So I did an export of the runbook and copied it to my USB drive.





When I imported the runbook in the Production environment, my runbook was all blank..... The import went to 100% but nothing there.. So I imported 10 times again and could not see where I had missed.... &/&(/&(/&/(&/%¤!!!

Then suddenly I remembered, did I check-in the runbook?.... No... (&(/&&%&/%&/!!!)

So that's my blog post of the day, check in the runbook With the changes then import / export will work smooth.....:)

 

Orchestrator: Read Line activity

Great overview over the Read line Activity usage.


Type the line numbers of the text that you want to read from the file that you specified.

·   To specify a range of lines, use a hyphen: 1-3. This reads lines 1 to 3.

·   To specify specific lines, use a comma: 5,7,9. This reads lines 5, 7, and 9.

·   Combine the range and specific lines: 1-3,5,7,9. This reads lines 1 to 3, and lines 5, 7, and 9.

·   To specify from a specific line to the last line of the file, type the line number, hyphen, and END: 4-END. This reads lines 4 to the last line of the file.

·   To specify from a specific line to a line relative to the last line of the file, type the line number, hyphen, the less-than sign, and the line number relative to the end line: 4-END<3. If the file has 20 lines, this reads lines 4 to 17 from the file. <3 represents the third line from the end.

·   To specify the last number of lines, type LASTLINES, colon, and the last number of lines that you want to delete: LASTLINES:10. This reads the last 10 lines of the file.

·   Combine different types of operations: 1-5, 8, 10-END<20, LASTLINES:10. This reads lines 1 to 5, line 8, line 10 to the 20th line from the end, and the last 10 lines. Do not overlap lines or line ranges when combining operations. For example, 5-END, LASTLINES:10 fails because the 5-END operation already reads to the end, so the LASTLINES:10 operation cannot succeed because the lines are already read, and the activity fails.

Wednesday, January 30, 2013

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

WarningWarning
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:
  1. Orchestrator
  2. Service Manager
  3. Data Protection Manager (DPM)
  4. Operations Manager
  5. Configuration Manager
  6. Virtual Machine Manager
  7. App Controller