Doubt about Report - Task Sequence - Deployments

Hello,
I have a doubt about this report Summary report for a task sequence deployment in Task Sequence - Deployments.
Last Friday I did deployed in 6 desktop ran this report and display my 6 desktop's all right.
Today a run this report and display no data.
Why occurred this? Anyone have idea?
I think this report have display me all data about my task sequence specific.
Thanks.

Are you sure the deployment wasn't deleted or recreated?
Query your DB and see what the NumberInstalled says. That should show you 6 were installed. You just need the Deployment ID added to this query below.
select *
from dbo.DeploymentSummary
where
OfferID = 'YOUR DEPLOYMENT ID HERE'
Best, Jacob I'm a PC.
My TS wasn't modified or recreated, but in DB display NumberInstalled = 0.
Anyone have modify this TS since last friday, I don't know the reason this happened.
I will do news deploys and see this report after if still have same issue.
Thanks your opinion.

Similar Messages

Confused about a task sequence - multiple applications - base name variables

Hello,
I am trying to get familiar in a new SCCM 2007 environment (badly documented I'm afraid). The TS used for computer deployment contains a long sequence of 'Install Software'-steps labled 'Install PACKAGES' (0 to 9). Within each of these the 'Install multiple
applications'-box is checked and a Base Name Variable has been given (PACKAGES0 -->9).
I have been reading about the mechanism behind defining variables in the CustomSettings.ini, but of all the CS.ini files I have found on the SCCM server I have not found traces of these variables.
I have found no collections with these variables.
So my question is: How to figure out what may be included in these ? What software is installed, if any?

When you deploy the task sequence to a computer, does it get any applications installed from these steps?
The variables can come from different sources, like:
1) Collections variables
2) Computer variables
3) Dynamically set variables, using either a custom script or MDT (CustomSettings.ini)
If the computers get any of the "unknown" packages installed, try looking in the smsts.log on the client.
This should also give you an indication, where the variables come from.
You can get all computer variables with this small PowerShell script - This can help you identify if the variables are set per computer:
$smsprovider = "Server01"
$sitecode = "CEN"
$objMachineSettings = gwmi -ComputerName “$smsProvider” -Namespace “root\sms\site_$siteCode” -class “sms_machinesettings”
$objMachineSettings.Get()
ForEach ($objComputerVar in $objMachineSettings.MachineVariables)
Write-Host "ResourceID:" $objMachineSettings.ResourceID "Variable:" $objComputerVar.Name "=" $objComputerVar.Value
-Heine

Doubt about Report Suite Office in SCCM 2012

Hi all,
I have a question about Suite Office in SCCM 2012.
Why in my report 07B - Computers that recently used a specified executable program
when I specific Office 2010 don't display nothing about Outlook?
Just display follows softwares: Word,Excel,PowerPoint,Visio and Project. Someone have idea?
Thanks.

Do you have Software Metering enabled for that executable?
Mike Leach | http://blogs.catapultsystems.com/mleach/default.aspx
Mike Thank's your opinion...my answer....Yes, I do.My software metering is OK.
My doubt is why Microsoft Outlook don't display as being part suite Office?
Is necessary I select Microsoft Outlook (separately) for do my software metering but I think this is not correct, because the correct is suite Office contains: Word,Excel,Visio,Project,Powerpoint
and Outlook...
So when I selected Microsoft Office 2010 display all softwares as I saw in my first post and any about Outlook.
Thanks any suggestions.

Doubt About Report Software Metering

Hello Guys,
I create my rule about metering for SoftwareX and is OK, run with success.
I have 2 computers(PC01,PC02) where I uninstall SoftwareX but when I run after 72hours Report: Computers that have run a specific metered software program ....still display PC01 and PC02 has SoftwareX metered.
My doubt is I set Software Metering Properties for 45 days, follow:
Will it take 45 days for PC1 and PC2 doesn't display more in my Report? Is this right?
If isn't right, how I can fix this for doesn't display SoftwareX if was uninstall in PC1 and PC2? My hardware inventory run ever 24hs and 24hs.
Thanks a lot.

Correct it will take ~45 days for the data to be removed from CM12.
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

Doubt about report FBL5N of screen field:Open items and Cleared items

hi
i know the report FBL5N is use DDF LDB and the report work flow is BSID->BKFP->BSEG
but i don't know to differentiate Open Items and Cleared items in this report.
Open items and Cleared items stand for a field flag in these table (BSID,BKFP,BSEG )? if true the field is?
or they must be calc in program ? if true what about calc rules?
waiting for help! thank you!

Hi,
Here is the difference in Open Items and Cleared Items.
In FI first the document is Open (when it is posted) so the entry is made in table BSID. Once the document is cleared, it will move from BSID to BSAD. And for Cleared item you will see Clearing Document no and Clearing date values updated (these are blank when the item is open).
The only difference in Open and Cleared is via Clearing Document and Clearing Date. If the values are present, it means document is cleared.
Hope this helps.
ashish
Message was edited by:
Ashish Gundawar

Doubt about Report:: Count users by domain

Guys,
when I run report: Count users by domain, display my domain XXX and some hostnames users logged in my domain and 15 users logged locally.
Well,some users after 2 weeks already logged in domain but in my report still display info user logged locally.
Why this?
Is there someone I do run manually for not display more this users now log on in domain but display logged locally? I think this only cache,but I don't want my report contains data wrong.
Any idea?
Thanks.

Hi,
If you are talking about the information in report "Users in a specific domain", the information are collected by hardware inventory. SCCM collects inventories on a periodic basis, not real-time. You could initiate Hardware Inventory Cycle from client to
accelerate the speed for updating data.
Best Regards,
Joyce Li
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Doubt about CURRENT LOG SEQUENCE NUMBER

I just want to know that why the "current log sequence number" is added to the header of each data file ? why oracle needs to do that ? as it is also added to the control file and whenever it needs to know the current log sequence number , it can get it from control file , then why to add this in the header of data files ?

For Recovery.
When you are doing a Recovery of a database where the datafiles have been restored from backups but the controlfile has been recreated (thus, the controlfile has no information about log sequence numbers and checkpoint scns), the Recovery must read this information from the datafile headers.
Say you have 5 datafiles and they have been backed up 6 months ago using ALTER TABLESPACE BEGIN BACKUP commands and, therefore, have different checkpoint SCNs. The checkpoint SCNs could be 1021, 1059, 1085, 1745, 2045.
How would Oracle know which Log Sequence Numbers are needed ? It knows that a Recovery must start with SCN 1021. But if the information about Log Sequence Numbers is not available in the controlfile (either because it is as of today and the controlfile doesn't store information about 6 months of redo logs OR because the controlfile has been recreated), what is the Log Sequence Number corresponding to that SCN 1021 ?
That information is available in the datafile header. You will NOT see it in V$DATAFILE or V$DATAFILE_HEADER. You will not see it in a level 1 dump of datafile headers.
You will see an example here :
http://web.singnet.com.sg/~hkchital/Incomplete_Recovery_with_BackupControlfile.doc
Hemant K Chitale
http://hemantoracledba.blogspot.com

OSD Task Sequence fails with "There are no task sequences available for this computer"

Let me preface this by saying that I have read at least 100 forum posts with people having similar issues. However, none of the solutions in those
posts have worked for me.
The Problem: SCCM 2012 R2 will not image unknown computers.
The task sequence gives the error "There are no task sequences available for this computer." As soon as that error occurs, SCCM places an Unknown entry into the All Systems collection. I have been imaging unknown computers, without fail, for
4 months and no environmental changes have been made. NOTE: I am using USB media, not PXE.
What I've Tried:
Checked for duplicate SMSBIOS GUIDS in the console, none.
Checked for duplicate MAC Addresses in the console, none.
Checked for expired certificates, none.
Recreated Boot Media, twice.
Deleted the Unknown entry and retried, SCCM just recreates the Unknown entry.
Deleted all of my task sequence deployments, and then redeployed them each to All Systems (Only Boot Media and PXE) and to Unknown Systems (Only Boot Media and PXE)
I have also ran the following in the SQL Server Management Studio;
SELECT
* FROM
ResPolicyMap WHERE
machineid = 0 and
PADBID IN
(SELECT
PADBID FROM PolicyAssignment
WHERE BodyHash
IS NULL)
No result
Select
* From
vMacAddresses Where
MacAddresses = '00:00:00:00:00:00'
This displays an entry for every time that I have tried to image the unknown machine attached to the MAC Address with a different ItemKey and SMS_Unique_Identifier for each entry.
Added the machine manually using Import Computer Information, immediately recognized the Task Sequences that I have advertised to the All Systems collection.
Any and all assistance is welcome, I am going on the third straight day of dead ends. Below I have tried my best to post the entire SMSTS Log;

LOGGING: Finalize process ID set to 744
==============================[ TSBootShell.exe ]==============================
Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL'
Debug shell is enabled
Waiting for PNP initialization...
RAM Disk Boot Path: MULTI(0)DISK(0)RDISK(0)PARTITION(1)\SOURCES\BOOT.WIM
WinPE boot path: C:\SOURCES\BOOT.WIM
Booted from removable device
Found config path C:\
Booting from removable media, not restoring bootloaders on hard drive
C:\WinPE does not exist.
C:\_SmsTsWinPE\WinPE does not exist.
Executing command line: wpeinit.exe -winpe
The command completed successfully.
Starting DNS client service.
Executing command line: X:\sms\bin\x64\TsmBootstrap.exe /env:WinPE /configpath:C:\
The command completed successfully.
==============================[ TSMBootStrap.exe ]==============================
Command line: X:\sms\bin\x64\TsmBootstrap.exe /env:WinPE /configpath:C:\
Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL'
Succeeded loading resource DLL 'X:\sms\bin\x64\TSRESNLC.DLL'
Current OS version is 6.2.9200.0
Adding SMS bin folder "X:\sms\bin\x64" to the system environment PATH
Failed to open PXE registry key. Not a PXE boot.
Media Root = C:\
WinPE boot type: 'Ramdisk:SourceIdentified'
Failed to find the source drive where WinPE was booted from
Executing from Media in WinPE
Verifying Media Layout.
MediaType = BootMedia
PasswordRequired = false
Found network adapter "Intel(R) Ethernet Connection I217-LM" with IP Address XXX.XX.XXX.XXX.
Running Wizard in Interactive mode
Loading Media Variables from "C:\sms\data\variables.dat"
no password for vars file
Activating Welcome Page.
Loading bitmap
WelcomePage::OnWizardNext()
Loading Media Variables from "C:\sms\data\variables.dat"
no password for vars file
Spawned thread 1008 to download policy.
Entering TSMediaWizardControl::GetPolicy.
Creating key 'Software\Microsoft\SMS\47006C006F00620061006C005C007B00350031004100300031003600420036002D0046003000440045002D0034003700350032002D0042003900370043002D003500340045003600460033003800360041003900310032007D00'
Environment scope successfully created: Global\{51A016B6-F0DE-4752-B97C-54E6F386A912}
Creating key 'Software\Microsoft\SMS\47006C006F00620061006C005C007B00420041003300410033003900300030002D0043004100360044002D0034006100630031002D0038004300320038002D003500300037003300410046004300320032004200300033007D00'
Environment scope successfully created: Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03}
Setting LogMaxSize to 1000000
Setting LogMaxHistory to 1
Setting LogLevel to 0
Setting LogEnabled to 1
Setting LogDebug to 1
UEFI: false
Loading variables from the Task Sequencing Removable Media.
Loading Media Variables from "C:\sms\data\variables.dat"
Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL'
Setting SMSTSMP TS environment variable
Setting _SMSMediaGuid TS environment variable
Setting _SMSTSBootMediaPackageID TS environment variable
Setting _SMSTSBootMediaSourceVersion TS environment variable
Setting _SMSTSBrandingTitle TS environment variable
Setting _SMSTSCertSelection TS environment variable
Setting _SMSTSCertStoreName TS environment variable
Setting _SMSTSDiskLabel1 TS environment variable
Setting _SMSTSHTTPPort TS environment variable
Setting _SMSTSHTTPSPort TS environment variable
Setting _SMSTSIISSSLState TS environment variable
Setting _SMSTSMediaCreatedOnCAS TS environment variable
Setting _SMSTSMediaPFX TS environment variable
Setting _SMSTSMediaSetID TS environment variable
Setting _SMSTSMediaType TS environment variable
Setting _SMSTSPublicRootKey TS environment variable
Setting _SMSTSRootCACerts TS environment variable
Setting _SMSTSSiteCode TS environment variable
Setting _SMSTSSiteSigningCertificate TS environment variable
Setting _SMSTSStandAloneMedia TS environment variable
Setting _SMSTSSupportUnknownMachines TS environment variable
Setting _SMSTSTimezone TS environment variable
Setting _SMSTSUseFirstCert TS environment variable
Setting _SMSTSx64UnknownMachineGUID TS environment variable
Setting _SMSTSx86UnknownMachineGUID TS environment variable
Root CA Public Certs=
Missing root CA environment variable from variables file
Support Unknown Machines: 1
Custom hook from X:\\TSConfig.INI is
No hook is found to be executed before downloading policy
Authenticator from the environment is empty.
Need to create Authenticator Info using PFX
Initialized CStringStream object with string: 1F53C44B-1AE9-4CAF-8ADA-5ED28DC8FF9A;2014-07-16T18:15:39Z.
Set media certificate in transport
Set authenticator in transport
CLibSMSMessageWinHttpTransport::Send: URL: XXXXXXXXX.XXXXXX.com:80 GET /SMS_MP/.sms_aut?MPKEYINFORMATIONMEDIA
Request was successful.
Default CSP is Microsoft Enhanced RSA and AES Cryptographic Provider
Default CSP Type is 24
New settings:
site=XXX,XXX, MP=http://XXXX.XXXX.com, ports: http=80,https=443
certificates are received from MP.
Unknown machine GUIDs: 774b17a2-6eeb-44bc-9c94-ce9081f5fe4c 74f16942-dd75-437f-8c4b-2a5de4d0e5e5
MP specific X86 unknown machine GUID is received at run time
MP specific X64 unknown machine GUID is received at run time
Getting MP time information
Set authenticator in transport
Requesting client identity
Setting message signatures.
Setting the authenticator.
CLibSMSMessageWinHttpTransport::Send: URL: XXXX.XXXX.com:80 CCM_POST /ccm_system/request
Request was successful.
::DecompressBuffer(65536)
Decompression (zlib) succeeded: original size 406, uncompressed size 2460.
-120
Server time zone info: 300, , [0 11 0 1 2 0 0 0], 0, , [0 3 0 2 2 0 0 0], -60
Client Identity:
Netbios name:
Current time: 2014-07-16 18:15:39.787 TZ:Pacific Standard Time Bias:0480
Current time zone info: 480, Pacific Standard Time, [0 0 0 0 0 0 0 0], 0, , [0 0 0 0 0 0 0 0], 0
Adjusting the system time: -14400.551 seconds
Time zone info set to: 300, , [0 11 0 1 2 0 0 0], 0, , [0 3 0 2 2 0 0 0], -60
New time: 2014-07-16 14:15:39.235
Current time: 2014-07-16 14:15:39.231 TZ: Bias:0300
Downloading policy from http://XXXX.XXXX.com.
Initializing HTTP transport.
Setting URL = http://XXXX.XXXX.com.
Setting Ports = 80,443.
Setting CRL = false.
Setting Server Certificates.
Set authenticator in transport
Setting Media Certificate.
Preparing Client Identity Request.
Setting transport.
Setting SourceID = 1F53C44B-1AE9-4CAF-8ADA-5ED28DC8FF9A.
Setting site code = XXX.
Can not find DeploymentType in file TsmBootstrap.ini or the file doesn't exist. This is not running on Windows To Go.
Setting SMBIOS GUID = XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX.
Adding MAC Address XX:XX:XX:XX:XX:XX.
Executing Client Identity Request.
Requesting client identity
Setting message signatures.
Setting the authenticator.
CLibSMSMessageWinHttpTransport::Send: URL: XXXX.XXXX.com:80 CCM_POST /ccm_system/request
Request was successful.
::DecompressBuffer(65536)
Decompression (zlib) succeeded: original size 415, uncompressed size 2460.
-120
Server time zone info: 300, , [0 11 0 1 2 0 0 0], 0, , [0 3 0 2 2 0 0 0], -60
Client Identity:
Netbios name:
Client GUID = , Netbios name = , State = Known
Using unknown machine GUID: 74f16942-dd75-437f-8c4b-2a5de4d0e5e5
GetSystemEnclosureChassisInfo: IsFixed=TRUE, IsLaptop=TRUE
Hash computed from CSP: Microsoft Enhanced RSA and AES Cryptographic Provider, AlgID: 32772, HashSize: 20
Computed HardwareID=2:4AC96CD5003991BC201B7AC01FBC88E592C3E2BE
Hardware ID: 2:4AC96CD5003991BC201B7AC01FBC88E592C3E2BE
Preparing the Client DDR Message
Setting SourceID = 1F53C44B-1AE9-4CAF-8ADA-5ED28DC8FF9A.
Sending the Client DDR message.
Sending Report
<Report><ReportHeader><Identification><Machine><ClientInstalled>0</ClientInstalled><ClientType>1</ClientType><Unknown>1</Unknown><ClientID>GUID:26717327-194f-4cd6-90ba-309998c058f2</ClientID><ClientVersion>5.00.0000.0000</ClientVersion><NetBIOSName>Unknown</NetBIOSName><CodePage>437</CodePage><SystemDefaultLCID>1033</SystemDefaultLCID></Machine></Identification><ReportDetails><ReportContent>Inventory
Data</ReportContent><ReportType>Full</ReportType><Date>20140716141539.000000+000</Date><Version>1.0</Version><Format>1.1</Format></ReportDetails><InventoryAction ActionType="Predefined"><InventoryActionID>{00000000-0000-0000-0000-000000000003}</InventoryActionID><Description>Discovery</Description><InventoryAc
Setting message signatures.
Setting the authenticator.
CLibSMSMessageWinHttpTransport::Send: URL: XXXX.XXXX.com:80 CCM_POST /ccm_system/request
Request was successful.
Submitted new client identity: GUID:26717327-194f-4cd6-90ba-309998c058f2
Preparing Policy Assignment Request.
Setting transport.
Setting site code = XXX.
Setting client ID = 74f16942-dd75-437f-8c4b-2a5de4d0e5e5.
Setting site signing Certificate.
Setting SiteSigningCertificateContext
Executing Policy Assignment Request.
Sending RequestAssignments
Setting message signatures.
Setting the authenticator.
CLibSMSMessageWinHttpTransport::Send: URL: XXXX.XXXX.com:80 CCM_POST /ccm_system/request
Request was successful.
::DecompressBuffer(65536)
Decompression (zlib) succeeded: original size 274, uncompressed size 662.
Request client ID: 74f16942-dd75-437f-8c4b-2a5de4d0e5e5
Response client ID: 74f16942-dd75-437f-8c4b-2a5de4d0e5e5
Retrieving Policy Assignments:
Successfully read 0 policy assignments.
Retrieving collection variable policy.
Found 0 collection variables.
Retrieving machine variable policy.
Found 0 machine variables.
Setting collection variables in the task sequencing environment.
Setting machine variables in the task sequencing environment.
Exiting TSMediaWizardControl::GetPolicy.
WelcomePage::OnWizardNext()
Loading Media Variables from "C:\sms\data\variables.dat"
no password for vars file
No assigned task sequence.
Setting wizard error: There are no task sequences available for this computer.
Skipping Confirmation Page.
Skipping Task Sequence Selection Page.
Skipping Variables Selection Page.
Skipping Resolve Progress Page.
Activating Finish Page.
Loading bitmap
Executing command line: X:\windows\system32\cmd.exe /k
The command completed successfully.
Successfully launched command shell.

KB2918614 Breaks MDT2012 Update 1 Task Sequence "Install Application" Items on Windows 7 deployments

Consider the following scenario:
You have a WDS deployment environment for your enterprise running on Windows Server 2008 R2.
You use MDT 2012 Update 01 to create a Windows 7 Task Sequence for workstation deployment.
The task sequence has an "Install Application" task to install Symantec Endpoint Protection 12.1 RU4 MP1b.
You either refresh your reference build to incorporate KB2918614 or you publish the update via WSUS and use the Install Updates task in the task sequence prior to the "Install Application" task to install the hotfix.
In this scenario, the "Install Application" task starts but never completes. The Symantec installation executable is never called and does not show up in Task Manager. All subsequent "Install Application" tasks exhibit the same behavior.
No error messages are generated. Eventually the Task Sequence itself times out and moves on to the next task.
If you remove update KB2918614 from your reference build or unapprove it from your WSUS server, all "Install Application" tasks in the task sequence execute correctly.
Has anyone else experienced a similar issues with deployments? My hunch is that the problem is not specific to the application being installed, and it may also be a problem for environments using SCCM to install Windows 7. I have not had a chance to explore
this more, so I kept my scenario to the facts that I have directly observed.
Thanks,
Rick Reuling
Walker IT Group, LLC

Quite the few incorrect assumptions, but thank you for your input. I disagree with your methodology and irrelevant conclusions.
Problem is quite clearly seen under easily reproducible conditions, which according to your description was not correctly proscribed. No one ever said the patch did not install correctly.
Whether the root cause is that mainstream third party applications are utilizing Microsoft solution accelerator proscribed methods that a privately reported vulnerability implicated as harmful; and thus the aforementioned patch changed the
expected behaviour to the detriment of mainstream certified applications in an unattended environment is at fault is up for discussion. Jamal's experience implicates the overall method in not only MDT but also SCCM so there stands a reasonable chance
that the problem exhibits on a further scale beyond the MDT environment.
However, as has been documented on a real world basis in the context of actual running environments (in which many do indeed still run Windows 7, much to all our chagrin and your self-declared shock) the issue still exists, and we must decline
your proposed solution as being appropriate to the described scenario. Your response clearly does not duplicate nor even attempt to recreate the problem space, If you had read clearly you would have seen we had already inserted a reboot in between the Windows
Update step in the TS and the "Install Application" step. Of course there are many other potential variables, hence why one should be quite careful about declaring an explicit problem or an explicit solution.
I believe Mike Niehaus clearly indicated the next step, and Jamal has confirmed the immediate workaround. I will encourage my clients to raise the issue through their EA channel.
Regards,
Rick

Question about Disable Step Task Sequence

Hello guys,
I have 2 doubt about my scenario, I hope you help me.
Scenario1
I want deploy SO Windows7, I have only one partition.
If a disable step: Apply data image1 my deploy ocurred with sucess.
But if no disable step I saw up, ocurred error 0X8004005.
My question so: Why is
mandatorily I
disable this step?
Print1 Partition Disk0
Print2 Apply Data Image
Thanks any idea.

It seems the answer has been staring us in the face this whole time.
In the above image you posted previously, you are clearly applying an image that, from the title, contains an OS despite the warning below the selection box stating that this image
can not contain any operating system.
The apply operating system task sequence step is for applying any WIMs involved with OS or boot partitions. The apply image step should only be used if you had data partitions that you wanted all machines to have, for instance raw storage sections with company
specific data on it. I have never seen it used but I can imagine where it would come in handy.
I would recommend replacing all of those steps with the appropriate task sequence step.
I also recommend you stop using hardware specific WIMs, as it seems you are using based on the title
WIN7HP8200... above. You should be able to go fairly hardware independent with the WIM and only apply drivers to the Task SEquence based on hardware detected.
Dustin Estes - MCP | www.dustinestes.com

TASK Sequence Package Comparison Report

Hi,
Would be great if someone could figure this one out.
I have a report that checks a Task Sequence and lists the packages called within the Task Sequence(No probs). What I want is to compare this with another Task Sequence using the TS name. I
want to show the packages that are different.
I tried creating two identical queries using two different variables, and using the Except command.
Doesn't really work. Would it be better using a subquery ?
We use Task Sequences with large amounts of packages assigned.
Cheers

couple of reports on task sequence packages and its referenced used . make use of them to write subselected query to identify packages which exist in TS1 but not in TS2 (task sequence 2).
http://eskonr.com/2012/11/sccm-report-status-of-packages-used-in-task-sequence/
http://eskonr.com/tag/sccm-report-for-task-sequence-packages-missing-on-which-dp/
Eswar Koneti | Configmgr blog:
www.eskonr.com | Linkedin: Eswar Koneti
| Twitter: Eskonr

SCCM's OSD (not MDT): Task sequence can be tweaked into imaging Windows+VHD Native Boot, but can it go all the way and deploy?

Hello All,
What I am trying to do is use SCCM's own OSD Task Sequence / Windows PE to deploy an operating system that boots using VHD Native Boot. (C:\ = VHD File with Windows, D:\ Data drive with BCDBoot).
MDT 2013 Can do it I've been told, but I am putting off MDT until Windows 10 if I can get away with it.
TechNet VHD Native Boot on Windows 8.1:
http://technet.microsoft.com/en-us/library/hh825689.aspx
http://technet.microsoft.com/en-us/library/hh825691.aspx
The good news is it is working up to the "Apply Operating System" phase, but that apply operating system phase is reported as an error even though it completes successfully. It can't clean up the SMSTS folder it's looking for on the C:\ because
it's been moved over to the D:\ by a diskpart script. We are left with the deployment working but requiring IT staff to deal with the OOBE Personalization wizard and adding each PC to the domain manually. From that point on the SCCM client can do the rest,
which works for US before we upgrade to Windows 10 with utilizing MDT.
I am not talking about deploying an OS to a VHD file and putting that file on a network share i.e.
http://blogs.technet.com/b/configurationmgr/archive/2013/10/31/new-in-system-center-2012-r2-configuration-manager-deploying-an-operating-system-to-a-virtual-hard-drive-vhd.aspx
I reported getting the diskpart script working first here:
https://social.technet.microsoft.com/Forums/en-US/ff124f09-1d2e-4fc4-a5b6-63b683f3d208/native-vhd-boot-deployments-from-sccm-2012-r2?forum=configmanagerosd
Here it is:
rem work around any USB disk left in or any CDROM detected by PE as drive D
select volume D
assign letter=F noerr
rem select the formatted volume and reassign it's drive letter
select volume C
assign letter=D
rem create and setup VHD file
create vdisk file=D:\DEV_WIN81.VHD maximum=250000 type=expandable
select vdisk file=D:\DEV_WIN81.VHD
attach vdisk
create partition primary
active
format FS=NTFS quick label="Developer Win81 VHD"
assign letter=C
rescan
exit
(type=fixed is better for performance - we'll surely activate when we have dual boot 8.1 / Windows 10 later for the Win10 VHD's)
The Task Sequence looks like this:
I'd like to add a few more steps after apply operating system if I can, but I have to resolve this error with "Apply Operating system before I can go further."
Question:
Can an OSD guru tell me if there are any Task Sequence Variables we could throw at this to make the Apply Operating System sequence complete without error so we can do all SCCM OSD Deployment steps?
If we can, then someone (not me) gets to add a new TechNet blog post about this being possible. It's my understanding presently that only MDT can support deploying WIM files into VHDs on Workstations, that boot them.
The install image was created using dism to convert a VHD from a Hyper-V host into a wim. I know I'm meant to use SCCM to capture it, but I don't think that's causing this problem because when we are deploying from that image to a HDD without VHD we don't
get any issues.
I'm only allowed enough characters to paste the tail end of the apply operating system phase only:
<![LOG[Execution engine result code: Success (0)]LOG]!><time="18:29:37.691-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tsmanager.cpp:929">
<![LOG[Cleaning Up.]LOG]!><time="18:29:37.691-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tsmanager.cpp:675">
<![LOG[Removing Authenticator]LOG]!><time="18:29:37.691-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tsmanager.cpp:686">
<![LOG[shKey.DeleteValue( c_szRegValue_SecurityToken ), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\ccmutillib\ccmutillib.cpp,1660)]LOG]!><time="18:29:37.691-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="ccmutillib.cpp:1660">
<![LOG[Cleaning up task sequence folder]LOG]!><time="18:29:37.691-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="utils.cpp:2329">
<![LOG[Unable to delete file C:\_SMSTaskSequence\TSEnv.dat (0x80070005). Continuing.]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="ccmfile.cpp:1056">
<![LOG[hr, HRESULT=80070091 (e:\nts_sccm_release\sms\framework\core\ccmcore\ccmfile.cpp,1218)]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="ccmfile.cpp:1218">
<![LOG[Failed to delete directory 'C:\_SMSTaskSequence']LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="2" thread="960" file="ccmfile.cpp:1218">
<![LOG[(dwRet = ::SetNamedSecurityInfoW ((WCHAR*) pszObjectName, objectType, OWNER_SECURITY_INFORMATION, pOwnerSID, NULL, NULL, NULL)) == ERROR_SUCCESS, HRESULT=80070005 (e:\qfe\nts\sms\framework\tscore\utils.cpp,6675)]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="utils.cpp:6675">
<![LOG[SetNamedSecurityInfo() failed.]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="3" thread="960" file="utils.cpp:6675">
<![LOG[SetObjectOwner() failed. 0x80070005.]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="3" thread="960" file="utils.cpp:6687">
<![LOG[SetObjectOwner (szFName, SE_FILE_OBJECT, c_szAdministrators), HRESULT=80070005 (e:\qfe\nts\sms\framework\tscore\utils.cpp,6772)]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="utils.cpp:6772">
<![LOG[RemoveFile() failed for C:\_SMSTaskSequence\TSEnv.dat. 0x80070005.]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="3" thread="960" file="utils.cpp:6816">
<![LOG[RemoveDirectoryW failed (0x80070091) for C:\_SMSTaskSequence]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="2" thread="960" file="utils.cpp:6900">
<![LOG[Deleting volume ID file C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ...]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="resolvesource.cpp:506">
<![LOG[DeleteFileW(sVolumeIDFile.c_str()), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\resolvesource.cpp,508)]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="resolvesource.cpp:508">
<![LOG[Deleting volume ID file D:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ...]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="resolvesource.cpp:506">
<![LOG[DeleteFileW(sVolumeIDFile.c_str()), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\resolvesource.cpp,508)]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="resolvesource.cpp:508">
<![LOG[Successfully unregistered Task Sequencing Environment COM Interface.]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="environmentlib.cpp:910">
<![LOG[Command line for extension .exe is "%1" %*]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="commandline.cpp:228">
<![LOG[Set command line: "X:\sms\bin\x64\TsProgressUI.exe" /Unregister]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="commandline.cpp:731">
<![LOG[Executing command line: "X:\sms\bin\x64\TsProgressUI.exe" /Unregister]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="commandline.cpp:827">
<![LOG[==========[ TsProgressUI started in process 8012 ]==========]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TsProgressUI" context="" type="1" thread="8040" file="winmain.cpp:330">
<![LOG[Command line: "X:\sms\bin\x64\TsProgressUI.exe" /Unregister]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TsProgressUI" context="" type="0" thread="8040" file="winmain.cpp:332">
<![LOG[Unregistering COM classes]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TsProgressUI" context="" type="1" thread="8040" file="winmain.cpp:204">
<![LOG[Unregistering class objects]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TsProgressUI" context="" type="1" thread="8040" file="winmain.cpp:495">
<![LOG[Shutdown complete.]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TsProgressUI" context="" type="1" thread="8040" file="winmain.cpp:512">
<![LOG[Process completed with exit code 0]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="commandline.cpp:1123">
<![LOG[Successfully unregistered TS Progress UI.]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="utils.cpp:2903">
<![LOG[Sending success status message]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tsmanager.cpp:784">
<![LOG[MP server http://OUR-SCCM.ourcompany.com. Ports 80,443. CRL=false.]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="utils.cpp:5881">
<![LOG[Setting authenticator]LOG]!><time="18:29:37.785-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="utils.cpp:5903">
<![LOG[Set authenticator in transport]LOG]!><time="18:29:37.785-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="libsmsmessaging.cpp:7734">
<![LOG[Sending StatusMessage]LOG]!><time="18:29:37.785-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="libsmsmessaging.cpp:4023">
<![LOG[Setting message signatures.]LOG]!><time="18:29:37.801-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="libsmsmessaging.cpp:1295">
<![LOG[Setting the authenticator.]LOG]!><time="18:29:37.801-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="libsmsmessaging.cpp:1325">
<![LOG[CLibSMSMessageWinHttpTransport::Send: URL: OUR-SCCM.ourcompany.com:80 CCM_POST /ccm_system/request]LOG]!><time="18:29:37.801-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="libsmsmessaging.cpp:8604">
<![LOG[Request was successful.]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="libsmsmessaging.cpp:8939">
<![LOG[::RegQueryValueExW(hSubKey, szReg, NULL, NULL, NULL, &dwSize), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\utils.cpp,811)]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="utils.cpp:811">
<![LOG[RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="2" thread="960" file="utils.cpp:811">
<![LOG[GetTsRegValue() is unsuccessful. 0x80070002.]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="2" thread="960" file="utils.cpp:842">
<![LOG[End program: ]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tsmanager.cpp:805">
<![LOG[Finalize logging request ignored from process 856]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tslogging.cpp:1737">
<![LOG[Process completed with exit code 0]LOG]!><time="18:29:37.863-420" date="12-26-2014" component="TSPxe" context="" type="1" thread="592" file="commandline.cpp:1123">
<![LOG[Task Sequence Manager returned code 0x00000000]LOG]!><time="18:29:37.863-420" date="12-26-2014" component="TSPxe" context="" type="1" thread="592" file="tsmediawizardcontrol.cpp:2180">
<![LOG[Exiting with return code 0x00000000]LOG]!><time="18:29:37.863-420" date="12-26-2014" component="TSPxe" context="" type="1" thread="592" file="tsmbootstrap.cpp:1238">
<![LOG[Execution complete.]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="1" thread="760" file="bootshell.cpp:693">
<![LOG[hMap != 0, HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\environmentscope.cpp,493)]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="0" thread="760" file="environmentscope.cpp:493">
<![LOG[m_pGlobalScope->open(), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\environmentlib.cpp,335)]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="0" thread="760" file="environmentlib.cpp:335">
<![LOG[this->open(), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\environmentlib.cpp,553)]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="0" thread="760" file="environmentlib.cpp:553">
<![LOG[::RegQueryValueExW(hSubKey, szReg, NULL, NULL, NULL, &dwSize), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\utils.cpp,811)]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="0" thread="760" file="utils.cpp:811">
<![LOG[RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="2" thread="760" file="utils.cpp:811">
<![LOG[GetTsRegValue() is unsuccessful. 0x80070002.]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="2" thread="760" file="utils.cpp:842">
<![LOG[End program: ]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="1" thread="760" file="bootshell.cpp:725">
<![LOG[Finalizing logging from process 752]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="1" thread="760" file="tslogging.cpp:1741">
<![LOG[Finalizing logs to root of first available drive]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="1" thread="760" file="tslogging.cpp:1583">
<![LOG[Successfully finalized logs to D:\SMSTSLog]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="1" thread="760" file="tslogging.cpp:1640">
<![LOG[Cleaning up task sequencing logging configuration.]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="0" thread="760" file="tslogging.cpp:584">
MCSE,MCNE,SCO,Sair Linux/GNU, Open source-enthusiast.

I have already set it to FALSE. The solution to this will be some different OSD Task Sequence variables or a statement that it can't be made to work.
I believe that setting defines what volume will be the BOOT / OS Drive Letter. Some people were getting D:\WINDOWS as their boot volume drive letter. Setting to true means whatever was the System Drive letter (usually C) in the image will remain as such
after it was was applied, setting it to false will make the system have the same drive letter arrangement as what Windows PE detects. In my case I set it to false so that no matter what the new VHD file setup as drive C will be the system drive. I'll set it
to true on the next deployment but I expect there to be no difference, because in both PE and the WIM the installation volume is the C:.
We are talking about the DRIVE LETTERS Windows PE SCCM OSD is using for it's temporary files - and how we can manipulate these locations using OSD Task Sequence Variables, so the Apply OS doesn't try and clean up files that are not there
- and fail with an error if you have added a VHD Native Boot volume.
This OSDPreserveDriveLetter setting isn't having any effect on the problem here.
I believe that Format step is setting some task variables used by the OSD Deployment process - telling it where to store it's temporary files. However between the Format Disks and Apply operating system steps the OSD Task Sequence isn't picking up on the
fact what was the C:\ after Format HDD step is now the D:\ .
A developer who has an understanding of how the OSD boot process executes in order would be able to see what's going on here.
MCSE,MCNE,SCO,Sair Linux/GNU, Open source-enthusiast.

Deploying the SCCM 2012 Client to WES 7 devices that are locked down with the FBWF using 2007 task sequence via WEDM.

I'm wondering how people are migrating their embedded devices that are using the FBWF. I've done some googling and it seems like most people are just re-imaging the devices and after migrating a single device i see why. Its not a pretty process. This will
be a long description but ultimately my question stems more from trying to find a better way to execute the device migration from 2007 to 2012.
Some back ground on my situation might be in order here. I'm in the process of wrapping up our 2007 to 2012 migration. We have a 2007 infrastructure that was a central server with 2 primaries and 286 secondary site servers. I've consolidated that to a single
2012 primary site server that hosts all the main roles. There are 2 more servers in the data centers both operating solely as push distribution points I'll refer to them as 2012 01 02 and 03. I'm over half way through the migration and so far haven't needed
to offload any site roles. There are almost 10,000 clients now reporting to the 2012 site server and almost a 100 field servers pulling content from 2012 02 as their source dp as pull dp is the only way forward for this many devices. I've read the horror stories
of trying spin up 200 plus push dps. We are running PKI. I'm at the point now where i need to start migrating the Windows Embedded Seven Standard clients that have the 2007 sccm client on them with WEDM for write filter handling.
What i'm wondering is if anyone has any pointers for me regarding migrating the WES 7 devices. My plan that i've come up with is to somehow script the process using a 2007 WEDM Task Sequence to try and migrate them over to 2012. Things are complicated as
I need to somehow script the install, the policy checkin, hardware inventory, software inventory, and validate the SCEP client installs before I reboot the device one last time to enable the FBWF. How I handled the SCCM 2007 client install on these devices
when they were provisioned was to just create a batch file that would sleep for ten minutes then check to see if the inventoryagent.log file had been created yet. I realize now that is inefficient as i can kick off the inventory using a WMI method once the
client has installed. Also I need to make sure the machine gets its first policy as that is how it creates the communication using PKI through that first policy transfer and that also finalizes the client install. The biggest piece i'm uncertain about in this
regard is the SCEP client.
I had to change the SCEP client install from yes to no in the default client settings as we have some Mcaffee servers that can't have the SCEP client on them. I have incremental updates enabled on the collection that has the policy that installs the SCEP
client but this will take an unknown amount of time unless i force the environment to update as the device starts in 2012 install, or if I could kick off the SCEP isntall... IDK. I'm also wondering if i should keep the device in the migration process until
i validate it has its proper scep policy applied which I believe can be validated by a registry key somewhere.
Once the 2012 client gets installed will that cause it to lose its place within the 2007 Task Sequence? Considering its going to take a minimum of 2 reboots I'd normally use the task sequence to handle its progression through the process.
I'm also considering trying to use an Orchestrator runbook, as that would be a good way to keep track of the migration process as each device migrates. Especially since this might take several seperate scripts.
I'm going to take a stab at scripting the migration process, but if anyone has any pointers that might make this a less complicated I'd really appreciate it as I've got about 3000 of these devices that need to be migrated over. The other things i've learned
the hard way is any time you have something this complicated over the course of 3000 devices you will run into unknowns and the failure rate increases. I'm in the precarious position of having to not only build this process out but in some situations have
it complete in the shortest amount of time possible as we have sites running 24x7. I know the end users behavior all to well and they will just keep hitting the power button sometimes even though their not supposed to so they can get their device functional
again. In those situations i'd end up, if i'm lucky with a device that no longer has a healthy SCCM client in either environment and the write filter disabled.
So like i said any pointers anyone could throw my way i'd really appreciate. I manually went through the migration process on a single device for proof of concept and ended up with almost 2 pages of pseudo code for my migration script/scripts.
Thanks,
-K.R.

Hi,
In R2 there are some new variables you can use to solve this,
http://ccmexec.com/2014/12/smstsmplistrequesttimeout-value-in-milliseconds/
In Sp1 though adding a step to sleep for 2-5 minuter after reboot and before the application install step is a common workaround.. a powershell command with "Start-Sleep
-s 120" should do it.
/Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

When is it safe to update a task sequence?

We have a fairly busy environment, with OSD happening all the time. We have been updating our major task sequences off hours, but I wonder if that is even necessary. After testing in QA, is it safe to update the task sequence at any time without bothering
or confusing workstations that are in the middle of an OSD operation?
I think I understand that the task sequence is pulled down to the local hard drive very early in OSD, and it doesn't return to re-read the task sequence after that. Is that correct? If that's true then we don't need to worry about workstations losing their
place in the task sequence if we update it while they are executing the task sequence.
Thank you for any light others can shed on this.
Gary
Gary Knigge, Senior Systems Analyst Division of Technology Services University of Wisconsin-River Falls Wisconsin, USA

Correct, the machine downloads the task sequence at the beginning of the process and uses that cached copy throughout, so modifying the task sequence will not affect any deployments already executing.
That said, the biggest risk you face in modifying production task sequences is content. If you add a task referencing content that is not yet fully deployed and available, you will cause any subsequent executions to fail. This is especially true of
adding new Driver Packages as there is a known issue with the content not being recognized as valid until Rev2 (you not only have to distribute it to your DPs but also subsequently update the DPs to rev the content).

SCCM 2012 - OSD Task Sequence Error 0x80091007

When deploying the OSD to a laptop model the TS is failing, see below from Status Message Viewer:
The task sequence execution engine failed executing the action (Apply E6220 Driver Package) in the group (PostInstall) with the error code 2148077575
Action output: urce, sSourceDirectory, dwFlags, hUserToken, pszUserName, pszUserPassword), HRESULT=80091007 (e:\nts_sccm_release\sms\framework\tscore\resolvesource.cpp,3217)
ResolveSource(pszSource, sSourceDirectory, dwFlags, 0, 0, 0), HRESULT=80091007 (e:\nts_sccm_release\sms\framework\tscore\resolvesource.cpp,3122)
TS::Utility::ResolveSource( pszPackageId, sSource ), HRESULT=80091007 (e:\nts_sccm_release\sms\client\osdeployment\osddriverclient\driverinstaller.cpp,472)
pDriverInstaller->InstallDriverPackage( sPackageId, pBootCriticalInfo ), HRESULT=80091007 (e:\nts_sccm_release\sms\client\osdeployment\osddriverclient\osddriverclient.cpp,380)
Exiting with return code 0x80091007
Hash could not be matched for the downloded content. Original ContentHash = EB2A940227C7043DDDCE0985EB37CBB650245F47F12ACD48C936521F5CECAFED, Downloaded ContentHash = 6F4ED0BD9ECC46712E6160BF681ED3785097D95A43652424FB97E12EB1EAF8E3
Failed to determine the driver source location. Code 0x80091007
Failed to provision driver. Code 0x80091007. The operating system reported error 2148077575: The hash value is not correct.
I have redistributed the Driver packages to the DP's but still no luck - does anyone have any idea's?
Thanks
MCTS | MCITP | MCSA

Below is the whole thread from Expert-sex-change.com:
SCCM OS deployment error (0x80091007)
Asked by: MoritzCSA
We are getting Error on one of your Primary Child site when deploying a XP Install Package.
In the Advertisment Status we are getting following errors:
The task sequence execution engine failed executing the action
(Apply Operating System Image) in the group () with the error code
2148077575
Action output: zSource, sSourceDirectory, dwFlags, hUserToken,
pszUserName, pszUserPassword), HRESULT=80091007
(e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,3130)
ResolveSource(pszSource, sSourceDirectory, dwFlags, 0, 0, 0),
HRESULT=80091007
(e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,3031)
TS::Utility::ResolveSource( this->packageID, this->packagePath,
TS::Utility::ResolveSourceFlags::PersistContents ),
HRESULT=80091007
(e:\nts_sms_fre\sms\client\osdeployment\applyos\installscripted.cpp,
160)
installer.install(), HRESULT=80091007
(e:\nts_sms_fre\sms\client\osdeployment\applyos\installscripted.cpp,
632)
Entering ReleaseSource() for
C:\_SMSTaskSequence\Packages\GID00004
The user tries to
release a source directory
C:\_SMSTaskSequence\Packages\GID00004 that is either already
released or we have not connected to it InstallScripted(
g_InstallPackageID, g_ImageIndex, targetVolume,
g_ConfigPackageID, g_ConfigFileName ), HRESULT=80091007
(e:\nts_sms_fre\sms\client\osdeployment\applyos\applyos.cpp,397).
The operating system reported error 2148077575: The hash value is
not correct.
The task sequence execution engine aborted execution for a failure
of the action (Apply Operating System Image) in the group (). The
operating system reported error 2148077575: The hash value is not
correct.
The task sequence execution engine failed execution of a task
sequence. The operating system reported error 2148077575: The
hash value is not correct.
The task sequence manager could not successfully complete
execution of the task sequence. A failure exit code of 16389 was
returned.
appreciate any help
IMAG0020.jpg
747 KBscreenshot off error on Client Computer when deploying OS
2010-02-05 at 04:39:43ID: 25117354TopicsMS System Center ,Deployment Software for DevelopmentParticipating Experts3Points0Comments9
Request Attention
Answers
EXPERT COMMENT
by: NJComputerNetworksPosted on 2010-02-05 at 05:29:05ID: 26494779
1) enable f8 boot console on your boot image: http://www.windows-noob.com/forums/index.php?/topic/546-how-can-i-troubleshoot-windows-pe-booting-in-sccm/ this will get you to a command prompt on the client
2) look at the smsts.log for exactly why your client is failing osd: http://blogs.technet.com/inside_osd/archive/2007/12/13/troubleshooting-tips.aspx
3) also look at the reports for information as to why your OSD is failing: http://blogs.technet.com/inside_osd/archive/2007/12/13/troubleshooting-tips.aspx
AUTHOR COMMENT
by: MoritzCSAPosted on 2010-02-05 at 05:39:33ID: 26494871
Hi,
Its not the Boot image what has problems. Its one single OS package as others workjust fine
EXPERT COMMENT
by: NJComputerNetworksPosted on 2010-02-05 at 06:01:11ID: 26495086
lol... ok... but enabling F8 will allow you to get to the smsts.log which should contain some more information about why the single OS package is failing.
EXPERT COMMENT
by: JonLambertPosted on 2010-02-08 at 01:43:35ID: 26512090
OK, it looks like (as descripted in the logs) that the Hash Value for the package GID00004 is not correct.
I've seen this before with Boot WIMS, if GID00004 is a boot WIM package, then try creating a new Boot Wim, deploying it to the relevant DPs, assigning it to th TS and try again.
If GID00004 is not a Boot WIM, then try updating the package, and keep an eye on DistMgr.log to ensure it get's distributed Ok.
AUTHOR COMMENT
by: MoritzCSAPosted on 2010-02-09 at 07:13:55ID: 26524885
Hi have recreated the OS Install Packlage and have distributed it again to the Primary Child site. Still the same issue as for example the same OS in English is running fine. GID00004 was an OS Install Package.
I have the log file from the F8 boot atached
smsts-20100210-001651.log
976 KBlog
smsts.log
391 KBlog2
ADMINISTRATIVE COMMENT
by: TheLearnedOnePosted on 2010-03-03 at 18:54:29ID: 27299334
MoritzCSA,
After 21 days without comment, it is time for you to finalize this old question -- accept an answer, split points, or get a refund. Please be a responsible EE Member and maintain your open questions! Click here to see your options: http://www.experts-exchange.com/help.jsp#hi331
EXPERTS,
I need your help. Please post your closing recommendations within a few days. If you do not respond, I may need to assume that no correct answer was provided.
TheLearnedOne
Experts-Exchange Cleanup Volunteer
EXPERT COMMENT
by: JonLambertPosted on 2010-03-03 at 19:17:39ID: 27299526
OK, now the package with an hash error is GID0002A .. which is the OS Install Package, Check the source directory for files with odd characters, or extremely long directory paths .. this can sometime cause a hash-check mismatch.
Hash could not be matched for the downloded content. Original ContentHash = A9173DC49D149170C0F7F5526154AC4381ED0DC0, Downloaded ContentHash = 88601C0BA124401EA13790D2F318AF04CB283DD1 ApplyOperatingSystem
9/02/2010 3:29:21 PM 1680 (0x0690)
ACCEPTED SOLUTION
by: MoritzCSAPosted on 2010-03-04 at 00:23:07ID: 27300766
I have change the OS installation to not download the package. After this change it works fine without issues.
0
excellent
Save to Personal Knowledgebase
EXPERT COMMENT
by: DSS-RMPosted on 2010-10-17 at 07:14:56ID: 33923836
Update the distribution points of the package that was failing. I have had this same problem and a distribution point update will fix it.

Doubt about Report - Task Sequence - Deployments

Similar Messages

Maybe you are looking for