Windows Essentials

Question

Are there any tips/documentation on managing a Windows Essentials domain with o365 integration using Adaxes?

I believe I need to run a PS command to link the accounts in the essentials dashboard, to connect it to o365:

$username = "******"
$password = "********"
$secstr = New-Object -TypeName System.Security.SecureString
$password.ToCharArray() | ForEach-Object {$secstr.AppendChar($_)}
$cred = new-object -typename System.Management.Automation.PSCredential -argumentlist $username, $secstr
Invoke-Command -ComputerName <ipaddress> -ScriptBlock {& Set-O365AssignedUser -LocalAccountName "%firstname%.%lastname%" -O365AccountUPN "%firstname%.%lastname%@domainname.com"} -credential $cred

But i am having trouble getting it to run remotely. Anyone else doing this?

TIA

Comments

Hello Jason,

Could you be more specific on what exactly you need to achieve?

If you want to manage your Windows Essentials domain with Adaxes, you just need to register it. For details, have a look at the following help article: https://www.adaxes.com/help/?HowDoI.Man ... omain.html. For information on how to manage and automate Office 365 tasks using Adaxes, have a look at the following tutorial: https://www.adaxes.com/tutorials_Active ... ice365.htm.

---

Sorry, finally getting back to this one. There is a component of the windows essentials dashboard (and the Essentials server experience, if installed) that links the local AD account with the o365 cloud account. There is a PS script that can do this, but I was having trouble with it. I got it to work using winrm to run the remote command, I learned it is very time sensitive. Sometimes the PS to link the account runs before the account is propagated in the o365 side side, meaning it sometimes completes and sometimes doesn't. It seem that extending the business rule run time in Adaxes with a sleep command (like Start-Sleep -s 250), helps improve the likelihood of it running without error, but if set too high then Adaxes times out with an error.
I am thinking that a separate custom command my be needed that can be run manually X number of minutes after a new user is created.

Answer 1

Hello Jason,

It seem that extending the business rule run time in Adaxes with a sleep command (like Start-Sleep -s 250), helps improve the likelihood of it running without error, but if set too high then Adaxes times out with an error.

You can try increasing the timeout for running PowerShell scripts. For details, see https://www.adaxes.com/help/?ManageBusi ... meout.html.

I am thinking that a separate custom command my be needed that can be run manually X number of minutes after a new user is created.

Yes, this will work. There is no possibility to postpone executing a Custom Command in Business Rules.