landesk自带的捕获工具，怎么可以只捕获\部署C盘的镜像？有脚本可以提供吗？
↧
imagew
↧
PXE boot fails to resolve core name when using provisioning template action to reboot into WinPE
LDMS 9.5
PXE boot fails to resolve core name when using provisioning template to reboot into WinPE (vboot)
ISSUE:
Schedule provisioning template with first action to reboot machine to WinPE (vboot) and start task.
WinPE loads and fails with error Could not resolve core server name.
WinPE Command:
X:\Windows\system32\wpeinit
X:\Windows\system32\wpeinit /unattend=x:\ldclient\setpeoptions.xml
X:\Windows\system32>\cba8\LDDrvLoad.exe
[LDDrvLoad]: This is not a valid folder name, cFileName = .
[LDDrvLoad]: This is not a valid folder name, cFileName = ..
[LDDrvLoad]: Driver Folder List is empty
[LDDrvLoad]: Fail to get Driver Inf File List
The command completed successfully.
X:\Windows\system32\reg import all.reg
The operation completed successfully.
The operation completed successfully.
.......
VBoot artition not found on disk
The operation completed successfully.
IP address xx.xx.xx.xx 127.0.0.127
resolving core server name (corename)......
Could not resolve core server name.
resolving core server name (corename)......
Could not resolve core server name.
Solution:
Manual F12 PXE boot uses the boot.wim from the PXE Representative. When you PXE boot using vboot, the PXE Rep will call the bootmedia.wim file from the core under Managementsuite\landesk\vboot. If the core name cannot be resolved you need to make sure both the boot.wim and bootmedia.wim on the Core have the FDQN on the corename.txt file and all.reg file.(Refer to Error: "resolving core server name (%mycoreserver%)" when booting into WinPE). If you make changes on the boot.wim, redeploy the PXE rep.
NOTE: Modifying the bootmedia.wim does not require redeployment to the PXE Rep.
↧
↧
LANDESK Support for Unattend.XML
Question:
I am attempting to use an Unattend.xml as part of my LANDESK Provisioning job.
What support does LANDESK offer for troubleshooting or customizing my unattend.xml?
Answer:
LANDESK provides a sample unattend.xml either on the LANDESK community or bundled with the product as a service to our customers to give them a starting point.
Customizing the UNATTEND.XML to cover the customer environment will be necessary in most cases.
Troubleshooting or customizing the UNATTEND.XML file is not covered within the scope of LANDESK Support.
It is recommended to use Microsoft Windows System Image Manager to create an UNATTEND.XML file.
For more information on the Microsoft Windows System Image Manager, refer to the following Microsoft Technet Article:
http://technet.microsoft.com/en-us/library/cc766347(v=ws.10).aspx
Microsoft documentation or contacting Microsoft support is advised for assistance with the UNATTEND.XML
See the following Microsoft article:
http://technet.microsoft.com/en-us/library/cc748874(v=ws.10).aspx
↧
Unable to setup template to filter out specific files when capturing the profile
Problem:
Trying to fine tune our Profile Captures. I have two issues.
1.) I am unable to filter out specific file types from the capture.
Even though I set specific filters for various file types such as *.wmv, *.avi, *.mp3, etc., these are still being captured.
2.) I am not able to find documentationt that lists all of the built-in variables that can be used in the configuration.
I know we can use the system variables like %username%, I also know there are built-in variables but I can not find a definitive list of what these varible names are.
Resolution:
There is no provision to do any filtering of files or folders that are in the desktop folder. If desktop is selected for the profile capture it will capture any and all files and folders in the desktop folder, regardless of any filters set.
You can filter all other folders in the profile, just not the desktop.
As a workaround I have built a script that searches for user added files and folders in the desktop folder, (everything except shortcuts). The script moves all of these to the local ?My Documents? folder, for that profile, then places shortcuts in the desktop folder to the moved items.
From there, I can filter out what I do not want to include in the profile capture, things like pictures, music, other multimedia files, etc.."
↧
Secure PXE Representative doesnt work post 9.5 upgrade
Problem:
The boot configuration data for your PC is missing.
Example Scenario:
We created a secure pxe deployment script but when testing as soon as you enter the PW you get the error attached.
This happens on my clients v9.5.1 environment and also my 9.5.2 test environment. Comparing the two install scripts for the normal PXE v the secure PXE it looks like the secure PXE has not been updated to v9.5 version.
Cause:
Secure PXE option was stopped working in 9.5 because the process uses ldlinux.img, which is not supported on 95.
Resolution:
Secure boot is not needed in Provisioning, as it is secure and requires a password. And as OSD is no longer present in 9.6 (to be released with-in the next month to the public) the decision was made not to resolve this one.
↧
↧
After Upgrading to 9.5 SP1, all of my Provisioning Templates are missing in WinPE
Problem:
After Upgrading to 9.5 SP1, all of my Provisioning Templates are missing in WinPE
Resolution:
Open the templates, alter something, apply the changes and the templates will re-appear.
↧
Dell E6300 can't boot from PXE Rep
Description:
PXE server is available, other machines can boot from this PXE server successfully, but Dell E6330 can't boot from this PXE Rep.
The error message is: PXE-E51, No DHCP or Proxy DHCP offers were received.
Cause:
The issue could be related to the Spanning Tree Protocol common to Cisco, Dell and other managed switches. The newer Dell System BIOS has a limited time out when PXE booting to a system during the imaging process. One workaround would be to press the Pause on the keyboard (i.e. the key combination on a Latitude E6400,) as soon as the DHCP cursor starts spinning on the display. Wait approximately 30 seconds then press the up arrow to resume the DHCP process. Note that if the DHCP response is not received by the third “dot”, the system is no longer looking for DHCP even though more dots are showing.
Resolution:
Shutdown STP.
↧
Preferred server fails with error
Problem:
Preferred server fails with error
Resolution:
1) Go to your operating System Deployment window and click on the "Manage the Windows Drivers in the PE" icon
2) Once that thing opens you will need to open the run command in the Start menu and type in %temp% and hit enter
3) Drill down to the IMGTMP folder and then further down to the Windows folder.
4) Look for a file called ALL.REG
5) Edit that file -Notepad will work or another acceptable editor
6) Add the following below what is already there
"SearchList" = "YourDomain.com,Internal.YourDomain.com,SomeOtherPlace.com"
NOTE: You need to substitute in the real names that you use for those bogus names I made above
7) Save the file and close the Windows Exploder so that nothing relating to that folder is open
8) Add a driver of some kind to the Manage Windows Driver window and name it Bogus Driver
9) Save that by clicking Finish
10) Once all of that is saved you need to go back in and open the "Manage the Windows Drivers in the PE" window again so that you can REMOVE that bogus driver.
NOTE ** The reason to add the bogus driver is that unless you add something your changes will not be saved out to your WIM file
11) Close the window and finish once you have removed the bogus driver
12) Redeploy the PXE server(s) as needed
You now have the ability to ping the server name without FQDN and you can find things in all of your DNS search domains.
↧
HII issues with unsigned drivers
Problem:
Once HII has started the drivers that are getting installed are listing as Unsigned and are not getting installed. This was not the way it was working on 9.03 and I did not see this behavior prior to SP1.
Cause:
What you have discovered is a change in the way we execute the dism command during the HII process. As a result of new OSes and some 64 bit Oses, the /forceunsigned switch has been removed. So when dism runs, it does not force the drivers that are not signed. Pre SP1 the switch was in there, so you would not have noticed the unsigned drivers.
Resolution:
If you need to force these drivers to install anyway, then you can pull the whole dism command out of the hiiclient log and add a new run exe action in your template. You can just paste in the dism command and add the /forceunsigned switch. Copy it out of your hiiclient.log, it should look something like;
DISM path and command line: x:\windows\system32\dism.exe /image:c:\ /add-driver /driver:"c:\Windows\LDDriverStore" /recurse /forceunsigned
***Make sure that if you have another DISM command in there, that you add this one after it, that you do not replace the other one with this one, and that you set the template to continue if it gets an error.
↧
↧
Not using old device name if already listing in LANDesk core
Problem:
My provisioning script is not using the device name listed in LANDESK when I reimage a machine that is in LANDESK.
This is working with OSD, just not with Provisioning
Cause:
The template variable for ldHostname is causing the problem and overrides the Public variable.
Resolution:
Delete the ldHostname template variable and try it again to see if the issue is resolved. The ldHostname public variable is correct and will name the computers correctly. The template variable for ldHostname is causing the problem and overrides the Public variable. Delete the ldHostname template variable and let me know if it resolves the issue for you.
↧
Tips for Building a Profile Migration Command Line with sample script
First, open up your command XML. The best way you want to view it is in the console's Profile Migration editor. To get to it, follow these steps;
- If you open up your Management Console, and go to Tools>Distribution>OS Deployment
- I am going to show you how to edit the XML in the provisioning template as OSD is gone in 9.6. But the same XML can be used in either location.
- Go into you're "my templates" section and create a new template (or edit an existing one). Create a "Capture Profile" action.
- Once you have added the action, you can browse to add a new Command XML, or edit to edit one.
- Hit "Edit" and select the template you want and hit "Edit" again. You can place the attached SampleProfileXML in the "...\ldlogon\uma\commandxml" folder and use it, or use one you are already working with.
Now that you are in the editor, here are some good rules of thumb to remember when building a Profile Migration Script (Command XML);
Rules of Thumb
- I found it best to INCLUDE all and then EXCLUDE the specific Users, Files, and Folders you do not want captured. When you look at the Command XML, you’ll notice on the User Profiles, and on Files and Folders I INCLUDE each of the top directories I want, and then EXCLUDE the lower directories I do not want captured.
- When doing either an INCLUDE or EXCLUDE, make sure to check the “Scan Sub Folders” option if it applies.
- There are some good variables that are specific to UMA\SMA, you have to look in the Documentation to find them.
- I found it best to have the users logged off at time of capture and deployment, but I have seen successful captures with the user logged on as well.
- The “My Documents” section, when you are building your script, appears to be useless, I just ignore it all together. All of you're "My Documents" can be included in the selection of "User Profiles" and in the "Files and Folders" as shown above in rule # 1. The %Personal Directory% variable takes care of it unless the user has been added to the exclude list.
- When in doubt, check the documentation listed in Rule # 3, it actually has a lot of information.
Here is the sample XML script as listed above. If you open it up in the Profile Migration editor, you can see how I apply each of the above mentioned rules.
↧
PXE Rep deployment script
I think my pxe deployment and removal scripts might be incorrect. Can someone please post these scripts for LANDesk 9 please?
Thanks,
↧
OSD Deploy Fail : "http://ldms9/landesk/vboot/BCD
Refer to following document
http://community.landesk.com/support/docs/DOC-23248
How to Capture a Windows 7 image with OSD in LANDesk® Management Suite 9.0 SP2
I followed the document P.11 and put the OSD script, which is a windows 7 image" I created in the schedule and started it.
Windows AIK is for Windows 7 base.
This is not first time to use OSD deploy feature of LDMS 9, so I don't know why it was failed this time. Please advice...
----------------------------------------------------------------------------------------
"Machine","CbaStatus","ExitCode","Duration","Begin","End","Command"
"PC-T500","OK",0,0:00:17,2011/10/28 21:10:51,2011/10/28 21:11:08,"<qt/>C:\Program Files\LANDesk\LDClient\sdclient.exe<qt/> /f /o /p="http://172.16.0.12/landesk/vboot/bootfile.exe""
"PC-T500","OK",0,0:00:07,2011/10/28 21:11:08,2011/10/28 21:11:15,"<qt/>C:\Program Files\LANDesk\LDClient\sdclient.exe<qt/> /f /o /p="http://172.16.0.12/landesk/vboot/tlibr16.dll""
"PC-T500","OK",0,0:00:07,2011/10/28 21:11:15,2011/10/28 21:11:22,"<qt/>C:\Program Files\LANDesk\LDClient\sdclient.exe<qt/> /f /o /p="http://172.16.0.12/landesk/vboot/tlibr32.dll""
"PC-T500","OK",0,0:00:07,2011/10/28 21:11:22,2011/10/28 21:11:29,"<qt/>C:\Program Files\LANDesk\LDClient\sdclient.exe<qt/> /f /o /p="http://172.16.0.12/landesk/vboot/lddefrag.exe""
"PC-T500","OK",0,0:00:07,2011/10/28 21:11:29,2011/10/28 21:11:36,"<qt/>C:\Program Files\LANDesk\LDClient\sdclient.exe<qt/> /f /o /p="http://172.16.0.12/landesk/vboot/FlushBuffer.exe""
"PC-T500","OK",0,0:00:07,2011/10/28 21:11:36,2011/10/28 21:11:43,"<qt/>C:\Program Files\LANDesk\LDClient\sdclient.exe<qt/> /f /o /p="http://172.16.0.12/landesk/vboot/cicfgmgr.vxd""
"PC-T500","OK",0,0:00:07,2011/10/28 21:11:43,2011/10/28 21:11:50,"<qt/>C:\Program Files\LANDesk\LDClient\sdclient.exe<qt/> /f /o /p="http://172.16.0.12/landesk/vboot/cindis.vxd""
"PC-T500","OK",0,0:00:07,2011/10/28 21:11:50,2011/10/28 21:11:57,"<qt/>C:\Program Files\LANDesk\LDClient\sdclient.exe<qt/> /f /o /p="http://172.16.0.12/landesk/vboot/copyfile.exe""
"PC-T500","OK",0,0:00:09,2011/10/28 21:11:57,2011/10/28 21:12:06,"<qt/>C:\Program Files\LANDesk\LDClient\sdclient.exe<qt/> /f /o /p="http://172.16.0.12/landesk/vboot/boot.img""
"PC-T500","OK",0,0:00:07,2011/10/28 21:12:06,2011/10/28 21:12:13,"<qt/>C:\Program Files\LANDesk\LDClient\sdclient.exe<qt/> /f /o /p="http://172.16.0.12/landesk/vboot/ChangeBCD.exe""
"PC-T500","ERR_Fail",-2147467259,0:00:01,2011/10/28 21:12:13,2011/10/28 21:12:14,"<qt/>C:\Program Files\LANDesk\LDClient\sdclient.exe<qt/> /f /o /p="http://172.16.0.12/landesk/vboot/BCD""
; "Job Complete","0 Done","1 Failed","0 Off","0 Unknown"
----------------------------------------------------------------------------------------
Thanks,
↧
↧
LD 9.5.2 Provisioning with GPT
Hi, does anyone have templates for creating a provision with GPT. I am having issues that it does not reboot after the ctos.
Thanks,
↧
WinPe Provisioning Issue
When WinPe starts and kicks off startnet.cmd. It fails at the "Downloading Prerequisites" section of the batch file. I noticed the following errors in the provisioning log. Does anyone know what causes the try "TryallWebService" to fail?
014-08-26 23:02:42(1732-1652) ldProvision:Provision Mode = PROVISION_MODE_CORE_SID
2014-08-26 23:02:42(1732-1652) ldProvision:Start TryallWebService Attempt:0.
2014-08-26 23:12:42(1732-1652) ldProvision:End TryallWebService Attempt:0. ExitCode:259
2014-08-26 23:12:56(1732-1652) ldProvision:Start TryallWebService Attempt:1.
2014-08-26 23:22:56(1732-1652) ldProvision:End TryallWebService Attempt:1. ExitCode:259
2014-08-26 23:23:07(1732-1652) ldProvision:Start TryallWebService Attempt:2.
2014-08-26 23:33:07(1732-1652) ldProvision:End TryallWebService Attempt:2. ExitCode:259
2014-08-26 23:33:13(1732-1652) ldProvision:Failed to call web service. exitCode=259
2014-08-26 23:33:13(1732-1652) ldProvision:Caught exception in main: code=80001500H, file=.\ProvisioningWebSvc.cpp, line=933
2014-08-26 23:33:13(1732-1652) ldProvision:Call web service GetStatusString()
2014-08-26 23:33:13(1732-1652) ldProvision:Start TryallWebService Attempt:0.
2014-08-26 23:33:14(1732-1652) ldProvision:End TryallWebService Attempt:0. ExitCode:0
2014-08-26 23:33:14(1732-1652) ldProvision:StatusString = The call to the Web service failed.
2014-08-26 23:33:14(1732-1652) ldProvision:Call web service SetActionStatus()
2014-08-26 23:33:14(1732-1652) ldProvision:Start TryallWebService Attempt:0.
2014-08-26 23:33:15(1732-1652) ldProvision:End TryallWebService Attempt:0. ExitCode:0
↧
Preferred server read-only user account
Hello everyone,
I'm trying to image and provision Windows Server 2008 R2 SP1 and Windows 8.1 update. I found this provisioning guide for Windows 7 and using it as a sample. After hours of fiddling with sysprep, unattend.xml and finding out how to do this and that in LDMS I managed to capture an image of Win2008R2. Now I'd like to provision it, but got stuck with the preferred server setup. It needs a read-only user account. I'm not able to find out to which share or what other thing should this account have read-only access. Is this a Windows account on the Core server or an account somewhere else? Thanks
↧
The Specefied file already has a notification GUID associated with it
I am getting the above error everytime I try and capture an image. Does not matter if i use Imagex, or ImageW. It does not matter what machine I deploy the script to. Has anyone seen this before. It is very frustrating.
↧
↧
LD 9.5 SP1 HII Driver Management: Disabling Drivers
I have a driver that is causing DISM error 2 when it tries to inject it into a Windows 8 offline image. This causes the whole provisioning task to fail.
I tried using the new "Disable Drivers" feature in LD 9.5 SP1 to disable the driver. I disabled it for all Windows 8 x64 Device ID's, but DISM is still trying to inject that driver.
Has anyone had any luck with the "Disable Drivers" feature, and, if so, how did you get it to work?
Thanks.
Pete
↧
Issue: 32(bit) UEFI Not PXE Booting in 9.5 SP2
Description: 32(bit) UEFI Not PXE Booting in 9.5 SP2
Problem: After scheduling a provisioning template, adding and starting the targeted device to the task, the PXE Rep is not picking up the task.
Symptoms: IA32 EFI file is not contained on the PXE Representative
Resolution:
Please ensure the PXE Representative has the required IA32 EFI file listed in the following locations:
File System
Program Files (x86)\Landesk\PXE\System\Images\IA32 EFI
Registry
HKEY_LOCAL_MACHINE\SOFTWARE\WoW6432Node\Intel\PXE\Mtftpd\Files (ia32 efi\undi\bstrap\bootia32.0)
If the file isn't present, Please check the PXE script and verify it includes ia32 efi\undi\bstrap\bootia32.0 and redeploy your PXE script.
If the file is listed in the PXE Script and after redeploying your PXE Script to your PXE Representative the file still is not listed in the registry and Program Files (x86)\Landesk\PXE\System\Images\IA32 EFI conduct the following:
On your core server, navigate to the following location:
Program Files (x86)\Landesk\ManagementSuite\Landesk\Files
Rename your current osdrep.msi file to osdrep.bak
Navigate to the location containing your 9.5 SP 2 install and copy the osdrep.msi file from this location and paste it in Program Files (x86)\Landesk\ManagementSuite\Landesk\Files
Redeploy your PXE Script and verify the IA32 EFI file is listed. The boot operation will not be allowed without this file.
↧
How do I resolve a PartitionHandler.exe memory error when capturing an image using Landesk provisioning?
When trying to capture an image on a Lenovo Ultrabook laptop, the provisioning process runs well until it starts the PartitionHandler. Once PartitionHandler.exe starts to run the process is halted with a cannot read memory error. I have attached the ldprovision.log and partitinohandler.log screenshots.......Please help.
↧