Imaging of WES

Similar Questions

• 1065984 error during installation or capture with sp4 4.6 HPDM

  Hello

  Yesterday, I did the update to sp3 HPDM 4.5 to 4.6 sp4.

  Now, I can not install image of wes or capture on my computer thinclient t5740e.

  Can I install the update agent, the agent is the last (4.6.3660.21244).

  This newspaper to install and capture (with the french):

  Install:

  2014-11-13 14:08 mapping of the repository to: master repository
  2014-11-13 14:08 sent the job to the managed devices management gateway
  2014-11-13 14:08:04 the task has been retrieved by the agent.
  2014-11-13 14:09:09 [error code: {0}] [Module: {1}] [category: {2}]
  2014-11-13 14:09:09 [error details]: \Ndm\branches\Release_4.6.4\Source\Cpp\Agents\Core\Task\wins\ImageTask_XPE.cpp@286: cannot download the image customer kit.
  \Ndm\branches\Release_4.6.4\Source\Cpp\Agents\Core\Task\common\ImageCommon.cpp@601: cannot download the image map file, file name: toolsConfig.xml
  \Ndm\branches\Release_4.6.4\Source\Cpp\Agents\Core\Task\common\ImageCommon.cpp@560: cannot download the mapping file.
  .\port_layer\ftpclient\fileclient.cpp@179: could not get the remote file LocalDir:C:\,RemoteDir:\\172.22.22.86\Repository/Repository/Tools/Imaging/Mapping,Name:toolsConfig.xml
  .\port_layer\ftpclient\ShareFolderClient.cpp@442: could not get the size of dir.
  .\port_layer\file_io\dirfuncs.cpp@845: failed to get the data from the file.
  .\port_layer\file_io\filefuncs.cpp@86: could not get the data of the file & colon;\\172.22.22.86\Repository/Repository/Tools/Imaging/Mapping\toolsConfig.xml
  .\port_layer\file_io\filefuncs.cpp@84: the specified path is not found.
  2014-11-13 14:09:09 failed to run the common task.

  Capture:

  2014-11-13 16:21:43 sent the job to the managed devices management gateway
  2014-11-13 16:21:47 the task has been retrieved by the agent.
  2014-11-13 16:22:51 [code error: {0}] [Module: {1}] [category: {2}]
  2014-11-13 16:22:51 [error details]: \Ndm\branches\Release_4.6.4\Source\Cpp\Agents\Core\Task\wins\ImageTask_XPE.cpp@118: cannot download the customer kit.
  \Ndm\branches\Release_4.6.4\Source\Cpp\Agents\Core\Task\common\ImageCommon.cpp@601: cannot download the image map file, file name: toolsConfig.xml
  \Ndm\branches\Release_4.6.4\Source\Cpp\Agents\Core\Task\common\ImageCommon.cpp@560: cannot download the mapping file.
  .\port_layer\ftpclient\fileclient.cpp@179: could not get the remote file LocalDir:C:\,RemoteDir:\\172.22.22.86\Repository/Repository/Tools/Imaging/Mapping,Name:toolsConfig.xml
  .\port_layer\ftpclient\ShareFolderClient.cpp@442: could not get the size of dir.
  .\port_layer\file_io\dirfuncs.cpp@845: failed to get the data from the file.
  .\port_layer\file_io\filefuncs.cpp@86: could not get the data of the file & colon;\\172.22.22.86\Repository/Repository/Tools/Imaging/Mapping\toolsConfig.xml
  .\port_layer\file_io\filefuncs.cpp@84: the specified path is not found.
  2014-11-13 16:22:51 cannot run the common task.

  Please, help me! I don't know what I can do.

  Best regards.

  It seems that the shared folder was not well configured.

  Could you please download the controller.conf under masterrepository folder and take a screenshot of the master repository configuration dialog box?

• TC520: HPDM 4.7.3610.23043 - cannot deploy images... error message 1080320

  Hello world

  We have not deployed any image TC520 for a few months.  I tried for a few days now, and we get an error.

  Nothing has changed (as far as I can see) in the past months.

  Deposits are still there and can connect on the TEST page.

  The images are still there... and have not been changed.

  TC520 are the same machines TC520

  The HPDM and the client, the version numbers match...

  I can reboot/update etc customers... just imaging that is a failure

  So, fundamentally, nothing has changed.

  But when I deploy an image, I get

  Refusal to execute the task DeployImage.

  2016-08-15 16:20:44 [error details]: deploy the image by using the master repository repository.
  Failed to deploy T520_Vanilla_2k7.ibr/Repository/Images/T520_Vanilla.
  Cannot run the task DeployImage.
  Error code: 1080320, error Info:...... \Task\wins\ImageTask_XPE.cpp@392: cannot run the script to repack wes.
  .. \.. \Task\wins\ImageTask_XPE.cpp@2416: error running script to repack
  .. \.. \Task\wins\ImageTask_XPE.cpp@2414: run = - 200 process return code. Command = C:\repack\Wes7ImageTool\bin\ImageTool.exe f C:\repack\Wes7ImageTool\Config.ini

  Any ideas?

  TIA

  Craig

  I suggest that you use 4.7 SP2 or later version. From SP2, we use the PE of the DM repository instead of the local device.

  This should be able to resolve the problem that you are experiencing.

• T610: thin client, multi-imaging platform

  Hi all

  IV ' e hoping to put this in the right place and someone can help or point me in the right direction.

  I'm looking for information on Thin Clients and Device Manager (HPDM), specifically on best practices on building and image capture, cross-platform and imaging would be advantageous.

  I am currently using HPDM Imaging for my thin clients t5470 and t5470e, t610, t620.

  I'm looking for a few docuemntation on recommended Configuration of HP for Imaging. is it to make a "gold" image or it can be pre-determined by HPDM like Microsofts SCCM or WDT?
  
  It would be fantastic if I could get it down to a single Image of WES7 for most of my Thin Clients if possible.

  Thanks in advance.
  J

  HPDM provides no functionality of creating an image, tt just do capture and deploy.

  The factory image include all drivers are built by HP R & D WES, there should be no one who can help you, but as far as I know there is no document to save the steps in detail. I suggest that you raise a ticket to impact to HP for help.

  MDT can not be used to deploy the image provided by HP. When building the image, no matter it is an original image or Thinupdate captured image, HP has done little customization in/after imaging process. I don't think that MDT can identify and carry out even these customizations.

• Code error-301 when you deploy the image

  Hello
  I have a problem.

  I want to deploy an image from a client light t5740e to a client t610.

  I cloned successfully of the image to a folder as a file .ibr deposit.
  I also have an older version of the image as a file on a FTP repository .img.

  I can successfully deploy the image the FTP repository to a t610 client.
  The problem is that this image is obsolete and cannot be used.

  When tryng to deploy the image to a file repository shared, I get the following error code:
  2013-04-22 11:38:47 ErrorCode:-301, error information: the device of the faimly bios is not match the image.

  I also tried to create an image using HP ThinState Capture, but recevie the following error during startup:

  Inititializing... * ERROR * system has failed the OS image.

  After that, I downloaded the standard image on the HP site and created a USB key. Then I replaced the .ibr file, but it still gives me the same error as ThinState installation.

  Is there a way to bypass the repository of shared folder and clone the image to the FTP repository under a .img file and deploy it to the client t610?

  Or is it possible to bypass the BIOS checking when deploying the repository of shared folder?

  Assuming that the version HPDM is common (4.5 with SP2), there is an option in the task editor when applying the deployment to enable Cross-platform for Imaging.

  This is however strongly discouraged because the picture you shot of the t5470e will not have the necessary drivers for the t610. The original image on the web site of HP will have drivers for both, but the part of the RunOnce scripts at first start after imaging USB is clean the unnecessary drivers by the platform to maximize space on the device.

  However, you should be able to pull the image of 7th WES using the FTP browser component in menu HPDM model. This will generate a model that can be deployed to clients light t5740e both t610.

  One last thing to remember is to make sure that the agent is updated on the device target before deployment and then again after the deployment.

• HPDM 4.5 SP2 - unable to capture the image

  I installed HPDM 4.5 w/SP2 and have hurt captures an image of Smart zero of a HP T410 (I have not tired yet other thin clients). I did not save my old settings because I wanted to start from scratch because I didn't keep any of the old images in any case.  A test of the ftp protocol and shared folder filing came back successfully by using the repository Editor.

  Everything else seems to work very well as I am able to clone parameters and send a command to reboot successfully but when I try to capture and image, it fails with the following information.

  2013-05-22 09:17:15 sent special to the device management gateway

  2013-05-22 09:17:17 task has been retrieved by the Agent.

  2013-05-22 09:17:20 capture image to the master repository.

  2013-05-22 09:17:20 capture image to the master repository.

  2013-05-22 09:17:20 the common task cannot run.

  2013-05-22 09:17:20 the common task cannot run.

  2013-05-22 09:17:20 the common task cannot run.

  2013-05-22 09:17:20 the common task cannot run.

  The agent update task also fails and the underside of the log information.

  2013-05-22 09:43:16 reference card: master repository

  2013-05-22 09:43:16 sent special to the device management gateway

  2013-05-22 09:43:18 task has been retrieved by the Agent.

  2013-05-22 09:43:22 copy files using the master repository repository.

  2013-05-22 09:43:22 the common task cannot run.

  2013-05-22 09:43:22 ErrorCode: 14031022, detail of error: could not download the file (s).

  2013-05-22 09:43:22 the common task cannot run.

  2013-05-22 09:43:22 ErrorCode: 14031022, detail of error: could not download the file (s).

  2013-05-22 09:43:22 the common task cannot run.

  2013-05-22 09:43:22 the common task cannot run.

  I don't know there is a setting somewhere that I forgot, but not sure it is and was hoping someone could point me in the right direction.

  Yes, the shared folder is mainly used for WES units.
  Can you see something in the ftp log which leads to an error?
  With FileZilla FTP Server, you can see in real time what is happening.
  With IIS, etc., you will need to check the logs.

• Auto new imaging HP T610 problem

  I have a bunch of new T610s from HP that I need the image. I used one to create the environment I want, and I can manually copy this image to the HPDM, then manually deploy that image on a new (self discovered) thin client.

  When I add a "rule" for first Contact Rules:

  Name: Auto Image

  Filter set (all criteria, IP address contains 10.22 which is the first two parts of all our internal IP space, I really want to a filter that would say all/all) if I click on generate a list of devices, it shows all existing devices.

  Trigger: first Contact

  Operating system: HP WES/XPe

  Category: imagery

  : Model 20131118 rule (self created when I took the picture manually)

  Activated: ticks

  When I plug a new HP T610, it is automatically detected by HPDM (DHCP specifies the HPDM) and then proceeds to restart in a cycle, and never made the task of imagery.

  The HPDM log shows:

  Card to the master repository repository

  Special Envoy to the device management gateway

  Task has been retrieved by the Agent

  Task has been retrieved by the Agent

  Task has been retrieved by the Agent

  Task has been retrieved by the Agent

  Task has been retrieved by the Agent

  etc., until I cancel the job

  Reset the status of the task to cancelled

  Can someone tell what I could be doing wrong, or how I can make this work? Should I manually start a task image, is the "first time" works not properly, I have to narrow the filter to avoid 'already seen' devices somehow?

  Thanks for your suggestions.

  Thanks for your suggestion, I checked that the devices already come with the new version of the agent.

  I found/solved the problem, which I had changed the settings by default in:

  Tools-> Configuration-> task settings-> write filter, WOL and adjournment of the task

  I changed it to "run regardless of the State of the write filter.

  So obviously the thin client was sent to the statement to start the task of imaging, rebooted, then collected the statement again from the beginning etc... creation of the loop.

  Once I changed this back to the ' If write filter on restart to clean the overlay, to execute and to commit and then restart for commitment is taken into account ", everything works perfectly.

  Hope this helps someone else...

  Kind regards

  Adam

• Deploy the Wyse Image via PXE on WDS

  Hi I was wondering if there was an instruction manual / somewhere that explains the process of deploying an image of wyse by using a WDS PXE server? I was not able to find any useful material.

  For anyone interested, I found the solution. Thanks for the reply, but this isn't really the answer I was looking for. I know you guys have a statement to manage/Imaging Wyse with SCCM Clients, which is a windows product, so I was hoping you had a statement for their imagery strictly with WDS (Windows Deployment Services) via a PXE boot. Here's what I did:

  1 customize your wyse image, how you want.

  2. for the sysprep file, I decided to follow directions in the Wyse - guide SCCM Chapter 4, Phase 1, step 1 (you are free to try sysprep file of your own, I felt it was easier for the test links below)

  https://appservices.Wyse.com/supportdownload/Wes/Wyse_SCCM_WES7_Admin_Guide_AUG2013.PDF

  3. then, I created a USB bootable for Windows PE. For this I used a computer laptop Windows 7, WindowsAIK for Windows 7 and ImageX. Im not going to go through these steps, because there are many references on the web on how to do it.

  4. now that I had a bootable USB key, I went back to my Client light Wyse and captured the image by using ImageX. Once more, there are many examples on the web on how to do.

  5. my image newly captured a reason any had the boot.wim on it, I went to microsoft.com and download a trial WES7. Follow the instructions to retrieve / create an ISO. This iso Wes7 inside, you will find a file named boot.wim. Copy this file and the image of Wyse WIM of step 4 of your WDS server.

  6. you will need to add the network adapter driver in the boot.wim file, I have also added a keyboard driver (once again a google search will show you how to do this via the command prompt).

  7 Add the boot.wim and wyse.wim file to WDS. (If you want to apply an unattend.xml file, follow these steps now)

  8. start to PXE boot of your wyse client, when he mode WindowsPE and you get the part of disk partition, press SHIFT + F11 to bring up a command prompt and type the following (pressing ENTER after each line):

  DiskPart

  Select disk 0

  Clean

  Create Primary Partition

  Format quick fs = ntfs label = Windows

  Assign Letter = C

  assets

  output

  9. press F5 and it should show the newly partitioned drive, continue on as normal by selecting the image you want and start the installation.

  This will get your PXE boot and running. You can use an unattended.xml file to join the field of disk partitioning/customer automated, but I don't the have not yet created. Hope this helps someone else who has had this problem.

• AppAssure best practices for the storage of machine image

  I work in a regulated environment where our machines are validated before being put into service.  Once they are put in service, changes to the machines are controlled and executed by a process of change request.  We use AppAssure to back up critical computers and with the ' always on ' incremental backup, works very well for the restoration of level file/folder in the case where something is removed, moved, etc..

  Management process asks me to perform once a machine is validated, to take a picture of it and store the image further so that if there is a hardware failure, the validated image can be restored and the machine is essentially to it of original validated state.  In addition to having the image of the machine as soon as it is posted, I need to also back up the machine on a regular basis in order to restore files, folders, databases, etc. on this machine.

  So my question is how to achieve this with AppAssure?  My first thoughts are to perform the backup of the machine Base, then archive it, and then let the AppAssure to perform the scheduled backup.  If I need to restore the computer to the Base image, then I back the Archive and then do the restore.  Is this a feasible solution and practice?  If this isn't the case, please tell us the best way I could accomplish what I want to do.

  Thank you

  Hi ENCODuane,

  You can carry out the plan of action of the WES in the following way

  1. to protect the agent with the name "[Hostname\IP_Base]".

  2. take the base image.

  3 remove the protection agent, but let the recovery points

  4. After these steps, you will have recovery basis point for the agent in the section 'recovery only Points.

  5. go to the agent computer, open the registry and change the ID of the Agent (a sign of evolution will be enough).  HKEY_LOCAL_MACHINE\SOFTWARE\AppRecovery\Agent\AgentId\Id

  for example, of

  94887f95-f7ee-42eb-AC06-777d9dd8073f

  TO

  84887f95-f7ee-42eb-AC06-777d9dd8073f

  6. restart the agent service

  7. from this point core Dell-AppAssure will recognize machine as a different agent.

  8 protect the machine with the name "[Hostname\IP]".

  If after these steps, you'll Base image for the 'Recovery only Points' machine (with the name "[Hostname\IP_Base]" which will not be changed by the update rollup and transfers) and protected the machine with the name "[Hostname\IP]" where the transfers will be made based on configured policy.

• Where Image Ready?

  I use the suite CS3. I have older versions of the CS he wes Image Ready for animation. In CS3, it went. What can I use as equivalent to this in CS3 application.

  Adobe offers this article for those who lack ImageReady:

  Guide to the location of the features of ImageReady CS2 Adobe for Photoshop CS3

  http://kb2.Adobe.com/CPS/400/kb400899.html

• Problems with still images

  Hi all!

  Since upgrading to FCP 10.2.3, 80% of my images still in the movies and work, the other 20% weird color lines to this topic, see the image below.

  

  I tried to re - register and again add the media to the event, etc. and also deleted the files generated rendering library that did nothing.

  Thank you

  This means that your gpu is unable to manage these photos. Try to use the smallest size photos if possible. If you don't need to zoom in on them there is no need to use photos that are much larger than the size of the image. Tell us your details specific mac and os and fcpx version.

• Apple Watch (1st version) flashing background image

  I have a first generation of Apple Watch.  I recently did the upgrade to the new operating system for watches.  I have a picture as my background.  Since the update, when I turn my wrist to me, to "turn on" the face of the watch, it a little 'flash' thing she had ever done before.  It's a quick way, irruption of the image of the picture on my watch that then remains on the image.  Has anyone else seen/noticed does this?

  Hello

  The following steps may help:

  • Close the watch application, and then restart your iPhone and your watch:
    • To close the application shows on your iPhone, click twice on the Home button, and then drag upward on Watch app preview.
    • Close the two devices together, and then restart your iPhone first.
      • Restart your iPhone, iPad or iPod touch - Apple Support
      • Restart your Apple Watch - Apple Support
  • Disable the twinning and re - pair your watch:
    • The app shows on your iPhone takes a backup of your watch automatically when the disparity with the app choose to restore from backup during the whole upward. Most of the data and settings will be restored, with a few exceptions (for example cards Pay Apple, access code).
    • Cancel the twinning of your iPhone - Apple and Apple Watch Support
    • Set up your Apple Watch - Apple Support

• images don't "move with the text" correctly when I have several columns

  I use 2 columns, have been inserting images in my text and chose 'move with the text' but when I have to go back and fix something, or add text over the images all move and do not stay with the text.  They start on their knees and move to the other columns and will not stay with the text.  In my view, this has to do with the use of columns, does anyone have any suggestions?

  What version explicit pages (Pages: pages) and the Apple logo: about this Mac) operating system version are you using? There are different, a functional version of the Pages that are running on the current releases of OS X and guessing will not help you.

• MBP: monitor detected but no image except by VGA

  I have a MBP of Mid 2012 running latest El Capitan.

  When I connect to an external monitor, it is detected correctly in views (exact name, resolution, etc.), but the monitor doesn't detect any image from the portable computer. I tried the DVI - D and DisplayPort with various cables and monitors with the same result, but a picture appears if I connect to VGA. It started in the past week.

  The built-in display does not work normally.

  Looks like a hardware failure in the computer DisplayPort connector laptop, as the pins are worn or something?

  Any other ideas?

  Hi johngirvin,

  Thank you for using communities Support from Apple. Sorry to hear that you had these display problems with your MacBook Pro. Looks like you've been on the right track trying to solve this problem. If you continue to have problems, you can find the additional steps described in the following article useful, up to and including contacting Apple Support if necessary:
  

  Get help with graphical problems on the external displays connected to your Mac - Apple Support

  Concerning

• What are disk images and can they be removed

  In downloads, I have a lot of disk images containing memory - such as Chrome - beyond 1 GB.

  I can remove them? Does make a difference? What are doing?

  All the other tips to speed up my mac because it is really slow!

  Have just updated the OS to Sierra - & that made matters worse, not better!

  A disk image is a convenient way for a developer to package and deliver the program. Once you have copied the program in your Applications folder, there is no reason to keep. You can safely remove. Note: Make sure that you have copied the image program in your applications folder before deleting.