I was looking for a video driver for the HP ProLiant DL360 G7 so I could import it into ConfigMgr for the purposes of deploying Windows Server 2008 R2 to them. Oddly enough, HP doesn’t list a video driver available for download on the driver download page for this system model. On one server, I noticed that the device name was "ATI ES1000,” and most of you are probably aware that the ATI brand name has been gone for some time, so this seemed a bit odd.
Posts Tagged ‘osd’
Posted by Trevor Sullivan on 2011/12/02
Just recently, I was getting an error in the pxemsi.log (pxemsi.log.lasterror) while trying to install a ConfigMgr 2007 PXE Service Point (PSP):
DEBUG: Error 2203: Database: C:\Windows\Installer\1e0d86.ipi. Cannot open database file. System error –2147287037
MSI (s) (20:FC) [09:46:12:689]: Product: SMS PXE Service Point — Internal Error 2203. C:\Windows\Installer\1e0d86.ipi, –2147287037
Internal Error 2203. C:\Windows\Installer\1e0d86.ipi, –2147287037
Posted in configmgr, fixes, OSD | Tagged: configmgr, configmgr 2007, microsoft, msft, osd, pxe, sccm, sccm 2007, sysctr, system center configuration manager, wds, windows deployment services | Leave a Comment »
Posted by Trevor Sullivan on 2011/06/28
You might need to set the Network Access Account (NAA) in System Center Configuration Manager 2012 Beta 2 if you are deploying operating systems with it. Windows Pre-Execution (WinPE) needs an account to access content on the distribution point. In order to set the network access account, open the SCCM console and navigate to this node: \Administration\Overview\Site Operations\Sites. Right-click on the SCCM site in the right-hand pane, and select Software Distribution. Click on the Network Access Account tab, and set the account you want to use.
Posted in configmgr, ConfigMgr vNext, OSD | Tagged: configmgr, configmgr 2012, configuration manager, microsoft, msft, osd, sccm, sccm 2012 beta 2, system center configuration manager 2012 | 1 Comment »
Posted by Trevor Sullivan on 2011/06/15
The System Center Configuration Manager 2012 Beta 2 client agent has been updated significantly. One of the things that has been changed a lot is the client-side interface that allows an end-user to select optional software to install, scripts to run, or operating systems to deploy.
In previous versions of ConfigMgr, there was a Control Panel applet called “Run Advertised Programs.” A user would open this in order to browse the list of optional program made available by a ConfigMgr administrator. There was another control panel applet called “Program Download Monitor” that would allow an end-user to monitor the download status of a program – admittedly, this was probably hardly ever touched by an end-user, realistically.
Posted in configmgr, ConfigMgr vNext | Tagged: configmgr, configmgr 2012, configuration manager, microsoft, msft, osd, sccm, sccm 2012 beta 2, system center, system center configuration manager 2012 | 3 Comments »
Posted by Trevor Sullivan on 2010/05/13
This article will briefly discuss how to export a ConfigMgr OSD task sequence.
The SMS_TaskSequencePackage class has a lazy property named Sequence which contains the XML for the task sequence. Because this is a lazy property, we must obtain a reference to each WMI instance using its direct path, before we can open the property’s value. Once we have the XML for the task sequence, we can send it off to a text file. The PowerShell code to do that would look like this:
$TsList = Get-WmiObject SMS_TaskSequencePackage -Namespace root\sms\site_lab
ForEach ($Ts in $TsList)
$Ts = [wmi]”$($Ts.__PATH)”
Set-Content -Path “$($ts.PackageId).xml” -Value $Ts.Sequence
Posted in configmgr, powershell, scripting, tools, wmi | Tagged: administration, configmgr, microsoft, osd, powershell, system center, task sequence, vbscript, windows management instrumentation, wmi | 7 Comments »
Posted by Trevor Sullivan on 2009/10/27
After upgrading from MDT 2008 to 2010, I recently experienced an issue with MDT / WinPE 3.0 that was simply a driver issue. The initial symptom reported to me was: Driver detection / copying (ZTIDrivers.wsf) is taking a long time in WinPE on a Lenovo T60. The build completed, but hung on the driver injection step for about an hour.
To start diagnosing, I booted WinPE 3.0 off of USB flash drive (UFD) on a Lenovo T60, brought up a command prompt (press F8) and tried to browse the disk (just by typing “c:”) I got: “The volume does not contain a recognized file system. Please make sure that all required file system drivers are loaded and that the volume is not corrupted.” Upon issuing “format fs=ntfs quick” to diskpart, I received: “DiskPart has encountered an error: The parameter is incorrect. See the System Event Log for more information.” Running “ipconfig” yielded normal results, and I was also able to mount network shares, and browse them without any issue.
Note: I typically use a UFD because they boot significantly faster than off of optical media. 🙂
After posting on the MDT-OSD discussion list on MyITforum, I discovered that I may not have the correct drivers in my boot image. Most other people have reported that they haven’t had to inject any drivers, and I figured that the Vista drivers I had in my old WinPE 2.x boot images should have worked alright. As it turns out however, the Intel NIC was using a built-in driver from Microsoft according to wpeinit.log, and there was no mass storage driver being loaded according to the output from “devcon driverfiles *“.
So, simply updating the mass storage and NIC drivers resolved the issue(s). The network drivers can be found here: http://www.intel.com/support/network/sb/cs-006120.htm. The storage drivers can be found here: http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=17882&lang=eng.
Posted by Trevor Sullivan on 2009/10/27
I just installed the Windows AIK for Windows7, and MDT 2010 on my 64-bit Windows 7 Release Candidate system, and attempted to open the Deployment Workbench. It opened just fine, but when I selected the Deployment Shares node in the snap-in, I got this error: “The file C:\Windows\system32\wimgapi.dll(version 6.1.7100.0 (winmain_win7rc.090421-1700)) is older than the installed Windows Automated Installation Kit (version 6.1.7600.16385). Please remove the C:\Windows\system32\wimgapi.dll file so the proper one is used.”
I am unable to remove the file, or replace it with the newer AIK one, due to a lock on the file (my guess would be that it’s Windows System File Checker).
Most likely, the solution (or at least it might help) would probably be to upgrade to Windows 7 RTM, but I’ve been putting that off for so long, what’s a couple more weeks? 🙂 I just wanted to document this error / scenario in case anyone else comes across it.