Jump to content

Brendo

Members
  • Content Count

    9
  • Joined

  • Last visited

  • Days Won

    1

Brendo last won the day on November 20 2018

Brendo had the most liked content!

Community Reputation

2 Neutral

My Information

  • Agent Count
    100+
  1. Brendo

    Major Windows 10 Updates (Anniversary, Creators)

    I am able to open it without issue
  2. Brendo

    Major Windows 10 Updates (Anniversary, Creators)

    https://docs.connectwise.com/ConnectWise_Automate/ConnectWise_Automate_Knowledge_Base_Articles/Scripting%3A_Windows_10_Install_Feature_Update_Script
  3. Brendo

    Windows 10 / 8 disable Fast boot

    Along the same lines, I had previously created a script that disables Fastboot 'manually'; automatically is nicer though! Check for regkey -> If does not exist, create and disable -> If it does exist, check current value --> If on, turn off --> If off, exit Turn off FastBoot.xml
  4. Brendo

    Script to capture all screens

    I have an old script (attached) that still works in v12. It uses boxcutter (I believe is this: http://keepnote.org/boxcutter/) Script by Jeffrey Brock Import script, copy MSP folder to /Labtech/Transfer Multi_Screen.zip EDIT: just realise that script is the same as the one posted in the link above
  5. Brendo

    Major Windows 10 Updates (Anniversary, Creators)

    Yes, the original script has some issues with getting from the network at times It all works...but not in every setup (it is simplified after all). My original hope for posting was as a starting point for others to build off I do wonder about running the setup.exe through psexec in order to get around uac and where the instances start, but don't actually seem to be doing anything, I've just not used that before
  6. Brendo

    Major Windows 10 Updates (Anniversary, Creators)

    Here you go I'm lazy too, so you'll see the attached scripts may have some stuff edited out compared to the pictures Scripts -> Maintenance -> Patching Win10 Major Update.zip
  7. Just a simple script to install Creators Update on Win 10 machines. Feel free to post any changes you think others may find useful Usage: 1. Download iso using media creation tool (suggest using the dual x86/x64 option). Extract to a central location (eg. server) 2. Select script to run on machine/s 3. Enter path to the extracted iso in the parameters field when the schedule page appears (eg. \\FILE01\Install\Win10_C) Notes: - machine will reboot immediately after doing its prep (can be negated with /noreboot parameter) - it can take a while before the prep completes, you'll notice 4 setup*.exe files which should change their ram usage every now and then which indicates it's still running - current settings are for Creators Update - '/compat ignorewarning' argument used to bypass issues such as different install language - will also work with Anniversary Update and future updates. Just make sure to update the value on line 1 to appropriate build number - ensure appropriate permissions to network share for robocopy to do it's thing - not sure best approach when it comes to uac, but using Process Execute as Admin (Line 4) seems to do the trick - using 'as Admin' means that setup.exe is run using the credentials defined in client/location. Could also use 'as User' and define credentials -15063 (creator update) 16299 (fall creator update) Links: Media: https://www.microsoft.com/en-au/software-download/windows10 Arguments: https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/windows-setup-command-line-options Download: Post #6 NOTE: More advanced script by tlphipps HERE
  8. Currently going through this. Starting from scratch though. Manually transferring everything is taking a bit of time
  9. Brendo

    Office 2013 Key

    Office 2013 is difficult to retrieve product key from. Here are some examples/workarounds that I made to retrieve the last 5 digits (Microsoft Link). These are only simple as not worked with sql etc before. Still has a bit of error checking (commented out), but I'm just posting these in hopes that it's useful for someone to use or build upon (Scripts -> Software -> Microsoft) View Office 2013 Key Check Office 2013 key (last 5 digits). Logs the result to the Scripts page of the computer View Office 2013 Key - All Check Office 2013 key (last 5 digits). To be run against location. Lists computer name and key and is recorded in LTShare\ClientName on the LTServer I've also found that more recent Produkey app versions will show (and log) some of the versions of Office 2013/2016 and Win8 bios key If you replace the exe in LTServer\Transfer\Tools you also need to update the MD5 hash in Get Product Keys script (System Automation -> Product Keys) which is on the Globals and Parameters tab O2013Key.zip
×