ZENworks Imaging Driver Jan 2014 on SLES10 SP4

Hi,
I have a new type of Dell laptop (E5440) which cannot find the ZENworks repository.
The laptop finds the wireless driver instead of the LAN driver.
We are running ZENworks 11.2 without any patches and now want to apply the imaging updates:
https://download.novell.com/Download...d=oOaONfBNtCg~
But on the page it states SLES 11.. Windows 2003/2008, Novell Open Enterprise Server 2, SUSE LINUX Enterprise Server 11
We are running SLES10 SP4 can I install it?
Also in the readme there is something about Kernel Version: 3.0.76-0.11-default , will this work on my SLES 10 SP4?
Will the imaging update work on my ZENworks 11.2 unpatched system?
Kr,
Joeri

jfeyen Wrote in message:
> I have a new type of Dell laptop (E5440) which cannot find the ZENworks
> repository.
> The laptop finds the wireless driver instead of the LAN driver.
> We are running ZENworks 11.2 without any patches and now want to apply
> the imaging updates:
> https://download.novell.com/Download...d=oOaONfBNtCg~
>
> But on the page it states SLES 11.. Windows 2003/2008, Novell Open
> Enterprise Server 2, SUSE LINUX Enterprise Server 11
> We are running SLES10 SP4 can I install it?
Yes - I'm not sure why SLES10 isn't listed but it should be.
> Also in the readme there is something about Kernel Version:
> 3.0.76-0.11-default , will this work on my SLES 10 SP4?
The kernel version relates to the Imaging files not the host OS.
> Will the imaging update work on my ZENworks 11.2 unpatched system?
So yes it will work although I'm curious why you haven't patched
your ZENworks 11.2 system, at least with an 11.2.x update as
those updates are released for a reason.
HTH.
Simon
Novell Knowledge Partner
----Android NewsGroup Reader----
http://www.piaohong.tk/newsgroup

Similar Messages

  • Jan 2014 Imaging driver update issues

    I upgraded my ZCM Primary server from 11.2.2 to 11.2.4 over the weekend. Today I downloaded the Jan 2014 Imaging Driver update from the 11.2.4 patches page. I downloaded the zenworks11.2.4_MU1_Jan14 that said it was for 11.2.4 and 11.2.4 MU1. I followed the readme.txt file that says to run the imaging_driver_update.bat file. I ran this and I get:
    "Applying wrong imagin driver updates........Exiting driver update."
    Does anyone have any solutions to get this fixed up? If I go to %zenworks_home%\share\preboot\update and look at the ZUpdate.sig file it shows 112303 for the [zen_client_version] If I go into the ZCC management page and look under the primary server all of the version show correct as being 11.2.4.
    Thanks for any information you can give. I also cannot PXE boot at this time as well. It gets through PXE fine and I choose "Start Zenworks Imaging Maintenance" from the Imaging menu screen and then it starts loading but then pops up "cannot connect to Zenworks repository" or something like that. I don't have it right in front of me now.
    Thanks for any help.
    Andrew
    Network Administrator
    West York Area School District

    Marceldejager,
    > Anyone any idea's?
    yes - read the screen when you go to the November Update you are redirected to the Monthly Update, sure - but at the top, with a bright yellow background are the words
    "You have been automatically redirected to this patch because it supercedes the patch you originally requested. The patch you originally requested is still downloadable, click here to download it instead of this newer patch."
    if you click on the link it takes you to the patch you want...
    Shaun Pond (now working for ENGL)
    newly reminted as a Knowledge Professional

  • ZCM 11.2.3a Jan 2014 driver updates

    Hi there
    Since applying the Jan 2014 driver updates one of our images downloads and fails to boot.
    File \Windows\System32\winload.exe
    Stauts 0xc000000f
    The image size is 86 Gig.
    Does anyone know if there is a image size limit.
    Switching back to the previous driver set and there are no problems, but we need to support new hardware so need the Jan 2014 drivers.
    Thanks
    Mark

    Originally Posted by markvh
    Hi there
    Since applying the Jan 2014 driver updates one of our images downloads and fails to boot.
    File \Windows\System32\winload.exe
    Stauts 0xc000000f
    The image size is 86 Gig.
    Does anyone know if there is a image size limit.
    Switching back to the previous driver set and there are no problems, but we need to support new hardware so need the Jan 2014 drivers.
    Thanks
    Mark
    Hi Mark,
    I know you have an SR open, but I'm also curious if you also applied the latest tntfs.ko driver?
    @Anders: is there some more detail to what the symptoms are of that found defect and in which situations it might occur?
    Cheers,
    Willem

  • PS CC (since JAN 2014 update) Layer-mask editing causes hangs/crashes

    ONLY since JAN 2014 update, PS CC has been hanging/crashing when I paint/edit a layer mask. All may be well at first (or not), but suddenly the display of the mask (or mask overlay on the layer itself, as shown when hitting backslash key) is not shown in full but renders in s-l-o-w-l-y in rectilinear pieces <snapshot below was taken before video card upgraded but is still typical of what I mean>. When I view Windows' Task Manager for PS, I see my CPUs are each working at their upper limits (up to 80+-90+%), varying only by a few points, over a VERY long time... which could be MANY minutes. OR the System has decided PS is Not Responding.
    In any case, whenever this happens, it means in all practicality PS CC is not working, so I either kill it or it's crashed.
    Now, here's the thing: that VERY file, can immediately be opened in PS CS6 (which I have fortunately kept installed on my computer), and the mask will be as I thought it should be, and I can edit it as I always could, just fine! So it's obviously a PS CC thing, and I do NOT recall this happening prior to the JAN update. It is still a problem after the two subsequent updates.
    I have not been able to determine the specific instances when this happens, as it seems to happen whenever I am editing a mask, no matter what size/softness/color brush, what magnification, what view mode, many or few layers, big or small file, etc.
    I did upgrade my NVIDIA card (from GeForce GTX 260 [with current driver] to GTX660), just in case it was a factor (maybe kept it from crashing as fast? hard to tell... but it's still an unworkable problem). You can see from my Sys Info shown here from the PS CC Help menu  that it should be more than sufficient for any PS CC task, and it's running the latest driver:
    Adobe Photoshop Version: 14.2.1 (14.2.1 20140207.r.570 2014/02/07:23:00:00) x64
    Operating System: Windows 7 64-bit
    Version: 6.1 Service Pack 1
    System architecture: Intel CPU Family:6, Model:14, Stepping:5 with MMX, SSE Integer, SSE FP, SSE2, SSE3, SSE4.1, SSE4.2
    Physical processor count: 4
    Processor speed: 2664 MHz
    Built-in memory: 16379 MB
    Free memory: 12453 MB
    Memory available to Photoshop: 14697 MB
    Memory used by Photoshop: 60 %
    Image tile size: 1024K
    Image cache levels: 4
    Font Preview: Medium
    TextComposer: Latin
    Display: 1
    Display Bounds: top=0, left=0, bottom=1200, right=1920
    OpenGL Drawing: Enabled.
    OpenGL Allow Old GPUs: Not Detected.
    OpenGL Drawing Mode: Advanced
    OpenGL Allow Normal Mode: True.
    OpenGL Allow Advanced Mode: True.
    AIFCoreInitialized=1
    AIFOGLInitialized=1
    OGLContextCreated=1
    NumGPUs=1
    gpu[0].OGLVersion="3.0"
    gpu[0].MemoryMB=2048
    gpu[0].RectTextureSize=16384
    gpu[0].Renderer="GeForce GTX 660/PCIe/SSE2"
    gpu[0].RendererID=4544
    gpu[0].Vendor="NVIDIA Corporation"
    gpu[0].VendorID=4318
    gpu[0].HasNPOTSupport=1
    gpu[0].DriverVersion="9.18.13.3221"
    gpu[0].Driver="nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um"
    gpu[0].DriverDate="20131219000000.000000-000"
    gpu[0].CompileProgramGLSL=1
    gpu[0].TestFrameBuffer=1
    gpu[0].OCLPresent=1
    gpu[0].OCLVersion="1.1"
    gpu[0].CUDASupported=1
    gpu[0].CUDAVersion="6.0.1"
    gpu[0].OCLBandwidth=1.16816e+011
    gpu[0].glGetString[GL_SHADING_LANGUAGE_VERSION]="4.40 NVIDIA via Cg compiler"
    gpu[0].glGetProgramivARB[GL_FRAGMENT_PROGRAM_ARB][GL_MAX_PROGRAM_INSTRUCTIONS_ARB]=[16384]
    gpu[0].glGetIntegerv[GL_MAX_TEXTURE_UNITS]=[4]
    gpu[0].glGetIntegerv[GL_MAX_COMBINED_TEXTURE_IMAGE_UNITS]=[192]
    gpu[0].glGetIntegerv[GL_MAX_VERTEX_TEXTURE_IMAGE_UNITS]=[32]
    gpu[0].glGetIntegerv[GL_MAX_TEXTURE_IMAGE_UNITS]=[32]
    gpu[0].glGetIntegerv[GL_MAX_DRAW_BUFFERS]=[8]
    gpu[0].glGetIntegerv[GL_MAX_VERTEX_UNIFORM_COMPONENTS]=[4096]
    gpu[0].glGetIntegerv[GL_MAX_FRAGMENT_UNIFORM_COMPONENTS]=[2048]
    gpu[0].glGetIntegerv[GL_MAX_VARYING_FLOATS]=[124]
    gpu[0].glGetIntegerv[GL_MAX_VERTEX_ATTRIBS]=[16]
    gpu[0].extension[AIF::OGL::GL_ARB_VERTEX_PROGRAM]=1
    gpu[0].extension[AIF::OGL::GL_ARB_FRAGMENT_PROGRAM]=1
    gpu[0].extension[AIF::OGL::GL_ARB_VERTEX_SHADER]=1
    gpu[0].extension[AIF::OGL::GL_ARB_FRAGMENT_SHADER]=1
    gpu[0].extension[AIF::OGL::GL_EXT_FRAMEBUFFER_OBJECT]=1
    gpu[0].extension[AIF::OGL::GL_ARB_TEXTURE_RECTANGLE]=1
    gpu[0].extension[AIF::OGL::GL_ARB_TEXTURE_FLOAT]
    I work on digital-photography files, and use a layer mask in almost every file, so this relatively-recent bug is a big PITA, having to switch back and forth between CS6 and CC!
    Until there's a fix... is there a way to roll-back my PS CC version to BEFORE the JAN 15, 2014 update?

    I am not qualified to comment on technical issues; I'm just a user whose son in IT is my 'technical support department.' (But he's not much of a PS user.)
    I'm pretty sure, however, that all my Prefs were set to the same things BEFORE the Jan 16, 2014 PS CC update as after (unless the update itself changed something I was unaware of... the settings APPEARED to be the same but I can't easily locate my notes of what my Prefs were from long ago).
    And they were the same as the PS CS6 I have had installed on this same system for a very long time, with older video card with older driver, with newer driver; newer video card with newest driver, etc. Yet after that CC update, CC has not (until this workaround) worked re 'the masking bug' for me, yet CS6 has always worked just the same.
    So I conclude that the only variable (other than the video card upgrade I did in an attempt to solve this and of course those Windows auto-updates) in this scenario IS something to do with PS *CC*, and after Jan 16, 2014.
    As for restarting the machine vs. restarting PS, well, PS is the major player of my system, so when I shut that (and LR) down, I might as well 'clean things up' by Restarting. BTW, I am in the habit of closing and reopening PS (CC or CS6) whenever I finish with a file and load another, in order to get back some of that memory which PS never seems to want to let go. (This is not new to the latest versions, I think. My son says it's a 'memory hog'? ;-) ) I track its memory use in Windows' Task Manager and find that seems to let it 'refresh' itself. (See, I told you I'm not a technical person. ;-) ) But I do not think this has anything to do with the bug. Just a quirk of PS. Like when a tool goes all wonky (for example, its little icon becomes just a 'plus' sign even though the tool is still performing correctly, it's telling me, I think, that it would like to be restarted. And that makes it feel all better... I mean, tool icon reappears.)
    Anyway... it's up to Adobe to figure out IF and what may be wrong with PS CC -- it still doesn't work for me as I had it configured at first, and I think it should, right? -- and to fix that... PLEASE. SOON.

  • Zenworks imaging failed with error:200

    We just got new PC's and when I try to use ZENworks 6.5 to put my image
    on them, I get "ZENworks imaging failed with error:200"
    I have not been able to find anything in the KB for this.
    The PCs are Gateway E-4500D, ZENworks is 6.5 running on NetWare 6.5 SP 4a.
    TIA

    We are on SP2 and getting the error code: 200 error. The PC's are DC5100
    Small form factor. They have SATA drives. Some work and some get this
    error, reboot and then start the image restore, but never gets to the
    Pre-Formatting. Any ideas?
    > On Tue, 18 Jul 2006 14:32:30 GMT, Rhonda Richardson wrote:
    >
    > > No. We are on SP1. Sorry, forgot that part.
    >
    > could you try sp2?
    > --
    >
    > If you have already compiled drivers or have linux.2 please put them on
    > http://forge.novell.com/modules/xfmo...ect/?zfdimgdrv
    > Live BootCd and USB Disk from Mike Charles
    > http://forge.novell.com/modules/xfmod/project/?imagingx
    > eZie http://forge.novell.com/modules/xfmod/project/?ezie
    >
    > Marcus Breiden
    >
    > If you are asked to email me information please change -- to - in my e-mail
    > address.
    > The content of this mail is my private and personal opinion.
    > http://www.edu-magic.net

  • Applying wrong imaging driver updates ....

    ZENworks 11.3.2 Windows 2008 R2 SP1
    Last night we upgraded from ZENworks 11 SP3 to 11.3.2
    Applying Imaging Driver Update Feburary 2015 zenworks11.3.2_FRU1_Feb15.zip results in error message 'Applying wrong imaging driver update'
    ZUpdate.sig on primary server where running the update says ZEN_CLIENT_VERSION 112403 - timestamps on certain folders in the tftp directory and in the share\preboot\update folder though indicate that updates did take place at the time of the upgrade.
    Also a seconday server shows ZEN_CLIENT_VERSION 113200.
    'Assuming' that only the ZUpdate.sig file didn't update on the primary server - would it be safe to manually update the ZEN_CLIENT_VERSION and then run the imaging update?
    Thanks.

    Sector osh wrote:
    >
    > ZENworks 11.3.2 Windows 2008 R2 SP1
    >
    > Last night we upgraded from ZENworks 11 SP3 to 11.3.2
    >
    > Applying Imaging Driver Update Feburary 2015
    > zenworks11.3.2_FRU1_Feb15.zip results in error message 'Applying wrong
    > imaging driver update'
    >
    > ZUpdate.sig on primary server where running the update says
    > ZEN_CLIENT_VERSION 112403 - timestamps on certain folders in the tftp
    > directory and in the share\preboot\update folder though indicate that
    > updates did take place at the time of the upgrade.
    >
    > Also a seconday server shows ZEN_CLIENT_VERSION 113200.
    >
    > 'Assuming' that only the ZUpdate.sig file didn't update on the primary
    > server - would it be safe to manually update the ZEN_CLIENT_VERSION
    > and then run the imaging update?
    >
    > Thanks.
    Before doing so... I would run a ZDC, just to check - could me more
    than just this one file...
    Niels
    I have always liked... Cowabunga!
    If you find this post helpful, please show your appreciation by clicking
    on the star below.
    A member must be logged in before s/he can assign reputation points.

  • Lack of BT products since 20th Jan 2014 first day ...

    I ordered BT infinity2 (because I was told I could get infinity 2 speed) the first issue I found out that I can only get infinity 1.
    Along with the infinity I ordered the Phone line and TV on the 20th of Jan 2014, it is now the 31 Mar 2014 they have just got the pone line sorted, and when my wife said fine now fix the broadband and TV after he wascshown the issue my wife was told we need an engineer for the broadban and an other engineer for the TV. I was informed by BT engineering that they do not have enineers that can do all 3 products is this not a waste of resources and manpower.?
    besides all that I have been informed you cant cancel your BT contract untill the engineering team cant fix it, well I think 20th Jan until now is long enough and they still wont let me cancel. Myself and my wife have lost money by taking time off waitingvfor BT and some of them only to find that they havent been booked only a line test,I ask for an engineer for a Saturday and get told they dont work Saturdays,  that is funny how an enginer was at my house lsst weekend trying to fix the issue but only making it worse.
    Now I have now raised it with ombudsmen and an email to a UK team member to pass to Managment.
    If no reply tomorrow then it will be a letter to the CEO Gavin Paterson to be signed for on delivery

    Hi uktemplar,
    I'm really sorry to hear about the delay in getting your BT services activated, if you need any help with this please use the 'contact the mods' link in my forum profile under the 'about me' section to send in your details. You can find the link by clicking on my username.
    Thanks
    Neil
    BTCare Community Mod
    If we have asked you to email us with your details, please make sure you are logged in to the forum, otherwise you will not be able to see our ‘Contact Us’ link within our profiles.
    We are sorry but we are unable to deal with service/account queries via the private message(PM) function so please don't PM your account info, we need to deal with this via our email account :-)
    If someone answers your question correctly please let other members know by clicking on ’Mark as Accepted Solution’.

  • How do I get rid of the trial question on my Premier elements - which I purchased in Jan 2014

    I purchased my Adobe  Premier Elements in Jan 2014 - but now every time I use the program for editing and DVD burning it confronts me with a trial program (saying I have 2 days left on the trial) - how do I get rid of this trial Advertisement/program so that I can continue with the Premier Elements that I have already purchased?
         Thanks Brian Dearden@

    Mooivoel
    The answer would be expected to be....
    When you are given the Trial Message, click on the tab that says License The Product (or something like that) and then follow the instructions which will include inserting your purchased serial number.
    Have you been there and done that?
    ATR

  • ZENworks Imaging & Image Safe Data Problems

    Hi All,
    I'm in the preparation stage of a Windows 7 rollout to 4000 desktops. So far we've packaged up 200 applications/bundles and tested them against our image, everything on that front is fine.
    Our new ZENworks 11.3.2 server is being now being used to deploy our old Windows XP images (created in ZfD7), I'm using hardware rules to do this and it's working perfectly.
    When I use the hardware rules to deploy our new Windows 7 Image it will image once as expected. The PC then boots, a powershell script will build the hostname from the model and serial number, join the domain, install the ZCM agent and all looks good.
    The problem comes later when I try to image the machines again, we get "no work to do". After some reading I assume this is because of the Image Safe Data.
    I've tried a things so far but seem to be getting inconsistent results, basically each time I PXE the machine I want the machine to use the hardware rule to pull down the image.
    The only way I have found that seems to work,is to clear the Image Safe Data and delete the "Novell ZENworks Image-Safe Data Service" after the agent has been installed (as part of my build script). This seems like overkill to me and I'm sure I'm missing something. Help!
    Any help/guidance would be much appreciated!
    Thanks
    Carl

    Often the just use the ZCC to tell the device to Apply the Assigned Image and then upon reboot it will just apply the image.
    Some often script this with WOL so that every morning at 3am all of their lab devices will re-image.
    Also you don't want to "Delete" the ZISD Service, it is better to configure the Default ZCM Agent Settings to install that service if you do not want it.
    Otherwise, it will come back.
    You may also be able to make configure the ZCM Imaging Menu to Always show when PXE Booting.
    Then you could manually select an image to restore, regardless of the state of the ZENworks Image Safe Data.
    Originally Posted by carlhanson
    Thanks for the reply Craig.
    We haven't used an "Imaging Scripts", we've only used the "ZENworks Image" bundle category.
    It seems to be working the way we want now, although I'm still not entirely happy with the changes we've had to make...
    Added C:\Program Files\Novell\ZENworks\bin\preboot\ZISWIN.EXE -WIPE to the HKLM\..\Run registry key.
    Deleted the "Novell ZENworks Image-Safe Data Service" service.
    I'm not sure how this will effect client machines in the future when we update the Agent.
    When other customers reimage a machine which is already registered in ZENworks, do they push out images from the console?

  • I used adobe to convert a file in Jan 2014 and I've been charged $9.99 everymonth since. What is this??? How do I discontinue

    I used adobe to convert a file in Jan 2014 and I've been charged $9.99 everymonth since. What is this??? How do I discontinue

    Hi ocbeacher,
    To cancel a subscription, follow the instructions in this document Cancel your membership or subscription | Acrobat.com online services
    Best,
    Sara

  • ZCM 10.3.4 Imaging Driver Updates

    Hi,
    Does anyone know if there will continue to be imaging driver updates for ZCM 10.3.4 post Sept 2012?
    M.

    Hughesm,
    well of course we'd like you to upgrade! There's always http://www.novell.com/documentation/...a/ba69n4p.html
    but eventually you'll come across a problem that requires a new kernel...
    Shaun Pond

  • FAILURE ( 5640 ): FALSE: Verify File: \\SERVER\DeploymentShare\Operating Systems\Image 11-13-2014.wim\image.wim ERROR

    Guys,
    I need help with this error please. I have a WDS in building 13 and another 1 in building 31; Both servers have MDT 2013. At some point, both deployment shares were linked via MDT but I deleted that few days to solve some deployment share corruption in building
    31 WDS.
    Presently I have 2 32bit images (my 64bit images work fine) giving me the following MDT error in BUILDING 13 during the image deployment:
    FAILURE ( 5640 ): FALSE: Verify File: \\BUILDING 31 SERVER\DeploymentShare\Operating Systems\Image 11-13-2014.wim\image.wim
    Litetouch deployment failed, Return Code = -2147467259 0x80004005
    Failed to run the action: Install Operating System.
    Unknown error (Error:00001608; Source: Unknown)
    The Execution of the group (Install) has failed and the execution has been aborted. An action failed....
    Please note, BUILDING 13 deployment share is not linked to BUILDING 31 deployment share. I don't understand why this error is pointing to BUILDING 31 deployment share.
    \\BUILDING 31 SERVER\DeploymentShare\Operating Systems\Image 11-13-2014.wim\image.wim  has been removed. I need the task sequence to point to
    \\BUILDING 13 SERVER\DeploymentShare\Operating Systems\Image 11-13-2014.wim. BUILDING 13 deployment Share task sequences are pointing to
    \\BUILDING 13 SERVER\DeploymentShare as well as my CustomSettings.ini and Bootstrap.ini 
    1. I have diskpart and cleaned the disc, no luck.
    2. I have checked the Install action for both images task sequences and even verified each action on both tasks and cant find any error.
    3. I have re-generated the boot images and retyped
    \\BUILDING 13 SERVER\DeploymentShare on its CustomSettings.ini and Bootstrap.ini 
    4. I am in the process of copying Image 11-13-2014.wim back to
    \\BUILDING 31 SERVER\DeploymentShare\Operating Systems BUT again I don't understand why these task sequences are pointing to building 31. If this step doesn't work, I will restore both images from a backup and re-added them to building 13 MDT.
    But I don't think these steps are the solution.I am out of ideas here...

    I disabled McAfee AV, moved images boot files to a different location, regenerate boot images files in MDT, update deployment share, re-add boot files to WDS & refresh WDS. This works for me.

  • Decompression error's with Zenworks Imaging v6.5

    As part of our re imaging process, policy requires us to backup all
    workstations before re imaging. this often results in images ~25GB in size.
    (I am aware that it is not good practice to save data locally and ideally
    backup images should not be huge. Unfortunately due to policy this is
    unavoidable.)
    ZENworks imaging works great, except that occasionally individual files
    cannot be extracted from the image.
    When i try to extract a file in the above situation i am prompted with the
    following error:
    "A decompression error occured while attempting to extract the file from
    the image (-112). This file may not be extracted."
    In the past i have noted that the file in question tends to be quite large,
    (280MB) and is compressed in a fairly large image, ~20GB.
    Have checked on the original PC and the file is intact and working fine.
    When i backup the machine via Ghost the file is able to be extracted fine.
    Any help on this topic would be great as its difficult to test individual
    files and once the PC has been re imaged, if a file is corrupt in the
    image, it is impossible to retrieve.
    Cheers, Leon

    Is the file compressed using NTFS compression?
    It may be colored blue if you look at it in Windows Explorer.
    [email protected] wrote:
    > As part of our re imaging process, policy requires us to backup all
    > workstations before re imaging. this often results in images ~25GB in size.
    > (I am aware that it is not good practice to save data locally and ideally
    > backup images should not be huge. Unfortunately due to policy this is
    > unavoidable.)
    > ZENworks imaging works great, except that occasionally individual files
    > cannot be extracted from the image.
    >
    > When i try to extract a file in the above situation i am prompted with the
    > following error:
    >
    > "A decompression error occured while attempting to extract the file from
    > the image (-112). This file may not be extracted."
    >
    > In the past i have noted that the file in question tends to be quite large,
    > (280MB) and is compressed in a fairly large image, ~20GB.
    >
    > Have checked on the original PC and the file is intact and working fine.
    > When i backup the machine via Ghost the file is able to be extracted fine.
    >
    > Any help on this topic would be great as its difficult to test individual
    > files and once the PC has been re imaged, if a file is corrupt in the
    > image, it is impossible to retrieve.
    >
    > Cheers, Leon
    Jeremy Mlazovsky
    Senior System Engineer - Enterprise Desktop
    UDit-Central Hardware Systems & Network Storage
    University of Dayton
    http://forge.novell.com/modules/xfmod/project/?udimage
    http://vmpconfig.sourceforge.net/
    http://regeditpe.sourceforge.net

  • ZENworks Imaging Loop

    Sorry for posting again, but here is some more information, as well as some extra things we have tried.
    Hi,
    The screen results with this exit code after the workstation has been imaged, prior to booting back into PXE and then re-imaging, along with completion and the same message.
    ================================================== ==================
    Novell ZENworks Imaging Engine v10.2.0.0
    Copyright 1999-2009, Novell, Inc.
    All rights reserved.
    Imaging operation(s) assigned by 10.0.0.21
    Elapsed time: 12:48
    No more jobs to be done in policy
    ZENworks imaging failed with error: 52.
    Novell ZENworks SID changer for linux
    Version 10.2.0.0 Copyright 2007 - 2009
    Exiting: Computer has not been recently imaged
    ================================================== ==================
    The above message occurs (and this happens to other Laptops & PCs) after the machine has been imaged, but we are still having the computer re-imaging itself, it is in a constant loop.
    We were running Zenworks 7SP1 IR4. Last week we loaded Zenworks 7SP1 SR4.
    My manager has rolled back to IR4, but no change, as we have computers constantly re-imaging over and over in a loop.
    I have tried deleting the workstation object (name) from within ConsoleOne, and still the problem occurs. I have also made sure there are no add-on images attached to the imaging.
    Notes:
    Now, whenever we image a PC, the imaging process appears to finish, but we get an error: "Zenworks Imaging failed with Error:52"
    The system then reboots and starts the process again. If you look at the workstation properties, the Zenworks Image tickbox has not cleared, and hence the restart of the imaging.
    I found that Zenworks error 52 is: "52 - No partition type given when asked to create a part". I don't know why it would be saying that. (It is also possible that this message has always been there, but we have never noticed it, as the process has always worked).
    I came across an article that suggests the "ZENworks agent on the workstation has to be the same version as the ZENworks snap-ins in ConsoleOne".
    We are using:
    ConsoleOne Version 1.3.6h
    ZENworks Desktop Management 7.0.1 = snap-ins for configuring policy settings
    ZENworks Desktop Management 7.0.1 = snap-ins for administering and managing software distributions
    If you have any ideas could you please let us know?
    Cheers and thanks,

    anthonywhill,
    It appears that in the past few days you have not received a response to your
    posting. That concerns us, and has triggered this automated reply.
    Has your problem been resolved? If not, you might try one of the following options:
    - Visit http://support.novell.com and search the knowledgebase and/or check all
    the other self support options and support programs available.
    - You could also try posting your message again. Make sure it is posted in the
    correct newsgroup. (http://forums.novell.com)
    Be sure to read the forum FAQ about what to expect in the way of responses:
    http://forums.novell.com/faq.php
    If this is a reply to a duplicate posting, please ignore and accept our apologies
    and rest assured we will issue a stern reprimand to our posting bot.
    Good luck!
    Your Novell Product Support Forums Team
    http://support.novell.com/forums/

  • Factory image drive d: is completely empty, Why?

    my factory image drive d: is completely empty, why i do not know. i did not delete the contents.What should I do to replace Information?

    As the drive:d is in encrypted hidden form.
    Kindly follow the instruction to check if recovery partition is working or not.
    -turn off the system.
    -as soon as you turn on the system, keep tapping F11 button to load to recovery manager.
    -if it's loading into recovery means that the partition is fine and do not delete the partition.
    If it's not loading to recovery manager , contact customer support to order a set of rcd.
    Please respond with the result
    Thanks
    I am an HP Employee supporting Desktop and Notebook computers.

Maybe you are looking for