USMT Estimation Report

, , , , , ,

USMT Estimation Report

USMT Estimation Report – One of the deliverable items at a customers site was to identify the amount of data each machine would would have to backup. This is important data to capture to help plan your estimated migration times as well as identify systems that will not be able to successfully perform a backup. This data is not something that SCCM will automatically absorb, but Jason Sandy already has a solution for that. We used his script here with a few mods for our environment we were able to capture this information.

let me point out that if you look inside of the MDT Toolkit for ZTIUserState.wsf you will see that it is estimated to need 1.1 times the size of the data you are trying to catpure. This is something that was pointed out from a co-worker.
USMT Estimation Report
OLD Report Visuals
USMT Estimation Report

New Report Visuals

 

USMT Estimation ReportUSMT Estimation Report

 

The new report allows you to look up specific computers, interactive sorting, better visuals, graphs, and more efficient SQL logic.

you will have to modify the CASE WHEN statements to fit your own environment. Please do some testing and then modify for the “USMT Only Time Estimate” column. Several factors go into consideration for determining this value. These are things such as server specs, amount of systems running the task concurrently, bandwidth, etc.

THE RDL: https://gallery.technet.microsoft.com/USMT-Space-Estimator-2c5d728b

SCCM Power Plan SQL Queries

, , , ,

SCCM Power Plan SQL Queries

In one of my customers environments there was a request for a quick review of ConfigMgr SCCM Power Plan settings. This turned out to show us that there were over 20+ power plans in the environment and needed to be reduced. Below is the quick query I came up with for the customer.

— individual systems with power plans and collection they belong to
select
SMS_R_System.Name0 AS [System Name],
V_Collection.Name AS [Collection Name],
__R_MANAGEMENT_CONFIGURATION0.NonPeakPowerPlanName00 AS ‘Non Peak Power Plan Name’,
__R_MANAGEMENT_CONFIGURATION0.PeakPowerPlanName00,
__R_MANAGEMENT_CONFIGURATION0.PowerConfigID00 AS [Collection Power setting Source] from
vSMS_R_System AS SMS_R_System
INNER JOIN POWER_MANAGEMENT_CONFIGURATION_DATA AS __R_MANAGEMENT_CONFIGURATION0 ON __R_MANAGEMENT_CONFIGURATION0.MachineID = SMS_R_System.ItemKey
Inner JOIN V_Collection on V_Collection.CollectionID = __R_MANAGEMENT_CONFIGURATION0.PowerConfigID00
Order by
SMS_R_System.Name0

 

SCCM Power Plan

— collections with count of systems with power plans
select
V_Collection.Name AS [Collection Name],
__R_MANAGEMENT_CONFIGURATION0.PowerConfigID00 AS [Collection Power setting Source],
count (V_Collection.Name) AS Count,
__R_MANAGEMENT_CONFIGURATION0.NonPeakPowerPlanName00 AS ‘Non Peak Power Plan Name’,
__R_MANAGEMENT_CONFIGURATION0.PeakPowerPlanName00
from
vSMS_R_System AS SMS_R_System
INNER JOIN POWER_MANAGEMENT_CONFIGURATION_DATA AS __R_MANAGEMENT_CONFIGURATION0 ON __R_MANAGEMENT_CONFIGURATION0.MachineID = SMS_R_System.ItemKey
Inner JOIN V_Collection on V_Collection.CollectionID = __R_MANAGEMENT_CONFIGURATION0.PowerConfigID00
Group by
v_Collection.Name,
__R_MANAGEMENT_CONFIGURATION0.NonPeakPowerPlanName00,
__R_MANAGEMENT_CONFIGURATION0.PeakPowerPlanName00,
__R_MANAGEMENT_CONFIGURATION0.PowerConfigID00

 

SCCM Power Plan

In a future blog post I’ll drop a massive amount of sql queries you should find helpful in any environment.