SCSM + Orchestrator Licensing

Hello All,
I'm trying to figure out how the System Center licensing works when implementing only SCSM + Orchestrator for the Self service part.
We want to implement SCSM and Orchestrator only to offer runbooks to endusers via the portal.
We will only make use of the AD Connector and the Request Fulfillment parts.
The licensing datasheet states the following:
System Center 2012
License metric: server-based + OSE + user-based
•Each Server ML covers up to 2 physical processors
•Each Client ML is available on a per-OSE or per-user basis
Editions:
•Datacenter
•Standard
With System Center 2012, only the endpoints to be managed need licences, with no differentiation between server workloads. Rights to SQL Server Technology and Management Server software are included.
How does it work then for SCSM and orchestrator?
No endpoints are actually managed in our scenario, so I think that we only have to foresee Client MLs on a per-user basis for each user that will make requests.
The runbooks will however connect to AD, SCCM, ...
Do we have to foresee Server ML's then for all our AD and SCCM Servers?
If I'm not mistaken then no Server ML licenses need to be foreseen for the servers hosting the SCSM and Orchestrator software, right?
Thanks for helping me solve this puzzle :)
Kind regards,
Filip

Hello,
if you want to license your Server and Clients with SCSM and Orchestrator than you need to purchase the System Center SML Standard or datacenter for each physical Server up to two CPUs. the only difference between Standard and datacenter is about virtualization
rights: Standard up to two VMs for each license and datacenter for unlimited VMs.
for Clients, you need to purchase the System Center Client(CML) Management Suite for each user or OSE.
the SCSM and the Orchestrator are not available as a standalone products.
thanks
diramoh

Similar Messages

SCSM-Orchestrator querying "Support Group" with "path info"

In SCSM List "Incident Tier Queue" we created a tree-like structure similar to this one:
Helpdesk\Tier 1
Helpdesk\Tier 2
SysAdmin\Networking
Sysadmin\Storage
SysAdmin\Tier 1
SysAdmin\Tier 2
editing an incident, the console shows this like a path:
SysAdmin\Tier 1
but when i query the data through orchestrator with a Get Object activity, i see only "Tier 1" in the returned value. so not the full "path" is shown, only the last child element of the tree.
this makes it impossible to distinguish between "Helpdesk\Tier 1" and "Sysadmin\Tier 1".
how can i access the Support Group field and query its "full path" ?

Hi,
you will not get the Enumeration-List with an Activity of the IP for SCSM. You will need a PowerShell-Script similiar (not the same) as here
http://blogs.technet.com/b/georgewallace/archive/2014/07/08/pulling-all-enumerations-and-child-nodes-with-powershell-scsm-2012-r2.aspx
You can run this Script with the "Run .Net Script" Activity.
Regards,
Stefan
www.sc-orchestrator.eu ,
Blog sc-orchestrator.eu

Service Manager is not working anymore - license expired

Hello guys,
our Service Manager 2012 R2 is not working since yesterday. We could not connect to the Management Server but via Hyper-V. And then we detected in the logs that the issue is that the SCSM License is expired.
Have anyone an idea how can I change the license? I have read of the SCSM Change License Tool, but how can I get it? Is there other way to change the license? I would be very pleased to receive your answers.

How was your SCSM servers installed? With the trial? Or did you enter in CD Keys? I'm on a MS Volume License Agreement so once I enter in my CD Keys, there is no expiration (that I'm aware of!). If you installed on the trial, there
*should* be some KB articles on how to enter in your CD Keys.

SCSM - looks GREAT but...

Hey guys,
I've just finished watching an introduction video to SCSM / Orchestrator - wow. Really impressed. We already utilise SCCM and SCOM - SCSM / Orchestrator just seems to be HUB for system center... love it.
However, I was wondering... we currently have on premise instances of Exchange, Lync and SharePoint. If we decide to move these technologies into the cloud (365) how does interoperability then work between SCSM / Orchestrator and 365? Done a little digging
about and can't find much on the subject.
Many thanks to those that take the time to respond to this post.
Cheers.
M Tipler

There is no problem with moving your lync or exchange to office 365. You have to reconfigure the exchange connector but other then that no problem.
I guess you mention the sharepoint because of the webportal in SCSM that uses sharepoint. This you can't put in office 365 but other then that you should not have any problems in future changes.
Cheers,
Thomas Strömberg
System Center Specialist
Blog:
Twitter: LinkedIn:
Please remember to 'Propose as answer' if you find a reply helpful

SCSM Query shows correct information in SMportal but sends only user name back to scorch

When creating a services request in SMportal it will send back correct information to scorch and make configution change if I use use text and not query in the request. When using query it will show the information the users should see but SCSM sends only
the user name back to scorch and not the value that was selected.
Thanks for the help
Hans Petter

When you create a Request Offering that uses a query, that item is added to the Service Request as a related item. In your case you will need to get the related Active Directory Users for your service request. See the link below for more details on this.
http://blogs.technet.com/b/servicemanager/archive/2012/05/22/working-with-relationships-in-the-scsm-orchestrator-integration-pack.aspx
Matthew Dowst |
Blog | Twitter

How do I use a runbook Activity on an Incident and Runbook Initialize Data activity to sync and get the GUid from the Incident?

I currently have a runbook running every hour to attach Incidents Templates to Problems. I would like to just add a runbook activity to the Incident Template to activate the runbook, and only link that Incident to the problem it needs to be attached to.
I don't know how to set-up my Initialize Data activity in my runbook to load the calling Incidents GUID though.
I'm very new to Orchestrator, so please be detailed in your directions.
The way my runbook works now is, I make my incident templates have the PR # they are for in the Alt Contact Block. My runbook searched for that, and then loads the PR# it has there and creates the relationship between the two, and then deletes that PR# so
it doesnt hit on the next search.
I would like my activity that calls the runbook to pass the Incident GUID to the runbook, so my runbook only has to query the PR# included in the incident, and create the relationship that way.
Thanks for any help you can provide.

This might help:
Working With Relationships in the SCSM Orchestrator Integration Pack
Basically, you'll receive the ID of the runbook automation activity from Service Manager, which you can then use with the Get Object and Get Relationship to get the runbook activity object, then get the incident object related to it. I realize this is confusing,
but there should be more info out there to search on as well. Hope that helps.
Noah Stahl | Automys |
Downloadable Microsoft automation examples and solutions

Moving Service Manager Database From SQL 2008 R2 SP2 to SQL 2012 SP1

Hi Guys,
Just looking for some clarification about moving our Service Manager 2012 R2 database to a new SQL Server.
Our Service Manager database is currently on a remote SQL server, shared with other databases, running SQL 2008 R2 SP2. It was originally setup this way as we only deployed Change Management but we are now wanting to deploy everything, fully
utilising SCSM/Orchestrator and Cireson's suite. Due to the limited resources available on that SQL server we are seeing performance issues before even getting it all up and running.
I want to move the Service Manager database to a new dedicated SQL server running SQL 2012 SP1. I am aware of the official DB move procedure but it does not specifically mention moving up SQL versions. I have seen some comments around here that
it is fine to do but some feedback would be good, it is not something I have done before.
All servers in this are fully patched Windows 2008 R2. Also, we do not currently have a Data Warehouse so do not need to worry about that. It was dropped and uninstalled before upgrading to Service Manager 2012 R2 and will be reinstalled after this DB move
using a separate dedicated SQL server.
Thanks, Chris.

As long as your collations and permissions are the same as before it
should not be a problem. That sad i could not find any other documentation saying it's not supported.
I have moved SCSM databases between different SQL-versions before and it has worked fine if the collations etc are correct.
Cheers,
Thomas Strömberg
System Center Specialist
Blog:
Twitter: LinkedIn:
Please remember to 'Propose as answer' if you find a reply helpful

Retrieving the Affected Configuration Items from a Service Request

I have a service request that gathers the usernames of AD Users that need to be added to a new security group. I have Query Result field set to add the users that are selected as Affected Configuration Items. My problem is when I get the SR's related AD
Users it gives me all of the Affected CIs but it also gives me the user that submitted the form. Is there any way to filter the relationship to only get users in the Affected CI list?
Here's the steps I'm using:
Identify Runbook Automation Activity
Get Parent Service Request Relationship from RBA
Get Parent SR Object
Get related AD Users from SR
Get AD User Objects
Any help is much appreciated.

I figured it out. If anyone else is having this issue, you have to filter the Get User Relationship to exclude everything that does not match the Affected User Relationship Class:
http://blogs.technet.com/b/servicemanager/archive/2012/05/22/working-with-relationships-in-the-scsm-orchestrator-integration-pack.aspx

SQL problem encountered when setting up SCCM

Hi all,
I am currently trying to setup a configuration manager primary site (as a stand-alone site) in a test environment. My SQL server has already been setup, with other components of system center 2012 (SCOM, SCSM, Orchestrator) relying on the same
SQL 2008 standard edition R2 SP2 server.
I have been unable to install SCCM itself though. lets say I am now logged into my SCCM server using a domain admin account called scadmin. I have used scadmin to install other components of system center. Under my SQL server, in management studio, scadmin
has rights of "public", "securityadmin", "serveradmin", "setupadmin", "sysadmin".
When trying to specify my SQL server, instance name, I encountered the following error.
Setup is unable to connect to SQL Server with the connection information provided. Verify the following:
1. The SQL server and instance names are entered correctly
2. The specified SQL server instance is not configured to use dynamic ports
3. If a firewall is enabled on the SQL server, inbound rules exist to allow connections to the correct ports
4. The account used to run setup has permissions to connect to the specified SQL Server instance
I have verified against the 4 mentioned points above:
1. Yes
2. My understanding is SQL server by default uses static ports, so mine should be static
3. No firewall involved, all servers are on the same physical machine, connected to a switch, Windows firewall off
4. Permissions as mentioned above.
I also went to check out the log file in the SCCM server, C:\ConfigMgrSetupWizard.txt
this is what i saw everytime i tried to click next in the setup
"Creating SQL connection to database scsqlserver\master on server SC-SQL-01.testdomain.com"
My SQL server hostname: SC-SQL-01
SQL instance: scsqlserver
i also noticed in the same log file that when I start the installation, there is an error saying
"Cannot not connect to SMS provider on local machine. Either it is not installed or access is denied.
Cannot detect SMS Type because either SiteServer, SqlServer or SiteServerName is empty."
is there anyone who might be able to point out what went wrong?

As you mentioned to check the “SQL Server Network Configuration->Protocols for Named_Instance (the
sql instance name you gave)" but I see the TCP\IP for the SQL Instance's (i.e. SQLEXPRESS as I selected Default) is Enabled. I have installed all Windows Server 2008 R2 Roles on the same system along with the SQL Server 2012 R2. Then I have also set the
Inbound and Outbound Firewall rules using gpedit.msc. Do you also have any idea why the SQL Server Agent service is not running. Other services i.e Windows Internal Database, SQL Server and SQL Server Browser are running fine. Please suggest. Moreover, its
also an Administrator account and thats the only account I use for logging in and installing everything on this system. Its not allowing me to attach the screenshots at this moment as it says it will first verify my account and then allow me but I dont think
it will be difficult for you to imagine this issue as you have seen this similar issue elsewhere.

Review activity set to notify Affected User of Approval Required - Service Request

We are trying to setup a new employee on boarding process. We have a service request form that gathers information.
We also have a review activity that the affected user (who is the manager on boarding the employee) has to approve when they get a signed confidentiality agreement, etc.
We cant set Affected User as a Reviewer but the affected user can approve.
How can we notify the affected user to review and approve the review activity.
On the screen shot below it is the first review activity.
Note: we have some workflow activity events setup that work when the reviewer is assigned in the template.
Thanks Lance

You want to set the affected user of the SR as a reviewer on the RA? In essence approving their own request. Why not just make the signed confidentiality agreement mandatory (cannot create request without it).
Anyways you have two ways to go. A custom workflow/scheduled PS-script or a runbook. If you have Orchestrator that is the easiest. Setup a "Monitor Object" that targets new SRs and a criteria that uniquely identifies the SR (Title may do). Then get the related
user from the SR and add this to the RA as a reviewer. Should be fairly easy to google a blog on specifics on how to do this.
http://www.scsm.se/?p=895
and a long one:
http://blogs.technet.com/b/servicemanager/archive/2012/05/22/working-with-relationships-in-the-scsm-orchestrator-integration-pack.aspx
http://codebeaver.blogspot.dk/

Orchestrator - SCSM List not updating

Hi,
When updating or adding a list item in Service Manager it is not showing in Orchestrator.
For instance, I added a new support group that will trigger a task whenever a ticket is assigned to that Support Group. On the Monitor Object task when I select Support Group as a filter, it shows a list without my newly created Support Group.
I have an SCSM connector to Orchestrator, but when I run it I see no change.
Is there something else that I have to try?

Hi,
Yes it's a real problem ... you can try this
In order to force SCO runbookactivity (i.e. Get Object) to re-read a class property:
1. Open an activity
2. If the activity had any filters, make a note of them
2. Under Class field, click on Brows button and select the same class
3. If the activity had any filters, they would be deleted at this point - re-enter the filters.
FYI you can read this :
https://social.technet.microsoft.com/Forums/en-US/ee9b3ca7-415f-4c74-afeb-0f6ec08c2ba2/orchestrator-scsm-2012-activity-does-not-update-custom-class-properties-automatically-how-to?forum=scogeneral
Remy BOVI

Installing Orchestrator on SCSM

Hi,
I would like to install Orchestrator for SCSM.
However, I do not have a dedicated server.
I have:
Service Manager server
DW SM server
Database server
Sharepoint Foundation 2010 / Self service Portal Server
On which server I can install Orchestrator to cause least damage?
Thanks in advance.

Orchestrator and service manager coexist well, you shouldn't have much issue using the same servers and database instances. be aware, however, that the management server is very CPU bound, the database server is very memory and I/O bound, and SharePoint
is it's own resource hog, so you might need to add extra compute capacity to make sure you don't have a usability impact.

Upgrade SCSM 2012 Eval to Licensed - How?

I am one of the multiple people who have installed SCSM 2012 in eval mode and need to be able to license it if possible.
I see in recent threads on this subject that this may be possible in some cases. I hope it is possible in my case which is that the system was installed as 2012 R2 originally but is now currently expired. My reference that it may be possible is this thread:
https://social.technet.microsoft.com/Forums/systemcenter/en-US/ed4b8b37-7ef0-40c4-8993-61f62d5e600d/activation-of-scsm-2012-sp1-from-evaluation-to-full-version?forum=systemcenterservicemanager
I also see a page on TechNet that references changing from eval to licensed on R2. However, I have not been able to find in the documentation how to do this.
http://blogs.technet.com/b/thomase/archive/2013/10/29/service-manager-2012-r2-fixes-included.aspx
Does anyone have any additional information on this process?

You need to create a support case at Microsoft to change from eval to full. It says so in both links :D
http://codebeaver.blogspot.dk/

Is there a way of monitoring SCSM connector failures using SCOM

I have an environment comprising SCSM2012 SP1, SCOM2012 SP1 and SCCM2012SP1 with Orchestrator forwarding the CI data and alerts to a 3rd party CMDB/ServiceDesk system. We have SCSM connectors for AD, SCCM and SCOM CI. There was a recent issue with SCSM UR6
where the SCCM connector stopped working. I regressed the Microsoft.EnterpriseManagement.ServiceManager.Linking.Consumer.OperationalStore.dll back to the RTM release version and it all works again.
I want to know if there is a way of monitoring each of the connectors in SCOM to ensure I get alerted if the status of the 3 connectors is anything other than "Finished Success" - maybe only generating an alert if the status stays in a failed status
for more than 24 hours.
There appears to be very little documentation on how these connectors work or what errors they write into logs. Any tricks or tips would be appreciated.

On you management server, if you open Event Viewer, the logs are keep under Application and Services Logs Operations Manager. (Yes, the Service Manager logs are keep in the Operations Manager logs folder) In this folder you should find the event logs for
your connectors. Just search for different sources to find the connector you want to monitor. Some of the sources include Exchange Connector, OpsMgr Connector, Data Connectors (AD connector), System Center Orchestrator, and Lfx Service (SCCM
Connector). You could easily setup SCOM or Orchestrator to monitor these logs.
Matthew Dowst |
Blog | Twitter

Install Failing when attempted to Add a new Management Server into SCSM Management Group

Hello Experts
I am adding a additional MS into my current SCSM 2012 sp1 MANAGEMENT Group. But its failing with the below error message .One thing is little wiered here is ...that the wizard fails with the message that the UPGARDE FAILED , but I am not rying to upgrade
, I am adding a MS on a new 2012 vm. It goes all the way and install the services with the account , but then it rollbacks everything I am installing the bits with the same account which is the admin on the workflow server . I have created a registry
key ServicesPipeTimeout to 600000ms , but still no luck . The new VM is all up to date with patches , the sdk/config account is the admin on the new ms vm . The service manager db is a cluster , not sure if that's wats causing it .
SCSM2012 SP1
Primary Workflow MS : WIN2008R2
SQL CLUSTER : 2008R2SP1
New MS :- WIN2012
Calling custom action CAManaged!Microsoft.MOMv3.Setup.MOMv3ManagedCAs.WaitForSDKServiceStart
WaitForSDKServiceStart:Entering
WaitForSDKServiceStart: Error: The client has been disconnected from the server. Please call ManagementGroup.Reconnect() to reestablish the connection.,
Stack:    at Microsoft.EnterpriseManagement.Common.Internal.ExceptionHandlers.HandleChannelExceptions(Exception ex)
   at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.CreateEndpoint(EnterpriseManagementConnectionSettings connectionSettings, SdkChannelObject`1 channelObjectDispatcherService)
   at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.ConstructEnterpriseManagementGroupInternal(EnterpriseManagementConnectionSettings connectionSettings, ClientDataAccessCore clientCallback)
   at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.RetrieveEnterpriseManagementGroupInternal(EnterpriseManagementConnectionSettings connectionSettings, ClientDataAccessCore callbackDispatcherService)
   at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.Connect(EnterpriseManagementConnectionSettings connectionSettings, ClientDataAccessCore callbackDispatcherService)
   at Microsoft.EnterpriseManagement.EnterpriseManagementGroup.InternalInitialize(EnterpriseManagementConnectionSettings connectionSettings, EnterpriseManagementGroupInternal internalsProxy)
   at Microsoft.EnterpriseManagement.EnterpriseManagementGroup.Connect(EnterpriseManagementConnectionSettings connectionSettings)
   at Microsoft.MOMv3.Setup.MOMv3ManagedCAs.WaitForSDKServiceStart(Session session)
MSI (s) (B8:98) [16:36:03:050]: NOTE: custom action _WaitForSDKServiceStart unexpectedly closed the hInstall handle (type MSIHANDLE) provided to it. The custom action should be fixed to not close that handle.
CustomAction _WaitForSDKServiceStart returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (B8:78) [16:36:05:044]: Executing op: Header(Signature=1397708873,Version=500,Timestamp=1156350899,LangId=0,Platform=589824,ScriptType=2,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=1)
MSI (s) (B8:78) [16:36:05:044]: Executing op: DialogInfo(Type=0,Argument=0)
MSI (s) (B8:78) [16:36:05:046]: Executing op: DialogInfo(Type=1,Argument=Microsoft System Center 2012 - Service Manager)

D5DB645B01E7},AssemblyType=1,,AssemblyName=Microsoft.EnterpriseManagement.Core,fileVersion="7.5.2905.0",version="7.0.5000.0",culture="neutral",publicKeyToken="31BF3856AD364E35",processorArchitecture="MSIL",)
MSI (s) (80:88) [11:29:02:669]: Executing op: AssemblyPublish(Feature=SMCommon,Component={4D0CB3BB-D941-408A-AA30-F8B7996AB220},AssemblyType=1,,AssemblyName=Microsoft.EnterpriseManagement.Packaging,fileVersion="7.5.2905.0",version="7.0.5000.0",culture="neutral",publicKeyToken="31BF3856AD364E35",processorArchitecture="MSIL",)
MSI (s) (80:88) [11:29:02:675]: Executing op: AssemblyPublish(Feature=SMCommon,Component={B6133F85-0B89-4120-ADFD-9A426FB7D5A3},AssemblyType=1,,AssemblyName=Microsoft.EnterpriseManagement.OperationsManager.Common,fileVersion="6.0.6278.0",version="6.0.4900.0",culture="neutral",publicKeyToken="31BF3856AD364E35",processorArchitecture="MSIL",)
MSI (s) (80:88) [11:29:02:681]: Executing op: AssemblyPublish(Feature=SMCommon,Component={58A6B313-BD98-46E0-B344-0D6861535208},AssemblyType=1,,AssemblyName=Microsoft.EnterpriseManagement.ServiceManager,fileVersion="7.5.2905.0",version="7.0.5000.0",culture="neutral",publicKeyToken="31BF3856AD364E35",processorArchitecture="MSIL",)
MSI (s) (80:88) [11:29:02:688]: Executing op: AssemblyPublish(Feature=SMCommon,Component={41071460-6573-41C8-AED8-06CEC0D0AFB9},AssemblyType=1,,AssemblyName=Microsoft.EnterpriseManagement.DataWarehouse,fileVersion="7.5.2905.0",version="7.0.5000.0",culture="neutral",publicKeyToken="31BF3856AD364E35",processorArchitecture="MSIL",)
MSI (s) (80:88) [11:29:02:693]: Executing op: AssemblyPublish(Feature=SMCommon,Component={E51AEF3C-9B2D-4B0E-AB7E-AD0423899C39},AssemblyType=1,,AssemblyName=Microsoft.EnterpriseManagement.OperationsManager,fileVersion="6.0.6278.0",version="6.0.4900.0",culture="neutral",publicKeyToken="31BF3856AD364E35",processorArchitecture="MSIL",)
MSI (s) (80:88) [11:29:02:713]: Executing op: AssemblyPublish(Feature=SMCommon,Component={9718BF1D-6A9F-3406-A992-630F7EF2F164},AssemblyType=2,,AssemblyName=Microsoft.VC90.CRT,version="9.0.30729.1",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="amd64",type="win32",)
MSI (s) (80:88) [11:29:02:720]: Executing op: ActionStart(Name=NetFxExecuteNativeImageCommitUninstall.62894CB9_4320_40DB_B4E4_C0347FAB97B6,,)
MSI (s) (80:88) [11:29:02:721]: Executing op: CustomActionSchedule(Action=NetFxExecuteNativeImageCommitUninstall.62894CB9_4320_40DB_B4E4_C0347FAB97B6,ActionType=3649,Source=BinaryData,Target=ExecNetFx,)
MSI (s) (80:88) [11:29:02:722]: Executing op: ActionStart(Name=NetFxExecuteNativeImageCommitInstall.62894CB9_4320_40DB_B4E4_C0347FAB97B6,,)
MSI (s) (80:88) [11:29:02:724]: Executing op: CustomActionSchedule(Action=NetFxExecuteNativeImageCommitInstall.62894CB9_4320_40DB_B4E4_C0347FAB97B6,ActionType=3649,Source=BinaryData,Target=ExecNetFx,)
MSI (s) (80:88) [11:29:02:725]: Executing op: ActionStart(Name=NetFxExecuteNativeImageCommitUninstall,,)
MSI (s) (80:88) [11:29:02:726]: Executing op: CustomActionSchedule(Action=NetFxExecuteNativeImageCommitUninstall,ActionType=3649,Source=BinaryData,Target=ExecNetFx,)
MSI (s) (80:88) [11:29:02:726]: Executing op: ActionStart(Name=NetFxExecuteNativeImageCommitInstall,,)
MSI (s) (80:88) [11:29:02:728]: Executing op: CustomActionSchedule(Action=NetFxExecuteNativeImageCommitInstall,ActionType=3649,Source=BinaryData,Target=ExecNetFx,CustomActionData=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe install "E:\Program Files\Microsoft
System Center 2012\Service Manager\Microsoft.EnterpriseManagement.UI.ConsoleFramework.dll" /queue:1?500?C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe install "E:\Program Files\Microsoft System Center 2012\Service Manager\Microsoft.EnterpriseManagement.UI.Foundation.dll"
/queue:1?500?C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe install "E:\Program Files\Microsoft System Center 2012\Service Manager\Microsoft.EnterpriseManagement.UI.Controls.dll" /queue:1?500?C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe
install "E:\Program Files\Microsoft System Center 2012\Service Manager\Microsoft.EnterpriseManagement.UI.ViewFramework.dll" /queue:1?500?C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe install "E:\Program Files\Microsoft System Center 2012\Service
Manager\Microsoft.EnterpriseM
MSI (s) (80:88) [11:29:02:729]: Executing op: ActionStart(Name=_ConfigureConfigService.D2179E31_E456_401A_A820_CEBB135E3429,Description=Configure Config Service,)
MSI (s) (80:88) [11:29:02:734]: Executing op: CustomActionSchedule(Action=_ConfigureConfigService.D2179E31_E456_401A_A820_CEBB135E3429,ActionType=3585,Source=BinaryData,Target=ConfigureSDKConfigService,CustomActionData=1 OMCFG)
MSI (s) (80:88) [11:29:02:736]: Executing op: ActionStart(Name=_ConfigureSDKConfigService,,)
MSI (s) (80:88) [11:29:02:737]: Executing op: CustomActionSchedule(Action=_ConfigureSDKConfigService,ActionType=3585,Source=BinaryData,Target=ConfigureSDKConfigService,CustomActionData=1 OMSDK)
MSI (s) (80:88) [11:29:02:738]: Executing op: ActionStart(Name=_WaitForSDKServiceStart,,)
MSI (s) (80:88) [11:29:02:840]: Executing op: CustomActionSchedule(Action=_WaitForSDKServiceStart,ActionType=1537,Source=BinaryData,Target=WaitForSDKServiceStart,)
MSI (s) (80:88) [11:29:02:924]: Executing op: ActionStart(Name=_RegisterSdkSCP,,)
MSI (s) (80:88) [11:29:02:944]: Executing op: CustomActionSchedule(Action=_RegisterSdkSCP,ActionType=1089,Source=BinaryData,Target=RegisterSdkSCP,CustomActionData=SCSMPROD|DOMAIN\_SVCACCT|SMSDKSCP)
MSI (s) (80:6C) [11:29:03:103]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI16CE.tmp, Entrypoint: RegisterSdkSCP
CAPACK: Extracting custom action to temporary directory: C:\Windows\Installer\MSI16CE.tmp-\
CAPACK: CLR version v2.0.50727 is installed.
CAPACK: CLR version v2.0.50727 is detected.
CAPACK: CLR version v4.0.30319 is installed.
CAPACK: CLR version v4.0.30319 is detected.
CAPACK: Binding to CLR version v2.0.50727
Calling custom action CAManaged!Microsoft.MOMv3.Setup.MOMv3ManagedCAs.RegisterSdkSCP
RegisterSdkSCP: There is no previous serviceConnectionPoint
RegisterSdkSCP: Creating New serviceConnectionPoint
RegisterSdkSCP: Adding ACL for current user: DOMAIN\_SVCACCT
RegisterSdkSCP: Adding ACL for SM Admini: DOMAIN\_SVCACCT
RegisterSdkSCP: Error: Access is denied.
StackTrace:    at System.DirectoryServices.Interop.UnsafeNativeMethods.IAds.SetInfo()
   at System.DirectoryServices.DirectoryEntry.CommitChanges()
   at Microsoft.MOMv3.Setup.MOMv3ManagedCAs.RegisterSdkSCP(Session session)
MSI (s) (80:6C) [11:29:10:243]: NOTE: custom action _RegisterSdkSCP unexpectedly closed the hInstall handle (type MSIHANDLE) provided to it. The custom action should be fixed to not close that handle.
MSI (s) (80:88) [11:29:10:246]: Executing op: ActionStart(Name=_SetupSdkDefaultConnector,Description=Setting SDK default connector,)
CustomAction _RegisterSdkSCP returned actual error code 1603 but will be translated to success due to continue marking
MSI (s) (80:88) [11:29:10:265]: Executing op: CustomActionSchedule(Action=_SetupSdkDefaultConnector,ActionType=17921,Source=BinaryData,Target=SetupSdkDefaultConnector,CustomActionData=EDVXSCSMWEBPP02)
MSI (s) (80:88) [11:29:10:366]: Executing op: ActionStart(Name=_CreateSetupUser,,)
MSI (s) (80:88) [11:29:10:381]: Executing op: CustomActionSchedule(Action=_CreateSetupUser,ActionType=1537,Source=BinaryData,Target=CreateSetupUser,CustomActionData=DOMAIN\_SVCACCT)
MSI (s) (80:88) [11:29:10:461]: Executing op: ActionStart(Name=_CreateInstanceQualityRelationship,Description=Creating Default Instances, Qualities And There Relationships,)
MSI (s) (80:88) [11:29:10:481]: Executing op: CustomActionSchedule(Action=_CreateInstanceQualityRelationship,ActionType=17921,Source=BinaryData,Target=CreateInstanceQualityRelationship,CustomActionData=Cmdb^Microsoft.SystemCenter.ResourceAccessLayer.CmdbResourceStore^Ral.CmdbResourceStore.Cmdb^SCSMSMDBDOMAIN,DOMAIN^ServiceManager^Microsoft.SystemCenter.ResourceAccessLayer.Stores|Ods^Microsoft.SystemCenter.ResourceAccessLayer.SqlResourceStore^Ral.SqlResourceStore.Ods^SCSMSMDBDOMAIN,DOMAIN^ServiceManager^Microsoft.SystemCenter.ResourceAccessLayer.Stores|Workflows^Microsoft.SystemCenter.ResourceAccessLayer.SqlResourceStore^Ral.SqlResourceStore.Workflows^SCSMSMDBDOMAIN,DOMAIN^ServiceManager^Microsoft.SystemCenter.ResourceAccessLayer.Stores|Orchestration^Microsoft.SystemCenter.ResourceAccessLayer.DagResourceStore^Ral.DagResourceStore.Orchestration^EDVXSCSMWEBPP02^Dag^Microsoft.SystemCenter.ResourceAccessLayer.Stores|Sdk^Microsoft.SystemCenter.ResourceAccessLayer.SdkResourceStore^Ral.SdkResourceStore.Sdk^EDVXSCSMWEBPP02^Sdk^Microsoft.SystemCenter.ResourceAccessLayer.Stores$Cmdb^Cmdb|Ods^Ods|Workflows^Wo
MSI (s) (80:88) [11:29:10:551]: Executing op: ActionStart(Name=_CreateSLAOOBMetric,,)
MSI (s) (80:88) [11:29:10:593]: Executing op: CustomActionSchedule(Action=_CreateSLAOOBMetric,ActionType=1537,Source=BinaryData,Target=CreateSLAOOBMetric,)
MSI (s) (80:88) [11:29:10:669]: Executing op: ActionStart(Name=_AddAuthenticatedUserToSmEndusersRole,,)
MSI (s) (80:88) [11:29:10:687]: Executing op: CustomActionSchedule(Action=_AddAuthenticatedUserToSmEndusersRole,ActionType=17921,Source=BinaryData,Target=AddUserGroupToSmRole,CustomActionData=SERVERNAMEDOMAIN,DOMAIN|0CDDEB2B-5AC7-4E9b-8918-F73A5A5DC5FA|S-1-5-11)
MSI (s) (80:88) [11:29:10:764]: Executing op: ActionStart(Name=PublishFeatures,Description=Publishing product features,Template=[1])
MSI (s) (80:88) [11:29:10:769]: Executing op: FeaturePublish(Feature=SMCommon,,Absent=2,Component=(q3HBAv]i@qJ'%Q!&u`-E'vFHJKp&?B*BP3I&v8CI)GV$dS}K9o{`+oQzOH`6rk8o}k)$9h9ht?25ep*M5[kQmAiu8ksDfcfd?7Y`cA}%6azL=&%e(j@mj@Fz,ecq(qrp8](TKe3L$PCRH97spltW=ku%.hsb*,Om8nB9k-6cA0[3pMQTZ)ilXhqI.}^o8,EuQO7^U_3+@[M`@}[t9u8Wo6!tFc%bh)^7q6wW=apEHCHH1,?v,UEvGBSJArZu~HLod%Kb5o96e+p$903LI])2$p$F%OJdG^%+A=LH+73@4VPU6Grpj92,@+LF6KK25&]=f`,Pw3-%=3zM^iId4@ZCcxSHi&g39aNS8{R&72hWL`[email protected]`]AQmIfehM.h8y$eKidM0ZZCIg^udzEY?vKfT%PHraR*_a5.zP5_@[KW{oCEn$OB[,Y5D*`m9ByA])z,POCbb@sj&oXSAAcoGYM11_t!LQ[A2'u.90@8@Eats}$VHsbIFnRS=HM!!AA67_?kk^q?LXxN=r$8P(zZWMJJ{9@Z'[&R=ibW(AelUb.T7J9-G*B~='`,6hc~mWukk*QjX6`=?+MOCxGuQnGmy*71a$.d=q2UJvQ$^-E1ev?yK?40?AC856b78PAvp@-+AM.W?c~waDTv0,B3zl1iw%vO9)BKj!jy7~r^wE3]d*T-@NwxfGl[ns7%KANUrxZ_9)ODbn-q(ifd)oMIA18&?By'*2%,lY+,!UmZHa]_8+TSP[td}bT-CL%NNDP3?Z*yqPzZpJL.g@_oYZZZ@f!r?*1+']Zj]ZqjdIrE93ZaoSS_`udf%hNKO=9j?aFhCl*?,uleMNZ1Z~ZE9FqKxu+Isz3ow_9L8eB^=3X9%1XjT_huv(S=Kofh9JKrEq.?bB!L`vCwRLC3@2y4WO-0'Ic%eNDY,x-y@1n30[^'z+cLCX]e[=7a8'W6k*?}q&'br-YB(.!`@fw0~&p`8-=Mnx6qys!X9TQW^09zZ@pU
MSI (s) (80:88) [11:29:10:821]: Executing op: FeaturePublish(Feature=SMServer,,Absent=2,Component=Ik{Op{5Kr=GT6Le$}XC3c6,M6L((V9pkVNH,10cG1+tmy*`TG?4+OQ_V,p$dVCsu8xeQf9Brt8)ud$Sf^SsJTSpso8TFvFZg+*V!vIFSk4eIY98NOU2f+BvOK_yzaR8Je9TA*L3kFh1Q^c{'C@}z5=0HxnJ+Ye5m?Bt&'[email protected][Q%j-V=`9aWmoOnwf@bG~tm6{U72@o$9HI1rY8sqD'n71MVZ?sjtIJ^RR~x(I9V?3bEV9=E%_oQj-dfO26gb,)~X?v_5H&}8OBC,Zd3FO*6x?^&vV^oAnT8W]VCJ5{1D?cF2hz^y{{p&uDdwpd}h8`NZJv_a3H!)feXUfw]v?_@*Otsy%B'YK$aq~=M9AbjW10uEDJQXE)3'L82.?,2W6FLDxVGn^9T&=1y~9]TMt7^XvHXTYuO[z=6}@L_^wh,(g}ZqJ^O1bEhS?r)iI.5E.A7i&@zDQdtV='FS(W8wl!b1yF'DVKLY={M5MYbn*wOxsSgjVY3D@oGP5W(_$7[fx&!R(pHF=T%$LsMp7?spYDG3w!zC?5B2{8,F)[H!uUfS0'_m?$WG=P,jT7WOo2W_*dsE@=5jq^lyW?1(8?&32w,NAkc8wJs8GCEu1_2Xc^g[?VhL-,XO~{,H,a]zRr,2=]XThvu.EBR0v?pCd&1@?-Rud!Nf*yt-S'NdXk~P99PFN(w0J9RAmQC40IY9AQKBcb!S?=CnT=EuzE1q=w)`V(40a'jdyXR+pN}`A.UP3IQjE(9xOtNZV!)e9YJ=NzOE[$(Itp!&{M^09-FPfKKbD1uIz}V_z3K^9t3U4Tvo(Gq8eyV`z3K^9b)@zEvo(Gq}1+M!-vLb9Y{kU8s)9cs`p`b,X*][=!CtK^UfdUy]u[kDa&5C?dr&Nb_m6L%E'Tes__*W=Cf)0-^yp**S{$*8j'~D=bv,m!@w5F5^Yvr?u^T??[Dr^?X5&DC{BJ]9S.IY?X_+EYCq`~aII17]HE$Y=G,N.-Z]Nu9F
MSI (s) (80:88) [11:29:10:862]: Executing op: FeaturePublish(Feature=SMConsole,,Absent=2,Component=-t's,QtH^Aw+6FO*=Se(iQRgqk%_g=dT63!k9!rD@dhrK&d7h=K@C5tXh+0WxiGiG5${}83t&igNy{fY&JO-tv~W3Ah1fGYB1.`B!^o%uu!H)9R}66fvSA0Wv%z,9-1jG9y?v}nwk!s?K=B`'Nk^.93`591RA^Ebzru^Hg?vMA6WScC*[V.DUtMfGl+Os98*Wc&+YY[2abg{3@n-]@5Gxvon=g76CVQ~Ijn^X9P2H12*)v(!KYwG+v*QS={[,{TMbA'(jZhl`KmU$?Vez&@)YK[mVm~2X&18E@])Ry4^X^KQ`vnk@+v{B?dAn}YD*9*5S_~w'M?2c?s8Sf^yA)9@nE@ABBSrt8T++.V{d4gb6,p$83`m4?OV9^r0F`IO[`o_-lb2}91AcKjfKCE2=q?*Gk,g'?2O7pkHrC*](^yu[K}-S9elzyj=2zt[iF(M2nb-z9sgF?29J6($ZQAS%izDO9oq$k`dG4]?OicWT^[Y=AlFJBP05%gId7HBQ9jDv?bh(2W~-B+J%ZHxQK2k4?Umi{dWK[GK_mG&(el!^AR,YT-X9P-m(9%C-l..z==Oh(RE,xmDS6=!lKz,O=&,deE`++iQ5VCXL[Y^Z?LB7r)u}k4n7=LtnTJwZA)eY8vfB@7vvdYD(a8ZU=qVm47sBI?iaZk6p!S]8?6D_x4Z7cJjqfl~xo!zh@7X%ORA?XADrzW?JWEfO9?9@$3t_Qr`{kPS!rsu19(OfCf'~0~Po4[nv@Xp]=P^LkdkaG14a99ww^FX2@Amv.^j+f3M*e)H?o6qr@fx9b'rGbrKH@FR8}kA.9^kv{98D@Qy?cq4uLo2o=_8G4&1&IqY(CeD&$F@G@MdV7cI5ewzftyD$`o_k=~X5yoL3!&A`NSB.WH!LA3(1Rmkk9?ethX(x,HWR9_OUZ=H!k3Xko]}oWUVJ@QG{ztU'eAplc=@70chp9&@F34p~'T)CfM[I(VWm9.a`6U-hvjpUZDg96]v?@_S7.CdN=Uj
MSI (s) (80:88) [11:29:10:908]: Executing op: ActionStart(Name=_StartNamedServices_CoreServices.80B659D9_F758_4E7D_B4FA_E53FC737DCC9,,)
MSI (s) (80:88) [11:29:10:910]: Executing op: CustomActionSchedule(Action=_StartNamedServices_CoreServices.80B659D9_F758_4E7D_B4FA_E53FC737DCC9,ActionType=3649,Source=BinaryData,Target=StartNamedServices,CustomActionData=HealthService System Center Management
APM)
MSI (s) (80:88) [11:29:10:913]: Executing op: ActionStart(Name=PublishProduct,Description=Publishing product information,)
MSI (s) (80:88) [11:29:10:918]: Executing op: CleanupConfigData()
MSI (s) (80:88) [11:29:10:918]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\5BA67A970AE3F4C4989BC10A4083CEE2\Patches 3: 2
MSI (s) (80:88) [11:29:10:918]: Executing op: RegisterPatchOrder(Continue=0,SequenceType=1,Remove=0)
MSI (s) (80:88) [11:29:10:918]: Note: 1: 1402 2: UNKNOWN\Products\5BA67A970AE3F4C4989BC10A4083CEE2\Patches 3: 2
MSI (s) (80:88) [11:29:10:923]: Executing op: ProductPublish(PackageKey={1B3B79AF-1391-4E6E-9BE2-2BD0832DADE7})
MSI (s) (80:88) [11:29:10:932]: Note: 1: 1402 2: UNKNOWN\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2 3: 2
MSI (s) (80:88) [11:29:10:932]: Note: 1: 1402 2: UNKNOWN\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2 3: 2
MSI (s) (80:88) [11:29:10:932]: Note: 1: 1402 2: UNKNOWN\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2 3: 2
MSI (s) (80:88) [11:29:10:932]: Note: 1: 1402 2: UNKNOWN\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2 3: 2
MSI (s) (80:88) [11:29:10:932]: Note: 1: 1402 2: UNKNOWN\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2 3: 2
MSI (s) (80:88) [11:29:10:932]: Note: 1: 1402 2: UNKNOWN\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2 3: 2
MSI (s) (80:88) [11:29:10:932]: Note: 1: 1402 2: UNKNOWN\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2 3: 2
MSI (s) (80:88) [11:29:10:932]: Note: 1: 1402 2: UNKNOWN\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2 3: 2
MSI (s) (80:88) [11:29:10:932]: Note: 1: 1402 2: UNKNOWN\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2 3: 2
MSI (s) (80:88) [11:29:10:932]: Note: 1: 1402 2: UNKNOWN\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2 3: 2
MSI (s) (80:88) [11:29:10:932]: Note: 1: 1402 2: UNKNOWN\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2 3: 2
MSI (s) (80:88) [11:29:10:942]: Executing op: UpgradeCodePublish(UpgradeCode={4F70C213-6F45-4AA0-8994-1A09CBF27D77})
MSI (s) (80:88) [11:29:10:947]: Executing op: SourceListPublish(,,DiskPromptTemplate=Please Insert Disk 1,,NumberOfDisks=1)
MSI (s) (80:88) [11:29:10:947]: Note: 1: 1402 2: UNKNOWN\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2\SourceList 3: 2
MSI (s) (80:88) [11:29:10:948]: Executing op: ProductPublishClient(,,)
MSI (s) (80:88) [11:29:10:949]: Executing op: SourceListRegisterLastUsed(SourceProduct={79A76AB5-3EA0-4C4F-89B9-1CA00438EC2E},LastUsedSource=E:\SCSM2012sp1\amd64\Setup\Server\)
MSI (s) (80:88) [11:29:10:949]: Entering CMsiConfigurationManager::SetLastUsedSource.
MSI (s) (80:88) [11:29:10:963]: Specifed source is already in a list.
MSI (s) (80:88) [11:29:10:963]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (80:88) [11:29:10:963]: Adding new sources is allowed.
MSI (s) (80:88) [11:29:10:963]: Set LastUsedSource to: E:\SCSM2012sp1\amd64\Setup\Server\.
MSI (s) (80:88) [11:29:10:963]: Set LastUsedType to: n.
MSI (s) (80:88) [11:29:10:963]: Set LastUsedIndex to: 1.
MSI (s) (80:88) [11:29:10:964]: Executing op: ActionStart(Name=_EnabledDiscoveryDataAuthorization,,)
MSI (s) (80:88) [11:29:10:979]: Executing op: CustomActionSchedule(Action=_EnabledDiscoveryDataAuthorization,ActionType=1537,Source=BinaryData,Target=EnabledDiscoveryDataAuthorization,)
MSI (s) (80:88) [11:29:11:086]: Executing op: ActionStart(Name=_RegisterVssExpressWriterSM,,)
MSI (s) (80:88) [11:29:11:104]: Executing op: CustomActionSchedule(Action=_RegisterVssExpressWriterSM,ActionType=1089,Source=BinaryData,Target=RegisterVssExpressWriterSM,CustomActionData=SCSMSMDBDOMAIN,DOMAIN|ServiceManager)
MSI (s) (80:EC) [11:29:11:173]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI36AB.tmp, Entrypoint: RegisterVssExpressWriterSM
CAPACK: Extracting custom action to temporary directory: C:\Windows\Installer\MSI36AB.tmp-\
CAPACK: CLR version v2.0.50727 is installed.
CAPACK: CLR version v2.0.50727 is detected.
CAPACK: CLR version v4.0.30319 is installed.
CAPACK: CLR version v4.0.30319 is detected.
CAPACK: Binding to CLR version v2.0.50727
Calling custom action CAManaged!Microsoft.MOMv3.Setup.VssWriterCAs.RegisterVssExpressWriterSM
RegisterVssExpressWriter: Registering VSS express writer.
MSI (s) (80:EC) [11:29:15:881]: NOTE: custom action _RegisterVssExpressWriterSM unexpectedly closed the hInstall handle (type MSIHANDLE) provided to it. The custom action should be fixed to not close that handle.
MSI (s) (80:88) [11:29:15:884]: Executing op: ActionStart(Name=_Rollback_RegisterVssExpressWriterSM,,)
RegisterVssExpressWriter: Registered VSS express writer.
MSI (s) (80:88) [11:29:15:896]: Executing op: CustomActionSchedule(Action=_Rollback_RegisterVssExpressWriterSM,ActionType=1345,Source=BinaryData,Target=RemoveVssExpressWriterSM,)
MSI (s) (80:88) [11:29:15:975]: Executing op: End(Checksum=0,ProgressTotalHDWord=0,ProgressTotalLDWord=639325328)
MSI (s) (80:88) [11:29:42:385]: An error occured while refreshing environment variables updated during the installation of ''. Some users logged on to the machine may not see these changes until they log off and then log back on.
MSI (s) (80:88) [11:29:42:445]: Note: 1: 2265 2: 3: -2147287035
MSI (s) (80:88) [11:29:42:446]: User policy value 'DisableRollback' is 0
MSI (s) (80:88) [11:29:42:446]: Machine policy value 'DisableRollback' is 0
MSI (s) (80:88) [11:29:42:452]: Note: 1: 2265 2: 3: -2147287035
MSI (s) (80:54) [11:29:42:890]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIB293.tmp, Entrypoint: StopNamedServices
MSI (s) (80:BC) [11:29:43:709]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIB40B.tmp, Entrypoint: ExecNetFx
MSI (s) (80:BC) [11:29:43:731]: Generating random cookie.
MSI (s) (80:BC) [11:29:44:395]: Created Custom Action Server with PID 4800 (0x12C0).
MSI (s) (80:F0) [11:29:45:368]: Running as a service.
MSI (s) (80:F8) [11:29:45:393]: Hello, I'm your 32bit Elevated custom action server.
MSI (s) (80:F0) [11:29:45:460]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIBCA7.tmp, Entrypoint: ExecNetFx
MSI (s) (80:F4) [11:29:45:593]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIBCF6.tmp, Entrypoint: ExecNetFx
MSI (s) (80:EC) [11:29:45:662]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIBD83.tmp, Entrypoint: ExecNetFx
ExecNetFx: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe install "E:\Program Files\Microsoft System Center 2012\Service Manager\Microsoft.EnterpriseManagement.UI.ConsoleFramework.dll" /queue:1
ExecNetFx: Microsoft (R) CLR Native Image Generator - Version 4.0.30319.33440
ExecNetFx: Copyright (c) Microsoft Corporation. All rights reserved.
ExecNetFx: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe install "E:\Program Files\Microsoft System Center 2012\Service Manager\Microsoft.EnterpriseManagement.UI.Foundation.dll" /queue:1
ExecNetFx: Microsoft (R) CLR Native Image Generator - Version 4.0.30319.33440
ExecNetFx: Copyright (c) Microsoft Corporation. All rights reserved.
ExecNetFx: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe install "E:\Program Files\Microsoft System Center 2012\Service Manager\Microsoft.EnterpriseManagement.UI.Controls.dll" /queue:1
ExecNetFx: Microsoft (R) CLR Native Image Generator - Version 4.0.30319.33440
ExecNetFx: Copyright (c) Microsoft Corporation. All rights reserved.
ExecNetFx: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe install "E:\Program Files\Microsoft System Center 2012\Service Manager\Microsoft.EnterpriseManagement.UI.ViewFramework.dll" /queue:1
ExecNetFx: Microsoft (R) CLR Native Image Generator - Version 4.0.30319.33440
ExecNetFx: Copyright (c) Microsoft Corporation. All rights reserved.
ExecNetFx: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe install "E:\Program Files\Microsoft System Center 2012\Service Manager\Microsoft.EnterpriseManagement.UI.WpfViews.dll" /queue:1
ExecNetFx: Microsoft (R) CLR Native Image Generator - Version 4.0.30319.33440
ExecNetFx: Copyright (c) Microsoft Corporation. All rights reserved.
ExecNetFx: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe install "E:\Program Files\Microsoft System Center 2012\Service Manager\Microsoft.EnterpriseManagement.UI.ExtendedControls.dll" /queue:1
ExecNetFx: Microsoft (R) CLR Native Image Generator - Version 4.0.30319.33440
ExecNetFx: Copyright (c) Microsoft Corporation. All rights reserved.
ExecNetFx: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe install "E:\Program Files\Microsoft System Center 2012\Service Manager\CommunicatorAPIInterop.dll" /queue:1
ExecNetFx: Microsoft (R) CLR Native Image Generator - Version 4.0.30319.33440
ExecNetFx: Copyright (c) Microsoft Corporation. All rights reserved.
ExecNetFx: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe install "E:\Program Files\Microsoft System Center 2012\Service Manager\CommunicatorPrivateInterop.dll" /queue:1
ExecNetFx: Microsoft (R) CLR Native Image Generator - Version 4.0.30319.33440
ExecNetFx: Copyright (c) Microsoft Corporation. All rights reserved.
ExecNetFx: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe install "Microsoft.EnterpriseManagement.Core, Version=7.0.5000.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" /queue:2
ExecNetFx: Microsoft (R) CLR Native Image Generator - Version 4.0.30319.33440
ExecNetFx: Copyright (c) Microsoft Corporation. All rights reserved.
ExecNetFx: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe update /queue
ExecNetFx: Microsoft (R) CLR Native Image Generator - Version 4.0.30319.33440
ExecNetFx: Copyright (c) Microsoft Corporation. All rights reserved.
MSI (s) (80:9C) [11:29:50:885]: Invoking remote custom action. DLL: C:\Windows\Installer\MSID199.tmp, Entrypoint: ConfigureSDKConfigService
ConfigureSDKConfigService: Custom action data property value. 1 OMCFG
ConfigureSDKConfigService: RHS so start services. 1
CAStartServices: CAStartServices was passed . OMCFG
CAStartServices: Checking if service already started. OMCFG
CAStartServices: Attempting to start service. OMCFG
ConfigureSDKConfigService: CAStartServices succeeded!. OMCFG
MSI (s) (80:F4) [11:30:01:168]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIF733.tmp, Entrypoint: ConfigureSDKConfigService
ConfigureSDKConfigService: Custom action data property value. 1 OMSDK
ConfigureSDKConfigService: RHS so start services. 1
CAStartServices: CAStartServices was passed . OMSDK
CAStartServices: Attempting to start service. OMSDK
MSI (s) (80:A0) [11:30:04:965]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI82C.tmp, Entrypoint: WaitForSDKServiceStart
CAPACK: Extracting custom action to temporary directory: C:\Windows\Installer\MSI82C.tmp-\
CAPACK: CLR version v2.0.50727 is installed.
CAPACK: CLR version v2.0.50727 is detected.
CAPACK: CLR version v4.0.30319 is installed.
CAPACK: CLR version v4.0.30319 is detected.
CAPACK: Binding to CLR version v2.0.50727
Calling custom action CAManaged!Microsoft.MOMv3.Setup.MOMv3ManagedCAs.WaitForSDKServiceStart
WaitForSDKServiceStart:Entering
WaitForSDKServiceStart: Error: The client has been disconnected from the server. Please call ManagementGroup.Reconnect() to reestablish the connection.,
Stack:    at Microsoft.EnterpriseManagement.Common.Internal.ExceptionHandlers.HandleChannelExceptions(Exception ex)
   at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.CreateEndpoint(EnterpriseManagementConnectionSettings connectionSettings, SdkChannelObject`1 channelObjectDispatcherService)
   at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.ConstructEnterpriseManagementGroupInternal(EnterpriseManagementConnectionSettings connectionSettings, ClientDataAccessCore clientCallback)
   at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.RetrieveEnterpriseManagementGroupInternal(EnterpriseManagementConnectionSettings connectionSettings, ClientDataAccessCore callbackDispatcherService)
   at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.Connect(EnterpriseManagementConnectionSettings connectionSettings, ClientDataAccessCore callbackDispatcherService)
   at Microsoft.EnterpriseManagement.EnterpriseManagementGroup.InternalInitialize(EnterpriseManagementConnectionSettings connectionSettings, EnterpriseManagementGroupInternal internalsProxy)
   at Microsoft.EnterpriseManagement.EnterpriseManagementGroup.Connect(EnterpriseManagementConnectionSettings connectionSettings)
   at Microsoft.MOMv3.Setup.MOMv3ManagedCAs.WaitForSDKServiceStart(Session session)
MSI (s) (80:A0) [11:30:36:809]: NOTE: custom action _WaitForSDKServiceStart unexpectedly closed the hInstall handle (type MSIHANDLE) provided to it. The custom action should be fixed to not close that handle.
CustomAction _WaitForSDKServiceStart returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (80:88) [11:30:37:805]: Executing op: Header(Signature=1397708873,Version=500,Timestamp=1156471542,LangId=0,Platform=589824,ScriptType=2,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=1)
MSI (s) (80:88) [11:30:37:805]: Executing op: DialogInfo(Type=0,Argument=0)
MSI (s) (80:88) [11:30:37:806]: Executing op: DialogInfo(Type=1,Argument=Microsoft System Center 2012 - Service Manager)
MSI (s) (80:88) [11:30:37:807]: Executing op: RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Rolling back action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription=Removing backup files,CleanupTemplate=File: [1])
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835ea.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835eb.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835ec.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835ed.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835ee.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835ef.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835f0.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835f1.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835f2.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835f3.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835f4.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835f5.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835f6.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835f7.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835f8.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835f9.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835fa.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835fb.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835fc.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835fd.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835fe.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835ff.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\8883600.rbf)
MSI (s) (80:88) [11:30:40:009]: Executing op: ActionStart(Name=_Rollback_RegisterVssExpressWriterSM,,)
MSI (s) (80:88) [11:30:40:013]: Executing op: ProductInfo(ProductKey={79A76AB5-3EA0-4C4F-89B9-1CA00438EC2E},ProductName=Microsoft System Center 2012 - Service Manager,PackageName=SM.msi,Language=0,Version=117771097,Assignment=1,ObsoleteArg=0,ProductIcon=ServiceManager.ico,,PackageCode={1B3B79AF-1391-4E6E-9BE2-2BD0832DADE7},,,InstanceType=0,LUASetting=0,RemoteURTInstalls=0,ProductDeploymentFlags=3)
MSI (s) (80:88) [11:30:40:029]: Executing op: CustomActionRollback(Action=_Rollback_RegisterVssExpressWriterSM,ActionType=1345,Source=BinaryData,Target=RemoveVssExpressWriterSM,)
MSI (s) (80:EC) [11:30:40:772]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI920E.tmp, Entrypoint: RemoveVssExpressWriterSM
CAPACK: Extracting custom action to temporary directory: C:\Windows\Installer\MSI920E.tmp-\
CAPACK: CLR version v2.0.50727 is installed.
CAPACK: CLR version v2.0.50727 is detected.
CAPACK: CLR version v4.0.30319 is installed.
CAPACK: CLR version v4.0.30319 is detected.
CAPACK: Binding to CLR version v2.0.50727
Calling custom action CAManaged!Microsoft.MOMv3.Setup.VssWriterCAs.RemoveVssExpressWriterSM
RemoveVssExpressWriter: Unregistering VSS express writer.
MSI (s) (80:EC) [11:30:43:808]: NOTE: custom action _Rollback_RegisterVssExpressWriterSM unexpectedly closed the hInstall handle (type MSIHANDLE) provided to it. The custom action should be fixed to not close that handle.
RemoveVssExpressWriter: VSS express writer unregister succeeded.
MSI (s) (80:88) [11:30:43:834]: Executing op: ActionStart(Name=_RegisterVssExpressWriterSM,,)
MSI (s) (80:88) [11:30:43:853]: Executing op: ActionStart(Name=_EnabledDiscoveryDataAuthorization,,)
MSI (s) (80:88) [11:30:43:862]: Executing op: ActionStart(Name=PublishProduct,Description=Publishing product information,)
MSI (s) (80:88) [11:30:43:892]: Executing op: RegOpenKey(Root=-2147483646,Key=Software\Classes\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2\SourceList\Net,SecurityDescriptor=BinaryData,BinaryType=1,,)
MSI (s) (80:88) [11:30:43:898]: Executing op: RegOpenKey(Root=-2147483646,Key=Software\Classes\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2\SourceList,SecurityDescriptor=BinaryData,BinaryType=1,,)
MSI (s) (80:88) [11:30:43:910]: Executing op: RegRemoveValue(Name=LastUsedSource,Value=#%n;1;E:\SCSM2012sp1\amd64\Setup\Server\,)
MSI (s) (80:88) [11:30:43:916]: Executing op: RegCreateKey()
MSI (s) (80:88) [11:30:43:925]: Executing op: RegOpenKey(Root=-2147483646,Key=Software\Classes\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2,SecurityDescriptor=BinaryData,BinaryType=1,,)
MSI (s) (80:88) [11:30:43:930]: Executing op: RegRemoveValue(Name=Clients,Value=[~]:,)
MSI (s) (80:88) [11:30:43:937]: Executing op: RegCreateKey()
MSI (s) (80:88) [11:30:43:944]: Executing op: RegOpenKey(Root=-2147483646,Key=Software\Classes\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2\SourceList\Media,SecurityDescriptor=BinaryData,BinaryType=1,,)
MSI (s) (80:88) [11:30:43:951]: Executing op: RegRemoveValue(Name=1,Value=;,)
MSI (s) (80:88) [11:30:43:959]: Executing op: RegCreateKey()
MSI (s) (80:88) [11:30:43:980]: Executing op: RegOpenKey(Root=-2147483646,Key=Software\Classes\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2\SourceList\Media,,BinaryType=1,,)
MSI (s) (80:88) [11:30:43:986]: Executing op: RegRemoveValue(Name=DiskPrompt,Value=Please Insert Disk 1,)
MSI (s) (80:88) [11:30:43:994]: Executing op: RegRemoveKey()
MSI (s) (80:88) [11:30:43:994]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Classes\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2\SourceList\Media 3: 2
MSI (s) (80:88) [11:30:43:999]: Executing op: RegOpenKey(Root=-2147483646,Key=Software\Classes\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2\SourceList\Net,,BinaryType=1,,)
MSI (s) (80:88) [11:30:44:005]: Executing op: RegRemoveValue(Name=1,Value=#%E:\SCSM2012sp1\amd64\Setup\Server\,)
MSI (s) (80:88) [11:30:44:011]: Executing op: RegRemoveKey()
MSI (s) (80:88) [11:30:44:011]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Classes\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2\SourceList\Net 3: 2
MSI (s) (80:88) [11:30:44:017]: Executing op: RegOpenKey(Root=-2147483646,Key=Software\Classes\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2\SourceList,,BinaryType=1,,)

SCSM + Orchestrator Licensing

Similar Messages

Maybe you are looking for