Jump to content
[[Template core/front/profile/profileHeader is throwing an error. This theme may be out of date. Run the support tool in the AdminCP to restore the default theme.]]

kelliott last won the day on January 4

kelliott had the most liked content!

Community Reputation

7 Neutral

My Information

  • Agent Count
    2000 - 3000 Agents

Recent Profile Visitors

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

  1. Yeah, it needs updating for 2019, just haven't had time to do that as of yet.
  2. Well, I mean you and I were going to test it out. When I was asking in slack if others tried it, no one had any input so I think we're on new ground with it.
  3. Suspend script if too many are active View File This script is used to suspend any other scripts that may be running by the same name if too many of it are active on the same client at once. This has the practical effect of sleeping a script, recording it's place in line and checking again in 30 seconds to validate if it's time to try again. To use it, set a variable in your script of MaxRuns to however many you want to run at a time, add a 15 second sleep step then use the script run function to call it. This allows it to effectively build the queue and then process them as they come in. Once it's time for that one to resume, it will return to your source script and continue. Special thanks to @danialbulloch, who without his help this script would have not happened. He was both the inspiration and the source of the SQL query that makes it all work Submitter kelliott Submitted 01/04/19 Category Scripts  
  4. Version 1.0.0

    9 downloads

    This script is used to suspend any other scripts that may be running by the same name if too many of it are active on the same client at once. This has the practical effect of sleeping a script, recording it's place in line and checking again in 30 seconds to validate if it's time to try again. To use it, set a variable in your script of MaxRuns to however many you want to run at a time, add a 15 second sleep step then use the script run function to call it. This allows it to effectively build the queue and then process them as they come in. Once it's time for that one to resume, it will return to your source script and continue. Special thanks to @danialbulloch, who without his help this script would have not happened. He was both the inspiration and the source of the SQL query that makes it all work
  5. There's a change needed to the offscrub.vbs files. It seems MS missed that one when they published the initial release. @Leapo gave me good feedback via slack (this is the easiest way to reach me), just need to find time to correct the offscrub files and republish it. I've added a quick change to the offscrub files. I haven't run into that SKU in the wild, so if someone could replace their copy of this file with my new one and let me know if it resolves the issue I'd appreciate it. Remove-PreviousOfficeInstalls.ps1
  6. Didn't @jundis make a functional free one? I know he did for Slack for sure.
  7. Wait, I was third? How. I was sure my ramblings would have kept me a solid #1.
  8. See third post for newest change log and top post for newest file. Reviewed script and identified what @Jacobsa was referring to. Thanks for spotting the bug!
  9. @MGreen Hasn't been any changes in a bit to it, been solid for me for the deployment I wrote it for. We did run in to about 10 that it failed on (out of 200ish) due to an issue of a stub version of office being on there On those ones I split out the install into yet another script, and then submitted to those to install and get them caught up. @Jacobsa - were you having it look for an additional set, or is it the validation part that failed for you? @timbo83251 yeah, I did that to avoid problems in other spots. It extracted clean, but in the end it's a generic installer anyway.
  10. Due to the changes, please make sure you replace ALL files with the updated version. Many have had changes and it will not work if several are not replaced. Changes: 6-28-18: - Corrected issue with 2016 not being removed correctly - Corrected issue with language locales not being detected at all - Created secondary removal type, one will remove all office, including Visio & Project, the other will only remove the main office suite. Ensure you pick the correct one for your deployment. --- To pick what version you want, change line 67's source file from "Remove-PreviousOfficeInstalls-MainProductOnly.zip" to "Remove-PreviousOfficeInstalls-All.zip" - Created additional deploy scripts for presets - Created non Shared computer activation version of template - This version is preconfigured in the "All Apps" version of the script - Enabled process logging to c:\windows\temp\offscrub.txt - Corrected issue with one office installer extract going to an incorrect folder 8-30-18: - Corrected check for completion, previously a * was used to close out the Office 365 detection, this was incorrect, and was correctly changed to a %. Credit to @Jacobsa for catching this.
  11. Corrected issue with some versions of offscrub being coded to work from system32 and no copies of the scripts existing there Added changelog to the Readme (with dates) to ensure you can easily see if you're using the latest version.
  12. I have just completed a office purge and replace with 365 script that I feel may be useful to the wider community. This script will determine the version installed, purge it and then install a fresh copy of 365 in "Shared Computer Activation Mode". If you don't want or need shared computer activation mode, edit the file configuration.xml in the Office-365-business-retail.zip and remove these lines <Property Name="SharedComputerLicensing" Value="1" /> <Property Name="SCLCacheOverride" Value="1" /> <Property Name="SCLCacheOverrideDirectory" Value="%userprofile%\microsoft\" /> To change edition installed, replace the product ID with one of the following: Office 365 plan Product ID Office 365 ProPlus Office 365 Enterprise E3 Office 365 Enterprise E4 Office 365 Enterprise E5 Office 365 Midsize O365ProPlusRetail Office 365 Business Office 365 Business Premium O365BusinessRetail Office Small Business Premium O365SmallBusPremRetail Delete any excluded apps you want to be installed from the block below <Language ID="MatchOS" Fallback="en-us" /> <ExcludeApp ID="Lync" /> <ExcludeApp ID="Publisher" /> <ExcludeApp ID="Groove" /> <ExcludeApp ID="OneDrive" /> <ExcludeApp ID="OneNote" /> </Product> It also places updates on the "broad" track, so not bleeding edge, but not "disable all updates either" Office_purge_and_replace.zip
  13. No, that's the local account. This behavior was only observed on customers that had non domain computers. We're not on pilot, we're on v11.0.365 (patch 12)
  14. i have no idea what that image was or what database you are referring to. That's from the customer password manager screen, for one specific site, all those LTSVC accounts were created by MSP Accounts. Every site it touched is like that.
  15. Mr Rat - We pushed this out and found that when it does the local accounts, it does this. It can't be one per computer, because we have less computers on that site than that It;s going to really litter up our system if it creates a new entry every time it rotates passwords. Every single customer has at least 11 entries in their database. I'm hoping the most recent one is correct, but there's no way to know without testing them all.
×
×
  • Create New...