Is there a way to specify the order assigned driver packages will install?  I am trying to assign drivers for a panasonic toughbook, but the panasonic driver bundle package loses network connection when it installs.  Then other assigned driver packages do not install (intel proset, sierra wireless, usb3) because it does the panasonic driver first.

Applies to LANDESK Management Suite 9.0 SP4 and later

Issue

The following error occurs when booting into Windows PE:

WinPE boot error "resolving core server name (%mycoreserver%)........"

Cause

• This normally occurs when the ALL.REG file within the BOOT.WIM does not contain the Core Server name or it needs changed to FQDN.
• If CORENAME.TXT and ALL.REG get modified manually and a later patch, service pack, or upgrade updates the boot.wim or boot_x64.wim, the CORENAME.TXT and ALL.REG will need to be updated again.

Resolution

The following steps will be taken on the core server:

• Mount the .WIM files that are used to create the Windows PE boot environment
• Modify the CORENAME.TXT and ALL.REG files that are used to specify the core server name for Windows PE
• Commit the changes made to the .WIM files so that the boot.wim and boot_x64 .WIM files contain the changes made
• Update the PXE Representatives with the newly changed .WIM files

These steps follow:

1. Create a new directory you will eventually mount your 32-bit .WIM file to.   Example: C:\bootwim
2. Create a new directory you will eventually mount your 64-bit. WIM file to.   Example: C:\boot_x64wim)
3. From a command prompt change to the \Program Files (x86)\LANDESK\ManagementSuite\vboot directory.
4. Type the following command to mount the Boot.wim file:
   
   This will mount the 32-bit boot.wim file that contains the 32-bit Windows PE environment used with computers booting to a Legacy 32-bit bios.  This means it will open up the .wim image file and allow access to it through a directory.
   

   dism /mount-wim /wimfile:boot.wim /index:1 /mountdir:c:\bootwim

5. Type the following command to mount the boot_x64.wim file:
   
   This will mount  the 64-bit boot_x64.wim file that contains the 64-bit Windows PE environment used with computers booting to a UEFI bios.   
   

   dism /mount-wim /wimfile:boot_x64.wim /index:1 /mountdir:c:\boot_x64wim

6. Change to the Temp subdirectory under C:\bootwim\ you created in Step 1.
7. Save your changes to the CORENAME.TXT file.
   

   CORENAME.TXT will simply contain one line with the name of the core server.   This can be changed to FQDN or IP address to suit the needs of your environment.

8. Change to the WINDOWS\SYSTEM32  subdirectory under c:\bootwim and edit the file ALL.REG in Notepad or other text editor.
9. Modify the line that says "CoreServer"="[Corename]" and change the core name to FQDN or IP address as suits your needs.
10. Save your changes to the ALL.reg file.
11. Repeat steps 6-9 for the boot_x64.wim
    
    Now it is necessary to commit the changes made in the C:\bootwim and C:\boot_x64wim directories to save them into the .WIM files.  This is done by using the DISM (Deployment Image Servicing and Management) tool with the switch "/commit-wim" to save the changes to the images we mounted in steps 4 and 5. IMPORTANT: It is absolutely necessary to close all Explorer windows related to the bootwim mount directory before running the unmount commands. Failure to do so will cause your commit to fail due to files still being in use.
    
    
12. Type the following command to unmount the boot.wim and commit (save) the changes:
    

    dism /unmount-wim /mountdir:c:\bootwim /commit
    This will commit (or save) the changes to the boot.wim made in modifying the CORENAME.TXT and ALL.REG.

13. Type the following command to unmount the boot_x64.wim and commit (save) the changes:
    

    dism /unmount-wim /mountdir:c:\boot_x64wim /commit
    This will commit (or save) the changes to the boot_x64.wim made in modifying the CORENAME.TXT and ALL.REG

14. At this point it is necessary to re-deploy the PXE representatives, as the .WIM files reside on the PXE Representatives.  When the targeted devices do a network boot they are directed to their PXE representative for their subnet and download the associated .WIM file that will then be their Windows PE environment.  The following steps detail this.
15. In the LANDESK Management Suite console, go to the Distribution tool group and then go to the OS Deployment tool.
16. From the OS Deployment tool expand the "All Other Scripts" section.
17. Right-click "PXE Representative Deployment" and select "Schedule".
18. The "Scheduled Tasks" tool should open and the newly created task should be highlighted.
19. Add the PXE representatives to the task and start the task.
    
    Note: If you already have a PXE Representative Deployment task created, you can just re-use that one to re-push the PXE representative.
    
    

    If the BOOT.WIM and BOOT_X64.WIM files were updated by a patch, service pack or upgrade, these steps will need to be done again.

    
    
    
    
    
    

Prerequisite:

Before you can deploy image based partitions, you need to prepare the image file based partitions, To capture image based partitions , please refer to this article:

http://community.landesk.com/support/docs/DOC-30713

How do I create a deployment script?

a. Open the LDMS console. Click Tools > Distribution >OS Deployment

b. Right click on All OSD/Profile Migration Scripts and select a new script based on the imaging environment you will use.

c. Select deploy image. Give the script a name and a description.

d. Specify the credentials to be used

e. Specify the image information. If you will use LANDESK's imaging tools, choose LANDESK ImageW V2 for the Image type. Enter the UNC path where you will capture the image. For the path to the imaging application, use \\coreservername\ldmain\osd\imagew 2

Replace "coreservername" with the name of your core server. Replace "imagingtool" with imagew.exe (for Windows PE) or image.exe (for DOS).

f. Click save button to save the deploy image script

g. Right click on the OSD script and click advance edit

g. Click Use editor button

h. Copy and paste this line, and modify OSD script as below:

i. If using the PXE Boot Menu, it is necessary to drag the script from the scripts folder to the PXE Boot Menu folder under the PXE Boot Menu section. This places the script in the bootmenu.cfg file.

NOTE: It is advised that you use the "Image Type" of "LANDesk ImageW V2".   This will require the path to be entered for the image application in the last line of the script to reflect the correct path.  For version 9.5, it is "\\Coreservername\ldmain\osd\imagew 2\imagew.exe"

To open this screen select Tools | Distribution | PXE Boot Menu. Once this screen is open, drag the script to the PXE Boot Menu folder. After the script is copied to the PXE Boot Menu, click the Update button which refreshes the bootmenu.cfg file stored on the core.

i am trying to image through winpe provisioning for both LENOVO X240 AND HP 2570P , IT FAILS I DONT KNOW HOW TO FIGURE THIS OUT , THE OTHER IMAGE WORKS BUT THE DRIVERS DONT WORK .......I AM SCREWED , CAN SOME ONE HELP ME

We have been using HII with provisioning from 9.0(I believe it was SP2) to 9.5 and we haven't had any issues with drivers causing bluescreens. Last week we upgraded to 9.5 SP2 and now every Dell box we provision bluescreens on bootup right after the CTOS action. I started testing on a T3610 to try and sort out the issues and it looks like the bluescreen is being caused by the chipset drivers. These are the same drivers we have been using for long time with no issues. I tried updating them from Dell's driver cab files and the behavior stays the same. I talked with some LANDesk guys at Interchange and they indicated it was problem with my drivers as nothing has really changed with how HII assigns drivers, but the only thing that has change is upgrading to 9.5 SP2. When I search the community and find articles like this http://community.landesk.com/support/message/101688#101688 (9.5 SP1 - Best Practice HII 9.5SP1 for DELL Computers) I get the impression this is a known issue and doesn't look it has been fixed. Is anybody else having these issues or have suggestions on how to fix this?

Environment:

- LDMS 9.5 SP1

- Agent installed on Windows 7 64bit SP1

I have this case when I wanted to Deploy Profile using Provisioning, Local account always successfully restored, but not a domain account.

Every time this domain account login, on system tray always show a baloon that said "this is temporary account bla..bla..bla".

Already tried restart and then login again, always the same baloon poped out...and after the 3rd login attempt windows throw "The group policy client service failed the logon".

This is the steps that I do for testing, and the PC are already join domain and theres already a domain account set up:

1. Login using local account

2. Capture Profile using provisioning, this contains one local account and one domain account. (Success)

3. Restore windows to its original state with an empty local account profile.

4. Deploy Profiles using provisioning, the tasks sequence are all success.

5. Restart.

6. Login using local account, the delayed UMA windows appear and then automatically restart.

7. Login using local account and check whether the profile are restored correctly. it is restored correctly (success)

8. Logged off and then logged in using domain account.

9. The delayed UMA appears again and then automaticcaly restart.

10. Login using domain account, then the baloon pop up started appear.

11. Restart again, login using domain account, the baloon pop up appear again.

12. Restart again, login using domain account, then the account are locked out and show  "The group policy client service failed the logon".

Another behavior that I'm observed is, it seems like SMA creating a profile called TEMP on the C:\users folder

Any insight, solution or workaround are appreciated

Hi there,

I have an issue when multicasting OS images using PXE/WinPE. If I previously choose a MDR manually in the LDMS console for multicasting the OSD/PXE task, then the image deployment works all right as expected. But if instead there is not a previously manually selected MDR for the task then the multicast task fails as soon as it starts even a MDR shows as been selected in the interactive core server multicast task .

Moreover, if I choose manually a MDR for the PXE/WinPE OSD deployment task and when the selected MDR node starts receiving the OS image from the Core Server and simultaneously multicasting the OS image to the rest of the selected client nodes, if then I disconnect the current MDR node, then the process instead of selecting a new MDR by a initiated automatic election, the task fails and none of the other client nodes is selected as an alternate MDR.

Any ideas?    

We just upgraded from V9.5 to V9.5 SP2.  All of our software distribution actions involving .exe's no longer work.  We can use use software distribution outsde of provisioning and it works fine.  Any thoughts?

I am trying to image a HP t510 thin client using LANDesk and Image W.  I captured the image and send it back out to the thin client.  I followed the instructions in the link below.

HP Thin Client Management with LANDesk Management Suite 9.5

  When Windows goes to start up I receive the error below.

I noticed the errors below in the "setuperr.log."

According to the link below this is an issue with the second partition not being created.

Windows Embedded Stanard 7 - Sysprep Failure occurred while executing ewfcfg.dll,EwfSysprepSpecialize

With all that being said I have a few questions for the community:

• What is the best way to create multiple partitions with LANDesk?
• Has anyone found documentation on the imagew switches?

Hi

We install several software during the provisioning, one software needs a reboot after installation. So we put in the reboot action in the template. When we start the scheduled task from the template with 12 clients, 8 clients do the task successfully. The other four clients hang after the reboot action and do nothing (the provisioning agent do not start after the reboot). There are still a few actions pending, the task is active and after a few hours the task is failed.

Have someone an idea, what the problem is with the reboot or why the provisiong does not start after the reboot?

Thanks

I have been playing around with using locked templates to fire up provisioning on computes to keep the "all public templates" folder free from all the locked templates that are created when provisioning from non-locked templates.

When a tech provisioned from an unlocked template and had it fail, I would delete the locked template created in the "all public" folder and the tech would be able to relaunch the template without it trying to pick up from where it failed.

My question is, what is the best way to deal with failed provisioning tasks?  If I have the technicians launch a template from a locked one, the only things I will be able to delete from the database is the task that is created in the technician's "My tasks" folder and the device id in "All devices" from the network view in the console.

Also, is there a way to rename a locked template?  I'd like to have the template tree look a bit more clean than having a bunch of time stamped templates to choose from.

Thanks.

I have been fighting with this intermittent issue and spending way too much time on it.  It is maddening since it will fail 3 times in a row and then succeed without any modifications whatsoever on the same hardware. 

What is happening is that after the generalize pass of the sysprep run, it will install device drivers and then move onto applying system settings where it fail to parse the unattend.xml at C:\Windows\Panther saying the answer file is invalid.  Looking at the unattend file, it will be truncated at the line stated in the error message. 

I have tried injecting the unattend into the root of the drive, into C:\Windows\Panther with the same result.  I have put waits in the provisioning template after the inject to ensure that it is being written completely.  Looking at the unattend file before the generalize pass shows that the file is intact. Looking through the sysprep logs yeilds no clue as to what is happening.

I generated the unattend file with Windows Systems Image Manager and is attached below.  I am on LD 9.5 SP2 trying to provision Windows 7 Enterprise SP1 x64.

Anybody know what is happening to the unattend and any suggestions on making this more reliable?

Applies to LANDesk Management Suite 9.0 SP3 and newer

Issue

• Cannot right-click a provisioning template to schedule it.
• Schedule option is greyed out.
• Cannot schedule OSD scripts.
• Cannot create OSD scripts.
• Cannot select Windows when creating Provisioning Boot Media.
• Cannot select Windows PE for the Boot environment when creating a new provisioning template.

Cause

Installed a new Core Server using the existing Core Server database and the WAIK licensing information was not transferred properly.

Note:  The issue can also be caused by moving the existing LANDesk database to a new database server.

Resolution

1. Run the following SQL statement against the LANDesk database:
   
   update keyvalue set intvalue=0 where applicationname='WAIKLicenseAgreement'
   
   
2. Reopen the LANDesk Console and accept the license agreement.

Ok, so with the current OSD task, which was working up until yesterday, has started giving me grief. Tried to image 4 computers, 2 of which had the OS Deployment task fail right at the start of provisioning. Tried a couple more times, just because that seems to happen sometimes, which didn't help. I tried deleting the tasks, deleting the machines, starting over with bare-metal machine config, scheduled a new task, and now instead of automatically pulling up provisioning, I have to press F8 and select WINPE Provisioning (which has happened before.)

Next it prompts me for my credentials, which I enter, then it brings up the template list. All well and good, been down this road before. I select the appropriate template, and it can't seem to pull it down from the core server. Some searching suggest the Scheduler task on the core might not be running, but I restarted that task, to no avail. I looked into the provisioning.log and found the following

Anyone have any idea what might be going on?

Currently, our environment consists of a few subnets with pxe reps which we use for provisioning deployment.

However we are about to do a mass migration from WinXP to Win7.

So we will need all the computers in various subnets to be able to pxe boot into WinPE provisioning.

We will end up setting an option in DHCP to forward all pxe requests to the Landesk 9 server.

It works great for the few subnets where we have this deployed.

The question is, if there is a way to change the pxe menu if we have it set up that way?

My boss wants me to remove the other options that we rarely use.

Is that possible?

Hi,

I am having trouble installing the PXE representative.  Like many other posts I’ve read:

https://community.landesk.com/support/message/75035#75035

https://community.landesk.com/support/message/67341#67341

It says it installed successfully but in fact it has not.  I’ve also looked at this:

https://community.landesk.com/support/message/73264#73264

Here are some lines from the osdrep.log file on the machine I am trying to install the PXE rep on:

MSI (s) (D0:F0) [18:29:24:077]: Product: LANDesk(R) PXE Proxy -- Installation failed.

MSI (s) (D0:F0) [18:29:24:077]: Windows Installer installed the product. Product Name: LANDesk(R) PXE Proxy. Product Version: 1.0.4. Product Language: 1033. Manufacturer: LANDesk. Installation success or error status: 1603.

Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor.  Action _360D8BE7_4ED6_4312_B447_37B1A0861E4C, location: C:\Program Files (x86)\LANDesk\PXE\System\pxectrl.exe, command: /Install "/svcdir=C:\Program Files (x86)\LANDesk\PXE\System\\"

Action ended 18:29:23: InstallExecute. Return value 3.

Action ended 18:29:24: INSTALL. Return value 3.

Here is an entry in the event log is during the install

Failed to connect to server. Error: 0x800401F0

And another:

Product: LANDesk(R) PXE Proxy -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action _360D8BE7_4ED6_4312_B447_37B1A0861E4C, location: C:\Program Files (x86)\LANDesk\PXE\System\pxectrl.exe, command: /Install "/svcdir=C:\Program Files (x86)\LANDesk\PXE\System\\"

Here is the CJ-PXE Representative Deployment log file:

"Machine","CbaStatus","ExitCode","Duration","Begin","End","Command"

"PXEREP","OK",1605,0:00:00,6/2/2014 6:11:38 PM,6/2/2014 6:11:38 PM,"MsiExec.exe /q /X{F238CE99-6614-4072-9D20-1D2FA7ED951A}"

"PXEREP","OK",0,0:00:00,6/2/2014 6:11:39 PM,6/2/2014 6:11:39 PM,"C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\files\bootmenu.1, C:\Program Files (x86)\LANDesk\LDClient\bootmenu.1, TOREMOTE"

"PXEREP","OK",0,0:00:01,6/2/2014 6:11:40 PM,6/2/2014 6:11:41 PM,"C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\files\bstrap.0, C:\Program Files (x86)\LANDesk\LDClient\bstrap.0, TOREMOTE"

"PXEREP","OK",0,0:00:00,6/2/2014 6:11:42 PM,6/2/2014 6:11:42 PM,"C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\files\dosundi.1, C:\Program Files (x86)\LANDesk\LDClient\dosundi.1, TOREMOTE"

"PXEREP","OK",0,0:00:00,6/2/2014 6:11:43 PM,6/2/2014 6:11:43 PM,"C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\vboot\bootmenu.0, C:\Program Files (x86)\LANDesk\LDClient\bootmenu.0, TOREMOTE"

"PXEREP","OK",0,0:00:00,6/2/2014 6:11:44 PM,6/2/2014 6:11:44 PM,"C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\vboot\dosundi.0, C:\Program Files (x86)\LANDesk\LDClient\dosundi.0, TOREMOTE"

"PXEREP","OK",0,0:00:00,6/2/2014 6:11:45 PM,6/2/2014 6:11:45 PM,"C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\vboot\bcd.dat, C:\Program Files (x86)\LANDesk\LDClient\bcd, TOREMOTE"

"PXEREP","OK",0,0:00:00,6/2/2014 6:11:46 PM,6/2/2014 6:11:46 PM,"C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\vboot\bcd_x64.dat, C:\Program Files (x86)\LANDesk\LDClient\bcd_x64, TOREMOTE"

"PXEREP","OK",0,0:00:00,6/2/2014 6:11:48 PM,6/2/2014 6:11:48 PM,"C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\vboot\bcd_ia32.dat, C:\Program Files (x86)\LANDesk\LDClient\bcd_ia32, TOREMOTE"

"PXEREP","OK",0,0:00:00,6/2/2014 6:11:49 PM,6/2/2014 6:11:49 PM,"C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\vboot\boot.sdi, C:\Program Files (x86)\LANDesk\LDClient\boot.sdi, TOREMOTE"

"PXEREP","OK",0,0:00:02,6/2/2014 6:11:50 PM,6/2/2014 6:11:52 PM,"C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\vboot\boot.wim, C:\Program Files (x86)\LANDesk\LDClient\boot.wim, TOREMOTE"

"PXEREP","OK",0,0:00:02,6/2/2014 6:11:53 PM,6/2/2014 6:11:55 PM,"C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\vboot\boot_x64.wim, C:\Program Files (x86)\LANDesk\LDClient\boot_x64.wim, TOREMOTE"

"PXEREP","OK",0,0:00:00,6/2/2014 6:11:56 PM,6/2/2014 6:11:56 PM,"C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\vboot\bootx64.efi, C:\Program Files (x86)\LANDesk\LDClient\bootx64.0, TOREMOTE"

"PXEREP","OK",0,0:00:00,6/2/2014 6:11:57 PM,6/2/2014 6:11:57 PM,"C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\vboot\bootia32.efi, C:\Program Files (x86)\LANDesk\LDClient\bootia32.0, TOREMOTE"

"PXEREP","OK",0,0:00:00,6/2/2014 6:11:59 PM,6/2/2014 6:11:59 PM,"C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\vboot\bootmgr.exe, C:\Program Files (x86)\LANDesk\LDClient\bootmgr.exe, TOREMOTE"

"PXEREP","OK",0,0:00:00,6/2/2014 6:12:00 PM,6/2/2014 6:12:00 PM,"C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\vboot\pxeboot.0, C:\Program Files (x86)\LANDesk\LDClient\startrom.0, TOREMOTE"

"PXEREP","OK",1603,0:00:09,6/2/2014 6:12:01 PM,6/2/2014 6:12:10 PM,"<qt/>C:\Program Files (x86)\LANDesk\LDClient\sdclient.exe<qt/> /p="http://128.8.118.44/landesk/files/osdrep.msi" /msi /N /An /Ac /g="{F238CE99-6614-4072-9D20-1D2FA7ED951A}" /disableclientqueue"

"PXEREP","OK",0,0:00:50,6/2/2014 6:12:11 PM,6/2/2014 6:13:01 PM,"<qt/>C:\Program Files (x86)\LANDesk\LDClient\LDISCN32.EXE<qt/> /NTT=128.8.118.44:5007 /S="128.8.118.44" /F /SYNC /NOUI"

; "Job Complete","1 Done","0 Failed","0 Off","0 Unknown"

I’ve tried chasing down these various error logs but they quickly become a morass.

Hi,

I had provisioning working but sometime during the upgrade to 9.5 SP3 it seems to have broken.  I am now getting these TFTP errors:

PXE-T01: File not found

PXE-E3B: TFTP Error – File not found

PXE-M0F: Exiting Intel PXE ROM

I have the provisioning template (that used to work) scheduled. I create a device in ‘Bare Metal Servers’ schedule it, start it, and boot the system and get the errors above. When I use Sysinternals Process Monitor to see where it is looking for the file it is looking in ‘C:\Program Files (x86)\LANDesk\PXE\System\images’.  Indeed there is no startrom.0 there but I think it should be looking in a different directory like ‘C:\Program Files (x86)\LANDesk\PXE\System\images\x86pc\undi\provwin’ right?  I’ve messed around with PxeConfig.exe a little but I’m not sure how/when the magic happens for a device that is scheduled to do a provisioned install and what boot files it is supposed to get at what point.

I’ve removed and reinstalled the PXE representative (which is my core server, I know it’s a no no but it worked before) but it was not helpful. My core server is now listed twice in devices (once with just a hostname and once with FQDN).  Could this be the problem?  Should I do the PXE rep removal dance, remove both core servers, deploy the agent, and then deploy the PXE rep?

Thanks,

Brad

I successfully injected drivers for  HP ZBook 15 and 17 into core server but I am not able imaging them via PXE booting. I see it communicate with PXE rep and load files but it does not get IP. Here is excerpt of the error:

The operation completed successfully.

IP addresses: 127.0.0.1

Waiting for IP address…………………..

and then it stays like that for two minutes or so and then it says

Timed before acquiring an IP address.

Windows IP confifugration

The operation failed as no adapter is in the state permissible for this operation

and then it starts all over again

IP addresses: 127.0.0.1

Waiting for IP address………………

Please help me with this as I have very urgent request...

Thanks

I have a few questions about your product in regards to
capturing a Windows 7 image using the steps “How to Capture a Windows 7
image with OSD using Imagew.exe v2 in 9.0 SP2 & SP3 and 9.5” which can be found at this link How to Capture a Windows 7 image with OSD in LANDesk® Management Suite 9.5, 9.0 SP2 and SP3. I added the link that I used so that you can see what I have already
completed and the step that I’m getting stuck on and perhaps you can give me a
solution to this issue.

So the step that I’m having trouble with is the last step on
this document. Once I select the “OSD capture script
(Capture_Windows_7_Imagew)” at the end of this document I’m not seeing the
process that the last page shows (which is the progress of Creating Image).
Instead I see two or three command prompt windows that appear and disappear and
then I just see the LANDesk background only. I do not see the image in the last
step of this document. Any ideas what this could be from?

I have tried the different options for running SYSPREP.EXE
for the Image Capturing and still have had no luck.

Hi,

I working on provisioning and when I go to HII Driver Manager, I can not disable drivers or run the build library. When I build the library, I get a permission error on the drivers.db3. What permissions are needed to do this operations.

Thanks ahead of time for any information.