Management Group Not Configured

Hello,
My SCOM 2012 R2 server was upgraded from 2007 R2 CU7. Now that it is SCOM 2012 R2, I noticed in the Event Log that I have this error multiple times:
OpsMgr has no configuration for management group xxxx and is requesting new configuration from the Configuration Service.
How do i resolve this?

Hi,
Have you load the latest update for SCOM 2012 R2?
http://blogs.technet.com/b/momteam/archive/2014/01/28/issues-that-are-fixed-in-system-center-2012-r2-operations-manager-update-rollup-1.aspx
If so, you may need to reinstall management servers and re-configure the management group.
Niki Han
TechNet Community Support

Similar Messages

Enterprise Manager is not configured to monitor node rac2

Hi
DB=11.2.0.2
i installed my database on RAC with 2nodes.all of the things is ok:
$ emca -displayconfig dbcontrol -cluster
**************** Current Configuration ****************
INSTANCE NODE DBCONTROL_UPLOAD_HOST
orcl rac1 rac1.irisad.net
orcl rac2 rac1.irisad.net
and i execute command $ emca -reconfig dbcontrol -cluster -EM_NODE rac1 -EM_SID_LIST orcl1,orcl2
but Enterprise Manager is not configured to monitor node rac2 and i see only rac1!!!
what i must to do???pls help.

open dbconsole and see if both instance are coming in monitoring tab or not.
http://docs.oracle.com/cd/E11882_01/server.112/e10595/dbcontrol002.htm

A device which is not part of this management group has attempted to access this Health Service.

Has anyone found an answer to this yet? I have uninstalled/reinstalled the agents both manually and through the push. Rebooted the client, rebooted the sce server. Forced the group policy to reapply, forced the health agent to /reportnow and I still get the error. The client shows up under the agent managed section but under the health state column it shows not monitored. The clients can ping the SCE server by FQDN and RDP to it as well so name resolution is working fine.
On the the SCE server I get this in the log
Event Type: Information
Event Source: OpsMgr Connector
Event Category: None
Event ID: 20000
Date:  6/25/2009
Time:  10:09:40 AM
User:  N/A
Computer: *******
Description:
A device which is not part of this management group has attempted to access this Health Service.
Requesting Device Name : *****
And this
Event Type:            Information
Event Source:           OpsMgr Connector
Event Category:       None
Event ID: 21042
Date:                        6/25/2009
Time:                       10:25:14 AM
User:                        N/A
Computer:                ***********
Description:
Operations Manager has discarded 1 items in management group Servername_MG, which came from $$ROOT$$. These items have been discarded because no valid route exists at this time. This can happen when new devices are added to the topology but the complete topology has not been distributed yet. The discarded items will be regenerated.
On the client I get
Event Type: Error
Event Source: OpsMgr Connector
Event Category: None
Event ID: 20070
Date:  06/25/2009
Time:  10:06:13 AM
User:  N/A
Computer: ******
Description:
The OpsMgr Connector connected to ****** but the connection was closed immediately after authentication occured. The most likely cause of this error is that the agent is not authorized to communicate with the server, or the server has not received configuration. Check the event log on the server for the presence of 20000 events, indicating that agents which are not approved are attempting to connect.
And this as well
Event Type:            Error
Event Source:           OpsMgr Connector
Event Category:       None
Event ID: 21016
Date:                        06/25/2009
Time:                       10:06:18 AM
User:                        N/A
Computer:                ******
Description:
OpsMgr was unable to set up a communications channel to **** and there are no failover hosts. Communication will resume when ******* is both available and allows communication from this computer.
And this
OpsMgr has no configuration for management group Servername_MG and is requesting new configuration from the Configuration Service.

Hey Nathan,
Yea I have sent the script to eveyone that has aked for it. I dont know if its helped anybody else as none has given me any feedback either way.
I guess I can post it here for everyone to use.
Please keep in mind that if you use this script from MS its at your own risk, If your DB blows up, massive catastrophic failure ensues and so forth ITS YOUR OWN FAULT. MAKE SURE YOU HAVE GOOD BACKUPS
Step 1) Run this against your SCE 2007 DB
DECLARE @BaseManagedEntityInternalId int
DECLARE @BaseManagedEntityId uniqueidentifier
DECLARE @ViewName sysname
DECLARE @Statement nvarchar(max)
SET @BaseManagedEntityInternalId = 0
WHILE EXISTS (SELECT * FROM BaseManagedEntity WHERE (BaseManagedEntityInternalId >
@BaseManagedEntityInternalId))
BEGIN
SELECT TOP 1
@BaseManagedEntityInternalId = bme.BaseManagedEntityInternalId
,@BaseManagedEntityId = bme.BaseManagedEntityId
,@ViewName = met.ManagedTypeViewName
FROM BaseManagedEntity bme
JOIN ManagedType met ON (bme.BaseManagedTypeId = met.ManagedTypeId)
WHERE (bme.BaseManagedEntityInternalId > @BaseManagedEntityInternalId)
AND (bme.IsDeleted = 0)
ORDER BY BaseManagedEntityInternalId
SELECT @Statement = 'IF NOT EXISTS (SELECT * FROM ' + QUOTENAME(@ViewName) + '
WHERE BaseManagedEntityId = ''' + CAST(@BaseManagedEntityId AS varchar(50)) + ''')
PRINT ''' + CAST(@BaseManagedEntityId AS varchar(50)) + ' ' + @ViewName + ''''
EXECUTE(@Statement)
END
STEP 2)
If your problem was the same a mine you should get some GUID’s returned. (For example 93790c0B-09C4-3A4D-CE72-F4E3Dd917D78 MTV_DeploymentSettings)
Using the GUID that we got in the output file
Execute the below given query:
==========================
select fullname
from basemanagedentity
where basemanagedentityid = ‘<GUID>’
==========================
Verify that the device or the object mentioned in the above output is not displayed in Operations console.
Only in case if the object is not displayed then use the below given query to delete it from database.
==========================
update basemanagedentity
set isdeleted = 1
where basemanagedentityid = ‘<GUID>’
==========================
Before executing the above query please ensure that you have the backup of the database. Also note that you need to run the above said query only incase if you do not see the object in the Operations console.
After executing this query, run this stored procedure:
==========================
exec p_Detectandfixinstancespaceinconsistencies
==========================
Once it is done:
> Stop all the three OpsMgr services: health, Config and SDK on Management Server
> Cleared the health service state folder.
> Start all the three OpsMgr services: SDK, Config, and health on Management Server.
> Wait for 30 minutes and see if the agents start getting monitored.
I hope this helps everyone

SCOM Connected Management Group to SCSM Connector not working

Hi
We have successfully connected 3 management groups using Connected Management Group . I can see the alerts from all the 3 MG in one console. I also configured SCSM connector and connected to the local Management where the other 2 are connected . I can successfully
forward the alerts from that MG which is registered in SCSM , but when I try to forward the alerts from the other 2 mg I get the below message on the respective Management servers . Is connected management group supported in SCSM . Or am I missing any step
need
Log Name:      Operations Manager
Source:        DataAccessLayer
Date:          11/4/2014 4:58:20 PM
Event ID:      33333
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      server
Description:
Data Access Layer rejected retry on SqlError:
Request: AlertUpdate -- (AlertId=c89b3ebc-2e45-47e9-a6d8-e96c05b787f3), (BaseManagedEntityId=9f8aa0d1-1b31-d133-e66a-a91830a42405), (ResolutionState=0), (Owner=), (CustomField1=), (CustomField2=), (CustomField3=), (CustomField4=), (CustomField5=), (CustomField6=),
(CustomField7=), (CustomField8=), (CustomField9=), (CustomField10=), (Comments=Alert modified by user), (TimeLastModified=10/14/2014 5:28:11 AM), (ModifiedBy=xx\xxxx), (TicketId=), (ConnectorId=a680dc76-2fc2-429d-b6dd-d1a851e9bd8f), (ModifyingConnectorId=),
(TfsWorkItemId=), (TfsWorkItemOwner=), (RETURN_VALUE=1)
Class: 16
Number: 547
Message: The UPDATE statement conflicted with the FOREIGN KEY constraint "FK_Alert_ConnectorId". The conflict occurred in database "OperationsManager", table "dbo.Connector", column 'ConnectorId'.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="DataAccessLayer" />
    <EventID Qualifiers="32768">33333</EventID>
    <Level>3</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-11-05T00:58:20.000000000Z" />
    <EventRecordID>35534</EventRecordID>
    <Channel>Operations Manager</Channel>
    <Computer>server</Computer>
    <Security />
</System>
<EventData>
    <Data>AlertUpdate -- (AlertId=c89b3ebc-2e45-47e9-a6d8-e96c05b787f3), (BaseManagedEntityId=9f8aa0d1-1b31-d133-e66a-a91830a42405), (ResolutionState=0), (Owner=), (CustomField1=), (CustomField2=), (CustomField3=), (CustomField4=), (CustomField5=),
(CustomField6=), (CustomField7=), (CustomField8=), (CustomField9=), (CustomField10=), (Comments=Alert modified by user), (TimeLastModified=10/14/2014 5:28:11 AM), (ModifiedBy=FAREAST\v-sanaug), (TicketId=), (ConnectorId=a680dc76-2fc2-429d-b6dd-d1a851e9bd8f),
(ModifyingConnectorId=), (TfsWorkItemId=), (TfsWorkItemOwner=), (RETURN_VALUE=1)</Data>
    <Data>16</Data>
    <Data>547</Data>
    <Data>The UPDATE statement conflicted with the FOREIGN KEY constraint "FK_Alert_ConnectorId". The conflict occurred in database "OperationsManager", table "dbo.Connector", column 'ConnectorId'.</Data>
</EventData>
</Event>

For Fix error 33333, you can refer below links
http://opsmgradmin.blogspot.com/2011/05/scom-event-id-33333-in-scom-from-source.html
http://blogs.technet.com/b/smsandmom/archive/2008/03/13/opsmgr-2007-dataaccesslayer-event-id-33333-with-should-not-generate-data-about-this-managed-object.aspx
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
Mai Ali | My blog: Technical | Twitter:
Mai Ali

The Em Key is not configured properly or is corrupted in the file system and doe s not exist in the Management Repository.

I'm getting this error and is there any way to resolve this without re-creating the service/s again, etc. Just curious if there are any suggestions/steps I may have missed, if not, I'll drop and recreate the services again
Anyway, I have a backup of the emkey.ora and put it in the sysman/config directory, but still doesn't work... please see below...
C:\Documents and Settings\abigail>emctl status emkey
Oracle Enterprise Manager 11g Database Control Release 11.2.0.1.0
Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved.
Please enter repository password:
The Em Key is not configured properly or is corrupted in the file system and doe
s not exist in the Management Repository. To correct the problem:
1) Copy the emkey.ora file from another OMS or backup machine to the OH/sysman/c
onfig directory.
2) Configure the emkey.ora file by running "emctl config emkey -emkeyfile <emkey
.ora file location>".
C:\Documents and Settings\abigail>emctl config emkey -emkeyfile E:\app\abigail\p
roduct\11.2.0\dbhome_1\sysman\config
Oracle Enterprise Manager 11g Database Control Release 11.2.0.1.0
Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved.
Please enter repository password:
The Em Key is already configured. To override the current configuration, run "em
ctl config emkey <options> -force".
C:\Documents and Settings\abigail>emctl config emkey -emkeyfile E:\app\abigail\p
roduct\11.2.0\dbhome_1\sysman\config -force -sysman_pwd ********
Oracle Enterprise Manager 11g Database Control Release 11.2.0.1.0
Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved.
The Em Key could not be configured. Unable to access file E:\app\abigail\product
\11.2.0\dbhome_1\sysman\config.
C:\Documents and Settings\abigail>emctl secure dbconsole -sysman_pwd ********
Oracle Enterprise Manager 11g Database Control Release 11.2.0.1.0
Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved.
http://ABIGAIL:5501/em/console/aboutApplication
DBCONSOLE already stopped...   Done.
Agent is already stopped...   Done.
Securing dbconsole...   Started.
Please enter repository schema password:
Securing dbconsole...   Failed.
EMKey is misconfigured.

Sorry but I'll have to ignore your suggestion, and don't worry about how I spend my time
AND OHMYGODD IT WORKSS!!! For future reference, this is how I solved it based on my searches, actually based on one particular search:
http://franjv.blogspot.com/2013/08/emkey-problems-in-oracle-rac-11gr2.html
Thank youuu whoever wrote that and... is it the same "Fran" who helped me the last time?!? Coincidence??
ANyway, thank youuuu

SCOM 2012 RC - SCVMM 2012 RC - Virtual machine manager management group is not getting monitored

Hi All,
I have integrated SCOM 2012 with SCVMM 2012 environment. I could see two strange behaviors. All these instance are running on Windows 2008 R2 + Sp1 OS along with SQL 2008 R2 for database.
1) I could see two instance of VirtualmanagerDB
in the Database State view under the Microsoft SQL Server, out of that
one is showing as monitored and another one is
showing as not monitored. Why it is showing two instance of the same database? How can I remove the not monitored one?
2) In the distributed apps- Virtual machine manager management group is not showing as a monitored item. However the SCVMM server is getting monitored.
I'd appreciate if someone could help me out in understanding and resolving this.
Regards,
Ren.

Hi
I opened up a connect ticket on this on 17th Jan so sorry for not noticing your post earlier. The response was:
Health State dashboard view is targeted to two state views. "Agent Watcher State" and "Agent State". "Agent State" view (view with duplicate entry) is targeted to an abstract class "VMM Agent" which has below child classes.
    VMM Library Agent
    VMM Host Agent
    Guest Agent
For the Dashboard view, we need to taget the view to "Host Agent" not "VMM Agent". When we install VMM, it adds itself as a Library server and that is the reason for duplicate entry (VMM Library Agent).
Cheers
Graham
Regards Graham New System Center 2012 Blog! -
http://www.systemcentersolutions.co.uk
View OpsMgr tips and tricks at
http://systemcentersolutions.wordpress.com/

Restricted Group setting in GPO is not configured after domain join

Hi all,
I'm configuring a GPO as part of a test environment in which I create a custom GPO for within an OU, it configures fine and I can RDP (using the settings in the GPO) to the domain controller. However, when I add a computer to the AD domain, I cannot RDP
using the user, I can log on locally though. After looking into it further I've found that the setting I have applied to my Restricted Group is not being brought across properly. The group I need is in the restricted group but it is not appearing as a member
of Administrators (in the "Member of") column. I have an 'X' in red next to the group giving the usual check win logon log file. The content of which is:
Make a local copy of \\shire6.vce\sysvol\shire6.vce\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\Machine\Microsoft\Windows NT\SecEdit\GptTmpl.inf.
GPLinkDomain
Make a local copy of \\shire6.vce\SysVol\shire6.vce\Policies\{6D41C716-CDD9-457E-AB89-02C4192226FF}\Machine\Microsoft\Windows NT\SecEdit\GptTmpl.inf.
GPLinkOrganizationUnit
Process GP template gpt00000.dom.
This is not the last GPO.
Monday, April 27, 2015 3:36:03 PM
Copy undo values to the merged policy.
----Un-initialize configuration engine...
Process GP template gpt00001.inf.
Monday, April 27, 2015 3:36:03 PM
----Configuration engine was initialized successfully.----
----Reading Configuration Template info...
----Configure User Rights...
Configure S-1-5-32-545.
remove SeInteractiveLogonRight.
Configure S-1-5-32-551.
remove SeInteractiveLogonRight.
Configure S-1-5-32-555.
remove SeRemoteInteractiveLogonRight.
Configure S-1-5-21-330840483-2018858548-1314766947-1104.
add SeInteractiveLogonRight.
add SeRemoteInteractiveLogonRight.
Configure S-1-5-32-544.
User Rights configuration was completed successfully.
----Configure Group Membership...
Configure SHIRE6\System_Admins.
successfully added object to Administrators.
new memberof tattoo list: *S-1-5-32-544,
Group Membership configuration was completed successfully.
----Configure Security Policy...
0
Undo value for group policy setting <MinimumPasswordLength> was saved.
0
Undo value for group policy setting <PasswordHistorySize> was saved.
42
Undo value for group policy setting <MaximumPasswordAge> was saved.
0
Undo value for group policy setting <MinimumPasswordAge> was saved.
1
Undo value for group policy setting <PasswordComplexity> was saved.
0
Undo value for group policy setting <RequireLogonToChangePassword> was saved.
0
Undo value for group policy setting <ClearTextPassword> was saved.
Configure password information.
0
Undo value for group policy setting <LockoutBadCount> was saved.
0
Undo value for group policy setting <ForceLogoffWhenHourExpire> was saved.
Configure account force logoff information.
System Access configuration was completed successfully.
LSA anonymous lookup names setting : existing SD = D:(D;;0x800;;;AN)(A;;0xf1fff;;;BA)(A;;0x20801;;;WD)(A;;0x801;;;AN)(A;;0x1000;;;LS)(A;;0x1000;;;NS)(A;;0x1000;;;S-1-5-17)(A;;0x801;;;AC).
0
Undo value for group policy setting <LSAAnonymousNameLookup> was saved.
Configure LSA anonymous lookup setting.
Configure machine\system\currentcontrolset\control\lsa\nolmhash.
Mismatch - machine\system\currentcontrolset\control\lsa\nolmhash.
Undo value for group policy setting <machine\system\currentcontrolset\control\lsa\nolmhash> was saved.
Configuration of Registry Values was completed successfully.
Configure event audit settings.
0
Undo value for group policy setting <AuditPrivilegeUse> was saved.
0
Undo value for group policy setting <AuditAccountLogon> was saved.
Audit/Log configuration was completed successfully.
----Configure available attachment engines...
Configuration of attachment engines was completed successfully.
----Un-initialize configuration engine...
this is the last GPO.
Make a local copy of \\shire6.vce\sysvol\shire6.vce\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\Machine\Microsoft\Windows NT\SecEdit\GptTmpl.inf.
GPLinkDomain GPO_INFO_FLAG_BACKGROUND )
Make a local copy of \\shire6.vce\SysVol\shire6.vce\Policies\{6D41C716-CDD9-457E-AB89-02C4192226FF}\Machine\Microsoft\Windows NT\SecEdit\GptTmpl.inf.
GPLinkOrganizationUnit GPO_INFO_FLAG_BACKGROUND )
Process GP template gpt00000.dom.
This is not the last GPO.
Monday, April 27, 2015 3:42:06 PM
Copy undo values to the merged policy.
----Un-initialize configuration engine...
Process GP template gpt00001.inf.
Monday, April 27, 2015 3:42:06 PM
----Configuration engine was initialized successfully.----
----Reading Configuration Template info...
----Configure User Rights...
Configure S-1-5-21-330840483-2018858548-1314766947-1104.
Configure S-1-5-32-544.
User Rights configuration was completed successfully.
----Configure Group Membership...
Configure SHIRE6\System_Admins.
old memberof tattoo list: *S-1-5-32-544,
object already member of Administrators.
new memberof tattoo list: *S-1-5-32-544,
Group Membership configuration was completed successfully.
----Configure Security Policy...
Configure password information.
Configure account force logoff information.
System Access configuration was completed successfully.
LSA anonymous lookup names setting : existing SD = D:(D;;0x800;;;AN)(A;;0xf1fff;;;BA)(A;;0x20801;;;WD)(A;;0x801;;;AN)(A;;0x1000;;;LS)(A;;0x1000;;;NS)(A;;0x1000;;;S-1-5-17)(A;;0x801;;;AC).
Configure LSA anonymous lookup setting.
Configure machine\system\currentcontrolset\control\lsa\nolmhash.
Configuration of Registry Values was completed successfully.
Audit/Log configuration was completed successfully.
----Configure available attachment engines...
Configuration of attachment engines was completed successfully.
----Un-initialize configuration engine...
this is the last GPO.
Any help would be much appreciated.
Thanks,
Adrian

> I cannot RDP using the user
Any error message?
Greetings/Grüße,
Martin
Mal ein
gutes Buch über GPOs lesen?
Good or bad GPOs? - my blog…
And if IT bothers me -
coke bottle design refreshment (-:

Reporting Install fails - Data Reader account is not the same as in management group

We recently upgraded from SCOM 2012 SP1 to R2, but I'm unable to get the reporting role installed. I get to the part where I enter the Data Reader account credentials, then get the error "Data Reader account provided is not same as that in the management
group." No matter what I do I cannot get passed this error.
Here is what I have tried so far:
- I have verified the correct DR account is set in the Data Warehouse Report deployment account and profile.
- I have deleted the DR account from the profile and added it back.
- Verified all permissions are setup properly on the SQL server for all databases, included reporting.
- Completely uninstalled SSRS and re-installed.

you must distribute the Run As account to ensure that all members of the resource pool (All Management Servers Pools) have access to the permissions in the Run As account.
Also check below link {It's same issue}
http://social.technet.microsoft.com/Forums/systemcenter/en-US/11e25eac-fbde-4ed5-aff5-4faa0563cfbc/scom-2012-reporting-installation-issue?forum=operationsmanagerdeployment
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
Mai Ali | My blog: Technical | Twitter:
Mai Ali

The risks of not configuring the countries in their specific country group?

Hi Experts,
Please let me know the the risks of not configuring the countries in their specific country group /Molga, rather assigning them to international MOLGA 99.
I have in my SAP HR box many countries assigned to their MOLGA, but some of them like say DENMARK is assigned to 99. So please let me know the risk of doing so (like issues with reports etc).
Thanks & Regards, Swapnil Mishra

Hi Swapnil,
Suppose you are customizing the payroll international version for the country UAE. So along with the driver customization you may have to group certain functions for e.g the IF condition for checkeing the SPRN for special run off cycle payments.
We may have to group this function for country UAE ( Molga AE). But during any patch upgrade, this standard function grouping will get reset. i.e the grouping for this function will get resumed to its original version. As a result your grouping for AE will not be there in the Function, which will give you an error while executing the schema. This was experienced to us while we are migrating to EHP 4.
Since there is a standard SAP Product available for country Denmark, you are recommened to proceed with the standard product, rather going for the international version. You may be able to directly use all the standard legal/statutory reports readily available with this product. Else it will cost you huge effort in developing or copying these reports.
Hope this will clarify your query.
Regards
Raviiiiiiiiiii
Edited by: ravishanker m on Feb 18, 2011 6:14 AM

Software Updates Failing - Group Policy Overwritten - Server and Policy NOT CONFIGURED

I have seen a few posts about this issue and group policy overwriting the settings needed by SCCM with the wrong WSUS server. I checked the wuahandlerlog and found this error but it didnt have the server information.
"Group policy settings were overwritten by a higher authority (Domain Controller) to: Server and Policy NOT CONFIGURED"
The only coputer policy that applies to this system does not have WSUS entries in it. Windows update runs ok, and I deleted the WSUS registry keys that were set by a script and reinstall the client still getting the same error. I dont see any GPO local or domain, or reg keys that are setting anything. I have 10 other servers is the same AD container that this is working perfecly on.......
Suggestions????

Check out this GPO:
Computer Configuration -> Administrative Templates -> System -> Group Policy:
"Turn off Local Group Policy Objects processing"
The help text:
"This policy setting prevents Local Group Policy Objects (Local GPOs) from being applied.
By default, the policy settings in Local GPOs are applied before any domain-based GPO policy settings. These policy settings can apply to both users and the local computer. You can disable the processing and application of all Local GPOs to ensure that only
domain-based GPOs are applied.
If you enable this policy setting, the system does not process and apply any Local GPOs.
If you disable or do not configure this policy setting, Local GPOs continue to be applied.
Note: For computers joined to a domain, it is strongly recommended that you only configure this policy setting in domain-based GPOs. This policy setting will be ignored on computers that are joined to a workgroup."
Rolf Lidvall, Swedish Radio (Ltd)

Sharepoint 2013 Active Directory Import- Manager field not updating

Hi,
SharePoint 2013 Active directory import -Manager field not updating
Concern/Issue-
We are using SharePoint and configured the Active Directory Import .First import it seems everything is working fine and OOB Organization chart built using User profile data is coming out right.
Now the user is moved from one Organization Unit to Another.
Now our Manager field is not Updating .There is change in AD manager attribute but not reflecting in the SharePoint User profile.
Manger field is mapped to "manager" attribute in SharePoint.
We tried removing the user and Re-Import using Incremental import but no luck.
Thanks for help in advance
Sachin

Moving a user from one OU to another in AD won't normally change the Manager attribute in AD. You would need to edit the user's organization settings to change the manager value in AD. I've also seen these changes not be picked up unless something
other than just the manager field in AD changing. Try changing something like Office location and see if the manager change is picked up by AD Import.
Paul Stork SharePoint Server MVP
Principal Architect: Blue Chip Consulting Group
Blog: http://dontpapanic.com/blog
Twitter: Follow @pstork
Please remember to mark your question as "answered" if this solves your problem.

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,,)

Error with Transport system not configured that may be related to CHaRM

Who has in depth knowledge on setting up SAP Solution Manager CHaRM. Had an odd problem with the transport system failing when the QA system was shut down for maintenance. Transports were not able to be created or save to. Error message was Transport System not configured. Brought up QA and re-distributed system and Transport group and transport requests started working again.

Hello,
if a system, e.g. QA system, will not be available due to a maintenance task,
we set the status of this system to "temporarily inactive" (see header data in transaction SMSY).
This status allows us, to create new transport requests in DEV-System although consolidation system QA is not available.
(Of course you have to reset the status, when QA-system ist started again.)
Hint: it is not possible to release or to import a transport request, when consolidation system is shut down.
Therefore the developer should pay attention to the messages, which raise in urgent corrections.
best regards
Horst

Response Group Not responding

Hi,
We have lync 2013 environement and we have configured Response Group Service in enviroement. Respnse groups has stop responding. We are getting below event ID :
Log Name:      Lync Server
Source:        LS Response Group Service
Date:          18/07/2014 11:52:56 PM
Event ID:      31165
Task Category: (2001)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Frontend server2 FQDN
Description:
The passive Match Making Service cannot connect to the active Match Making Service.
Access active Match Making Service: Frontend server1 FQDN failed.
Failure occurrences: 23175, since 16/07/2014 3:19:05 AM.
Cause: There may not be an active instance at this moment or connectivity to that machine was lost.
Resolution:
Verify the Microsoft Lync Server 2013 certificate and Microsoft Lync Server 2013 installation and make sure that the active Match Making Service is reachable.
Kindly suggest how to resolve the issue and remove above event.
Thanks
jitender

Do you see the errors on FE1? How many front end servers are in your pool? This looks like a communications error. Can the servers directly communicate with eachother or is there any kind of HLB that's intercepting the traffic?
From FE2, if you ping FE1's FQDN, is the IP address the IP address that's directly assigned to FE1?
If there's anything intercepting traffic, a overactive firewall or endpoint management solution, HLB configuration or other, make sure it's out of the way. If that's not an issue, off-hours it may make sense to bounce the response group services as
well in case an active instance simply isn't available.
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
SWC Unified Communications

11.3.1 remote manage group issues

Ever since we upgraded from 11.2.3a to 11.3.1 when I add people to my remote
manage group they are not given the rights to VL the devices folders and
users. I confirmed that all of the device folders and user source are still
configured under device management configuration. All previous upgrade users
are still functioning as normal. I had to add these rights manually to the
two new users I added post upgrade. Previous to the upgrade I could add
support people to this group that were limited to remote control and view to
all devices and all users (user source eDir) without me having to do
anything extra and the rights tab would populate on its own. Is this a bug
or by design change?

To be honest I was fumbling around with it and basically copied what was
already there from the pre upgrade users to the post upgrade users. I had
actually never explored the assigned rights tab before. So I think what your
saying is the populated rights entries that I saw that only had one VL
option checked in and the rest denied is a new feature populated by the
upgrade then I'm back to square one. Specifically I had to add under
"assigned rights" the device right to the context "/devices" and VL view
and all the rest of the options deny for this new user to see the
workstations. I never had to do that before. before I just added the user to
the remote mngt role and they were able to do only what they needed. Until I
manually added the assigned rights she saw nothing. Is this the way it is
now? the roles no longer give what is needed?
"Shaun Pond" wrote in message
news:[email protected]..
Ccps,
the VL rights are new with 11.3, designed to allow you to stop admins
seeing parts of the "tree" that they're not entitled to...
Shaun Pond
newly reminted as a Knowledge Professional

Management Group Not Configured

Similar Messages

Maybe you are looking for