Follow

Active Directory (AD) Extensions

Program

https://admin.365command.com/Download/DirectoryExtensionsInstaller

 

Set up

http://365command.com/support/active-directory-extensions/initial-configuration/



Help

http://365command.com/support/active-directory-extensions/



http://365command.com/support/active-directory-extensions/custom-tabs/groups/office-365-custom-attributes/

 

AD Extensions are Community Supported. If you have issues...

This usually means that the user has not successfully followed the instructions on the website, or the domain they entered is not associated with a valid 365 command subscription.

The instructions for the tool explain how to enter the proper credentials: http://365command.com/support/active-directory-extensions/initial-configuration/

In this case I cannot find any tenant with the domain rettieco1uk.omnimicrosoft.com. However, the AD extension tool has been running in their environment since Jan 8, 2015, without success. We log all the failed license request attempts, and in this case the license request has never succeeded, as we have no customer on file with that domain. It is possible they had a valid messageops license file at one time, but we wouldn't have a record of that. If a customer is using a messageops assigned license, then the tool never contacts 365 command for verification, and it doesn't use 365 command resources at all.

Below is some related info I put in COMMAND-880, btw:

Resolutions:

1) While there is no particular problem with the AD Extension licensing, the instructions for initial configuration could be improved slightly to set user expectations. See this link and attachment:

http://365command.com/support/active-directory-extensions/initial-configuration/

The initial-configuration does not explain that the license issued is only valid for 30 days, but that it will automatically renew for another 30 days if it is expired, and if the customer has a 365 command account in good standing associated with their Office 365 global admin credentials in the tool.

 

Could you please try a few things for us to further test this:

1) First try a new version of the AD extension was deployed on Monday. It has a more reliable powershell host farm name embedded in it.

They can download it here > https://admin.365command.com/Download/DirectoryExtensionsInstaller

2) If that doesn't work, please test the following powershell commands on the same machine where the AD extension is installed.

When prompted for credentials you should enter the same O365 global admin credentials that were entered into the AD extension.

Import-Module MsOnline

$credential = Get-Credential

Connect-MsolService -Credential $credential

Get-MsolDomain

$O365Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid-Credential $credential -Authentication Basic -AllowRedirection

Import-PSSession $O365Session

Get-AcceptedDomain

Remove-PSSession $O365Session

Please then send the output to us. We may need to set up a call with you to investigate further.

Kind Regards,

This usually means that the user has not successfully followed the instructions on the website, or the domain they entered is not associated with a valid 365 command subscription.

The instructions for the tool explain how to enter the proper credentials: http://365command.com/support/active-directory-extensions/initial-configuration/

Initial Configuration - 365 Command

Click the links below for initial configuration instructions, additional information and technical support: Initial Configuration Understanding the Account Attribute Changing a Name with the Active Directory Addin: Changing the Name of a Federated User Changing the Name of a Directory …[ Read More ]

Read more...

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.