Does right click Export as CSV and then Import doesn't work?
I have never tried that but there is an option for it.
Not sure if it would work on same version but logic says no as for landesk to process imports they need to be ldms files in XML format - pretty sure about that...
That's true, estrange that there is an Export ans .csv but not an import the same format.
This may be a database related task.
Yes i thought that too but it appears its just informational.
If you just want to migrate users with the current ldap structure, you could theoretically move over the ConsoleUsers table by scripting the current data and then running that on the end database.
However, that wouldn't migrate anything owned by the user like tasks, queries, etc, and you would need to be using the same LDAP sources, added in the same order (otherwise the ldap source IDN would change and you'd have to update those manually). You would also need to run CreateLandeskRights.exe, ResolveUserGroups.exe and ResolveDBCustomGroups.exe to rebuild some attributes based on the new Core, like local groups that use hostname\groupname.
This sounds promising thanks!
So yes same ldap structure and as long as i get the user info and what roles and scopes they have ( they are mirrored on the cores ) then it should work.
So the roles and scopes do not have individual IDs that would be different on the cores? We do not need tasks, queries etc just scopes and roles.
would that still work?
So we are looking at only exporting certain users and there roles / scopes...
It may not work and we are backing the DB up before the import in case. But i dont want to overwrite the table... wish me luck
Permissions would involve moving over the tables below:
Those link together to define permissions for users. I've migrated users and permissions using those, but depending on your situation there may be a few others that are configuration specific. Migrating everything is harder than just the user object.
For just users, I'm not sure there's a good way to do that without essentially developing an application/process. There's too many specifics tied to the user that are well defined, but would take a lot of work to manually trawl through.
A user export would be a good ER though. Something that retains their rights and roles. We already allow you to export and import Roles.