Windows 7 64bit task sequence with HP 6570b.

SCCM 2012 Sp1

They hang just after the sccm client installation.
I verified we have the AD group ConfigMgr Remote Control Users

Our 32bit image seems to work fine.

From the smstslog

Waiting for CcmExec service to be fully operational TSManager 1/17/2013 3:36:50 PM 2988 (0x0BAC)
Succeeded loading resource DLL 'C:\WINDOWS\CCM\1033\TSRES.DLL' TSManager 1/17/2013 3:36:51 PM 2988 (0x0BAC)
Failed to create an instance of COM progress UI object. Error code 0x80070015 TSManager 1/17/2013 3:36:51 PM 2988 (0x0BAC)

Hello,

I have an issue with one of my Task Sequence OSD loads. I am using SCCM 2012 with a CAS trying to load a standalone drive. 

The issue that i am having is it fails at the "Formatting C:\"

The logs are posted below. 

I have tried to follow this: http://cmsource.net/2014/01/21/another-80070057-fail-apply-operating-system-image-step-in-sccm-2012/  But to no avail. I have tried using Diskpart, running clean cmd, and rebooting. That doesn't seem to help. 

I've tried loading the drivers into my boot image but for this one particular laptop model (Latitude E6420), I still cannot get an IP address after it reboots after the "Setup is applying system settings" screen. 

So PXE boot works fine, it gets an IP, downloads and then applies the WIM file. 
Then it reboots and Windows configures, reboots and when it's at the task sequence when Config Mgr client is downloading/installing, I hit F8 and ipconfig shows no IP and going forward there's no IP, so all the next task sequences where I need network access fails. 

I've tried importing drivers into SCCM that were x86 and then I tried x64 (deleting and re-adding drivers between attempts) by importing and then telling it to update DP and then update the boot image. 

Then I tried the ConfigMgr Driver Injector tool to export the driver and then I imported that manually, but still, it doesn't seem to work, either! :( 

Hi all

We are working on a method to deploy WOL in our environment and giving our Helpdesk Technicians only the rights they really need .We have a Collection that has our OSD task sequence deployed to. All our helpdesk employees needs to do is to run a script to add the computer to this collection. Unfortunately we could not restrict our helpdesk with RBA inside Configuration Manager see my previous post https://social.technet.microsoft.com/Forums/en-US/3a37aa22-3bc5-4ccf-b25a-dfb9ca19b00a/rbac-importing-computers-with-collection-limiting-problem?forum=configmanagerosd

We managed that with a script , the script add the computer to the right OSD collection and the task sequence does his job.

But we now have another issue that issue is wake on lan .

We enabled all the prerequisites for Wake On Lan to work

• Hardware Inventory must be running, and information must be uploaded in the SCCM database
• Wake on LAN option to Power On in BIOS is enabled (workstation)
• Advanced tab of Ethernet adapter settings (workstation) Wake On magic packet are enabled
• Network settings of Ethernet adapter “allow this device to wake up computer” are enabled
• Enable send wake-up packages on OSD deployments (task sequences)
• IP Helpers are configured on the network site
• WOL is configured on the Primary site Server  

The current schedule for the OSD Task Sequence deployment is a required "As Soon As Possible" schedule. From my testing, I can drop machines into this collection, but the WOL won't kick off unless I modify the setting Send wake-up packets off and afterwards again on, on the deployment settings tab.

Is this normal behavior , why does WOL not work on computers that are added to the deployment collection , why don’t they get a trigger

How to deal with this do we need to create a new deployment for every new computer that is added to the OSD collection or do we need to change every time we add a computer to the OSD collection modify the setting Send wake-up packets on or off on the deployment settings tab. Or is there another solution for this problem we have.

I hope for some help

Thx in advance

Regards

Johan

I am having an odd problem with my SCCM 2012 OSD tasks. It appears that not all applications are showing up in the "install applications" task. For instance, I have separate applications for 32-bit and 64-bit Java. The 64-bit application shows up in the list of applications  you can choose to install, but the 32-bit version doesn't. I have tried both with and both without the "allow this application to be installed from the install application task sequence action without being deployed" box selected. (It also looks like that box does nothing, I have it unchecked for Acrobat Pro and it still shows up in the list).

Both deployments are working outside of the OSD stuff, but I'd like to be able to have them install as part of an OS deployment. Any ideas?

Does someone knows if it is possible to re-image a workgroup computer but immediately approve that computer in SCCM during the task sequence.

By that updates will be deployed using the sequencing....if not approved the updates are not received.

We're deploying a previously caputered Win 7 64 bit image via TaskSequence. After the OS deploy some add'l software should be installed via the TS. Randomly one task running a vbscript via a batch file hangs.

When looking at the processes the process is gone (neither cmd.exe nor cscript.exe are running). SMSTS.log shows "Waiting for job status notification" forever. Any idea what SCCM is waiting for?

<![LOG[Policy evaluation initiated]LOG]!><time="10:50:25.787-120" date="08-02-2012" component="InstallSoftware" context="" type="1" thread="2220" file="utils.cpp:3387">
<![LOG[Waiting for policy to be compiled in 'root\ccm\policy\machine' namespace ]LOG]!><time="10:50:25.787-120" date="08-02-2012" component="InstallSoftware" context="" type="1" thread="2220" file="installsoftware.cpp:370">
<![LOG[Query path = 'CCM_SoftwareDistribution.ADV_AdvertisementID="XXX20014",PRG_ProgramID="Install",PKG_PackageID="XXX00030"']LOG]!><time="10:50:25.787-120" date="08-02-2012" component="InstallSoftware" context="" type="1" thread="2220" file="installsoftware.cpp:401">
<![LOG[Verified policy is compiled in 'root\ccm\policy\machine' namespace]LOG]!><time="10:50:25.787-120" date="08-02-2012" component="InstallSoftware" context="" type="1" thread="2220" file="installsoftware.cpp:426">
<![LOG[content location count = 1]LOG]!><time="10:50:25.803-120" date="08-02-2012" component="InstallSoftware" context="" type="1" thread="2220" file="installsoftware.cpp:231">
<![LOG[Invoking Execution Manager to install software ]LOG]!><time="10:50:25.803-120" date="08-02-2012" component="InstallSoftware" context="" type="0" thread="2220" file="installsoftware.cpp:233">
<![LOG[Installing software for PackageID='XXX00030' ProgramID='Install' AdvertID='XXX20014' has started, jobID='{DD86D0B1-8763-4CFF-90AA-620EA0EABD07}']LOG]!><time="10:50:25.849-120" date="08-02-2012" component="InstallSoftware" context="" type="1" thread="2220" file="installsoftware.cpp:255">
<![LOG[Setting TSEnv variable 'SMSTSInstallSoftwareJobID_XXX0030_XXX20014_Install'='{DD86D0B1-8763-4CFF-90AA-620EA0EABD07}']LOG]!><time="10:50:25.849-120" date="08-02-2012" component="InstallSoftware" context="" type="1" thread="2220" file="installsoftware.cpp:52">
<![LOG[Waiting for installation job to complete..]LOG]!><time="10:50:25.849-120" date="08-02-2012" component="InstallSoftware" context="" type="1" thread="2220" file="installsoftware.cpp:857">
<![LOG[Waiting for job status notification...]LOG]!><time="10:50:55.810-120" date="08-02-2012" component="InstallSoftware" context="" type="1" thread="2220" file="installsoftware.cpp:876">
<![LOG[Waiting for job status notification...]LOG]!><time="10:51:25.787-120" date="08-02-2012" component="InstallSoftware" context="" type="1" thread="2220" file="installsoftware.cpp:876">

Hi @ all,

I have to deploy a Task Sequence with a X86 WinPe.

I try to use a Task Sequence Boot Medium with a x86 to start the client, it fails without any error like no valid boot medium is found. This means, that no action will be startet like loading files etc.

When I try to create a Task Sequence Medium with a x64 WinPe, everything is ok.

I have testet this on 2 different Laptops, same error.

Any ideas?

Thanks in advance.

Tom

I would like to know what the difference between a "local" and a "remote" distribution point is. I have looked through many blogs and articles referring to "local distribution point" or "remote distribution point", but noone explains actually what the difference is and how I can see in the SCCM console if one of my DPs is local or remote.

How do I install a local DP?
How do I install a Remote DP?

I Guess this is basically what I want to know.

Someone told me the "Schedule" and "Rate limits" tab in the DP Properties is one way to see it?

Freddy

I'm running SCCM 2012 R2 on Windows Server 2008 R2. My SMP is co-located with my MP. I'm attempting to do an offline USMT capture, but keep getting the same error. My smsts.log file indicates that the first connection attempt to the SMP is using the computer account which is obviously going to fail, but I have the option to use the NAA enabled in my TS. After receiving the error message "Unsuccessful in connecting to [SMP Share]. Invalid username or password.", it goes on to say "Trying to connect to [SMP Share] using NAA." as it should, but then a few lines down I get "Failed to connect to [SMP Share] (1219)."

I have reset the password on my NAA, reconfirmed the account in the Accounts node in the console (and successfully connected to the share with the test connection function), removed my SMP and readded it. I'm at a loss. Thanks for the help!

When trying to import the drivers from the Windows 8.1 x64 Dell E6330 SCCM CAB to our SCCM 2012 R2 U1 server, we receive the error "The selected driver is not applicable to any supported platforms" on a number of drivers.

Specifying the same source directory to the test Windows 8.1 Ent x64 computer via the install driver wizard in Device manager finds and installs the missing drivers successfully (Bluetooth 4.0 Module and STMicroelectronics 3-axis Digital Accelerometer). 

The manufacturer section of those drivers looks like this:

bcbturms-win8x64-brcm.inf

[Manufacturer]
%MfgName%=Broadcom, NTamd64.6.3, NTamd64

st_accel.inf

[Manufacturer]
%STM%=ST,NTAMD64

Any idea how I can successfully import these drivers?

Hi Team,

I am facing a very strange issue while testing Standalone media with VM and Hardware. 

I have OS stand alone media created that works fine on VM but same media fails while testing on hardware (tried couple of different hardware and models) . Every time it fails at 'applying OS settings' where it has to use unattend.xml. 

Error:

'THE unexpected computer reboots so, I was an unexpected error. The windows instalition pued not continue. For windows installer click OK to Reboot'

I can't even get to the logs at this stage since F8 is not working at this stage of OS deployment. 

Any pointers will be appreciated. Thanks. 

Regards.

Hi All,

I'm having issues building a Dell XPS13 9333 using OSD with SCCM 2012.

The issues is cause by the USB Ethernet adapter I have added all the drivers for this device to the laptops driver package and to the boot image this allows me to PXE boot the machine. 

Once the machine boots to windows for the first time it doesn't install the USB Ethernet adapter. However I know the driver is staged because if I click on the update drive button in device manager the device installs by searching the local computer.

After doing some digging into this I heard that this is caused by the driver being plugged into a USB 3.0 port and to resolve the issue I should plug it into a USB 2.0 port however the XPS13 9333 has no USB 2.0 port

Can anyone please advise who I can resolve this thanks

Hi,

We're having an issue importing new drivers, we can import drivers for Windows 7 fine but receive the following error when it's for Windows 8/8.1, 'The selected driver is not applicable to any supported platforms.' We've imported drivers before so it could be the recent upgrade to CU3. Anyone else on CU3 able to import Windows 8.1 drivers successfully. Installing the driver manually on the client works fine.

Thanks
Ben

Here's my environment:

SCCM 2012 SP1 installed on Server 2008 R2 in a Hyper-V environment

Brand new boot images created after SP1 upgrade using Windows ADK

The virtual is using 1 network adapter (the legacy network adapter has been disabled, as a trobleshooting step)

PXE and WDS have been removed and recreated numerous times

This has never worked since implementation of SCCM 2012 (7/2012)

Attempted on multiple physical clients and a virtual client

The boot images work fine when setup as USB boot media

The network boot always finds the SCCM server as this screen shows:

Then it proceeds to loading the \SMSboot\boot.sdi. Some times it fails right here other times it proceeds to \SMSImages\MFC0008D\BootImagex86.MFC0008D.wim. Either way it gets a bit into the progress bar but always fails to this screen:

The smspxe.log shows the following:

Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777391" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
 SMSPXE 4/10/2013 8:21:12 AM 844 (0x034C)
00:15:5D:0A:6C:0D, BB01BB09-CF61-4611-8820-73941512B432: device is in the database. SMSPXE 4/10/2013 8:21:12 AM 844 (0x034C)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777391" ServerName="" ServerRemoteName=""><Machine><ClientID>GUID:0ba9fb20-f317-475e-8a24-bead025b5e31</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="MFC200EE" OfferIDTime="4/2/2013 11:21:00 AM" PkgID="MFC00007" PackageVersion="" PackagePath="http://(siteserver)/SMS_DP_SMSPKG$/MFC0008D" BootImageID="MFC0008D" Mandatory="0"/></ClientIDReply>
 SMSPXE 4/10/2013 8:21:12 AM 844 (0x034C)
00:15:5D:0A:6C:0D, BB01BB09-CF61-4611-8820-73941512B432: found optional advertisement MFC200EE SMSPXE 4/10/2013 8:21:12 AM 844 (0x034C)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777391" ServerName="" ServerRemoteName=""><Machine><ClientID>GUID:0ba9fb20-f317-475e-8a24-bead025b5e31</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="MFC200EE" OfferIDTime="4/2/2013 11:21:00 AM" PkgID="MFC00007" PackageVersion="" PackagePath="http://(siteserver)/SMS_DP_SMSPKG$/MFC0008D" BootImageID="MFC0008D" Mandatory="0"/></ClientIDReply>
 SMSPXE 4/10/2013 8:21:16 AM 844 (0x034C)
00:15:5D:0A:6C:0D, BB01BB09-CF61-4611-8820-73941512B432: found optional advertisement MFC200EE SMSPXE 4/10/2013 8:21:16 AM 844 (0x034C)
Looking for bootImage MFC0008D SMSPXE 4/10/2013 8:21:16 AM 844 (0x034C)

________________________________________________________________________________________________________________________

It also shows this occasionally after "Looking for bootImage"

BootImage MFC0008D needs to be updated (new packageID=MFC0008D) VersionUpdate=true SMSPXE 4/2/2013 11:25:41 AM 4020 (0x0FB4)

________________________________________________________________________________________________________________________

The only errors I've found have been in the distmgr.log when I've updated the boot images: (notice errors related to wimgapi.dll and errors related to set attribute, remove file, and remove directory failures)

STATMSG: ID=2300 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=(siteserver) SITE=MFC PID=2676 TID=6104 GMTDATE=Tue Apr 02 20:18:43.917 2013 ISTR0="BootImagex86" ISTR1="MFC0008D" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="MFC0008D" SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:43 PM 6104 (0x17D8)
Start updating the package MFC0008D... SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:43 PM 6104 (0x17D8)
Package storage format has changed for MFC0008D. Updating the distribution points SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:43 PM 6104 (0x17D8)
Enabling package MFC0008D for SMB access on MSWNET:["SMS_SITE=MFC"]\\(siteserver)\SMSPKGC$\MFC0008D\ SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:44 PM 6104 (0x17D8)
Attempting to add or update a package on a distribution point. SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:44 PM 6104 (0x17D8)
The distribution point is on the siteserver and the package is a content type package. There is nothing to be copied over. SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:44 PM 6104 (0x17D8)
STATMSG: ID=2342 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=(siteserver) SITE=MFC PID=2676 TID=6104 GMTDATE=Tue Apr 02 20:18:44.683 2013 ISTR0="BootImagex86" ISTR1="["Display=\\(siteserver)\"]MSWNET:["SMS_SITE=MFC"]\\(siteserver)\" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=2 AID0=400 AVAL0="MFC0008D" AID1=404 AVAL1="["Display=\\(siteserver)\"]MSWNET:["SMS_SITE=MFC"]\\(siteserver)\" SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:44 PM 6104 (0x17D8)
The current user context will be used for connecting to ["Display=\\(siteserver)\"]MSWNET:["SMS_SITE=MFC"]\\(siteserver)\. SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:45 PM 6104 (0x17D8)
No network connection is needed to ["Display=\\(siteserver)\"]MSWNET:["SMS_SITE=MFC"]\\(siteserver)\ as this is the local machine. SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:45 PM 6104 (0x17D8)
CreateSignatureShare, connecting to DP SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:45 PM 6104 (0x17D8)
Signature share exists on distribution point path \\(siteserver)\SMSSIG$ SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:45 PM 6104 (0x17D8)
Set share security on share \\(siteserver)\SMSSIG$ SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:45 PM 6104 (0x17D8)
Share SMSPKGC$ exists on distribution point \\(siteserver)\SMSPKGC$ SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:45 PM 6104 (0x17D8)
Set share security on share \\(siteserver)\SMSPKGC$ SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:45 PM 6104 (0x17D8)
Set share security on share \\(siteserver)\SCCMContentLib$ SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:45 PM 6104 (0x17D8)
Successfully created directory \\(siteserver)\SMSPKGC$\MFC0008D for package MFC0008D SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:46 PM 6104 (0x17D8)
Copying package MFC0008D to the package share location \\(siteserver)\SMSPKGC$\MFC0008D on the server ["Display=\\(siteserver)\"]MSWNET:["SMS_SITE=MFC"]\\(siteserver)\ SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:46 PM 6104 (0x17D8)
SMSDP_ExpandPXEImage: MFC0008D, 1174406304 SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:47 PM 6104 (0x17D8)
Library path mismatch: \\?\C:\SCCMContentLib, C:\SCCMContentLib SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:47 PM 6104 (0x17D8)
Expanding C:\SCCMContentLib\FileLib\DE79\DE7975B36C7DCA08953E8404A1FC115DC9A250828456A8E34C5C158C1907EE14 from package MFC0008D SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:47 PM 6104 (0x17D8)
Finding Wimgapi.Dll SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:47 PM 6104 (0x17D8)
MsiEnumRelatedProducts failed SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:47 PM 6104 (0x17D8)
FindProduct failed; 0x80070103 SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:47 PM 6104 (0x17D8)
MsiEnumRelatedProducts failed SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:47 PM 6104 (0x17D8)
FindProduct failed; 0x80070103 SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:47 PM 6104 (0x17D8)
Found C:\Windows\system32\wimgapi.dll SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:47 PM 6104 (0x17D8)
Sleep 30 minutes... SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 4216 (0x1078)
SetFileAttributesW failed for C:\RemoteInstall\SMSTempBootFiles\MFC0008D\Windows\Boot\EFI\bootmgfw.efi SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
RemoveDirectoryW failed (0x80070091) for C:\RemoteInstall\SMSTempBootFiles\MFC0008D\Windows\Boot\EFI SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
SetFileAttributesW failed for C:\RemoteInstall\SMSTempBootFiles\MFC0008D\Windows\Boot\Fonts\segmono_boot.ttf SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
SetFileAttributesW failed for C:\RemoteInstall\SMSTempBootFiles\MFC0008D\Windows\Boot\Fonts\segoen_slboot.ttf SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
SetFileAttributesW failed for C:\RemoteInstall\SMSTempBootFiles\MFC0008D\Windows\Boot\Fonts\segoe_slboot.ttf SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
SetFileAttributesW failed for C:\RemoteInstall\SMSTempBootFiles\MFC0008D\Windows\Boot\Fonts\wgl4_boot.ttf SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
RemoveDirectoryW failed (0x80070091) for C:\RemoteInstall\SMSTempBootFiles\MFC0008D\Windows\Boot\Fonts SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
SetFileAttributesW failed for C:\RemoteInstall\SMSTempBootFiles\MFC0008D\Windows\Boot\PXE\abortpxe.com SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
SetFileAttributesW failed for C:\RemoteInstall\SMSTempBootFiles\MFC0008D\Windows\Boot\PXE\bootmgr.exe SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
SetFileAttributesW failed for C:\RemoteInstall\SMSTempBootFiles\MFC0008D\Windows\Boot\PXE\pxeboot.com SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
SetFileAttributesW failed for C:\RemoteInstall\SMSTempBootFiles\MFC0008D\Windows\Boot\PXE\pxeboot.n12 SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
SetFileAttributesW failed for C:\RemoteInstall\SMSTempBootFiles\MFC0008D\Windows\Boot\PXE\wdsmgfw.efi SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
SetFileAttributesW failed for C:\RemoteInstall\SMSTempBootFiles\MFC0008D\Windows\Boot\PXE\wdsnbp.com SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
RemoveDirectoryW failed (0x80070091) for C:\RemoteInstall\SMSTempBootFiles\MFC0008D\Windows\Boot\PXE SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
RemoveDirectoryW failed (0x80070091) for C:\RemoteInstall\SMSTempBootFiles\MFC0008D\Windows\Boot SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
RemoveDirectoryW failed (0x80070091) for C:\RemoteInstall\SMSTempBootFiles\MFC0008D\Windows SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
RemoveDirectoryW failed (0x80070091) for C:\RemoteInstall\SMSTempBootFiles\MFC0008D SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
Expanding MFC0008D to C:\RemoteInstall\SMSImages SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
Used 1 out of 3 allowed processing threads. SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 1872 (0x0750)
Sleep 3600 seconds... SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 1872 (0x0750)
STATMSG: ID=2330 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=(siteserver) SITE=MFC PID=2676 TID=6104 GMTDATE=Tue Apr 02 20:18:49.796 2013 ISTR0="MFC0008D" ISTR1="["Display=\\(siteserver)\"]MSWNET:["SMS_SITE=MFC"]\\(siteserver)\" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=2 AID0=400 AVAL0="MFC0008D" AID1=404 AVAL1="["Display=\\(siteserver)\"]MSWNET:["SMS_SITE=MFC"]\\(siteserver)\" SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:49 PM 6104 (0x17D8)
Successfully created/updated the package server in the data source SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:49 PM 6104 (0x17D8)
Performing cleanup prior to returning. SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:49 PM 6104 (0x17D8)
The Package Action is 1, the Update Mask is 266240 and UpdateMaskEx is 1064960. SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:49 PM 6104 (0x17D8)
Successfully created/updated the package MFC0008D SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:49 PM 6104 (0x17D8)
STATMSG: ID=2311 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=(siteserver) SITE=MFC PID=2676 TID=6104 GMTDATE=Tue Apr 02 20:18:49.943 2013 ISTR0="MFC0008D" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="MFC0008D" SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:49 PM 6104 (0x17D8)
Set share security on share \\(siteserver)\SCCMContentLib$ SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:49 PM 6104 (0x17D8)
Set share security on share \\(siteserver)\SCCMContentLib$ SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:49 PM 6104 (0x17D8)
Created policy provider trigger for ID MFC0008D SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:51 PM 6104 (0x17D8)
Package MFC0008D does not have a preferred sender. SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:51 PM 6104 (0x17D8)
Package MFC0008D is new or has changed, replicating to all applicable sites. SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:51 PM 6104 (0x17D8)
CDistributionSrcSQL::UpdateAvailableVersion PackageID=MFC0008D, Version=2, Status=2301 SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:51 PM 6104 (0x17D8)
StoredPkgVersion (2) of package MFC0008D. StoredPkgVersion in database is 2. SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:51 PM 6104 (0x17D8)
SourceVersion (2) of package MFC0008D. SourceVersion in database is 2. SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:51 PM 6104 (0x17D8)
STATMSG: ID=2301 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=(siteserver) SITE=MFC PID=2676 TID=6104 GMTDATE=Tue Apr 02 20:18:51.876 2013 ISTR0="BootImagex86" ISTR1="MFC0008D" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="MFC0008D" SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:51 PM 6104 (0x17D8)
Exiting package processing thread. SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:51 PM 6104 (0x17D8)
Used 0 out of 3 allowed processing threads. SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:57 PM 1872 (0x0750)
The last source update time for pkg MFC0008D is 4/2/2013 10:56:53 AM Pacific Daylight Time SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:57 PM 1872 (0x0750)
The next start time for pkg MFC0008D is 4/2/2013 1:18:57 PM Pacific Daylight Time SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:57 PM 1872 (0x0750)

___________________________________________________________________________________________________________________________

At this point I'm out of ideas. I've searched all the forums tried just about everything I can think of except for settings DHCP options or IP Helpers. I've declined to do that because it appears to find the server just fine. Also the client, DHCP, and the SCCMPXE Point are all on the same subnet.

Help me Obi-(technet)-wan you're my only hope!

server 2012, sccm 2012 sp1, MDT/UDI

I was trying to build a one size fits all MDT OSD task but couldn't figure out how to add mutiple OS keys so now I'm trying to at least build one that has Windows 8 32 and 64 bit types but only the 32 bit works even when I select the 64 bit image. Here is a picture from the UDI:

So I selected them and they are on the right. Any ideas what I'm doing wrong?

I can't imagine why that would be a drop down list if we couldn't select from multiple OS's.

I found an article that said to change the variable OSDImageIndex to OSDImageName in the

UDIWizard_Config.xml package file them update content but that changed nothing.

And lastly is this something we should even want to do. I was always told to keep drivers in our PE strickly to each type (32/64) and deploying 64 bit images from a single 32 bt would not contain all the drivers we need. So even if I add 2 images to a wim file I'd still be using a 32 bit PE right?

Just looking for a better way, good advice and best practice with this new product, thanks.

When I have successfully installed a client at my secondary site (with PXE Boot), I can't reinstall the same machine without removing it from the SCCM Console.

That means, I add a computer to SCCM, and I can successfully boot with PXE and the Task Sequence starts. When the Installation is finished, and I want to reinstall the computer, it will also PXE Boot, but it will not start a Task Sequence. I find in the smsts.log the entry "No task sequences available".

I searched for Obsolet Status, for Duplicated SMSBIOSGUIDs and even for dupicated MAC-Adresses, with no success. The computer Object reside in the Collection where I have the Task Sequence deployed.

I can also see in the smsts.log, that the client receive some Policies, but not the Policy for the Task Sequence. I could not find a way to reinstall the computer, without deleting it from SCCM, and add it again.

The computer can connect to the MP of the Primary Site, and to the MP at the Secondary site. And again, when I add a new computer, it always works.

If needed, I can deliver more information, and for any hints where to search, I would be very happy.

Thanks a lot.

www.sccmfaq.ch

Hi,

Can anyone help me with a preflight check in MDT (Winpe) checking for an Active Directory Computer account. By default the pre-flight is before the page which has the field for entering the computer name. If I was to move the page later in the wizard sequence would I be able to use the variable OSDComputerName. Additional does anyone have any Powershell or vscript code which could query AD for the computer account existence?

As I'll need to authenticate with AD I could use the variables OSDJoinAccount, OSDJoinPassword, OSDDomainName.

Mike