none
EMC connection fails with Unexpected error [0x145AAC30] executing command 'Get-LinkedRoleGroupForLogonUser' after SP2 is applied

    Pregunta

  • The EMC connection fails with Unexpected error [0x145AAC30] executing command 'Get-LinkedRoleGroupForLogonUser' after SP2 is applied

    This is hosted on a HP E5700 appliance and both nodes have been updated.  All services start and I can connect to the shell. 

    I did notice that if I run a Get-excommand from the shell, the Get-LinkedRoleGroupForLogonUser is not in the list.  Also, the user that I am logged on with is the god account from the root domain that I did all the forest and domain preparation with.  The EX2010 server is a child domain. It had been working up until the SP2 was applied.  Luckily this is in my lab environment that is an exact replica of production.  We are about to move the 5700 into production soon so I am glad we found this out now.  Any ideas?

     


    • Editado Gyrodog jueves, 08 de diciembre de 2011 16:30
    jueves, 08 de diciembre de 2011 16:22

Respuestas

Todas las respuestas

  • We have the same error (but with [0x1760B030]) in our test environment, except that the Exchange Server (2010 SP2) is located in the root domain. The child domain in a new domain tree was added after the root domain and the Exchange Server were installed as this will be the production scenario. The user affected is the principle administrator of the root domain.
    viernes, 09 de diciembre de 2011 15:07
  • we have the same error  0x9F7B030 in our pre-production environment all the servers is located in the root domain
    viernes, 09 de diciembre de 2011 17:05
  • Ok, good to know I am not alone. I will be moving my system into production next week and will just go with SP1 and RU6. I will be keeping an eye on this thread and other posts as I am sure there will be more errors. 
    Clint Weldon
    viernes, 09 de diciembre de 2011 20:24
  • Hi there,

    It appears to be an known issue. I am trying to involve a next level engineer in through our internal channel, and  it may take some day to take effect. Your understanding would be apprceciated.

    Refer to:

    http://blogs.technet.com/b/exchange/archive/2011/12/05/released-exchange-server-2010-sp2.aspx#3470235

     


    Fiona Liao

    TechNet Community Support

    lunes, 12 de diciembre de 2011 10:00
  • under 

    \Microsoft\Exchange Server\V14\RemoteScripts

    rename the file to ConsoleInitialize.ps1  to ConsoleInitialize.old

     create a new one  ConsoleInitialize.ps1  and past this text

    # Copyright (c) 2008 Microsoft Corporation. All rights reserved.  

    # THIS CODE IS MADE AVAILABLE AS IS, WITHOUT WARRANTY OF ANY KIND. THE ENTIRE RISK

    # OF THE USE OR THE RESULTS FROM THE USE OF THIS CODE REMAINS WITH THE USER. 

    #

    # This script is used by Exchange Management Console only to aid filter out based on some conditions.

    #    

     

    $global:ConfirmPreference = "None"

     

    # Get logon user identity

    # For the case of multi-domain topology which has the same prefix for the domain name, such as abc.com and abc.cn,

    # userInfo.Identity.Name is not unique since it only contains the short domain name, for example abc\administrator.

    # So EMC uses the unique security identifier userInfo.WindowsIdentity.User to identify the user when the WindowsIdentity is available.

    function global:Get-LogonUserIdentity ()

    {

    $userInfo = (Get-Variable PSSenderInfo).Value.UserInfo

     

    if ($userInfo.WindowsIdentity -ne $null)

    {

    $userInfo.WindowsIdentity.User.ToString()

    }

    else

    {

    $userInfo.Identity.Name

    }

    }

     

    # Get logon user

    function global:Get-LogonUser ()

    {

    BEGIN

    {

    set-variable VerbosePreference -value SilentlyContinue

    }

    PROCESS 

    {

    Set-ADServerSettings -ViewEntireForest:$true

    Get-User (Get-LogonUserIdentity)

    }

    }

     

    # Get linked role groups

    function global:Get-LinkedRoleGroupForLogonUser()

    {

    BEGIN

    {

    set-variable VerbosePreference -value SilentlyContinue

    }

    PROCESS 

    {

    Set-ADServerSettings -ViewEntireForest:$true

     

    $userIdentity = (Get-Variable PSSenderInfo).Value.UserInfo.WindowsIdentity

     

    if ($userIdentity -ne $null)

    {

    $allLinkedRoleGroups = Get-RoleGroup -Filter { RoleGroupType -eq "Linked" }

    $sids = [Microsoft.Exchange.Configuration.Authorization.ExchangeAuthorizationPlugin]::GetGroupAccountsSIDs($userIdentity)

     

    #111120965335188

    foreach ($sid in $sids) 

    try 

    $accountName = $sid.Translate([System.Security.Principal.NTAccount]).Value 

    catch 

    continue 

     

    if ($accountName -ne $null) 

    foreach ($roleGroup in $allLinkedRoleGroups) 

    if ([string]::Compare($roleGroup.LinkedGroup,$accountName,$True) -eq 0) 

    $roleGroup 

     

    }

    }

    }

     

    # Get ManagementRoleAssignment for logon user

    function global:Get-ManagementRoleAssignmentForLogonUser ([bool]$HasLinkedRoleGroup)

    {

    BEGIN

    {

    set-variable VerbosePreference -value SilentlyContinue

    }

    PROCESS 

    {

    Set-ADServerSettings -ViewEntireForest:$true

     

    if ($HasLinkedRoleGroup)

    {

    foreach ($roleGroup in Get-LinkedRoleGroupForLogonUser)

    {

    Get-ManagementRoleAssignment -RoleAssignee $roleGroup

    }

    }

    else

    {

    Get-ManagementRoleAssignment -RoleAssignee (Get-LogonUserIdentity)

    }

    }

    }

     

    # Get ManagementRole for logon user

    function global:Get-ManagementRoleForLogonUser ([bool]$HasLinkedRoleGroup)

    {

    BEGIN

    {

    set-variable VerbosePreference -value SilentlyContinue

    }

    PROCESS 

    {

    Set-ADServerSettings -ViewEntireForest:$true

    if ($HasLinkedRoleGroup)

    {

    foreach ($o in Get-ManagementRoleAssignmentForLogonUser($HasLinkedRoleGroup))

    {

    $o.Role | Get-ManagementRole

    }

    }

    else

    {

    foreach ($o in Get-ManagementRoleAssignment -RoleAssignee (Get-LogonUserIdentity))

    {

    $o.Role | Get-ManagementRole

    }

    }

    }

    }

     

    # Get ManagementScope for logon user

    function global:Get-ManagementScopeForLogonUser ([bool]$HasLinkedRoleGroup)

    {

    BEGIN

    {

    set-variable VerbosePreference -value SilentlyContinue

    }

    PROCESS 

    {

    Set-ADServerSettings -ViewEntireForest:$true

     

    $scopes = @{}

    $roles = @{}

     

    if ($HasLinkedRoleGroup)

    {

    $roles = Get-ManagementRoleAssignmentForLogonUser($HasLinkedRoleGroup)

    }

    else

    {

    $roles = Get-ManagementRoleAssignment -RoleAssignee (Get-LogonUserIdentity)

    }

     

    foreach ($o in $roles)

    {

    if ($o.CustomRecipientWriteScope -ne $null -and !$scopes.ContainsKey($o.CustomRecipientWriteScope))

    {

    $scopes.add($o.CustomRecipientWriteScope, $null)

    $o.CustomRecipientWriteScope | Get-ManagementScope -ErrorAction SilentlyContinue

    }

     

    if ($o.CustomConfigWriteScope -ne $null -and !$scopes.ContainsKey($o.CustomConfigWriteScope ))

    {

    $scopes.add($o.CustomConfigWriteScope , $null)

    $o.CustomConfigWriteScope | Get-ManagementScope -ErrorAction SilentlyContinue

    }

    }

    }

    }

     

    # Get Exclusive ManagementScope for logon user

    function global:Get-ExclusiveManagementScopeForLogonUser ()

    {

    BEGIN

    {

    set-variable VerbosePreference -value Continue

    }

    PROCESS 

    {

    Get-ManagementScope -Exclusive:$true

    }

    }

     

    # Get ADServerSettings for logon user

    # The reason to write this wrapper is that we cannot public the Get-ADServerSettings to any user

    # without a role assignment, otherwise it won't pass the check during setting Rbac Scope in task.cs.

    function global:Get-ADServerSettingsForLogonUser ()

    {

    BEGIN

    {

    set-variable VerbosePreference -value SilentlyContinue

    }

    PROCESS 

    {

    Get-ADServerSettings

    }

    }

     

     

    # Set ADServerSettings for logon user

    # The reason to write this wrapper is that we cannot public the Get-ADServerSettings to any user

    # without a role assignment, otherwise it won't pass the check during setting Rbac Scope in task.cs.

    function global:Set-ADServerSettingsForLogonUser ([object]$RunspaceServerSettings)

    {

    BEGIN

    {

    set-variable VerbosePreference -value SilentlyContinue

    }

    PROCESS 

    {

    Set-ADServerSettings -RunspaceServerSettings $RunspaceServerSettings

    }

    }

     

    # Filter out object which NameProperty equals an input SearchText

    function global:Filter-PropertyStringContains ([string]$Property, [string]$SearchText)

    {

    BEGIN

    {

    set-variable VerbosePreference -value Continue

    }

    PROCESS 

    {

    :connectScope do

    {

    $_ | where-object {$_.$Property.ToString().ToUpper().Contains($SearchText.ToUpper())}

    }

    while ($false) #connectScope

    }

    }

     

    # Filter out object wich $Property not contains $SearchText

    function global:Filter-PropertyStringNotContains ([string]$Property, [string]$SearchText)

    {

    BEGIN

    {

    set-variable VerbosePreference -value Continue

    }

    PROCESS 

    {

    :connectScope do

    {

    $_ | where-object {$_.$Property.ToString().ToUpper().Contains($SearchText.ToUpper()) -eq $false}

    }

    while ($false) #connectScope

    }

    }

     

    # Sort the pipeline objects with specified property

    function global:Sort-Objects ([string]$Property)

    {

    BEGIN

    {

    set-variable VerbosePreference -value Continue

    }

    PROCESS 

    {

    :connectScope do

    {

    $_ | Sort-Object -Property $Property

    }

    while ($false) #connectScope

    }

    }

     

    # Equal to

    function global:Filter-PropertyEqualTo ([string]$Property, [object]$Value=$null)

    {

    BEGIN

    {

    set-variable VerbosePreference -value Continue

    }

    PROCESS 

    {

    :connectScope do

    {

    $_ | where-object {$_.$Property -eq $Value}

    }

    while ($false) #connectScope

    }

    }

     

    # Not Equal to

    function global:Filter-PropertyNotEqualTo ([string]$Property, [object]$Value=$null)

    {

    BEGIN

    {

    set-variable VerbosePreference -value Continue

    }

    PROCESS 

    {

    :connectScope do

    {

    $_ | where-object {$_.$Property -ne $Value}

    }

    while ($false) #connectScope

    }

    }

     

    # Equal or Greater Than

    function global:Filter-PropertyEqualOrGreaterThan ([string]$Property, [object]$Value=$null)

    {

    BEGIN

    {

    set-variable VerbosePreference -value Continue

    }

    PROCESS 

    {

    :connectScope do

    {

    $_ | where-object {$_.$Property -ge $Value}

    }

    while ($false) #connectScope

    }

    }

     

    # Filter out recipients without primary smtp address

    function global:Filter-Recipient ()

    {

    BEGIN

    {

    set-variable VerbosePreference -value Continue

    }

    PROCESS 

    {

    :connectScope do

    {

    $_ | where-object {$_.PrimarySmtpAddress.Length -ne 0}

    }

    while ($false) #connectScope

    }

    }

     

    # Resolve a bunch of objects 

    function global:Filter-PropertyInObjects ([string]$ResolveProperty, [string[]]$inputObjects = $null)

    {

    BEGIN

    {

    set-variable VerbosePreference -value Continue

    }

    PROCESS 

    {

    :connectScope do

    {

    if ($inputObjects -eq $null)

    {

    return

    }

    if ($inputObjects -contains $_.$ResolveProperty)

    {

    $_

    }

    }

    while ($false) #connectScope

    }

    }

     

    # Will be removed with Delegation Feature

    function global:Filter-Delegation ()

    {

    BEGIN

    {

    set-variable VerbosePreference -value Continue

    }

    PROCESS 

    {

    :connectScope do

    {

    # All Delegation feature will be cut soon.

    $_ 

    }

    while ($false) #connectScope

    }

    }

     

    # Filter mailboxes which version equal or greater than the specific

    function global:Filter-Mailbox ([object]$Value=$null)

    {

    BEGIN

    {

    set-variable VerbosePreference -value Continue

    }

    PROCESS 

    {

    :connectScope do

    {

    $_ | where-object {$_.ExchangeVersion.ToInt64() -ge $Value}

    }

    while ($false) #connectScope

    }

    }

     

    # Specific Filter for DatabaseMaster Picker to get all Databases or Master of its DatabaseCopies

    function global:Filter-DatabaseMasterServer ()

    {

    BEGIN

    {

    set-variable VerbosePreference -value Continue

    }

    PROCESS 

    {

    :connectScope do

    {

    foreach ($copy in $_.DatabaseCopies)

    {

    $copy.HostServerName | Get-ExchangeServer

    }

     

    }

    while ($false) #connectScope

    }

    }

     

    # Specific Filter for ServersInSameDag Picker to get servers in the same DAG as $dagMemberServer

    function global:Filter-ServersInSameDag ([string]$dagMemberServer)

    {

    BEGIN

    {

    set-variable VerbosePreference -value Continue

    }

    PROCESS 

    {

    :connectScope do

    {

    if ($_.Servers -Contains $dagMemberServer)

    {

    foreach ($server in $_.Servers)

    {

    if ($server -ne $dagMemberServer)

    {

    $server | Get-ExchangeServer

    }

    }

    }

    }

    while ($false) #connectScope

    }

    }

     

    # Get all PublicFolder Installed Exchange Server

    function global:Filter-PublicFolderInstalledExchangeServer ([int]$minVersion = 8, [string]$excludeServer = $null)

    {

    BEGIN

    {

    set-variable VerbosePreference -value Continue

    }

    PROCESS 

    {

    :connectScope do

    {

    if ($_.Server -eq $excludeServer)

    {

    return

    }

    else

    {

    $_.Server | Get-ExchangeServer | where-object {$_.AdminDisplayVersion.Major -ge $minVersion}

    }

    }

    while ($false) #connectScope

    }

    }

     

    # Filter for ExchangeCertificate picker

    function global:Filter-ExchangeCertificate ([object]$isSelfSigned, [object]$hasKeyIdentifier, [object]$privateKeyExportable, [object]$status)

    {

        BEGIN

        {

            set-variable VerbosePreference -value Continue

        }

        PROCESS

        {

            :connectScope do

            {

                if (($status -eq $null -or $_.Status -eq $status) -and ($isSelfSigned -eq $null -or $_.IsSelfSigned -eq $isSelfSigned) -and ($hasKeyIdentifier -eq $null -or [string]::IsNullOrEmpty($_.KeyIdentifier) -ne $hasKeyIdentifier) -and ($privateKeyExportable -eq $null -or $_.PrivateKeyExportable -eq $privateKeyExportable))

                {

                    $_

                }

            }

            while ($false) #connectScope

        }

    }

     

    # A generic ExchangeServer Filter for all ExchangeServer Pickers

    function global:Filter-ExchangeServer ([int]$minVersion = 8, [int]$maxVersion = 2147483647, [string[]]$serverRoles, [switch]$includeLegacyServer, [switch]$backendServerOnly, [string[]]$excludedServers, [Microsoft.Exchange.Data.ExchangeBuild]$exactVersion)

    {

    BEGIN

    {

    set-variable VerbosePreference -value Continue

    }

    PROCESS 

    {

    :connectScope do

    {

    if ($excludedServers -contains $_.Identity)

    {

    return

    }

    if ($includeLegacyServer -and $_.AdminDisplayVersion.Major -lt 8)

    {

    # only return backend server

    if ($backenServerOnly -and ($_.ExchangeLegacyServerRole -ne 0))

    {

    return

    }

    $_

    }

    else

    {

    $targetServerRole = $false

    foreach($role in $serverRoles)

    {

    if ($_.ServerRole -like '*'+$role+'*')

    {

    $targetServerRole = $true

    }

    }

    if ($targetServerRole -and $_.AdminDisplayVersion.Major -ge $minVersion -and $_.AdminDisplayVersion.Major -le $maxVersion)

    {

    if ($exactVersion -ne $null)

    {

    if (($_.AdminDisplayVersion.Major -eq $exactVersion.Major) -and ($_.AdminDisplayVersion.Minor -eq $exactVersion.Minor) -and ($_.AdminDisplayVersion.Build -eq $exactVersion.Build))

    {

    $_

    }

    }

    else

    {

    $_

    }

    }

    }

    }

    while ($false) #connectScope

    }

    }

    # SIG # Begin signature block

    # MIIbHwYJKoZIhvcNAQcCoIIbEDCCGwwCAQExCzAJBgUrDgMCGgUAMGkGCisGAQQB

    # gjcCAQSgWzBZMDQGCisGAQQBgjcCAR4wJgIDAQAABBAfzDtgWUsITrck0sYpfvNR

    # AgEAAgEAAgEAAgEAAgEAMCEwCQYFKw4DAhoFAAQU5h7ut8I5/vHcl9DX5Te57Xfr

    # fWSgghXyMIIEoDCCA4igAwIBAgIKYRr16gAAAAAAajANBgkqhkiG9w0BAQUFADB5

    # MQswCQYDVQQGEwJVUzETMBEGA1UECBMKV2FzaGluZ3RvbjEQMA4GA1UEBxMHUmVk

    # bW9uZDEeMBwGA1UEChMVTWljcm9zb2Z0IENvcnBvcmF0aW9uMSMwIQYDVQQDExpN

    # aWNyb3NvZnQgQ29kZSBTaWduaW5nIFBDQTAeFw0xMTExMDEyMjM5MTdaFw0xMzAy

    # MDEyMjQ5MTdaMIGDMQswCQYDVQQGEwJVUzETMBEGA1UECBMKV2FzaGluZ3RvbjEQ

    # MA4GA1UEBxMHUmVkbW9uZDEeMBwGA1UEChMVTWljcm9zb2Z0IENvcnBvcmF0aW9u

    # MQ0wCwYDVQQLEwRNT1BSMR4wHAYDVQQDExVNaWNyb3NvZnQgQ29ycG9yYXRpb24w

    # ggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDDqR/PfCN/MR4GJYnddXm5

    # z5NLYZK2lfLvqiWdd/NLWm1JkMzgMbimAjeHdK/yrKBglLjHTiX+h9hY0iBOLfE6

    # ZS6SW6Zd5pV14DTlUCGcfTmXto5EI2YWpmUg4Dbrivqd4stgAfwqZMiHRRTxHsrN

    # KKy65VdZJtzsxUpsmuYDGikyPwCeg6wlDYTM3W+2arst94Q6bWYx6DZw/4SSkPdA

    # dp6ILkfWKxH3j+ASZSu8X+8V/PfsAWi3RQzuwASwDre9eGuujeRQ8TXingHS4etb

    # cYJhISDz1MneHLgCRWVJvn61N4anzexa37h2IPwRE1H8+ipQqrQe0DqAvmPK3IFH

    # AgMBAAGjggEdMIIBGTATBgNVHSUEDDAKBggrBgEFBQcDAzAdBgNVHQ4EFgQUAAOm

    # 5aLEcaKCw492zSwNEuKdSigwDgYDVR0PAQH/BAQDAgeAMB8GA1UdIwQYMBaAFFdF

    # dBxdsPbIQwXgjFQtjzKn/kiWMFYGA1UdHwRPME0wS6BJoEeGRWh0dHA6Ly9jcmwu

    # bWljcm9zb2Z0LmNvbS9wa2kvY3JsL3Byb2R1Y3RzL01pY0NvZFNpZ1BDQV8wOC0z

    # MS0yMDEwLmNybDBaBggrBgEFBQcBAQROMEwwSgYIKwYBBQUHMAKGPmh0dHA6Ly93

    # d3cubWljcm9zb2Z0LmNvbS9wa2kvY2VydHMvTWljQ29kU2lnUENBXzA4LTMxLTIw

    # MTAuY3J0MA0GCSqGSIb3DQEBBQUAA4IBAQCQ9/h5kmnIj2uKYO58wa4+gThS9LrP

    # mYzwLT0T9K72YfB1OE5Zxj8HQ/kHfMdT5JFi1qh2FHWUhlmyuhDCf2wVPxkVww4v

    # fjnDz/5UJ1iUNWEHeW1RV7AS4epjcooWZuufOSozBDWLg94KXjG8nx3uNUUNXceX

    # 3yrgnX86SfvjSEUy3zZtCW52VVWsNMV5XW4C1cyXifOoaH0U6ml7C1V9AozETTC8

    # Yvd7peygkvAOKg6vV5spSM22IaXqHe/cCfWrYtYN7DVfa5nUsfB3Uvl36T9smFbA

    # XDahTl4Q9Ix6EZcgIDEIeW5yFl8cMFeby3yiVfVwbHjsoUMgruywNYsYMIIEujCC

    # A6KgAwIBAgIKYQUTNgAAAAAAGjANBgkqhkiG9w0BAQUFADB3MQswCQYDVQQGEwJV

    # UzETMBEGA1UECBMKV2FzaGluZ3RvbjEQMA4GA1UEBxMHUmVkbW9uZDEeMBwGA1UE

    # ChMVTWljcm9zb2Z0IENvcnBvcmF0aW9uMSEwHwYDVQQDExhNaWNyb3NvZnQgVGlt

    # ZS1TdGFtcCBQQ0EwHhcNMTEwNzI1MjA0MjE3WhcNMTIxMDI1MjA0MjE3WjCBszEL

    # MAkGA1UEBhMCVVMxEzARBgNVBAgTCldhc2hpbmd0b24xEDAOBgNVBAcTB1JlZG1v

    # bmQxHjAcBgNVBAoTFU1pY3Jvc29mdCBDb3Jwb3JhdGlvbjENMAsGA1UECxMETU9Q

    # UjEnMCUGA1UECxMebkNpcGhlciBEU0UgRVNOOjE1OUMtQTNGNy0yNTcwMSUwIwYD

    # VQQDExxNaWNyb3NvZnQgVGltZS1TdGFtcCBTZXJ2aWNlMIIBIjANBgkqhkiG9w0B

    # AQEFAAOCAQ8AMIIBCgKCAQEAnDSYGckJKWOZAhZ1qIhXfaG7qUES/GSRpdYFeL93

    # 3OzmrrhQTsDjGr3tt/34IIpxOapyknKfignlE++RQe1hJWtRre6oQ7VhQiyd8h2x

    # 0vy39Xujc3YTsyuj25RhgFWhD23d2OwW/4V/lp6IfwAujnokumidj8bK9JB5euGb

    # 7wZdfvguw2oVnDwUL+fVlMgiG1HLqVWGIbda80ESOZ/wValOqiUrY/uRcjwPfMCW

    # ctzBo8EIyt7FybXACl+lnAuqcgpdCkB9LpjQq7KIj4aA6H3RvlVr4FgsyDY/+eYR

    # w/BDBYV4AxflLKcpfNPilRcAbNvcrTwZOgLgfWLUzvYdPQIDAQABo4IBCTCCAQUw

    # HQYDVR0OBBYEFPaDiyCHEe6Dy9vehaLSaIY3YXSQMB8GA1UdIwQYMBaAFCM0+NlS

    # RnAK7UD7dvuzK7DDNbMPMFQGA1UdHwRNMEswSaBHoEWGQ2h0dHA6Ly9jcmwubWlj

    # cm9zb2Z0LmNvbS9wa2kvY3JsL3Byb2R1Y3RzL01pY3Jvc29mdFRpbWVTdGFtcFBD

    # QS5jcmwwWAYIKwYBBQUHAQEETDBKMEgGCCsGAQUFBzAChjxodHRwOi8vd3d3Lm1p

    # Y3Jvc29mdC5jb20vcGtpL2NlcnRzL01pY3Jvc29mdFRpbWVTdGFtcFBDQS5jcnQw

    # EwYDVR0lBAwwCgYIKwYBBQUHAwgwDQYJKoZIhvcNAQEFBQADggEBAGL0BQ1P5xtr

    # gudSDN95jKhVgTOX06TKyf6vSNt72m96KE/H0LeJ2NGmmcyRVgA7OOi3Mi/u+c9r

    # 2Zje1gL1QlhSa47aQNwWoLPUvyYVy0hCzNP9tPrkRIlmD0IOXvcEnyNIW7SJQcTa

    # bPg29D/CHhXfmEwAxLLs3l8BAUOcuELWIsiTmp7JpRhn/EeEHpFdm/J297GOch2A

    # djw2EUbKfjpI86/jSfYXM427AGOCnFejVqfDbpCjPpW3/GTRXRjCCwFQY6f889GA

    # noTjMjTdV5VAo21+2usuWgi0EAZeMskJ6TKCcRan+savZpiJ+dmetV8QI6N3gPJN

    # 1igAclCFvOUwggYHMIID76ADAgECAgphFmg0AAAAAAAcMA0GCSqGSIb3DQEBBQUA

    # MF8xEzARBgoJkiaJk/IsZAEZFgNjb20xGTAXBgoJkiaJk/IsZAEZFgltaWNyb3Nv

    # ZnQxLTArBgNVBAMTJE1pY3Jvc29mdCBSb290IENlcnRpZmljYXRlIEF1dGhvcml0

    # eTAeFw0wNzA0MDMxMjUzMDlaFw0yMTA0MDMxMzAzMDlaMHcxCzAJBgNVBAYTAlVT

    # MRMwEQYDVQQIEwpXYXNoaW5ndG9uMRAwDgYDVQQHEwdSZWRtb25kMR4wHAYDVQQK

    # ExVNaWNyb3NvZnQgQ29ycG9yYXRpb24xITAfBgNVBAMTGE1pY3Jvc29mdCBUaW1l

    # LVN0YW1wIFBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAJ+hbLHf

    # 20iSKnxrLhnhveLjxZlRI1Ctzt0YTiQP7tGn0UytdDAgEesH1VSVFUmUG0KSrphc

    # MCbaAGvoe73siQcP9w4EmPCJzB/LMySHnfL0Zxws/HvniB3q506jocEjU8qN+kXP

    # CdBer9CwQgSi+aZsk2fXKNxGU7CG0OUoRi4nrIZPVVIM5AMs+2qQkDBuh/NZMJ36

    # ftaXs+ghl3740hPzCLdTbVK0RZCfSABKR2YRJylmqJfk0waBSqL5hKcRRxQJgp+E

    # 7VV4/gGaHVAIhQAQMEbtt94jRrvELVSfrx54QTF3zJvfO4OToWECtR0Nsfz3m7IB

    # ziJLVP/5BcPCIAsCAwEAAaOCAaswggGnMA8GA1UdEwEB/wQFMAMBAf8wHQYDVR0O

    # BBYEFCM0+NlSRnAK7UD7dvuzK7DDNbMPMAsGA1UdDwQEAwIBhjAQBgkrBgEEAYI3

    # FQEEAwIBADCBmAYDVR0jBIGQMIGNgBQOrIJgQFYnl+UlE/wq4QpTlVnkpKFjpGEw

    # XzETMBEGCgmSJomT8ixkARkWA2NvbTEZMBcGCgmSJomT8ixkARkWCW1pY3Jvc29m

    # dDEtMCsGA1UEAxMkTWljcm9zb2Z0IFJvb3QgQ2VydGlmaWNhdGUgQXV0aG9yaXR5

    # ghB5rRahSqClrUxzWPQHEy5lMFAGA1UdHwRJMEcwRaBDoEGGP2h0dHA6Ly9jcmwu

    # bWljcm9zb2Z0LmNvbS9wa2kvY3JsL3Byb2R1Y3RzL21pY3Jvc29mdHJvb3RjZXJ0

    # LmNybDBUBggrBgEFBQcBAQRIMEYwRAYIKwYBBQUHMAKGOGh0dHA6Ly93d3cubWlj

    # cm9zb2Z0LmNvbS9wa2kvY2VydHMvTWljcm9zb2Z0Um9vdENlcnQuY3J0MBMGA1Ud

    # JQQMMAoGCCsGAQUFBwMIMA0GCSqGSIb3DQEBBQUAA4ICAQAQl4rDXANENt3ptK13

    # 2855UU0BsS50cVttDBOrzr57j7gu1BKijG1iuFcCy04gE1CZ3XpA4le7r1iaHOEd

    # AYasu3jyi9DsOwHu4r6PCgXIjUji8FMV3U+rkuTnjWrVgMHmlPIGL4UD6ZEqJCJw

    # +/b85HiZLg33B+JwvBhOnY5rCnKVuKE5nGctxVEO6mJcPxaYiyA/4gcaMvnMMUp2

    # MT0rcgvI6nA9/4UKE9/CCmGO8Ne4F+tOi3/FNSteo7/rvH0LQnvUU3Ih7jDKu3hl

    # XFsBFwoUDtLaFJj1PLlmWLMtL+f5hYbMUVbonXCUbKw5TNT2eb+qGHpiKe+imyk0

    # BncaYsk9Hm0fgvALxyy7z0Oz5fnsfbXjpKh0NbhOxXEjEiZ2CzxSjHFaRkMUvLOz

    # sE1nyJ9C/4B5IYCeFTBm6EISXhrIniIh0EPpK+m79EjMLNTYMoBMJipIJF9a6lbv

    # pt6Znco6b72BJ3QGEe52Ib+bgsEnVLaxaj2JoXZhtG6hE6a/qkfwEm/9ijJssv7f

    # UciMI8lmvZ0dhxJkAj0tr1mPuOQh5bWwymO0eFQF1EEuUKyUsKV4q7OglnUa2ZKH

    # E3UiLzKoCG6gW4wlv6DvhMoh1useT8ma7kng9wFlb4kLfchpyOZu6qeXzjEp/w7F

    # W1zYTRuh2Povnj8uVRZryROj/TCCBoEwggRpoAMCAQICCmEVCCcAAAAAAAwwDQYJ

    # KoZIhvcNAQEFBQAwXzETMBEGCgmSJomT8ixkARkWA2NvbTEZMBcGCgmSJomT8ixk

    # ARkWCW1pY3Jvc29mdDEtMCsGA1UEAxMkTWljcm9zb2Z0IFJvb3QgQ2VydGlmaWNh

    # dGUgQXV0aG9yaXR5MB4XDTA2MDEyNTIzMjIzMloXDTE3MDEyNTIzMzIzMloweTEL

    # MAkGA1UEBhMCVVMxEzARBgNVBAgTCldhc2hpbmd0b24xEDAOBgNVBAcTB1JlZG1v

    # bmQxHjAcBgNVBAoTFU1pY3Jvc29mdCBDb3Jwb3JhdGlvbjEjMCEGA1UEAxMaTWlj

    # cm9zb2Z0IENvZGUgU2lnbmluZyBQQ0EwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAw

    # ggEKAoIBAQCfjd+FN4yxBlZmNk7UCus2I5Eer6uNWOnEz8GfOgokxMTEXrDuFRTF

    # +j6ZM2sZaXL0fAVf5ZklRNc1GYqQ3CiOkAzv1ZBhrd7cGHAtg8lvr4Us+N25uTD9

    # cXgcg/3IqbmCZw16uMEJwrwWl1c/HJjTadcwkJCQjTAf2CbUnnuI2eIJ7ZdJResE

    # UoF1e7i1IrguVrvXz6lOPAqDoqg6xa22AQ5qzyK0Ix9s1Sfnt37BtNUyrXklHEKG

    # 4p2F9FfaG1kvLSaSKcWz14WjnmBalOZ7nHtegjRLbf/U7ifQotzRkAzOfQ4VfIis

    # NMfAbJiESslEeWgo3yKDDbiKLEhh4v4RAgMBAAGjggIjMIICHzAQBgkrBgEEAYI3

    # FQEEAwIBADAdBgNVHQ4EFgQUV0V0HF2w9shDBeCMVC2PMqf+SJYwCwYDVR0PBAQD

    # AgHGMA8GA1UdEwEB/wQFMAMBAf8wgZgGA1UdIwSBkDCBjYAUDqyCYEBWJ5flJRP8

    # KuEKU5VZ5KShY6RhMF8xEzARBgoJkiaJk/IsZAEZFgNjb20xGTAXBgoJkiaJk/Is

    # ZAEZFgltaWNyb3NvZnQxLTArBgNVBAMTJE1pY3Jvc29mdCBSb290IENlcnRpZmlj

    # YXRlIEF1dGhvcml0eYIQea0WoUqgpa1Mc1j0BxMuZTBQBgNVHR8ESTBHMEWgQ6BB

    # hj9odHRwOi8vY3JsLm1pY3Jvc29mdC5jb20vcGtpL2NybC9wcm9kdWN0cy9taWNy

    # b3NvZnRyb290Y2VydC5jcmwwVAYIKwYBBQUHAQEESDBGMEQGCCsGAQUFBzAChjho

    # dHRwOi8vd3d3Lm1pY3Jvc29mdC5jb20vcGtpL2NlcnRzL01pY3Jvc29mdFJvb3RD

    # ZXJ0LmNydDB2BgNVHSAEbzBtMGsGCSsGAQQBgjcVLzBeMFwGCCsGAQUFBwICMFAe

    # TgBDAG8AcAB5AHIAaQBnAGgAdAAgAKkAIAAyADAAMAA2ACAATQBpAGMAcgBvAHMA

    # bwBmAHQAIABDAG8AcgBwAG8AcgBhAHQAaQBvAG4ALjATBgNVHSUEDDAKBggrBgEF

    # BQcDAzANBgkqhkiG9w0BAQUFAAOCAgEAMLywIKRioKfvOSZhPdysxpnQhsQu9YMy

    # ZV4iPpvWhvjotp/Ki9Y7dQuhkT5M3WR0jEnyiIwYZ2z+FWZGuDpGQpfIkTfUJLHn

    # rNPqQRSDd9PJTwVfoxRSv5akLz5WWxB1zlPDzgVUabRlySSlD+EluBq5TeUCuVAe

    # T7OYDB2VAu4iWa0iywV0CwRFewRZ4NgPs+tM+GDdwnie0bqfa/fz7n5EEUDSvbqb

    # SxYIbqS+VeSmOBKjSPQcVXqKINF9/pHblI8vwntrpmSFT6PlLDQpXQu/9cc4L8Qg

    # xFYx9mnOhfgKkezQ1q66OAUM625PTJwDKaqi/BigKQwNXFxWI1faHJYNyCY2wUTL

    # 5eHmb4nnj+mYtXPTeOPtowE8dOVevGz2IYlnBeyXnbWx/a+m6XKlwzThL5/59Go5

    # 4i0Eglv80JyufJ0R+ea1Uxl0ujlKOet9QrNKOzc9wkp7J5jn4k6bG0pUOGojN75q

    # t0ju6kINSSSRjrcELpdv5OdFu49N/WDZ11nC2IDWYDR7t6GTIP6BuKqlXAnpig2+

    # KE1+1+gP7WV40TFfuWbb30LnC8wCB43f/yAGo0VltLMyjS6R4k20qcn6vGsEDrKf

    # 6p/epMkKlvSN99iYqPCFAghZpCCmLAsa8lIG7WnlZBgb4KOr3sp8FGFDuGX1NqNV

    # EytnLE0bMEwxggSXMIIEkwIBATCBhzB5MQswCQYDVQQGEwJVUzETMBEGA1UECBMK

    # V2FzaGluZ3RvbjEQMA4GA1UEBxMHUmVkbW9uZDEeMBwGA1UEChMVTWljcm9zb2Z0

    # IENvcnBvcmF0aW9uMSMwIQYDVQQDExpNaWNyb3NvZnQgQ29kZSBTaWduaW5nIFBD

    # QQIKYRr16gAAAAAAajAJBgUrDgMCGgUAoIHEMBkGCSqGSIb3DQEJAzEMBgorBgEE

    # AYI3AgEEMBwGCisGAQQBgjcCAQsxDjAMBgorBgEEAYI3AgEVMCMGCSqGSIb3DQEJ

    # BDEWBBSKZlgt7Zb1hp2ZyRqdEOZLa5xVezBkBgorBgEEAYI3AgEMMVYwVKAsgCoA

    # QwBvAG4AcwBvAGwAZQBJAG4AaQB0AGkAYQBsAGkAegBlAC4AcABzADGhJIAiaHR0

    # cDovL3d3dy5taWNyb3NvZnQuY29tL2V4Y2hhbmdlIDANBgkqhkiG9w0BAQEFAASC

    # AQBwEO05BJ8sT52gTJYBnPGRLWVyuBKFbj/F103Ddkk2sX1dmGVDv/7Sbi5YcFCD

    # RQp6uOYn6y0lcZ4nplve4d92wAUGlV2YpJr7AX5+afiksTiTWjZ/URiAUqLl+y0W

    # 4ZWj5mJpsbdJmcNMYGL2iRqyOcKw5lqP/tMJewbpuGlH6Ft0dFu0WA5My80KeIVK

    # NG0PLKvnfhBdqwaQWsU2/rUpaUQOBkPGXd8E1xTOKpo/rk6NLczGiQ7PEya8tY7W

    # WCUm7vqx/6ZpgzwLo0B7dqKpWY9wo+eVJBB/pED2O04CNhNph8nMB9HogUcXsiac

    # xrSTMVY3+lk98zA46FuDusLgoYICHTCCAhkGCSqGSIb3DQEJBjGCAgowggIGAgEB

    # MIGFMHcxCzAJBgNVBAYTAlVTMRMwEQYDVQQIEwpXYXNoaW5ndG9uMRAwDgYDVQQH

    # EwdSZWRtb25kMR4wHAYDVQQKExVNaWNyb3NvZnQgQ29ycG9yYXRpb24xITAfBgNV

    # BAMTGE1pY3Jvc29mdCBUaW1lLVN0YW1wIFBDQQIKYQUTNgAAAAAAGjAHBgUrDgMC

    # GqBdMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTEx

    # MTEyMzIxMDYyMFowIwYJKoZIhvcNAQkEMRYEFN32wne6QPaX+ZTTjUt/phDpGLrw

    # MA0GCSqGSIb3DQEBBQUABIIBABePASsY+Itm6Ifq7ypbHALI0uxWFWqedheRgjSE

    # KNQzZd5gWpT2jHZ4tumKW4yTELrSklwsBMqv3icBVclp3i8sDY56xRSRNQtnEyKt

    # ct5nkn2Tyb43eMG3OAjIqNjXHbRosFAS8WPu/5tJBo2E7rYdzK1ERmFlQC82sx3t

    # zw9AUOd5/9OfnGALY16nPVdWwarcNBYt0nYHTifgUGDXUTqQynypsS7gJYcnbQQR

    # AFN91G6CHwfmAs6AEGbbLiKg1agvKC+W3NP1JPNmmj1LMKdPz6uetNeN11LRjESk

    # haMNyoBY+OwSq+UF+yakqZx8HWvGj1kr2LUIU7Al5+9Qp8w=

    # SIG # End signature block

     

    lunes, 12 de diciembre de 2011 17:59
  • Thanks for this solution. I won't be able to test though.  I had to move forward with SP1+RU6 as we move from the lab to production.  I ran out of time for testing SP2.  Depending on how the SP1 implementation goes, and how the project timelines work out with our pilot, I may be able to test this in a couple of months if we decide to upgrade.  For now, I am going to sit back and wait for these type of inevitable issues to be worked out. Thanks again.


    Clint Weldon
    lunes, 12 de diciembre de 2011 19:04
  • I've used this script in the test environment. Instead of the original error it now shows (translated from German):

    Initialization error

    Error while retrieving user information for "INTRANET\Administrator".

    The operation failed because "INTRANET\Administrator" could not be found.

    "INTRANET\Administrator" is of course the main administrative account found in AD  <rootdomain>\users that was used to install the whole thing. Thoughts ?

    martes, 13 de diciembre de 2011 12:10
  • SP2 EMC connected to SP1 server?

    Can you force it to connect SP2 server.

    Get-LinkedRoleGroupForLogonUser not present on SP1 as far as i know.


    MCSE:M 2003, MCITP:EA, SA, EMA, EMA:2010
    miércoles, 14 de diciembre de 2011 8:46

  • Hello Gyrodog,

    There are known issues with the EMC loading after installing Exchange 2010 SP2, Product team is already aware of this issue and working on getting a permanent fix .The workaround for this is to replace the script as provided in the previous response.

    You can try to change the script when you want to test and update us with the status.


    Thanks

    Venkat

     

    miércoles, 14 de diciembre de 2011 12:10
  • I restarted the server and it fixed the issue for me.
    Did you gave a try? 
    Gulab | MCITP: Exchange 2010-2007 | Lync Server 2010 | Windows Server 2008 | Skype: Exchange.Ranger | Blog: www.ExchangeRanger.Blogspot.com
    miércoles, 14 de diciembre de 2011 12:24
  • Hi everyone,

    i am having the exact same issue launching the EMC.
    Without the script above i get this error:

    Initialization failed

    The following error occured when retrieving user information for 'TEST\Administrator':

    Unexpected error [0x1BECB030] While executing command 'Get-Linkedrolegroupforlogonuser'.

    When replace the script by the one posted above i get this error:

    Initialization error

    Error while retrieving user information for "TEST\Administrator".

    The operation failed because "TEST\Administrator" could not be found.

     

    Anyone found a solution, IISreset did nothing, and rebooting the server did not help also. I have installed all exchange updates.

    Thanks

     

    jueves, 15 de diciembre de 2011 12:59
  • I'm having the same issue, rebooting server did not work, the script did not work, the unexpected error I get is 0x170DB030 the command shell works and the ECP web site works but not the EMC

     

    viernes, 16 de diciembre de 2011 21:07
  • hi everyone

    i received this file from microsoft

    my guest, use the file Diff and copy only the difference to your original .ps1 

    or contact microsoft this issue is now  listed by microsoft support

    Yan

     

     

     

    lunes, 19 de diciembre de 2011 16:16
  • HI..

    I am also having the same issue, Please advice ASAP


    Best Regards, SA
    lunes, 19 de diciembre de 2011 18:26
  • In the same boat as the rest of you, SP2, update the ConsoleInitialize.ps1 script as indicated now get an error:

     

    The operation couldn't be performed because 'CORP\Administrator' couldn't be found.

     

    This is putting me in a very bad stop as the plan was to migrate email off of an SBS to a new Exchange 2010 over this last weekend.  ANY help would be extremely appreciated!

    lunes, 19 de diciembre de 2011 20:26
  • Is there an updated status on this?
    martes, 20 de diciembre de 2011 14:24
  • :( Any word on this?  It's hard to believe that there are not other posts  on this, I can't use the EMC at all.  Anything from Microsoft.  Should I open a ticket with MS?
    miércoles, 21 de diciembre de 2011 18:00
  • Hi everyone

    I also get the same issue with different error code. I upgraded the SP1 to SP2 and also install New Exchange 2010 with SP2 but problem is same in both environments.

    Without the script i get this error:

    Initialization failed

    The following error occured when retrieving user information for 'DOMAIN\Administrator':

    Unexpected error [0xA6BB030] While executing command 'Get-LinkedRoleGroupForLogonUser'.

    After changing the script get this error:

    Initialization error

    Error while retrieving user information for "DOMAIN\Administrator".

    The operation failed because "DOMAIN\Administrator" could not be found.

    Please help

     

    jueves, 22 de diciembre de 2011 8:16
  • Any word on this?

    lunes, 26 de diciembre de 2011 19:15
  • I'm suffering from this same problem on numerous test systems. Upgraded one server from RTM to SP2 that included CAS, HUB, MBX, and UM roles, problem arose immediately. Rebooted, tried replacing the PowerShell script as described in this thread, rebooted, no luck. Installed 4 new servers, each with one role (CAS, HUB, MBX, and UM). All in the same AD domain but each fresh installs direct to SP2, same results. Rebooted the entire infrastructure including the domain controller, no luck. Tried a new AD infrastructure and clean install of SP2, same issue. The only server that hasn't been impacted by this is a 2010 EDGE server that I upgraded from RTM to SP2. Ironically, this is having a major impact on the project I'm doing for Microsoft, creating security guides for Exchange 2007 & 2010 with PowerShell-based tools for applying the guidance and scanning for compliance.
    Kurt Dillard http://www.kurtdillard.com
    martes, 27 de diciembre de 2011 15:34
  • It would be great  if you could get a sollution. I dont understand what went wrong and why. Lesley Shand.I have sent group emails out before to the two groups. One group T keep adding to , but the other group I heve neither added to nor subtracted from.

     Now since December 2011, I keep getting the message when I attempt to send a group email,An internal support function returned an error.Lesley Shand

    lunes, 02 de enero de 2012 2:35
  • Even I get the same error. This completely is a new AD & direct install of Exchange 2010 SP2, which means no tweaks that I can think of in this environment.  When I use the script suggested, I get the same behaviour as mentioned by "Hammad Massood" above.

    How soon can this bug be fixed?

     

    lunes, 02 de enero de 2012 7:17
  • Well, I got this working in my environment, and it was pretty easy, I'm concerned about the MSFT people that are monitoring this.  I don't mean to be mean, but it's increasable to me that there was not a post to fix this, or at least some direction to fix this, on THIS forum.

     In my case, not sure if it was the same with the rest of you, my environment is made up of VM’s.  Everything, AD and Exchange server.  I made a “Master” image, patched and configured it then exported it.  I then imported the image into a new VM, renamed etc. activated windows and continued to configure the machine.  It all worked well until the Exchange install.  My mistake was that I FORGOT to sysprep my “Master” image.  So the new VM’s I created from it all had the same SID.

     This article describes talks about the issue and the steps to correctly create your master image: http://www.rayheffer.com/619/cloning-windows-server-2008-r2-use-sysprep-no-more-newsid/

    I hope this helps someone as it was a real pain in the back side. 

     

    lunes, 02 de enero de 2012 21:12
  • You are right Medstar. It definitely was a SID issue. I had a similar setup as yours.  I had even sysprep the "Master" image. But the only thing I missed was.. Tick the ‘Generalize’ option.  I rebuild the Master image and sysprep again. Exchange console works fine now. Thank you.

    miércoles, 04 de enero de 2012 9:48
  • Hello,

    For information i confirm that it's a SID issue, and not a bug. You have to keep in mind to start a sysprep with generalize option in cas of a VM clone.

    Best regards,

    J.ND

    • Propuesto como respuesta J.ND miércoles, 11 de enero de 2012 14:04
    miércoles, 11 de enero de 2012 14:02
  • Hello Team,

    Does this fix if we upgrade it to SP2 RU1? I could not find in the description of RU1.


    Kottees : My Blog : Please mark it as an answer if it really helps you.

    sábado, 25 de febrero de 2012 4:06
  • Well, I got this working in my environment, and it was pretty easy, I'm concerned about the MSFT people that are monitoring this.  I don't mean to be mean, but it's increasable to me that there was not a post to fix this, or at least some direction to fix this, on THIS forum.

     In my case, not sure if it was the same with the rest of you, my environment is made up of VM’s.  Everything, AD and Exchange server.  I made a “Master” image, patched and configured it then exported it.  I then imported the image into a new VM, renamed etc. activated windows and continued to configure the machine.  It all worked well until the Exchange install.  My mistake was that I FORGOT to sysprep my “Master” image.  So the new VM’s I created from it all had the same SID.

     This article describes talks about the issue and the steps to correctly create your master image: http://www.rayheffer.com/619/cloning-windows-server-2008-r2-use-sysprep-no-more-newsid/

    I hope this helps someone as it was a real pain in the back side. 

    Thanks. It solved my issue.

    domingo, 26 de febrero de 2012 18:32
  • Sysprep works for my lab! EMC Works  as fine!

    Marcelo Lagden

    • Propuesto como respuesta JimBobUK jueves, 22 de marzo de 2012 13:03
    • Votado como útil JimBobUK jueves, 22 de marzo de 2012 13:30
    martes, 13 de marzo de 2012 2:19
  • Hi

    I had the same issue after installing SP2 on 2010 CAS. I tried changing the customize.ps1 file and changing execution policy with no luck.
    I took a break and it dawned on me I have had this issue before but a different error

    The resolution:

    1. Revert customize.ps1 back to originl (after SP2 install)

    2. In ADUC I duplicated the admin I was using assigned a new user and logged in

    VOILA! it works. EMC is working as it should

    3. Backed up the admin profile which EMC didnt work for

    4. Removed admin profile via advanced settings

    5. Logged on as affecd admin

    VOILA again! the admin EMC didnt work for is now working

    I backed up the user profile as I was unsure if the admin had any data within their profile they wanted to keep. If they dont I will delete their profile (its only 50mb so not taking up any storage on OS drive)

    I hope this helps to resolve th same issue for anyone out there :)

    • Propuesto como respuesta JimBobUK jueves, 22 de marzo de 2012 13:04
    jueves, 22 de marzo de 2012 13:03
  • Did as jimbobuk suggested and it works

    Hany George | Consultant | IDC S.p.A | MCITP: Lync Server | MCITP: Exchange 2010 | MCTS: OCS | Blog: http://dusk1911.wordpress.com/ | If this post has been useful please click the green arrow to the left or click Propose as answer

    domingo, 25 de marzo de 2012 10:10
  • Did as jimbobuk suggested and it works

    Hany George | Consultant | IDC S.p.A | MCITP: Lync Server | MCITP: Exchange 2010 | MCTS: OCS | Blog: http://dusk1911.wordpress.com/ | If this post has been useful please click the green arrow to the left or click Propose as answer


    Glad it helped, much easier than changing scripts etc :)
    domingo, 01 de abril de 2012 11:51
  • For me EMC was working fine but suddenly its not working. The following error message is coming

    "Failed to find the well-known Exchange Group in Active Directory. It was running the command "Get-LinkedRoleGroupForLogonUser"

    can u please help me to sort this out.


    PK Bhalotia

    viernes, 13 de abril de 2012 13:07
  • For me EMC was working fine but suddenly its not working. The following error message is coming

    "Failed to find the well-known Exchange Group in Active Directory. It was running the command "Get-LinkedRoleGroupForLogonUser"

    can u please help me to sort this out.


    PK Bhalotia

    PK, See my fix above. This has worked for me on many occasions. It has also worked for Hany George on this thread

    Let us know how you get on

    viernes, 13 de abril de 2012 13:13
  • So basically this is a profile issue.  All I did was create a new admin user account, login with that, and the EMC worked.  So there has to be something cached in the user profile of that old admin account. 

    lunes, 30 de abril de 2012 21:20
  • So basically this is a profile issue.  All I did was create a new admin user account, login with that, and the EMC worked.  So there has to be something cached in the user profile of that old admin account. 


    Hence my resolution, creating a new user with the same permissions as the current user :)
    • Editado JimBobUK martes, 01 de mayo de 2012 8:16
    martes, 01 de mayo de 2012 8:16
  • Hello, is there a fix for that issue?

    Thanks

    lunes, 21 de mayo de 2012 9:39
  • Hello, is there a fix for that issue?

    Thanks

    Thomas

    See my post above

    lunes, 21 de mayo de 2012 10:08
  • There's no other way?

    lunes, 21 de mayo de 2012 11:01
  • There's no other way?


    AFAIK there is no other way but as a quick test / resolution it works
    lunes, 21 de mayo de 2012 11:14
  • Hello

    There is the rollup 2 which should solve this issue. But it is not work in my environment.

    Thx

    lunes, 21 de mayo de 2012 12:07
  • Hello

    There is the rollup 2 which should solve this issue. But it is not work in my environment.

    Thx

    Should but does it?

    This is more of a profile issue or is it?

    lunes, 21 de mayo de 2012 13:12
  • I think so too.

    It would be helpful to find the profile issue without deleting it.

    Thx

    lunes, 21 de mayo de 2012 14:41
  •  

    Hi Gyrodog,

    This issue can be resolve with Update Rollup 2 for Exchange Server 2010 Service Pack 2. Bellow you can find the MSKB which describe the issue and have the resolution.

      ü  A user in a trusted account forest cannot use the EMC to manage an Exchange Server 2010 SP2 server

     ü  2661854 (http://support.microsoft.com/kb/2661854/ ) Description of Update Rollup 2 for Exchange Server 2010 Service Pack 2

    Regards

    Catastrophic Failure "JV"


    Catastrophic failure is a sudden and total failure of some system from which recovery is impossible...Thats me....!

    miércoles, 30 de mayo de 2012 10:29
  • Hi,

    does this problem occur on the exchange 2010 server or on the client connecting to the exchange 2010 server via emc?

    Thomas

    miércoles, 30 de mayo de 2012 10:31
  • I was getting the Get-LinkedRoleGroupForLogonUser error when trying to expand Microsoft Exchange On-Premises.  I renamed ConsoleInitialize.PS1 and then created a new one using Yan Gauthier's  as a fix.  Initialization now fails saying "The following error occurred when retrieving user information for smc\administrator.  The operation could not be performed because SMC\administrator couldn't be found. "

    I'm not sure where it's looking but I am logged in as that user when trying to open the EMC console.  Anyone have any ideas on this?


    sábado, 09 de junio de 2012 23:09
  • If I was you I would revert the changes you made and follow the quick tests I outlined above.

    Quick

    Simple

    and works :)

    Or as per Catastrophic Failure post

    "This issue can be resolve with Update Rollup 2 for Exchange Server 2010 Service Pack 2. Bellow "

    lunes, 11 de junio de 2012 3:05
  • Hello,

    I reverted my changes to the initialization powershell script.  I have updated to Rollup 3.  This did not fix the issue so I tried JimBobUK's steps by copying the Administrator user in ADUC to a new username.  However, when I login under that new user, it won't even let me open Exchange Management Console, says I don't have permission.  I double checked in ADUC and the duplicated user was successfully copied, it has all the same group memberships as the original administrator.  At sort of a loss here....

    Thanks in advance for any help.

    martes, 12 de junio de 2012 23:05
  • Hello,

    I reverted my changes to the initialization powershell script.  I have updated to Rollup 3.  This did not fix the issue so I tried JimBobUK's steps by copying the Administrator user in ADUC to a new username.  However, when I login under that new user, it won't even let me open Exchange Management Console, says I don't have permission.  I double checked in ADUC and the duplicated user was successfully copied, it has all the same group memberships as the original administrator.  At sort of a loss here....

    Thanks in advance for any help.

    How odd!

    You sure you duplicated the user with Exchange permissions?

    I would suggest duplicating again just to make sure

    I have tested my fix a number of times by duplicating the user and everytime it works.

    Make sure you reverted all changes

    martes, 12 de junio de 2012 23:19
  • Hello,

    I reverted my changes to the initialization powershell script.  I have updated to Rollup 3.  This did not fix the issue so I tried JimBobUK's steps by copying the Administrator user in ADUC to a new username.  However, when I login under that new user, it won't even let me open Exchange Management Console, says I don't have permission.  I double checked in ADUC and the duplicated user was successfully copied, it has all the same group memberships as the original administrator.  At sort of a loss here....

    Thanks in advance for any help.

    How odd!

    You sure you duplicated the user with Exchange permissions?

    I would suggest duplicating again just to make sure

    I have tested my fix a number of times by duplicating the user and everytime it works.

    Make sure you reverted all changes

    Hello,

    I agree that it's odd.  I tried copying the admin user with exchange permissions again in ADUC to another user, and it still acts like the new user doesn't have exchange permissions even though they are right there.  Very very odd.  I also made sure that all changes were reverted.  Not sure what's going on here.


    martes, 12 de junio de 2012 23:53
  • Hello,

    I reverted my changes to the initialization powershell script.  I have updated to Rollup 3.  This did not fix the issue so I tried JimBobUK's steps by copying the Administrator user in ADUC to a new username.  However, when I login under that new user, it won't even let me open Exchange Management Console, says I don't have permission.  I double checked in ADUC and the duplicated user was successfully copied, it has all the same group memberships as the original administrator.  At sort of a loss here....

    Thanks in advance for any help.

    How odd!

    You sure you duplicated the user with Exchange permissions?

    I would suggest duplicating again just to make sure

    I have tested my fix a number of times by duplicating the user and everytime it works.

    Make sure you reverted all changes

    Hello,

    I agree that it's odd.  I tried copying the admin user with exchange permissions again in ADUC to another user, and it still acts like the new user doesn't have exchange permissions even though they are right there.  Very very odd.  I also made sure that all changes were reverted.  Not sure what's going on here.



    Try using the duplicated account on a different Exchange node that you have not upgraded or touched yet, see what heppens with the account
    miércoles, 13 de junio de 2012 8:54
  • Hello,

    I reverted my changes to the initialization powershell script.  I have updated to Rollup 3.  This did not fix the issue so I tried JimBobUK's steps by copying the Administrator user in ADUC to a new username.  However, when I login under that new user, it won't even let me open Exchange Management Console, says I don't have permission.  I double checked in ADUC and the duplicated user was successfully copied, it has all the same group memberships as the original administrator.  At sort of a loss here....

    Thanks in advance for any help.

    How odd!

    You sure you duplicated the user with Exchange permissions?

    I would suggest duplicating again just to make sure

    I have tested my fix a number of times by duplicating the user and everytime it works.

    Make sure you reverted all changes

    Hello,

    I agree that it's odd.  I tried copying the admin user with exchange permissions again in ADUC to another user, and it still acts like the new user doesn't have exchange permissions even though they are right there.  Very very odd.  I also made sure that all changes were reverted.  Not sure what's going on here.



    Try using the duplicated account on a different Exchange node that you have not upgraded or touched yet, see what heppens with the account

    Hello,

    I tried it on a fresh node that was just installed.  Nothing has been done to it yet.  It still would not let the either duplicated user open EMC. 

    • Propuesto como respuesta Rene Sosa sábado, 21 de julio de 2012 18:47
    • Votado como útil Rene Sosa sábado, 21 de julio de 2012 18:47
    • Propuesto como respuesta Komal Bhatia sábado, 04 de agosto de 2012 3:26
    miércoles, 13 de junio de 2012 21:27
  • Created a copy user and was able to successfully open the EMC.  For the earlier user, deleted the windows profile of the user and rebooted the server.  It resolved the issue
    sábado, 04 de agosto de 2012 3:27
    • We installed the SP2 in all roles (2 cas \ 2 hub) and this problem not occurred again

    miércoles, 12 de septiembre de 2012 12:56
  • Glad to hear my fix is working :)
    jueves, 13 de septiembre de 2012 9:28
  • Very good :)

    jueves, 13 de septiembre de 2012 16:13
  • Hi everyone,

    applied the script and I get the error "domain\administrator" could not be found !


    ISMAILL

    martes, 06 de noviembre de 2012 18:51
  • @ISMAILL

    It may be worth you reading through this thread, It may also help if you gave examples of what you have tried already

    miércoles, 07 de noviembre de 2012 9:04