intrntpirate

Does anyone know how to read the USMTSIZE.txt file that's produced when you run Scanstate.exe \\server\path /p /nocompress? This is what I'm getting when I run it. 4096 15474688 0 15231206 512 15258624 1024 15286272 2048 15355904 4096 15474688 8192 15761408 16384 16351232 32768 17629184 65536 20709376 131072 27000832 262144 39321600 524288 65011712 1048576 115343360 How can I take that information and actually find out how much space the uncompress store is going to take up? Any assistance is greatly appreciated.

I would like to be able to update the BIOS on Dell machines that need it during the WinPE phase of my task sequence. I've been messing around with it for a couple days now and the task sequence keeps failing with 0x00000032. It works fine if I try to run the BIOS update once in the OS, so I'm assuming that there's something missing from WinPE that's preventing it from updating. Has anyone done this or have any idea's on how to do this?

I ended up deleting the driver package that contained the mass storage drivers, then re-creating it.

*RESOLVED* Hey everyone, Up until last week I was always using nLite to inject mass storage drivers into XP, then I finally took the time to figure out how to apply driver packages before the XP mini setup to inject the drivers. During my testing I had the task sequence apply the operating system package, auto apply drivers, and then apply the mass storage driver using an advertisement that was set to access content directly. The testing went great, so I went ahead and applied it to one of my main task sequences only to find that the mass storage driver step fails every time. The only difference between the two task sequences is that the testing task sequence accesses content directly and the main task sequence downloads content locally. So, I suppose my question is do I have to have my task sequences accessing content directly in order to apply mass storage drivers with driver packages? Thanks in advance. Edit1: Maybe the error information would be useful. ttpContentSources, saSMBContentSources, saMulticastContentSources, sDestination, dwFlags, L"", 0, dwPackageFlags, pszUserName, pszUserPassword ), HRESULT=80091007 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,3002) DownloadContentLocally(pszSource, sSourceDirectory, dwFlags, hUserToken, pszUserName, pszUserPassword), HRESULT=80091007 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,3130) ResolveSource(pszSource, sSourceDirectory, dwFlags, 0, 0, 0), HRESULT=80091007 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,3031) TS::Utility::ResolveSource( pszPackageId, sSource ), HRESULT=80091007 (e:\nts_sms_fre\sms\client\osdeployment\osddriverclient\driverinstaller.cpp,472) pDriverInstaller->InstallDriverPackage( sPackageId, pBootCriticalInfo ), HRESULT=80091007 (e:\nts_sms_fre\sms\client\osdeployment\osddriverclient\osddriverclient.cpp,409) Exiting with return code 0x80091007 Failed to determine the driver source location. Code 0x80091007 Failed to provision driver. Code 0x80091007

So I've got an interesting issue to throw to the community here. I have a ConfigMgr site that has been 100% operational for the past 1 1/2 years. WIthin the past 2 weeks however the operating system deployment portion has stopped functioning correctly. During the deployment of Windows XP Pro SP3 ConfigMgr will run its PnP drivers deployment, find all the drivers, copy them to the C:\ drive, then add the driver location to the unattended file for XP to use during setup. So far, so good. However once the task sequence is done installing XP and goes to communicate with the distribution point to run additional tasks it fails. It fails because the network card failed to get installed even though the drivers were copied over. Now if I go into device manager I can manually install the network card using the drivers already on the C: drive, so I know the drivers are good, and it's not just a particular model of PC because this is happening on all the model of PC's not just one. Now just to get this out, absolutely nothing has changed in the environment. I'm the only ConfigMgr admin. Here are the things I've done in troubleshooting with the same result of having no network card installed. * Refreshed the operating system source files * Downloaded the latest operating system source files from Microsoft * Refreshed the driver packages * Deleted all the drivers from ConfigMgr then reloaded just the drivers for one model of PC, still no luck * Reloaded ALL the drivers back into ConfigMgr * Created a custom task sequence that only installs XP I'm up for any suggestions or ideas. I'm completely confused as to why this is happening all of a sudden especially since I haven't changed anything. Thanks in advance.

Ummm... I'm pretty sure that you should know your product codes... if you're refering to automating the installation you can run setup.exe and use the admin switch. (setup.exe /admin) Is this what you're talking about?