All about preventing erroneous sites from being created in SDP upon user sync/user import

All about preventing erroneous sites from being created in SDP upon user sync/user import

I have a real challenge in that when on of my 85 technicians creates an AD Account and the site has a typo or is altogether incorrect, SDP creates a new site and if we don't catch it quickly, requests come in, are associated with those requests, and appear as being logged against UNKNOWN site and UNKNOWN region in our reporting. Then, after fixing the AD Account, we have to move the users to the correct site by hand. We have to search for an bulk edit any tickets generated to update the site, move any assets, and, if some thing else ends up being populated, we end up forever having to see the erroneous site in our site list. (We have 112 sites and 65 inactive sites at the moment, and growing).

FEATURE REQUEST
I have a feature request in to deny the sync. of AD Accounts if the site isn't within our list of active sites.
  • Is it possible to have the feature request number again; I have so many requests and I can't keep track.

FEATURE REQUEST
  • Is it possible to get a list of all my submitted and assigned feature requests?

We use ADManager in our environment, so templating user account creation has help quite a bit, but we still have some techs who create by hand, and so we have to babysit this.

FEATURE REQUEST: Remove Inactive Sites
  • Right now I have about 65 inactive sites that can't be removed because there is data out there somewhere in SDP still associate to the erroneous site. I'd love a process of removing those because it clutters up our environment. May I have a process or feature request for doing so?

If some find this helpful, I'm asking for help from the ADManager team to produce a report that runs daily to tease out erroneously created AD Accounts. There's no doubt that one can do this in PowerShell, so even if you don't have ADManager, you should be able to do this, but an ADManager schedule report would be a nice touch.

==========

See my request

Not all of our techs use ADManager and still create AD accounts manually. The result is that we frequently have AD User Accounts created with an office location that either isn't exactly correct or is entirely incorrect for our environment.

Because we also use ServiceDesk Plus, the erroneous Office Location results in a new and erroneous Site created during our AD sync.

I'd like to be able to run an ADManager report that essentially says, "Show me a list of user accounts in the domain that do not have Office Location" set to one of x values."  Unfortunately, that list of "x" values is about 130 sites.


I'd like to be able to schedule a report to run daily to show all user accounts that do not have one of our listed sites in Office Location.

Is this possible in ADManager?


Many thanks,
Adam
                New to ADManager Plus?

                  New to ADSelfService Plus?