Greetings,

I'm trying to apply updates to my Windows 7 SP1 x64 Operating System Image.  SCCM 2012 SP1.

From the OfflineServicingMgr.log

Checking if update (20 of 56) with ID 16808244 needs to be applied on the image. 2 content binarie(s) are associated with the update.  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:30.489+420><thread=12784 (0x31F0)>
Applicability State = APPLICABLE, Update Binary = E:\ConfigMgr_OfflineImageServicing\c39fc94e-b976-41c9-8b8e-01ad700d8be2\windows6.1-kb2676562-x64.cab.  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:33.329+420><thread=12784 (0x31F0)>
Applying update with ID 16808244 on image at index 1.  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:33.329+420><thread=12784 (0x31F0)>
Failed to install update with error code -2146498512~  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:36.272+420><thread=12784 (0x31F0)>
InstallUpdate returned code 0x800f0830~  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:36.273+420><thread=12784 (0x31F0)>
STATMSG: ID=7911 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=ISTSCCM03.isllc.local SITE=P01 PID=2476 TID=12784 GMTDATE=Tue Jan 22 22:57:36.273 2013 ISTR0="16808244" ISTR1="P0100024" ISTR2="1" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:36.274+420><thread=12784 (0x31F0)>
Failed to install update with ID 16808244 on the image. ErrorCode = 2096  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:36.275+420><thread=12784 (0x31F0)>
Applicability State = APPLICABILITY_CHECK_NOT_SUPPORTED, Update Binary = E:\ConfigMgr_OfflineImageServicing\06d06abe-595b-4c15-909b-65bd368ae388\mpsyschk.exe.  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:36.276+420><thread=12784 (0x31F0)>
STATMSG: ID=7917 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=ISTSCCM03.isllc.local SITE=P01 PID=2476 TID=12784 GMTDATE=Tue Jan 22 22:57:36.277 2013 ISTR0="E:\ConfigMgr_OfflineImageServicing\06d06abe-595b-4c15-909b-65bd368ae388\mpsyschk.exe" ISTR1="16808244" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:36.278+420><thread=12784 (0x31F0)>
Not applying this update binary, it is not supported.   $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:36.280+420><thread=12784 (0x31F0)>
Checking if update (21 of 56) with ID 16808261 needs to be applied on the image. 1 content binarie(s) are associated with the update.  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:36.327+420><thread=12784 (0x31F0)>
Applicability State = APPLICABLE, Update Binary = E:\ConfigMgr_OfflineImageServicing\29f0e274-ad1d-4599-bf3d-0c8fa9064e76\windows6.1-kb2660649-x64.cab.  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:39.344+420><thread=12784 (0x31F0)>
Applying update with ID 16808261 on image at index 1.  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:39.345+420><thread=12784 (0x31F0)>
Failed to install update with error code -2146498512~  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:42.464+420><thread=12784 (0x31F0)>
InstallUpdate returned code 0x800f0830~  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:42.464+420><thread=12784 (0x31F0)>
STATMSG: ID=7911 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=ISTSCCM03.isllc.local SITE=P01 PID=2476 TID=12784 GMTDATE=Tue Jan 22 22:57:42.465 2013 ISTR0="16808261" ISTR1="P0100024" ISTR2="1" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:42.466+420><thread=12784 (0x31F0)>
Failed to install update with ID 16808261 on the image. ErrorCode = 2096  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:42.468+420><thread=12784 (0x31F0)>
Checking if update (22 of 56) with ID 16808368 needs to be applied on the image. 1 content binarie(s) are associated with the update.  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:42.650+420><thread=12784 (0x31F0)>
Applicability State = APPLICABLE, Update Binary = E:\ConfigMgr_OfflineImageServicing\96815fb1-35a9-4d82-bf16-f3d257800211\windows6.1-kb2656411-x64.cab.  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:45.644+420><thread=12784 (0x31F0)>
Applying update with ID 16808368 on image at index 1.  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:45.647+420><thread=12784 (0x31F0)>
Failed to install update with error code -2146498512~  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:48.699+420><thread=12784 (0x31F0)>
InstallUpdate returned code 0x800f0830~  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:48.700+420><thread=12784 (0x31F0)>
STATMSG: ID=7911 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=ISTSCCM03.isllc.local SITE=P01 PID=2476 TID=12784 GMTDATE=Tue Jan 22 22:57:48.700 2013 ISTR0="16808368" ISTR1="P0100024" ISTR2="1" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:48.703+420><thread=12784 (0x31F0)>
Failed to install update with ID 16808368 on the image. ErrorCode = 2096  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:48.704+420><thread=12784 (0x31F0)>
Checking if update (23 of 56) with ID 16808433 needs to be applied on the image. 1 content binarie(s) are associated with the update.  $$<SMS_OFFLINE_SERVICING_MANAGER><01-22-2013 15:57:48.712+420><thread=12784 (0x31F0)>

I can't seem to figure out why about 10 updates installed, and the rest just bomb out. I did go ahead and exclude all the folders from the antivirus, even though I'm running SCEP.

Thanks

Hello guys,

I have set up SCCM 2012 R2 about a year ago.

Captured and image and deployed it with all necessary programs to the clients. Then I have disabled "Build and Capture".

Now I wanted to capture again a win7 image. The problem is, I don`t understand it anymore how it works. Sounds crazy now. But in my documentation I have only written: PXE-Boot "Build and Capture" - modify operating system - capture.

But when I now boot in Build and Capture. It is going through all the points in the Task Sequence but doesn`t allow me to modify the operating systems. In my imagination the operating system booted up I could login in the windows 7 system modify what I wanted, shut off the system and captured it.

Now it is starting - Windows is finalizing things - Sysprep - Capture - End.

What do I miss? How can I stop the Task sequence, until I have modified the operating system in the way I would like to have it?

Thank you

Hi guys

I'm using SCCM 2012 R2 CU4. we have one standalone primary site with all the roles together on the server 

I have this weirdest issue. every few days I get this error at the beginning of an OSD process.

DownloadContentAndVerifyHash() failed. 80070002.

<![LOG[Set authenticator in transport]LOG]!><time="15:10:12.107-180" date="04-26-2015" component="OSDSetupHook" context="" type="0" thread="1044" file="libsmsmessaging.cpp:7734"><![LOG[WinHttp credentials set]LOG]!><time="15:10:12.107-180" date="04-26-2015" component="OSDSetupHook" context="" type="1" thread="1044" file="downloadcontent.cpp:796"><![LOG[CLibSMSMessageWinHttpTransport::Send: URL: ECA-SCCM.ECA.LOCAL:80  PROPFIND /SMS_DP_SMSPKG$/ECA00003]LOG]!><time="15:10:12.107-180" date="04-26-2015" component="OSDSetupHook" context="" type="1" thread="1044" file="libsmsmessaging.cpp:8604"><![LOG[Error. Status code 404 returned]LOG]!><time="15:10:12.123-180" date="04-26-2015" component="OSDSetupHook" context="" type="0" thread="1044" file="libsmsmessaging.cpp:8967"><![LOG[dwHttpResultCode >= 200 && dwHttpResultCode <= 299, HRESULT=80190194 (e:\nts_sccm_release\sms\framework\tscore\downloadcontent.cpp,824)]LOG]!><time="15:10:12.123-180" date="04-26-2015" component="OSDSetupHook" context="" type="0" thread="1044" file="downloadcontent.cpp:824"><![LOG[Http result: 404]LOG]!><time="15:10:12.123-180" date="04-26-2015" component="OSDSetupHook" context="" type="3" thread="1044" file="downloadcontent.cpp:824"><![LOG[SendResourceRequest() failed. 80190194]LOG]!><time="15:10:12.123-180" date="04-26-2015" component="OSDSetupHook" context="" type="3" thread="1044" file="downloadcontent.cpp:847"><![LOG[SendResourceRequest(), HRESULT=80190194 (e:\nts_sccm_release\sms\framework\tscore\downloadcontent.cpp,516)]LOG]!><time="15:10:12.123-180" date="04-26-2015" component="OSDSetupHook" context="" type="0" thread="1044" file="downloadcontent.cpp:516"><![LOG[oDavRequest.GetDirectoryListing (setDirs, setFiles), HRESULT=80190194 (e:\nts_sccm_release\sms\framework\tscore\resolvesource.cpp,2516)]LOG]!><time="15:10:12.123-180" date="04-26-2015" component="OSDSetupHook" context="" type="0" thread="1044" file="resolvesource.cpp:2516"><![LOG[Download() failed. 80190194.]LOG]!><time="15:10:12.123-180" date="04-26-2015" component="OSDSetupHook" context="" type="3" thread="1044" file="resolvesource.cpp:2534"><![LOG[DownloadContentAndVerifyHash() failed. 80070002.]LOG]!><time="15:10:12.123-180" date="04-26-2015" component="OSDSetupHook" context="" type="1" thread="1044" file="resolvesource.cpp:2963"><![LOG[DownloadContentAndVerifyHash ( pszPackageID, L"SMSPackage", saHttpContentSources, saSMBContentSources, saMulticastContentSources, sDestination, dwFlags, L"", 0, dwPackageFlags, mapNetworkAccess ), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\resolvesource.cpp,3052)]LOG]!><time="15:10:12.123-180" date="04-26-2015" component="OSDSetupHook" context="" type="0" thread="1044" file="resolvesource.cpp:3052"><![LOG[DownloadContentLocally (pszSource, sSourceDirectory, dwFlags, hUserToken, mapNetworkAccess), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\resolvesource.cpp,3273)]LOG]!><time="15:10:12.339-180" date="04-26-2015" component="OSDSetupHook" context="" type="0" thread="1044" file="resolvesource.cpp:3273"><![LOG[TS::Utility::ResolveSource(sClientPackageID, sClientPackagePath), HRESULT=80070002 (e:\nts_sccm_release\sms\client\osdeployment\osdgina\basesetuphook.cpp,1717)]LOG]!><time="15:10:12.339-180" date="04-26-2015" component="OSDSetupHook" context="" type="0" thread="1044" file="basesetuphook.cpp:1717"><![LOG[Failed to resolve package source "ECA00003"]LOG]!><time="15:10:12.339-180" date="04-26-2015" component="OSDSetupHook" context="" type="3" thread="1044" file="basesetuphook.cpp:1717"><![LOG[Exiting ConfigureEx: 0x80070002]LOG]!><time="15:10:12.339-180" date="04-26-2015" component="OSDSetupHook" context="" type="0" thread="1044" file="basesetuphook.cpp:1816"><![LOG[BaseSetupHook::configure(sWindowsDir), HRESULT=80070002 (e:\nts_sccm_release\sms\client\osdeployment\osdgina\osdsetuphook.cpp,292)]LOG]!><time="15:10:12.339-180" date="04-26-2015" component="OSDSetupHook" context="" type="0" thread="1044" file="osdsetuphook.cpp:292"><![LOG[Failed to configure OSD setup hook (0x80070002)]LOG]!><time="15:10:12.339-180" date="04-26-2015" component="OSDSetupHook" context="" type="3" thread="1044" file="osdsetuphook.cpp:292"><![LOG[Process completed with exit code 2147942402]LOG]!><time="15:10:12.339-180" date="04-26-2015" component="OSDSetupWindows" context="" type="1" thread="1360" file="commandline.cpp:1123"><![LOG[exitCode, HRESULT=80070002 (e:\nts_sccm_release\sms\client\osdeployment\setupwindows\setupwindows.cpp,617)]LOG]!><time="15:10:12.339-180" date="04-26-2015" component="OSDSetupWindows" context="" type="0" thread="1360" file="setupwindows.cpp:617"><![LOG[Configure hook failed with error code (80070002).]LOG]!><time="15:10:12.339-180" date="04-26-2015" component="OSDSetupWindows" context="" type="3" thread="1360" file="setupwindows.cpp:617"><![LOG[this->configureGina(this->sysDir), HRESULT=80070002 (e:\nts_sccm_release\sms\client\osdeployment\setupwindows\setupwindows.cpp,762)]LOG]!><time="15:10:12.339-180" date="04-26-2015" component="OSDSetupWindows" context="" type="0" thread="1360" file="setupwindows.cpp:762"><![LOG[this->installSetupHook(), HRESULT=80070002 (e:\nts_sccm_release\sms\client\osdeployment\setupwindows\setupwindows.cpp,452)]LOG]!><time="15:10:12.339-180" date="04-26-2015" component="OSDSetupWindows" context="" type="0" thread="1360" file="setupwindows.cpp:452"><![LOG[Failed to install setup hook (80070002)]LOG]!><time="15:10:12.339-180" date="04-26-2015" component="OSDSetupWindows" context="" type="3" thread="1360" file="setupwindows.cpp:452"><![LOG[setup.run(), HRESULT=80070002 (e:\nts_sccm_release\sms\client\osdeployment\setupwindows\setupwindows.cpp,1650)]LOG]!><time="15:10:12.339-180" date="04-26-2015" component="OSDSetupWindows" context="" type="0" thread="1360" file="setupwindows.cpp:1650"><![LOG[Exiting with code 0x80070002]LOG]!><time="15:10:12.339-180" date="04-26-2015" component="OSDSetupWindows" context="" type="1" thread="1360" file="setupwindows.cpp:1696"><![LOG[Process completed with exit code 2147942402]LOG]!><time="15:10:12.339-180" date="04-26-2015" component="TSManager" context="" type="1" thread="568" file="commandline.cpp:1123">

what I found out is that if I redistribute all the OS related packages to the DP - the problem resolves BUT it holds only for a few days.

after a few days I get the same error again and the only thing I could find is redistributing all the content again

• I don't have AV on my DP so I can't think of something that can modify the contentlib folder
• I already tried to remove the DP completely and create a new one
• I have only one DP in my environment, so I can't check it with another DP
• the SCCM is installed under Windows Server 2008 R2

couldn't find any solution online yet

hope to get one from here :)

thanks

Tamir Levy

SCCM 2012 R2 CU4

Recent change CU1-4

This was all working until recently. The SMSTS log shows no failures. The Netsetup.log has no entries. The Panther\setupact.log shows a few odd things " [msoobe.exe] Failed to open event to start up services [0x80070002]" but then appears to proceed fine.

The account used for Domain join is not locked out. I have no log telling me why it is not working. I have refreshed the drivers on the DP just incase the NIC driver got corrupt, though it appears to be fine in device manager and works.

I am just lost as I don't have any log that shows me any real failures and since SCCM passes the Domain Join off to the OS I don't know where else to look.

Hi,

We want to deploy a task sequence and run every package from the distribution point. However, this optio is not available. Probably due to this https://social.technet.microsoft.com/Forums/en-US/9686cfe8-7bf8-4fe5-90bb-73f43156b018/access-content-directly-from-a-distribution-point-when-needed-by-the-running-task-sequence-wim-file
= package not enabled for sharing on data access tab
My question:

how to find out which package it is or how to force this for all packages and trigger an update (Powershell?)

Please advise.
J

Jan Hoedt

I have a SCCM 2012 SP1 CU4 environments with Windows 7 SP1 computers.

I am deploying the machines using a task sequence, which all worked fine.

Now I want to Pre-Provision the laptops with BitLocker to save hours of time after the installation which is required for bitlocker the disk. So I want to speed things up.

I changed my current task sequence to use Pre-Provision which seems to work.......but....

After the machine is deployed I sometimes (!) got a D-drive which is the 500MB System Reserved boot partition.

My OS is properly installed on the C-drive...that is worinkg fine and the C-drive is also completely bitlockered.

But why is my boot disk (System reserverved) partition not hidden and does it contain a drive letter ???

Any ideas what goes wrong here ?

I checked the partition section in the task sequence and the 500MB disk should not get a drive letter. I configured it to not get a drive letter !

Could you problem be related to BIOS updates which are installed after the OS is installed during the task sequence ???

Strange however is that is sometimes goes wrong and sometimes OK......I could not found why :-(

I have a OSD task sequence with pre-provision of bitlocker and have created partitions following the images in this thread:

http://social.technet.microsoft.com/Forums/en-US/configmanagerosd/thread/7a9b6953-7dad-4935-b480-ce4b6f75e5a7

Pre-provision seems to be working, but the BDEDrive is assigned letter C: and the OSDisk gets D: although the BDEDrive should not be assigned a letter.

When the workstation is done installing the BDEDrive is visible. What am I doing wrong? I would like to end up with the os on C: and the BDEDrive not visible.

Carl

Hi,

With ConfigMgr 2007/2012 I used the bdehdcfg tool to partition the drive after the OS installation was done. This creates the bitlocker partition at the end of the drive, marked as system and boot, without a drive letter.

With ConfigMgr 2012 R2 there is a new option "pre-provision BitLocker" before windows is installed and "Enable BitLocker" at the end. This benefit of this option is basically zero encryption time, compared to the old method I was using which would take about an hour on a good sized SSD.

This new method creates a 350mb system reserved partition at the start of the drive, marks as system and boot AND assigns a drive letter. In the task sequence the "Partition Disk 0 - BIOS" task is set to "do not assign a drive letter to this partition". It seems that checking/unchecking this box does not have any effect whatsoever.

I've tried with various scripts to remove this default partition but unfortunately no success. The scripts work when run from an administrative command prompt on the desktop, however when running during a task sequence I get an access denied error (4005)

Does anyone have a suggestion on how to remove the drive letter from this default partition and/or how to get the task sequence to actually abide to the checkbox at the partition stage?

Thanks!

I read a post on the internet: Link

In here is explained that you can't Pre-Provisioning 2 disks win Windows 7 during OSD.....but is that still the case ?

Or is there a way to get this working ?

I have a system with 1TB disk. During deployment I pre-provisioning the OSDISK of 400GB. This takes seconds :-)

After finishing the deployment I encrypt the DATADISK which takes up to 6 hours although it is empty.

Is there a way to Pre-Provisioning both OSDISK and DATADISK during the WinPE phase and for Windows 7 ?

Any ideas ? How ?

We have recently introduced MDT 2013 for XP image deployment, Base image is successfully getting built on both Desktops & Laptops however, Application software are not getting installed on Laptops through SCCM. We have OUs created which is as follows: 

All Desktops are under: "Managed Objects/Managed Computers/Locations1/desktop 1..2..3 ect"

All Laptops are under:  "Managed Objects/Managed Computers/XP Laptops/Locations1/Laptop 1..2..3 ect"

We have been trying troubleshoot but not able to resolve this issue for a long time. could some pls advise where should we focus to investigate the root cause or if someone aware of this issue pls reply. It would a huge help.

If any more information required pls let me know i will provide it.

Hey Guys -

Our company has an extensive OSD Task Sequence which incorporates many scripts and custom processes.  For a variety of reasons, it's been decided that we start using Dell's ImageDirect.  In this scenario, once we unbox systems, they want OSD to still be applied - but to the existing image on the PC - not re-apply the OS

I created a Windows 7 image via imagedirect, downloaded it, and applied it to a test system.  Currently, it would boot to Windows' mini-setup if powered on.  I took our existing OSD TS and basically removed any steps where OSD applies the image, but steps which come after it that are still required are failing.

For example, for a test I did this afternoon, the "Apply Win7 Settings" step would fail which usually comes after Apply OS image, but as it's disabled, errored out with the below in logs:

Failed to read installation type from environment.. Please ensure you are running this executable inside a properly configured OS Deployment task sequence.
Unspecified error (Error: 80004005; Source: Windows)

As I found all of the info in that step is already in the ImageDirect image, I disabled it and tried again.  This time, it failed at the "Apply Network Settings" step.  These settings (including joining the domain) are obviously not in ImageDirect's image.

What is the best way to approach working with what I've been asked to do?  Thanks!

Ben K.

I don't think this is a cm2012 issue but I need to prove this before I throw it back to the networking team :-)   Over the weekend a new 4500 switch was added to our network.  Now, we are not able to build any workstations via OSD from any site. We have 8 DPs in different offices and nothing builds.  when you do build here is what happens.

F12 to boot from network (working)

Then it will not connect to any DP.  we see this error each time.    Can a new switch cause this on all DPs?  

mqh7

Hi everyone

We have Configuration Manager 2012 R2 and have task sequences for AD-joined computers with Windows 7 and Windows 8.1 These task sequences works fine. We have also task sequences for workgroup-joined computers with windows 7 and windows 8.1 and the problem with those two is that when they come to the step where it is going to install applications it fails with error code 80004005. The checkbox for Allow clients to connect anonymously is checked on the DP. Is there anyone who has an idea whats wrong?

Thanks in advance

Lasse

In the following scenario where there are 2 MP's - 1 is HTTPs and the other is HTTP, is there a way to specify which MP is used during PXE? Both MPs are in the same boundary group. (One primary site with 2 MPs).  Alphabetically, the HTTPs MP will be first in the list.

I've read this and I believe the answer to be no.

https://social.technet.microsoft.com/Forums/en-US/a5c0d086-c149-4b1a-95b0-6cbb633b4c5c/pxe-boot-osd-connects-to-internetonly-management-point-a-bug?forum=configmanagerosd

So, if this is correct, moving the HTTPs MP out of the boundary group and into another boundary group will accomplish nothing?

I assume then that this is also the case for site assignment - it doesn't matter what boundary group the MP is in, the client will always pick the HTTPs one first - as referenced here: (unless the MP is specified during client install)

http://blogs.msdn.com/b/ameltzer/archive/2013/06/17/quick-summary-on-how-management-point-selection-works-in-flexible-formerly-native-mode-in-configuration-manager-2012.aspx

There are several issue’s. but I hope you can help me with some of them.

I’m deploying Windows 8.1 from within SCCM 2012 R2, using the latest (oktober 2013) version for MDT 6.2.5019.0

I’ve created a MDT Task Sequence option “Client Task Sequence”, and didn’t change anything there.

Followed a hands-on example fromhttps://www.youtube.com/watch?v=wi1I2XfO11M

The Windows 8.1 OS is installed, but all kinds of failures came up:

-      Received an Application Discovery Warning in the UDI wizard designer, and none of the selected programms and applications where installed during running of the task sequence.

Looking at the logging aftherwards in AppDiscovery.log it showed

07:23:43.416 03-27-2014     3          AppDiscovery Error 2: Product version registry not found.

07:23:43.431 03-27-2014     2          AppDiscovery Opening file [\\AppDiscoveryresult.xml.app]

07:23:43.431 03-27-2014     3          AppDiscovery Error 1: File open failed

07:23:43.431 03-27-2014     3          AppDiscovery Error 33554432: Fatal error while processing master list:

07:23:43.431 03-27-2014     3          AppDiscovery Error 16: --| Failure while opening master list file.

07:23:43.431 03-27-2014     3          AppDiscovery Error 33685504: --| Failure to open file.

-      The Computername, which seems to be a very common error, is not correct. I’ve added “Computer-%serialnumber%” as a default value in UDI Wizard designer.

But stil during installation when the several deployment options where shown, it proposed MININT-xxxxxx.

Even changed this setting there, but still the computername remained MININT-xxxxxx when the installation completed.

-      The OS was installed on an E:\ volume instead on C:\. Even when I chose C:\ during installation.

There where several Volumes created. BDEDrive without a drive letter.

OSDisk with drive letter E:

CD-Rom Station with drive letter D:\

Hope you can help me with some of these issues.

I think this question has been asked before in other forums however I cannot seemed to find a resolution for this issue.

Some people say it cannot be fixed.

Anyway to the question.

As part of our SCCM UDI OSD build process  we install a number of applications through the UDI wizard including
adobe flash, adobe shockwave and Microsoft Office 2010. They show up in the wizard and in the deployment summary.

The msi install apps (such as flash and shockwave) are successfull and in the deployment window show up with a nice big green tick.

The other script based apps such as microsoft office (although succesfull installed) show up with an exclamation mark instead.

Because we will have a number of people imaging workstations with our UDI task sequence I would like to have Office also come up with Green ticks.

Does anyone know why Microsoft office does this?

is this something to do with success/failure codes as other forums have alluded to.

We use the office msi product id as the detection method for the install.

We are running sccm 2012 r2 cu1.

We are running MDT 2013 with integration.

Let me know if you need any more information.

Cheers

Greg Turnbull

Hi All,

I installed SCCM2012 SP1 on Server 2012 R2 version. During the installation process i forget to disable the Mcafee. Because of that i dont see the default boot images avaibale under Software Library -> Operating Systems -> Boot images. After doing some research i found that the images can be created. I followed the post - http://myitforum.com/myitforumwp/2013/08/01/how-to-create-configmgr-2012-boot-images-from-scratch/

I have WADK 8.1 installed on my server. I tried to add the boot images in the SCCM console, but it says specified UNC path does not contain a valid WIM image.

Not sure what am missing.

Regards,

Vinod



Hello All.....I am looking for a solution that allows me to deploy OS (7&8), Applications (Office, etc.) and User Settings onto laptops as quickly as possible.  What technologies would be required to implement such a solution.

Brief explanation:

OS:  Normal OS Installation.  How would the updates be managed? By adding a reference image that already has updates or through WSUS? What is best approach?

Applications:  Would it be possible to provide a portal to users from where they can select applications and install as per their need? Would it be good practice? OR App-V would be better?

User Settings:  We want to provide similar settings to all users along with the customizations that they make to their settings in the OS or other Apps?  Is it achievable through UE-V and practical?

BitLocker:  We want to utilize BitLocker as well.  What would be best approach to do it afterwards once the image is deployed?

I have little understanding of technologies that would be required, but would appreicate a detail account of it as to what technologies and number of services that would be required to complete this task.  Also, any reference to blog/article where I can read and clear my understanding of it would appreicated as well.  Thanks in advance.

Hi everyone,

I have a question regarding UEFI and architecture of boot images since I'm reading some contradictive information on the internet (probably due to old content): Is it possible to install a 32-bit OS on a X64 UEFI?

In some old posts, I came across some information that 32-bit OS is not supported for UEFI. I guess this is not true anymore, since technet states:

While in UEFI mode, the Windows version must match the PC architecture. A 64-bit UEFI PC can only boot 64-bit versions of Windows. A 32-bit PC can only boot 32-bit versions of Windows. In some cases, while in legacy BIOS mode, you may be able to run 32-bit Windows on a 64-bit PC, assuming the manufacturer supports 32-bit legacy BIOS mode on the PC.

Based on this information, could you guys please confirm these statemets and answer these questions so I know I've not misinterpreted the information:

• If legacy BIOS is still used and 32bit & 64bit OS need to be supported, it's "best"(most compatible) to use X86 boot image so both 32bit & 64bit OS can be installed.
• When your company must support 32bit & 64bit OS (due to some applications requiring 32bit), they can't use the same hardware when this hardware has a x64 UEFI (except when they can turn on legacy BIOS to install 32bit OS)? I assume x64 UEFI will be the standard option in the future or will this be x64/x86 supported UEFI?
• When deployment for 32bit & 64bit OS is required via UEFI, it's best to target the X64 boot image last so this is used by default (before you choose the TS)? When 32bit OS is required x86 bootable media can be used to install the 32bit OS on x86 UEFI as it is treated as an exception?
• What would be your advice for using BIOS/UEFI at the moment? Already switch to UEFI for windows 7 computers? I thought that "Secure Boot" wasn't possible for windows 7? The only benefit would be the faster boot times?

Thanks in advance!

Regards,

Sven