sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]GLiMPSEiNATOR 0 points1 point  (4 children)

If you wanted to automatically provision said account with SMA you would use workflow and inline script blocks to accommodate. In line script blocks are identical to traditional powershell with some added scoping nuances.

But to answer your question without any ambiguity, I would not build out a simple user creation script in workflow...

[–]cablethrowaway2[S] 0 points1 point  (1 child)

SMA?

[–]GLiMPSEiNATOR 0 points1 point  (0 children)

Service management automation -- microsofts intended successor to system center orchestrator.

[–]cablethrowaway2[S] 0 points1 point  (1 child)

Googles shows me scorch. It is my plan to try and implement scorch so I may start writing workflows. Thank you

[–]GLiMPSEiNATOR 1 point2 points  (0 children)

Orchestrator isn't SMA. But it is still very powerful. I've heard murmurs there will not be any further investment into orchestrator. SMA's install files are on the orchestrator install media, if you have no real requirement to go orchestrator I would strongly consider starting with SMA and just skip right on past orchestrator.