Spartacus Tv Series Season 3 ^hot^ < CERTIFIED • SECRETS >
Liam McIntyre fully inhabits the role in this final stretch, portraying a leader burdened by the weight of thousands of lives. His journey from a man fighting for his wife to a man fighting for the concept of freedom is the heartbeat of the season.
The stakes are raised with the introduction of (Simon Merrells), the wealthiest man in Rome. Unlike the villains before him, Crassus respects Spartacus. He studies his opponent’s tactics, making him the most dangerous adversary the rebels have ever faced. Beside him is a young, ambitious Julius Caesar (Todd Lasance), who provides a tactical edge and a glimpse into the future of the Roman Empire. Character Arcs and Evolution spartacus tv series season 3
The third and final season of the Starz original series, , stands as a monumental conclusion to one of the most visceral and visually striking sagas in television history . Following the massive success of Blood and Sand , the prequel Gods of the Arena , and the second season Vengeance , Season 3 brings the legendary slave rebellion to its inevitable, tragic, and heroic climax. The Premise: All Roads Lead to Rome Liam McIntyre fully inhabits the role in this
Hi!
thanks for the detailed post. I’m facing an issue that isn’T listed here and wonder if you would have an idea.
When signing in the wizard, I get :
a managed service account with name “” could not be set up due to the following error, unexpected error while searching for MSA: specified directory service attribute or value does not exist.
in the log, it looks like this.
ODJ Connector UI Error: 2 : ERROR: Enrollment failed. Detailed message is: Microsoft.Management.Services.ConnectorCommon.Exceptions.ConnectorConfigurationException: Unexpected error while searching for MSA: The specified directory service attribute or value does not exist.
I believe I have all the requirements check… I tried to pre-create a gMSA account, set it to the service, no luck. On different servers as well, with or without the OU specified in the XML…. nothing budge…
Any idea is more than welcomed!
thanks
Jonathan – SystemCenterDudes
Hi Jonathan – great question, and you’re definitely not alone on this one.
That specific error is a bit misleading, but the key part is “error while searching for MSA” rather than creating it. In the cases I’ve seen, this usually points to an Active Directory lookup issue, not a missing requirement in Intune itself.
A few things that are not the root cause (even though they feel like they should be):
Pre-creating a gMSA (unfortunately unsupported by the connector at the moment)
The OU specified (or not specified) in the XML
Setting the service to run under a manually created account
The most common things I’d double-check instead:
Managed Service Accounts container
Make sure the “Managed Service Accounts” container exists at the domain root and is readable. The connector explicitly queries this container, and if it’s missing, hidden, or permissions are restricted, you’ll get exactly this error.
Schema visibility
Verify that the AD schema attributes for managed service accounts (for example msDS-ManagedServiceAccount) exist and are fully replicated. I’ve seen this break in domains that were upgraded in-place or restored at some point.
Domain controller selection / replication
The connector doesn’t let you choose a DC. If it’s hitting a DC where schema or container replication hasn’t completed yet (or a different site), the MSA lookup can fail even though “everything looks correct”.
Permissions beyond create
Even if the installing admin can create MSAs, make sure they also have read permissions on the Managed Service Accounts container and schema objects. Hardened AD environments sometimes block this unintentionally.
One important note: right now, the connector expects to create and manage the MSA itself. Pre-creating a gMSA or assigning it manually tends to make things worse rather than better.
If you check those areas and still hit the issue, I strongly suspect this is an edge-case bug in the new MSA discovery logic introduced with the updated connector. Hopefully we’ll see clearer documentation or a fix in an upcoming build.
Hope this helps – let me know what you find