Thank you @koryknick, the solution worked.
I happen to tweak the expression in the mapper a bit so that no extra spaces were observed:
Yes, the text file will always have “x” fields, it wouldn’t even go to x-1 or x+1.
Moreover, as there is no max value in a group size as per documentation, I can pretty much keep it to 100 for instance to handle the additional rows coming in the future. What are your thoughts?
Intentionally, kept 100 and not 99999999 as I’m not anticipating anything more than 8.
Thank you.
Regards,
Darsh
Hi Vish
We are creating a new user object successfully but are having an issue with giving this new account a password. Can you shed any light on how to do this?
Hi @Rod, It has been a long time since I looked at this 🙂 I don’t remember exactly but I think I’ve always used useraccountcontrol 544 to force a password change on 1st login. I’d suggest starting here: New-ADUser | Microsoft Docs and make sure you are setting the right attributes like useraccountpassword and also ensure you have the right user account control value (list of values here: All Codes (by Rajnish Bhatia): Active Directory userAccountControl Values)
I’m attempting to create user with a password as well but the userPassword field doesn’t seem to populate into it. Is userPassword not something that is accepted as a key attribute in the Active Directory snap in? It doesn’t give me an error when passing values in that attribute, but it doesn’t actually set any password. I assume the underlying connection is ldap calls and not using any dot net.
Also I’m trying to find out how to pass in multiple array values.
Also lastly, i want to get the object guid back, but it seems the snap-in pre-interprets the value by decoding with base 64 but provides it as a string (which is unusable) vs the byte array or even better decoded to bytes and properly providing the guid as the string value
