Associate scripts with a customer(s), or per customer scripts
You may have scripts that contain information that pertains to only a single customer. In order to prevent engineers from running those scripts potentially on another customer, it would be incredibly helpful to be able to do either:
A. Associate scripts with a customer(s)
B. Have scripts that can only exist with a given customer
An example of a use for this: Deployment of an external or otherwise unsupported security product that requires a customer GUID that is supplied as an argument for an MSI installer. This feature would prevent a mismatch for this scenario from occurring.
TDR Helpdesk
shared this idea
-
David Yoder
commented
Other scenarios include:
Installing applications that require company specific information. Examples would include things like backup agents, anti-malware agents, Outlook extensions, etc. Associating scripts with a customer would eliminate the chances of incorrectly installing the wrong thing, and would really help to organize the scripts.
-
TDR Helpdesk
commented
Other scenarios include:
Microsoft SharePoint deployment where a TenantID, SiteID etc. are required. Being long GUIDs its not feasible to have engineers copy paste these every time. Instead scripts are made for each customer with them hard coded.