You should be able to enable security and tweak the permissions.  The other way would be to utilize DSWEB (the web interface).  This seems to be an easier way to restrict this, however, it can be cumbersome to use.

but there isnt an alternative for the drag and drop part when i want to install an image ????

You don't have to drag'n drop in the Win32 GUI, you can also use the Job Schedulig Wizard. This you can find under the Operations menu. The you selcetc the job and computer you want. Is that what you are looking for?

You can also right click in either the Computers or Jobs section and select the Job scheduling wizard.

that might be a sollution; the jib scheduling wizard and a way to disable drag and drop

I do not think it is posible to disable Drag'n drop. You will have to either trust that your DS users knows what they are doing. But another option could be implementing Security.

In my opinion DS i quite a dangerous tool, where you have to be very alert of what you are doing..... So it is not a good idea to use the tool after 14 hours straight work ;)

well, the last months some tired engineers dragged the jobs to too many computers; thats why i am searching a different way of getting the job to the clients.

I've learned over time, the only way to combat that is to either enable security or to enforce consequences on the offending parties (i.e. a write up, a fine, etc.).  I've found fines work the best as there are no job related consequences and the money can be used to benefit the entire group (sort of like a swear jar or something similar).

I've also found it's best to train the staff to drag the computer to the job and not the other way around.  Also, I train them to click the second tab of the scheduling window to ensure that the correct machine(s) is(are) being scheduled.

we do that; dragging the job to the computers. But last month something went wrong; 100 computers got installed instead of 1. We still dont know what happened. Maybe we should train the people to click the second tab but still, they can click too fast.

In your post above, you mention that you are dragging the job to the computer.  This is where most mistakes are made (accidentally gets dragged to the wrong computer or gets dragged to the folder containing all of the computers).  It's better to drag the computer to the job.  This way, if you intend to run a job on 100 computers, you can drag the folder to the job, instead of accidentally dragging the job to 100 computers that you didn't want it run on....make sense? 

Yup, makes sense and thats the way we work. the only problem is that even this way of working can cause erorrs and thats why i am looking for a different way of sending jobs to client and disabeling the drag and drop functionality

I wrote ImageInvoker a little while ago which gets around the need for lots of techhies logging into the DS console for day-to-day tasks. Imaging is done client side by booting into Linux automation and choosing the desired job from an image menu.

This only works however for imaging at the desk so to speak, but completely eliminates the issue of techies imaging the wrong computer!

http://www.symantec.com/connect/articles/imageinvo...

aaah. can you give me some real time examples when one can use image invoker?

1. Connect it to the network
2. Boot into Linux Automation (PXE, or USB boot usually for us)
3. Enter Imaging Menu (press i)
4. Select the imaging job you want
5. Enter in the name you want the computer to have
6. Watch it start imaging and move onto the next one. 

and i still need to add the pc's macadres into altiris deployment??

and what about the deployment structure; we got groups for every site and for desktop/notebooks. And how do you define a computername? from within imageinvoker?

 Hi,

By default ImageInvoker allows you to change the name of the target computer before imaging. The default computer name is,

• For computers which already exist in DS, the name of the computer in the DS Console
• For computers not existing in DS, the default name is the computer's serial number

As for DS console group structures, re-imaging computers using ImageInvoker will preserve their place in the structure. This is one of the features which sets it apart from forcing Initial Deployment (which moves computers back into the console root).

If you image computers which aren't in the DS Console, these will however appear by default in the root. To cater for this, we implement a policy for a DS Administrator give the console a tidy-up each week, so that new PCs can be filed into their appropriate group.

Kind Regards,
Ian./