-
Notifications
You must be signed in to change notification settings - Fork 2
MSP_Config
CJ edited this page Feb 11, 2019
·
5 revisions
MSP_Config "strHDR" "strCHG" - Designed to update the MSP Backup 'config.ini' file in a semi-automated fashion, currently can only add internal strings.
- Current Validation : [Validated]
-
Arguments : 2, Required 2
- "strHDR" - REQUIRED - String, Identify which Header ("Section") of 'config.ini' file to modify
- "strCHG" - REQUIRED - String, Line to add to 'config.ini' file
-
Use :
-
Scheduled Task :
- Create new "Scripting" scheduled task in N-Central, give the task a meaningful name
- Set RMMTech credentials, select "MSP_Config" for "Repository Item" field.
- Select the devices to target for script execution, set an appropriate schedule ("Now" is default)
- Configure Arguments "strHDR" "strCHG" accordingly, replacing everything in quotes with the appropriate values; for more information on the 'config.ini' file and a list of configurable "Internal Strings" and their possible values, please see MSP Backup Config.ini and MSP Backup Misc. Settings
- Set notifications as desired and run the scheduled task. Will write output to "C:\temp\MSP_Config.txt"
-
Command Prompt :
- Right-Click MSP_Config.vbs, select "Properties"
- Ensure script is not blocked;
- If you see a button in the lower right labelled "UnBlock", click this button to unblock the file.
- Run Command Prompt as Admin
- Enter "cscript.exe //nologo \MSP_Config.vbs "strHDR" "strCHG""; for more information on the 'config.ini' file and a list of configurable "Internal Strings" and their possible values, please see MSP Backup Config.ini and MSP Backup Misc. Settings
-
Scheduled Task :
-
Automated Functions :
- Parses MSP Backup 'config.ini' file, locating "Section" to modify via strHDR
- Parses MSP Backup 'config.ini' file, if strCHG is not found, will add strCHG as the last line under the specified "Header"
To submit a new Bug Report, please click here.
-
- When submitting a Bug Report, please make the Title according to this standard : "[Script or Project] - [Title]"
-
- Be descriptive and clear about actions, conditions, and details of the issue. Answering What? When? Where? will go a long way to assisting with answering Why? and How? and providing a solution. Most everything here creates a logfile automatically when ran, so please include these logs and any screenshots if possible, attempt to fill out all relevant sections of the Bug Report before submitting!
-
- Be courteous and understanding; if you have submitted a Bug Report for an issue, please be patient and wait for communication or updates. Flooding Issues with duplicate / harassing requests will not be tolerated!
To submit a new Feature Request, please click here.
-
- When submitting a Feature Request, please make the Title according to this standard : "[Script or Project] - [Title]"
-
- Be descriptive and clear about intent and expectation of feature requested
-
- Be courteous and understanding; if you are told a request will not happen, accept this
To submit a General Request, please click here.
-
- When submitting a General Request, please make the Title according to this standard : "[Your Name] - [Title or Request]"