SQL Query BIOS PASSWORD ON SYSTEMS (Dell and HP)

, , , , ,

Prior to deploying the proprietary client tools described in the sections below, it is helpful to first identify which systems have administrator and/or system passwords configured because some of the tools’ functionality will fail if these passwords are set and not used during deployment.In order to use certain proprietary management tools to make changes to the BIOS/UEFI settings, it is necessary to determine which systems are currently configured to require passwords before settings can be modified. The queries will identify systems that need a password.

Dell

Select
sys.Name0,
DBP.AttributeName0,
ElementName0,
DBP.IsSet0
from
v_GS_DCIM_BIOSPASSWORD0 DBP
Inner Join
V_R_System sys on sys.ResourceID = DBP.ResourceID
Where DBP.IsSet0 = ‘1’
Order By sys.Name0, DBP.AttributeName0

HP

Select
sys.Name0,
HPBP.Name0,
HPBP.IsSet0
from
v_GS_HPBIOS_BIOSPASSWORD HPBP
Inner Join
V_R_System sys on sys.ResourceID = HPBP.ResourceID
Where HPBP.IsSet0 = ‘1’
Order By sys.Name0, HPBP.Name0

 

ALSO SEE : Secondary Site stuck in “Deleting” state

SCCM 2012 R2 SP1 failed upgrade

, , , ,

This was a project that occurred over a year ago so forgive me for missing a few screenshots. The customer site was preparing for a windows 10 migration by moving SCCM to a level to be supported. This was moving from SCCM 2012 R2 to SCCM 2012 R2 SP1.

Pre upgrade tasks:
– back up site servers the night before via maintenance task
– take snap shot of CAS / Primaries
– restart server and stop key sccm services from running (we disabled maintenance tasks, and deployments as well)
– Restore site database to SQL server running the same version as our SQL instance.

During the upgrade
– Successful SCCM Database upgrade
– Successful pre-req checks
– failed configmgr upgrade

There is where the wizard produced the error about a hash mismatch on MSRDCOOB_AMD63.exe that I forgot to take a screenshot of, but I do have an excerpt of the log file. During this step of the process updated files are being copied and replaced into the program files directory on your site server. When I looked at the wizards error message on face value it made me believe my download was somehow corrupted as I am always quick to suspect HBSS lol. It wasn’t until I read the few lines below in the ccmfigmgrsetup.log that I realized it was a permissions issue.

Error #1 Configmgrsetup.log
Failed to copy \CASd$FOR UPGRADEUPDATES FOR UPGRADEmsrdcoob_amd64.exe to d:program filesmicrosoft configuration managerclientx64msrdcoob_amd64.exe, Win32 error = 5
– ERROR: Failed to delete file d:program filesmicrosoft configuration managerclientx64msrdcoob_amd64.exe, Win32 error = 5

The initial implementation of SCCM years before I inherited the environment was performed with a service account that was not any longer in use. I quickly then took ownership of the folder and reset permissions. After the permissions were corrected I restarted the wizard and ran into another error.

Error #2 Configmgrsetup.log

ERROR: SQL Server error: [42S02][208][Microsoft][SQL Server Native Client 11.0][SQL Server]Invalid object name ‘UpgradeViewMapping’. : spHandleDviewUpgrade
– ERROR: Failed to execute query: spHandleDviewUpgrade

This particular message occurred b/c the earlier run of the upgrade had already made it past the successful upgrade of the database and the stored procedure mentioned “spHandleDviewUpgrade” already deleted a key table needed.

In order to fix this you must run perform 2 actions.

The first is to run this SQL query on your database

GO
SET ANSI_NULLS ON
GO

SET QUOTED_IDENTIFIER ON
GO

CREATE TABLE [dbo].[UpgradeViewMapping](

[TmpViewName] [nchar](10) NULL,

[ViewName] [nchar](10) NULL,

[ViewType] [nchar](10) NULL

) ON [PRIMARY] GO

The second is to delete the perf_msg.dll and smsperf.dll in the c:windowssystem32 folder because otherwise the setup will fail again.

Once these actions were completed the upgrade to R2 SP1 went successful.

Take away: the pre-req checker doesn’t exactly check everything like permissions to key folders and be prepared to do sql work.

 

ALSO SEE : Status Message ID 11756

Windows 10 Migration Project (General UEFI Queries)

, , ,

For environments where there several manufacturers the option to use BIOS tools to gather all information may not be possible. We can guesstimate a system will be UEFI Capable based on the PCBios Date Attribute. We will be generous and system with PC Bios date after 1/1/2013
will be UEFI Capable

UEFI Capable Systems
select distinct SMS_R_System.Name, SMS_G_System_PC_BIOS.ReleaseDate, SMS_G_System_COMPUTER_SYSTEM.Manufacturer, SMS_G_System_COMPUTER_SYSTEM.Model from SMS_R_System inner join SMS_G_System_PC_BIOS on SMS_G_System_PC_BIOS.ResourceID = SMS_R_System.ResourceId inner join SMS_G_System_COMPUTER_SYSTEM on SMS_G_System_COMPUTER_SYSTEM.ResourceID = SMS_R_System.ResourceId where SMS_G_System_PC_BIOS.ReleaseDate > “1/1/2013 12:00:00 AM”

NOTE: There are more specific ways to identify systems that are UEFI capable but that will require
Creating a new WMI namespace. That method described will only work on certain manufacturers like Dell, Lenovo, HP in a future blogpost

UEFI CAPABLE SYSTEM MODELS
select distinct SMS_G_System_COMPUTER_SYSTEM.Manufacturer, SMS_G_System_COMPUTER_SYSTEM.Model from SMS_R_System inner join SMS_G_System_PC_BIOS on SMS_G_System_PC_BIOS.ResourceID = SMS_R_System.ResourceId inner join SMS_G_System_COMPUTER_SYSTEM on SMS_G_System_COMPUTER_SYSTEM.ResourceID = SMS_R_System.ResourceId where SMS_G_System_PC_BIOS.ReleaseDate > “1/1/2013 12:00:00 AM”


Non-UEFI Capable Systems

select distinct SMS_R_System.Name, SMS_G_System_PC_BIOS.ReleaseDate, SMS_G_System_COMPUTER_SYSTEM.Manufacturer, SMS_G_System_COMPUTER_SYSTEM.Model from SMS_R_System inner join SMS_G_System_PC_BIOS on SMS_G_System_PC_BIOS.ResourceID = SMS_R_System.ResourceId inner join SMS_G_System_COMPUTER_SYSTEM on SMS_G_System_COMPUTER_SYSTEM.ResourceID = SMS_R_System.ResourceId where SMS_G_System_PC_BIOS.ReleaseDate > “1/1/2013 12:00:00 AM”

Non-UEFI Capable System Models
select distinct SMS_G_System_COMPUTER_SYSTEM.Manufacturer, SMS_G_System_COMPUTER_SYSTEM.Model from SMS_R_System inner join SMS_G_System_PC_BIOS on SMS_G_System_PC_BIOS.ResourceID = SMS_R_System.ResourceId inner join SMS_G_System_COMPUTER_SYSTEM on SMS_G_System_COMPUTER_SYSTEM.ResourceID = SMS_R_System.ResourceId where SMS_G_System_PC_BIOS.ReleaseDate < “1/1/2013 12:00:00 AM”

NOTE: The results from this query will be used later in the WIN 10 task sequence. These models will receive the “Warning: System Not UEFI Capable” step in the task sequence. These are the system models that will not boot UEFI and will receive Windows 10 on a MBR partition

 

ALSO SEE : Windows 10 Migration Project (General Starter Queries)