Deployment and Imaging Group

Is it possible to password protect task in the Intial Deployment so that jobs could not be run on accident by end users?

If this is not possible can I put in a feature request for that as option in a release down the line.

To create an enhancement request, simply create a Connect Idea so that the community can then vote on it. 

Also, if you have a good Symantec Sales contact, you can have them talk to the Product Manager of that product so that they can create an Accept360 ticket directly. 

Another route is via your Support contact, especially if you have a BCS contract. 

The ideas section is an absolute waste of time. 

Yeah but Microsoft system Center allows for password protection of jobs.

We use DS6.9 and ImageInvoker to gain this functionality (it has simple password and and AD authentication & authorisation support). This means we use DS6.9 to deploy machines which we then manage with 7.5

Password protection in the 7.x DS world has gone in circles since the 7.1 and I'm not sure there is a will to implement it given it's already huge worklist.

Kind Regards,
Ian./

This can be easily done by putting a PowerShell or any script task which can do authentication to your AD.

Or you can just a put a script task to ask for a PIN or a generic password.

Then you fail your Initial Deployment Job if auth was not successful.

Hope this helps.

I have a simple password script I can use.  Do you have an example of how I could fail the intial deploy if the password is not given?

You make your Job to fail if any task fails - tick the box on the user interface on Fail Job if any Task fails!.

Alternatively you can use conditions in your Job.

You make your auth script to exit 0 if auth is successful and exit with 1 if not or cancelled or timeout perphaps...

Then in your Initial Deployment Job go to New / Condition - depending on exit code from your script task adjust further actions.

Should look something like this below: