System Center 2012 Service Pack 1 Yenilikleri

Yeni Integration Packler

  • Exchange Administrator Integration Pack for Orchestrator in System Center 2012 SP1
  • Exchange Users Integration Pack for Orchestrator in System Center 2012 SP1
  • Representational State Transfer (REST) Integration Pack Guide for Orchestrator in System Center 2012 SP1

Güncellenen Integration Packler

  • Active Directory Integration Pack for System Center 2012 – Orchestrator
  • HP Service Manager Integration Pack for System Center 2012 – Orchestrator
  • System Center Integration Pack for System Center 2012 Operations Manager
  • System Center Integration Pack for System Center 2012 Virtual Machine Manager
  • VMware vSphere Integration Pack for System Center 2012 – Orchestrator

Orchestrator DB'sinin başka bir SQL sunucuya yüklenmesi

Eğer varolan Orchestrator DB instance’ınızı değiştirmek ya da farklı bir SQL sunucu üzerinde çalıştırmak istiyorsanız aşağıdaki adımları izlemeniz yeterli olacaktır:

  • İlk ortamdaki SQL Server master key yedeğini alın (Bu işlemi atlarsanız migration sonrasında runbook export/import işlemlerinde problem yaşarsınız)
  • İlk ortamdaki Orchestrator DB yedeğini alın
  • Yeni ortamda SQL Server 2008 R2 kurulumunu tamamlayın
  • SQL Server master key restore edin
  • Orchestrator DB restore edin
  • Orchestrator bileşenlerinin kurulumlarını tamamlayın.

SQL Server 2008 R2 üzerinde master key yedeğini almak içn aşağıdaki scripti çalıştırmak yeterli olacaktır:

 

Sqlcmd –Q”BACKUP SERVICE MASTER KEY TO FILE ='C:BACKUPMASTER_KEY.BAK' ENCRYPTION BY PASSWORD = 'password'”

 

Orchestrator veritabanı yedeğini almak için ise aşağıdaki scripti çalıştırın:
Sqlcmd –Q ”BACKUP DATABASE Orchestrator TO DISK=N'C:BACKUPOrchestratorDB.bak'”

Orchestrator master key restore için:
Sqlcmd –Q “RESTORE SERVICE MASTER KEY FROM FILE = 'C:BACKUPMASTER_KEY.BAK' DECRYPTION BY PASSWORD = 'password';”
Orchestrator DB restore için:
Sqlcmd –Q”RESTORE DATABASE [Orchestrator] FROM  DISK = N'C:BACKUPOrchestratorDB.bak'WITH  FILE = 1,  NOUNLOAD,  STATS = 10”

Orchestrator Entegrasyon Soru-Cevap

Orchestrator ile ilgili sıklıkla akıllara takılan birkaç soru ve  cevabı:

Orchestrator 3rd party araçları yönetebilirmi, comman UI yada API ile?

Evet yönetebilir. Orchestrator içerisinde CLI uygulamalarını, SSH based CLI uygulamalarını, SOAP based Web Service API lerini, REST based Web Services APIlerini, .NET based APIleri yönetebilecek aktiviteler bulunuyor. Örn:

Run Program

Run SSH Comman

Invoke Web Services

Run .Net Script (PowerShell, C#.net, VB.NET ve Javascript)

Bu araçlar ile entegrasyon sağlanması için Orchestrator içerisinde gerçekleştirilmesi gerekli ön gereksinimler varmıdır?

Hayır, yukarıda bahsedilen entegrasyon yöntemleri Orchestrator içerisinde default olarak sunulmuştur.

3rd Party sistem içerisinde gerçekleştirilmesi gereken ön gereksinimler varmıdır?

Hayır, Eğer sistem CLI,API, Database gibi yönetilebilir bir alan sunuyor ise Orchestrator integrate olabilir.

Orchestrator MultiDomain desteği

Orchestrator kullanarak aynı zamanda farklı domainleri, forestları ya da workgroup ortamları yönetebilme imkanınız bulunuyor. Ancak bu noktada dikkat edilmesi gereken çok önemli bir nokta var.

Örneğin DomainA üzerinde bulunan runbook server’ınız üzerinde bir Run Program aktivitesi çalıştırdınız. Ve bu aktiviteninde ilgili programı DomainB’deki bir bilgisayar üzerinde çalıştırmasını istiyorsunuz.

Bu noktada eğer domainler arasında trust ilişkisi var ise hiçbir problem yaşamadan yetkiler dahilinde işleminizi gerçekleştirebilirsiniz. Ancak arada bir trust ilişkisi yok ise bağlantı sırasında iletişim NTLM üzerine düşecektir ve bu da her iki domainde de aynı isme ve şifreye sahip bir kullanıcı hesabı bulundurmanızı gerektirir.

Bu şekilde bir konfigurasyon gerçekleştirdiğinizde untrusted domainleri de yönetmeniz mümkündür.

AVIcode 5.7 Support

p>

System Center 2012’nin Nisan ayı ile birlikte available olmasıyla AVICode 5.7 artık MS tarafından standalone bir ürün olarak sunulmayacak ve support devam eden 12 ay sonrasında durdurulacaktır.

Bu sebeple kısa zamanda Avicode’un .NET application performance monitoring’e upgrade edilmesi gerekmektedir.

System Center 2012 Orchestrator – Link Conditions

Here is the part 4 of System Center 2012 Orchestrator Runbook concept series.

In this blog post we’ll start to cover designing basic and complex runbooks.

Previous parts:

Part1 – System Center Orchestrator 2012 – Test & Start RunBooks

Part2 – System Center 2012 Orchestrator–RunBook Activities

Part3 – System Center 2012 Orchestrator–RunBook Basics

Orchestrator lets you to configure conditions with Smart Links. Smart Links connect individual activities in a runbook and support precedence between two activities.

Also as soon as previous activity finishes, these links invoke next activity. Best part is you can set link conditions to determine the direction of workflow.

For example you can monitor a folder and trigger next activity for each changed and deleted files within that folder. At this situation, you can split in two your workflow to configure separated activities for changed and deleted triggers. For example;

If monitor file activity notices a change event, then smart link will redirect entire workflow through upside activities.

If monitor file activity notices a delete event, then smart link will redirect flow through downside activities.

Look at the simple design;

1

For such a scenario, here are the basic configuration steps;

(more…)

System Center Orchestrator 2012 – Test & Start RunBooks

In this part of Orchestrator 2012 RunBook Concepts series, let’s cover how to test, save and run your existing RunBooks.

For the first two parts:

Part1: http://blogs.technet.com/b/meamcs/archive/2012/03/06/system-center-2012-orchestrator-runbook-basics.aspx

Part2: http://blogs.technet.com/b/meamcs/archive/2012/03/09/system-center-2012-orchestrator-runbook-activities.aspx

In RunBook Designer console, on the top bar you’ll notice three button:

image

Check Out: To be able to edit an existing RunBook, it must be checked out. Main purpose for that action is to prevent concurrent editing of same RunBook by different users.

image

If someone else is already editing RunBook, you will notice a pop-up window informing that someone is already editing RunBook.

Check In:After you finish your editing, you can Check In RunBook and so that all your changes will be committed. And also other users can then edit RunBook.

Undo Check Out: If you click Undo Check Out button when editing the RunBook, all changes you made are reverted.

Testing RunBooks

Before you run Runbooks, you can test it with RunBook Tester and also easily debug each activity or entire RunBook. This is especially helpful for troubleshooting issues. But don’t be confused about terms, RunBook Tester will apply each activity changes to your current environment, that means it will not use a demo or isolated env.

Please also note that tester runs in the currently logged user context. Orchestrator Service account will not be used for testing purposes. So it would be better to open RunBook Tester as Administrator with high-level security token.

image

When you click RunBook Tester from the toolbar, Tester starts and loads relevant RunBook

image

RunBook tester interface consists of five panes;

Run Time Properties:This is one of the mostly used pane. It displays resolved published data items. It’s important because if you use several published items for activities, you may want to see what data is carried between activities. Best way to see them in a clear way is RunBook Tester.

Design Time Properties: Displays design-time information for each activity. This is same with Activity details page.

image

Workspace: Displays active current Runbook. You can set a breakpoint for each activity.

image

Breakpoint will be marked with a red round on activity and tester will stop on it.

Log: Displays detailed information for each activity.

image

You can expand each entry to show details.

image

Resource Browser: Displays the counters, variables, computer groups and schedules.

image

You can predefine each of them and make available for all RunBooks.

Computers Groups and global items can be added within Connections Node.

image

Lets add a computer set to use it within activities.

image

image

Now you can use Computer Group within an activity;

image

image

image

This activity will be performed for all computers which members of previously created Computer Group.

Starting Test

You can start your test with different options;

image

Step Through: Runbook starts with first activity and after completion, it waits for your input. You can click Step button to move one step forward. So you can view design time properties for each activity easily.

image

Waits for my next click..

Starting RunBooks

To start a RunBook, firstly you must click Check In button to commit changes. Then just navigate related Runbook tab and click Run.

image

To stop, just click Stop button on the Toolbar. You can track activity’s success&failure progress on Log Pane;

image

All related events will be logged under Events Pane;

image

Also to track RunBook changes, In the RunBook Designer, select Audit History tab at the bottom and click individual items.

image

image

This is important if there are multiple Runbook designer users in your environment. You can track each Runbook change easily within Audit History.

Next part we’ll cover how to design basic and complex Runbooks.

System Center 2012 Orchestrator–RunBook Basics

http://blogs.technet.com/b/meamcs/archive/2012/03/06/system-center-2012-orchestrator-runbook-basics.aspx

System Center Orchestrator 2012 which is a new member of System Center 2012 family and next version of Opalis, takes place at the center of Private Cloud scenarios. During automation of your dynamic datacenters, Orchestrator can move your operations one more step forward and can integrate with Microsoft and non-Microsoft solutions with just a few clicks.

Let me give you a few examples;

  • You can trigger Orchestrator workflows through an incident management system such as Service Manager 2012.
  • Periodic installation processes can be automated. For example during installation you can take actions on active directory, stop load balancer pools, check service status etc.
  • Active directory operational tasks such as user create, user delete, group create, change memberships etc. can be moved to the orchestrator RunBooks.
  • You can monitor SCOM alerts and trigger custom RunBooks. For example when a virtual machine run out of disk, SCOM generates an alert and orchestrator can assign additional disk through triggered RunBook.

In this blog post series we’ll cover of how to design RunBooks from basic to complex. And at end of the series you will understand what Orchestrator 2012 can do and how can you integrate it into your current environment.

For the first part “RunBook Basics” I’ll mention basic RunBooks concept and activities that resides within RunBooks.

A RunBook consists of automated tasks and process steps. Also each automated step within RunBooks is called activities.

Here is the very basic RunBook design;

clip_image001[4]

That RunBook reads a static text file and maps each line to the server names then restarts a service for each remote server automatically.

Before going into the RunBook creation details, let’s look at the RunBook properties.

clip_image002[4]

Right click a previously created RunBook and click Properties.

GENERAL:

clip_image003[4]

On the General tab, you can customize name and description fields. Name is an important field because if you decide to import your RunBooks into the Service Manager as activities, you will recognize each RunBook with its name. (Yes you can import your RunBooks into the Service Manager!)

Also on general tab, you can set a schedule to allow RunBook runs only on dates and times you specify.

RUNBOOK SERVERS:

clip_image004[4]

Each RunBook needs a RunBook server to run. In case of requirement High Availability , you must add additional RunBook Servers. For each RunBook, primary and standby RunBook Servers can be set.

Failure of primary RunBook server will trigger standby RunBook server to act as primary.

clip_image005[4]

To set Primary and Standby RunBook Server for RunBooks, click Add and specify your RunBook servers.

LOGGING:

In this section you can choose more logging options to store in Orchestrator Database and show up within Orchestrator Console.

I’ll talk about in more details in future posts.

clip_image006[4]

EVENT NOTIFICATION

clip_image007[4]

On event notification tab, additional log file can be generated when a RunBook fails to run or run for more than specified seconds. Related log files can be viewed with Designer Console or Web Console.

JOB CONCURRENCY

clip_image008[5]

One of the most critical option is Job Concurrency. Even you configure this setting for one single RunBook, in fact it has impact on overall Orchestrator RunBook Servers. Main purpose is specifying concurrent jobs for this RunBook. A RunBook server can have maximum 50 concurrent jobs. So that if you need more than this limit you must deploy additional RunBook servers.

RETURNED DATA

clip_image009[4]

If you finalize your activities with “Return Data” activity, this RunBook can carry out defined data to the other RunBooks.

clip_image010[4]

In this blog post we cover basic RunBook concept. For the next parts we’ll drive in more detail about designing and deploying RunBooks over multiple RunBook servers.

cell phone spy software

765qwerty765