Windows 7 USB Build from SCCM 2012
Team, I've having real issues trying to get my head around what the issue could be with my Windows 7 Offline Media created from SCCM 2012, it appears to failing when trying to install Adobe Reader 11.0.14
But builds without issues when building over WAN/LAN, can you please assist me with trying to find out why the USB build is failing, is there anything im missing when creating the USB offline media using SCCM 2012 "create task sequence media" feature?
I've attached the smsts log file, in the hope you can guide me as to what the issue is
smsts-20160404-114036.log
But builds without issues when building over WAN/LAN, can you please assist me with trying to find out why the USB build is failing, is there anything im missing when creating the USB offline media using SCCM 2012 "create task sequence media" feature?
I've attached the smsts log file, in the hope you can guide me as to what the issue is
smsts-20160404-114036.log
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
thanks Mike T for your response,
I'm currently testing this ISO on a VM, hoping I can replicate the issue,
Just to be clear, this same task sequence works fine when I build using PXE over the LAN, no issues,
I created the USB Offline media using SCCM 2012, and extracted the ISO to a USB flash drive which we made bootable,
at this stage it's something specific to either USB device, or perhaps an issue with the extracted iso? as I don't understand how and why the same task sequence works when building over the LAN/PXE?
I'm currently testing this ISO on a VM, hoping I can replicate the issue,
Just to be clear, this same task sequence works fine when I build using PXE over the LAN, no issues,
I created the USB Offline media using SCCM 2012, and extracted the ISO to a USB flash drive which we made bootable,
at this stage it's something specific to either USB device, or perhaps an issue with the extracted iso? as I don't understand how and why the same task sequence works when building over the LAN/PXE?
Hi,
I just had a thought - doesn't happen often - you are using packages or applications. I had awful problems quite recently when we had lots of applications in the TS. A network (PXE) build worked well, but suddenly USB builds from the same TS fell over on an app. We disabled that and then it fell over on a different app. We flipped everything from apps to packages and now it works reliably on both PXE and USB. It's a known issue apparently but not known enough it seems!
We used the same source files, command lines etc, just migrated apps to packages. I used PowerShell which made it less painful, but it took a day as we had about 20 apps to install.
I'm pretty sure that will be your main problem.
Mike
I just had a thought - doesn't happen often - you are using packages or applications. I had awful problems quite recently when we had lots of applications in the TS. A network (PXE) build worked well, but suddenly USB builds from the same TS fell over on an app. We disabled that and then it fell over on a different app. We flipped everything from apps to packages and now it works reliably on both PXE and USB. It's a known issue apparently but not known enough it seems!
We used the same source files, command lines etc, just migrated apps to packages. I used PowerShell which made it less painful, but it took a day as we had about 20 apps to install.
I'm pretty sure that will be your main problem.
Mike
ASKER
the issue at this stage seems to be one particular application yes, which has a ton of dependencies.
Try swapping it for a package - Adobe Reader wasn't it? What dependencies does it have?
ASKER
nah, it's not Adobe Reader, its my clients document management suite,
it has things like .DOT Net 4.5 and Visual C++ 2008 redistribute which all installs as part the application, and it's set as dependency for one of the components,
in our case a Network PXE build works fine, I will have to look into how to move/convert that to an package, and still have all the dependencies, but thanks so far for your help
it has things like .DOT Net 4.5 and Visual C++ 2008 redistribute which all installs as part the application, and it's set as dependency for one of the components,
in our case a Network PXE build works fine, I will have to look into how to move/convert that to an package, and still have all the dependencies, but thanks so far for your help
ASKER
Mike T, just uploaded another AppEnforce Log file from my latest build attempt,
ASKER
I've copied the production TS sequence and made a few slight tweaks to it, just building another key now to test, I've not gone down the route to convert it to a package yet...
Is that relatively straight forward, given this particular App has quite a few dependencies?
Is that relatively straight forward, given this particular App has quite a few dependencies?
HI Craig,
I'm just looking at the log. It's straightforward for one app, but not sure about one with dependencies. One thing that strikes me is you are using CMD files to install most apps. Why?
CMD files and SCCM don't work well together. Your app for Chrome is perfect. Why is that one different?
I'm just looking at the log. It's straightforward for one app, but not sure about one with dependencies. One thing that strikes me is you are using CMD files to install most apps. Why?
CMD files and SCCM don't work well together. Your app for Chrome is perfect. Why is that one different?
ASKER
Honestly Mike T, im not sure, I stepped into this account with it in this state,
Our lead SOE Engineer converted all packages to applications as we were informed the new model works better with SCCM 2012, as opposed to using packages which is 2007 and earlier,
When applications are packaged, we always use the script method with an installer batch file to kick off the install, it seems to work pretty well?
Our lead SOE Engineer converted all packages to applications as we were informed the new model works better with SCCM 2012, as opposed to using packages which is 2007 and earlier,
When applications are packaged, we always use the script method with an installer batch file to kick off the install, it seems to work pretty well?
Right at the start of the log this step fails:
Performing detection of app deployment type Set Cache 20GB is failing. "PrepareCommandline failed with 0x87d01106 for cmdline". What is it meant to do? Set the CM client cache?
Performing detection of app deployment type Set Cache 20GB is failing. "PrepareCommandline failed with 0x87d01106 for cmdline". What is it meant to do? Set the CM client cache?
I was in almost the same position and made the same mistake. I happily changed packages to apps because "apps are better" and it worked for about two months. Then the Gremlins arrived and everything went wrong - USB builds were just horribly unreliable. We got a consultant in and against the grain I changed everything back to packages and Voila - it's 100% reliable.
As for CMD's - it's just not good method because of the error code. It's very limited, there's no error trapping without making the BAT file much more complicated and doesn't really give you anything.
If the CMD is just
@echo off
msiexec /i somefile.msi /qn
then there's no reason to use it. I know I'm giving you more work but it will make your TS more reliable and readable. When you switch the packages you see the command line directly instead of just "install.cmd". This makes it a lot easier to see typo's etc.
As for CMD's - it's just not good method because of the error code. It's very limited, there's no error trapping without making the BAT file much more complicated and doesn't really give you anything.
If the CMD is just
@echo off
msiexec /i somefile.msi /qn
then there's no reason to use it. I know I'm giving you more work but it will make your TS more reliable and readable. When you switch the packages you see the command line directly instead of just "install.cmd". This makes it a lot easier to see typo's etc.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I will split the points between u 2 as u took the time to look into this
ASKER
Figured this out myself, however appreciate the guys taking the time to respond, especially Mike
ASKER