Jump to content

danialbulloch

Members
  • Content Count

    90
  • Joined

  • Last visited

  • Days Won

    13

danialbulloch last won the day on October 8

danialbulloch had the most liked content!

Community Reputation

27 Excellent

1 Follower

Recent Profile Visitors

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

  1. I actually do script the VPN connection for most of our clients, so it isn't a major issue for us, one reason I haven't spent the time looking into solutions.
  2. View File Offline Domain Join This is the latest version of my Offline Domain Join script for ConnectWise Automate. This script will join a computer to a domain with no network connection to the domain controller. Automate finds the "Domain naming master" server for the client, generates a file, transfers the file over to the target agent, then uses it to do a domain join. The script can also work when a computer is in the same network as the domain controller. We use it for all domain joining. If a client has multiple domain naming masters the script will
  3. Version 1.0.0

    23 downloads

    This is the latest version of my Offline Domain Join script for ConnectWise Automate. This script will join a computer to a domain with no network connection to the domain controller. Automate finds the "Domain naming master" server for the client, generates a file, transfers the file over to the target agent, then uses it to do a domain join. The script can also work when a computer is in the same network as the domain controller. We use it for all domain joining. If a client has multiple domain naming masters the script will automatically fail. If the target computer is on a domain or a
  4. No kidding. Didn't consider that, but yes, if you had exclusions setup for the update process, those are now invalid. Or any system that might have had to do with the update system. Although you really shouldn't have AV exclusions pointing anywhere a standard user can write files. Again, without telling us, anything could change and we wouldn't know until we investigated a system breaking.
  5. I am posting this as a reminder to everyone here, keep your automate up-to-date. Connectwise has decided to include security patches in the monthly updates, without notifying anyone. As a result, what may seem like a lackluster feature update may include critical security updates. An example I just published is a privilege escalation bug that was in all versions of Automate below 2020.8. It was patched in 2020.8 after I reported it, but they didn't announce it in any way. They didn't even tell me it was fix, I had to find out through testing. Now, this isn't a critical one, it expands acc
  6. @ckochosky Try restarting the control center. It's a common problem when importing scripts that come with EDFs.
  7. Check the command history of the computer you are running it on. If you open the script and click the debug button you can step through it step by step, watching what it does, and referencing the commands on the computer to see if it does things right. While also hand verifying for things like downloading the ISO.
  8. So I never saw this post when I made my offline domain join script, but check mine out @KyleChx. It does work. Feel free to post there if you have any questions.
  9. @srogersOne issue I see with your logic is that you are setting the EDF before verifying the password. If the password fails to set properly, you are updating the EDF anyways, so the wrong password will be set. I'd recommend doing a variable check on the output of line 10 to make sure it says "Credentials Correct". Any other return should be counted as a failure, and not update the EDF. Also, check the command history of the computer you are testing on, see what the results are of both of the commands I gave.
  10. Sounds like the powershell is failing to even run. Make sure the computer has the latest version of powershell installed(PS5.1). I'm not sure what is required, but it does use a bunch of powershell, and I can see that causing a problem. You can also check the target machine's command history and see what the powershell command returned directly.
  11. @ObsidianJason There are logs of the install attempt stored in C:\tne\temp\ (unless you changed the default folder). That can be used to help debug any failures you have.
  12. If you are on hosted, you are going to have to put the file somewhere else. You can change the download line in the script to be the other download option, and update the address to have the domain on it(and possibly folders). That's what a lot of people do when they are either on hosted, or don't have a lot of bandwidth to spare on their server.
  13. On your Connectwise Automate server. Where exactly? I cannot say, that depends on your setup. If you cannot access the ltshare, you could preload it on client networks and put it on a local network share.
  14. Perhaps try restarting the CWA server? Someone else suggested it started working after that happened(they restarted it for unrelated reasons).
  15. That's odd, must mean that the script didn't create the EDF properly. Try reimporting it.
×
×
  • Create New...