OSD- Erros during deploynment

March 31, 2015, 7:13 am

≫ Next: Network Adapter Failure When Using PXE Boot Image

≪ Previous: SCCM 2012 R2 not accepting Win 8 or 8.1 Drivers

Greetings,

I used 2 images for PXE Boot on this test against HP8300 (W15MTC02LAB03).

(A) # NU64bit - System Refresh - (HL AV Pulse) - HOP0011D

(i.e. used for PXE Boot & Windows 7 Re-clone (TS will hardlink (copy profile))

(B) #64-bit System Refresh - (HL AV)

(i.e. used for PXE Boot & Windows 7 Re-clone (TS Will hardlink (copy profile))

Screenshots in step:-

1. (Both PXEs start with following

2.Choose the PXE to be installed (Here is (A))

3. Supply the PC hostname

4. After machine restart, TS error (0x00000032).

5. F8 to the hard disk and show if disk 0 is available. (Disk 0 is available)

6. Run another PXE option – (Now is (B)). After clicking “Finish”. Machine rebooted and all above 4 and 5 repeated

In a nutshell, both PXEs failed with errors even though they are able to see the hard disk.

SMSTS.Log

https://onedrive.live.com/redir?resid=f3743c55dc76b1ee%211985

↧

Network Adapter Failure When Using PXE Boot Image

March 31, 2015, 11:52 am

≫ Next: ServerManagerCMD.exe fails in Windows Server 2008 SP2 Build and Capture

≪ Previous: OSD- Erros during deploynment

I am using SCCM 2012 R2 and currently am using the x64 default boot image with jno drivers. It has been working fine with all of our machines until I just got a new HP Elitebook Folio 1020 G1 and the boot image isn't working, as I am getting the failed the find network adapter error message. I am guessing that it may in part be due to the fact that the Ethernet port is not built in to this model but is connected using an adapter. At any rate, I attempted to inject the Win7 and Win8 network drivers into the boot image and it's not working still (win 8 drivers won't import). What else am I missing? Thanks in advance!

↧

ServerManagerCMD.exe fails in Windows Server 2008 SP2 Build and Capture

March 25, 2015, 3:11 pm

≫ Next: SCCM 2012 - PXE-E32: TFTP Open timeout

≪ Previous: Network Adapter Failure When Using PXE Boot Image

I am sort of new to the whole Build and Capture process. I just got it working for W2K12R2 and W2K8R2, and now I'm trying to set it up for W2K8 SP2 x64. I am not using MDT as it (seems to) add extra complexity and because we don't use Config Mgr for OSD. I am simply trying to build images.

I am using the W2K8 SP2 x64 RTM image direct from MS (install.wim timestamp is 4/11/2009).

My Task Sequence completes the image deployment and CCM client install. The next step is a Run Command Line that contains "servermanagerCMD.exe -install Telnet-Client". 64-bit redirection is checked.

SMSTS error:

The task sequence execution engine failed executing the action (Install Telnet-Client) in the group (CUSTOMIZATIONS) with the error code 1002
Action output: [ smsswd.exe ]
PackageID = ''
BaseVar = '', ContinueOnError=''
ProgramName = 'servermanagerCMD.exe -install Telnet-Client'
SwdAction = '0001'
Command line for extension .exe is "%1" %*
Set command line: Run command line
Working dir 'not set'
Executing command line: Run command line
Error: Failed to initialize.. The operating system reported error 1002: The window cannot act on the sent message

Servermanager.log:

1568: 2015-03-25 13:00:53.842 [ServerManagerCmd] Running with the following arguments: '-install Telnet-Client'
1568: 2015-03-25 13:00:53.951 [LoadExtensionAssemblies] No extension assemblies registered.
1568: 2015-03-25 13:00:53.983 [OobOptionalComponentInfo] Loading OCs from registry.
1568: 2015-03-25 13:00:54.419 [CBS] LastModified CBS Time (UTC): 03/25/2015 19:57:32
1568: 2015-03-25 13:00:54.419 [Provider] C:\Windows\system32\ServerManager\Cache\CbsUpdateState.bin does not exist.
1568: 2015-03-25 13:00:54.419 [CBS] IsCacheStillGood: False.
1568: 2015-03-25 13:00:54.419 [CBS] CreateSessionAndPackage: begin
1568: 2015-03-25 13:00:54.419 [CBS] Error (Id=0) Function: 'CreateSessionAndPackage()->Session_OpenPackage' failed: 800b0100 (-2146762496)
1568: 2015-03-25 13:00:54.435 [ExceptionHandler] Error (Id=0) An unexpected exception was found:
System.Runtime.InteropServices.COMException (0x800B0100): No signature was present in the subject. (Exception from HRESULT: 0x800B0100)
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at Microsoft.Windows.ServerManager.ComponentInstaller.CreateSessionAndPackage(IntPtr& session, IntPtr& package)
at Microsoft.Windows.ServerManager.ComponentInstaller.InitializeUpdateInfo()
at Microsoft.Windows.ServerManager.ComponentInstaller.Initialize()
at Microsoft.Windows.ServerManager.Common.Provider.Initialize(DocumentCollection documents)
at Microsoft.Windows.ServerManager.ServerManagerModel.InternalRefreshModelResult(Object state)
1568: 2015-03-25 13:00:54.435 [ServerManagerCmd] Error (Id=0) Failed to initialize.

Things I've tried that still resulted in the above errors:

Insert reboot after CCM Client install
Install all updates (200+ install successfully)

Does anyone know how I can get this to work?

Thanks

Joel

↧

SCCM 2012 - PXE-E32: TFTP Open timeout

October 23, 2013, 9:15 pm

≫ Next: Deployment Complete Message

≪ Previous: ServerManagerCMD.exe fails in Windows Server 2008 SP2 Build and Capture

When I trying deploy through PXE in the vmware workstation 10.0, I'm getting the error below

Error: PXE-E32: TFTP Open timeout
TFTP....

The machine got the IP addresss and I'm stop in below error

Client MAc ADDR: 00 0C 29 6C 3F   GUID: xxxxxxxxxxxxxxx
Client IP : 192.168.100.15    MASK: 255.255.255.0   DHCP IP : 192.168.100.254
GATEWAY IP: 192.168.100.1     192.168.100.2
PXE-E32: TFTP Open timeout
TFTP....

Robert

↧

Deployment Complete Message

March 31, 2015, 5:37 am

≫ Next: Two issues with Windows 8/8.1 deployment

≪ Previous: SCCM 2012 - PXE-E32: TFTP Open timeout

When deploying Win 8.1 on a Dell Venue 11 Pro, the Deployment Complete does not display when complete. It seems to be a function of the touch screen device. It does display on non touch screen devices. Any ideas?

↧

Two issues with Windows 8/8.1 deployment

March 31, 2015, 8:55 am

≫ Next: Configure Network Settings. DHCP is used unless otherwise specified

≪ Previous: Deployment Complete Message

Hello,

I'm trying to deploy Windows 8 x64 using SCCM 2012 R2 (CU4) and having two issues once the task sequence is completed. Note that I only experience it with Windows 8 and 8.1 (both x64). The same procedure works fine with Windows 7 (x86 and x64), 2008 R2 and 2012/R2.

I'm using media (Task Sequence > Create Task Sequence Media > Bootable Media) to deploy the OS.

Sysprep and capture of the source OS is done manually because I was having problems with CopyProfile in unattend.xml. Here are my sysprep and capture commands just in case:

sysprep /generalize /oobe /shutdown /unattend:c:\windows\system32\sysprep\unattend.xml

Dism /Capture-Image /ImageFile:g:\iso\sccm\ref\20150331-W8-X64.wim /CaptureDir:D:\ /Name:"Windows 8 x64"

I'm capturing D: drive since C: in the source OS is assigned to System Reserved.

The OSD task sequence is pretty default:

Partitions: System Reserved (Primary, 350 MB, make it the boot partition and do not assign a drive letter) and Windows (Primary, 100% of remaining disk space)

At the Apply Operating System step the Destination is set to "Next available formatted partition".

There is a step to join the domain and finally "Setup Windows and Configuration Manager". I don't deploy any drivers since it's a virtual server.

Problem 1:

Once the task sequence is completed I have a Windows 8 installation, joined the domain, with C: drive with data and copied profile. However, I also see "System Reserved" drive which has a drive letter assigned (E:). Is there something specific to Windows 8 with regards to hiding the "System Reserved" drive? It never happened to me with Windows 7 and 2012/R2.

Problem 2:

The last step "Setup Windows and Configuration Manager" seems to fail, since I see it downloading files, then reboot, then continuation of installation (it finishes too quick), reboot, and I see a Windows 8 login prompt like it's completed successfully.

I couldn't find any errors with regards to "System Reserved" drive issue in the logs, however CCM client installation fails with the error:

<![LOG[Executing command line: "C:\_SMSTaskSequence\OSD\SITE100003\ccmsetup.exe" /useronly /source:C:\_SMSTaskSequence\OSD\SITE100003 /config:MobileClient.TCF /status:728]LOG]!><time="11:01:13.781-120" date="03-31-2015" component="OSDSetupHook" context="" type="1" thread="1948" file="commandline.cpp:827"><![LOG[Process completed with exit code 1]LOG]!><time="17:21:22.305-120" date="03-31-2015" component="OSDSetupHook" context="" type="1" thread="1948" file="commandline.cpp:1123"><![LOG[FALSE, HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\osdgina\installclient.cpp,1151)]LOG]!><time="17:21:22.305-120" date="03-31-2015" component="OSDSetupHook" context="" type="0" thread="1948" file="installclient.cpp:1151"><![LOG[Client installation failed, code 1]LOG]!><time="17:21:22.305-120" date="03-31-2015" component="OSDSetupHook" context="" type="3" thread="1948" file="installclient.cpp:1151">

I uploaded the full log file to http://pastebin.com/r560eena

Any assistance would be greatly appreciated.

Thank you.

↧

Configure Network Settings. DHCP is used unless otherwise specified

March 31, 2015, 8:21 am

≫ Next: Specify WSUS server based on client location boundary

≪ Previous: Two issues with Windows 8/8.1 deployment

Hello

I have created a task sequence that is used in multiple domains.

In one domain DHCP is not configured and we need to use the "Bootable media that uses the Configmr infrastructure".

This bootable media is running fine when DHCP is enabled.

However, when I configure the network settings Manual in WINPE the client can connect to the SCCM server.

After SCCM applies the OS image and reboots the network settings are gone and the Task Sequence crashes.

Is there a simple way to transfer the network settings from WINPE to the OS?

↧

Specify WSUS server based on client location boundary

April 1, 2015, 7:12 am

≫ Next: Trying to create a deployment in SCCM 2012R2 which is then ghosted by our DR Partner

≪ Previous: Configure Network Settings. DHCP is used unless otherwise specified

Hello. We are currently using SCCM 2012 R2 to do OSD at our main site, and I'm in the process of getting OSD working at our eight remote locations. Unfortunately, we haven't set up SUP yet (it's coming soon...I hope). So, in the interim, we specify our WSUS server in the task sequence during imaging; or, inject updates into the WIM using a script if the latest updates "break" OSD. However, this poses a bit of a problem for our remote locations.

Currently, all our remote locations have their own OU in AD, and boundaries are set based on their OU. We also have IP address range boundaries at our remote locations so that unknown machines will get assigned to the correct boundary during imaging. Additionally, we have a DP on-site at every remote location. Testing with our current task sequence shows that content is being pulled from the correct DP during imaging at the remote location (not across the WAN, which is great). But, I'm not sure how I would go about adding a task sequence step that would specify each remote location's on-site WSUS server.

I'd rather not create eight more task sequences just to specify the WSUS server for each location, since managing one task sequence would be ideal. And, the fact that we will have SUP up soon, means we won't have to deal with this for long. So, is there a way to check what boundary the machine is in during imaging, and make a task sequence step only run if it's in that boundary? I really appreciate and help and/or advice anyone can give me. Thanks.

↧

Trying to create a deployment in SCCM 2012R2 which is then ghosted by our DR Partner

April 1, 2015, 7:14 am

≫ Next: Client with Patch fails to install - Build and Capture

≪ Previous: Specify WSUS server based on client location boundary

We are using SCCM 2012R2 to create an image. We need to sysprep the image and then send it off to our DR partner who will ghost the image for use at our DR Site.

We managed to successfully create an image previously but when it got sent to our DR Provider something went wrong and the image doesn't take. It says....

Windows setup could not configure Windows to run on this computers hardware.

Then Windows could not complete the installation. To install windows on this computer please restart the installation.

We have tested our DR image back at our offices and it installs the OS on the PC no problem. It does have other issues with application installation but I would have expected the DR Machines to at least install Windows 7.

Has anyone else experienced issues with images being created in SCCM and then applied using ghost?

↧

Client with Patch fails to install - Build and Capture

April 1, 2015, 9:17 am

≫ Next: OS Deployment status? using SCCM 2012 R2

≪ Previous: Trying to create a deployment in SCCM 2012R2 which is then ghosted by our DR Partner

Hi,

We recently hit an issue where our Build and Capture task sequence, previously fully working, was deleted. As such I've had to rebuild it from documentation. So far so good. However when I now test it out, the sequence fails during the installation of the client. It appears to be due to access to the patch, however I can't work out why. The installation flags are:

/mp:sccmpri01.domain.com CCMLOGMAXHISTORY=4 PATCH=\\SCCMPRI01.domain.com\HotFixes\KB2938441\Client\i386\configmgr2012ac-r2-kb2938441-i386.msp

And the share is set for the network access account to have read/write/execute, and everyone to have read access. As it's a build and capture the machine is in a workgroup not the domain.

The error I'm getting is most detailed in the ccmsetup folder under the client.msi.log

MSI (s) (EC:4C) [15:51:37:441]: Unable to create a temp copy of patch '\\SCCMPRI01.DOMAIN.COM\HOTFIXES\KB2938441\CLIENT\I386\CONFIGMGR2012AC-R2-KB2938441-I386.MSP'.
MSI (s) (EC:4C) [15:51:37:441]: Note: 1: 1708
MSI (s) (EC:4C) [15:51:37:441]: Product: Configuration Manager Client -- Installation failed.
MSI (s) (EC:4C) [15:51:37:441]: Windows Installer installed the product. Product Name: Configuration Manager Client. Product Version: 5.00.7958.1000. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 1635.

I'm a little lost as to what to try next. If I install without the patch it's alright but then fails as soon as it hits the next step in the sequence.

Any help would be great!

↧

OS Deployment status? using SCCM 2012 R2

April 1, 2015, 11:56 am

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

≪ Previous: Client with Patch fails to install - Build and Capture

I've searched around can't seem to figure out if there is a status window for OS deployments. Specifically, I've got both unicast and multicast working now. If I go under "Monitoring > Deployments >" and check the status it takes it a few seconds and then tells me under "In Progress" Assets 1. So this tells me I guess that there is one computer currently running this deployment. I really was hoping for something better like the old Ghost interface or even WDS with it's multicast display. Is there anything that I'm missing or is figuring out what you currently have going on rather difficult to make sense of? I would like to see how many are unicast and multicast assuming I had many computers imaging at the same time. I would like to know what IP address they are using and what speeds they are sending data at.

Bonus question on Multicast if you choose the "Custom" speed how do you edit this? I found something for SCCM 2007 for editing the registry but the same entry didn't exist for me in 2012 R2.

↧

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

June 20, 2014, 9:28 am

≫ Next: Cannot connect to Out of Band Management Console (SCCM2012 R2)

≪ Previous: OS Deployment status? using SCCM 2012 R2

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?

↧

Cannot connect to Out of Band Management Console (SCCM2012 R2)

April 1, 2015, 12:04 pm

≫ Next: Error: PXE-E53: No boot filename received

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

Any help much appreciated

I am trying to figure out AMT.

Computers has been provisioned and able to use Power Control with Manage Out of Band.

But using Out of Band Management console its keeps connecting and disconnect after 30 seconds

Here is what I gets

System: Connecting

IDE-Redirect: Inactive

Serial connection : Inactive.

Tools> Open Serial- Connection over LAN is greyed out

I have verify settings in BIOS IDER and Serial connection is Enabled.

I tried review OOBConsole.log on site server and find this error.

GetAMTPowerState fail with result:0x80070005

Searched on google but couldn't find an answer to problem,

Here are the logs if someone could please direct me to right direction.

[1, PID:14236][04/01/2015 11:38:30] :OOBConsole: Trace started
[1, PID:14236][04/01/2015 11:38:30] :Create AmtClientManager.
[12, PID:14236][04/01/2015 11:38:30] :Success report status message Type:Audit, ID:0x000000004000765C, User:domain\rj, Machine:domain-SCCM.
[13, PID:14236][04/01/2015 11:38:32] :IMR_Init with C:\Users\rj\AppData\Local\Microsoft\ConfigMgr\AdminUI\OOBConsole\imrsdk.ini success with Microsoft.ConfigurationManagement.AdminConsole.OobConsole.Utilities.IMRVersion.
[1, PID:14236][04/01/2015 11:38:32] :AmtDevice Open.
[1, PID:14236][04/01/2015 11:38:32] :WSMan Open Session success.
[1, PID:14236][04/01/2015 11:38:32] :IMR_AddClient with ip=tech-210.domain.net and useTLS = True success with 0.
[1, PID:14236][04/01/2015 11:38:32] :status message Type:Audit, ID:0x0000000040007665, User:domain\rj, Machine:domain-SCCM, Target:tech-210.domain.net add to queue, waiting for report.
[13, PID:14236][04/01/2015 11:38:32] :Executing static method SMS_StatusMessage.RaiseRawStatusMsg()
[13, PID:14236][04/01/2015 11:38:32] :Success report status message Type:Audit, ID:0x0000000040007665, User:domain\rj, Machine:site-server.
[16, PID:14236][04/01/2015 11:38:33] :GetAMTPowerState fail with result:0x80070005
[12, PID:14236][04/01/2015 11:38:43] :GetAMTPowerState fail with result:0x80070005
[16, PID:14236][04/01/2015 11:38:52] :GetAMTPowerState fail with result:0x80070005
[1, PID:14236][04/01/2015 11:38:52] :AmtDevice Close.
[13, PID:14236][04/01/2015 11:38:52] :Cleanup AmtSettings...
[13, PID:14236][04/01/2015 11:38:52] :All BackgroundWorkers stoped.
[13, PID:14236][04/01/2015 11:38:52] :CloseIderConnection.
[13, PID:14236][04/01/2015 11:38:52] :PrepareNormalBootOption.
[13, PID:14236][04/01/2015 11:38:53] :OOBPrepareNormalBootOption: BypassPassword:False, LockKeyboard:False, EnableSOL:False. fail with result:0x80070005
[13, PID:14236][04/01/2015 11:38:53] :RemoveClient and close wsman session...
[13, PID:14236][04/01/2015 11:38:53] :IMR_RemoveClient with clientID=0 success.
[13, PID:14236][04/01/2015 11:38:53] :WSMan Close Session success.
[1, PID:14236][04/01/2015 11:38:53] :Cleanup AmtSettings completed.
[1, PID:14236][04/01/2015 11:38:53] :Microsoft.ConfigurationManagement.ManagementProvider.SmsException\r\nSystem error.\r\n at Microsoft.ConfigurationManagement.AdminConsole.OobConsole.Utilities.AmtWSMan.CheckResult(Int32 result)
at Microsoft.ConfigurationManagement.AdminConsole.OobConsole.Utilities.AmtWSMan.PrepareNormalBootOption(Boolean enableBypassPassword, Boolean enableLockKeyboard, Boolean enableSOL)
at Microsoft.ConfigurationManagement.AdminConsole.OobConsole.Utilities.AmtDevice.CleanUpAmtSettings(Object sender, DoWorkEventArgs e)
at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)\r\nNo details are available for this error.\r\n
[1, PID:14236][04/01/2015 11:38:59] :Connect to AMT, FQDN:tech-210.domain.net, user:domain\rj.
[1, PID:14236][04/01/2015 11:39:00] :AmtDevice Open.
[1, PID:14236][04/01/2015 11:39:00] :WSMan Open Session success.
[1, PID:14236][04/01/2015 11:39:00] :IMR_AddClient with ip=tech-210.domain.net and useTLS = True success with 1.
[1, PID:14236][04/01/2015 11:39:00] :status message Type:Audit, ID:0x0000000040007665, User:domain\rj, Machine:siteserver-SCCM, Target:tech-210.domain.net add to queue, waiting for report.
[11, PID:14236][04/01/2015 11:39:00] :Executing static method SMS_StatusMessage.RaiseRawStatusMsg()
[11, PID:14236][04/01/2015 11:39:00] :Success report status message Type:Audit, ID:0x0000000040007665, User:domain\rj, Machine:domain-SCCM.
[12, PID:14236][04/01/2015 11:39:01] :GetAMTPowerState fail with result:0x80070005
[13, PID:14236][04/01/2015 11:39:10] :GetAMTPowerState fail with result:0x80070005
[12, PID:14236][04/01/2015 11:39:20] :GetAMTPowerState fail with result:0x80070005
[1, PID:14236][04/01/2015 11:39:20] :AmtDevice Close.
[16, PID:14236][04/01/2015 11:39:20] :Cleanup AmtSettings...
[16, PID:14236][04/01/2015 11:39:21] :All BackgroundWorkers stoped.
[16, PID:14236][04/01/2015 11:39:21] :CloseIderConnection.
[16, PID:14236][04/01/2015 11:39:21] :PrepareNormalBootOption.
[16, PID:14236][04/01/2015 11:39:21] :OOBPrepareNormalBootOption: BypassPassword:False, LockKeyboard:False, EnableSOL:False. fail with result:0x80070005
[16, PID:14236][04/01/2015 11:39:21] :RemoveClient and close wsman session...
[16, PID:14236][04/01/2015 11:39:21] :IMR_RemoveClient with clientID=1 success.
[16, PID:14236][04/01/2015 11:39:21] :WSMan Close Session success.
[1, PID:14236][04/01/2015 11:39:21] :Cleanup AmtSettings completed.
[1, PID:14236][04/01/2015 11:39:21] :Microsoft.ConfigurationManagement.ManagementProvider.SmsException\r\nSystem error.\r\n at Microsoft.ConfigurationManagement.AdminConsole.OobConsole.Utilities.AmtWSMan.CheckResult(Int32 result)
at Microsoft.ConfigurationManagement.AdminConsole.OobConsole.Utilities.AmtWSMan.PrepareNormalBootOption(Boolean enableBypassPassword, Boolean enableLockKeyboard, Boolean enableSOL)
at Microsoft.ConfigurationManagement.AdminConsole.OobConsole.Utilities.AmtDevice.CleanUpAmtSettings(Object sender, DoWorkEventArgs e)
at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)\r\nNo details are available for this error.\r\n
[1, PID:14236][04/01/2015 11:39:25] :IMR_RemoveAllClients success.
[1, PID:14236][04/01/2015 11:39:25] :OOBConsole exit

RJ09

↧

Error: PXE-E53: No boot filename received

March 27, 2015, 6:06 am

≫ Next: PXE Booting pc for Image deployment

≪ Previous: Cannot connect to Out of Band Management Console (SCCM2012 R2)

Hi,

Keep getting the PXE-E53 error when I try to PXE boot.

Infrastructure

Primary server (SCCM 2012 R2) (9.9.9.9)

DP1: Not PXE-enabled (1.1.1.1)

DP2: Not PXE-enabled (2.2.2.2)

DP3: PXE-enabled (3.3.3.3)

DHCP server: Options 60, 66 & 67 not set (4.4.4.4)

Network setup

interface vlan 602

ip address [SUBNET OF THE SERVERS]

ip helper-address 4.4.4.4

ip helper-address 3.3.3.3

end

What did I try

Case 1

ip helper-address 9.9.9.9 --> PXE-E53

Case 2

DHCP scope options: 66 & 67 --> PXE-E53

Case 3

ip helper-address 3.3.3.3 --> PXE-E53

SMSPXE.log

<![LOG[Begin validation of Certificate [Thumbprint 49C3D9CE1B84207A2E18FC0ABC70E92C1D183514] issued to 'c116eb70-eb43-4d21-b4e1-2c698f77382a']LOG]!><time="12:24:36.068-60" date="03-17-2015" component="SMSPXE" context=""
 type="1" thread="3144" file="ccmcert.cpp:1662"><![LOG[Completed validation of Certificate [Thumbprint 49C3D9CE1B84207A2E18FC0ABC70E92C1D183514] issued to 'c116eb70-eb43-4d21-b4e1-2c698f77382a']LOG]!><time="12:24:36.068-60" date="03-17-2015" component="SMSPXE" context=""
 type="1" thread="3144" file="ccmcert.cpp:1803"><![LOG[PXEClientKey certificate valid.]LOG]!><time="12:24:36.068-60" date="03-17-2015" component="SMSPXE" context="" type="1" thread="3144" file="certhdl.cpp:174"><![LOG[Purging old images: 0]LOG]!><time="12:24:42.370-60" date="03-17-2015" component="SMSPXE" context="" type="1" thread="3144" file="bootimagemgr.cpp:1647"><![LOG[Purging old images: 0]LOG]!><time="12:34:42.397-60" date="03-17-2015" component="SMSPXE" context="" type="1" thread="4872" file="bootimagemgr.cpp:1647"><![LOG[Purging old images: 0]LOG]!><time="12:44:42.423-60" date="03-17-2015" component="SMSPXE" context="" type="1" thread="1624" file="bootimagemgr.cpp:1647"><![LOG[Purging old images: 0]LOG]!><time="12:54:42.450-60" date="03-17-2015" component="SMSPXE" context="" type="1" thread="3000" file="bootimagemgr.cpp:1647"><![LOG[Purging old images: 0]LOG]!><time="13:04:42.476-60" date="03-17-2015" component="SMSPXE" context="" type="1" thread="3992" file="bootimagemgr.cpp:1647"><![LOG[Purging old images: 0]LOG]!><time="13:14:42.503-60" date="03-17-2015" component="SMSPXE" context="" type="1" thread="3132" file="bootimagemgr.cpp:1647"><![LOG[Begin validation of Certificate [Thumbprint 49C3D9CE1B84207A2E18FC0ABC70E92C1D183514] issued to 'c116eb70-eb43-4d21-b4e1-2c698f77382a']LOG]!><time="13:24:36.180-60" date="03-17-2015" component="SMSPXE" context=""
 type="1" thread="3708" file="ccmcert.cpp:1662"><![LOG[Completed validation of Certificate [Thumbprint 49C3D9CE1B84207A2E18FC0ABC70E92C1D183514] issued to 'c116eb70-eb43-4d21-b4e1-2c698f77382a']LOG]!><time="13:24:36.180-60" date="03-17-2015" component="SMSPXE" context=""
 type="1" thread="3708" file="ccmcert.cpp:1803"><![LOG[PXEClientKey certificate valid.]LOG]!><time="13:24:36.180-60" date="03-17-2015" component="SMSPXE" context="" type="1" thread="3708" file="certhdl.cpp:174"><![LOG[Purging old images: 0]LOG]!><time="13:24:42.529-60" date="03-17-2015" component="SMSPXE" context="" type="1" thread="3708" file="bootimagemgr.cpp:1647"><![LOG[Purging old images: 0]LOG]!><time="13:34:42.555-60" date="03-17-2015" component="SMSPXE" context="" type="1" thread="3496" file="bootimagemgr.cpp:1647"><![LOG[Purging old images: 0]LOG]!><time="13:44:42.582-60" date="03-17-2015" component="SMSPXE" context="" type="1" thread="5116" file="bootimagemgr.cpp:1647"><![LOG[Purging old images: 0]LOG]!><time="13:54:42.608-60" date="03-17-2015" component="SMSPXE" context="" type="1" thread="1028" file="bootimagemgr.cpp:1647"><![LOG[Purging old images: 0]LOG]!><time="14:04:42.635-60" date="03-17-2015" component="SMSPXE" context="" type="1" thread="2396" file="bootimagemgr.cpp:1647"><![LOG[Purging old images: 0]LOG]!><time="14:14:42.661-60" date="03-17-2015" component="SMSPXE" context="" type="1" thread="3608" file="bootimagemgr.cpp:1647"><![LOG[Begin validation of Certificate [Thumbprint 49C3D9CE1B84207A2E18FC0ABC70E92C1D183514] issued to 'c116eb70-eb43-4d21-b4e1-2c698f77382a']LOG]!><time="14:24:36.291-60" date="03-17-2015" component="SMSPXE" context=""
 type="1" thread="4780" file="ccmcert.cpp:1662"><![LOG[Completed validation of Certificate [Thumbprint 49C3D9CE1B84207A2E18FC0ABC70E92C1D183514] issued to 'c116eb70-eb43-4d21-b4e1-2c698f77382a']LOG]!><time="14:24:36.291-60" date="03-17-2015" component="SMSPXE" context=""
 type="1" thread="4780" file="ccmcert.cpp:1803"><![LOG[PXEClientKey certificate valid.]LOG]!><time="14:24:36.291-60" date="03-17-2015" component="SMSPXE" context="" type="1" thread="4780" file="certhdl.cpp:174"><![LOG[Purging old images: 0]LOG]!><time="14:24:42.688-60" date="03-17-2015" component="SMSPXE" context="" type="1" thread="4780" file="bootimagemgr.cpp:1647"><![LOG[Cannot read the registry value of MACIgnoreListFile (00000000)]LOG]!><time="14:24:52.438-60" date="03-17-2015" component="SMSPXE" context="" type="1" thread="4780" file="provsettings.cpp:353"><![LOG[MAC Ignore List Filename in registry is empty]LOG]!><time="14:24:52.438-60" date="03-17-2015" component="SMSPXE" context="" type="1" thread="4780" file="provsettings.cpp:468"><![LOG[Cannot read the registry value of MACIgnoreListFile (00000000)]LOG]!><time="14:26:52.484-60" date="03-17-2015" component="SMSPXE" context="" type="1" thread="1828" file="provsettings.cpp:353"><![LOG[MAC Ignore List Filename in registry is empty]LOG]!><time="14:26:52.484-60" date="03-17-2015" component="SMSPXE" context="" type="1" thread="1828" file="provsettings.cpp:468"><![LOG[================= PXE Provider shutdown. =====================]LOG]!><time="14:29:08.926-60" date="03-17-2015" component="SMSPXE" context="" type="1" thread="2636" file="smspxe.cpp:223">

This is the last of the PXE log, it was last changed after case 1. Nothing happened to it after case 2 and case 3.

Anyone got some ideas what might cause this error?

Sander

↧

PXE Booting pc for Image deployment

April 1, 2015, 7:15 am

≫ Next: Standalone USB media not installing applications

≪ Previous: Error: PXE-E53: No boot filename received

Hi Folks,

our sccm 2012 system was working fine then all of a sudden has stopped working, when we try to image a pc using F12 we get this error message, can anyone help me out resolving this issue.

I've already uninstalled/installed pxe/wds but still getting this error, I've also create our boot images fresh but still the same.

↧

Standalone USB media not installing applications

August 28, 2013, 4:38 am

≫ Next: Setting IE Proxy from MDT2012 Not working

≪ Previous: PXE Booting pc for Image deployment

Hello,

When staging a machine with standalone media (usb) applications are not installed, when staging via PXE with the same Task Sequence all applications are installed during the staging.

I checked the setting "allow this application to be installed from the install application task sequence action..."

Errors I find in smsts.log are:

<![LOG[spCIStore->StoreCIFromDisk(pInfo), HRESULT=80004005 (e:\nts_sccm_release\sms\dcm\sdk\cisdkclass.cpp,2237)]LOG]!><time="13:24:24.675-120" date="08-28-2013" component="InstallApplication" context="" type="0" thread="2644" file="cisdkclass.cpp:2237">
<![LOG[StoreCIFromDisk: Unable to store CI: 0x80004005]LOG]!><time="13:24:24.675-120" date="08-28-2013" component="InstallApplication" context="" type="3" thread="2644" file="cisdkclass.cpp:2243">
<![LOG[spAppSDK->StoreCIFromDisk (&PathInfo), HRESULT=80004005 (e:\nts_sccm_release\sms\framework\tscore\utils.cpp,912)]LOG]!><time="13:24:24.675-120" date="08-28-2013" component="InstallApplication" context="" type="0" thread="2644" file="utils.cpp:912">
<![LOG[StoreCIFromDisk failed]LOG]!><time="13:24:24.675-120" date="08-28-2013" component="InstallApplication" context="" type="3" thread="2644" file="utils.cpp:912">
<![LOG[StoreAppDocuments failed; 0x80004005]LOG]!><time="13:24:24.691-120" date="08-28-2013" component="InstallApplication" context="" type="3" thread="2644" file="utils.cpp:948">
<![LOG[TS::Utility::StoreAppDocuments (sAppDocs.c_str()), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\installapplication\installapplication.cpp,880)]LOG]!><time="13:24:24.691-120" date="08-28-2013" component="InstallApplication" context="" type="0" thread="2644" file="installapplication.cpp:880">
<![LOG[StoreAppDocuments failed]LOG]!><time="13:24:24.691-120" date="08-28-2013" component="InstallApplication" context="" type="3" thread="2644" file="installapplication.cpp:880">
<![LOG[Step 3 out of 5 complete]LOG]!><time="13:24:24.691-120" date="08-28-2013" component="InstallApplication" context="" type="0" thread="2644" file="daprogress.cpp:226">
<![LOG[Install application action failed: 'Adobe Reader XI (11.0.0.3 ) - Français'. Error Code 0x80004005]LOG]!><time="13:24:24.691-120" date="08-28-2013" component="InstallApplication" context="" type="3" thread="2644" file="installapplication.cpp:798">
<![LOG[Sending error status message]LOG]!><time="13:24:24.691-120" date="08-28-2013" component="InstallApplication" context="" type="1" thread="2644" file="installapplication.cpp:802">
<![LOG[sClientGUID.empty()==false, HRESULT=80004005 (e:\nts_sccm_release\sms\framework\tscore\utils.cpp,5699)]LOG]!><time="13:24:24.691-120" date="08-28-2013" component="InstallApplication" context="" type="0" thread="2644" file="utils.cpp:5699">
<![LOG[The client GUID must be set in an environment variable]LOG]!><time="13:24:24.691-120" date="08-28-2013" component="InstallApplication" context="" type="3" thread="2644" file="utils.cpp:5699">
<![LOG[Non fatal error 0x80004005 in sending task sequence execution status message to MP]LOG]!><time="13:24:24.691-120" date="08-28-2013" component="InstallApplication" context="" type="2" thread="2644" file="utils.cpp:5811">

Any idea ?

Thanks

↧

Setting IE Proxy from MDT2012 Not working

April 2, 2015, 2:53 am

≫ Next: PXE DHCP ICMP:Destination Unreachable Message

≪ Previous: Standalone USB media not installing applications

Im trying to predefine IE proxy setting during Win7 deployment from WDS2012

I tried following this guide:

http://blogs.technet.com/b/deploymentguys/archive/2010/11/30/using-the-mdt-windows-update-tasks-in-image-engineering.aspx

using command line: cscript CFG-ProxySetting.wsf /Proxy:<Proxyname.company.com or IP Address>:<Port> /Exceptions:local

But it fails to execute giving an error code 0000001 if i remember right.

i also tried cscript.exe "%SCRIPTROOT%\CFG-ProxySetting.wsf" /Proxy:proxy.address.local:8080 /Exceptions:local

Anyone have any suggestions ?

(PS. I dont want to set proxy with Group Policy because users need to be able to change it if necessary)

↧

PXE DHCP ICMP:Destination Unreachable Message

April 2, 2015, 12:50 am

≫ Next: How to Enable BitLocker without TPM?

≪ Previous: Setting IE Proxy from MDT2012 Not working

I have a question regarding PXE and DHCP. Is it possible to ping a machine, which is in PXE boot with a DHCP address and able to access my SCCM server? Unfortunately i cannot ping the machine and in network traffic i see:

12913 17:00:17 01.04.2015 759.8323064 SRV-SCCMDP-501 <00> 172.16.10.66 ICMP ICMP:Destination Unreachable Message, Port Unreachable, 172.16.8.38:69 {IPv4:228}

No firewall between the machines and is the same subnet.

Thank you in Advance

↧

How to Enable BitLocker without TPM?

March 23, 2015, 5:50 pm

≫ Next: BCD Store

≪ Previous: PXE DHCP ICMP:Destination Unreachable Message

Hi all

We're running SCCM 2012 R2 CU4. All has gone well with our global migration to Windows 7 SP1 Enterprise with MBAM using our SCCM task sequence.

2 offices remain: Beijing and Shanghai. However, Chinese regulations do not permit the use of TPM chips, in fact, all laptops we buy locally have the TPM chip disabled permanently at manufacturing. So we have been trying to create a task sequence that enables BitLocker using a Startup (USB) key instead of the TPM but we're getting a task sequence error 0x80004005 during the "Enable BitLocker" step. This is proving to be more difficult than anticipated.

Can anyone offer an assistance or a link to a guide that walks us through the process for enabling BitLocker using a Startup key in the absence of a TPM chip please?

Best regards
Scott

↧

BCD Store

April 2, 2015, 6:33 am

≫ Next: SMS_INVENTORY_DATA_LOADER failed to process HYDYGY8R.MIF

≪ Previous: How to Enable BitLocker without TPM?

Just trying to get some clarification on the pxe boot process and I found this article http://henkhoogendoorn.blogspot.com/2012/02/pxe-boot-files-in-remoteinstall-folder.html which is detailed and provides a good explanation. The one thing I can't find is the BCD Store in the RemoteInstall folder. I do have the other files and even a Boot folder but no default.bcd files. Should they be also be distributed with the other folders?

↧