Jump to content

Recommended Posts

Posted

I'm assuming the answer is no but did anyone manage to figure out anything for the HP 255 G7s?

 

Been here for a few hours but haven't once got past the "securing your hardware" stage

Posted
I'm assuming the answer is no but did anyone manage to figure out anything for the HP 255 G7s?

 

Been here for a few hours but haven't once got past the "securing your hardware" stage

 

I’ve changed jobs since I last posted so won’t be able to provide much more info on the issue, but i heard that a BIOS update from HP (not the one via Windows Update) then initiated a TPM update and that resolved it for the HP 255 G8’s.

 

Hopefully one of my previous colleagues will post here with more info on it and if the ticket is still open with HP for the other models affected.

 

I assume latest BIOS from HP doesn’t work for the 255 G7’s. Worth logging a ticket with HP for them if they’re still under warranty.

  • Thanks 1
Posted
As a shared device which self propels through the enrollment they won't work and hp say they don't have a fix. They should work as a 121 device where the user is prompted to log in with there Azure login to continue enrolment.
Posted
I'm assuming the answer is no but did anyone manage to figure out anything for the HP 255 G7s?

 

Been here for a few hours but haven't once got past the "securing your hardware" stage

I've never been able to get the G7s to work, so we have them all set as user enrollment and then remove the primary user within Intune to set them as shared devices.

  • Thanks 1
Posted
I've never been able to get the G7s to work, so we have them all set as user enrollment and then remove the primary user within Intune to set them as shared devices.

I appreciate the message thank you! I will go for user enrollment then.

  • 3 months later...
Posted

I've just come across this issue with these DFE laptops...

 

Does this issue occur with pre-provisioning? 

 

Just trying a BIOS update now. 

 

 

  • 9 months later...
Posted

Can confirm the issue still exists. We've got a couple of them still plodding along. Joined to intune fine just fails when trying to assign to autopilot. Only this specific model too.

  • 1 month later...
  • 4 weeks later...
Posted

I had this issue when I first joined the HP G7's , took lots of attempts to get them on the system.

 

With these machines only being able to run Windows 10 , for security they are now removed from our system , Wiped etc . Parents informed that they can keep or return , But no longer supported by us .

 

If anyone wants my script that can remove bulk ( Serials required in a CSV ) 

 

# Path to CSV
$csvPath = "C:\Scripts\Intune\devices_to_remove.csv"

# Connect to Microsoft Graph
Connect-MgGraph -Scopes `
"DeviceManagementManagedDevices.ReadWrite.All",
"DeviceManagementServiceConfig.ReadWrite.All",
"Directory.ReadWrite.All"   # Required for Azure AD device removal

# Import CSV
$devices = Import-Csv $csvPath

# Get all Autopilot devices once
$autopilotDevices = Get-MgDeviceManagementWindowsAutopilotDeviceIdentity -All

# Get all Intune managed devices once
$managedDevices = Get-MgDeviceManagementManagedDevice -All

# Get all Azure AD devices once
$aadDevices = Get-MgDevice -All

# Check if the cmdlet exists
$wipeCmdletExists = Get-Command Invoke-MgDeviceManagementManagedDeviceWipe -ErrorAction SilentlyContinue

foreach ($entry in $devices) {

    $serial = $entry.SerialNumber.Trim().ToUpper()
    Write-Host "`nProcessing serial:" $serial

    # --- Remove from Autopilot ---
    $apDevice = $autopilotDevices | Where-Object { $_.SerialNumber -and $_.SerialNumber.Trim().ToUpper() -eq $serial }

    if ($apDevice) {
        Write-Host "Removing from Autopilot..."
        Remove-MgDeviceManagementWindowsAutopilotDeviceIdentity -WindowsAutopilotDeviceIdentityId $apDevice.Id
        Write-Host "Autopilot entry removed"
    } else {
        Write-Host "Autopilot device not found"
    }

    Start-Sleep -Seconds 5  # small wait for propagation

    # --- Remove from Azure AD ---
    $aadDevice = $aadDevices | Where-Object {
        ($_.devicePhysicalIds -match "SerialNumber:$serial") -or
        ($_.deviceId -eq $serial) -or
        ($_.displayName -like "*$serial*")
    }

    if ($aadDevice) {
        Write-Host "Removing device from Azure AD..."
        foreach ($d in $aadDevice) {
            Remove-MgDevice -DeviceId $d.Id
        }
        Write-Host "Azure AD device removed"
    } else {
        Write-Host "Azure AD device not found"
    }

    # --- Find Intune managed device ---
    $managedDevice = $managedDevices | Where-Object { $_.SerialNumber -and $_.SerialNumber.Trim().ToUpper() -eq $serial }

    if ($managedDevice) {
        Write-Host "Managed device found:" $managedDevice.DeviceName

        # --- Send wipe command ---
        if ($wipeCmdletExists) {
            Write-Host "Using Invoke-MgDeviceManagementManagedDeviceWipe..."
            Invoke-MgDeviceManagementManagedDeviceWipe -ManagedDeviceId $managedDevice.Id -KeepEnrollmentData:$false -KeepUserData:$false
        } else {
            Write-Host "Cmdlet not available, using direct Graph API request..."
            $body = @{
                keepEnrollmentData = $false
                keepUserData       = $false
            } | ConvertTo-Json

            Invoke-MgGraphRequest -Method POST `
                -Uri "https://graph.microsoft.com/v1.0/deviceManagement/managedDevices/$($managedDevice.Id)/wipe" `
                -Body $body
        }

        Write-Host "Wipe command sent"
    } else {
        Write-Host "Intune managed device not found for serial:" $serial
    }

    Write-Host "-----------------------------"
}

Write-Host "`nAll devices processed"

 

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...