I have been trying to use the sample provisioing templates and sysprep xml files. I can everything to work ok except that after the macines images, goes through HII and reboots it says it can't logon as Administrator. If I log it on manually it works fine (runs through the sysprep, installls agent etc). I've been working with support and so far haven't really gotten any help. I've double checked the AdminPass variable is set right, the autologon count in sysprep is set. Any ideas or has anyone else had this problem? We currently use ghost and landesk to re-image all our computers but we'd rather really just use one product. I really don't want to go around and logon hundreds of computers to the admin account manually...

Thanks

Steve

Is there a limit to the size of profile that can be captured with a provisioning template using UMA?  It seems larger profiles sizes fail when smaller sized profiles are successful.  There is plenty of space to store the large profile.

We have upgraded from 9.0 sp3 to 9.5 sp1.

Now that this is completed we seem to be seeing some issues.

Once we have setup an OSD and we drag it to the PXE boot menu the item will show correctly. I can then save these changes and send them to the PXE reps however if i refresh the tab after doing this the item i just dragged over looses its name and just shows as a blank entry. I can still select this from the client machine but it doesnt deploy the image. This happens to all new OSD i drag to the PXE menu.

After upgraded to LDMS95 SP1 I decided to use OSD imagew v2 instead of Provisioning. After capturing I got an error message from the source marchine "missing bootmgr press ctrl-alt-del to restart". The source machine is a physical PC not a VM.  I only installed Windows 7; there are no Windows updates or hardware drivers installed as of yet. I didn't even run sysprep.  I'm not sure if anyone had experiencing similiar issue and able to resolve it.

This a NEW Dell Optiplex 7010, right out the box. Just received a shipment of 200 computers, have already imaged 25 of the set with Our Windows 7- Dell 7010 image and then cpu # 26 - 40, will not do anything after you select the deploy option. Tried swapping ram and hard drives. Verified that the configuration for the first batch (cpu #0 - 24) was that same as the second batch (#25-40). Funny thing is that, if I take one of the cpu's from the first batch (#0-24) and try to reimage it using the same 7010 image, EVERYTHING works ok or if I take one of the hard drives from the first batch (that is imaged) and place it in the second batch, it will boot to our startup script. Using LANDesk ver 9.0.3.1.

Greetings,

I'm learning the ways of Landesk Provisioning and trying to setup a provisioning template to succesfully deploy a .wim image file using imagex, but am running into a brick wall when the template gets to the "Deploy Image" action. To get to the point where I'm at now, I've been referencing this guide and started out using the samle templte found here.  I've read here that the "Map Drive" actions are no longer necesarry since we are running ver 9.5. SP1 and also when using ImageX. I've also read in other discussions that for ImageX to work properly, you need to first create and format the partition the image is going to.

I'm not trying to accomplish anything fancy with using multiple partitions. Just hoping to lay an image onto the drive (one partition).

Here's my Create Partition Action whcih seems to be working (Result is Success).

Here's my Deploy Image action, which fails each time:

I did setup some public variables as the "getting started" guide says to (ldpass, lduser, imageshare, imagetool, etc). I'm wondering if the imageshare/imagetool variables are still having an effect even though I deleted the actions to map the drives??

Short of asking for sample templates using ImageX , any help is apprecaited. Thanks in advance.

Anyone successfully get USB 3.0 Host and Hub drivers to inject via HII in a Windows 7 image with the new WinPE 4.0 that came with SP1?

I used to be able to load the host drivers in WinPE 3.0 to allow it to see the hub so HII could detect it was there.  In WinPE 4.0, there are no USB 3.0 drivers for it since its Windows 8 based (at least none that i can find).  I tried using the windows 7 drivers but it errors on loading during WinPE setup script. Using Lenovo devices, FWIW.

Hello,

when I try to install WIN 98 on a HP 8300 ELITE I see THISE ERROR:

ERROR: unable control a20 line

xms driver not installed

XMS RAMdisk v1.91 (FU - 08/98): XMS manager required.

memory allocation error.

cannot load COMMAND, system halted.

my RAM is 4GB

I have to try with 2GB the problem is the same.

thk.

I am running Landesk 9.5 no SP1.

This is rather long and confusing but bare with me.

This is the 2nd discussion I had about this and it keeps reoccuring. 1st discussion: http://community.landesk.com/support/message/89993#89993

From time to time I keep getting complaints a provision template message pops up when a user boots up their computer.

What is happening is the computer is looking for a Provisioning Template to run but not finding one scheduled.(This is indicated in Provisioning.log on the core server)

What we have found is sometimes (in the case I'm looking at now was in June 2013) a provisioning was run but never completely finished. In other words it was imaged but during the tail end during software installs it failed.

In the right click of the computer in Landesk console under Provisioning History it shows the task still running.

As in the other discussion I uninstalled and reinstalled the PXE Rep. Didn't Help.

Now for the confuseing part, I ran a Clear_Task_Queue 3 times and heres what I found. 1. deleted all users\landesk\manage suite\database  and remade database   2. deleted All user\landesk\manage suite\landesk\files  3. Did Not Delete All users\vulscan\*.xml     4.  May have deleted Program Files\landesk\ldclient\smdcache\*.xml (there are none showing)  5. Deleted  Program Files\landesk\ldclient\sdmcache\ldlogon\packages

One last thing, the provisioning log both new and .old  only go back to September 9th 2013 and this computer only shows up in Provisioning log on September 16 at 4pm til now September 17 10AM.  We find no triggers to cause this.

After rebooting the computer several times the provisioning template quit coming up but still indicates running in Right Click Provisioning History.

Besides this computer I see 2 others constantly showing up in Provisioning log doing same thing but had no complaints of it showing up on boot up yet.

I am attempting to capture an image & have created a boot usb to boot into my provisioning environment.  it seems, however, that it is booting in 64bit mode rather than 32bit mode.

I am using ghost to capture the image & it is using the ghost32.exe file.  I believe it is failing because the provisioning environment is running in 64bit mode.  It is able to map network drives successfully, but specifically fails at the capture image command.

Is there any way to force the provisioning to 32-bit mode?

Thanks!

I got a Dell Precision T3600 that is not showing drives within diskpart using LANDesk PE. We are using a 9.5 core with it's latest PE configuration. The drive is attached via a SAS controller. Has anyone else seen this issue? I have tried loading the Storage Controller drivers from Dell's website into the PE image but it still will not see this drive. Any ideas?

Hi,

I use LDMS 9 SP4 and yesterday, all was fine...

today when i try to use provisioning i have this message..

ERROR TemplateFinder  17/09/2013 16:29:52  : couldn't find task for computer 191

I don't change anything...

I check my template, all is ok.

Ben

I am trying to setup an image and have captured the image. I am having a hard time deploying it. It seems from the logs that it is hanging during the unattend.xml portion. Does anyone have any ideas?  I have attached the log file below.

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

"8851FB6EE1A0","OK",0,0:00:01,9/17/2013 4:42:37 PM,9/17/2013 4:42:38 PM,"WINPE, TIMEOUT=1800"

"8851FB6EE1A0","OK",-2147024809,0:00:01,9/17/2013 4:42:39 PM,9/17/2013 4:42:40 PM,"diskpart /s X:\LDClient\rmvol.txt"

"8851FB6EE1A0","OK",230227968,0:00:00,9/17/2013 4:42:41 PM,9/17/2013 4:42:41 PM,"ldrun drvmap.exe cypruscu\landesk 20CAB89CCF7D350225C159032AB10E75A845D641F77 I: """\\ldms.cypruscu.net\ldmain""", STATUS FACILITY=3513"

"8851FB6EE1A0","OK",230227968,0:00:01,9/17/2013 4:42:42 PM,9/17/2013 4:42:43 PM,"ldrun drvmap.exe cypruscu\landesk 20CAB89CCF7D350225C159032AB10E75A845D641F77 H: """\\ldms.cypruscu.net\ldmain""", STATUS FACILITY=3513"

"8851FB6EE1A0","OK",0,0:00:06,9/17/2013 4:42:44 PM,9/17/2013 4:42:50 PM,"ldrun sdclient /f /o /dest="X:\LDClient\LDPathExist.exe" /p="http://172.16.160.241/landesk/files/LDPathExist.exe" /disableclientqueue, STATUS"

"8851FB6EE1A0","OK",0,0:00:00,9/17/2013 4:42:51 PM,9/17/2013 4:42:51 PM,"ldrun LDPathExist.exe """I:\ImageStore\HP 8200\LD8851FB6EE3EF.TBI""", STATUS"

"8851FB6EE1A0","OK",0,0:00:00,9/17/2013 4:42:52 PM,9/17/2013 4:42:52 PM,"ldrun LDPathExist.exe """H:\osd\imagew 2\imagew_x64.exe""", STATUS"

"8851FB6EE1A0","OK",0,0:00:02,9/17/2013 4:42:53 PM,9/17/2013 4:42:55 PM,"diskpart /s X:\LDClient\WIPECLEANDISK0.TXT"

"8851FB6EE1A0","OK",-1,0:00:00,9/17/2013 4:42:56 PM,9/17/2013 4:42:56 PM,"ldrun h:\osd\IMAGEW~1\IMAGEW~1.EXE /r /o /d:0 /f:"""i:\IMAGES~1\HP8200~1\LD8851~1.TBI""" /rb:0"

"8851FB6EE1A0","OK",0,0:00:06,9/17/2013 4:42:57 PM,9/17/2013 4:43:03 PM,"ldrun sdclient /f /o /dest="X:\LDClient\diskinfo.exe" /p="http://172.16.160.241/landesk/files/diskinfo.exe" /disableclientqueue, STATUS"

"8851FB6EE1A0","OK",0,0:00:06,9/17/2013 4:43:04 PM,9/17/2013 4:43:10 PM,"ldrun sdclient /f /o /dest="X:\LDClient\assvol2.txt" /p="http://172.16.160.241/landesk/files/assvol.txt" /disableclientqueue, STATUS"

"8851FB6EE1A0","OK",0,0:00:06,9/17/2013 4:43:11 PM,9/17/2013 4:43:17 PM,"ldrun sdclient.exe /f /o /dest="x:\ldclient\RMVOLLETTER.TXT" /p="http://172.16.160.241/landesk/files/RMVOLLETTER.TXT" /disableclientqueue"

"8851FB6EE1A0","OK",0,0:00:01,9/17/2013 4:43:18 PM,9/17/2013 4:43:19 PM,"ldrun tokreplw X:\LDClient\assvol2.txt partition=1"

"8851FB6EE1A0","OK",-2147024809,0:00:00,9/17/2013 4:43:20 PM,9/17/2013 4:43:20 PM,"diskpart /s X:\LDClient\RMVOLLETTER.TXT"

"8851FB6EE1A0","OK",-2147212265,0:00:00,9/17/2013 4:43:21 PM,9/17/2013 4:43:21 PM,"diskpart /s X:\LDClient\assvol2.txt"

"8851FB6EE1A0","OK",0,0:00:06,9/17/2013 4:43:22 PM,9/17/2013 4:43:28 PM,"ldrun sdclient.exe /f /o /dest="x:\ldclient\fixvista.bat" /p="http://172.16.160.241/landesk/files/FixVista.bat" /disableclientqueue"

"8851FB6EE1A0","OK",0,0:00:08,9/17/2013 4:43:29 PM,9/17/2013 4:43:37 PM,"ldrun sdclient.exe /f /o /dest="x:\ldclient\fixntfs.exe" /p="http://172.16.160.241/landesk/files/fixntfs.exe" /disableclientqueue"

"8851FB6EE1A0","OK",0,0:00:06,9/17/2013 4:43:38 PM,9/17/2013 4:43:44 PM,"ldrun sdclient.exe /f /o /dest="x:\ldclient\bcdedit.exe" /p="http://172.16.160.241/landesk/files/bcdedit.exe" /disableclientqueue"

"8851FB6EE1A0","OK",0,0:00:07,9/17/2013 4:43:45 PM,9/17/2013 4:43:52 PM,"ldrun sdclient.exe /f /o /dest="x:\cba8\FixWindows.exe" /p="http://172.16.160.241/landesk/files/FixWindows.exe" /disableclientqueue"

"8851FB6EE1A0","OK",1,0:00:01,9/17/2013 4:43:53 PM,9/17/2013 4:43:54 PM,"ldrun x:\cba8\FixWindows.exe 1"

"8851FB6EE1A0","ERR_Fail",-1,0:00:06,9/17/2013 4:43:55 PM,9/17/2013 4:44:01 PM,"ldrun sdclient /f /o /dest="C:\unattend.xml" /p="http://172.16.160.241/landesk/files/HP%208300.xml" /disableclientqueue, STATUS"

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

I am working on developing HII for our HP Desktops.  I've started with two HP Models - Pro 6200 and 6300.  I have all drivers for both systems loaded in the HII driver database.

The whole provisioning processing as well as HII goes smoothly, except for each machine ends up with a generic "Standard VGA Adapter" driver instead of the actual Intel graphics driver adapter.  The intel driver is loaded in the HII database.  Howcome it always chooses the generic driver?  How can I force it to choose the correct driver?

Thanks!

Good afternoon all,

I'm having some issues deploying a sysprepped HII images to some HP Compaq 6305s. The basic issue that I'm having is that I can get it to load WinPE, open up the PXE menu, select a deployment script, and it just hangs.

To even get it that far I had to install a secondary NIC and run two ethernet cables into the box (one into the onboard, one into the card). Originally it wasn't able to load the NIC drivers once it booted into WinPE, despite having the 32 bit Win 7 drivers in the PE image. So the onboard is getting me into the PXE boot menu from Network Boot (using only the card didn't work), and then the card is successfully connecting to the network once it's actually in WinPE.

I managed to get it deployed to one HP this way, but the other two aren't cooperating.

I've covered all the basic troubleshooting steps, and verified that the current setup is working on the Dells that we customarily use (since the symptoms are what usually occur when the network path to the image file is invalid or the credentials are incorrect). So far I've:

• Imported the Win 7 32 bit drivers into the WinPE image file
• Updated the PXE Rep with the new boot.wim
• Completely uninstalled the PXE Rep and reinstalled
• Logged into a computer with the service account and manually verified both the UNC path to the image store and credentials
• Been able to successfully ping the image store, the PXE Rep, and the LanDesk server from the target HP both before and after selecting the deployment script
• Verified the deployment script on a spare Dell machine
• Verified the NIC is functional on the HP by booting into the OEM Win 7 that came with the machine
• Verified the HP is on the newest BIOS version for that model
• Unplugged the onboard (non-functional in WinPE) ethernet cable and verified that the card had a valid and functional connection, with a valid IP, then attempted to continue with deployment

I'm at my wit's end here. I have no idea why this wouldn't be working on the HP but is working on the Dell, and I have absolutely no clue why this worked once and won't work on the other two. I've never had this many issues depoying an image to new hardware. Any suggestions are greatly appreciated!

Description

This issue is characterized by selecting an OSD script from within the PXE Boot Menu inside WinPE, the Boot Menu window disppearing, and then no further pop ups or display windows occurring.

There are several causes for this behavior, and therefore, several possible solutions. This troubleshooting guide is centered around the issue of the OSD script failing to be initiated on the core server, or the OSD logs indicating that the machine is "OFF". If the OSD script indicates that it is launching at least one EXEC line against the target, then this troubleshooting guide can be skipped.

A visual representation of this process is attached as a flowchart below:

Step 1 - Identifying the Issue

To determine the troubleshooting path, it must first be determined how far the process is progressing. The fastest way to accomplish this is to determine if a CustJob log is being created. Follow the steps below to determine this:

1. On the core server, go to the log directory. This is located at the following path <Install Drive>:\Program Files\LANDesk\ManagementSuite\logs or can also be accessed via UNC share at <coreservername>\ldlog.

2. Once in the log directory, it is reccomended to sort by Date Modifed, with most recent at the top.

3. The log file will be named CJ-OSD-<scriptname>-<timestamp>.log

4. If there is a log file, open it with a text editor, such as notepad or word.

5. If the log file is similar to the one listed below, and indicates that the machine is OFF, then CBA is unable to contact the specified machine or CustJob has targeted an incorrect machine record.

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

"(OFF) XPSP2B","OFF","N/A","0:00:00","11/6/2008 12:19:28 PM","11/6/2008 12:19:28 PM","N/A"
; "Job Complete","0 Done","0 Failed","1 Off","0 Unknown"

 

If there is no log, then the process did not complete to the point of initiating CustJob to launch the OSD script. See below for actions.

First, verify that the following service are installed and running on the core server:

LANDesk Inventory Server

LANDesk Management Agent

If these services are running, it may be beneficial to restart these services. If the LANDesk Management Agent service is missing, go to the "No logging generated on the core" section below. Once restarted, reboot the machine into WinPE and select the script from the menu, if the same behavior occurs, follow the indicated directions:

If there was no log file generated in the log directory on the core, go to the "No logging generated on the core" section below.

If there was a log and it indicated that the machine was OFF, go to the "Machine shows OFF" section below.

No logging generated on the core.

The process to request a script to run on the client machine involves a series of processes to request, resolve and schedule the task from the client to the core server. The below steps will attempt to identify and resolve the issue related to these processes.

Missing LANDesk Management Agent service

If the core does not have a LANDesk Management Agent service, you can install this service by following the steps listed below:

1. On the core, pull up the Start > Run window

2. In the field, type or paste the following command and then hit enter:

"C:\Program Files\LANDesk\Shared Files\residentagent.exe" /register

Once the service is installed, start the service and then try the OSD process again.

If there is not a C:\Program Files\LANDesk\Shared Files folder on the core server, please contact LANDesk Technical Support for further assistance.

If the LANDesk Management Agent service is installed and running and a service restart did not resolve the issue, please follow these additional troubleshooting steps:

Verifying the Inventory Record

OSD needs an inventory of the device being imaged in order to create the task and begin logging.  New machines that have not been inventoried before will be listed by its MAC address in the Device Name column in the console.

If there is no inventory record for that device, restart the inventory service and reboot the client and try imaging again.  If still no inventory record appears for the device please contact LANDesk Technical Support for furhter assistance.

Verifying the PXE.amsx Web Service functionality

• Open the CoreWebServices.log located in the log directory on the core server. The log should contain lines that are similar to those listed below:

RunScript: started with client mac address 000C29461DD1, script GUID bc6a8a9c-3edc-4845-83fb-5e1cceb60b71
RunScript: completed succesfully with client mac address 000C29461DD1, script GUID bc6a8a9c-3edc-4845-83fb-5e1cceb60b71

• Can the LANDesk PXE.asmx web page be accessed? (Note: This must be run locally on the Core Server

• Open a web browser on the core and type/paste the following address:

http://localhost/landesk/ManagementSuite/Core/core.webservices/PXE.asmx

This should display the web page shown below:

• Will the GetObjIDFromMacAddress function resolve a Mac address to a Computer_Idn from the PXE.asmx web page? (Note: This must be run locally from the Core Server)

1. Click on the GetObjIDFromMACAdress link in the web site.

2. On the MAC Address field, enter in the mac with no spaces or dashes.

3. Click on the "Invoke" button to process.

4. The following return should be displayed:

NOTE: The number encased by > < is the object ID and corresponds to the machine's ID assigned by Inventory.

If this process fails, then there is most likely a missing record. Ensure that the Inventory contains the MAC address associated with a machine record.

• Will the RunScript function start the job by manually putting in the MAC Address and ScriptGUID? (Note: This must be run locally from the Core Server)

1. Click on the RunScript link in the website.

2. On the indicated fields, input the MAC Address and the script GUID.

3. Hit the Invoke button.

A CustJob window should launch on the core and start processing the script. You can also look to see if this process generates a log file in the log directory. If this process succeeds, then it indicates that IIS may be hung or not correctly processing SOAP requests. Try running an "IISreset" command from Start > Run. You may also need to re-register ASP.NET on the core with the following command:

For 8.7 Core

"C:\Windows or WINNT\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe -i"

For 8.8 Core

"C:\Windows\Microsoft.NET\Framwork\V2.2.50727\aspnet_regiis.exe -i"

• Enable the OSD Web Tracing by doing the following:

1. Edit the web.configfile in C:\ProgramFiles\LANDesk\LANDesk\ManagementSuite\LANDesk\ManagementSuite\Core\Core.WebServices so that the line "<trace enabled="false"" reads "<trace enabled="true"" and restart the WWW Publishing service.

2. The following URL may be used to pull up the Web Trace to track what requests are made to the OSD Web service on the core: (Note: This must be run on the LANDesk Core Server)

http://localhost/landesk/ManagementSuite/Core/core.webservices/trace.axd

• An http caching appliance will respond to the http requests made by the client. Due to the caching appliance responding, the client will not receive the subsequent lines of the script. Configure the caching applicance to not cache the http traffic from the Core Server.

Verifying the LANDesk Management Agent Service functionality.

• Run script calls a local execute on the Core Server. The LANDesk Management Agent service must be running on the Core Server.

• To test the Management Agent service, run the following command line:

"C:\Program Files\LANDesk\Managementsuite\custjoblaunch.exe"

" /bootonly

For Example:

"C:\Program Files\LANDesk\Managementsuite\custjoblaunch.exe" 83 "DeployGhostImage.ini" /bootonly

If this does not launch the script, remove and re-install the LANDesk Management Agent service with the following commands:

Remove:

"C:\Program Files\LANDesk\Shared Files\residentagent.exe" /unregister

Install:

"C:\Program Files\LANDesk\Shared Files\residentagent.exe" /register

If these steps do not resolve the issue, please contact LANDesk Technical Support for further assistance.

Machine shows "OFF"

NOTE: When troubleshooting Inventory related issues, please ensure that you are logged in to the core console with a user that does not have any restricted scopes applied and that is allowed to view the Default All Machines scope.

Causes

1. Another machine in the database has the IP address assigned to the machine in WinPE.  Custjob.exe is targeting that device.

2. The inventory scan had not yet processed the ip address from the miniscan. This could be because the inventory service is stopped or hung.

3. Duplicate devices (two machines with the same MAC Address) in the database.

4. Core cannot contact the Agent on UDP port 9595. (Firewall, or other filtering device is blocking this port.)

5. Under Configure | Services | Custom Jobs, the Discovery setting may be set to TCP only.  WinPE only responds to UDP.

6. DNS can be in a state where the client can resolve the Core Server but the Core Server cannot resolve the agent workstation.

7. NIC driver may not be entirely functioning properly.

8. Name resolution problems may prevent the core from targeting the machine by DNS name.

Resolutions

1. Start or restart the inventory service.

2. Search for the IP address that WinPE has.  If another device has this IP address, delete that inventory record.

3. That device may show up twice in the database.  Delete all devices with that MAC Address.  See
   community article 1569 for assistance with this.

4. Open UDP port 9595 between the Core Server and the Agent workstation.

5. Go to Configure | Services | Custom Jobs and set the Discovery to try both UDP and TCP.

6. Go to Configure | Services | Custom Jobs and check the box to Disable DNS/WINS Lookup.

7. Make sure the Core Server can ping the Agent workstation by name and IP.

8. Update the NIC driver In the WinPE image.

9. Make sure the Core Server and PXE reps are running the same version of software.

10. Verify that the client miniscans are being received by the core server. Enable the Store Scans option in Configure | Service | Inventory | Advanced. Set the value to 1 and restart the Inventory service. Browse to the ldmain\ldscan\Storage directory and verify that .IMS files are being received when the client boots into WinPE.

11. Verify that the core is processing mini scans. Check Configure | Services | Inventory | Advanced | Ignore mini scans. This value needs to be set to 0

The links below go to the LANDesk Help Center user documentation:

• OS deployment overview
• Using OS deployment to deploy images
• OS image guidelines
• Validating licenses for imaging environments
• Select a default preboot environment
• Customizing images with Setup Manager and Sysprep
• Create a sysprep image
• Deploying images
  • PXE-based deployment
  • Agent-based deployment
  • Using Targeted Multicast to deploy scripts
  • Setting the maximum packet size for Targeted Multicast
  • Viewing image status reports
  • Image scripts
• Profile Migration
  • Profile migration overview
  • Creating profile migration scripts
  • Create a profile capture script
  • Create a profile restore script
  • Run a profile migration script
  • Customizing profile migration settings
• OS deployment and Profile migration wizard help
• Appendix: Additional OS deployment and profile migration information

This is not working after the latest service pack 1, 9.50.2.6.  Basically, I don't use the Agent for imaging.  I have OSD scripts set up and have them show up in the PXE menu.  After I PXE boot a client, a Landesk script runs and says that remote control is installed on the client.  This is prior to me selecting anything on the PXE boot menu.  If I go back to the core, find the machine that PXE booted and select remote control, I find "Remote Control" grayed out under the new pop-out menu.  This is the same story with XP, XPE, 2003, WES7, etc.,  Is this a known issue?  Thank you

-Jesse

After upgraded to LDMS95 SP1 I decided to use OSD imagew v2 instead of Provisioning. After capturing I got an error message from the source marchine "missing bootmgr press ctrl-alt-del to restart". The source machine is a physical PC not a VM.  I only installed Windows 7; there are no Windows updates or hardware drivers installed as of yet. I didn't even run sysprep.  I'm not sure if anyone had experiencing similiar issue and able to resolve it.

I tried to personal the unattend.xml for Windows 7 deployment.  I thought I have everything entered correctly but can’t seem to automate the local account logon process.  When it booted up the first time it prompted me to create an account. I tested the unattend.xml file directly on a Windows 7 machine without using LANDesk. I attached the unattend.xml file hoping you guys can point out the correct entry for the local account.  Thanks.