/build/static/layout/Breadcrumb_cap_w.png

Deployment Failed error log.

1st off I would like to thank everyone here for helping me. I have had no training on the k1 and k2 and I now am able to get this far. I'm not a Pro at this, not even close! but now I'm starting to appreciate the kbox.

Here is my error log. Thanks in advance! everything seems to be working when I reboot the system but it's just a hassle that it won't reboot on its own because of this error.

My k2 is on 3.4.54256 and I downloaded the media manager from the "Home" menu and installed it before creating the KBE and capturing the image. For some reason the c: partition is still the 100mb partition for windows 7 licensing. I always need to run diskpart to reassign the drive letters to get the image right.

...

2012-07-27 09:53:36-0800 [error] Error in SetFileShortName for C:\Windows\winsxs\x86_wsdscdrv.inf.resources_31bf3856ad364e35_6.1.7600.16385_en-us_6fbc043aa5345b18\WSDScDrv.dll.mui: (183) Cannot create a file when that file already exists.

2012-07-27 09:53:36-0800 [error] Error in SetFileShortName for C:\Windows\winsxs\x86_wudfusbcciddriver.inf.resources_31bf3856ad364e35_6.1.7600.16385_en-us_f0e901c698c4159b\WUDFUsbccidDriver.dll.mui: (183) Cannot create a file when that file already exists.

2012-07-27 09:53:36-0800 [error] Error in SetFileShortName for C:\Windows\winsxs\x86_wudfusbcciddriver.inf.resources_31bf3856ad364e35_6.1.7600.16385_en-us_f0e901c698c4159b\WUDFUsbccidDriver.inf_loc: (183) Cannot create a file when that file already exists.

2012-07-27 09:53:36-0800 [error] Error in SetFileShortName for C:\Windows\winsxs\x86_wudfusbcciddriver.inf.resources_31bf3856ad364e35_6.1.7600.16385_en-us_f0e901c698c4159b\WUDFUsbccidDriver.inf_loc: (183) Cannot create a file when that file already exists.

2012-07-27 09:53:36-0800 [error] Error in SetFileShortName for C:\Windows\winsxs\x86_wudfusbcciddriver.inf.resources_31bf3856ad364e35_6.1.7600.16385_en-us_f0e901c698c4159b\WUDFUsbccidDriver.dll.mui: (183) Cannot create a file when that file already exists.

2012-07-27 09:53:36-0800 [error] Error in SetFileShortName for C:\Windows\winsxs\x86_wudfusbcciddriver.inf_31bf3856ad364e35_6.1.7600.16385_none_625005cc63085793\WUDFUsbccidDriver.dll: (183) Cannot create a file when that file already exists.

2012-07-27 09:53:36-0800 [error] Error in SetFileShortName for C:\Windows\winsxs\x86_wudfusbcciddriver.inf_31bf3856ad364e35_6.1.7600.16385_none_625005cc63085793\WUDFUsbccidDriver.inf: (183) Cannot create a file when that file already exists.

2012-07-27 09:53:36-0800 [error] Error in SetFileShortName for C:\Windows\winsxs\x86_wudfusbcciddriver.inf_31bf3856ad364e35_6.1.7600.16385_none_625005cc63085793\WUDFUsbccidDriver.inf: (183) Cannot create a file when that file already exists.

2012-07-27 09:53:36-0800 [error] Error in SetFileShortName for C:\Windows\winsxs\x86_wudfusbcciddriver.inf_31bf3856ad364e35_6.1.7600.16385_none_625005cc63085793\WUDFUsbccidDriver.dll: (183) Cannot create a file when that file already exists.

2012-07-27 09:53:36-0800 [error] Error in SetFileShortName for C:\Windows\winsxs\x86_wwf-perfcnt_ini_31bf3856ad364e35_6.1.7600.16385_none_739abb4d5ca4ee30\PerfCounters_D.ini: (183) Cannot create a file when that file already exists.

2012-07-27 09:53:36-0800 [error] Error in SetFileShortName for C:\Windows\winsxs\x86_wwf-perfcnt_ini_31bf3856ad364e35_6.1.7600.16385_none_739abb4d5ca4ee30\PerfCounters_D.ini: (183) Cannot create a file when that file already exists.

2012-07-27 09:53:36-0800 [error] Error in SetFileShortName for C:\Windows\winsxs\x86_wwf-system.workflow.activities_31bf3856ad364e35_6.1.7600.16385_none_323c4905d95242ca\System.Workflow.Activities.dll: (183) Cannot create a file when that file already exists.

2012-07-27 09:53:36-0800 [error] Error in SetFileShortName for C:\Windows\winsxs\x86_wwf-system.workflow.activities_31bf3856ad364e35_6.1.7600.16385_none_323c4905d95242ca\System.Workflow.Activities.dll: (183) Cannot create a file when that file already exists.

2012-07-27 09:53:36-0800 [error] Error in SetFileShortName for C:\Windows\winsxs\x86_wwf-system.workflow.componentmodel_31bf3856ad364e35_6.1.7600.16385_none_8bba6f9c6f693e3b\System.Workflow.ComponentModel.dll: (183) Cannot create a file when that file already exists.

2012-07-27 09:53:36-0800 [error] Error in SetFileShortName for C:\Windows\winsxs\x86_wwf-system.workflow.componentmodel_31bf3856ad364e35_6.1.7600.16385_none_8bba6f9c6f693e3b\System.Workflow.ComponentModel.dll: (183) Cannot create a file when that file already exists.

2012-07-27 09:53:36-0800 [error] Error in SetFileShortName for C:\Windows\winsxs\x86_wwf-system.workflow.runtime_31bf3856ad364e35_6.1.7600.16385_none_64f133bd015a8f4f\System.Workflow.Runtime.dll: (183) Cannot create a file when that file already exists.

2012-07-27 09:53:36-0800 [error] Error in SetFileShortName for C:\Windows\winsxs\x86_wwf-system.workflow.runtime_31bf3856ad364e35_6.1.7600.16385_none_64f133bd015a8f4f\System.Workflow.Runtime.dll: (183) Cannot create a file when that file already exists.

2012-07-27 09:53:36-0800 [error] Error in SetFileShortName for C:\Windows\winsxs\x86_xnacc.inf.resources_31bf3856ad364e35_6.1.7600.16385_en-us_8ef6f9a790103a93\xnacc.inf_loc: (183) Cannot create a file when that file already exists.

2012-07-27 09:53:36-0800 [error] Error in SetFileShortName for C:\Windows\winsxs\x86_xnacc.inf.resources_31bf3856ad364e35_6.1.7600.16385_en-us_8ef6f9a790103a93\xnacc.inf_loc: (183) Cannot create a file when that file already exists.

2012-07-27 09:53:39-0800 [error] Failed to unlock file for writing for D:\Boot\BCD: (5) Access is denied.

2012-07-27 09:53:39-0800 [error] Couldn't apply metadata for D:\Boot: (5) Access is denied.

2012-07-27 09:53:39-0800 [info] Items processed: 56766 (7.84 GB)
2012-07-27 09:53:39-0800 [info] Items transferred: 378 (286.6 MB)
2012-07-27 09:53:39-0800 [warning] Metadata Errors: 1
2012-07-27 09:53:39-0800 [error] Failed to complete successfully.


0 Comments   [ + ] Show comments

Answers (1)

Answer Summary:
Posted by: SMal.tmcc 11 years ago
Red Belt
1

you said:

 For some reason the c: partition is still the 100mb partition for windows 7 licensing. I always need to run diskpart to reassign the drive letters to get the image right.

Is this a scrited install or a deployment of a captured image?


Comments:
  • Look on your master you captured from using disk manager or diskpart, how many partitions are on the drive? - SMal.tmcc 11 years ago
  • If there is only one could you post a screen shot of your pre tasks of that deployment - SMal.tmcc 11 years ago
  • When I am about to capture an image. On the screen where it lets you name the image and select the partitions to copy. It is always switched around. - iandizon 11 years ago
  • You should recreate your master with only one partition
    lots of problems keeping the 100meg and it does not help much by keeping.

    http://www.itninja.com/question/windows-7-image-strategies

    http://www.kace.com/support/resources/kb/article/Deploy-a-Windows-7-Image-Containing-the-100-MB-System-Partition - SMal.tmcc 11 years ago
  • All my images have only 1 partition and works much easier
    http://www.itninja.com/blog/view/windows-7-image-process-for-the-college-s-classrooms - SMal.tmcc 11 years ago
  • I don't want to keep the 2nd partition for some reason it's always there on a fresh windows 7 installation. I thought it had something to do with licensing. BTW I have OEM windows 7 pro keys and I don't have a volume license, would this be an issue? My image is all complete and I don't want to start over is there something I can do to just get rid of the 100mb partiton and have a working OS?

    Thanks in advance. - iandizon 11 years ago
    • What I do is create my images on a VM. Then snapshot right before sysprep. That way if you screw up you just load the snapshot. This helped me a lot when I was learning how to create XML files.

      This also makes updating the image quicker. - dugullett 11 years ago
      • They gave me over a dozen machines of different models, I like it since I do not have deal with VM and also I can make sure drivers work on all models. I use windows image to a second HDD, it creates a VHD file to restore to primary. I think your greatest advantage is restore a master image time is seconds comparied to mine taking 5-10 min

        The very last things I do before sysprep is file cleanup and then backup of image. - SMal.tmcc 11 years ago
  • Here's the screen shot. what a pain. http://screencast.com/t/FT0gVCy9j - iandizon 11 years ago
  • Capture the OS drive on your master to Kace (do not sysprep). Shut down the machine and put a different HDD in your master machine. Deploy that image back to the new drive, creating only a single partition in Kace and do no extra post tasks to image just the basics to create file system. Do not reboot when done, instead go to recovery and open a command window, fix anything needed with diskpart. If it boots you now have a master with only one partition and no reinstall - SMal.tmcc 11 years ago
  • Do not boot both drives in different computers at same time, will generate Dup SIDS, Best to either shelf for emergancy or erase old drive after - SMal.tmcc 11 years ago
  • Thanks for all your help SMal.tmcc everything works now. I still get the file already exsits error but it now reboots automatically so I'm happy. I'm from Reno NV aswell maybe we can grab some coffee sometime. - iandizon 11 years ago
  • If you want to go to the Air Race's in Sept, let me know I take care of their POS and other systems so I live there. Just shoot me an email.
    If you did take a image of your master prior to sysprep make sure you delete the image so no one deplyoys it and creates Dup SID's - SMal.tmcc 11 years ago

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ