how can I order manually the AD Properties, so that they have a desired order in the Workflow form.
It would be really nice to have this possibility.
I observed, that sometimes the Template Generator (V2) will rorder the AD Properties automatically by himself.
normally on the web frontend it should be shown in the order which are in the template file. If that is not the case it is a bug. In the rich client you have mandatory fields, like samaccountname, givenname, surname and description where you can't change the order, but the LDAP properties itself should be the same as in the template file.
When it is reordered by the TG then it would be great if Paul find time to fix it.
for OpenOrder Templates you can change the order by editing the Hierarchy (there should be a button there somewhere ).
For all other templates currently you can not change the order in the Generator.
I might add that in a future release but at the moment you will probably have to manually reorder them in the template.
nice tool, thanks.
I got an Error whren editing lookup table entries. After pressing ok the program dies. Tested with the user-example and a self created template.
Hope you have an idea.
Edit: And the minimum password length for user creation schould be chooseable or 8 for me.
I'm trying to get this to work, however I'm having some difficulty with the username creation. Our usernames are the first 3 letters of the surname and the first 3 letters of the first name.. so for example, if the user was James Dean, his username should be deajam. How do I set this in the template??
At the moment its taking the first letter of the firstname. surname...
this creationrule should work for your case:
it selects the first 0 to 3 characters of sn and firstname, the 0 to 3 part is important in case you have names that are less than 3 characters long.
That worked successfully!
Last question, is it possible when creating the exchange mailbox as part of the template that it applies our corporate retention policy to the newly created mailbox?
I thought I could make use of the Exchange Scripting Agent, however it looks like its not being called when creating a user based off a template in ARM. Works when i manually create a mailbox in exchange though.
the way to do this is to use the script execution you can define in the template and set the retention policy in that script (for example via powershell: set-mailbox -retentionpolicy "policyname").
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process. Learn more today by joining now.