Error Creating Image Drive C Rc 2
Contents |
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove error creating an image of drive d rc=112 From My Forums Answered by: Error creating an image "error creating an image of drive d" "rc = 5" of Drive C:, rc =2 Solution Accelerators > Microsoft Deployment Toolkit Question 0 Sign zti error - non-zero return code by ztibackup, rc = 112 in to vote Hello, as mentioned in the subject line above, I get the following error when trying to capture an image of
Mdt "error Creating An Image Of Drive D:" "rc = 5"
my reference computer: Error creating an image of Drive C:, rc =2 ZTI Error - Non Zero return code by ZTIBackup, rc=2 ZTI ERROR - Non-zero return code by LiteTouch, rc = -2147467259 I've looked at other threads and tried suggestions such as adding the "Set error creating an image of drive c +"rc=112" Image Folder" / "Set Image Name" into the Task Sequence, but it solved nothing. I am running Windows 7 Professional x64 and capturing from a server running MDT 2010. Would there be anything else that would cause this? Edited by Rick Castello Wednesday, June 13, 2012 9:31 PM More information Wednesday, June 13, 2012 9:28 PM Reply | Quote Answers 0 Sign in to vote If you look at the command line that it's attempting to run i.e. About to run command: cmd /c ""C:\WINDOWS\SYSTEM32\imagex.exe" /capture /compress maximum C: "\.wim" "201206141609CDrive" >> C:\MININT\SMSOSD\OSDLOGS\ZTIBackup_imagex.log 2>&1" You will see the file name it's trying to back up to is "\.wim". This of course isn't a valid backup file. I would suggest adding the following variables in to your customsettings.ini ComputerBackupLocation=%deployroot%\Captures BackupFile=MyFile.wim (change this to suit) Marked as an
- System zarządzania relacjami z klientem File/Email Archiving Installed Symantec Enterprise Vault for File Server and Email Archiving Upgrade Quickbooks 2010 to Quickbooks 2013 Upgrade from Quickbooks 2010 to Quickbooks 2013 and utilize the mdt rc=13 server database manager. TECHNOLOGY IN THIS DISCUSSION Microsoft 491311 Followers Follow Microsoft Windows Server 2012
Ztibackup Rc=13
Microsoft Windows 7 Microsoft Depl...t Toolkit 2013 Microsoft Depl... 2012 Update 1 VMware Project Join the Community! Creating your
Zti Error Non-zero Return Code By Ztibackup, Rc=5
account only takes a few minutes. Join Now I am getting a ZTI ERROR - Non- zero return code by ZTIBackup, RC=2 when I try to capture an image from a VMware Workstation VM of Windows 7 x64. https://social.technet.microsoft.com/Forums/en-US/7f268390-303f-40e8-ab42-14226af94bc7/error-creating-an-image-of-drive-c-rc-2?forum=mdt This image is not on the domain, has a local administrator account. Any ideas? Thanks! Tags: Microsoft Deployment Toolkit 2013Review it: (9) Reply Subscribe RELATED TOPICS: MDT End Error Odd Error in MDT MDT error   16 Replies Ghost Chili OP ErikN Mar 7, 2014 at 1:36 UTC The "windows cannot find the file specified error" may suggest that the local administrator account in your VM does not have write access to your image https://community.spiceworks.com/topic/454901-microsoft-mdt-zti-error target share. Also, I haven't captured any images from VMW Workstation, but when I capture my images, I do it from within Windows by browsing to my MDT share and running the LiteTouch.vbs script and not using the WinPE interface in your screenshot. 0 Sonora OP Nathan4783 Mar 7, 2014 at 1:40 UTC Thanks for the quick response, I am new to this. I started the capture process just like you described, it rebooted my VM and launched MDT and then I got the screen above. I will look into the account issue. thanks! 0 Tabasco OP J500 Mar 7, 2014 at 2:18 UTC You need to start the capture from within Windows. Go to the "Scripts" folder on your deployment share and select the "LiteTouch.vbs" script. Then select your Capture TS. Example: \\ServerName\DeploymentShare\Scripts\LiteTouch.vbs 2 Tabasco OP J500 Mar 7, 2014 at 2:38 UTC Sorry, didn't refresh before replying. Some things to check: What version of MDT are you running? Have you upgraded recently? Did you check both NTFS and the Share permissions? While on that error screen, if you press F8 and in the command window, can you access the Deployment Share by UNC? By IP? Is there, by any chance, already a WIM in the capture folder with the same name? Edited for readabilit
FailureThis topic has been locked. 9 replies Latest Post - 2010-12-01T19:18:45Z by JackCoates91 Display:ConversationsBy Date 1-10 of 10 Previous Next SirFixAlot91 270004W1SJ 9 Posts Pinned topic Image Capture Failure 2010-11-24T17:58:12Z | Tags: Answered question This question https://www.ibm.com/developerworks/community/forums/html/topic?id=77777777-0000-0000-0000-000014764140 has been answered. Unanswered question This question has not been answered yet. I am attempting to capture an image for the first time and it is failing at the first step of http://www.techtalkz.com/windows-deployment/408841-error-creating-image-drive-x-rc-2-a.html four: "Failed Create Image Info File " Anyone know what the issue may be or how I can find out? Thanks, Dan JackCoates91 270004W1KK 77 Posts Re: Image Capture Failure 2010-11-25T01:12:53Z error creating This is the accepted answer. This is the accepted answer. Hi Dan, double-check your credentials to the share. SirFixAlot91 270004W1SJ 9 Posts Re: Image Capture Failure 2010-11-29T13:41:31Z This is the accepted answer. This is the accepted answer. Hey Jack, I checked and verified that I am using the correct user account and credentials for a Domain account we created for this error creating an task and that the account has full access to the share. I also turned off the firewall on the relay hosting the repository, but I am still seeing the capture fail. One side question I have is that in the BigFix OS Deployment instructions says the target capture computer should be a virtual machine rather than a physical machine (page 16). I wasn’t sure if this was correct or a typo, but in our instance I am attempting to capture from a physical system. If this is the reason for the failure please let me know. Thanks, Dan JackCoates91 270004W1KK 77 Posts Re: Image Capture Failure 2010-11-29T17:57:47Z This is the accepted answer. This is the accepted answer. Hi Dan, okay, next step is to check your PE drivers. Here's a forum post on reading MDT logs: http://forum.bigfix.com/viewtopic.php?pid=25864 But you probably just need to hit F8 on the target to get a terminal and then try to ping the relay. On the virtual vs. physical thing, it's not a typo. MDT sysprep's the machine and can be destructive (particularly with Win7's aggressive stance on key validity). We're reco
Community Community Links Social Groups Pictures & Albums Members List Go to Page... Error Creating Image of Drive X: RC=2 Windows Deployment View First Unread Thread Tools Display Modes 25-01-2008, 10:30 AM #1 Rick Gates Guest Posts: n/a Error Creating Image of Drive X: RC=2 We are using the Computer backup from BDD 2007 and have the error RC=2 come up on laptop computers, all of our Desktop computers have always completed the Computer Backup WIM file properly. Is this a known issue with ImageX? Is there a later version or hotfix available? -- Rick Gates Sponsored Links 25-01-2008, 10:30 AM #2 greatbarrier86 Guest Posts: n/a RE: Error Creating Image of Drive X: RC=2 Rick, I cant explain why it works on desktops, but if you are in Windows PE, drive X is the RAM disk. I dont think you can image the ram disk. "Rick Gates" wrote: > We are using the Computer backup from BDD 2007 and have the error RC=2 come > up on laptop computers, all of our Desktop computers have always completed > the Computer Backup WIM file properly. > > Is this a known issue with ImageX? Is there a later version or hotfix > available? > -- > Rick Gates 25-01-2008, 10:30 AM #3 greatbarrier86 Guest Posts: n/a RE: Error Creating Image of Drive X: RC=2 Rick, I cant explain why it works on desktops, but if you are in Windows PE, drive X is the RAM disk. I dont think you can image the ram disk. "Rick Gates" wrote: > We are using the Computer backup from BDD 2007 and have the error RC=2 come > up on laptop computers, all of our Desktop computers have always completed > the Computer Backup WIM file properly. > > Is this a known issue with ImageX? Is there a later version or hotfix > available? > -- > Rick Gates 26-01-2008, 08:51 AM #4 Rick Gates Guest Posts: n/a RE: Error Creating Image of Drive X: RC=2 I should have expalin my environment is SMS/OSD package and so WINPE runs off the hard drive, that is why the X: drive is the drive to backup. -- Rick Gates "greatbarrier86" wrote: > Rick, > > I cant explain why it works on desktops, but if you are in Windows PE, drive > X is the RAM disk. I dont think you can image the ram disk. > > "Rick Gates" wrote: > > > We are using the Computer backup from BDD 2007 and have the error RC=2 come > > up on laptop computers, all of our Desktop computers have always completed > > the Computer Backup WIM file properly. > > > > Is this a known issue with ImageX? Is there a later version or hotfix > > available? > > -- > > Rick Gates 28-01-2008, 05:33 PM #5 Alex Ignatenko Guest Posts: n/a Re: Error Creating Image of Drive X: RC=2 Check if you already have a WIM file on drive X:. If so try to rename