Migrating DS Jobs after Upgrade and separation

Jobs in DS can be exported at any time and then re-imported to other servers. Upon reimport you would need to ensure that any paths to files and folders were adjusted.

Is that what you're referring to or are you asking about something else?

I little more information would be nice, like what version of DS were you running before.

The version does seem to make a difference. If your old DS was 6.5 (like ours was) and you try to export the jobs out then import them into a 6.8 or 6.9 DS, it will not let you. It gives a database error of Invalid object name 'x_task'

Hi-

We are currently encountering this problem while trying to import 6.5 exported jobs and also newly created 6.9 exported jobs. We setup the console users to have public access to the express database, as the 6.9 installation notes suggest, but after being plagued by errors when trying to do things, we ran the dsdbsecurity.exe utility and the public permissions were configured correctly. Everything worked great after this except for importing jobs. Even if the console user has DBO access to the sql express database, the super fun "Database error: Invalid object name 'x_task'" remains. Any suggestions whatsoever would be greatly appreciated. Thanks in advance.

Hi,

We had the same problem with importing in DS 6.8 SP2.
We have created a workaround by adding the users that have to import jobs to the sysadmins group on the sql server.

this is a bug in DS since 6.8 SP2 that is stil not solved by altiris.

i hope they will do so soon because making users sysadmin is not a good option from security point of view.

Regards,
Dennis Snelleman