SCCM - not a valid .wim file?System Center Configuration Manger 2012 SP1 PXE bootHow do you conduct your SCCM updates?SCCM 2012 patching design - no subcollectionsChange SCCM Service Broker PortSCCM 2012 software updates failingSCCM - does captured image HW = deployed?SCCM migration error: “Failed to insert OSD binaries into the WIM file”SCCM 2012 Application Deployment Keeps FailingRemoving SCCM Offline Servicing schedules without a next run timefailed to get volume information sccm 2012
Must a warlock replace spells with new spells of exactly their Pact Magic spell slot level?
Do copyright notices need to be placed at the beginning of a file?
Are cells guaranteed to get at least one mitochondrion when they divide?
Why did Jon Snow admit his fault in S08E06?
Why do Russians almost not use verbs of possession akin to "have"?
Final exams: What is the most common protocol for scheduling?
Are runways booked by airlines to land their planes?
One word for 'the thing that attracts me'?
Sorting with IComparable design
The disk image is 497GB smaller than the target device
Why A=2 and B=1 in the call signs for Spirit and Opportunity?
Why is the Eisenstein ideal paper so great?
Why isn't Tyrion mentioned in the in-universe book "A Song of Ice and Fire"?
Gravitational Force Between Numbers
Is there any chance a man can get the death penalty for causing a miscarriage?
Is this homebrew "Cactus Grenade" cantrip balanced?
Is my plasma cannon concept viable?
Is it legal to have an abortion in another state or abroad?
Is "vegetable base" a common term in English?
Grade-school elementary algebra presented in an abstract-algebra style?
...And they were stumped for a long time
How would a developer who mostly fixed bugs for years at a company call out their contributions in their CV?
Variable declaraton with extra in C
Why isn't 'chemically-strengthened glass' made with potassium carbonate? To begin with?
SCCM - not a valid .wim file?
System Center Configuration Manger 2012 SP1 PXE bootHow do you conduct your SCCM updates?SCCM 2012 patching design - no subcollectionsChange SCCM Service Broker PortSCCM 2012 software updates failingSCCM - does captured image HW = deployed?SCCM migration error: “Failed to insert OSD binaries into the WIM file”SCCM 2012 Application Deployment Keeps FailingRemoving SCCM Offline Servicing schedules without a next run timefailed to get volume information sccm 2012
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
Am attempting to start using SCCM 2012 to image and maintain new machines. Have unpacked a win7 x64 .iso file to a network share and am trying to add it to SCCM via the Software Library/Operating Systems/Operating System Images. When I navigate to the 'install.wim' file I get the message:
The specified UNC path does not contain a valid WIM file or you do not have
permission to access it. Specify a valid path.
My connection to the file server has all privileges (in so far as I can tell). I am able to create / delete files and folders on it as well as run applications. Looking at the file server I don't see any errors or other indications that permissions are lacking.
EDIT: went to 'file/properties' for install.wim. Updated to ensure that everybody has full control. Note that there isn't an associated 'open with' for the '.wim' file type. Is this a problem?
sccm-2012
asked May 9 '14 at 11:11
ethrbunnyethrbunny
1,35232663
add a comment |
Am attempting to start using SCCM 2012 to image and maintain new machines. Have unpacked a win7 x64 .iso file to a network share and am trying to add it to SCCM via the Software Library/Operating Systems/Operating System Images. When I navigate to the 'install.wim' file I get the message:
The specified UNC path does not contain a valid WIM file or you do not have
permission to access it. Specify a valid path.
My connection to the file server has all privileges (in so far as I can tell). I am able to create / delete files and folders on it as well as run applications. Looking at the file server I don't see any errors or other indications that permissions are lacking.
EDIT: went to 'file/properties' for install.wim. Updated to ensure that everybody has full control. Note that there isn't an associated 'open with' for the '.wim' file type. Is this a problem?
sccm-2012
asked May 9 '14 at 11:11
ethrbunnyethrbunny
1,35232663
1
Have you tried re-extracting the .wim file? Maybe it's just corrupt.
– MichelZ
May 9 '14 at 11:13
Just tried this. Same result.
– ethrbunny
May 9 '14 at 11:57
Agree with MichelZ, as long as you've checked the permissions, it is not uncommon for a .wim file to be corrupted during the extraction (or transfer) process.
– Get-HomeByFiveOClock
May 9 '14 at 13:43
1
Can you try moving it to a different fileserver?
– MDMoore313
May 16 '14 at 14:21
Both your admin workstation and the SCCM server need permission to access the path of your .wim. That means that unless you're deliberate about it, you can easily end up with your workstation having permission to access the file but the SCCM does not.
– alx9r
Jul 28 '15 at 14:37
add a comment |
Am attempting to start using SCCM 2012 to image and maintain new machines. Have unpacked a win7 x64 .iso file to a network share and am trying to add it to SCCM via the Software Library/Operating Systems/Operating System Images. When I navigate to the 'install.wim' file I get the message:
The specified UNC path does not contain a valid WIM file or you do not have
permission to access it. Specify a valid path.
My connection to the file server has all privileges (in so far as I can tell). I am able to create / delete files and folders on it as well as run applications. Looking at the file server I don't see any errors or other indications that permissions are lacking.
EDIT: went to 'file/properties' for install.wim. Updated to ensure that everybody has full control. Note that there isn't an associated 'open with' for the '.wim' file type. Is this a problem?
sccm-2012
asked May 9 '14 at 11:11
ethrbunnyethrbunny
1,35232663
Am attempting to start using SCCM 2012 to image and maintain new machines. Have unpacked a win7 x64 .iso file to a network share and am trying to add it to SCCM via the Software Library/Operating Systems/Operating System Images. When I navigate to the 'install.wim' file I get the message:
The specified UNC path does not contain a valid WIM file or you do not have
permission to access it. Specify a valid path.
My connection to the file server has all privileges (in so far as I can tell). I am able to create / delete files and folders on it as well as run applications. Looking at the file server I don't see any errors or other indications that permissions are lacking.
EDIT: went to 'file/properties' for install.wim. Updated to ensure that everybody has full control. Note that there isn't an associated 'open with' for the '.wim' file type. Is this a problem?
sccm-2012
sccm-2012
asked May 9 '14 at 11:11
ethrbunnyethrbunny
1,35232663
asked May 9 '14 at 11:11
ethrbunnyethrbunny
1,35232663
edited May 9 '14 at 12:02
ethrbunny
asked May 9 '14 at 11:11
ethrbunnyethrbunny
1,35232663
asked May 9 '14 at 11:11
ethrbunnyethrbunny
1,35232663
asked May 9 '14 at 11:11
ethrbunnyethrbunny
1,35232663
1,35232663
1
Have you tried re-extracting the .wim file? Maybe it's just corrupt.
– MichelZ
May 9 '14 at 11:13
Just tried this. Same result.
– ethrbunny
May 9 '14 at 11:57
Agree with MichelZ, as long as you've checked the permissions, it is not uncommon for a .wim file to be corrupted during the extraction (or transfer) process.
– Get-HomeByFiveOClock
May 9 '14 at 13:43
1
Can you try moving it to a different fileserver?
– MDMoore313
May 16 '14 at 14:21
Both your admin workstation and the SCCM server need permission to access the path of your .wim. That means that unless you're deliberate about it, you can easily end up with your workstation having permission to access the file but the SCCM does not.
– alx9r
Jul 28 '15 at 14:37
add a comment |
1
Have you tried re-extracting the .wim file? Maybe it's just corrupt.
– MichelZ
May 9 '14 at 11:13
Just tried this. Same result.
– ethrbunny
May 9 '14 at 11:57
Agree with MichelZ, as long as you've checked the permissions, it is not uncommon for a .wim file to be corrupted during the extraction (or transfer) process.
– Get-HomeByFiveOClock
May 9 '14 at 13:43
1
Can you try moving it to a different fileserver?
– MDMoore313
May 16 '14 at 14:21
Both your admin workstation and the SCCM server need permission to access the path of your .wim. That means that unless you're deliberate about it, you can easily end up with your workstation having permission to access the file but the SCCM does not.
– alx9r
Jul 28 '15 at 14:37
1
1
Have you tried re-extracting the .wim file? Maybe it's just corrupt.
– MichelZ
May 9 '14 at 11:13
Have you tried re-extracting the .wim file? Maybe it's just corrupt.
– MichelZ
May 9 '14 at 11:13
Just tried this. Same result.
– ethrbunny
May 9 '14 at 11:57
Just tried this. Same result.
– ethrbunny
May 9 '14 at 11:57
Agree with MichelZ, as long as you've checked the permissions, it is not uncommon for a .wim file to be corrupted during the extraction (or transfer) process.
– Get-HomeByFiveOClock
May 9 '14 at 13:43
Agree with MichelZ, as long as you've checked the permissions, it is not uncommon for a .wim file to be corrupted during the extraction (or transfer) process.
– Get-HomeByFiveOClock
May 9 '14 at 13:43
1
1
Can you try moving it to a different fileserver?
– MDMoore313
May 16 '14 at 14:21
Can you try moving it to a different fileserver?
– MDMoore313
May 16 '14 at 14:21
Both your admin workstation and the SCCM server need permission to access the path of your .wim. That means that unless you're deliberate about it, you can easily end up with your workstation having permission to access the file but the SCCM does not.
– alx9r
Jul 28 '15 at 14:37
Both your admin workstation and the SCCM server need permission to access the path of your .wim. That means that unless you're deliberate about it, you can easily end up with your workstation having permission to access the file but the SCCM does not.
– alx9r
Jul 28 '15 at 14:37
add a comment |
1 Answer
1
active
oldest
votes
Can I ask what command switches you used to create the .wim file with? Namely, I am looking for switches like /compress because I have found -in personal experience- that trying to compress .wim files during extraction can often lead to this type of problem. If space is not too much of an issue, try re-extracting the .wim with no compression. (it may mean a "thick" image may come out to roughly 8-10 GB in size vrs high compression of about 4-6GB)
Note* You mentioned that there is no known file association properties with the .wim file, this is normal behavior as .wim files can only be manipulated with specific tools:
1.) Windows ADK/Deployment and Imaging toolkit(s) - GUI
2.) Imagex - command line tool for Windows 2003-2008
3.) DISM - command line tool (replacing) ImageX - lots of options here rolled into one command line tool, definitely look it up if you are not already using this instead of the dated Imagex.
One thing to note, although I have not had problems with this before, but if you are using Imagex; and Server 2012 is supported to handle DISM created images, there may be something you may want to look into. Hope this helps.
answered May 9 '14 at 13:55
Get-HomeByFiveOClockGet-HomeByFiveOClock
373412
I didn't create the .wim file. This is the Windows 7 x64 installer.
– ethrbunny
May 9 '14 at 15:52
1
Well, there is the problem right there! Something to note: there are actually 2 separate .wim files that are required for SCCM to successfully deploy an image. The first .wim is just a specialized .wim file that loads a stripped down OS that allows the computer to download and install the actual image. The second .wim you need is one that you create that will be loaded into SCCM where you are experiencing the problem. technet.microsoft.com/en-us/library/hh825072.aspx check out this link to see how to create a .wim through CLI, otherwise, SCCM has a capture image feature built in.
– Get-HomeByFiveOClock
May 9 '14 at 16:05
Point being in that previous rant. Are you trying to add the correct .wim files to to correct places?
– Get-HomeByFiveOClock
May 9 '14 at 16:12
I have extracted the contents of the win 7 iso file to a network share. From here I'm trying to import the initial OS image. See step 3.7 here: toolzz.com/?p=879
– ethrbunny
May 9 '14 at 18:52
I checked the link, I do not see a section 3.7 though. :( But I think I know where you are getting stuck at. Just as a precaution, can you left-click the .wim file you are trying to import and check properties --> General --> Attributes and see anything funny going on there?
– Get-HomeByFiveOClock
May 9 '14 at 20:09
|
show 3 more comments
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f594114%2fsccm-not-a-valid-wim-file%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Can I ask what command switches you used to create the .wim file with? Namely, I am looking for switches like /compress because I have found -in personal experience- that trying to compress .wim files during extraction can often lead to this type of problem. If space is not too much of an issue, try re-extracting the .wim with no compression. (it may mean a "thick" image may come out to roughly 8-10 GB in size vrs high compression of about 4-6GB)
Note* You mentioned that there is no known file association properties with the .wim file, this is normal behavior as .wim files can only be manipulated with specific tools:
1.) Windows ADK/Deployment and Imaging toolkit(s) - GUI
2.) Imagex - command line tool for Windows 2003-2008
3.) DISM - command line tool (replacing) ImageX - lots of options here rolled into one command line tool, definitely look it up if you are not already using this instead of the dated Imagex.
One thing to note, although I have not had problems with this before, but if you are using Imagex; and Server 2012 is supported to handle DISM created images, there may be something you may want to look into. Hope this helps.
answered May 9 '14 at 13:55
Get-HomeByFiveOClockGet-HomeByFiveOClock
373412
I didn't create the .wim file. This is the Windows 7 x64 installer.
– ethrbunny
May 9 '14 at 15:52
1
Well, there is the problem right there! Something to note: there are actually 2 separate .wim files that are required for SCCM to successfully deploy an image. The first .wim is just a specialized .wim file that loads a stripped down OS that allows the computer to download and install the actual image. The second .wim you need is one that you create that will be loaded into SCCM where you are experiencing the problem. technet.microsoft.com/en-us/library/hh825072.aspx check out this link to see how to create a .wim through CLI, otherwise, SCCM has a capture image feature built in.
– Get-HomeByFiveOClock
May 9 '14 at 16:05
Point being in that previous rant. Are you trying to add the correct .wim files to to correct places?
– Get-HomeByFiveOClock
May 9 '14 at 16:12
I have extracted the contents of the win 7 iso file to a network share. From here I'm trying to import the initial OS image. See step 3.7 here: toolzz.com/?p=879
– ethrbunny
May 9 '14 at 18:52
I checked the link, I do not see a section 3.7 though. :( But I think I know where you are getting stuck at. Just as a precaution, can you left-click the .wim file you are trying to import and check properties --> General --> Attributes and see anything funny going on there?
– Get-HomeByFiveOClock
May 9 '14 at 20:09
|
show 3 more comments
Can I ask what command switches you used to create the .wim file with? Namely, I am looking for switches like /compress because I have found -in personal experience- that trying to compress .wim files during extraction can often lead to this type of problem. If space is not too much of an issue, try re-extracting the .wim with no compression. (it may mean a "thick" image may come out to roughly 8-10 GB in size vrs high compression of about 4-6GB)
Note* You mentioned that there is no known file association properties with the .wim file, this is normal behavior as .wim files can only be manipulated with specific tools:
1.) Windows ADK/Deployment and Imaging toolkit(s) - GUI
2.) Imagex - command line tool for Windows 2003-2008
3.) DISM - command line tool (replacing) ImageX - lots of options here rolled into one command line tool, definitely look it up if you are not already using this instead of the dated Imagex.
One thing to note, although I have not had problems with this before, but if you are using Imagex; and Server 2012 is supported to handle DISM created images, there may be something you may want to look into. Hope this helps.
answered May 9 '14 at 13:55
Get-HomeByFiveOClockGet-HomeByFiveOClock
373412
I didn't create the .wim file. This is the Windows 7 x64 installer.
– ethrbunny
May 9 '14 at 15:52
1
Well, there is the problem right there! Something to note: there are actually 2 separate .wim files that are required for SCCM to successfully deploy an image. The first .wim is just a specialized .wim file that loads a stripped down OS that allows the computer to download and install the actual image. The second .wim you need is one that you create that will be loaded into SCCM where you are experiencing the problem. technet.microsoft.com/en-us/library/hh825072.aspx check out this link to see how to create a .wim through CLI, otherwise, SCCM has a capture image feature built in.
– Get-HomeByFiveOClock
May 9 '14 at 16:05
Point being in that previous rant. Are you trying to add the correct .wim files to to correct places?
– Get-HomeByFiveOClock
May 9 '14 at 16:12
I have extracted the contents of the win 7 iso file to a network share. From here I'm trying to import the initial OS image. See step 3.7 here: toolzz.com/?p=879
– ethrbunny
May 9 '14 at 18:52
I checked the link, I do not see a section 3.7 though. :( But I think I know where you are getting stuck at. Just as a precaution, can you left-click the .wim file you are trying to import and check properties --> General --> Attributes and see anything funny going on there?
– Get-HomeByFiveOClock
May 9 '14 at 20:09
|
show 3 more comments
Can I ask what command switches you used to create the .wim file with? Namely, I am looking for switches like /compress because I have found -in personal experience- that trying to compress .wim files during extraction can often lead to this type of problem. If space is not too much of an issue, try re-extracting the .wim with no compression. (it may mean a "thick" image may come out to roughly 8-10 GB in size vrs high compression of about 4-6GB)
Note* You mentioned that there is no known file association properties with the .wim file, this is normal behavior as .wim files can only be manipulated with specific tools:
1.) Windows ADK/Deployment and Imaging toolkit(s) - GUI
2.) Imagex - command line tool for Windows 2003-2008
3.) DISM - command line tool (replacing) ImageX - lots of options here rolled into one command line tool, definitely look it up if you are not already using this instead of the dated Imagex.
One thing to note, although I have not had problems with this before, but if you are using Imagex; and Server 2012 is supported to handle DISM created images, there may be something you may want to look into. Hope this helps.
answered May 9 '14 at 13:55
Get-HomeByFiveOClockGet-HomeByFiveOClock
373412
Can I ask what command switches you used to create the .wim file with? Namely, I am looking for switches like /compress because I have found -in personal experience- that trying to compress .wim files during extraction can often lead to this type of problem. If space is not too much of an issue, try re-extracting the .wim with no compression. (it may mean a "thick" image may come out to roughly 8-10 GB in size vrs high compression of about 4-6GB)
Note* You mentioned that there is no known file association properties with the .wim file, this is normal behavior as .wim files can only be manipulated with specific tools:
1.) Windows ADK/Deployment and Imaging toolkit(s) - GUI
2.) Imagex - command line tool for Windows 2003-2008
3.) DISM - command line tool (replacing) ImageX - lots of options here rolled into one command line tool, definitely look it up if you are not already using this instead of the dated Imagex.
One thing to note, although I have not had problems with this before, but if you are using Imagex; and Server 2012 is supported to handle DISM created images, there may be something you may want to look into. Hope this helps.
answered May 9 '14 at 13:55
Get-HomeByFiveOClockGet-HomeByFiveOClock
373412
answered May 9 '14 at 13:55
Get-HomeByFiveOClockGet-HomeByFiveOClock
373412
answered May 9 '14 at 13:55
Get-HomeByFiveOClockGet-HomeByFiveOClock
373412
answered May 9 '14 at 13:55
Get-HomeByFiveOClockGet-HomeByFiveOClock
373412
373412
I didn't create the .wim file. This is the Windows 7 x64 installer.
– ethrbunny
May 9 '14 at 15:52
1
Well, there is the problem right there! Something to note: there are actually 2 separate .wim files that are required for SCCM to successfully deploy an image. The first .wim is just a specialized .wim file that loads a stripped down OS that allows the computer to download and install the actual image. The second .wim you need is one that you create that will be loaded into SCCM where you are experiencing the problem. technet.microsoft.com/en-us/library/hh825072.aspx check out this link to see how to create a .wim through CLI, otherwise, SCCM has a capture image feature built in.
– Get-HomeByFiveOClock
May 9 '14 at 16:05
Point being in that previous rant. Are you trying to add the correct .wim files to to correct places?
– Get-HomeByFiveOClock
May 9 '14 at 16:12
I have extracted the contents of the win 7 iso file to a network share. From here I'm trying to import the initial OS image. See step 3.7 here: toolzz.com/?p=879
– ethrbunny
May 9 '14 at 18:52
I checked the link, I do not see a section 3.7 though. :( But I think I know where you are getting stuck at. Just as a precaution, can you left-click the .wim file you are trying to import and check properties --> General --> Attributes and see anything funny going on there?
– Get-HomeByFiveOClock
May 9 '14 at 20:09
|
show 3 more comments
I didn't create the .wim file. This is the Windows 7 x64 installer.
– ethrbunny
May 9 '14 at 15:52
1
Well, there is the problem right there! Something to note: there are actually 2 separate .wim files that are required for SCCM to successfully deploy an image. The first .wim is just a specialized .wim file that loads a stripped down OS that allows the computer to download and install the actual image. The second .wim you need is one that you create that will be loaded into SCCM where you are experiencing the problem. technet.microsoft.com/en-us/library/hh825072.aspx check out this link to see how to create a .wim through CLI, otherwise, SCCM has a capture image feature built in.
– Get-HomeByFiveOClock
May 9 '14 at 16:05
Point being in that previous rant. Are you trying to add the correct .wim files to to correct places?
– Get-HomeByFiveOClock
May 9 '14 at 16:12
I have extracted the contents of the win 7 iso file to a network share. From here I'm trying to import the initial OS image. See step 3.7 here: toolzz.com/?p=879
– ethrbunny
May 9 '14 at 18:52
I checked the link, I do not see a section 3.7 though. :( But I think I know where you are getting stuck at. Just as a precaution, can you left-click the .wim file you are trying to import and check properties --> General --> Attributes and see anything funny going on there?
– Get-HomeByFiveOClock
May 9 '14 at 20:09
I didn't create the .wim file. This is the Windows 7 x64 installer.
– ethrbunny
May 9 '14 at 15:52
I didn't create the .wim file. This is the Windows 7 x64 installer.
– ethrbunny
May 9 '14 at 15:52
1
1
Well, there is the problem right there! Something to note: there are actually 2 separate .wim files that are required for SCCM to successfully deploy an image. The first .wim is just a specialized .wim file that loads a stripped down OS that allows the computer to download and install the actual image. The second .wim you need is one that you create that will be loaded into SCCM where you are experiencing the problem. technet.microsoft.com/en-us/library/hh825072.aspx check out this link to see how to create a .wim through CLI, otherwise, SCCM has a capture image feature built in.
– Get-HomeByFiveOClock
May 9 '14 at 16:05
Well, there is the problem right there! Something to note: there are actually 2 separate .wim files that are required for SCCM to successfully deploy an image. The first .wim is just a specialized .wim file that loads a stripped down OS that allows the computer to download and install the actual image. The second .wim you need is one that you create that will be loaded into SCCM where you are experiencing the problem. technet.microsoft.com/en-us/library/hh825072.aspx check out this link to see how to create a .wim through CLI, otherwise, SCCM has a capture image feature built in.
– Get-HomeByFiveOClock
May 9 '14 at 16:05
Point being in that previous rant. Are you trying to add the correct .wim files to to correct places?
– Get-HomeByFiveOClock
May 9 '14 at 16:12
Point being in that previous rant. Are you trying to add the correct .wim files to to correct places?
– Get-HomeByFiveOClock
May 9 '14 at 16:12
I have extracted the contents of the win 7 iso file to a network share. From here I'm trying to import the initial OS image. See step 3.7 here: toolzz.com/?p=879
– ethrbunny
May 9 '14 at 18:52
I have extracted the contents of the win 7 iso file to a network share. From here I'm trying to import the initial OS image. See step 3.7 here: toolzz.com/?p=879
– ethrbunny
May 9 '14 at 18:52
I checked the link, I do not see a section 3.7 though. :( But I think I know where you are getting stuck at. Just as a precaution, can you left-click the .wim file you are trying to import and check properties --> General --> Attributes and see anything funny going on there?
– Get-HomeByFiveOClock
May 9 '14 at 20:09
I checked the link, I do not see a section 3.7 though. :( But I think I know where you are getting stuck at. Just as a precaution, can you left-click the .wim file you are trying to import and check properties --> General --> Attributes and see anything funny going on there?
– Get-HomeByFiveOClock
May 9 '14 at 20:09
|
show 3 more comments
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f594114%2fsccm-not-a-valid-wim-file%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Have you tried re-extracting the .wim file? Maybe it's just corrupt.
– MichelZ
May 9 '14 at 11:13
Just tried this. Same result.
– ethrbunny
May 9 '14 at 11:57
Agree with MichelZ, as long as you've checked the permissions, it is not uncommon for a .wim file to be corrupted during the extraction (or transfer) process.
– Get-HomeByFiveOClock
May 9 '14 at 13:43
1
Can you try moving it to a different fileserver?
– MDMoore313
May 16 '14 at 14:21
Both your admin workstation and the SCCM server need permission to access the path of your .wim. That means that unless you're deliberate about it, you can easily end up with your workstation having permission to access the file but the SCCM does not.
– alx9r
Jul 28 '15 at 14:37