Skip to content

Conversation

@Robby-Swartenbroekx
Copy link

This version adds the CustomerID to the PartnerConfig.xml file. Giving you the possibility to change the CustomerID location from the GPO to the xml file. This way we can deploy the GPO to install the agent without user interaction and the xml file can easily be changed from within an AMP.
The old way to pass the Customers ID with the GPO still works and precedes the number given in the PartnerConfig.xml file.

This version adds the possibility to configure the CustomerID in the xml settings file instead of needing to pass it with the installer
@prejay prejay requested a review from rad-ryanc August 26, 2020 17:16
willrutherford and others added 3 commits October 15, 2020 16:44
If there was a CustomerID given through commandline, it was possible to run the powershell with an empty RegistrationToken. It's unlogic that you provide a CustomerID through commandline and the registration token through PartnerConfig.xml.
If one is given and not the other it now quits with an error instead of trying to run the powershell script
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants