Jump to content

Anders Bermann

Members
  • Content Count

    10
  • Joined

  • Last visited

Everything posted by Anders Bermann

  1. 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.
  2. 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
  3. 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.
  4. 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.
  5. 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!
  6. 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.
  7. Does anybody know anything about this? I'm kinda at a loss...
  8. 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.
  9. 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...