Quantcast
Channel: Configuration Manager 2012 - Operating System Deployment forum
Viewing all 9126 articles
Browse latest View live

MDT 2012 Update 1 Boot Image Creation Fails in SP1

$
0
0

I have my site server (SCCM 2012 SP1) installed on Server 2012 with the Windows 8 ADK installed (I've also tried installing the Win7 WAIK with no change to the below problem). It is hosting the site server, FSP, AIS, and Endpoint protection roles. I installed MDT 2012 Update 1 (build 6.1.2373.0) and installed ConfigMgr integration. I have a share\\siteserver\bootimages that I'm creating the boot image to and the system account has full control on both the NTFS and Share permissions. When I create the boot image I get an error almost immediately and a popup that the Microsoft.BDD.ElevatedProxy has stopped working. Details from the pop-up:

Description:
  Stopped working

Problem signature:
  Problem Event Name: CLR20r3
  Problem Signature 01: microsoft.bdd.elevatedproxy.exe
  Problem Signature 02: 3.0.0.0
  Problem Signature 03: 50400c36
  Problem Signature 04: System.ServiceModel
  Problem Signature 05: 3.0.0.0
  Problem Signature 06: 4fee6b19
  Problem Signature 07: fb9
  Problem Signature 08: a7
  Problem Signature 09: G3DT0URDW53KGT4VJDEEQCRAUIFCNTLL
  OS Version: 6.2.9200.2.0.0.272.7
  Locale ID: 1033

The error in the boot image creation wizard is:

Started processing.
Creating boot image.
Error while importing Microsoft Deployment Toolkit Task Sequence.

System.ServiceModel.FaultException: The server was unable to process the request due to an internal error.  For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework 3.0 SDK documentation and inspect the server trace logs.

Server stack trace:
   at System.ServiceModel.Channels.ServiceChannel.ThrowIfFaultUnderstood(Message reply, MessageFault fault, String action, MessageVersion version, FaultConverter faultConverter)
   at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc)
   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at INewBootImage.Create(String platform, String scratchSpace, String[] components, String[] extraContent, String wimFile)
   at NewBootImageClient.Create(String platform, String scratchSpace, String[] components, String[] extraContent, String wimFile)
   at Microsoft.BDD.Wizards.SCCM_ImportTaskSequenceTask.DoWork(SmsPageData smspageData, Dictionary`2 data)

I haven't found anything online on this particular error, I've seen all the ones about MDT 2012 and ConfigMgr 2012 CU 1. Any ideas? Any logs that may be revealing to the cause of this error? I've tried removing integration components, uninstalling MDT, reboot, re-installing, etc, but same problem occurs each time.


Boot image quantity and requirements

$
0
0
While reading up on MDT, I created a new boot image while creating an MDT task sequence even though I had one. It seems based on SMSPXE.log that the newest one was used to boot the client and both my native and MDT sequence were available for selection.

So is it reasonable to say you only need at most two boot images for both architectures, or what is the criteria by which a boot image is chosen for a PXE client and how do you control this for new deployments?

Boot wim generates errors in SMSPXE.log

$
0
0
I have created a couple task sequences and noticed they both generate a series of invalid file errors followed by a message that indicates the image needs to be updated:

<![LOG[Invalid file version '' found]LOG]!><time="18:55:28.606+360" date="09-05-2016" component="SMSPXE" context="" type="3" thread="8908" file="util.cpp:1530"><![LOG[CcmGetFileVersion failed with 0x80004005]LOG]!><time="18:55:28.606+360" date="09-05-2016" component="SMSPXE" context="" type="2" thread="8908" file="util.cpp:1553"><![LOG[Failed to retrieve the version of file 'E:\RemoteInstall\SMSBoot\Fonts\wgl4_boot.ttf'. Error code: 0x80004005]LOG]!><time="18:55:28.606+360" date="09-05-2016" component="SMSPXE" context="" type="3" thread="8908" file="miscutil.cpp:38"><![LOG[Looking for bootImage PS100010]LOG]!><time="18:55:33.765+360" date="09-05-2016" component="SMSPXE" context="" type="1" thread="3820" file="bootimagemgr.cpp:1774"><![LOG[BootImage PS100010 needs to be updated (new packageID=PS100010) VersionUpdate=true]LOG]!><time="18:55:33.765+360" date="09-05-2016" component="SMSPXE" context="" type="1" thread="3820" file="bootimagemgr.cpp:1786"><![LOG[PXE::CBootImageInfo::CBootImageInfo: key=PS100010]LOG]!><time="18:55:33.765+360" date="09-05-2016" component="SMSPXE" context="" type="1" thread="3820" file="bootimagecache.cpp:60">

What exactly is the cause of this?

WINHTTP_CALLBACK_STATUS_FLAG_invalid_ca

$
0
0

I have a problem with OSD task sequence - just for tests I imported WinPE 10 from our development environment from SCCM 2012 to our production environment. I am able to boot laptop from PXE then after providing password computer restarts automatically. If I press F8 before restart I see smsts.log where I can find an error:

WINHTTP_CALLBACK_STATUS_FLAG_invalid_ca

I already looked at:

https://social.technet.microsoft.com/Forums/en-US/f6eedffe-25a4-48e8-bc9c-e9e30551794f/certificates-and-other-domains?forum=configmanagergeneral

but this is not the same issue as I am not in full Windows OS but in WinPE. I also checked date and time in BIOS - looks ok. I am able to run another OSD task sequence on this laptop from our SCCM (using different WinPE of course).

I am wondering what certificates are used\checked during WinPE phase when contacting with MP ? How to check it?

Our Management Point is set to HTTP - client connections

Deploy image with PXE error: pending request id 8

$
0
0

Hi

im loosing my mind here :-)

SCCM 2012 i prepared PXE and OS to deploy

when i boot my pc i get response from pxe that is : "pending request id 8"

message from administrator: configuration manager is looking for policy

in the smspxe.log i see:

 mac address follow with some id "no advertisement found"

help please...

HP Zbook Studio G3 BSOD's upon first reboot when OS and drivers have been deployed

$
0
0

I am using SCCM 2012 R2 to deploy an image Windows 7 Ent SP1 x64 to this system. I use this same image for all other HP devises with no issues. I downloaded and expanded the driver package SP73082 and installed those drivers on SCCM like I have for all other devices. Upon the completion of installing the OS and drivers and at the first reboot the system will BSOD and restart, at which point I attempt to stop the page from changing with no luck, so am unable to capture the error code that is being generated. I validated that the drivers were the correct ones, the number of files and folders are the same. I even changed the amount of RAM to see if that was the issue to no avail.

Troubleshooting steps:

I have validated that the drivers are the correct ones for this model and OS.
I have verified that the drivers are setup correctly within SCCM 2012 and are being pushed out to the system during the installation process.
There is nothing that shows this system is failing to load any of the drivers or that it is having an issue with the OS.
The system once the initial reboot happens continues to BSOD. Even attempting to load in safe mode does not resolve. Loads up to disk.sys and fails.

I used this image today to image a HP Elitebook Folio 1040 G2 with no issues so I know the image is working.

I also verified that the drivers when uncompressed match what was imported into SCCM to deploy to this system.

Any assistance with understanding what could be causing this would be great. 

Mark Reny

OSD for Virtual Servers

$
0
0

Been tasked with automating Server OSD in Virtual environment. 2008/2012/2016... Are any of you doing this today any thoughts/blog post you would like to share or how you are accomplishing this today would be great.

Running SCCM 2012 R2 right now.

Problem when trying to picture deploy in CCE equipment with motherboard ECS Model H55H

$
0
0
Good Morning!

I'm sorry forwhat is writtenbecause I amusinggoogle translatorto express myself.

InCCEequipmentwithmotherboardECSModelH55H-M2for example,can notperformdeploybecause the systemidentifies thathas no tasksfor this model.In my opinionandaccording to some explanations thatpassedmeit seems that theSIDboardis duplicated andSystem Centeridentifiesthe equipmentis already added to thedevices.I wonder ifthere is any waytoget around this.

Grateful for theattention.


Traffic on subnet with PXE boot

$
0
0

Hello

I have a DHCP server and WDS&SCCM server on the same subnet. I have option 066 and 067 configured on my DHCP. The computers are in other subnet.

It had worked without traffic, but some days ago Network team told me that they see a lot of traffic in their IDF. 

We import the MAC and name to SCCM server. When 4 computers try to take the image, the others computer on the same subnet have 100% network utilization on LAN card. They dont try to get a PXE boot.

What can I review to resolve it?  some log?
Thanks in advance


WDS Server not starting

$
0
0

Hi all, I hope this is the correct place.

I have 6 server currently doing this. They are all Server 2008 R2 Standard.

I have removed PXE and Multicast from the DP and uninstalled WDS. Reboot and reinstall all 3. The server works for a couple of hours and then quits. I get 2 error messages when it stops.

Error 1:

The description for Event ID 258 from source WDSIMGSRV cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event: 
0xC1030104

Error 2 (technically it's a warning):

An error occurred while trying to initialize provider WdsImgSrv from C:\Windows\system32\WdsImgSrv.dll. Since this provider is not marked as critical, Windows Deployment Services server will  continue.
Error Information: 0xC1030104 

When I run the WDSUtil command verbose I get this:

Windows Deployment Services Management Utility [Version 6.1.7600.16385]
Copyright (C) Microsoft Corporation. All rights reserved.

Setting up server...

-> Creating the installation tree for Windows Deployment Services
---> Creating the installation root for Windows Deployment Services at \\<DP>\E$\RemoteInstall
---> Creating the share for Windows Deployment Services at \\<DP>\REMINST
---> Creating the folder for Windows Deployment Services at \\<DP>\REMINST\Images
---> Creating the folder for Windows Deployment Services at \\<DP>\REMINST\Boot
---> Creating the folder for Windows Deployment Services at \\<DP>\REMINST\Boot\x86\Images
---> Creating the folder for Windows Deployment Services at \\<DP>\REMINST\Boot\ia64\Images
---> Creating the folder for Windows Deployment Services at \\<DP>\REMINST\Boot\x64\Images
---> Creating the folder for Windows Deployment Services at \\<DP>\REMINST\Boot\Fonts
---> Creating the folder for Windows Deployment Services at \\<DP>\REMINST\Tmp
---> Creating the folder for Windows Deployment Services at \\<DP>\REMINST\Mgmt
---> Creating the folder for Windows Deployment Services at \\<DP>\REMINST\WdsClientUnattend
---> Creating the folder for Windows Deployment Services at \\<DP>\REMINST\Templates
---> Creating the folder for Windows Deployment Services at \\<DP>\REMINST\Stores\Drivers
---> Creating the folder for Windows Deployment Services at \\<DP>\REMINST\Stores\Staging
---> Creating the folder for Windows Deployment Services at \\<DP>\REMINST\Stores\Drivers\Metadata\Backup
-> Installing Windows Deployment Services files
---> Installing system files
.
---> Installing boot files for x86
..........
---> Installing boot files for ia64
..
---> Installing boot files for x64
...........
-> Updating the registry
-> Configuring the TFTP provider
-> Configuring the service control point for BINL
Enabling services for Windows Deployment Services...
Starting the services for Windows Deployment Services...

An error occurred while trying to execute the command.
Error Code: 0x41D
Error Description: The service did not respond to the start or control request in a timely fashion.

After that, I get 2 errors every time it tried to start back up.

An error occurred while trying to initialize provider WDSMC from C:\Windows\system32\wdsmc.dll. Windows Deployment Services server will be shutdown.
Error Information: 0x7E 

And

An error occurred while trying to start the Windows Deployment Services server. 
Error Information: 0x7E 

If there are any log files I can get more information from, please let me know. But as it stands, this is all I have at the moment. And I have another 35+ server that are currently working. 

Thank you

Charles

Installing a cert during OSD

$
0
0

I need to install a cert during my TS previous to an application within the TS. From what reading I have done I have come up with a package/run command task and am looking for some confirmation on what I have so far.

I have created a package with no program pointing to the folder containing the cert and certutil.exe. I am running the following in my TS run cmd task: certutil -addstore root entrust_2048_ca.cer


tconners


Task Sequence: Image Capture Wizard has failed with the error code (0x80070079).

$
0
0
I'm trying to capture an image for a new PC and I keep getting the above error. I have not been able to find anything on this error. I am capturing the image to an external drive. 

WDS service will not start after adding Multicast function on DP

$
0
0

We have been adding the Multicast function to DP's for about two years and the last time it worked was before 1503. Since upgrading anytime we add the Multicast function to a standalone DP it stops the WDS service. Removing the Multicast option allows WDS to start again. I have tried removing PXE and Multicast but leave the role installed. then manually remove WDS role, reboot, delete Remote install folder, install WDS role, reboot, and adding the PXE/Multicast function back. Same results.

I have seen many forum posts in steps to try and fix this, but none have worked so far. The issue happens on Server 2008 r2 and server 2012 R2. below are the errors that come up after the Multicast function is installed. SCCM logs show no failures as I can see and site/components statuses all show green.

Here are the error logs.

event ID 257
An error occurred while trying to start the Windows Deployment Services server.

 Error Information: 0x2 

event ID 513
An error occurred while trying to initialize provider WDSMC from C:\Windows\system32\wdsmc.dll. Windows Deployment Services server will be shutdown.

 Error Information: 0x2 

Event ID: 603
The Content Provider SMSProvider failed to initialize. The provider is marked as critical. WDS Multicast server will fail to start.

 Error Information: 0x2 

Event ID: 594
The Content Provider SMSProvider loaded from C:\Windows\CCM\smswdstp.dll failed to initialize.

 Error Information: 0x2 


We are also on version 1602 Hotfix  (5.00.8355.1306)




Intel i217/8-LM Network Drivers will not install during OSD to W10

$
0
0

Hi, 

We have hit an issue that it seems many other people are having, i cannot install NIC drivers for the Intel i217-LM Network Card. My particular issue is on the HP 800 G1 USDT (one revision of it). 

(this issue is also present on multiple Dell models)

I have downloaded the last 9 driver revisions directly from intel and attempted to apply using both the "Auto Apply Drivers" and "Install Driver Package" steps (directed at model WMI query). 

Here are some of the many driver versions i have attempted to apply:

The Task Sequence will fail 90% of the time when attempting to bind to the domain , the other 10% will fail at the very next step, all of course post "Setup Windows and ConfigMGR". I have no issues with this NIC from within WINPE, it fails over shortly after rebooting into windows.

If i run a continuous ipconfig/all i can see the NIC stable and fine and then it will disappear on next reboot (first reboot into windows). On next reboot my TS has failed and usually i will see "Network Cable Unplugged" - this will only go away when i look into devicemanager and disable/enable the NIC. 

You can also see in device manager the NIC driver that ALWAYS shows, 12.13.17.7 this is what i always see even if i attempt to install different versions.

The below screenshot is from device manager, note the confusing version number and dates?

I cant see how 12.15.22.3 was from 2015 whereas 12.13.17.7 is listed as 2016

My last test yesterday was to attempt to inject the latest driver directly into my Windows10 Wim file, which also did not work.

The file i injected:


Others with this issue please append to this post so we can get a response on this issue. 

here are some screenshots from smsts.log


other discussions: 

https://www.reddit.com/r/SCCM/comments/46fgxi/intel_i217lm_on_hp_800g1_windows_10/

https://social.technet.microsoft.com/Forums/en-US/2a8aec4c-ea09-4f46-898d-ce692ee01c9c/osd-not-working-on-hp-zbook-14-g2?forum=configmanagerosd

https://www.reddit.com/r/SCCM/comments/41j96p/new_machines_with_intel_i217lm_and_i218lm_nics/

https://social.technet.microsoft.com/Forums/en-US/d24fb24a-c61b-4086-b417-2614f9f35549/hp-elitedesk-800-g1-with-the-intel-i217lm-nic-and-wds-on-server-2012-both-r2-and-nonr2?forum=w7itproinstall


Purge Cache when an Application Group Installs in a task sequence

$
0
0

<g class="gr_ gr_104 gr-alert gr_gramm gr_run_anim Punctuation only-ins replaceWithoutSep" data-gr-id="104" id="104">Hi</g> Could someone tell me how I can purge the Cache during a task Sequence deployment?  I currently have SPSS and SAS eating up a great deal of space.  I would like to blow away the cache files when they are complete so the task sequence can continue.

Thanks


Getting Windows Setup Failed Code 31

$
0
0

Trying a new deployment from a new SCCM server and have been getting Windows setup failed code 31. I have captured all the logs and can post them if needed.

In the SMSTSLog I have a few warnings about drivers and a couple other warnings

Unsuccessful in finding a suitable device driver for device 'High Definition Audio Controller'.OSDDriverClient9/6/2016 3:53:41 PM1804 (0x070C)
Unsuccessful in finding a suitable device driver for device 'High Definition Audio Controller'.OSDDriverClient9/6/2016 3:53:41 PM1804 (0x070C)
Unsuccessful in finding a suitable device driver for device 'USB Mass Storage Device'.OSDDriverClient9/6/2016 3:53:41 PM1804 (0x070C)
Unsuccessful in finding a suitable device driver for device 'Microsoft System Management BIOS Driver'.OSDDriverClient9/6/2016 3:53:42 PM1804 (0x070C)
Unsuccessful in finding a suitable device driver for device 'Plug and Play Software Device Enumerator'.OSDDriverClient9/6/2016 3:53:45 PM1804 (0x070C)

RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgramTSManager9/6/2016 4:09:02 PM1472 (0x05C0)
GetTsRegValue() is unsuccessful. 0x80070002. TSManager9/6/2016 4:09:02 PM1472 (0x05C0)
RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgramTSBootShell9/6/2016 4:09:02 PM996 (0x03E4)
GetTsRegValue() is unsuccessful. 0x80070002. TSBootShell9/6/2016 4:09:02 PM996 (0x03E4)

And These Errors

Windows setup failed, code 31OSDSetupWindows9/6/2016 3:53:55 PM1368 (0x0558)
Failed to run the action: Setup Windows and ConfigMgr. 
Unspecified error (Error: 80004005; Source: Windows)TSManager9/6/2016 3:53:55 PM1472 (0x05C0)
The group (Execute Task Sequence) ignored action failure and continue execution on the next step following the group.TSManager9/6/2016 3:53:55 PM1472 (0x05C0)
Start executing an instruction. Instruction name: Gather Logs and StateStore on Failure. Instruction pointer: 132TSManager9/6/2016 3:53:55 PM1472 (0x05C0)
Set a global environment variable _SMSTSCurrentActionName=Gather Logs and StateStore on FailureTSManager9/6/2016 3:53:55 PM1472 (0x05C0)
The condition for the group (Gather Logs and StateStore on Failure) is evaluated to be trueTSManager9/6/2016 3:53:55 PM1472 (0x05C0)
The group (Gather Logs and StateStore on Failure) has been successfully startedTSManager9/6/2016 3:53:55 PM1472 (0x05C0)
ZTI deployment failed, Return Code = -2147467259  0x80004005InstallSoftware9/6/2016 3:53:59 PM1480 (0x05C8)
Failed to run the action: Error in the task sequence. 

Unspecified error (Error: 80004005; Source: Windows)TSManager9/6/2016 3:53:59 PM1472 (0x05C0)

Let the parent group (Gather Logs and StateStore on Failure) decides whether to continue executionTSManager9/6/2016 3:53:59 PM1472 (0x05C0)
The execution of the group (Gather Logs and StateStore on Failure) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows)TSManager9/6/2016 3:53:59 PM1472 (0x05C0)
Failed to run the last action: Error in the task sequence. Execution of task sequence failed.
Unspecified error (Error: 80004005; Source: Windows)TSManager9/6/2016 3:53:59 PM1472 (0x05C0)

Execution::enExecutionFail != m_eExecutionResult, HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmanager\tsmanager.cpp,1087)TSManager9/6/2016 4:09:01 PM1472 (0x05C0)
Task Sequence Engine failed! Code: enExecutionFail TSManager9/6/2016 4:09:01 PM1472 (0x05C0)
Task sequence execution failed with error code 80004005TSManager9/6/2016 4:09:01 PM1472 (0x05C0)
Failed to delete directory 'C:\_SMSTaskSequence' TSManager9/6/2016 4:09:02 PM1472 (0x05C0)
SetNamedSecurityInfo() failed.TSManager9/6/2016 4:09:02 PM1472 (0x05C0)
SetObjectOwner() failed. 0x80070005.TSManager9/6/2016 4:09:02 PM1472 (0x05C0)
RemoveFile() failed for C:\_SMSTaskSequence\TSEnv.dat. 0x80070005.TSManager9/6/2016 4:09:02 PM1472 (0x05C0)
RemoveDirectoryW failed (0x80070091) for C:\_SMSTaskSequenceTSManager9/6/2016 4:09:02 PM1472 (0x05C0)

Can i deploy Windows 10 Education vía System Center 2012 Configuration Manager R2 SP1 CU3 with ADK 1511?

$
0
0

Hi Technet masters,

I Need help because i need to deploy windows 10 education to my desktop's via SCCM 2012 R2 SP1 CU3 w/ADK1511 but i'm not sure if windows 10 education has support for being used in OS Deployment via SCCM.

Need some help here and official Links with the information.

i'll appreciate your help thanks

The version specific of windows 10 is 1607 from July 2016 release. According to these article 

https://blogs.technet.microsoft.com/enterprisemobility/2015/10/27/system-center-configuration-manager-support-for-windows-10-and-microsoft-intune/

this version is only supported by System center current branch but im not sure what version is. all the information is very confuse.


Best Regards - Saludos cordiales Juan Carrillo Vaccaris,

Latinshare Chile. E-Mail: JCarrillo@latinshare.com Website: http://www.Latinshare.com


Software Updates hand - W10 Task sequence with Bitlocker

$
0
0

Have setup new TS for Windows 10 Enterprise under R2 SP1 CU1. I apply the Software Updates step after installing apps so that it picks up all the updates including Office 2013. On laptops I am enabling Bitlocker. I'm finding the SU step finds about 57 patches, downloads then starts applying and then stops at particular office updates - nothing showing in SMSTS.log other than "Waiting for RefreshUpdates complete notification from Updates Deployment Agent". Strangely a desktop (non bitlocker) works just fine i.e. applies all the patches without fail. So I've had to move the apply SU step higher up so it only applies O/S updates and that is ok. I tried taking specific update it was failing out of the SU group but it hangs at a different Office update, but as I say never a problem with the desktop - same build just no bitlocker. I also tried moving the bitlocker step below the software updates to no avail. The TS never times out - i.e. still sitting there over night hanging at the SU step


Ian Burnell, London (UK)

TS don't continue after the first restart

$
0
0

Hi all,

I have a strange issue in one environment. I have created a few TS with different steps but I have seen that none of then are finished during the deployment. So after the first reboot is made computer is comeback with windows logon window. I didn't find any errors in SMSTS.log. SCCM client is copied but not installed, no cmd commands and apps executed, nothing.

Please find attached last part from my log:

Start executing the command line: osdnetsettings.exe configure TSManager 23/06/2016 15:58:18 1188 (0x04A4)
!--------------------------------------------------------------------------------------------! TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Expand a string: WinPEandFullOS TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Executing command line: osdnetsettings.exe configure TSManager 23/06/2016 15:58:18 1188 (0x04A4)
==============================[ OSDNetSettings.exe ]=========================== OSDNetSettings 23/06/2016 15:58:18 1960 (0x07A8)
Command line: "osdnetsettings.exe" configure OSDNetSettings 23/06/2016 15:58:18 1960 (0x07A8)
Setting %SystemRoot% to "C:\Windows" OSDNetSettings 23/06/2016 15:58:18 1960 (0x07A8)
Loading existing answer file "C:\Windows\panther\unattend\unattend.xml" OSDNetSettings 23/06/2016 15:58:18 1960 (0x07A8)
Configuring global network settings OSDNetSettings 23/06/2016 15:58:18 1960 (0x07A8)
Join type: 1 OSDNetSettings 23/06/2016 15:58:18 1960 (0x07A8)
Joining workgroup: workgroup-test OSDNetSettings 23/06/2016 15:58:18 1960 (0x07A8)
Getting namespace "Microsoft-Windows-UnattendedJoin" for architecture "amd64" OSDNetSettings 23/06/2016 15:58:18 1960 (0x07A8)
DNS domain:  OSDNetSettings 23/06/2016 15:58:18 1960 (0x07A8)
DNS domain search order:  OSDNetSettings 23/06/2016 15:58:18 1960 (0x07A8)
IP filter sec enabled: false OSDNetSettings 23/06/2016 15:58:18 1960 (0x07A8)
No adapters found in environment.  Performing global configuration only. OSDNetSettings 23/06/2016 15:58:18 1960 (0x07A8)
Writing configuration information to C:\Windows\panther\unattend\unattend.xml OSDNetSettings 23/06/2016 15:58:18 1960 (0x07A8)
Successfully saved configuration information to C:\Windows\panther\unattend\unattend.xml OSDNetSettings 23/06/2016 15:58:18 1960 (0x07A8)
Configuring "OSDNetSettings.exe finalize" to run on first boot OSDNetSettings 23/06/2016 15:58:18 1960 (0x07A8)
OSDNetSettings finished: 0x00000000 OSDNetSettings 23/06/2016 15:58:18 1960 (0x07A8)
Process completed with exit code 0 TSManager 23/06/2016 15:58:18 1188 (0x04A4)
!--------------------------------------------------------------------------------------------! TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Successfully completed the action (Apply Network Settings) with the exit win32 code 0 TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Do not send status message in full media case TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Set a global environment variable _SMSTSLastActionRetCode=0 TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Set a global environment variable _SMSTSLastActionSucceeded=true TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Expand a string: %_SMSTSMDataPath%\Logs TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Clear local default environment TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Updated security on object C:\_SMSTaskSequence. TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Set a global environment variable _SMSTSNextInstructionPointer=7 TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Set a TS execution environment variable _SMSTSNextInstructionPointer=7 TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Set a global environment variable _SMSTSInstructionStackString=0 TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Set a TS execution environment variable _SMSTSInstructionStackString=0 TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Save the current environment block TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Successfully save execution state and environment to local hard disk TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Start executing an instruction. Instruction name: Install Operating System. Instruction pointer: 7 TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Set a global environment variable _SMSTSCurrentActionName=Install Operating System TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Set a global environment variable _SMSTSNextInstructionPointer=7 TSManager 23/06/2016 15:58:18 1188 (0x04A4)
The group (Install Operating System) has been successfully completed TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Do not send status message in full media case TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Updated security on object C:\_SMSTaskSequence. TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Set a global environment variable _SMSTSNextInstructionPointer=8 TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Set a TS execution environment variable _SMSTSNextInstructionPointer=8 TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Set a global environment variable _SMSTSInstructionStackString= TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Set a TS execution environment variable _SMSTSInstructionStackString= TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Save the current environment block TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Successfully save execution state and environment to local hard disk TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Start executing an instruction. Instruction name: Setup Operating System. Instruction pointer: 8 TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Set a global environment variable _SMSTSCurrentActionName=Setup Operating System TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Set a global environment variable _SMSTSNextInstructionPointer=8 TSManager 23/06/2016 15:58:18 1188 (0x04A4)
The group (Setup Operating System) has been successfully started TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Do not send status message in full media case TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Updated security on object C:\_SMSTaskSequence. TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Set a global environment variable _SMSTSNextInstructionPointer=9 TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Set a TS execution environment variable _SMSTSNextInstructionPointer=9 TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Set a global environment variable _SMSTSInstructionStackString=8 TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Set a TS execution environment variable _SMSTSInstructionStackString=8 TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Save the current environment block TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Successfully save execution state and environment to local hard disk TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Start executing an instruction. Instruction name: Setup Windows and Configuration Manager. Instruction pointer: 9 TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Set a global environment variable _SMSTSCurrentActionName=Setup Windows and Configuration Manager TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Set a global environment variable _SMSTSNextInstructionPointer=9 TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Set a local default variable SMSClientInstallProperties TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Set a local default variable _SMSClientPackageID TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Set a global environment variable _SMSTSLogPath=X:\windows\TEMP\SMSTSLog TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Expand a string: OSDSetupWindows.exe TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Expand a string:  TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Command line for extension .exe is "%1" %* TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Set command line: OSDSetupWindows.exe TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Start executing the command line: OSDSetupWindows.exe TSManager 23/06/2016 15:58:18 1188 (0x04A4)
!--------------------------------------------------------------------------------------------! TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Expand a string: WinPEandFullOS TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Executing command line: OSDSetupWindows.exe TSManager 23/06/2016 15:58:18 1188 (0x04A4)
==============================[ OSDSetupWindows.exe ]=========================== OSDSetupWindows 23/06/2016 15:58:18 1880 (0x0758)
Command line: "OSDSetupWindows.exe" OSDSetupWindows 23/06/2016 15:58:18 1880 (0x0758)
ResolveSource flags: 0x00000000 OSDSetupWindows 23/06/2016 15:58:18 1880 (0x0758)
SMSTSPersistContent: . The content for package NTM00075 will be persisted OSDSetupWindows 23/06/2016 15:58:18 1880 (0x0758)
Package location: _SMSTSNTM00075, file:VOL001:\SMS\PKG\NTM00075 OSDSetupWindows 23/06/2016 15:58:18 1880 (0x0758)
Searching C:\ for Fullmedia content OSDSetupWindows 23/06/2016 15:58:18 1880 (0x0758)
Searching D:\ for Fullmedia content OSDSetupWindows 23/06/2016 15:58:18 1880 (0x0758)
Found Fullmedia content in drive D:\. OSDSetupWindows 23/06/2016 15:58:18 1880 (0x0758)
Entering ReleaseSource() for D:\SMS\PKG\NTM00075 OSDSetupWindows 23/06/2016 15:58:18 1880 (0x0758)
The user tries to release a source directory D:\SMS\PKG\NTM00075 that is either already released or we have not connected to it OSDSetupWindows 23/06/2016 15:58:18 1880 (0x0758)
Command line for extension .EXE is "%1" %* OSDSetupWindows 23/06/2016 15:58:18 1880 (0x0758)
Set command line: "X:\sms\bin\x64\OSDSETUPHOOK.EXE" "/configure:C:\Windows\SYSTEM32" /version:6.1 OSDSetupWindows 23/06/2016 15:58:18 1880 (0x0758)
Executing command line: "X:\sms\bin\x64\OSDSETUPHOOK.EXE" "/configure:C:\Windows\SYSTEM32" /version:6.1 OSDSetupWindows 23/06/2016 15:58:18 1880 (0x0758)
Configuring OSD setup hook OSDSetupHook 23/06/2016 15:58:18 1696 (0x06A0)
Configuring setup hook OSDSetupHook 23/06/2016 15:58:18 1696 (0x06A0)
Resolving source for SMS client, package ID = NTM00003. OSDSetupHook 23/06/2016 15:58:18 1696 (0x06A0)
ResolveSource flags: 0x00000000 OSDSetupHook 23/06/2016 15:58:18 1696 (0x06A0)
SMSTSPersistContent: . The content for package NTM00003 will be persisted OSDSetupHook 23/06/2016 15:58:18 1696 (0x06A0)
Package location: _SMSTSNTM00003, file:VOL001:\SMS\PKG\NTM00003 OSDSetupHook 23/06/2016 15:58:18 1696 (0x06A0)
Searching C:\ for Fullmedia content OSDSetupHook 23/06/2016 15:58:18 1696 (0x06A0)
Searching D:\ for Fullmedia content OSDSetupHook 23/06/2016 15:58:18 1696 (0x06A0)
Found Fullmedia content in drive D:\. OSDSetupHook 23/06/2016 15:58:18 1696 (0x06A0)
Copying SMS client package source from "D:\SMS\PKG\NTM00003" to "C:\_SMSTaskSequence\OSD\NTM00003". OSDSetupHook 23/06/2016 15:58:18 1696 (0x06A0)
Locating architecture-specific OSDGina.dll OSDSetupHook 23/06/2016 15:58:29 1696 (0x06A0)
Successfully copied file OSDSETUPHOOK.EXE to C:\Windows\SYSTEM32 OSDSetupHook 23/06/2016 15:58:29 1696 (0x06A0)
Successfully copied file TSProgressUI.exe to C:\Windows\SYSTEM32\_SMSOSDSetup OSDSetupHook 23/06/2016 15:58:29 1696 (0x06A0)
Successfully copied file tsres.dll to C:\Windows\SYSTEM32\_SMSOSDSetup\1033 OSDSetupHook 23/06/2016 15:58:29 1696 (0x06A0)
Saving desktop wallpaper information. OSDSetupHook 23/06/2016 15:58:29 1696 (0x06A0)
Entering ReleaseSource() for D:\SMS\PKG\NTM00003 OSDSetupHook 23/06/2016 15:58:29 1696 (0x06A0)
The user tries to release a source directory D:\SMS\PKG\NTM00003 that is either already released or we have not connected to it OSDSetupHook 23/06/2016 15:58:29 1696 (0x06A0)
Exiting ConfigureEx: 0x00000000 OSDSetupHook 23/06/2016 15:58:29 1696 (0x06A0)
Process completed with exit code 0 OSDSetupWindows 23/06/2016 15:58:29 1880 (0x0758)
Installing hook to 'C:\Windows' OSDSetupWindows 23/06/2016 15:58:29 1880 (0x0758)
Command line for extension .EXE is "%1" %* OSDSetupWindows 23/06/2016 15:58:29 1880 (0x0758)
Set command line: "X:\sms\bin\x64\OSDSETUPHOOK.EXE" "/install:C:\Windows" /version:6.1 OSDSetupWindows 23/06/2016 15:58:29 1880 (0x0758)
Executing command line: "X:\sms\bin\x64\OSDSETUPHOOK.EXE" "/install:C:\Windows" /version:6.1 OSDSetupWindows 23/06/2016 15:58:29 1880 (0x0758)
Installing OSD setup hook OSDSetupHook 23/06/2016 15:58:29 1748 (0x06D4)
Setup hook install completed successfully OSDSetupHook 23/06/2016 15:58:29 1748 (0x06D4)
Process completed with exit code 0 OSDSetupWindows 23/06/2016 15:58:29 1880 (0x0758)
OfflineRegistry::Init("C:\Windows") OSDSetupWindows 23/06/2016 15:58:29 1880 (0x0758)
Loading offline registry hive "C:\Windows\system32\config\software" into HKLM\OfflineRegistry1 OSDSetupWindows 23/06/2016 15:58:29 1880 (0x0758)
Loading offline registry hive "C:\Windows\system32\config\system" into HKLM\OfflineRegistry2 OSDSetupWindows 23/06/2016 15:58:31 1880 (0x0758)
CurrentControlSet is mapped to ControlSet001 OSDSetupWindows 23/06/2016 15:58:31 1880 (0x0758)
SMS Client is not installed OSDSetupWindows 23/06/2016 15:58:31 1880 (0x0758)
Unloading offline SOFTWARE registry hive OSDSetupWindows 23/06/2016 15:58:31 1880 (0x0758)
Unloading offline SYSTEM registry hive OSDSetupWindows 23/06/2016 15:58:31 1880 (0x0758)
Exiting with code 0x00000000 OSDSetupWindows 23/06/2016 15:58:32 1880 (0x0758)
Process completed with exit code 0 TSManager 23/06/2016 15:58:32 1188 (0x04A4)
!--------------------------------------------------------------------------------------------! TSManager 23/06/2016 15:58:32 1188 (0x04A4)
Successfully completed the action (Setup Windows and Configuration Manager) with the exit win32 code 0 TSManager 23/06/2016 15:58:32 1188 (0x04A4)
Do not send status message in full media case TSManager 23/06/2016 15:58:32 1188 (0x04A4)
Set a global environment variable _SMSTSLastActionRetCode=0 TSManager 23/06/2016 15:58:32 1188 (0x04A4)
Set a global environment variable _SMSTSLastActionSucceeded=true TSManager 23/06/2016 15:58:32 1188 (0x04A4)
Expand a string: %_SMSTSMDataPath%\Logs TSManager 23/06/2016 15:58:32 1188 (0x04A4)
Clear local default environment TSManager 23/06/2016 15:58:32 1188 (0x04A4)
The action (Setup Windows and Configuration Manager) requested a retry TSManager 23/06/2016 15:58:32 1188 (0x04A4)
Reboot to local harddisk TSManager 23/06/2016 15:58:32 1188 (0x04A4)
_OSDGinaIsConfigured variable set to TRUE TSManager 23/06/2016 15:58:32 1188 (0x04A4)
_SMSTSServiceStartType variable set to  TSManager 23/06/2016 15:58:32 1188 (0x04A4)
Command line for extension .exe is "%1" %* TSManager 23/06/2016 15:58:32 1188 (0x04A4)
Set command line: "bcdedit.exe" TSManager 23/06/2016 15:58:32 1188 (0x04A4)
Executing command line: "bcdedit.exe" TSManager 23/06/2016 15:58:32 1188 (0x04A4)
Process completed with exit code 0 TSManager 23/06/2016 15:58:32 1188 (0x04A4)
Calling RebootSystem() TSManager 23/06/2016 15:58:32 1188 (0x04A4)
OSD type of task sequence. ignore the service window setting TSManager 23/06/2016 15:58:32 1188 (0x04A4)
Updated security on object C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca. TSManager 23/06/2016 15:58:32 1188 (0x04A4)
Updated security on object C:\_SMSTaskSequence. TSManager 23/06/2016 15:58:32 1188 (0x04A4)
Set a global environment variable _SMSTSNextInstructionPointer=9 TSManager 23/06/2016 15:58:32 1188 (0x04A4)
Set a TS execution environment variable _SMSTSNextInstructionPointer=9 TSManager 23/06/2016 15:58:32 1188 (0x04A4)
Set a global environment variable _SMSTSInstructionStackString=8 TSManager 23/06/2016 15:58:32 1188 (0x04A4)
Set a TS execution environment variable _SMSTSInstructionStackString=8 TSManager 23/06/2016 15:58:32 1188 (0x04A4)
Save the current environment block TSManager 23/06/2016 15:58:32 1188 (0x04A4)
Expand a string: %_SMSTSMDataPath%\Logs TSManager 23/06/2016 15:58:32 1188 (0x04A4)

Windows 7 OSD Task Sequence Not Completing after Upgrade to Build 1606

$
0
0

Hello,

I recently upgraded from COnfiguration Manager 2012 R2 to Build 1606 with Hotfix (Full Version 5.00.8412.1205).  I have not made any changes to my Windows 7 OSD Task Sequences is not completing all tasks.  When I log into the machine after it has completed, all tasks have not been run and the ConfigMgr client control panel only shows 6 tabs and the ConfigMgr console shows the machine as having No client installed.

CCMSETUP logs show the following message for all client components (SCEPInstall.exe \ Silverlight.exe \ vcredit_x86.exe etc.):

File 'C:\Windows\ccmsetup\client.msi' with hash '99475FA2A7AC62AD98443E1858FA70B69BE0CFF7D36A4AFEB4B61AB894B593EC' from manifest doesn't match with the file hash 'A5732CE24F2B1545E9FBA458971E0A5504093E0F743CA9E8BD9C047582902878'

The Configuration Manager Client Package being used for the task sequence has Source Folder \\siteservername\SMS_SiteCode\Client and I have created a new client install package specifically for OSD but have the same results.  Is there anything step in the Task Sequence that needs to be updated as a result of the ConfigMgr update?

Thanks

Scott

Viewing all 9126 articles
Browse latest View live