Jump to content

Anders Bermann

Members
  • Content Count

    18
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Anders Bermann

  1. How do you setup 'line 4'?! I assume, it's a Function 'Variable Set'. But what's the Set Type? Parameter? etc...? Thanks for any help...
  2. Hi all, I don't know if this has been asked and answered already (used the search function, but no luck...). I wanted to know: Is there any way to create line-breaks in a Popup Message box? The Console Show Message function ... Thanks for all help.
  3. Thanks for this one. How do you remove the trailing line feed and line break/return? I think that's what my problem is...
  4. Thanks for this. But I cannot unfortunately get it to work... The log is here: The Script(6571) failed in the Then section at step 36. The reason: ERR Download File Failed Script: S6571 - Starting at Server Time: Friday, May 29, 2020 4:39:02 PM IF F1 T: 1.4181753 L1 F17 Script (P1): 6563 Delay (P2): T: 1.4181753 Start S6563 IF F1 T: 1.4211694 L3 F135 Command (P1): '(Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion" -Name Release...' T: 1.4211694 L4 F20 SetType(P1):1 Parameter(P2):2004 VariableName(P3):WindowsVersion T: 3.4263059 L5 F80 EdfId (P1): 966 TargetId (P2): 2023 Value (P3): 2004 T: 3.4263059 L6 F29 Message (P1): Windows version is: 2004 T: 3.4273154 End S6563 L2 F20 SetType(P1):1 Parameter(P2):10 VariableName(P3):requiredSpaceGBWindows T: 3.4283085 L3 F17 Script (P1): 6566 Delay (P2): T: 3.4283085 Start S6566 IF F1 T: 3.4313083 L1 F235 T: 3.4313083 L2 F29 Message (P1): Newest Win 10 build is: 2004 T: 7.4397355 End S6566 L4 F17 Script (P1): 6477 Delay (P2): T: 7.441677 Start S6477 IF F1 T: 7.4436777 L2 F235 T: 7.444678 L3 F29 Message (P1): OS language is: da-DK T: 11.4558989 End S6477 L5 F70 Value (P1): @OSTargetVersion@ Comparer (P2): 3 To (P3): Jump (P4): :OSTargetVersionOK T: 11.4578963 L8 F139 Note (P1): :OSTargetVersionOK T: 11.4578963 L9 F29 Message (P1): OS target version set to: @OSTargetVersion@ T: 11.4578963 L10 F70 Value (P1): WindowsVersion Comparer (P2): 7 To (P3): @OSTargetVersion@ Jump (P4): :NoUpgradeNeeded T: 11.4589048 L11 F29 Message (P1): Restarting LabTech service... T: 11.4589048 L12 F235 T: 11.4598955 L13 F115 User (P1): T: 15.4651002 L14 F115 User (P1): T: 15.4660986 L15 F139 Note (P1): :BelowTargetVersion T: 15.4660986 L16 F53 T: 15.4660986 L17 F29 Message (P1): Checking if there is enough free space to run the upgrade. T: 33.471692 L18 F20 SetType(P1):1 Parameter(P2):'SELECT CONCAT(drives.letter,':...' VariableName(P3):sqlToRun T: 33.473675 L19 F117 Sql (P1): 'SELECT ROUND(free/1024) FROM `drives`, computers WHERE drives.computerid = computers.compu...' T: 33.473675 L22 F139 Note (P1): :ContinueInstall T: 33.4746694 L23 F114 File (P1): 'C:\WindowsSetupFolder\setup\se...' Check (P2): 0 Jump (P3): :BeginInstall T: 33.4746694 L24 F114 File (P1): 'C:\WindowsSetupFolder\Windows1...' Check (P2): 0 Jump (P3): :upgrade_continue T: 35.4766877 L25 F29 Message (P1): Creating folders T: 37.4805116 L26 F154 Folder (P1): C:\WindowsSetupFolder T: 37.4814735 L27 F29 Message (P1): da-DK T: 39.483734 L28 F17 Script (P1): 6567 Delay (P2): T: 39.4847343 Start S6567 IF F1 T: 39.487728 L1 F235 T: 39.4887265 L2 F29 Message (P1): Path is: Win10_2004_da-DK_x64.iso T: 43.5018379 End S6567 L29 F29 Message (P1): Filename: Win10_2004_da-DK_x64.iso T: 43.5038292 L35 F29 Message (P1): Downloading da-DK ISO T: 43.5038292 L36 F28 Local (P1): Windows10\ISO\Win10_2004_da-DK_x64.iso Destination (P2): C:\WindowsSetupFolder\Windows10.iso T: 43.5048289 What's interesting is, that the L36 Source and Destination is (or seems to be) correct... The File Download dialog is looking like this... Is there any issues with this approach?
  5. Hi all, Is it possible in Automate, in a script, to include a variable in the Download File ? I know it's possible to do in the Destination - but is this possible in the Source? My problem is, that I have 3 ISO files, which filename is dependend on the language setting on the target OS. I have found a way to extract the base language information in PowerShell and through that build an ISO file name, which reflects the various language setting. However I cannot set this up in the Download File in the script in Automate. Does anyone have any idea of this, or is this simply not possible?
  6. Hi all, I don't know if this has been explained before (or if this is a stupid question), but I've been searching around, and couldn't seem to come up with - well at least a straight answer. How do you create an Agent Template and how do you apply it to a localtion-only (or a sub-location)? For instance: I have a client, which has locations split into 4 different sub-locations in Automate. I'm looking to apply a different Tray Menu for each of the 4 locations (and 1 which everyone is getting). How do I create Agent Templates, which are limited in scope, to only 'hit' specific locations or clients? Hope that was somewhat understandable... Thanks in advance!
  7. Interesting idea... You did this manually? As far as I know, there's no command switches for Media Creation Tool? I have run into a multitude of problems related to upgrading Windows 7 computers to Windows 10... Typically it fails with an error (Critical_Process_Died) and then crashes, reboots and reverts the changes and I end back up with Windows 7... Kinda annoying actually... So far, I haven't found a solution - or any common denominator. They're all Lenovo machines and software-wise they have most in common - with slight differences.
  8. This is only for Lenovo. Within the webresponse variable, there's a value which is being queried, which makes up the warranty end-date. Basically I query two variables instead of one. After exporting the webresponse as XML, I analyzed it, and found that there are two variable (depending on whether there's extended warranty or not) being filled. The first one is: $webresponse.wiOutputForm.warrantyInfo.serviceInfo.wed | select -first 1 That one, is the factory warranty. But after looking at the XML file, I found that there's another one too. That one is found by querying a bit different: $webresponse.SelectSingleNode("//mEndDate") | Select-Object -ExpandProperty `#text After finding this, I realised, that the mEndDate is only set, if extended warranty is present. So I made a simple if-else statement, to check for $null value: $WarrantyEndDate_Expanded = $webresponse.SelectSingleNode("//mEndDate") | Select-Object -ExpandProperty `#text if ($WarrantyEndDate_Expanded -eq $null) { $WarrantyEndDate_Expanded = $webresponse.wiOutputForm.warrantyInfo.serviceInfo.wed | select -first 1 } I have uploaded a text file for the updated Function: Get-LenovoWarrantyInfo. When updating the original script, just replace the function with the modified one The only changed made, is written above. Thanks again for your work. Updated_Get-LenovoWarrantyInfo.txt
  9. I seem to have fixed it, by some trial and error. Made some modifications to the powershell script, so it catches both extended warranties AND non-extended (purchased-extended) warranties now. This is only for Lenovo computers. Thanks again, @DarrenDK for this.
  10. Thanks for the suggestions. When you say, removing the wireless card - do you mean, open the laptop up, and removing it, or 'just' disabling it from the BIOS? I'll give the suggestions a try and report back - thanks.
  11. I get a weird error when trying to upgrade Windows 7 SP1 to Windows 10 1903. I've attached two screenshots of the errors. The first one comes, as a BSOD when approaching around 90% in the Working on Updates part of the installation. Afterwards, it reverts to Windows 7, and upon logging in, it comes with the second attached screenshot... Any ideas of what's wrong? I've tried a gazillion things... *SIGH* It says "Critical Process Died" Here it says: 0xC1900101 - 0x4000D Installation failed in the SECOND_BOOT Phase with an error during MIGRATE_DATA operations. Have tried everything from SFC /SCANNOW to uninstalling and/or updating drivers/software/windows updates etc... I cannot fathom why this happens... Any ideas would be welcome. Thanks in advance!
  12. Amazing work! @DarrenDK When running this script, I get warranty information, which doesn't coincide with the information, when making a lookup at Lenovo - or at least, there some warranty missing. For example, when looking up my own computer with serial PC0A51B2, I get the following information from the script: Purchase date (dd/mm/yyyy): 18/02/2016 Expiration date: (dd/mm/yyyy): 03/04/2017 However when looking up the computer at Lenovo, it says: As you can see, if there is extended warranty purchased for the product, it's missing in the data received from the script... the script seems only to be able to extract the factory warranty. We have other computers, which have 3 years factory warranty, but have 2 years additional warranty purchased. This 'extended' warranty is not received from the script... Can something be done about this, or is this 'just' a limitation? What data do you receive from the REST API request? Thanks again.
  13. Does anybody know anything about this? I'm kinda at a loss...
  14. Thanks for getting back to me, Darren I believe the script is sending the mail? It's using Send-MailMessage in Powershell with an encoding flag.
  15. Hi all, I just recently starting discovering the world of scripting in Automate (I have some experience in scripting and programming outside of Automate, though) I have a powershell script, which checks for password expiration in an AD. It then sends an email out, to all users, who's password expire in a set number of days or less. The script generates the email within the script. When executing this script in Powershell ISE in Windows, the emails arrive and are looking as intended. All letters and characters are looking fine. I have set an -Encoding flag to UTF8, since the emails are in Danish. If I set the -Encoding flag to ASCII, the special characters, show up as '?'. When set to UTF8 - they are correct. When executing the script in Automate, using Execute Script, the script executes fine and I receive the same number of emails, with the same content - expect the emails which contains special characters are not looking as they should. You would typically see this type of thing, if there's an encoding error of some kind... I don't know what's happening... is there some kind of special encoding that Automate is using or does it default to another encoding? Hope I'm making sense here... Thanks for all help and suggestions.
×
×
  • Create New...