Posted on June 26th, 2016
This was forwarded to me from one of our Microsoft guys. I have been using a batch file to fix WMI with this line for years: WMI: Stop hurting yourself by using “for /f %%s in (‘dir /s /b *.mof *.mfl’) do mofcomp %%s”
Posted on February 13th, 2016
My friend, Nick Miller, has gone to work with another company, and is involved in a Windows 7 image standardization project. He recently told me that he had figured out how to have a single bootable USB WinPE disk to create both 32 bit and 64 bit OS images. Nick is a smart guy, and he had not found instructions for this anywhere else on the web. I suggested that he be my first Guest Blogger.
For a long time I have wanted to have a single USB bootable media that will install every Windows OS known to man. This has always eluded me because of the differences between architectures. Recently it bothered me to the point of fixing it.
If you have found this article, you probably already know how to build a WINPE 32 bit bootable media, and I will not bore you with the details. Start by creating a directory for the Windows 7 (32 bit) files. Create another directory for the Windows 7 (64 bit) file. For each OS architecture, create a Unattend.xml and place it inside the corresponding directory. It is important to note that both versions must be identical. For example, if you plan on deploying Windows 7 Professional (64 bit) you will need to start the Windows 7 Professional (32 bit) install process.
Here is where it gets mind numbing. Create a new unattend.xml called SpecialUnattend.xml (link has example file) with the WinPE phase of the x86, and the other 6 phases of the x64. Place this in the Windows 7 (64 bit) directory. Be sure to add the “Microsoft-Windows-Setup\Installimage\OSImage\InstallFrom\Path” in the Unattend.xml to point to the Windows 7 (64 bit) wim. IE. “D:\W764\Sources\Install.wim”. And last but not least, at the bottom of the Unattend.xml file (edited with notepad) make sure that the wim is correctly located when booted to the WinPE OS.
To execute, run the following example. “D:\W732\Sources\Setup.exe /InstallFrom:D:\W764\Sources\Install.wim /unattend:D:\W764\SpecialUnattend.xml”
Do not forget that the target drive will need to be wiped with diskpart.
For more information, feel free to reach out to me at NCSHREK on Hotmail.
Thanks Nick. I know that other SCCM admins will find this to be very helpful.
Posted on September 7th, 2012
Sometimes you get a panicked call saying, “I got a message saying my computer will reboot in 5 minutes”. StopSCCMRestart.cmd allows you to abort the reboot on a local or remote machine. It works by killing the SMSCliUI.exe task. The task will be eventually restarted, but this should give your user a chance to reboot at a more convenient time.
Posted on October 13th, 2011
Sometimes a poorly framed query or collection can cause SCCM collections to be left forever in an evaluation state. As a result, the TempDB for the SCCM server can grow to the point where it fills the available drive space. When that happens, SQL stops, and SCCM stops.
Some advice: TempDB is recreated when the SQL Server service is restarted. This is your first action to clear the problem. You should thereafter restart the SMS Executive service.
As the tempdb begins to grow, you can find out what is going on by looking at reports. In the SQL Server Management Studio, expand system databases, right clicking on tempdb, and selecting Reports/Standard Reports. “Top Transactions By Age” will show you what has been stuck, and can give you evidence to track back from there.
In a large SCCM environment, keeping track of the tempdb can be time consuming. SCCM TempDB Space.vbs will connect to the SCCM database and report tempdb size, path, and free space from all site servers. The script has some interesting combinations of WMI queries and SQL queries.