Open DJ12220 opened 3 years ago
DJ12220
commented
3 years ago An update, stepping through the PowerShell it errors after trying to populate the SKU into $computerdetails.
Not sure how to remedy this, I have added the additional Win32_Baseboard SKU into the hardware collection which didn't resolve the issue.
DJ12220
commented
3 years ago Found the issue: Fujitsu use Product not SKU for storing the baseboard, at least on the two models I've tried (Esprimo D958 and LIFEBOOK A357)
Changing the code to:
"*Fujitsu*" { $ComputerDetails.Manufacturer = "Fujitsu" $ComputerDetails.Model = (Get-WmiObject -Class "Win32_ComputerSystem" | Select-Object -ExpandProperty Model).Trim() $ComputerDetails.SystemSKU = (Get-WmiObject -Class "Win32_BaseBoard" | Select-Object -ExpandProperty Product).Trim()
resolved the issue, however if some fujitsu's does use SKU this will break it for those models.
I am not very good at powershell, so don't know if you can add something that if the SKU result is empty it checks the PRODUCT property?
Just set this up to test in our environment, rest API service is up and running and produces the expected results when tested via the method suggested by MS in the webpages linked in the instructions.
A service account has been created and has been added to the task sequence as instructed.
When ran with the -debugmode switch, it fails at the same point with not further information.
It also runs and closes instantly.
SCCM fails with an error 0x80004004 which I don't seem to be able to find a reference for on the internet, well at least that isn't on some dodgy website our filtering blocks.
the GUI is connected and has created a driver pack successfully and uploaded it to the DPs.
Any pointers will be greatly appreciated.