Palmetto
-
Total Posts
:
14
- Scores: 2
-
Reward points
:
5360
- Joined: 9/14/2010
-
Status: offline
|
OSD Add Boot Image-'specified file cannot be imported'
Friday, August 26, 2011 1:28 PM
( permalink)
When running the OSD 'Add Boot Image' wizard, we're getting the ever-popular "The specified file can not be imported. Please make sure you have read and write access to the specified file and its folder." We're pretty sure we've identified the cause as renaming the folders that held the driver source files. We've tried the usual suspects - removing all drivers, reinstalling WAIK, reinstalling the original boot.wim files, checking the rights on the source directory, doing it all logged on the SCCM server as a local admin, etc. Here's the bizarre part: we can add the original 64-bit image and push it to the distribution points; it's just the 32-bit boot image that we can't add. The security is identical on the \boot\i386 and \boot\x64 directories and their contents. I've tried moving the 32-bit boot.wim into the x64 directory and pushing down the security, but that made no difference. Any suggestions? Also, can anyone tell us the log file for adding boot images?
<message edited by Palmetto on Friday, August 26, 2011 2:08 PM>
|
|
|
|
gjones
-
Total Posts
:
2291
- Scores: 136
-
Reward points
:
97820
- Joined: 6/5/2001
- Location: Ottawa, Ontario, Canada
-
Status: offline
|
Re:OSD Add Boot Image-'specified file cannot be imported'
Sunday, July 01, 2012 10:15 AM
( permalink)
Yes, I know this is an old post, I’m trying to clean up older posts that are unanswered. Did you ever figure this out?
|
|
|
|
josh02
-
Total Posts
:
2
- Scores: 0
-
Reward points
:
3740
- Joined: 9/1/2011
-
Status: offline
|
Re:OSD Add Boot Image-'specified file cannot be imported'
Monday, August 20, 2012 2:15 PM
( permalink)
I had this same issue but only on a server 2003 environment, my server 2008 environment had no issue. try restarting the Windows Management Instrumentation Service (WMI). Cheers
|
|
|
|