Integrating Service Desk in a new Forest
Hello support !
I've discovered Service Desk quite recently and highly appreciate it. I have a question though and though you might certainly help :)
Here is the scenario: my company recently acquired another company that was using Service Desk as its ticketing system and asset management.
We have started using the product on their domain for user support and asset management (domains have not merged yet) and are quite satisfied about it. We are now planning to use it as the global ticketing system in our company for the whole forest.
I've searched the forum before posting and found this post that was quite interesting: forums.adventnet.com/viewtopic.php?t=198111
One thing is said there:
I fear that might be a problem for us since the naming strategy for users is completely different between the company we acquired and ours. Since users and technicians that are today in the Service Desk Database will soon have different names (after the migration), how will that impact Service Desk ?
Should it be a blocking issue technically speaking what could be our options to still keep the history for user request/assets/knowledge base ?
Well i guess that's it. Thank you for reading and i wish you a happy (soon to come) new year :)
Best regards,
Julien Durand
I've discovered Service Desk quite recently and highly appreciate it. I have a question though and though you might certainly help :)
Here is the scenario: my company recently acquired another company that was using Service Desk as its ticketing system and asset management.
We have started using the product on their domain for user support and asset management (domains have not merged yet) and are quite satisfied about it. We are now planning to use it as the global ticketing system in our company for the whole forest.
I've searched the forum before posting and found this post that was quite interesting: forums.adventnet.com/viewtopic.php?t=198111
One thing is said there:
Ensure that you have the same list of users (both requesters and technicians) across the new domain.
I fear that might be a problem for us since the naming strategy for users is completely different between the company we acquired and ours. Since users and technicians that are today in the Service Desk Database will soon have different names (after the migration), how will that impact Service Desk ?
Should it be a blocking issue technically speaking what could be our options to still keep the history for user request/assets/knowledge base ?
Well i guess that's it. Thank you for reading and i wish you a happy (soon to come) new year :)
Best regards,
Julien Durand