[Topaz George]

Thank you, Rajesh. Hermenegildo, can you please check if the above-mentioned deployment of an “empty” task sequence with the sccmtspsi boot image helps you resolve the ‘boot image not found’ issue.

[Topaz George]

Hermenegildo, Can you also please check the following?
Check if both x86 and amd64 version of the PXEboot image is available on your PXE enabled distribution points. Remove other unnecessary boot images from the DP’s
Check if at the least one of your task sequences has the ‘sccmtspi PXE image’ attached to it and it is deployed as ‘available‘ to the UNKNOWN SYSTEMS collection in addition to the Realm deployment collection (as described in the documentation). See the attached image.

[Topaz George]

Are you using boot USB medium or pxe?Is you virtual machine a Legacy BIOS or advanced UEFI system?
Did you download the winpe from https://sccmtspsi.com/sccmtspsi-downloads/?section=winpe-boot-images
have you checked boot device priority?
What hypervisor are you using?

• This reply was modified 4 years, 9 months ago by  Topaz George.
• This reply was modified 4 years, 9 months ago by  Topaz George.

sccmtspsi-downloads

[Topaz George]

Hope this helps.

If(Test-Path -Path($((Get-WmiObject Win32_OperatingSystem).SystemDrive) +"\windows.old"))
{ 
	New-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\VolumeCaches\Previous Installations" -Name "StateFlags1221" -PropertyType DWORD  -Value 2 -Force | Out-Null 
	cleanmgr /SAGERUN:1221 
}

[Topaz George]

Use the below script to delete user profiles using PowerShell.

Get-CimInstance win32_userprofile -verbose | Where {$_.LastUseTime -lt $(Get-Date).Date.AddDays(-60)} | Remove-CimInstance -Verbose

You could deploy the above script using the following methods.

• SCCM package.
• SCCM Run Script.

This is normally a one off activity so I prefer the ‘Run Script’ function. Hope this helps.

[Topaz George]

Does the below SQL query help?

select v_R_System.Name0, Count(LocalPath0) as profileTotal from v_GS_USER_PROFILE
left join v_R_System ON v_R_System.ResourceID = v_GS_USER_PROFILE.ResourceID
where LocalPath0 LIKE '%\users\%' and v_R_System.Operating_System_Name_and0 LIKE '%worksta%'
group by v_R_System.Name0 order by profileTotal desc

[Topaz George]

Howdy Denver. I’ve experienced similar issues before. I guess a recently installed update might have caused this issue (But I say this based on previous experience alone).
I recommend opening a support ticket with Microsoft. Run the Recovery Assistant for Office 365 (SaRA) tool and send Microsoft the results.

[Topaz George]

• You can do the either one of the following.

 Set-ExecutionPolicy unrestricted

or execute the script using the following command.

powershell.exe -noprofile -executionpolicy bypass -file .\getcal.ps1

The acceptable execution policy values are as follows:

• AllSigned : Requires that all scripts and configuration files are signed by a trusted publisher, including scripts written on the local computer.
• Bypass : Nothing is blocked and there are no warnings or prompts.
• Default : Sets the default execution policy. Restricted for Windows clients or RemoteSigned for Windows servers.
• RemoteSigned : Requires that all scripts and configuration files downloaded from the Internet are signed by a trusted publisher. The default execution policy for Windows server computers.
• Restricted : Doesn’t load configuration files or run scripts. The default execution policy Windows client computers.
• Undefined : No execution policy is set for the scope. Removes an assigned execution policy from a scope that is not set by a Group Policy. If the execution policy in all scopes is Undefined, the effective execution policy is Restricted.
• Unrestricted : Beginning in PowerShell 6.0, this is the default execution policy for non-Windows computers and can’t be changed. Loads all configuration files and runs all scripts. If you run an unsigned script that was downloaded from the internet, you’re prompted for permission before it runs.

Source => https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.security/set-executionpolicy?view=powershell-7

• This reply was modified 4 years, 10 months ago by  Topaz George.

[Topaz George]

@Rocky . Furter to Bobby’s questions, can you also clarify what you mean by ‘will be available at the time of installation‘ Will you be adding conditions to your Task Sequence steps using the values you collect from the UI (User Interface)?

[Topaz George]

$disks = Get-WmiObject -Query "Select * from Win32_LogicalDisk where DriveType=3" -ComputerName $env:COMPUTERNAME -Namespace root\cimv2
$fList = $disks | ForEach-Object {
New-Object PSObject -Property @{
'Name' = $_.DeviceID
'Space in Total (GB)' = $_.Size / 1GB
'Free Space in GB' = $_.FreeSpace / 1GB
'Free Space as a %' = 100 * $_.FreeSpace / $_.Size
}
}
$fList|Format-List

[Topaz George]

Hope this helps.

%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\PowerShell.exe -NonInteractive -WindowStyle Hidden -noprofile -ExecutionPolicy Bypass -command "&{$tsenv = New-Object -COMObject Microsoft.SMS.TSEnvironment;if ((get-wmiobject -class Win32_SystemEnclosure).chassistypes -in ("""8""","""9""","""10""","""11""","""14""")) {$tsenv.Value('isLaptop') = 'True'} else {$tsenv.Value('isLaptop') = 'False'}}"

[Topaz George]

Thanks for your feedback, Jessica. We are here to serve. Message us anytime for support. Marking this topic as fixed.

[Topaz George]

Log on to your account at manage.microsoft.com. In Administration Overview select View Service Status. The location of your tenant and the maintenance schedule are listed there. For details of the service, updates see Windows Intune Service Updates on TechNet.
https://techcommunity.microsoft.com/t5/intune-customer-success/microsoft-intune-service-updates/ba-p/358728

[Topaz George]

Jess, Try and update your distribution point. The version of the Package that you are distributing might be different from the version available in the Client assigned distribution point.
The dependency checking algorithms in the SCCM task sequence will identify and report the absence of a referenced package or application. Still, it will not identify version mismatches before the task sequence begins.
So, try updating content on the distribution point. If it is an SCCM application, delete historical revisions too.