Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Aenabs last won the day on November 11 2019

Aenabs had the most liked content!

Community Reputation

1 Neutral

1 Follower

My Information

  • Location
  • Agent Count
    < 500 Agents

Recent Profile Visitors

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

  1. Hi @SteveYates @DarrenWhite99 Sorry if I am going over old topics, however I am looking for something very simple. A script to set sleep settings on a device to never. We want to run this script on individual devices rather than across our estate. Do you happen to have a script or guide that can achieve this? Kind regards,
  2. @SteveYates Thanks for your reply. I agree with you however due to security concerns I was wondering if there is better way to maintain the service accounts used by Automate. When I use the .\username format on a dc it still tries to login as Domain\username. I think we missed a trick here, we use our domain admin details as the Service Account for Automate. I might look into creating new domain admin service accounts to be strictly used by automate. Thanks
  3. @Dew Ok managed to get it to work.
  4. @Dew Hi Dew, I am looking for an automated process to retire scripts very similar to what you have setup. I would like to retire devices not seen online for last 90 days for specific service plans(I have EDF for this) and also ensure the process inputs the reason into automate of why it was retired for auditing purposes. Is there anyway you can search your script for me to have access to it?
  5. Hi Guys, Trying to get some ideas and thoughts on how everyone has there CW Automate Deployment & Defaults - Login to use for Administrator Access configure. Fairly used to CW Automate after 1+ year plus using the system and I am trying to make minor improvements in our CW Automate environment. This post is to do with using domain admin details in the Deployment & Defaults - Administrator Access. I would like to use local admin credentials instead of Domain admin credentials in the Deployment & Defaults - Administrator Access. This works great for our cloud based tenants no on-site servers, however I am struggling to find an ideal solution to facilitate the use of local admin details for clients with Domain servers. As you might know DC's cannot have local admin details configured on the server so finding a one fit all solution has been a pain. I thought about creating a new location for each client and have the servers in there or the DC but that might mitigate the issue of domain admin used for all devices, however my main aim to remove domain admin details from Automate entirely. Looking forward replies and ideas. Thanks
  6. @Matthew Mclaughlin Hopefully the changes help, for me it did help for sure. I believe with new ISO I’ll have to repeat the process again. I’ll download the new ISO directly to our client servers and stage it for download to workstations. Regards
  7. Hi @Matthew Mclaughlin How have you got on? I have made the required modifications and the script is now working as i wanted. Great to hear its working. I avoided the whole cloud based issue by using a desktop on the client side to host the ISO. That worked fine. I didn't have to split the script since I have the ISO staged on each client side it doesn't need to download the file from the internet for each client. I also changed the format of the script. Checks for free space on workstation to download ISO from cache location 5GB Checks for free space on the workstation to mount and run the workstation 10GB Downloads the file to the cache directory Checks to see if user is logged in and if user is logged in - (POP-UP message to state windows feature update is running in background with 90 sec count down) If user not logged in proceed to next step Mounts ISO and installs file Checks to see if user is logged in and if user is logged in - (advise user update has been applied and reboot required, count down to reboot device or postpone for 2 hours) If user selects postpone in 2 hours the reboot script is triggered prompting user to reboot Hope that helps, PS I never built in any checks to see if its downgrading Windows Versions as most if not all our clients are on 1809. Thanks
  8. Hi @Matthew Mclaughlin How have you got on? I have made the required modifications and the script is now working as i wanted
  9. Hi @Matthew Mclaughlin Apologies for the late reply, I used the Location Cache Directory for our clients with servers. I configured a shared folder on the client server\workstation which is always online. Shared the folder with read access only so no domain details required. Set the folder location as the cache share in Automate - client location. I then have a copy file command using PS to copy file from cache directory to device. I also tested it using LT copy command and it copies the file from the cache to the specified directory on the agent. For clients without servers or workstations that are always online - I am looking to script a download from Onedrive or any other storage platforms. Only downside to the script is the end user is not notified when the update command is completed. It automatically reboots the device. I am now looking for a way to modify the script to prompt the user to reboot when completed.
  10. Hi @Matthew Mclaughlin Apologies for the late reply, I managed to get the script working (Windows 10 - Install Feature Update). I changed the setup of the script to perform all checks before prompting the logged in user. It was the other way around initially, It prompted the users initial and then did drive space checks. At the moment I have the script pointing to a shared location on the network to download and copy the Windows 10 ISO to the local device and running the install. I have been in touch with Automate and they advised me the Cache function in Automate does not work and they are currently trying to fix it.
  11. Hi @Matthew Mclaughlin I am very interested to see if or how you manage to get this sorted. I am in the process of looking for a way to achieve the Version upgrades for more than 200 endpoints. Interesting I see you are trying to achieve this by using a server location I am trying to use it by using the Cache function in Automate. However we do have some cloud clients who would have the suffer the brunt of having the exe downloaded to each device.
  12. @MGreenThanks for your response. Sorry it took a while to respond back. What you advised worked and I have actioned it, however I made a slight change to make it less persistently painful on the device processors. 1) I created a search function and limited it to the location, laptops and online devices. 2) Created a group under the client and applied the search to populate the devices in group. Devices in group is limited search. 3) Created a script to copy the exe file across to the devices and linked script to the group. 4) Created a remote monitor for the group to run the exe on the device and if it has VPN installed take no action. If VPN is not installed the remote monitor has an alert to install the VPN client using the script. Early days but seems to be all working. Important part there was to limit the group to online devices. Thanks once again.
  13. Sorry for the late reply @MGreen The EXE returns the following results; IF already installed Exe_output - Displays VPN name (LOGGED-IN User RAS Phonebook) Exe_output1 - Displays VPN name (GLOBAL RAS Phonebook) IF not installed Exe_output - Displays OK (LOGGED-IN User RAS Phonebook) Exe_output1 - Displays OK (GLOBAL RAS Phonebook)
  14. Thanks for your reply @MGreen I have a script (VPN Install) that checks is not automated. It is triggered manually on devices by technicians. The function of this script is to check if VPN native adaptor is installed with a specific name eg Work VPN. If the VPN is installed, the script goes on to delete the VPN adaptor on the device and reinstalls the VPN Likewise if the VPN is not installed, the script goes on to create a new VPN adaptor with name Work VPN. This script works a treat and allows our technicians to remotely deploy & update VPN adaptors for our clients. However I am trying to make it smarter. The script has an EXE it downloads & runs to check if a VPN adaptor is installed. Like I mentioned above if the VPN is not installed it proceeds to install the VPN. I am trying to run this EXE against 80 endpoint periodically so it catches any endpoint without a VPN adaptor and puts this device into a group (VPN Not Installed) where i can action the full script to install VPN on any endpoint(s) in the group. I think your suggest about a remote monitor might work however i am struggling to see how i can run the exe periodically e.g weekly, to check endpoints and put these endpoints into a group where i can trigger the script inside Automate to install the VPN. I hope this makes sense? Thanks
  • Create New...