Hello, I'm currently having issues creating boot images for a Windows 7 deployment via SCCM. When I attempt to create a new boot image, I receive this error: "The specified file can not be imported. Please make sure the file is not read only and you have read and write access to it." I have ensured that I have both read and write access to this file. Additionally, I am unable to update the distribution points of currently existing images. The wizard comes back with this error: The ConfigMgr Provider reported an error.: ConfigMgr Error Object: instance of SMS_ExtendedStatus { Description = "Failed to insert OSD binaries into the WIM file"; ErrorCode = 2152205056; File = "c:\\qfe\\nts_sms_fre\\sms\\siteserver\\sdk_provider\\smsprov\\sspbootimagepackage.cpp"; Line = 4262; ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook"; Operation = "ExecMethod"; ParameterInfo = "SMS_BootImagePackage.PackageID=\"HAI00001\""; ProviderName = "WinMgmt"; StatusCode = 2147749889; }; I have looked into several of the other threads regarding this issue, but they seemed to have problems when attempting driver insertion. This problem occurs whether or not I have drivers to update the image with. Thanks, Blake

I have ensured that I have both read and write access to this file. [...] The ConfigMgr Provider reported an error.: ConfigMgr Error Object: It's the ConfigMgr provider (computeraccount) that needs access to the file, not your user account. Please double check that.Torsten Meringer | http://www.mssccmfaq.de

What is the object name for the ConfigMgr provider? Thanks.

It's the computer account for the system hosting the SMS Provider.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

Alright, I have ensured that the computer account has R/W access to the file. I am still getting the same errors both in the Add Boot Image and in the Update Distribution Points wizard.

Share and NTFS permissions? How did you verify that?Torsten Meringer | http://www.mssccmfaq.de

In Share and Store Management, SYSTEM has read and write permissions set in both NTFS permissions and Share permissions.

Hi, Did you changed or updated anything to the boot image before you updating it? If you update the DP with boot image changed, then verify that only new network adapter or mass storage device drivers are updated. And check whether correct version of driver is updated. Thanks

No, the boot image I'm trying to load is basically the stock one provided with the install. Thanks!

Just for testing purposes: try mounting the boot image manually using dism /Mount-Wim on the siteserver.Torsten Meringer | http://www.mssccmfaq.de

Mounting the image also failed. Attached is the portion of the log file that begins to reference errors. 2011-07-12 13:02:13, Info DISM DISM Provider Store: PID=6184 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider 2011-07-12 13:02:37, Error DISM DISM WIM Provider: PID=6184 Failed to mount the image. - CWimImageInfo::Mount(hr:0x80070005) 2011-07-12 13:02:37, Error DISM DISM WIM Provider: PID=6184 d:\w7rtm\base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:999 - CWimManager::InternalOpMount(hr:0x80070005) 2011-07-12 13:02:37, Error DISM DISM WIM Provider: PID=6184 d:\w7rtm\base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:2247 - CWimManager::InternalCmdMount(hr:0x80070005) 2011-07-12 13:02:37, Error DISM DISM WIM Provider: PID=6184 Error executing command - CWimManager::InternalExecuteCmd(hr:0x80070005) 2011-07-12 13:02:37, Error DISM DISM WIM Provider: PID=6184 d:\w7rtm\base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:516 - CWimManager::ExecuteCmdLine(hr:0x80070005) 2011-07-12 13:02:37, Info DISM DISM.EXE: Image session has been closed. Reboot required=no. 2011-07-12 13:02:37, Info DISM DISM.EXE: 2011-07-12 13:02:37, Info DISM DISM.EXE: <----- Ending Dism.exe session -----> EDIT: It occurs to me that the log is referencing the d: drive, which on this server is a currently empty DVD drive. Is this relevant?

that doesnt matter, where are your boot images stored ? if they are in a share called \\server\share\bootimages make sure that the SYSTEM account has full control of \\server\share (the root of the share) did you try that ? My step by step SCCM Guides I'm on Twitter > ncbrady

The SYSTEM account has full control of the root of the share, in both NTFS and Share permissions.

If you are using a UNC on Server 2008 or 2008 R2, it's not the SYSTEM account that needs share permissions, it's the actual AD computer account for the system holding the provider role because this is technically a network transaction. NTFS permissions using SYSTEM should be fine.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

Sorry if this is a trivial question, but how would I determine the AD computer account name? I'm assuming that's not the same thing as the computer name, as I've tried adding that to no avail. Thanks for your time.

It is the same as the computer name. Where did you try adding it? Have you tried opening a command-prompt as the local system on the system hosting the SMS Provider (using PSExec) and testing it manually?Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

I have tried adding it in the permissions dialog for the share. Where might I find the SMS Provider on the local system? In other words, what should I be running with PSExec?

psexec -i -s cmd.exe this starts a command prompt in Local System context and you can then try doing a dir of the unc where the boot image is, what output do you see ? My step by step SCCM Guides I'm on Twitter > ncbrady

It appears to be the expected directory listing of the files, there are no errors or access messages.

EDIT: It occurs to me that the log is referencing the d: drive, which on this server is a currently empty DVD drive. Is this relevant? Did you try to mount the image locally or over the network? Did you also try to mount the WIM that Niall mentioned? ("D:\Win7rtm" does not matter; it's just an error message of dism).Torsten Meringer | http://www.mssccmfaq.de

I believe I was trying to mount it locally... Does DISM accept UNC paths as valid? Also, I did attempt to mount the WIM suggested, with the same results.

does anyone solve the problem? I encountered the same problem. "Failed to insert OSD binaries into the WIM file" few days before I can use it update,, but now can't , I try to re-install WAIK several tiems still exist. thanks feiout

This isn't a generic problem, there is no one solution as it will be very specific to your configuration. Reinstalling WAIK is not the answer though. Please start a new thread with a lot more details including error messages and log dumps.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

Jason is right, this is a hard one to troubleshoot without logs a specific config. I have had this issue myself a few times and it was always when I made changes to the boot WIM outside of the SCCM console (i.e. via DISM or similar). I had all sorts of trouble when I recently tried integrating 802.1x binaries into boot WIMs, and then updated distribution points. There is a way around it by 'reloading' the boot WIM and then selecting 'Refresh on dist points' rather than update (which rebuilds it). If your site and boot images are relatively new, I would consider uninstalling the PXE SP role from your server, Uninstalling WDS, reinstalling WDS and reinstall PXE SP. Reimport your boot images from the WAIK. This may help get you back to a baseline that you can work from then. Goodluck,

Hi Scott, follow your guide still can't not slove the problem . I had create a new POST here, thanks for answer. http://social.technet.microsoft.com/Forums/en/configmgrosd/thread/93bd9134-7a45-4b16-8666-fdc8554877a7 Feiout

I have discovered the error with my particular instance of this problem. Our server was running McAfee Enterprise v. 8.8, which was interfering with the installation process. Below is the relevant Windows error log: Log Name: Application Source: McLogEvent Date: 7/29/2011 3:40:50 PM Event ID: 257 Task Category: None Level: Information Keywords: Classic User: SYSTEM Computer: COMPNAMEHERE Description: Blocked by access protection rule. Access to object C:\Windows\TEMP\BootImages\{1738FB53-FAC1-438B-99CC-1A3DBA20CA0B}\mount\Windows\winsxs\x86_microsoft-windows-csrss_31bf3856ad364e35_6.1.7600.16385_none_58ba39fb456943bd\csrss.exe was blocked by rule Anti-virus Standard Protection:Prevent Windows Process spoofing. Thanks, everyone, for all your help and input!

way to go Mcafee, at least we see now that it wasn't a ConfigMgr problem but AV software getting in the way of progress, thanks for the update My step by step SCCM Guides I'm on Twitter > ncbrady