Login to participate
Endpoint Management & Virtualization IdeasRSS
3
Centraly maintain the user account used to install applications
Jeremy Roberts
September 10th, 2009
3 Agree, 0 Disagree
We use a service account to install applications. This means we have to ennter the account details for every task in every job we create. Not so bad as you go alog but if we need to change teh password we will need to renter it twice for each task which can be a real pain if you have one or two hundred jobs with multiple tasks and also filters.
The account information used to join the PCs to a domain is stored in the system surely it must a simple task to store account information centrally to be used to install software as well, that way I would only need to make changes in one place to update these details.
Deployment Solution can
Deployment Solution can already help. While it would be nice to have a feature where we can set the install account once and define the "Run as user" and username/password as defaults, once the username/password HAS been entered, it's easy to change for all jobs. Just use the "Task Password" tab from the "Program Options" in DS to enter the username, old password and new password. Click "Update" and it's done.
I am still going to vote for this as well, as it would be nice to have a program configuration setting for "Run Script" and "Distribute Software" task defaults... and the username/password is a big part of that in our environment.
Would you like to reply?
Login or Register to post your comment.