arvin

I'm having that same problem also. Very annoying!! Can anyone please help?

HI there, I'm having the same issue. Could you please go into what you did to resolve this issue? Thanks AL

Update: A little patient and it worked. --------------------------------------------------------------------------------------------- I had configured my environment according to this guide. SCCM server with WSUS installed. Standalone environment. - It sync with Microsoft update server and downloaded correctly. - When ADR runs, it downloads and create the package correctly. - According to the report, Scan was completed successfully on the client running windows 7. - States for a deployment and computer report also shows all necessary information correctly. - checked local gpo and it's been pointed correctly to the sccm2012 server by the SCCM agent. - Application was deployed to the machine and installed successfully. However, when I run Software Centre, I do not see any software been published nor can I click on anything to install it. Is there anything I did wrong or can I check? Thanks heaps.

Update 2: Is it me not installing it right ? or Does it (SCCM 2012) require certain magic before it will work? After my last update, I was able to import all OS images. (Windows 7 and 8) However, Build and Capture failed to work. (It was working before.) Therefore I then try to check the report and see what exactly went wrong. Only then discovered Reports weren't working either!! The installation sequence for this trial was SCCM 2012 SP1 -> CU1 -> CU2 -> Configure bounndaries -> following the guide until build and capture and then somewhere around here I added the reporting role. After finding this annoying issue, I revert everything back again and install it with the following sequence. SCCM 2012 SP1 -> Install reporting, catalog roles, test reporting working, reboot > CU1, reboot, test reporting working > CU2, reboot, test reporting ,working again > I will go ahead and follow the guide again. am I the only person who is experiencing this issue?? My environment is Vmware ESXi 5.1 with Windows 2008 R2 and Windows 2008 SQL ==================================================================================== I just test it again and it's showing that same error message for all wim files!!! All possible location I can try, local, network, and all...... Is this a bug or have I done something wrong which killed it?! :( This is really odd. I'm rebuilding the whole server again! Update: It's working again after I rebuilt the server. However, I am not importing Windows 8 Pro image this time. I have no idea what's the cause of this issue though.

Yes, It does. As I mentioned, it worked with different images located at \\bafflo\software$\Installers\Microsoft\Windows 8\WIN8X64PRO\Sources\install.wim and \\bafflo\software$\Installers\Microsoft\Windows 7\WIN7X64\Sources\install.wim and \\bafflo\software$\Installers\Microsoft\Windows 7\WIN7X86\Sources\install.wim I also tried coping the entire folder to the server and create a share that way. Same thing.

Thanks for replying, really appreciated. It was just a normal UNC path. I type it in and then browse to the install.wim file manually. \\bafflo\software$\Installers\Microsoft\Windows 8\WIN8X64\Sources\install.wim I have also tried to copy the entire directory to the local machine, also failed to load. There's another copy of Windows 8 Pro within the same location under \\bafflo\software$\Installers\Microsoft\Windows 8\WIN8PRO\ and it loaded fine. These Windows 8 Enterprise ISOs I just downloaded were not available from the site. I believe it was only made available recently by Microsoft. Therefore I thought it might be the problem with my ADK, so then I installed the latest package for Windows 8.1 Preview, It still fails. Log from SMSProv.log shows *~*~e:\qfe\nts\sms\siteserver\sdk_provider\smsprov\sspimagepackage.cpp(586) : Failed to get the image property from the source WIM file due to error 80070002~*~* SMS Provider 1/08/2013 8:26:56 AM 852 (0x0354)*~*~Failed to get the image property from the source WIM file due to error 80070002 ~*~* SMS Provider 1/08/2013 8:26:56 AM 852 (0x0354)

I'm trying to import the install.wim for Windows 8 Enterprise. It failed with "The specified UNC path does not contain a valid WIM file or you do not have permission to access it. Specify a valid path." The permission is not an issue. I tried to load the wim file using Windows System Image Manager and it's giving another error message. "Error Opening Windows image at ............with the detail log attached below: 1:06 PM : This application requires version 6.2.9200.16384 of the Windows ADK. Install this version to correct the problem 1:06 PM : 1:06 PM : Error opening Windows image at Y:\Installers\Microsoft\Windows 8\Win8X86\sources\install.wim. 1:06 PM : 1:06 PM : System.ComponentModel.Win32Exception (0x80004005): Reached the end of the file at Microsoft.ComponentStudio.ComponentPlatformInterface.WimFileHandle..ctor(String wimPath) at Microsoft.ComponentStudio.ComponentPlatformInterface.WimInfo..ctor(String wimPath) at Microsoft.ComponentStudio.ComponentPlatformInterface.Cpi.OpenWim(String wimPath) at Microsoft.ComponentStudio.ImagePicker.GetImageInfoFromPath(String path) at Microsoft.ComponentStudio.ImagePicker.ValidateImageFileOrFolder(String fileOrFolder) ========================================================================= I've checked version for the installed Windows ADK and it's exactly 6.2.9200.16384. I don't see a newer version of windows ADK available anywhere on the net. Does anyone know what's happening with this issue?

Hi all, Update: This question was too stupid to answer. Of course all updates needs to be downloaded by my server B before server A can grab the files and package it. All good now. cheers Environment: I have two server A and B. A : Standalone Primary Site, Installed with SCCM 2012 SP1 CU1 + SQL 2008 R2 SP2 + WSUS 3.0 SP2 console only and all necessary updates B: Site system server, installed with WSUS 3.0 SP2 and all necessary updates. B server is configured with the "Software update Point" role. A isn't. B server is configured through SCCM to sync with Microsoft Update and store it locally. ================================================================ B server had synchronized successfully with Microsoft and all updates appeared on Server A under "Software Library" Step 1 from the SUP guide on this forum suggested to also install SUP on the primary server. "Note: Repeat the above on the Primary server P01." However, it was a CAS and Primary Situation, which I don't think applicable to my setup. I am planning to manage all Microsoft Updates through SCCM. Do I need to install SUP on my SCCM server (Server A), in order to deploy Microsoft Updates to all clients? If not, will they (server A and B sync automatically)? When I try to create software deployment package, it's asking me about the "Package Source", "source location for software updates" It failes when I tried to specifiy to download it from the internet or point it to the WSUS server contentshare. What should I do?? From my remote WSUS server with SUP installed, Should I untick "Download update files to this server only when updates are approved"? Update: From Microsoft Site: Configuring Software Updates in Configuration Manager - The software update point is required on the central administration site and on the primary sites in order to enable software updates compliance assessment and to deploy software updates to clients. The software update point is optional on secondary sites. The software update point site system role must be created on a server that has WSUS installed. - Starting with Configuration Manager SP1, you have the option to synchronize software updates from a WSUS server that is not in your Configuration Manager hierarchy. - Sarting with Configuration Manager SP1, you have the option to add multiple software update points at a site.

Hi Bill, Did you find out the answer to your question?

Update: This question was too stupid to answer. Of course all updates needs to be downloaded by my server B before server A can grab the files and package it. All good now. Thanks for the lovely guide. I am getting quite confused wtih these WSUS/SUP roles and hope someone can point me to the right direction. ========================================================================= I have two server A and B. A : Standalone Primary Site, Installed with SCCM 2012 SP1 CU1 + SQL 2008 R2 SP2 + WSUS 3.0 SP2 console only and all necessary updates B: Site system server, installed with WSUS 3.0 SP2 and all necessary updates. B server is configured with the "Software update Point" role. A isn't. B server is configured through SCCM to sync with Microsoft Update and store it locally. B server had synchronized successfully with Microsoft and all updates appeared on Server A under "Software Library" Step 1 from this guide suggested to also install SUP on the primary server. "Note: Repeat the above on the Primary server P01." I am planning to manage all Microsoft Updates through SCCM. Do I need to install SUP on my SCCM server (Server A), in order to deploy Microsoft Updates to all clients? If not, will they (server A and B sync automatically? When I try to create software deployment package, it's asking me about the "Package Source", "source location for software updates" Should I point the source to \\WSUS\WSUSContent instead of downloading it again from the Internet? or? I will continue to read other posts, perhaps there are answers somewhere out there. Thanks in advance. Update: From Microsoft Site: Configuring Software Updates in Configuration Manager - The software update point is required on the central administration site and on the primary sites in order to enable software updates compliance assessment and to deploy software updates to clients. The software update point is optional on secondary sites. The software update point site system role must be created on a server that has WSUS installed. - Starting with Configuration Manager SP1, you have the option to synchronize software updates from a WSUS server that is not in your Configuration Manager hierarchy. - Sarting with Configuration Manager SP1, you have the option to add multiple software update points at a site.

Thanks for answering. Answer to my own question. No, there's no need to install SUP on my primary server for updates to populate to SCCM. Update: This question was too stupid to answer. Of course all updates needs to be downloaded by my server B before server A can grab the files and package it. All good now.

hi Guys, Please help. I have two server A and B. A : Standalone Primary Site, Installed with SCCM 2012 SP1 CU1 + SQL 2008 R2 SP2 + WSUS 3.0 SP2 console only and all necessary updates B: Site system server, installed with WSUS 3.0 SP2 and all necessary updates. B server is configured with the "Software update Point" role. A isn't. B server is configured through SCCM to sync with Microsoft Update and store it locally. B server had synchronized successfully with Microsoft and all updates appeared on Server A under "Software Library" Step 1 from this guide suggested to also install SUP on the primary server. "Note: Repeat the above on the Primary server P01." I am planning to manage all Microsoft Updates through SCCM. Do I need to install SUP on my SCCM server (Server A), in order to deploy Microsoft Updates to all clients? If not, will they (server A and B sync automatically? When I try to create software deployment package, it's asking me about the "Package Source", "source location for software updates" Should I point the source to \\WSUS\WSUSContent instead of downloading it again from the Internet? or? I will continue to read other posts, perhaps there are answers somewhere out there. Thanks in advance. Update: From Microsoft Site: Configuring Software Updates in Configuration Manager - The software update point is required on the central administration site and on the primary sites in order to enable software updates compliance assessment and to deploy software updates to clients. The software update point is optional on secondary sites. The software update point site system role must be created on a server that has WSUS installed. - Starting with Configuration Manager SP1, you have the option to synchronize software updates from a WSUS server that is not in your Configuration Manager hierarchy. - Sarting with Configuration Manager SP1, you have the option to add multiple software update points at a site.

Problem Resolved and Information below for anyone who might need it. It turns out to be driver issue indeed. Firstly, I was having problem injecting "some" drivers into my boot image despite the instruction says I only need the WinPE3.0 driver set. So I thought perhaps the drivers aren't enough, therefore tried to inject more from Intel, Dell and whatever you can name it. However, after making my boot image huge and slow, it still refuses to work!!! Did a quick search on why drivers gets refused from entering into the driver, I found the following patch from Microsoft. http://support.microsoft.com/kb/978754 The whole reason why these drivers were rejected because they are signed for Windows 7 OS in SCCM only and therefore TS failed because of it. So I applied the patch, removed all imported drivers, import only the WINPE3.0 drivers and it works beautifully. Hooray!!!

Hi Eswar, Thanks for replying I uses their WINPE3.0 Driver pack (.cab) but it didn't covers it I guess. I downloaded their CAB driver file also and I did notice that those Intel drivers failed to get injected with error saying the platform are not supported for both x86 and x64. I am not too sure why though. I did try to find where those pxe logs are, but couldn't find any. Could you point me to the right direction?

Hi there, I am having a very strange issue with my environment. I am sure the experts here will be able to help me. Please bare with me as I am quite new with SCCM. I have an SCCM 2007 SP2 with R3 installed. The default boot images are still available and I created two others. WINPE3.0 drivers were added to both x86 and x64 boot images. Two TS were created using x64 and x86 boot image to capture and build images. Problem: If I boot using VM machine (both x86 and x64), it boots correctly into the PE and prompt me for the protected password, build and capture the image with no issue. However, If I use physical machines with the same TS (x86), it boots fine into the PE, but it just sits there and eventually it will reboot. Press F8 and tried to run "tsbootshell", the windows comes up and then disappeared. If I boot it using the 64bit TS, it worked fine. Does anyone know what's going on? Am I missing anything? Drivers? or??? ================================= Update: It appears to be network driver issue I believe. When I run ipconfig, it comes up with no IP address. However, I had added all network drivers already into the boot images already though. Does anyone know how?