Good Morning,
My client has a Config Manager 2012 R2 installed, with ADMT 8, MDT 2012 update 1 and the WINPE3.1 support patch installed.
He's captured and built his own Windows 7 Pro x86 WIM file with some built-in drivers and softwares and deploying it alone works like magic.
Now, when he tries to perform an XP to 7 deloyment it failes. this is the task real quick:

Capture Windows Settings, Capture Network Settings,  Set Local State Location, Set USMT Additional Capture (which is the OSDMigrateAdditionalCaptureOptions variable with /nocompress and /hardlink), Capture User Files and Settings (Using USMT package which saves everything to a share on the SCCM server), Reset in Windows PE, Apply Operating System (Location is Disk 0 Partition 1), Apply Windows Settings, Apply Network Settings (Joins in a domain), Apply Device Drivers, Setup Windows and Configuration (Using the Config Manager Client Upgrade 6), Set USMT Additional Restore, Retore User Files and Settings.

I'll be adding the smsts.log from the latest attemp in the following post. if you need anything else, be it a file or any answer, please tell me.

Thank you for any insight you may grant.

Hi there,

I'm new to SCCM 2012, and am receiving the following error when deploying an operating system. This happens when I PXE boot or use bootable media to bare metal boot (haven't tested any other form of OSD)."Failed to create instance for IMTCTokenHandler interface, hr=0x80070005OSDSetupHook3/19/2014 3:45:01 PM1292 (0x050C)" The OSD completes, and I'm able to log into the new machine normally. Everything looks like it worked correct, but I'd like to figure out why SCCM is throwing that error. I can attatch the full error log if that would help, but that line is the only failure I saw. Any suggestions or help would be appreciated.

Thanks,

Alex

I am currently using PRINTMIG to migrate mapped printers from XP to win7 on workstations. I am experiencing failures to map Dell and RICO printers. I just read "Printbrm" is supposed to replace PRINTMIG but does it also work with XP?

Im also curious what others are currently using to migrate and remap printers from XP to Win7?????

tconners

Hi,

i have a OSD set up for my travel mate 6594 machine that currently only install Windows 8.1 32bit and the SCCM client. This works with no problems however when I try changing it to a 64bit OS ( ive tried win8.1, 8 and 7) after applying the image and when it tried to install the SCCM client it crashes saying OSDSetupHook.exe - Aplication Error the error says The instruction at *number* referenced memory at *numbers*. the memory could not be read. I have installed a 64bit os manually on this machine previously without problems.

My server is 2012 and SCCM is 2012 sp1 v5.07804.1400

Thanks

Mike

We are currently experiencing an issue when completing an operating system deployment with Office 2010 integration.

A summary of our current environment is as follows:

- The package/software deployment feature itself works on Windows 7 and 8 domain workstations, but not during OSD.

- We created another distribution point server to do the operating system deployment.

- The task sequence feature works for software and packaging deployment (not during OSD).

- We do have a secure and certificate based SCCM 2012 R2 environment in place, which may play a part in the issues that we are experiencing.

Anyways, what we would like to do is have Office 2010 and other software installed prior to capturing an image. Also, the Task Sequence Media option that we were attempting had failed as well. Any thoughts on this? Thanks.

Running into an odd situation between OSD refresh and "software center". I have an OSD task sequence advertised to a device collection as "available" which runs a OSD refresh sequence (same OS).

The sequence kicks off fine from software center and the OSD sequence is working, however when the sequence finishes and i log back into the machine, when i check Software center the task sequence is showing as "installed" versus available. How do I make it so the sequence always shows as "available" regardless of if it has been executed or not?

I seem to be getting a fairly common generic error but with possibly with a slight difference then some of the other problems/answers I have seen.  Generally it looks like this is a DNS issue but I am not sure in my case.

Let me 1^st describe my infrastructure and what I am trying to accomplish.  System Center 2012 R2, trying to deploy server 2012.  We use PKI on the main MPs/DPs.  I have another DP that I will use for OSD content that won’t use PKI.  I am 1^st attempting to use boot media, vs PXE, to image a computer.  I have distributed the content to the DP, created a boot media USB and everything looks good there as far as I can tell.  My boot media selects the PKI MP and we have created the client cert and I direct it to the non-http DP.  The process seems to accept the certificate and the boot media creation completes.  Next boot off the media on the computer and drop into Windows PE where I can manually enter the IP information.  When I click next the process fails.

Error:

Failed to Run Task Sequence

An error occurred while retrieving policy for this computer (0x80004005).

So starting some of the troubleshooting I F8.

-Can I ping the SCCM site servers?  Yes, I can ping, both short and FQDN, the primary, MP, DP.

Looking at the SMSTSLog I see the following lines/errors.

1)Failed to open PXE registry key.  Not a PXE boot.

2)Failed to find the source drive where WinPE was booted from

But then the next line is:  Executing from Media WinPE

These 2 are at the top of the log and the process seems to continue on with the IP and variable information.  These are the lines of information later in the log with the error(s):

-CLibSMSMessageWinHTTPTransport::Send:URL: (my MP)

-In SSL, but with no client cert

-Error.  Received 0x80072ee7 from WinHttpSendRequest.

-Hr,HRESULT=80072ee7

-sending with winhttp failed, 80072ee7

-m_pHttp Transport -> (etc….)

-MPKeyInformation.RequestMPKeyInformationForMedia

-Failed to get information of MP: https//(my MP)

So I am wondering where I start.  I don’t see that unknown host line that seems to indicate that it is a DNS issue.  I see some stuff about the in SSL but with no cert.  Does this mean that the cert we had to create isn’t working correctly?  We pretty much followed http://www.jamesbannanit.com/2012/05/how-to-build-and-capture-in-configuration-manager-2012-using-https/

I have also looked through this http://blogs.technet.com/b/configurationmgr/archive/2009/07/27/a-step-by-step-for-using-osd-through-system-center-configuration-manager-2007.aspx

And I have pretty much everything done there except a network access account.  Looking at my settings I am set to, “Use the computer account of the Configuration Manager client”  However, my computer I am trying to image is a “WORKGROUP” and not joining the domain.  But.. am I really getting that far in the process?  Would I be failing to get policy because of this or does this just come into play when I try to get the OS from the DP?

 Hi,
 
I am trying to import drivers into SCCM 2012 SP1. It gets to 99% then fails with errors like listed below.
Any suggestions on how I can make this work?

Thanks,

Ward.
 
 Success: Imported CI category instance (5):
• Create new x86
• Create new Win7
• Create new NIC
• Create new Acer TravelMate 6592
• Create new Bootwim x86
 
  Success: Imported Device Drivers (2):
• Create new Intel(R) PRO/1000 PT Dual Port Network Connection
• Create new Intel(R) PRO/1000 PT Dual Port Network Connection
 
  Error: Imported Driver Package (1):
• Create new Intel 82566MM Gigabit Network Driver (Win7)
Generic failure
instance of SMS_ExtendedStatus
{
 Description = "CIContentSourcePath - '\\\\server1\\Data\\OSD_Test\\Intel 82566MM Gigabit Network Driver (Win7)_files\\Intel(R) PRO1000 PT Dual Port Network Connection_1\\' could not be found\n";
 ErrorCode = 3;
 File = "e:\\qfe\\nts\\sms\\siteserver\\sdk_provider\\smsprov\\ssppackage.cpp";
 Line = 3815;
 Operation = "ExecMethod";
 ParameterInfo = "SMS_DriverPackage.PackageID=\"P0100019\"";
 ProviderName = "WinMgmt";
 StatusCode = 2147749889;
};
 
ll

  Error: Imported Driver Package (1):
• Create new XMS6630-4630 W7x64 drivers
Generic failure
instance of SMS_ExtendedStatus
{
 Description = "SMS provider doesn't have read, write or delete permission to the package source path";
 ErrorCode = 2;
 File = "e:\\qfe\\nts\\sms\\siteserver\\sdk_provider\\smsprov\\sspdriverpackage.cpp";
 Line = 131;
 ObjectInfo = "\\\\server1\\Data\\OSD_Test\\VTest Share\\XMS6630-4630_W7x64_SCCM2012_Drivers_v2_files\\XMS6630-4630 W7x64 drivers\\";
 Operation = "PutInstance";
 ParameterInfo = "";
 ProviderName = "ExtnProv";
 StatusCode = 2147749889;
};

I have a few command lines I would like to run so I've added the steps to my task sequence.  Under Properties of the Run Command Line step, I have the command line: set as follows

cmd /c del c:\Win7CapImage

I also have the Options page of the task to continue on error.

The folder definitely exists but never gets deleted, am I doing something wrong?

HunBoy Started learning from this page

I'm using MDT in conjunction with WDS to deploy Windows 7 in my organization. I use the MDT Computers database to profile machines. (i.e. select certain applications to be installed to specific machines based on MAC address.) In my reference images I have removed all the components under Media Features, as most users do not need them. However, some users need Windows Media Player.

In the Computers Database properties, under the Details section, I noticed a property called OSFeatures. I tried setting the value to MediaPlayback,WindowsMediaPlayer and just WindowsMediaPlayer, but Windows Media Player does not get installed. Am I not entering the value correctly?

My goal is to be able to add Windows Media Player to specific machines.

Thanks in advance

I am a true believer in using Build and Capture and have never used capture media to generate a WIM from a reference computer.  I do believe there are some scenarios where the capture media is required.  I have a few questions about using capture media.  Should the ConfigMgr client be deployed on the reference computer before capturing?  I believe the answer is no.  I think it could be buty it would be cleaner to leave it off. Should SCEP be deployed on the reference computer before capturing?  I believe the answer is no.  Are there any guidelines outlining these particular type questions?

I believe there is a reason why SCEP should not be deployed before the capture, but I can't find a reference to the reason.

Thanks

Good day and thanks for any help I can get with this.  From what I have seen on Google, it seems that there is no need to worry about this but I just wanted to be sure.

We are running System Center 2012 R2 on Windows Server 2012 R2 and everything is running pretty well. We are now looking at OS deployment of Windows 8.1 enterprise.  Images are in place and I have created a task sequence that will install the OS to known computers in a collection.  The task sequence seems to run fine but at the very end I get a Task Sequence failed with error 0x80004005.  If I click the reboot button the system reboots and everything looks fine, except that in SC2012 and in Software Center the sequence shows as failed. Below is just the end of the SMSTS.Log file from the client system

I guess what I would like to know is 1) should I be concerned about this error 2) if so what can I do to fix it.

Jan Hoedt

I have SCCM R2 with MDT 2013.

PXE boot enabled. I am trying to deploy Windows 7 reference image to LENOVO computer where Windows 8 UEFI OEM is preinstalled.

My image is BIOS only so I change in LENOVO bios to disable UEFI.

Deployment is MDT task sequence (did not change anything in it)

I can PXE boot and when TS starts it momentarily failed with error 800700A1

smsts.log shows that c: is not bootable:

Create and capture works great with MDT TS, but I run it on clean Hyper-v.

Is it possible to workaround this problem?

There are several issue’s. but I hope you can help me with some of them.

I’m deploying Windows 8.1 from within SCCM 2012 R2, using the latest (oktober 2013) version for MDT 6.2.5019.0

I’ve created a MDT Task Sequence option “Client Task Sequence”, and didn’t change anything there.

Followed a hands-on example fromhttps://www.youtube.com/watch?v=wi1I2XfO11M

The Windows 8.1 OS is installed, but all kinds of failures came up:

-      Received an Application Discovery Warning in the UDI wizard designer, and none of the selected programms and applications where installed during running of the task sequence.

Looking at the logging aftherwards in AppDiscovery.log it showed

07:23:43.416 03-27-2014     3          AppDiscovery Error 2: Product version registry not found.

07:23:43.431 03-27-2014     2          AppDiscovery Opening file [\\AppDiscoveryresult.xml.app]

07:23:43.431 03-27-2014     3          AppDiscovery Error 1: File open failed

07:23:43.431 03-27-2014     3          AppDiscovery Error 33554432: Fatal error while processing master list:

07:23:43.431 03-27-2014     3          AppDiscovery Error 16: --| Failure while opening master list file.

07:23:43.431 03-27-2014     3          AppDiscovery Error 33685504: --| Failure to open file.

-      The Computername, which seems to be a very common error, is not correct. I’ve added “Computer-%serialnumber%” as a default value in UDI Wizard designer.

But stil during installation when the several deployment options where shown, it proposed MININT-xxxxxx.

Even changed this setting there, but still the computername remained MININT-xxxxxx when the installation completed.

-      The OS was installed on an E:\ volume instead on C:\. Even when I chose C:\ during installation.

There where several Volumes created. BDEDrive without a drive letter.

OSDisk with drive letter E:

CD-Rom Station with drive letter D:\

Hope you can help me with some of these issues.

I am working on using PXE with SCCM 2012 and finally got my test VM to boot with the standard x86 boot image. This is the process:

1. Start up VM with no OS

2. Contacts SCCM and I press F12 to Network Boot

3. Boots into a SCCM screen and says " Windows is starting up" then " Preparing Network Connections".

4. Then all i see is a blank screen. After about a minute it will just reboot.

I found this post that discusses adding the drivers need for the boot images:

http://social.technet.microsoft.com/Forums/en-US/fd96466b-0521-48d8-b31e-4477468982fe/sccm-pxe-boot-initiated-but-nothing-happens-after-that?forum=configmgrosd

I added the entire VMware tools Driver folder to both my boot images. (All it had in there was a SCSI adapter)

Tried to redo the PXE and still get the same menages with the blank screen after that. 

What am I missing here? 

Hi ,

I am looking for simple steps to create capture image task sequence using configuration manager 2012 R2 integrated with MDT 2013. I already have reference VM created with all required applications including config manager client. I need steps to prepare config client, OS and capture the image on network location. Do I need to initiate it from within the running OS? Its windows 7 x64 that need to be captured as WIM. Thanks in advance.

Regards,

I'm need help in the issues I've having.   I've been working on this for days and I can't get it to work.  Here is what I know and what I've done.

I created a blank task sequence.  Here is what it looks like and what I've tried.


OSPreserveDriverLetter = DISABLED
Apply OS   =   specify a logical driver letter = C:
Result:  OS installs to D:\.    all applications Did install.    
Prior to the ConfigMan client installing the OS was on C:  after the client installed and the system rebooted the OS was on D:

OSPreserveDriverLetter = False
Apply OS   =   specify a logical driver letter = C:
Result:  OS installs to C:\.    No applications installed.



OSPreserveDriverLetter = True
Apply OS   =   specify a logical driver letter = C:
Result:   OS installs to D:\.   All applications Did install.


----------------------------------------------------------------------------------------------------------


OSPreserveDriverLetter = DISABLED
Apply OS   =   Logical driver letter stored in a variable
Result:    =   OS installs do D:\    All applications Did install



OSPreserveDriverLetter = False
Apply OS   =   Logical driver letter stored in a variable
Result:    =    OS installed to C:\.   No applications installed.  


OSPreserveDriverLetter = True
Apply OS   =   Logical driver letter stored in a variable
Result:    =    OS installed to  D:\.   All applications Did install.
Prior to the ConfigMan client installing the OS was on C:  after the client installed and the system rebooted the OS was on D:

Here is my task sequence

so why can I install to C: & have my apps install too?    Am I missing  hotfix or a patch?  Service Pack?   

Please help.

I have been having trouble with setting up PXE and booting and we suspected there were issues with PXE and WDS.

I unchecked PXE and uninstalled the WDS role. 

I also deleted the boot images (x86 and x64).

Now I'm having trouble re-adding boot images. 

I tried with WAIK command the copype.cmd amd65 d:\temp\winpe64, that didn't create the files I needed, as boot wizard would detect no boot information when I'd select the .wim in the wizard. 

Then I read that I may need Windows ADK instead, so I uninstalled WAIK and installed Windows ADK 8 and ran copype.cmd amd64 d:\winpe, that appeared to generate a boot.wim that the wizard would detect.

However, I cannot complete the Add Boot Image Wizard. it now throws me this error:

"The specified file is invalid. Only maximum compression type is supported. "

This error does not appear anywhere else on Google, so I'm really worried there's no solution. 

What can I do to just simply re-add the boot files for Windows 7 imaging?