0 votes

Hello!

We are using the new Adaxes 2014, and I have stumbled upon the two following events:

* Calculated default values are not updating when we are creating a new user through the web interface.
I have made some default user pattern values as such:

User Logon Name = %SAMAccountName%
User Logon Name (Pre Windows2000) = %firstname:lower,1%%lastname:lower,2%
Email: %SAMAccountName%@domain.com

Or for convenience, an image:

In my website config, it looks like this:

On the actual website, it looks like this: NB: Everything works perfectly if I don't change the username!

However, if I for some reason need to change the calculated value in User Logon Name and then press create, It creates the new mailbox, user etc with the default calculated value:

Create User Home Directory':    Create the '\\fileserver\d$\data\nte' home directory for the user and map it to 'H:' drive
'Create User Home Directory':   Share the home directory of the user as 'nte$'

Am I doing something wrong? :)

Also:

Business Rule -> Create User Home Directory

After creating a new user, create the \\fileserver\d$\data\%username% home directory for the user and map it to H: drive

Is it possible to make "map it to $drive" optional? We map all our drives via GPO, so for each user to also have their home drive hardcoded in their user profile is not necessary.

Regards,
Erlend

by (160 points)

1 Answer

0 votes
by (215k points)

Hello,

Issue with calculated default values

The thing is that, proceeding from your property patterns, the User Logon Name (pre-windows 2000) property (the LDAP name of which is sAMAccountName) is generated based on first name and last name, and then all the other properties that you mention (User Logon Name, Email, Exchange Alias, pattern for the home directory path etc) are generated based on that property. However, on your form for creating users, you have the field for the User Logon Name property, not for User Logon Name (pre-windows 2000). There are no other properties that are generated based on the User Logon Name property, and thus, when you change it on the Web Interface, you change only this property, and nothing else.

To workaround the issue, you can, for example, show the User Logon Name (pre-windows 2000) property on the form for creating users instead of User Logon Name. When this property is changed by users, all the other properties generated based on it will also be changed.

Create User Home Directory without a Drive Letter

Yes, it's possible. For this purpose, in your Business Rule, first you need to create a home directory for the user and map it to a certain drive, and then delete the Home Directory Drive property, which will 'unmap' the home directory. Pay attention that a home directory created like this will be displayed in Adaxes as a local path, not as a network path.

To add an action that 'unmaps' the home directory to your Business Rule:

  1. Launch Adaxes Administration Console.
  2. In the Console Tree, expand the service node for your Adaxes service.
  3. Navigate to and select your Business Rule that creates home directories for users.
  4. Right-click the action that creates home directories and click Add New Action.
  5. Select the Update the User action.
  6. Click Add.
  7. Select the Home Directory Drive property.
  8. Switch the radio button to Remove property.
  9. Click OK two times.
  10. Use the arrow buttons at the bottom and make sure that the new action goes after creating a home directory.
  11. Save the Business Rule.

Related questions

0 votes
1 answer

Given Scenario: Adaxes domain user is remote with his laptop and has adaxes self service client installed on Windows and is enrolled for self service via Adaxes. We ... get updated when a user initiates password reset/change password from the lock screen ?

asked Nov 2, 2020 by rsaran (70 points)
0 votes
5 answers

Good morning, We have been testing two separate laptops with the new off-site password change feature. We can successfully reset the password from the Reset Password option on ... accept the new password, only the old. AD is updated successfully. Please help!

asked Aug 27, 2017 by Piko (210 points)
0 votes
1 answer

Hello, I am trying to create a custom command that handles the process of converting a user account for a temp to a FTE. This needs to: 1. move the user to a new OU. 2. change ... to "xxx" OU Set 2: Always --Modify the user: set employee type to...... etc.

asked Jul 26, 2013 by DFassett (710 points)
0 votes
1 answer

We have a form to used by our HR Reps to create non-employee records. There are two fields on the form that are auto-generated via a property pattern: Full Name ( ... changed to cause this new behavior? Nothing has changed with our property pattern set-up...

asked Aug 30, 2016 by sandramnc (820 points)
0 votes
0 answers

Hello As I have mentioned before - when creating a new user, I need to fetch the formal name of the user from an external system. In the external system, the user's formal name ... as an logmessage, but ..... this will appear as a bad solution :oops: - Thanks

asked Jun 8, 2016 by Boxx.dk (2.6k points)
2,779 questions
2,511 answers
6,574 comments
25,626 users