SCCM SQL script to find users associated with computers

SELECT  GS.Name0,
GS.UserName0,
WS.LastHWScan,
GS.Domain0,
OS.Caption0,
SYS.SystemRole0
FROM
v_GS_COMPUTER_SYSTEM GS,
v_GS_OPERATING_SYSTEM OS,
v_GS_SYSTEM SYS,
v_GS_WORKSTATION_STATUS WS
WHERE
GS.ResourceID = SYS.ResourceID
AND WS.ResourceID = GS.ResourceID
AND OS.ResourceID = GS.ResourceID
AND SYS.SystemRole0<>’Server’
AND Datediff(dd,WS.LastHWScan,getdate()) > -1 and
GS.username0 in (‘DOMAIN\user1′,’DOMAIN\user2′,’DOMAIN\user3’)

http://eskonr.com/2012/08/sccm-configmgr-report-find-computers-for-the-list-of-selected-users/

Advertisements

Laptop dead after 1709 upgrade

I have had to avoid deploying 1709 mainly due to the fact that it was bricking all physical devices HP 725/745/612/X360 and rendering them dead halfway through the upgrade with no ability to rollback. This was back in October when we started to test this and the only virtual machines could be upgraded.

It was only recently that I found an article pointing a finger at a new setting in the latest baselines

https://blogs.technet.microsoft.com/secguide/2018/01/18/issue-with-bitlockerdma-setting-in-windows-10-fall-creators-update-v1709/

After changing this to “disabled” upgrades to 1709 now work.

More info here

https://support.microsoft.com/en-gb/help/4057300/devices-not-working-before-log-on-a-computer-running-windows-10-1709

Baselines modified for RS2/RS3 as below.

MSFT Windows 10 RS2 – Computer

Computer Configuration | Policies | Administrative Templates | Windows Components | BitLocker Drive Encryption = Disabled

MSFT Windows 10 RS3 – BitLocker

Computer Configuration | Policies | Administrative Templates | Windows Components | BitLocker Drive Encryption = Disabled

How to deploy a Windows Image on UEFI-based Computers

Various errors including:

Unable to find a raw disk that could be partitioned as a system disk
failed to validate for boot image staging
stagebootimagefailed 8007000f

The efi partition on a efi system must be fat32

Failed to prepare the system partition for staging
the request is not supported
80070032

Trick is you must disable Secureboot and create UEFI partitions yourself. Just turn Secureboot off in properties and when ConfigMgr boot media is started press F8 and create partitions yourself.
•Diskpart
•Select disk 0 (0 being the disk to setup)
•Clean (wipe the disk)
•Convert gpt (convert disk to GPT)
•Create partition efi size=200 (EFI system partition)
•Assign letter=s (Any allowable letter)
•Format quick fs=FAT32 (Format the ESP)
•Create partition msr size=128 (Create the MSR partition)
•Create partition primary (Create Windows partition)
•Assign letter=c
•Format quick fs=NTFS (Format primary partition)
•Exit

http://henkhoogendoorn.blogspot.co.uk/2014/11/how-to-deploy-windows-image-on-uefi.html

 

Adding Windows OEM information

1. Type regedit in RUN dialog box or Start Menu searchbox and press Enter. It’ll open Registry Editor, now go to:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion

Under this key, look for a key OEMInformation. If it doesn’t exist, create it.

2. Now select OEMInformation key and in right-side pane, create following String values and set their values as shown below:

Logopath_of_OEMlogo.bmp_file
ManufacturerAny_desired_name
ModelAny_desired_name
SupportHoursAny_desired_time_amount_like_24x7
SupportPhoneAny_desired_phone_number
SupportURLAny_desired_URL

https://www.askvg.com/add-customized-strings-in-system-properties-dialog-box-of-windows-vista/