When any of my provisioning templates run, I have a patch system task that runs in the template. Before upgrading to 9.5SP1, the patch system task worked. Now, after the upgrade, the task runs and says it was successful but no patching is done. It just blows threw the task and marks it complete.
I tried creating a new task using the same patching group but to no avail.
Anyone have any ideas?
Jeff
I hope this isn't too off-topic for this forum. I'm looking for feedback from anyone who may be doing this already.
I've been asked to find a solution for a 12-PC training room in our building. Currently, users have full admin rights to the boxes in order to load whatever they may need for training. I'm trying to come up with a good way of locking the machines down so that I'm not forced to go in there after each training and delete docs from the desktop, change the wallpaper back, find and reset anything users have changed, etc. I'd like to lock them down as much as possible.
I haven't looked at it seriously but I heard that there are plugins for using DeepFreeze with LANDesk. Is anyone using these, or know of another tool that does something similar? I'm looking for any hints or recommendations to get the ball rolling. Thanks in advance for your response.
Does anyone have any idea why when using the symantec imaging tool with LANDesk that the system just hangs at the LANDesk screen but images fine with LANDesk images.
New to LANDesk with 9.5sp2 and setting up in our lab first before production. Configuring HII and trying to create the library. The library requires a preferred server and I'm getting stuck on this configuration. My environment will only need on server to hold all patches. When creating a preferred server, the configuration looks to need a source server and a replica server as well. Can this all be combined into one? Can a source server, replica server and preferred server all be the same server?
Hi, I am having a problem with HII not installing the driver for a usb3.0 hub in Windows 7 x86.
HII detects the usb root and installs the driver, but not the usb hub.
It is an intel motherboard with usb 3.0 onboard.
SQL lite view of the drivers.db3 (select * from devices where inffiles_idn = 82)
If you build a fresh install of Windows 7, a single unknown usb device is shown, give it the usb3.0 driver and it installs a usbroot device. Then another unknown device appears, give it the usb driver and it installs a usb hub.
How do I troubleshoot this to fix it? attached is the driver .inf file for the usb3.0 hub.
Thanks!
HI
I Encountered an error When use OSD of 9.5
System image is win7 , through the Sysprep forpackage，
Deployment when face the following error：
"Windows encountered an internal error setup is loading or search no answer file"
But when I use the same image packets are deployed on 9.0sp3 is successful.
Thankyou！
Is this possible?
i'm sure the question has probably been asked before and I am probably using incorrect search terms, so apologies.
I am unable to upgrade to 9.5 currently due to my OS level being 2003 on the core and am still awaiting the business to sign off the costs to do the upgrade etc, but of course I am now being asked to manage Windows 8 devices.
So thought before I even attempt to get it work, probably better I ask if it's even possible, or if there may be some 'unofficial' hacks I may need to do in order to get it working?
Thanks
I recently upgraded our core to 9.5 SP2 and mainly in hopes of gaining the Server 2012 R2 and Windows 8.1 options for OSD. Under SP1 during deployment (of 2012 R2) HII runs successfully but since Server 2012 R2 reports its windows version as 6.3 HII finds no drivers. After upgrading to SP2 supposedly options have been added for Server 2012 R2 and 8.1 however I am unable to find these options when looking at any provisioning templates and HII fails with the same problem as previously seen in SP1. Since we have already upgraded to SP2 I don't think apply LD95-SP1-CP_BASE-2013-1017 is going to be the best option. Has anyone had success deploying Server 2012 R2 or Win8.1 since the SP2 upgrade?
Hi All,
I have a X86 unattended file that works great. I know have a request for x64 bit machines. So i need to create a copy of the unattended file and edit it so the X64 machines can build.....Problem is i dont have a clue what to edit. I have read http://community.landesk.com/support/docs/DOC-7556 and it means nothing to me! So i was hoping someone has had a simular experience and could offer some guidence.
By what i have read i need to replace the "x86" with "AMD64" however not all of them......But im not sure what ones to change, Secondly they have a publicKeyToken="31bf3856ad364e35" next to them, does this need editing? and thirdly i beleive i need to point this at a AMD64 wim (which will probably be the captured 64bit image i have), but where and what do i put in to point this in the right location?
I am a complete novice at this, the previous unattended was created by an engineer thats no longer with us so any help would be MUCH appreciated. I have attached my current x86 unattended file that works.
Hello,
i'm using LDMS 9.5 SP1 and want to deploy windows 8.1 to Elitepad 900 devices with Provisioning Template. Has someone successfull deployed Windows 8.1 to Elitepad and could possibly share there template ? Especially the partitioning and deployment part.
I'm not able to boot deployed Windows 8.1 because of BCD errors and so on. The partitioning part with GPT or not and 100MB boot partition or not is confusing for me .. 
Thanks
regards
Alex
After I image a computer it seems like it hangs on "setup is applying system settings" when it is trying to sysprep.
How to turn on logging to get a PXEMTFTP.LOG file for troubleshooting the PXE representative.
I am getting an error when provisioning a Dell E5440. Provisioning lays down an image, reboots, Windows does it's detecting driver 0-100% thing then I get an error from windows:
Windows could not configure one or more system components. To install
Windows, restart the computer and then restart the installation.
after a restart (and every restart) I get this:
The computer restart unexpectedly or encountered and unexpected error. Windows installation cannot proceed. To install Windows, click "OK" to restar the computer, and then restart the installation.
I have downloaded all the drivers from Dell's site and exploded them into directories under \\<core>\ldmain\landesk\files\drivers\E5440\ then did a Build Library under HII Driver Management.
Any ideas as to my next step?
How can I troubleshoot this?
The core is running 9.5 SP1. The client OS is Win7 x86. This provisioning task works on several other Dell models E6420,30,40 among others.
Hi,
Was hoping someone could confirm they can see Windows 2012 Server options listed under the Target OS dropdown list uder OSD when creating new templates in LANDesk 9.5 SP1?
I can see Windows 8 and Windows 8 x64, but no Windows 2012 Server options. is this an oversight?
Regards,
Richard.
Is it possible to PXE boot and use the WinPE menu to capture a system image to external media? I have tried to create an OSD script, and set the storage path to "D:\" (the first drive letter that is assigned when I insert removable media while in WinPE), but it definitely wants a UNC path.
Just upgraded to SP2 the other night and how provisioning is extremely slow. Our techs informed me that the entire provisioning process used to take about 45 - 55 minutes start to finish and now it's taking close to 5 or 6 hours to complete.
Anyone else having a similar experience? Any ideas?
This document is intended to explain provisioning action handlers so that failures seen in individual actions within a provisioning template can quickly be found and corrected.
Logs on the core will help with why a task is not starting, but do not provide a lot of detail about why a certain action failed. The core logs are found at ManagementSuite\logs\prov_schedule.exe.log and ManagementSuite\logs\provisioning\provisioning.log.
Device logs can be found either at x:\ldprovision or at systemdrive:\windows\temp.
Each action that is run in a provisioning template is done by an action handler. A action handler may launch multiple other action handlers as part of its task. These other tasks could be considered to be child actions. The deploy image action in 9.5 and higher is an example of this. The deploy image action hander may automatically download the appropriate tool for imaging using a download action handler. The deploy image action then maps a drive to the network location where the image file is using the MaptoPreferred action handler. Finally it will complete its own job of deploying the image using itself. The launch of each of the addition action handler used by deploy image will be logged in the DeployImageHandler.log along with the result code from the additional handler.
This sample DeployImageHandler.log shows the launch of two additional action handlers (DownloadHandler.exe and maptopreferredhandler) as well as the exit codes for those handlers.
ExecuteCmd DownloadHandler.exe /source="http://mycore/ldlogon/provisioning/windows/imagew.exe" /dest="x:\ldprovision\imagew.exe"
created process, file handle 60 with non-readonly parameter
Process Exit Code: 0
Verifying file was successfully downloaded.
The file (x:\ldprovision\imagew.exe) was successfully downloaded
Getting free drive letter
Free drive letter: f
ExecuteCmd maptopreferredhandler.exe /path="\\mycore\images\win7.tbi" /driveletter=f /pathisfile
created process, file handle 68 with non-readonly parameter
Process Exit Code: 0
If a failure occurred in either of the additonal actions (DownloadHandler and maptopreferredhandler) launched by deployimage the errors would be shown in the DeployImageHandler.log with a corresponding exit code. Zero indicates the task succeeded. If a failure occurred the DeployImageHandler.log may not contain enough detail to determine the root cause of the failure. Instead the log from the additional action handler (DownloadHandler.log or maptopreferredhandler.log) should be reviewed. The additional action handler may even launch its own child handlers before returning so those logs may also need to be reviewed.
If the failure seen in the DeployImageHandler.log was an error mapping the drive to the image, the MaptoPreferredHandler.log would provide additional details about the failure. Sometimes the error will be spelled out. Other times only an error code will be shown. The error codes shown will often correspond to the windows error codes listed at http://msdn.microsoft.com/en-us/library/windows/desktop/ms681381(v=vs.85).aspx. This allows a simple lookup to get additional information about the failure. Viewing the primary action handler log and following the failure through to the action handler log where the failure actually occurred will save time and frustration while troubleshooting provisioning templates.
| Provisioning Action | Action Handler Log (Client) |
|---|---|
| Capture Image | CaptureImageHandler.log |
| Capture Profile | CaptureProfileHandler.log |
| Configure Agent | ConfigHandler.log |
| Configure Target OS | ConfigTargetOSHandler.log |
| Control Service | ServiceControlHandler.log |
| Copy File | CopyFileHandler.log |
| Create Directory | ManageDirectoryHandler.log |
| Delete File | DeleteFileHandler.log |
| Deploy Image | DeployImageHandler.log |
| Deploy Profile | DeployProfileHandler.log |
| Distribute Software | SDClientHandler.log |
| Download File | GetFileHandler.log |
| Download from Preferred Server | DownloadHandler.log |
| Execute File | ExecuteHandler.log |
| Hardware-Independent Imaging | HIIHandler.log |
| Inject Script | InjectScriptHandler.log |
| Install Service | ServiceInstallHandler.log |
| Join Domain | JoinDomainHandler.log |
| Map/Unmap Drive | SmbShareHandler.log |
| Map/Unmap Drive to Preferred Server | MaptoPreferredHandler.log |
| Map Software to SLM Table | MappedSoftwareHandler.log |
| Partition | PartitionHandler.log |
| Patch System | PatchHandler.log |
| Replace Text | ReplaceTextHandler.log |
| Scripted Install | ClientActionHandler.log |
| Uninstall Service | ServiceRemoveHandler.log |
| Unzip File | UnzipHandler.log |
| Update Registry | RegUpdateHandler.log |
| Wait | WaitHandler.log |
Hello,
I have a simple Question about the deployment of an image.
Do LANDesk provide the ability to store an image (.wim) locally on the pc (on an extra partition), so that the image must not be loaded from the server always at a re-installation?
I hope you can help me!
RMaas
(Excuse my bad English!)
Hi all,
Just a quick one to give something back - we wanted to automatically name our stations to the service tag when provisioning. Here's a simple PowerShell script which you can save as rename.ps1 or something and then just add as a PowerShell distribution package and set as a provisioning step. Tested and works on all our Dell machines with Windows 7 and latest PowerShell, other manufacturers may vary but worth a go.
$computername = Get-Content env:computername
$servicetag = Get-WmiObject win32_bios | Select-Object -ExpandProperty SerialNumber
If ($computername -ne $servicetag)
{
Write-Host "Renaming computer to $servicetag..."
Rename-Computer -NewName $servicetag
}
Else
{
Write-Host "Computer name is already set to service tag, nowt to do!"
}
Hope this helps!
Seeing as people liked the last PowerShell script, here's another that we use - this one detects if the machine is a laptop and if so performs certain tasks - we use it to install a VPN client as an example. Modified from an idea by Hey Scripting Guy at Microsoft, plus I added return codes as suggested by David Watson in the other thread - thanks David, good tip! If you're not using those, knock off the Exit lines if you like, if you are then make sure you add matching entries in the package under 'Assign Return Codes'.
Function Get-Laptop
{
Param(
[string]$computer = "localhost"
)
$isLaptop = $false
if(Get-WmiObject -Class win32_systemenclosure -ComputerName $computer |
Where-Object { $_.chassistypes -eq 9 -or $_.chassistypes -eq 10 `
-or $_.chassistypes -eq 14})
{ $isLaptop = $true }
if(Get-WmiObject -Class win32_battery -ComputerName $computer)
{ $isLaptop = $true }
$isLaptop
}
If(get-Laptop)
{
New-Item "C:\I_AM_A_LAPTOP.txt" -type file
\\landeskserver\packages$\somelaptopscript.bat
Exit 2020
}
else
{
New-Item "C:\I_AM_NOT_A_LAPTOP.txt" -type file
\\landeskserver\packages$\somedesktopscript.bat
Exit 2021
}
We're still testing this so if anyone finds any issues then feel free to chip in, seems to work so far though on our Dell estate. Hope this helps!