0 votes

I am using the builtin Computer Management role.
I have modified the role to also provide the ability to change and reset the password.
My help desk users are assigned to it and to the OUs for the computers
I have created home page actions to create computers in the specific domains and OUs.
The user only has to fill in the name and who will be adding it to the domain.

When they add the computer to the domain in Adaxes via the home page action, the computer is created successfully. When they then go to the computer and attempt to add it to the domain, it fails indicating that the computer already exists on the domain. As a system admin using the default admin page, I am able to create the same computer in the same OU (after deleting it), set the same user to add the computer to the domain, and then have that user add it successfully. I had the user create a computer and I create another. I found that the one the user created was shown as disabled in AD. I do not have any business rules or patterns that I can see doing this. There is nothing in the home page action settings that I can find doing this either. Why is the computer being created as a disabled object?

Thanks

by (1.2k points)

1 Answer

0 votes
by (216k points)

Hello,

We confirm this as our bug that will be fixed in one of our future releases. Thank you for the bugreport!

The thing is that the Create Computer Home Page Action creates incorrect computer accounts when the 'Assign this computer account as...' options are removed from the Home Page Action form. To workaround the issue, you can add a default value for the Account Options property:

  1. On the computer, where your Web Interface is installed, start the Web Interface Customization tool.
  2. In the Interface type drop-down list, select the Web Interface that you want to configure.
  3. Activate the General tab and click Configure Home Page Actions.
  4. In the Home Page Actions dialog that appears, double-click the Home Page Action that you use to create computers.
  5. Activate the Form Customization tab.
  6. Click Add... in the Predefined Fields section.
  7. In the dialog box that appears, select the Account Options property.
  8. In the Default value field, type 4096.
  9. Click OK 2 times.
  10. Click Apply.

Now the Home Page Action will create normal computer accounts.

0

Confirmed. This resolved the issue.

Thank you

Related questions

0 votes
1 answer

I have been trying to use Adaxes and different tools to detect a new computer being joined to a domain or a computer being REjoined to the domain (uses an ... but must be filtered to remove Anonymous Logon because of automatic domain secure channel events.

asked Mar 3, 2015 by JoeC (470 points)
0 votes
0 answers

If a computer has the KB5020276 Netjoin: Domain join hardening changes Windows update installed, you might encounter the following error message when attempting to join such a ... the primary computer owner (specified in the ManagedBy (Primary) property).

asked Jan 20, 2023 by Adaxes (560 points)
0 votes
1 answer

I recently upgraded to version 2013.1 and since then a create user action on my help desk website no longer adds the @domainname.com to the User logon name field. ... there Exchange will not create the mailbox. Any help with this issue is appreciated. Thanks

asked May 13, 2013 by bemho (520 points)
0 votes
1 answer

Is there any way to add a warning message when someone tries to add a group member that already is member? Checked config but found nothing related. Added a new member that ... the group and there is no warning, and the logs show that the task was completed.

asked Jul 9 by lramirez (20 points)
0 votes
0 answers

So I modifyed the Script so that it can also search for the Public Folder Access as Owner. But i my getting an Error message. { $exchangeServer ... folders to report $searcher = $Context.CreateGuidBasedSearcher($guidsBytes) $Context.Items.Add($searcher)

asked Dec 19, 2022 by Sandberg94 (340 points)
3,589 questions
3,277 answers
8,303 comments
548,104 users