Jump to content

Braingears

Members
  • Content Count

    81
  • Joined

  • Last visited

  • Days Won

    9

Braingears last won the day on July 17

Braingears had the most liked content!

Community Reputation

18 Good

4 Followers

My Information

  • Agent Count
    1500+

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I like it! You can very easily add the Function: ExtraData Set to the script so that it's automatically populates these EDFs for you. I would also add the expiration date for reference as well.
  2. @Mark Hodges There is a Script Log that displays the token when run. You can see and verify the tokens in the `InstallerTokens` table. The logging is also enabled on line one, so you should be able to see if every line was executed within the Script Logs. @Jacobsa Perfect. Make it work for you, and make it fit YOUR needs.
  3. It's assumed that the domain controller with FSMO roles attached would have the module by default. Please continue to test, if I need to add it, I will.
  4. Can you confirm if the .bat file is located in the SYSVOL Share as expected?
  5. Thanks to @DeWaynePeden for discovering a Token link bug. If you've downloaded this script prior, it's time to update. The new Token requirement nullifies the previous versions. I've removed the duplicate links. Use the links in the first post.
  6. @DeWaynePeden Thanks for the update. I've updated the script. Remember to update the GPO's .bat file. You can also 'Remove GPO' then 'Create GPO' to replace it after the script has been updated.
  7. Just so I understand. If you copy the URL into your browser, is it downloading a .BAT or .MSI?
  8. Once a token is created, you can use that same token for all Clients & Locations by simply changing the LocationID in the Powershell when executed. Previously the MSI was hard coded with LocationID=1. Now with the token, it will embed the MSI with the selected LocationID when is was created with the script, although the Powershell will assign the LocationID upon execution.
  9. Although I did not limit the number of months that you could enter, it's my personal recommendation not to exceed 1-2 years. Fortunately every time you use the links provided it will download the most up-to-date agent installer to be used. On the other hand, I have no idea what CW Automate developers plan to do or change in the future. None of us expected the typical generic installers would be locked down, and they might also make changes to the Deployment.aspx or `installertokens` table in the future. The official web portal only creates these tokens for 24 hours and clears out expired tokens in a nightly routine. Time will tell...
  10. Will generate ticket with Windows MSI, Mac, and Linux installers with tokens. • Enter # of months until the token expires. If left blank, the default is 12 (enter number only) • Enter alternative LocationID. If left blank, it will default to the Location where the script was executed from. • Enter Email address if you want to receive an email with all of the links. • Additional PowerShell and Mac Terminal Scripts will be included to make deployments easier. Due to the latest vulnerability patches, we can no longer download any Automate Installer that is not downloaded with an Authenticated Automate User. With the help of Darren White creating the Token Generator, I've created Automate scripts to easily create the Automate Installers with Tokens and will currently create tokens from 1 month to years. I've also updated the "Agent Deploy - Create GPO on DC" to create a "CW Automate Agent Deployment" GPO and automatically link it to the root of the domain (optional parameter). **Caution** This not a ConnectWise Automate blessed method of creating installer tokens, and the the developers could change the installer methods just like the did with the previous installers at any time. This is also true for the tokens themselves in the `installertokens` table. Agent Deploy - Generate Installers with Tokens.xml Agent Deploy - Remove GPO on DC.xml Agent Deploy - Create GPO on DC.xml
  11. I have replaced the "Agent Deploy - Create GPO on DC" script due to the vulnerability lock-down of Deployment.aspx. If you've already used the GPO Creator: Import/Update both scripts. Run "Agent Deploy - Remove GPO on DC" on the existing client's Domain Controllers to remove the existing "CW Automate Agent Deployment" GPO. Run "Agent Deploy - Create GPO on DC.." on the Domain Controller with PDC FSMO Role. This will create a new GPO. You can enter the Token's expire time (in Months, default = 12 Months). You can automatically link the GPO by enter "True" in the script parameter when you run it. If you do not enter "True", it will create the GPO, but not link it to the domain or OU. You must do this manually. Review the ticket that's generated and GPO on the server to ensure everything working as expected.
  12. I have updated the Github Install-Automate and Push-Automate scripts to accept tokens. I have also created an Automate Script that will create tokens (from 1 month to several years) and automatically create a ticket and email (optional) with all of the links pre-created. I will continue discuss the PowerShell Module here, although I will maintain the new Automate script in a new thread. Agent Deploy - Generate Installers with Tokens.xml
  13. Try testing the install string from the command prompt from one of the computers to ensure that it's running unattended. https://quickbooks.intuit.com/enterprise/customer-resource-center/installation-and-setup/ https://eddiejackson.net/wp/?p=4508
  14. Use the Web Portal to view the most accurate compliance percentages.
  15. The installation is using the NT Authority\System account by default. It's not Run as Admin
×
×
  • Create New...