I am looking for a solution around a task that is growing bigger for us as roll out the system to more service desks.
Currently we create new users in AD and export them to LANDesk and also run a sp that creates a network login. This is a requirement for our internal analysts to have SSO, this works perfectly for us and isn't an issue but then when we bring end users (customers) into scope the tasks becomes unmanageable.
We have to create end users in our AD and run the sp to create the network login, the users don't have SSO but from my understanding we have to include AD because of the authentication issues of using LANDesk security.
The above task is only going to get worse when you start to factor in changes to user details and more customers being moved to the new help desk so I am looking at what options we have...
One suggestion was to use PowerShell that could export the new users (or changes) and then import them into AD, this sounds like a lot of work and I am not convinced we are the only organisation that requires SSO for internal users and a secure authentication/setup process for end users.
Are we missing something?