Unable to migrate Helpdesk 6.0 categories
Updated: 21 May 2010 | 7 comments
This issue has been solved. See solution.
I'm attempting to migrate Helpdesk 6.0 categories from my production Helpdesk server to my test network ServiceDesk. I keep getting an error "Unable to connect to NS, please verify credentials." I am attempting to connect using my production domain Altiris server application credentials.
My test network is not on the same domain as my production network. Is it not possible for the wizard to connect to a different domain?
Discussion Filed Under:
Comments
When specifying the domain on
When specifying the domain on the credentials screen, you should be using the domain where the HD server resides (s.t. a credential can be formed). Also, if the machine name by itself does not work, try using either the IP address of the HD machine or the machine name qualified with the domain name (i.e. <blah>.<domain name>)
User must be active helpdesk worker in the 6.0 database
Thanks for the tips. In testing your additional suggestions, we discovered that the issue was: the wizard will only connect using an account that is an active worker in the HD 6.x database. Here's what we tested:
ns address: IP address of HD server
use https: unchecked
domain: parent domain (domain of HD server)
against those options, we tested the following users:
1) Altiris service account - has altiris administrator rights on the 6.x NS, but no helpdesk worker account - can't connect
2) account with active helpdesk worker account and altiris administrator rights - can connect
3) account with active helpdesk worker account but no altiris admin rights (worker rights only) - can connect
4) account with helpdesk worker account and altiris worker rights, but helpdesk account set to "inactive" - can't connect
5) using the same account from (4), set the Helpdesk worker account back to "active" status - can connect
Unable to migrate Helpdesk 6.0 categories
Hi All,
For people who do not have Helpdesk 6 and want to load there own "Categories" hirearchy items here is a Workflow 7 form.
The import file must be a text file with lines:
Incident Management.Categorylevel1
Incident Management.Category.Cagetorylevel2
...
The space between incident and Management is required.
Enjoy
Fabrice
FABEMARA Consulting the main Symantec Altiris Partner in Spain
http://www.fabemara.es
http://assistance.fabemara.com
That's awesome, Fabrice
Text file input would be very cool. Thanks for posting. If you have time, please confirm what I think you're saying about text file input format:
For example, if I wanted to create the Heirarchy
Office Apps
MS word
MS excel
CADD apps
AutoDesk
C3D
Revit
Bentley
Microstation
WaterCAD
Then my text file input should be:
Incident Management.Office Apps
Incident Management.Office Apps.MS word
Incident Management.Office Apps.MS excel
Incident Management.CADD Apps
Incident Management.CADD Apps.AutoDesk
Incident Management.CADD Apps.AutoDesk.C3D
Incident Management.CADD Apps.AutoDesk.Revit
Incident Management.CADD Apps.Bentley
Incident Management.CADD Apps.Bentley.Microstation
Incident Management.CADD Apps.Bentley.WaterCAD
Also, I haven't looked at Workflow solution yet. The .zip file you uploaded is a package that I can add in workflow solution? I can read the workflow documentation to see how that's accomplished.
Workflow 7 package to load "Categories" Hirearchy items
Thanks :)
The format you explained is right.
This is a workflow project to be loaded on your Servicedesk server. Just double click and it will open the Workflow designer. It is using standard component so you should not need to have a Workflow Solution license, the SD7 license should be enough.
Best regards,
Fabrice
FABEMARA Consulting the main Symantec Altiris Partner in Spain
http://www.fabemara.es
http://assistance.fabemara.com
You're my hero
You rock. This is much better than importing. I marked your post as the solution.
Very nice, works great!
Good job!
Would you like to reply?
Login or Register to post your comment.