gwblok/garytown

GaryTown Scripts, Downloads, Etc

garytown's Issues

Should be Microsoft 365 "apps" for enterprise% and not Microsoft 365 for enterprise% Line 178

garytown/Office365/o365_install.ps1

Line 178 in 8f51813

$O365 = Get-WmiObject -Namespace 'root\cimv2\sms' -Query "SELECT ProductName,ProductVersion FROM SMS_InstalledSoftware where ARPDisplayName like 'Microsoft Office 365 ProPlus%' or ARPDisplayName like 'Microsoft 365 for enterprise%'"

Winget

Afternoon So myself and a fellow worker are busy working on OSD Cloud and would like to find out if there is any possibility of incorporating Winget into the Task sequence.
At the same time is there away to speed up the curl download for the OS.

Cannot convert the "System.Object[]" value of type "System.Object[]" to type "System.Version".

Running the latest version of the detect script 23.3.9.1, receive the following errors.

Cannot convert the "System.Object[]" value of type "System.Object[]" to type "System.Version".
At C:\Users\xxx\Desktop\Update-DellApps-Detect.ps1:235 char:24

• ... InstalledDCU){[Version]$DCU_InstalledVersion = $InstalledDCU.Version}

•               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  

  • CategoryInfo : MetadataError: (:) [], ArgumentTransformationMetadataException
  • FullyQualifiedErrorId : RuntimeException

WARNING: Name resolution of proxy-recastsoftware.com failed
No Proxy Server Found, continuing without
Downloading Dell Cab
VERBOSE: GET with 0-byte payload
VERBOSE: received 284281-byte response of content type application/vnd.ms-cab-compressed
Expanding the Cab File...
Loading Dell Catalog XML..
VERBOSE: GET with 0-byte payload
VERBOSE: received 231375-byte response of content type application/vnd.ms-cab-compressed
Cannot convert the "System.Object[]" value of type "System.Object[]" to type "System.Version".
At C:\Users\xxx\Desktop\Update-DellApps-Detect.ps1:315 char:32

• ... If ($InstalledDCU){[Version]$CurrentVersion = $InstalledDCU.Version}

•                     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  

  • CategoryInfo : MetadataError: (:) [], ArgumentTransformationMetadataException
  • FullyQualifiedErrorId : RuntimeException

Could not compare "10.9.1.11" to "". Error: "Cannot convert value "" to type "System.Version". Error: "Version string portion was too short or too long.""
At C:\Users\xxx\Desktop\Update-DellApps-Detect.ps1:404 char:17

•         if ($DCMVersion -gt $CurrentVersion)
  

•             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  

  • CategoryInfo : InvalidOperation: (:) [], RuntimeException
  • FullyQualifiedErrorId : ComparisonFailure

Non-Compliant, Exit 1, to trigger Remediation to Update Software

Typo in BGInfoRegBuilder.ps1

File OSD/BGInfo/BGInfoRegBuilder.ps1

Line 597 $SMSTSModel = (Get-CimInstance -ClassName Win32_ComputerSystem).Mode

Should $SMSTSModel = (Get-CimInstance -ClassName Win32_ComputerSystem).Model

Schedule the time

Hi,

thanks for nice work!
I want to try to add time/date Parameter for a schedule start of the task sequence. But i dont see in the code where i can set the time, have you an idea?

is this the ADV_ProgramWindowStartTime Value ?

Dell Command Update XML changed.

For version 4.4.0, the Universal App section in the Dell XML file does not have the letters UWP, so it doesn't get filtered out. FYI for the Intune detect script

Fix line 71 in o365_download.ps1 to $NewFolder = New-Item -Path $ODTExtractPath -ItemType Directory -Force

Fix line 71 in o365_download.ps1 to $NewFolder = New-Item -Path $ODTExtractPath -ItemType Directory -Force

the original line is $NewFolder = New-Item -Path $OSDExtractPath -ItemType Directory -Force

and it needs to be

$NewFolder = New-Item -Path $ODTExtractPath -ItemType Directory -Force

CVE-2023-24932 remediation has some new steps after the April updates

Hi Gary,

CVE-2023-24932 remediation has some new steps after the April updates:
https://support.microsoft.com/en-us/topic/kb5025885-how-to-manage-the-windows-boot-manager-revocations-for-secure-boot-changes-associated-with-cve-2023-24932-41a975df-beb2-40c1-99a3-b3ff139f832d

The remediation script looks like it will need an update.

Thank you for your work in the euc community.

Error in Windows 11 0x80070001 Incorrect function

TaskSequenceSteps2Excel | BootImage2Excel.ps1 - null-valued expression

I was going to test both:

• BootImage2Excel.ps1
• TS2Excelv2.ps1

In both cases i started without providing parameters and then inputted them interactive in the dialog

Both scripts fails for me with a:

You cannot call a method on a null-valued expression error

Example from BootImage2Excel.ps1

Any idea what i might be missing here?

HPIA-PR-Detect.ps1 - The Try statement is missing its Catch or Finally block. The string is missing the terminator: ". Missing closing '}' in statement block or type definition.

When running the HPIA-PR-Detect.ps1 script in PowerShell or VS Code it results in the following errors:

 PS C:\git\source\internal> . 'C:\Scripts\HPIA\HPIA-PR-Detect.ps1'
At C:\Scripts\HPIA\HPIA-PR-Detect.ps1:94 char:18
+                 }
+                  ~
The Try statement is missing its Catch or Finally block.
At C:\Scripts\HPIA\HPIA-PR-Detect.ps1:314 char:2 
+ }
+  ~
The Try statement is missing its Catch or Finally block.
At C:\Scripts\HPIA\HPIA-PR-Detect.ps1:327 char:36
+     Write-Host "Trigger Remediation"
+                                    ~
The string is missing the terminator: ".
At C:\Scripts\HPIA\HPIA-PR-Detect.ps1:315 char:6 
+ else {
+      ~
Missing closing '}' in statement block or type definition.
At C:\Scripts\HPIA\HPIA-PR-Detect.ps1:84 char:35
+     if ($HPIAIsCurrent -eq $false){
+                                   ~
Missing closing '}' in statement block or type definition.
At C:\Scripts\HPIA\HPIA-PR-Detect.ps1:34 char:22
+ Function Install-HPIA{
+                      ~
Missing closing '}' in statement block or type definition.
    + CategoryInfo          : ParserError: (:) [], ParseException
    + FullyQualifiedErrorId : MissingCatchOrFinally

Similar issue also occurs for other scripts.
VS Code raises the below for lines 310 - 312 and 316 - 318.

The character U+2013 "–" could be confused with the ASCII character U+002d "-", which is more common in source code.

Replacing as recommended doesn't resolve.

Update-DellApps-Detect.ps1 | Cannot convert System.Object to System.Version

If I run Update-DellApps-Detect.ps1 I get the following error message but the Dell Command | Monitor was installed.

---

<![LOG[error from script =Der Wert "System.Object[]" vom Typ "System.Object[]" kann nicht in den Typ "System.Version" konvertiert werden.
In C:\WINDOWS\IMECache\HealthScripts\8bca1ee6-4593-40dc-ab38-85e673f41f47_1\detect.ps1:296 Zeichen:13

•         [Version]$DCUVersion = $DellItem.vendorVersion
  

•         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  

  • CategoryInfo : MetadataError: (:) [], ArgumentTransformationMetadataException
  • FullyQualifiedErrorId : RuntimeException

Get-Date : "System.Object[]" kann nicht in den Typ "System.DateTime" konvertiert werden, der für den Parameter "Date"
erforderlich ist. Die angegebene Methode wird nicht unterstützt.
In C:\WINDOWS\IMECache\HealthScripts\8bca1ee6-4593-40dc-ab38-85e673f41f47_1\detect.ps1:297 Zeichen:42

• ... $DCUReleaseDate = $(Get-Date $DellItem.releaseDate -Format ...

•                                         ~~~~~~~~~~~~~~~~~~~~~
  

  • CategoryInfo : InvalidArgument: (:) [Get-Date], ParameterBindingException
  • FullyQualifiedErrorId : CannotConvertArgument,Microsoft.PowerShell.Commands.GetDateCommand

]LOG]!>

Dell-Updates.log

CVE-2023-24932-CI-Remediation.ps1 - Copy-Item throws "Illegal characters in path" on Windows 11

When running the script on Windows 11, The Copy-Item command throws "Illegal Characters in path"

HPIA-PR-Detect.ps1 - $HPIAInstallPath Parameter

Function Install-HPIA{
[CmdletBinding()]
    Param (
        [Parameter(Mandatory=$false)]
        $HPIAInstallPath = "$env:ProgramFiles\HP\HPIA\bin"
        )

Error when running:
Install-HPIA : Cannot bind argument to parameter 'HPIAInstallPath' because it is null.

Manually setting the variable works.
I moved this out of the function to be with the other variables line 22 and it works.