SCCM 2012 R2 OSD - Pre Provision Bit-Locker Drive Label Name Issues

I am trying to image machines Pre-provisioned for BitLocker. Everything works great in the Task Sequence except the Drive Label on Boot is "MININT-XXXXX" rather than the actual computer name. This happens whether the computer is known
or unknown.
The only other post regarding this issue I can find suggested changing the OSDComputerName variable name in the TS but that will not work because the hostname is set during the WinPE setup.
http://social.technet.microsoft.com/Forums/en-US/f9c6f565-e137-4c59-a8de-7314d9b88fe7/how-to-change-computername-on-bitlocker-pinrecovery-password-screen-drive-label?forum=mdt
I have tried to set the OSDComputerName variable during the Pre-Start and TS but the Drive Label always remains "MININT-XXXXX".
Any ideas?

First in Customsettings.ini or in a TS set the %OSDComputerName%
Then just add this to a Command in the task sequence before provisioning.
REG ADD HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\ComputerName\ActiveComputerName /v ComputerName /t REG_SZ /d %OSDComputerName% /f
REG ADD HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\ComputerName\ComputerName /v ComputerName /t REG_SZ /d %OSDComputerName% /f
SCCM now believes the name of winpe is %OSDComputerName%
Joakim Tomren

Similar Messages

Pre-Provisioning Bit Locker in MDT 2012 SP1 while using MBAM 2.5 - No Pin Required

Does anyone have some step by step instructions for Pre-Provisioning Bit Locker. Through task sequences, we are currently able to bit locker the computers but it's the last set of tasks. I would like to Bit Locker the computer while no data is on the
disc so it's faster and then as its imaging, the files are already encrypted.
Currently:
Creates BIOS Password
TPM turned on and enabled (using CCTK)
Remove Password
Registry changes
Installing MBAM 2.5
Removing Registry Entries
Any help would be appreciated!
Thanks
Rick

Bitlocker Pre-Provisioning is available by default on MDT Litetouch...
If you just want to pre-provision the drive without letting MDT LiteTouch enable any protectors (let MBAM do that) then just run the following command after the "FOrmat and PArtition" step in the Task Sequence:
x:\windows\system32\Manage-BDE.exe c: -used
(OR whatever drive letter OS exists on in WinPE)
AS an alternative, I would add a step just before the "ENable Bitlocker (offline)" step in the task sequence:
    BDEInstallSuppress=NO
    isBDE=YES
then after the "Enable Bitlocker (offline)" step in the Task Sequence, I would set the following:
    isBDE=NO
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

Fasten the Process of MDT UDI OD Installation in SCCM 2012 R2 OSD

Hi,
I have implemented MDT UDI Task Sequence in SCCM 2012 R2 OSD. The issue which I am facing is the UDI Installation progress is very slow. it is taking around 2 hours to complete the whole Installation.
Is there any way to fasten the Process of MDT UDI OD Installation in SCCM 2012 R2 OSD.
Thanks & Regards,
Sanjay Dubey

Application installs can take awhile - it depends on what applications you're installing, and how many. For instance, installing Office is clearly going to take longer than say 7-Zip. How many applications are you installing during a normal OS
deployment? You can check the AppEnforce.log to see how long an application(s) is taking to install, as the start and end times are recorded.
As for the MDT Settings package, how many times are you calling this package? My task sequence only calls it 5 times, and one of them is before you even get the UDI wizard, while the second and third is an either/or situation, depending on whether
you do a refresh or a fresh PC build.

Bit Locker Drive Encryption of Windows Vista

Have just downloaded the Bios Upgrade version 2.2 (QG40 BIOS_W220.exe), but I inadvertently omitted to turn the 'Bit Locker Drive Encryption of Windows Vista' off first, as Toshiba had advised.
Is there any corrections I can make to rectify this omission and ensure the G40 and the software operate correctly?

Thanks for your prompt reply Jeka-Nn. But I have several further questions before going too far with the suggestions as I am not familiar with software modifications.
1. What am I actually trying to do overall by downloading and using the suggested application.? Can you give me some overall picture of what I am trying to do?
2. Does this fix the problem without me having to make choices--is it self sufficient/self-installing?
3. Will it return the system to its correct operational settings before I downloaded the Bios upgrade?
4. I have downloaded the application suggested, but when I try to open the file it sends up a message that reads:
Error; this installer does not contain any compressed files. To create a self extracting installation package (with embedded files) run:
"TrueCrypt Setup.exe" /p
When I press OK, it simply reverts to the downloaded list which has the TrueCrypt v7.0 included, but nothing else happens.
What do I need to do to fully install the application?
5. Are there any other steps /inclusions that I need to make to fully correct my 'stupidity'?
Sorry about all these questions but you can see I am a raw beginner at this work.
With thanks, rons

SCCM 2012 R2: OSD Windows 7 Bitlocker pre-provisioning

Hi,
I succesfully configure bitlocker for Dell laptops during our W7 task sequence (thanks to this guide: http://www.windows-noob.com/forums/index.php?/topic/3875-customising-windows-7-deployments-part-5/)
Now I want to do the same for HP, found this link http://www.sccm.biz/2012/06/sccm-and-bitlocker-tpm-real-life.html but it seems a config for AFTER installing Windows, not in WINPE.
During the TS, OS reboots and then says "no OS found", so I'd need to enable the TPM/bitlocker differently.
Please advise (enabling bitlocker in TS, WINPE phase (pre-provision bitocker) for HP models).
J.
Jan Hoedt

Hi,
The pre-provisioning is the same for all vendors, it is the TPM part that is different from Vendor to Vendor so you can use these steps to enable TPM in the beggining och the Task Sequence and then let the pre-provisiong step enable bitlocker.
Regards,
jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

MBAM 2.0 SP1, SCCM 2012 SP1 - OSD

Found a few threads on this but just looking for an answer before I spend to much time fiddling to get this to work. What I am looking to do is encrypt laptops during OSD as follows:
Enable TPM (working fine)
Activate TPM (working fine)
Pre-Provision Bitlocker (using Win 7 Ent SP1)
Install OS
Install MBAM
Enable Bitlocker and escrow both TPM and Drive recovery keys to MBAM server
The bit I am not too sure about is the Pre-Provision and also the TPM key backup. Ideally I'd like both the TPM and Disk keys stored in MBAM but I am not sure if this will work if I have activated the TPM pre OS?
Cheers

Pre-provisioning only works on a bare metal machine and occurs in WinPE. It also uses TPM so you need to make sure that is on an active in the BIOS.
This blog post provides some detail on how to enable MBAM and pre-provisioning. If you are using Windows 8+, and you want MBAM to back up TPM to its db instead of AD, you have to turn off auto-provisioning or Windows 8+ will take ownership automatically
and escrow to AD. To disable auto-provisioning you can set the following key when the OS has come up:
Reg Key to disable auto-provision:
HKLM\System\CurrentControlSet\Services\TPM\WMI
NoAutoProvision = 1
you
will need
to create a
regkey called
NoAutoProvision=1
Hope that helps!
Lance

SCCM 2012 CU2 OSD forest trust: ReleaseRequest failed with error code 0x87d00317

Hello,
Actually i have a difficult Problem with my SCCM 2012 R2 CU2 Windows 7 x64 SP1 Tasksequence:
I get the folowing error in smsts.log:
::RegQueryValueExW(hSubKey, szReg, NULL, NULL, NULL, &dwSize), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\utils.cpp,811) TSManager 9/5/2014 1:20:35 PM 1740 (0x06CC)
RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram TSManager 9/5/2014 1:20:35 PM 1740 (0x06CC)
GetTsRegValue() is unsuccessful. 0x80070002. TSManager 9/5/2014 1:20:35 PM 1740 (0x06CC)
End program: TSManager 9/5/2014 1:20:35 PM 1740 (0x06CC)
Finalize logging request ignored from process 1736 TSManager 9/5/2014 1:20:35 PM 1740 (0x06CC)
Waiting for CcmExec service to be fully operational TSManager 9/5/2014 1:20:35 PM 1740 (0x06CC)
CcmExec service is up and fully operational TSManager 9/5/2014 1:20:35 PM 1740 (0x06CC)
Access handle will be read from _SMSTSActiveRequestHandle TSManager 9/5/2014 1:20:35 PM 1740 (0x06CC)
Access handle: {B699D570-B2BF-4874-8CB7-3B208B380969} TSManager 9/5/2014 1:20:35 PM 1740 (0x06CC)
Attempting to release request using {B699D570-B2BF-4874-8CB7-3B208B380969} TSManager 9/5/2014 1:20:35 PM 1740 (0x06CC)
CoCreateInstance succeeded TSManager 9/5/2014 1:20:35 PM 1740 (0x06CC)
pISoftwareExecutionRequestMgr->ReleaseRequest(ActiveRequestGUID), HRESULT=87d00317 (e:\nts_sccm_release\sms\client\tasksequence\tsmanager\tsmanagerutils.cpp,136) TSManager 9/5/2014 1:20:35 PM 1740 (0x06CC)
ReleaseRequest failed with error code 0x87d00317 TSManager 9/5/2014 1:20:35 PM 1740 (0x06CC)
Task Sequence Manager could not release active TS request. code 87D00317 TSManager 9/5/2014 1:20:35 PM 1740 (0x06CC)
Here is the complete smsts.log: http://1drv.ms/1pwTEBf
To explain the Problem in Detail:
The SCCM Primary Site Server and the Clients are in different trusted (bidirectional) forests!
Everythings working fine in this Scenario, I can install SCCM Agent on the Clients with Manual ccmsetup and with Client Push Installation. Additionally i can deploy Software Updates and so on... only OSD is crashing in the releaserequest step.
During my Tasksequence new Clients are joined to Domain A while SCCM Primary Site Server is installed in Domain B
If I change my TS and let the Clients also join Domain B everything works without any Problems and the Tasksequence finish without any Errors.
My Problem must be related to the different Domains and the forest trust.
My Setup:
MP published to DNS in both domains
Schema Extended in both domains
System Management Container published and verified in both domains
ccmsetup Parameters in TS: ccmsetup SMSMP=sccm.domain.b FSP=sccm.domain.b DNSSUFFIX=Domain.b
Network Access account configured with Domain B account
Domain Join account has create Computer rights on the OU in Domain A (Domain join is successful)
DNs conditional forwarders configured in both Domains and DNS resolutin is working in both directions
Any suggestions?
Many thanks.
regards,
Christian

Hi Christian,
So do you actual get an error message in your TS or is it just failing to join Domain B? (Could be both if the machines fails to join the domain).
Can you review netsetup.log on the machines after the issue and see what error message you might be getting during the domain join process?
Also, if it a domain join issue, can you try manually joining to domain B using the same service account?

SCCM 2012 SP1 OSD in 802.1X environment

Dears,
we have SCCM 2012 SP1 CU5, and the network team has enabled the CISCO port security (802.1X network authentication) on the desktops VLAN and OSD is not working since then until port security is removed. i've seen some guides regarding how to make SCCM 2007
OSD, WinPE 3.0 and 802.1X work together like : http://myitforum.com/cs2/blogs/lakey81/archive/2011/07/06/configuring-802-1x-network-authentication-for-winpe-3-0-and-configmgr-deployments.aspx , but ot's very confusing.
does anybody have the same scenario with SCCM 2012, WinPE 5.0, and 802.1X . please help me.

Hello,
What confused you here? 802.1X authentication is to authenticate before sending network packages. That is why we need import netwrok profile to win pe for anthentication. The point is authenticate, so I think it won't be any difference between
ConfigMgr 2012 and 2007.
Another good article here:
http://blogs.technet.com/b/deploymentguys/archive/2010/03/02/adding-support-for-802-1x-to-winpe.aspx
Please also pay attention to the shared document in the blog.
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

Latitude E6330 BSOD via SCCM 2012 R2 OSD

Hi All,
I'm currently struggling to build some Latitude E6330 laptops via SCCM 2012 R2 CU3 OSD . I'm getting a BSOD with error code 0000007E after the drivers are applied and the laptop reboots.
I've built nearly 100 OptiPlex desktops without issue from the same server. I've tried both the A09 and A10 E6330 driver CABs, and both have the same issue. I was having an issue even building the boot image with these drivers, but removed a faulty driver
before importing them into SCCM (Conexant USB Modem driver) which resolved that issue. I'm assuming that the removal of this driver wouldn't be causing the BSOD - but I'm currently trying to find a replacement driver to see if that resolves it anyway.
I've tried using 'Auto Apply Drivers' and 'Apply Driver Package' in the task sequence, using a WMI query and also without a WMI query to no avail. I've blown away all previous drivers, imported only the A09 and then blew away + imported only the A10
drivers, rebuilt the driver packages and re-added to the boot image numerous times. Yep I've been distributing/updating distribution points each time too :)
Unfortunately I can't get onto the laptop to check the smsts/setupact/etc etc logs because it blue screens even in safe mode.
My last resort will be to add just the network+HDD drivers, and then slowly add drivers until I figure out what driver is causing the BSOD. Unfortunately this would be quite a lengthy procedure, so I'm hoping that someone has had a similar problem and
may know which driver could be causing me this grief.. Or perhaps could point me in a different direction as to what may be causing this issue....
Thanks for your time.

Are you trying to deploying Windows 7 to the laptops?
If so does your WIM file include the platform update (how long has it been since you created / updated it)? If not then you may need to update / capture a new wim and try again.
A lot of newer drivers will cause this sort of problem if you try and inject them into an older wim file.
If this isn't the case, then I have had this happen to me a long time ago with a webcam driver so maybe exclude these drivers first? A long shot though.
Cheers
Damon

SCCm 2012 R2 - OSD fails when multiple computers are getting built

Hi everyone,
I ran into a weird issue with my SCCM 2012 R2. I noticed when I build one computer with SCCM OSD, it works fine. But when I try to run more than one built at a time, only one usually works. The rest usually doesn't get apps installed in the task sequence,
some don't get added to the domain etc. Any idea what it might be? Could it be that simultaneous connections to the distribution point are getting terminated and imaging fails?
Appreciate your help!

Ok guys, this seems to be a false alarm here. It turns out I was missing a driver for ethernet card on my Dell T1600. I kicked off 3 Dell Optiplex 9020 and they all worked flawlessly. This is weird though, since I did install OS on some T1600 before and
they all worked fine...
Anyway, I downloaded the driver and added it to SCCM. I will kick off the install again today and see if that solved it.

Task Sequence Failed 0x80091007. SCCM 2012 R2 OSD

Hi,
I have multicast deployment issue with Configuration Manager 2012 R2.
Unicast is working fine, Multicast throwing error 0x80091007.
Wait time starts and after 40 to 50 seconds pops up with error 0x80091007
I have already tried Redistributing and recreating image, trying with different systems, Direct access from DP settings, validating share access and all.
There is no SMSTS.LOG available on client systems.

Hi,
How about MCSISAPI.log?
Here is a blog talks about this error, you could have a look.
"Update 19-6-2013: Nick send me a possible solution in comments. What you have to do is make sure you don't have a custom Multicast range set - use the setting "Use IPv4 addresses within any range"
in the SCCM 2012 multicast tab under Distribution Point properties.
The default is 239.0.0.1 to 239.0.0.254 - if you have a custom range set - it IGNORES it and uses a random address in 239 range anyways. He has tried to statically set a 239 range on both SCCM multicast and WDS multicast settings - ignores them still uses a
random address in the 239 range regardless.
On your Cisco core - if your using that - make sure your ACL's and Rendezvous Point ACL for PIM permits the 239 range. As soon as this was done it's all working. > Will try that myself next month! "
http://henkhoogendoorn.blogspot.com/2013/02/multicast-error-0x80091007-during.html
(Note: Microsoft provides third-party contact information to help you find technical support. This contact
information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.)
Best Regards,
Joyce
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.

SCCM 2012 R2 OSD Application Install Problems

I am trying to run a fairly basic TS. It installs windows then office and Lync. Windows installs fine but Office does not get installed. The log file is below. I found the part that says "Application is not required on the client" a requirement was
not met. Log file is below.
Installing application 'Microsoft Office 2010 Profesional 32-bits with Proofing Tools'
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
GetAppMgmtSDKInterface successful InstallApplication
2/21/2014 2:05:37 PM 1744 (0x06D0)
Retrieving value from TSEnv for '_SMSTSPolicy_ScopeId_02324D38-9750-4C09-AD8C-8C70B370484B/Application_f634e9c2-50b4-4196-8391-1f55edca6ac6'
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
::DecompressBuffer(65536) InstallApplication
2/21/2014 2:05:37 PM 1744 (0x06D0)
Decompression (zlib) succeeded: original size 1227, uncompressed size 10576.
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
Found App policy modelname:ScopeId_02324D38-9750-4C09-AD8C-8C70B370484B/RequiredApplication_f634e9c2-50b4-4196-8391-1f55edca6ac6 and CIversion:18
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
Start to compile TS policy InstallApplication
2/21/2014 2:05:37 PM 1744 (0x06D0)
Policy complied successfully in WMI 'root\ccm\policy\defaultmachine\requestedconfig' namespace
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
End TS policy compilation InstallApplication
2/21/2014 2:05:37 PM 1744 (0x06D0)
Retrieving value from TSEnv for '_SMSTSCIVersionInfoPolicy'
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
::DecompressBuffer(65536) InstallApplication
2/21/2014 2:05:37 PM 1744 (0x06D0)
Decompression (zlib) succeeded: original size 11486, uncompressed size 121958.
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
Looking for policy ScopeId_02324D38-9750-4C09-AD8C-8C70B370484B/RequiredApplication_f634e9c2-50b4-4196-8391-1f55edca6ac6/VI in ts environment
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
Found policy: ScopeId_02324D38-9750-4C09-AD8C-8C70B370484B/RequiredApplication_f634e9c2-50b4-4196-8391-1f55edca6ac6/VI
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
ModelName = ScopeId_02324D38-9750-4C09-AD8C-8C70B370484B/RequiredApplication_f634e9c2-50b4-4196-8391-1f55edca6ac6
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
ModelName = GLOBAL/FreeDiskSpace InstallApplication
2/21/2014 2:05:37 PM 1744 (0x06D0)
ModelName = GLOBAL/Platform_Settings InstallApplication
2/21/2014 2:05:37 PM 1744 (0x06D0)
ModelName = Windows/All_Windows_Client_Server
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
ModelName = Windows/All_x64_Windows_7_Client
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
ModelName = Windows/All_x64_Windows_XP_Professional
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
ModelName = Windows/All_x86_Windows_7_Client
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
ModelName = Windows/All_x86_Windows_XP InstallApplication
2/21/2014 2:05:37 PM 1744 (0x06D0)
ModelName = Windows/x64_Windows_XP_Professional_SP2
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
ModelName = Windows/x86_Windows_XP_Professional_Service_Pack_3
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
ModelName = Windows/x86_Windows_7_Client InstallApplication
2/21/2014 2:05:37 PM 1744 (0x06D0)
ModelName = Windows/x64_Windows_7_Client InstallApplication
2/21/2014 2:05:37 PM 1744 (0x06D0)
ModelName = Windows/x86_Windows_7_SP1 InstallApplication
2/21/2014 2:05:37 PM 1744 (0x06D0)
ModelName = Windows/x64_Windows_7_SP1 InstallApplication
2/21/2014 2:05:37 PM 1744 (0x06D0)
ModelName = ScopeId_02324D38-9750-4C09-AD8C-8C70B370484B/DeploymentType_0fc0a9d6-ba9d-48cd-a80f-0f21f64f9edc
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
ModelName = ScopeId_02324D38-9750-4C09-AD8C-8C70B370484B/DeploymentType_916567e1-08c1-4455-85b8-1dd84c3eb96b
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
ModelName = ScopeId_02324D38-9750-4C09-AD8C-8C70B370484B/Application_f634e9c2-50b4-4196-8391-1f55edca6ac6
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
Start to compile TS policy InstallApplication
2/21/2014 2:05:37 PM 1744 (0x06D0)
Policy complied successfully in WMI 'root\ccm\policy\defaultmachine\requestedconfig' namespace
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
End TS policy compilation InstallApplication
2/21/2014 2:05:37 PM 1744 (0x06D0)
Get Install Directory for SMS Client InstallApplication
2/21/2014 2:05:37 PM 1744 (0x06D0)
Start to evaluate TS policy with lock InstallApplication
2/21/2014 2:05:37 PM 1744 (0x06D0)
Locked policy transaction lock successfully
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
Updating settings in \\.\root\ccm\policy\machine\actualconfig
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
RequestedConfig policy instance(s) : 434 InstallApplication
2/21/2014 2:05:37 PM 1744 (0x06D0)
Locked \\.\ROOT\CCM\Policy\Machine\RequestedConfig for source SMS:Client:Default:{BFDADC41-FDCD-4B9C-B446-8A818D01BEA3} successfully
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
Namespace: \\.\ROOT\CCM\Policy\Machine\RequestedConfig, Query: SELECT PolicyID FROM CCM_Policy_Policy5 WHERE (PolicySource = "SMS:Client:Default:{BFDADC41-FDCD-4B9C-B446-8A818D01BEA3}") AND (PolicyState = "Active") AND (PolicyType = "Machine")
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
There is no ccm_policy_policy instance, skipping addition to realinst map
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
Unlocked \\.\ROOT\CCM\Policy\Machine\RequestedConfig for source SMS:Client:Default:{BFDADC41-FDCD-4B9C-B446-8A818D01BEA3} successfully
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
RequestedConfig policy instance(s) : 0 InstallApplication
2/21/2014 2:05:37 PM 1744 (0x06D0)
Locked \\.\ROOT\CCM\Policy\Machine\RequestedConfig for source SMS:TOS successfully
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
Namespace: \\.\ROOT\CCM\Policy\Machine\RequestedConfig, Query: SELECT PolicyID FROM CCM_Policy_Policy5 WHERE (PolicySource = "SMS:TOS") AND (PolicyState = "Active") AND (PolicyType = "Machine")
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
There is no ccm_policy_policy instance, skipping addition to realinst map
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
Unlocked \\.\ROOT\CCM\Policy\Machine\RequestedConfig for source SMS:TOS successfully
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
RequestedConfig policy instance(s) : 0 InstallApplication
2/21/2014 2:05:37 PM 1744 (0x06D0)
Locked \\.\ROOT\CCM\Policy\Machine\RequestedConfig for source CcmPortal successfully
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
Namespace: \\.\ROOT\CCM\Policy\Machine\RequestedConfig, Query: SELECT PolicyID FROM CCM_Policy_Policy5 WHERE (PolicySource = "CcmPortal") AND (PolicyState = "Active") AND (PolicyType = "Machine")
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
There is no ccm_policy_policy instance, skipping addition to realinst map
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
Unlocked \\.\ROOT\CCM\Policy\Machine\RequestedConfig for source CcmPortal successfully
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
RequestedConfig policy instance(s) : 0 InstallApplication
2/21/2014 2:05:37 PM 1744 (0x06D0)
Locked \\.\ROOT\CCM\Policy\Machine\RequestedConfig for source Local successfully
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
RequestedConfig policy instance(s) : 9 InstallApplication
2/21/2014 2:05:37 PM 1744 (0x06D0)
Unlocked \\.\ROOT\CCM\Policy\Machine\RequestedConfig for source Local successfully
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
RequestedConfig policy instance(s) : 31 InstallApplication
2/21/2014 2:05:37 PM 1744 (0x06D0)
Locked \\.\ROOT\CCM\Policy\Machine\RequestedConfig for source CcmTaskSequence successfully
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
Namespace: \\.\ROOT\CCM\Policy\Machine\RequestedConfig, Query: SELECT PolicyID FROM CCM_Policy_Policy5 WHERE (PolicySource = "CcmTaskSequence") AND (PolicyState = "Active") AND (PolicyType = "Machine")
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
There is no ccm_policy_policy instance, skipping addition to realinst map
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
Unlocked \\.\ROOT\CCM\Policy\Machine\RequestedConfig for source CcmTaskSequence successfully
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
Total RequestedConfig policy instance(s) : 474
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
Locked ActualConfig successfully InstallApplication
2/21/2014 2:05:37 PM 1744 (0x06D0)
New/Changed ActualConfig policy instance(s) : 20
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
[1] Added/updated setting 'ccm_applicationciassignment:assignmentid=dep-tos200b6-scopeid_02324d38-9750-4c09-ad8c-8c70b370484b/application_f634e9c2-50b4-4196-8391-1f55edca6ac6'.
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
[2] Added/updated setting 'ccm_civersioninfo:modelname=global/freediskspace:version=2'.
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
[3] Added/updated setting 'ccm_civersioninfo:modelname=global/platform_settings:version=4'.
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
[4] Added/updated setting 'ccm_civersioninfo:modelname=scopeid_02324d38-9750-4c09-ad8c-8c70b370484b/application_f634e9c2-50b4-4196-8391-1f55edca6ac6:version=18'.
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
[5] Added/updated setting 'ccm_civersioninfo:modelname=scopeid_02324d38-9750-4c09-ad8c-8c70b370484b/deploymenttype_0fc0a9d6-ba9d-48cd-a80f-0f21f64f9edc:version=4'.
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
[6] Added/updated setting 'ccm_civersioninfo:modelname=scopeid_02324d38-9750-4c09-ad8c-8c70b370484b/deploymenttype_916567e1-08c1-4455-85b8-1dd84c3eb96b:version=15'.
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
[7] Added/updated setting 'ccm_civersioninfo:modelname=scopeid_02324d38-9750-4c09-ad8c-8c70b370484b/requiredapplication_f634e9c2-50b4-4196-8391-1f55edca6ac6:version=18'.
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
[8] Added/updated setting 'ccm_civersioninfo:modelname=windows/all_windows_client_server:version=1'.
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
[9] Added/updated setting 'ccm_civersioninfo:modelname=windows/all_x64_windows_7_client:version=1'.
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
[10] Added/updated setting 'ccm_civersioninfo:modelname=windows/all_x64_windows_xp_professional:version=1'.
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
[11] Added/updated setting 'ccm_civersioninfo:modelname=windows/all_x86_windows_7_client:version=1'.
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
[12] Added/updated setting 'ccm_civersioninfo:modelname=windows/all_x86_windows_xp:version=1'.
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
[13] Added/updated setting 'ccm_civersioninfo:modelname=windows/x64_windows_7_client:version=1'.
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
[14] Added/updated setting 'ccm_civersioninfo:modelname=windows/x64_windows_7_sp1:version=1'.
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
[15] Added/updated setting 'ccm_civersioninfo:modelname=windows/x64_windows_xp_professional_sp2:version=1'.
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
[16] Added/updated setting 'ccm_civersioninfo:modelname=windows/x86_windows_7_client:version=1'.
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
[17] Added/updated setting 'ccm_civersioninfo:modelname=windows/x86_windows_7_sp1:version=1'.
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
[18] Added/updated setting 'ccm_civersioninfo:modelname=windows/x86_windows_xp_professional_service_pack_3:version=1'.
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
[19] Added/updated setting 'ccm_policyagent_configuration:authorityname=sms:tos'.
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
[20] Added/updated setting 'ccm_scheduler_scheduledmessage:scheduledmessageid=dep-tos200b6-scopeid_02324d38-9750-4c09-ad8c-8c70b370484b/application_f634e9c2-50b4-4196-8391-1f55edca6ac6'.
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
Unlocked ActualConfig successfully InstallApplication
2/21/2014 2:05:37 PM 1744 (0x06D0)
Unlocked policy transaction lock successfully
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
Raising event:
instance of CCM_PolicyAgent_SettingsEvaluationComplete
ClientID = "GUID:4e654285-f613-48e9-ba1f-d1d67510fb95";
DateTime = "20140221130537.864000+000";
PolicyNamespace = "\\\\.\\root\\ccm\\policy\\machine\\actualconfig";
ProcessID = 3548;
ThreadID = 1744;
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
Successfully submitted event to the Status Agent.
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
End TS policy evaluation InstallApplication
2/21/2014 2:05:37 PM 1744 (0x06D0)
Policy evaluation initiated InstallApplication
2/21/2014 2:05:37 PM 1744 (0x06D0)
Get Install Directory for SMS Client InstallApplication
2/21/2014 2:05:37 PM 1744 (0x06D0)
Start to evaluate TS policy with lock InstallApplication
2/21/2014 2:05:37 PM 1744 (0x06D0)
Locked policy transaction lock successfully
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
Updating settings in \\.\root\ccm\policy\machine\actualconfig
InstallApplication 2/21/2014 2:05:37 PM
1744 (0x06D0)
RequestedConfig policy instance(s) : 434 InstallApplication
2/21/2014 2:05:38 PM 1744 (0x06D0)
Locked \\.\ROOT\CCM\Policy\Machine\RequestedConfig for source SMS:Client:Default:{BFDADC41-FDCD-4B9C-B446-8A818D01BEA3} successfully
InstallApplication 2/21/2014 2:05:38 PM
1744 (0x06D0)
Namespace: \\.\ROOT\CCM\Policy\Machine\RequestedConfig, Query: SELECT PolicyID FROM CCM_Policy_Policy5 WHERE (PolicySource = "SMS:Client:Default:{BFDADC41-FDCD-4B9C-B446-8A818D01BEA3}") AND (PolicyState = "Active") AND (PolicyType = "Machine")
InstallApplication 2/21/2014 2:05:38 PM
1744 (0x06D0)
There is no ccm_policy_policy instance, skipping addition to realinst map
InstallApplication 2/21/2014 2:05:38 PM
1744 (0x06D0)
Unlocked \\.\ROOT\CCM\Policy\Machine\RequestedConfig for source SMS:Client:Default:{BFDADC41-FDCD-4B9C-B446-8A818D01BEA3} successfully
InstallApplication 2/21/2014 2:05:38 PM
1744 (0x06D0)
RequestedConfig policy instance(s) : 0 InstallApplication
2/21/2014 2:05:38 PM 1744 (0x06D0)
Locked \\.\ROOT\CCM\Policy\Machine\RequestedConfig for source SMS:TOS successfully
InstallApplication 2/21/2014 2:05:38 PM
1744 (0x06D0)
Namespace: \\.\ROOT\CCM\Policy\Machine\RequestedConfig, Query: SELECT PolicyID FROM CCM_Policy_Policy5 WHERE (PolicySource = "SMS:TOS") AND (PolicyState = "Active") AND (PolicyType = "Machine")
InstallApplication 2/21/2014 2:05:38 PM
1744 (0x06D0)
There is no ccm_policy_policy instance, skipping addition to realinst map
InstallApplication 2/21/2014 2:05:38 PM
1744 (0x06D0)
Unlocked \\.\ROOT\CCM\Policy\Machine\RequestedConfig for source SMS:TOS successfully
InstallApplication 2/21/2014 2:05:38 PM
1744 (0x06D0)
RequestedConfig policy instance(s) : 0 InstallApplication
2/21/2014 2:05:38 PM 1744 (0x06D0)
Locked \\.\ROOT\CCM\Policy\Machine\RequestedConfig for source CcmPortal successfully
InstallApplication 2/21/2014 2:05:38 PM
1744 (0x06D0)
Namespace: \\.\ROOT\CCM\Policy\Machine\RequestedConfig, Query: SELECT PolicyID FROM CCM_Policy_Policy5 WHERE (PolicySource = "CcmPortal") AND (PolicyState = "Active") AND (PolicyType = "Machine")
InstallApplication 2/21/2014 2:05:38 PM
1744 (0x06D0)
There is no ccm_policy_policy instance, skipping addition to realinst map
InstallApplication 2/21/2014 2:05:38 PM
1744 (0x06D0)
Unlocked \\.\ROOT\CCM\Policy\Machine\RequestedConfig for source CcmPortal successfully
InstallApplication 2/21/2014 2:05:38 PM
1744 (0x06D0)
RequestedConfig policy instance(s) : 0 InstallApplication
2/21/2014 2:05:38 PM 1744 (0x06D0)
Locked \\.\ROOT\CCM\Policy\Machine\RequestedConfig for source Local successfully
InstallApplication 2/21/2014 2:05:38 PM
1744 (0x06D0)
RequestedConfig policy instance(s) : 9 InstallApplication
2/21/2014 2:05:38 PM 1744 (0x06D0)
Unlocked \\.\ROOT\CCM\Policy\Machine\RequestedConfig for source Local successfully
InstallApplication 2/21/2014 2:05:38 PM
1744 (0x06D0)
RequestedConfig policy instance(s) : 31 InstallApplication
2/21/2014 2:05:38 PM 1744 (0x06D0)
Locked \\.\ROOT\CCM\Policy\Machine\RequestedConfig for source CcmTaskSequence successfully
InstallApplication 2/21/2014 2:05:38 PM
1744 (0x06D0)
Namespace: \\.\ROOT\CCM\Policy\Machine\RequestedConfig, Query: SELECT PolicyID FROM CCM_Policy_Policy5 WHERE (Polic

What have you configured for requirements for the app?

SCCM 2012 SP1 OSD Multicast is failing 0x80004005

I am trying to get multicast to work on a DP. But when I kick off an OSD and get to one of the items that I have enabled multicasting (lets say the OS image) then I get the following in the smsts.log:
Failed to get MCS key (Code 0x80004005)
ClientRequestToMCS::DoRequest failed. error = (0x80004005)
Request to MCS 'MYSCCMSERVER.SCCM.LOCAL' failed with error (Code 0x80004005)
Multicast OpenSessionRequest failed (0x80004005)
Sending status message: SMS_OSDeployment_PackageDownloadMulticastStatusFail
And then it reverts to a normal HTTP download. Why is this failing?

there's a thread here about issues with MCS key though this is 2007 maybe it will point you in a right direction
http://social.technet.microsoft.com/Forums/systemcenter/en-US/07c735c8-9ce9-43b9-8cf3-e7b897568ef3/sccm-multicast-mcs-signedserializedkey-is-empty
The issues I had with multicast came up when the target device was not on the same subnet and network hardware was blocking communication.

SCCM 2012 R2 - OSD issues after update to CU4

Over the weekend, I updated my SCCM environment from RTM to CU4.
All seems to have gone well, except for OSD
When attempting OSD, I receive the following error:
"An error occurred while retrieving policy for this computer (0x80004005)..."
So, a quick look over at smsts.log and I see the following:
I did some bing'in and googling around for this and found plenty of pages about this error and all pointed to incorrect BIOS times. I checked the BIOS time on the system I was trying to image, and it was correct (including date). Just in case,
I tried two more machines and I had the same issue. Each machine has the correct BIOS date/time as well, so the issue I have doesn't seem related.
... and that brings me here. Does anyone have any insight as to what might be causing the issue?
Thanks!

I noticed two thing in your log file that are worth a check:
I noticed a 404 error in your log file that might indicate an issue with some files that can't be found. Check the IIS log file for more information;
I noticed that you're using HTTPS. I've seen weird issues after a CU update in which the distribution point certificate got missing. In that case, check the distribution point properties and update the boot image.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude
I did miss the 404 message... silly me.
This definitely pointed in the right direction. What we found was that it wasn't an issue IIS or the https certificate, but our certificate chain had issues. We cleared out the certificate chain issues and re-installed the MP role. This
cleared the issue immediately.
Thanks Peter for the guidance!

SCCM 2012 R2 OSD Task Sequence option

Hi, What to have an Install Applications step option that will identify computer record names with embed names for example
embedded name XXX inside a computer record for example:
Tabletxxx01
Tabletxxx02
Tabletabc01 - this computer record would skip the TS step.
Thanks!

Hi,
Here are an example on a WMI query checking for a computername using wildcards,.
http://fritschetom.blogspot.com/2012/03/sccm-task-sequence-add-wmi-condition.html
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

SCCM 2012 R2 OSD - Pre Provision Bit-Locker Drive Label Name Issues

Similar Messages

Maybe you are looking for