powercfg.exe -setactive 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c

Where the present GUID is the GUID of the power state. In this case, that is the High Performance power state.

To fix this, I downloaded the hotfix and created a package in SCCM then linked that package into our task sequences. Command line option for install via task sequence (for the program within your hotfix package):

wusa.exe Windows6.1-KB977944-x86.msu /quiet /norestart

I also have a reboot task sequence step right after this. The reason to block the update’s reboot and create your own is so that the TS will resume upon reboot and continue with your deployment.

Here is how I did it (in two task sequence steps for discernability):

1) Run Command Line > assoc .zip=7-Zip.zip
2) Run Command Line > ftype 7-Zip.zip=C:\progra~1\7-Zip\7zFM.exe

We are deploying x86 so we don’t have to worry about the Program Files issues, but if you are, 7-Zip has a 64-bit MSI and you just need to make your path point to the correct spot (IIRC, you will want progra~2 for x64, or you could just spell it out but we don’t do easy around here, dangit).

Run in: C:\Windows\System32
Command line: cscript.exe c:\windows\system32\slmgr.vbs /ato

SWIFSDRIVE is the drive letter you want to make as your APP-V local cache drive. Make sure this does not conflict with any mapped network drives or any local drive letters.

You can also control this through Group Policy by importing the APP-V ADM template.

This also applies to the TS client.

setup.exe /s /v"/quiet /norestart /qn"0\"\" SWIFSDRIVE="L"

1) In your task sequence, find the step you wish to limit.
2) Go into the Options tab.
3) Under Add Condition choose Query WMI
4) Namespace is root\cimv2
5) Query is SELECT * FROM Win32_ComputerSystem WHERE Model LIKE '%latitude%'

1) Download SQL Server Management Studio Express
2) When you launch the console, connect to \\.\pipe\mssql$microsoft##ssee\sql\query (You do not need to specify SERVER\INSTANCE, just copy that in and connect).

This is how you can exclude a collection from your True-Up results. In our case, we have many affiliate companies and one of them, being a Microsoft partner, performs their own True-Up. As such, we do not report them to our Microsoft reps. All machines belonging to that company are placed into their own collections and excluded. My example finds all 2008 Enterprise servers not in that affiliate’s collection.

SELECT distinct
SYS.Netbios_Name0,
SYS.AD_Site_Name0,
OS.Caption0
FROM
v_R_System SYS
INNER JOIN
v_GS_OPERATING_SYSTEM OS
ON
SYS.ResourceID = OS.ResourceID
WHERE
SYS.ResourceID NOT IN
(SELECT
ResourceID
FROM
v_FullCollectionMembership FCM
WHERE
(CollectionID = 'XXX000a6'))
AND
OS.Caption0 LIKE '%2008%enterprise%'