Straighten up and fly right WMI

sc config winmgmt start= disabled 
kill -f XXX <<<<<<<<<<<<<<<<<<<<<<<<<<<<<< pid obtained before 
cd /D %windir%\system32\wbem 
rmdir /s /q repository 
rmdir /s /q Logs 
mkdir Logs 
for /R %i in (*.dll) do (regsvr32 /s %i) 
regsvr32 /s fastprox.dll 
for /R %i in (*.exe) do (%i -regserver) <<<<<<<<<<<<< this will open wbemtest and/or wmic.exe. Just close it 
sc config winmgmt start= auto 
regsvr32 wbemupgd.dll  <<<<<<<<<<<<<< this can take 30 seconds to 2 minutes 
net start server && net start workstation && net start termservice 




snipped fromhttp://groups.google.com/group/microsoft.public.win32.programmer.wmi/msg/1da6ab3690bc75a0>

Those empty WSUS Groups got ya down

Can't delete those empty WSUS groups:

DELETE FROM [SUSDB].[dbo].[tbDeployment]

WHERE [TargetGroupID]=''

DELETE FROM [SUSDB].[dbo].[tbFlattenedTargetGroup]

WHERE [TargetGroupID]=''

DELETE FROM [SUSDB].[dbo].[tbTargetGroup]

WHERE [TargetGroupID]=''

Go

Quick DCOM Security Reset

Remote Administration: Quick DCOM Security Reset: "The ACLs are stored in the registry under the key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole, in the following binary values:

DefaultAccessPermission
DefaultLaunchPermission
MachineAccessRestriction
MachineLaunchRestriction"

Backup the registry key and then blow all of them away.

GPMC Backspace Bug: Not fixed in Windows 7 / Server 2008 SP1.. but in

GPMC Backspace Bug: Not fixed in Windows 7 / Server 2008 SP1.. but in




http://support.microsoft.com/kb/2466373

Suck on it Broadcom

After hours of freaking headaches here's how I got the broadcom drivers for the VBD to integrate and be detected in MDT 2010 Update 1...  May also be fixed by including system class drivers.  I'm testing that next.


Dism /mount-Wim /WimFile: /mountdir:c:\image /index:1
Dism /Image:C:\image /Add-Driver /Driver: /recurse /ForceUnsigned
Dism /unmount-Wim /mountdir: /commit

MDT 2010 - Customizing Application Installs based on option sets

When you're in the consulting business like I am, deploying/repairing/rebuilding systems can be a tedious task.  Especially when you want to have consistency across desktops.  This is why I love MDT 2010 and you should too.

So today I wanted to discuss how I manage one specific installation task to install VMTools on ESX guest OS.  In my case the guest OS is Windows.  I generally like to keep my task sequences simple so by dynamically installing VMTools on the fly it saves me one more step.

Assumptions:
A.  You already have a VMtools Install package working
B.  You are running ESX 3.5 (you can port it to a 4.x environment too)

In MDT
1.  Add a new Install Application task
2.  On the properties page select Install a single Application radial box
3.  Browse to your VMtools installation package and click OK
4.  Click the Options Tab
5.  Check Continue On Error
6.  Add Query WMI
7.  In the WQL query box enter Select * From Win32_ComputerSystem WHERE Model LIKE "%VMware%"
8.  Image your machine

Microsoft Test Lab Guides

Start Here to build your lab
Download details: Test Lab Guide: Base Configuration

Go here to pick a guide.
Test Lab Guides - TechNet Articles - TechNet Wiki