Just wondering if anyone has starting using SCCM 2012R2 MDT to deploy Surface Pro + OSD's via USB Network Adapter?
So far all I've done is pulled down all the drivers
http://www.microsoft.com/en-us/download/details.aspx?id=38826 and created a driver package.
Any great words of wisdom?
I previously posted this to the Powerwshell forum so hopefully cross posting isn't breaking any rules....
Does anyone know if there is any way to modify the sequence propery of an sms_tasksequencepackage object with Powershell? I am trying to migrate a task sequence from one site to another and want to programatically update the package IDs to match what
is on the destination site. I have everything down except the ability to actually write the value of the xml string to the sequence property.
When I connect to the wmi object directly, I can't even get the sequence property. It just comes back blank. When I use the get-cmtasksequence cmdlet, I can get the value, but I can't find any way to modify it and write it back. I have tried
using a combination of the two to get the sequence value with the cmdlet and then try to write it back to the wmi object, but that won't take either.
I have even tried running an export, extracting the zip, and modifying the xml from there to reimport, but there is some kind of psmdcp hash value that appears to be rejecting it when I try to reimport.
It seems like there must be some way unless Microsoft has just made the property read only via WMI and is using some proprietary hash value to prevent changing the task sequence between export and import. I'd love to hear anyone's input on this.
please assist me for lite touch installation. i have integrated MDT 2013 with SCCM 2012 R2 then not sure what next? like how to configure MDT tool kit files and UDI settings to enable lite touch installation
how to change windows8.1 start up screen and if settings needs to change before capturing image?
I have two SCCM sites, one DEV and one PROD. The packages on both sites are identical and were all created via scripting. The only difference is the package ID. I have a task sequence in my DEV environment that I would like to export and then import into PROD. I want to programmatically update all the package IDs so I don't have to go through and click and update every one. I have extracted my exported zip file and gone into the object.xml and referencesinfo.xml files. I updated all the package IDs to match the destination sites package IDs, but when I import they still all come up blank.
Everythings looks fine in the xml to me, and at this point I figure that there must be some other file in play. I have even gone into the task sequence after I imported the blank one, manually updated the packages, then exported and compared the object.xml files. They look identical except for the Task Sequence package ID, timestamp and sedoobjectversion which would all be expected.
Is there anything other than the object.xml file and referencesingo.xml that would need to be updated to change a package ID? I can provide the xml file if it would be useful.
Hi,
I have a requirement to partition disks during OSD. I have used step Partition Disk 0 to create a single drive.
Below are scenarios I would like advice on.
1. Creating C:\ 200GB & D:\ 300GB from a single disk of 500GB
2. D:\ if existing should not be formatted.
Hi
I'm currently building a ConfigMgr Tasksequence for a RDS VDI solution. At the end of the TS I have a PowerShell Script which prepares the SCCM Client for the master image (delete certs, remove provisioning mode). I would like to use the variable SMSTSPostAction for doing the sysprep with a shutdown. But the machine hangs after rebooting out from the PS Script. Of course the Agent is no longer available but the SMSTSPost Action Variable should start.
Does anyone have an idea?
I need to use SCCM as MDT is not an option.
how to integrate and configure task sequence for UDI (MDT 2013) same can used to deploy fresh\refresh new windows7/8 install or reinstall or reinstall scenarios
Hi all,
We are new to SCCM, and have built out 2012R2 CU3. Our field services team currently uses a process where they use the existing LANDesk solution to deploy an image to a drive and then they duplicate that drive with a hardware drive copying machine. They want to do the same process moving forward and we are investigating solutions. We have tried using OEM imaging, and even created a task that executes a script to start the process but all the documentation we've found seems to be from 2007 which leads to issues especially with GPT and UEFI systems.
I've also gotten inventive and tried creating a job that runs ONLY the partition/image deployment followed up with a second job that is supposed to finish the deployment. This blows up with errors on the second part because I am not installing an image.
I'm sure someone here has run into this and has a good solution. We are open to pretty much anything that would allow us to clone the drives and then finish the client and package installation afterwards. It would be particularly sexy if someone has a solution that allows us to install drivers for whatever model is detected after the drive has been dup'ed and put into the target system model, then have it install apps and the SCCM client.
Thanks in advance!
Hi All, I've got a bit of a weird issue and I'm hoping someone can help me out. My company recently purchased a number of Dell Latitude E7440 laptops, split between two configurations. One has an i7 Proc, 8GB of RAM and a 128GB SSD. The other has an i7 proc, 16GB of RAM and a 256GB SSD. Strange thing is, I can image the 8GB model but not the 16GB model..
I've searched all through the Internet (as far as I can find anyway) and so far everything I've found in reference to trouble imaging the E7440 model is related to the NIC drivers being wrong in the Dell CAB, or a Microsoft Hotfix (KMDF v1.11) that needed to be included in the WIM so that newer drivers could install without failure. After some investigation I have confirmed that neither one of these are the answer to my problem, which I figured right from the start since I can image the 8GB model without issue.
Here's my problem: I start the Windows 7 x64 task sequence, which pulls down a custom WIM and applies it. Then it installs drivers before moving on to the "Setup Windows and ConfigMgr" step, which it fails on. When the system reboots I see that it has all the driver installed, but the network is not working. Upon further investigation I find that there are a TON of Windows services that are not started, and cannot be started manually.
I've tried trimming my TS back to just applying the WIM and then installing the drivers, but that still does no good. Every time it has the same end result - screwed up Windows OS. And yet I can use this EXACT same TS for the 8GB model, and plenty of other Dell models too. Worst of all, there is no SMSTS.log file to reference for errors! This one seriously has me scratching my head..
Any help or direction you guys can give would be greatly appreciated.
Hi,
We have SCCM 2012 R2 in place and have previously had it working fine to PXE deploy images to machines.
Recently we have bought a bunch of Surface Pro 3 tablets and have setup a task sequence and imported drivers to our environment. We downloaded the drivers from microsofts website. We have the surface pro 3 docks and i have inserted both NIC drivers from microsofts website into the boot image its using. The content is showing as being successfully distributed to the local DP after adding the drivers.
The problem seems to be that when the client pxe boots it gets to the SCCM splash screen and then reboots. It looks like there is no network connectivity as i've looked at command prompt and tried to ping the sccm server and its unreachable.
In the smsts log file on the client there are errors stating:
"Failed to download pxe variable file. Code(0x00000001)
PxeGetPxeData failed with 0x80004005:
and
"RegOpenKeyExW failed for Software\Microsoft\SMS\Task Sequence
GetTsRegValue() failed. 0x80070002"
Any suggestions?
Any tips?
Hi everyone,
I have recently integrated MDT2013 with my SCCM 2012 R2 and I am trying to move away from OSD in SCCM and switch to MDT. I managed to get a blank image deployed and now I am trying to tweak CustomSettings.ini to install applications based on the default
gateway and model. For some reason, the apps are getting pulled but not deployed. Here is what I have in the files:
Settings Package - CustomSettings.ini
When the TS runs, I can see it's getting all the apps from the list, here is a snippet from ZTIGather.log
So the settings do get picked up and selected. ZTICoalesce.log also shows the apps picked up:
Now when I go to the smsts.log file, I can see this:
and later
After that, no other apps are mentioned and seems like the failure on ESET drops the whole sequence and moves forward. I can see later the default admin being added correctly.
Any ideas what I may be missing here? Especially on the failed policy download?
Thanks
Jakub
Hi there,
I have a SCCM 2012 R2 environment running on Windows Server 2012 on VMWare Workstation 10.0.1. My TS is deploying Win7x64 to another VM. I am using MDT integration and the first action after "Setup Winodws and ConfigMgr", and restarting from WinPE to Win7, is "Use Microsoft Deployment Toolkit Package". It always downloads part of the package before it fails on a seemingly random file.
From the F8 prompt i am able to ping the MP/DP. From the MP/DP I am also able to download the file in question using Internet Explorer. From my viewpoint this looks like a transient network error, but I am open to any suggestions at this point. I have also seen the TS run through without a hitch once, so it seems like it's not perfectly consistent.
Does anyone have any idea as to what could cause this? Where should I be looking? Any troubleshooting tips?
External link to smsts.log
Snippet of my TS
Snippet from the smsts.log:
Downloading file /SMS_DP_SMSPKG$/CEN00024/sccm?/Scripts/DeployWiz_Computer.png range 0-6593 InstallSoftware 2014-02-04 12:43:24 2356 (0x0934) Downloaded file from http://CM01.spectre.local:80/SMS_DP_SMSPKG$/CEN00024/sccm?/Scripts/DeployWiz_Computer.png to C:\_SMSTaskSequence\Packages\CEN00024\Scripts/DeployWiz_Computer.png InstallSoftware 2014-02-04 12:43:24 2356 (0x0934) Downloading file /SMS_DP_SMSPKG$/CEN00024/sccm?/Scripts/DeployWiz_ComputerBackup.vbs range 0-2690 InstallSoftware 2014-02-04 12:43:24 2356 (0x0934) Downloaded file from http://CM01.spectre.local:80/SMS_DP_SMSPKG$/CEN00024/sccm?/Scripts/DeployWiz_ComputerBackup.vbs to C:\_SMSTaskSequence\Packages\CEN00024\Scripts/DeployWiz_ComputerBackup.vbs InstallSoftware 2014-02-04 12:43:24 2356 (0x0934) Downloading file /SMS_DP_SMSPKG$/CEN00024/sccm?/Scripts/DeployWiz_ComputerBackup.xml range 0-2999 InstallSoftware 2014-02-04 12:43:24 2356 (0x0934) Downloaded file from http://CM01.spectre.local:80/SMS_DP_SMSPKG$/CEN00024/sccm?/Scripts/DeployWiz_ComputerBackup.xml to C:\_SMSTaskSequence\Packages\CEN00024\Scripts/DeployWiz_ComputerBackup.xml InstallSoftware 2014-02-04 12:43:24 2356 (0x0934) WinHttpSendRequest (hRequest, pszAdditionalHeader != NULL ? pszAdditionalHeader : WINHTTP_NO_ADDITIONAL_HEADERS, (DWORD)-1, NULL, 0, 0, NULL), HRESULT=80072ee2 (e:\qfe\nts\sms\framework\tscore\downloadcontent.cpp,1211) InstallSoftware 2014-02-04 12:43:45 2356 (0x0934) WinHttpSendRequest failed. InstallSoftware 2014-02-04 12:43:45 2356 (0x0934) SendWinHttpRequest failed. 80072ee2. InstallSoftware 2014-02-04 12:43:45 2356 (0x0934) SendWinHttpRequest (hSession, hConnect, hRequest, pszSourcePath, sWinHttpRangeHeader.c_str(), bUseSSL, ullContentLength, LastGoodCredentialsType), HRESULT=80072ee2 (e:\qfe\nts\sms\framework\tscore\downloadcontent.cpp,1424) InstallSoftware 2014-02-04 12:43:45 2356 (0x0934) DownloadFileWithRanges() failed. 80072ee2. InstallSoftware 2014-02-04 12:43:45 2356 (0x0934) DownloadFileWithRanges (hSession, hConnect, sRequest, hFile, pszDestination, ullFileSize, ulPackageSize, ulDownLoaded, LastGoodCredentialsType, bUseSSL), HRESULT=80072ee2 (e:\qfe\nts\sms\framework\tscore\downloadcontent.cpp,1514) InstallSoftware 2014-02-04 12:43:45 2356 (0x0934) DownloadFile() failed for http://CM01.spectre.local:80/SMS_DP_SMSPKG$/CEN00024/sccm?/Scripts/DeployWiz_ComputerName.vbs, C:\_SMSTaskSequence\Packages\CEN00024\Scripts/DeployWiz_ComputerName.vbs. 80072ee2. InstallSoftware 2014-02-04 12:43:45 2356 (0x0934) DownloadFile (hSession, hConnect, sSourceFile.c_str(), sDestinationFile.c_str(), ulPackageSize, ulDownLoaded, LastGoodCredentialsType, bUseSSL), HRESULT=80072ee2 (e:\qfe\nts\sms\framework\tscore\downloadcontent.cpp,1590) InstallSoftware 2014-02-04 12:43:45 2356 (0x0934) Error downloading file from http://CM01.spectre.local:80/SMS_DP_SMSPKG$/CEN00024/sccm?/Scripts/DeployWiz_ComputerName.vbs to C:\_SMSTaskSequence\Packages\CEN00024\Scripts/DeployWiz_ComputerName.vbs InstallSoftware 2014-02-04 12:43:45 2356 (0x0934) DownloadFiles() failed. 80072ee2. InstallSoftware 2014-02-04 12:43:45 2356 (0x0934) DownloadFiles (setDirs, setFiles, sDestination.c_str(), bUseSSL), HRESULT=80072ee2 (e:\qfe\nts\sms\framework\tscore\resolvesource.cpp,2529) InstallSoftware 2014-02-04 12:43:45 2356 (0x0934) Download() failed. 80072ee2. InstallSoftware 2014-02-04 12:43:45 2356 (0x0934) DownloadContentAndVerifyHash() failed. 80070002. InstallSoftware 2014-02-04 12:43:45 2356 (0x0934) DownloadContentAndVerifyHash ( pszPackageID, L"SMSPackage", saHttpContentSources, saSMBContentSources, saMulticastContentSources, sDestination, dwFlags, L"", 0, dwPackageFlags, mapNetworkAccess ), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\resolvesource.cpp,3052) InstallSoftware 2014-02-04 12:43:45 2356 (0x0934) DownloadContentLocally (pszSource, sSourceDirectory, dwFlags, hUserToken, mapNetworkAccess), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\resolvesource.cpp,3273) InstallSoftware 2014-02-04 12:43:45 2356 (0x0934) TS::Utility::ResolveSource (pszPkgID, sPath, 0, hUserToken, mapNetworkAccess), HRESULT=80070002 (e:\nts_sccm_release\sms\client\osdeployment\installsoftware\runcommandline.cpp,399) InstallSoftware 2014-02-04 12:43:45 2356 (0x0934) Failed to resolve the source for SMS PKGID=CEN00024, hr=0x80070002 InstallSoftware 2014-02-04 12:43:45 2356 (0x0934) cmd.Execute(pszPkgID, sProgramName, dwCmdLineExitCode), HRESULT=80070002 (e:\nts_sccm_release\sms\client\osdeployment\installsoftware\main.cpp,372) InstallSoftware 2014-02-04 12:43:45 2356 (0x0934) Install Software failed to run command line, hr=0x80070002 InstallSoftware 2014-02-04 12:43:45 2356 (0x0934) Process completed with exit code 2147942402 TSManager 2014-02-04 12:43:45 1672 (0x0688) !--------------------------------------------------------------------------------------------! TSManager 2014-02-04 12:43:45 1672 (0x0688) Failed to run the action: Use Toolkit Package. The system cannot find the file specified. (Error: 80070002; Source: Windows) TSManager 2014-02-04 12:43:45 1672 (0x0688) MP server http://CM01.spectre.local. Ports 80,443. CRL=false. TSManager 2014-02-04 12:43:45 1672 (0x0688) Setting authenticator TSManager 2014-02-04 12:43:45 1672 (0x0688)
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!
Single Primary Site running SCCM 2012 R2 CU3. Using USMT to copy profile locally and using State Migration Point.
Migrating from XP to Windows 7.
Last night I kicked off a profile copy for a system swap, the profile was 8Gb and the copy began at 8pm. The copy is still running.
Network is not happy, the process is taking over 60% of one site.
A couple of question;
Am I correct in that the process runs by <workstation site 1> to <server site 1> and then <server site 1> to <workstation site 2> ?