1 2 3 Previous Next 32 Replies Latest reply on Jul 6, 2009 6:09 AM by jan.buelens

    Can unattended install work with VMWare client?

    Employee

      Dear All,

       

      My apologies if the question sounds too stupid, as I am new to provisioning.

       

      I have downloaded some XP provision templates from the community and am now testing on the them. The job stay at the "Pending" stage even I force it to run. I am trying to do unattended install on a VMWare client. Is the "bare metal" need to be a physical hardware in order to do unattened install?

       

      If I look at my VMWare client, it stay at the the LANDesk title screen after loading the RAMDisk.....

       

      Thanks and regards,

      Winnie

        • 1. Re: Can unattended install work with VMWare client?
          ahe Expert

          Hello Winnie,

           

          did you create a virtual harddisk before? I've had the same problem in the past as I forgot to create a harddisk...

           

          Regards

          Axel

          • 2. Re: Can unattended install work with VMWare client?
            Employee

            Hi Axel,

             

            I think the harddisk has been created during the creation of the new VM?

             

            If I go back to the console, I find the VM machine is displayed as offline. (see attached screen shot).

             

            I added a new device in the bare metal folder, using the MAC address. Do you think I am missing something?

             

            Thanks and regards,

            Winnie

            • 3. Re: Can unattended install work with VMWare client?
              ahe Expert

              Hello Winnie,

               

              if you boot your VM with WinPE, open "New Console" in the "GO" button and check if a drive C: exist and check the size of the drive.

               

              In my first tests (for a while...) VM creates the harddisk later and my installation script (Provisioning didn't exist at this time :-)) couldn't create a partition...

               

              Regards

              Axel

              • 4. Re: Can unattended install work with VMWare client?
                Employee

                Hi Axel,

                 

                You are right, the system cannot find C: when I try to change drive. What should I do? I tried selecting "MSDOS" and "Other" as the OS type when creating VMImage, but the result is the same.

                 

                The OS template I used has some Pre-OS script and those scripts are suppose to delete all partition and re-create a c:, but as LD never detect the VMImage online, so I guess none of them has run.

                 

                What did you do in your case to make C: "see-able"?

                 

                Many thanks!

                 

                Thanks and regards,

                Winnie

                • 5. Re: Can unattended install work with VMWare client?
                  ahe Expert

                  Hello Winnie,

                   

                  in your VM machine settings you can create a disk or change the size of your VM Hard Disk.

                   

                  Try to create a new VM (I use VMware Server 1.0.2) and

                  Typical machine configuration method:

                  if you'll asked in dialog "Specify Disk Capacity" set the "Disk size" and mark "Allocate all disk space now"

                   

                  Custom machine configuration method:

                  Select a Disk:               Create a new virtual disk

                  Select a Disk Type:       IDE

                  Specify Disk Capacity:   Allocate all disk space now  

                   

                  Normally a disk will be created with your wished size. After boot WinPE you can check the existence with diskpart:

                   

                  • Start WinPE

                  • Open Console

                  • start "diskpart"    -> the diskpart environment will be started

                  • write "list disk"

                  What do you see?

                  If you see nothing, the harddisk won't be found. If you see something like this

                   

                  X:\i386\system32>diskpart

                  Microsoft DiskPart version 5.2.3790.1830
                  Copyright (C) 1999-2001 Microsoft Corporation.
                  On computer: MININT-TEL36FBI

                  DISKPART> list disk

                    Disk ###  Status      Size     Free     Dyn  Gpt
                    --------  ----------  -------  -------  ---  ---
                    Disk 0    Online        13 GB      0 B

                   

                  the harddisk is found...

                   

                  Test to create a partition:

                  • create a diskpart config file (this will create a 20GB partition) and store it somewhere in your net:


                  select disk=0
                  clean
                  create partition primary size=20480
                  assign letter=c
                  active
                  create partition extended
                  create partition logical
                  • map the drive in your WinPE console

                  • start in your PE console diskpart with parameter: *diskpart /s* <networkpath>\+ScriptName.txt+

                   

                  If you can create a partition and if you can map a network dirve, the provisioning task should write on the harddisk too...

                   

                  Regards

                  Axel

                  • 6. Re: Can unattended install work with VMWare client?
                    Employee

                    Hi Axel,

                     

                    Thanks for the detailed explanation and sorry for keep asking....

                     

                    I used the typical method as you mentioned to create a new VMImage and is able to see the disk 0. (see screen shot) I can also create the partition. But in the LD console, the job is still display as "delayed".

                     

                    For the last 2 step you mentioned below,

                    • map the drive in your WinPE console

                    • start in your PE console diskpart with parameter: *diskpart /s* <networkpath>\+ScriptName.txt+

                    Where is the network path I can find the script?

                     

                    Thanks again.

                    Winnie

                    • 7. Re: Can unattended install work with VMWare client?
                      ahe Expert

                      Hello Winnie,

                       

                      you can use a config/answer file, like "ScriptName.txt", for diskpart to create partitions...

                       

                      It was a example, if you've created a file and stored it in net, because in PE image is none :-)

                       

                      But you can use the commands from the listed textfile in command line to create a partition too.

                       

                      Also another question:

                      Is it possible to map a network drive from your PE boot VM session?

                       

                      Regards

                      Axel

                      • 8. Re: Can unattended install work with VMWare client?
                        Employee

                        Hi Axel,

                         

                        I am using the build in Pre-OS interface in LD to do the partitioning, thus I don't have a separte script for partitioning.

                         

                        And the answer to your second question is "yes". I can manually map a drive to the OS installation source from the VMImage.

                         

                        I remember if I do OS deployment of images, the LD multicast GUI pop up indicating communication between the PXE representive and the VM Image is success. Just wondering why the VMImage seems to be un-detectable from scripted install. From the schedule job GUI, it always appears as offine.

                         

                        Thanks and regards,

                        Winnie

                        • 9. Re: Can unattended install work with VMWare client?
                          Employee

                          What's (not) happening has nothing to do with whether or not the client's hard drive exists or is visible. If there's something wrong with the client's hard drive, that would be a good reason for the task to fail once it gets started. But it is no reason for the task not to get started.

                           

                          You "remember" how things worked with OSD. I suspect that's your problem. Provisioning is not OSD. There are usage modes that, based on your OSD experience, you may expect to work, but that don't. One test you might try if you expect OSD-like behaviour is following: manually boot client into WinPE, schedule provisioning task, see what happens. Answer: nothing will happen - at least, not until you reboot.

                           

                          Here's a test that will get you on the right track. First, to eliminate any doubts in your mind that any troubles might be to do with the contents of the template, create the most trivial tempate possible: boot environment = WinPE, target OS = WinPE, single action in "OS installation" section = execute program, notepad. Rright-click the template, schedule template, drag client (perhaps manually created "bare metal" item based on mac address) to it, start now. Now boot the client. Press F12 in the usual way. At the point where you would normally press F8, don't. The machine should automatically go into WinPE / provisioning mode and run the tempale.

                           

                          Further notes:

                          1. The fact that the agent remains invisible from the console while the machine is running WinPE is normal.

                          2. The fact that the task status is shown as "delayed" is also normal.

                          • 10. Re: Can unattended install work with VMWare client?
                            Employee

                            Hi Jan,

                             

                            I am setting up the test you suggested. When I recreate a new template, I can select the boot environment to WinPE, however, I cannot find WinPE as a choice in the target OS drop down list (see screenshot). I tried to choose WinXP Pro or just Windows. In both cases, I didn't get notepad to run.

                             

                            As usual, from the scheduled job list from console, the job is shown as "delayed". Where should I go for trouble shooting the case? I looked at the provision.log at the server and have changed the log level to debug. There is no error message. Here is what the log file shows,

                             

                            STARTUP BareMetalServer DEBUGGING 6/15/2009 11:47:28 AM Logging started
                            STARTUP BareMetalServerScannerRemoteProxy DEBUGGING 6/15/2009 11:48:15 AM Logging started
                            STARTUP ProvisioningSecure DEBUGGING 6/15/2009 11:48:15 AM Logging started
                            INFO ProvisioningSecure  6/15/2009 11:48:15 AM  : AddBareMetalServer
                            INFO ProvisioningSecure  6/15/2009 11:48:15 AM  :     Server Identifiers:
                            INFO ProvisioningSecure  6/15/2009 11:48:15 AM  :          MACAddress 000C29054985
                            STARTUP ProvUserValidator DEBUGGING 6/15/2009 11:48:15 AM Logging started
                            INFO ProvUserValidator  6/15/2009 11:48:15 AM  : ProvUserValidator.ProvUserValidator(), strAuth = Negotiate TlRMTVNTUAADAAAAGAAYAHgAAAAYABgAkAAAAAAAAABIAAAAGgAaAEgAAAAWABYAYgAAABAAEACoAAAANYKI4gUCzg4AAAAPYQBkAG0AaQBuAGkAcwB0AHIAYQB0AG8AcgBBAFYATwBMAEEATgBEAEUAUwBLADIALTlralh/kI8AAAAAAAAAAAAAAAAAAAAAxUTDoJ220CF9Mdecmf6muz/Goce4eEsuYEklD5og6XMgaAEInglDxg==
                            STARTUP BareMetalServer DEBUGGING 6/15/2009 11:48:15 AM Logging started
                            STARTUP BareMetalServerScanner DEBUGGING 6/15/2009 11:48:15 AM Logging started
                            STARTUP PROV_SCHEDULE DEBUGGING 6/15/2009 11:49:34 AM Logging started
                            INFO PROV_SCHEDULE  6/15/2009 11:49:35 AM  : Selected template idn: 131
                            INFO PROV_SCHEDULE  6/15/2009 11:49:35 AM  : Delivery method IDN: 9
                            INFO PROV_SCHEDULE  6/15/2009 11:49:35 AM  : Making sure template 131 is flat ...
                            INFO PROV_SCHEDULE  6/15/2009 11:49:35 AM  : Flattened template idn: 131
                            STARTUP PAction_Execute_file DEBUGGING 6/15/2009 11:49:35 AM Logging started
                            INFO PROV_SCHEDULE  6/15/2009 11:49:36 AM  : Frozen template idn: 134
                            INFO PROV_SCHEDULE  6/15/2009 11:49:36 AM  : iterating through 1 computer(s) ...
                            INFO PROV_SCHEDULE  6/15/2009 11:49:36 AM  : Checking indicates machines will NOT need prodding
                            INFO PROV_SCHEDULE  6/15/2009 11:49:36 AM  : computer 41 not busy; creating provisioning job
                            STARTUP PHistoryTask DEBUGGING 6/15/2009 11:49:36 AM Logging started
                            STARTUP PHistoryEntry DEBUGGING 6/15/2009 11:49:36 AM Logging started
                            INFO PROV_SCHEDULE  6/15/2009 11:49:38 AM  : Status: successfully created history task History task idn: 23
                            INFO PROV_SCHEDULE  6/15/2009 11:49:38 AM  : Removing Pxe Reservation for device 41
                            STARTUP DHCPServerInterface DEBUGGING 6/15/2009 11:49:38 AM Logging started
                            STARTUP DHCPServerInterface DEBUGGING 6/15/2009 11:49:38 AM Logging started
                            INFO PROV_SCHEDULE  6/15/2009 11:49:38 AM  : Made PXE reservation
                            INFO PROV_SCHEDULE  6/15/2009 11:49:38 AM  : Finished iterating through 1 computer(s)
                            STARTUP DHCPServerInterface DEBUGGING 6/15/2009 11:49:38 AM Logging started
                            DEBUGGING DHCPServerInterface  6/15/2009 11:49:38 AM  : Business.DHCPServerInterface.InitializePXEServerList:  list.Count: 1
                            DEBUGGING DHCPServerInterface  6/15/2009 11:49:39 AM  : Business.DHCPServerInterface.getPXEServerList:  Destination pxe\system path: C:\Program Files\LANDesk\PXE\system
                            VERBOSE DHCPServerInterface  6/15/2009 11:49:40 AM  : Configuring PXE server named [AVOLANDESK2] at address [192.168.183.134]
                            DEBUGGING DHCPServerInterface  6/15/2009 11:49:40 AM  : Business.DHCPServerInterface.InitializePXETargetList: Begin
                            DEBUGGING DHCPServerInterface  6/15/2009 11:49:40 AM  : Business.DHCPServerInterface.InitializePXETargetList: Computer_Idn: 41
                            DEBUGGING DHCPServerInterface  6/15/2009 11:49:40 AM  : Business.DHCPServerInterface.InitializePXETargetList: Got PXEConfig
                            DEBUGGING DHCPServerInterface  6/15/2009 11:49:40 AM  : In DHCPServerInterface, in setDevicePXEOptions(), m_PXEServerList #: 1
                            DEBUGGING DHCPServerInterface  6/15/2009 11:49:40 AM  : In DHCPServerInterface, in setDevicePXEOptions(), BuildLDPXEConfigXMLs() done
                            VERBOSE DHCPServerInterface  6/15/2009 11:49:42 AM  : Business.DHCPServerInterface.ConfigureLDPXE: PutFile rv: 0  for \\AVOLANDESK2\ldmain\Provisioning\TargetLists\AVOLANDESK2-pxeconfig.xml and C:\Program Files\LANDesk\PXE\system\pxeconfig.xml
                            VERBOSE DHCPServerInterface  6/15/2009 11:49:44 AM  : Business.DHCPServerInterface.ConfigureLDPXE: RemoteExeucte rv: 0  for C:\Program Files\LANDesk\PXE\system\PXECleanup.exe
                            VERBOSE DHCPServerInterface  6/15/2009 11:49:44 AM  : In DHCPServerInterface, setDevicePXEOptions() return: 0
                            INFO PROV_SCHEDULE  6/15/2009 11:49:44 AM  : PXE configuration has been pushed to all servers
                            INFO PROV_SCHEDULE  6/15/2009 11:49:44 AM  : Status: PULL_AVAILABLE, prov_schedule ends  --------------------

                             

                            Any idea?

                             

                            Best regards,

                            Winnie

                            • 11. Re: Can unattended install work with VMWare client?
                              Specialist

                              Based on what I am seeing in the log, I think there is still some confustion on how the provisioning job is going to start.  Keep in mind as Jan said, OSD and provisioning funciton in different ways.  The main reason for this is Ldprovision.exe.  This is a client-side application that will run on the target machine is is the piece responsible for managing the provisioning tasks.  You have to get ldprovision to "call" the core in order for a provisioning task to run.  There are two ways you can do this:

                               

                              1. On the console, create a task and add the machine to the newly created task and run the task.  This will place the task in a pending state.  Once the task is running, reboot the target machine into a network boot. At this point it should automatically load the ramdisk and start the process.

                               

                              2. Do not schedule the taks ahead of time.  Boot the machine into PXE and choose WinPE Provisioning from the list of PXE options.  Once in WinPE, ldprovision.exe will launch and prompt for credentials.  Enter in credentials for a console user with admin or Provisionoing Scheduling rights.   A list of templates will be made available.  Choose the templat you wish to run and the delivery method and hit OK.  A task will be created on the core and the requesting machine will be targeted.

                               

                              It is also likely that you have tried running this template multiple times and the core believes that there is another provisioning task pendging for this machine.  Right-click on the target machine in the device view and choose "View Provisioning History".  If there are any tasks that show they are "running", then the core is going to hang on trying to schedule any additional tasks to this machine.  To resolve the issue, delete the machine from the inventory and re-import your bare-metal device.  Run the template again with one of the two methods above.

                               

                              Hopefully this works for you.

                              • 12. Re: Can unattended install work with VMWare client?
                                Employee

                                Sorry, I had meant target OS = WinXP...

                                 

                                So notepad didn't come up. But you don't say what it is that you did that made you expect to see notepad come up. Which leaves room to speculate that maybe, you have your target machine sitting ready, presumably booted into WinPE, and you expect something to happen when you "start now". Wrong expectation. No matter what state your client is in (on-line, offline, running an agent, running WinPE), no matter whether the delivery method is policy or policy-supported push, nothing is suposed to happen at the time you "start now". You only expect something to happen when you next reboot the target into WinPE.

                                 

                                Your log is consistent with my speculation: I think I can see a login (i.e. the kind of login you get when you boot a client into WinPE/provisioning), followed by a provisioning task being targeted and scheduled (presumably "start now"). The last line says "pull available", i.e. the core server is waiting the hear from the target. But nothing further happens in the log. That next reboot, which is what would finally have triggered the task to run and the notepad to come up, would have been visible in the log if it happened. But the log doesn't show it.

                                • 13. Re: Can unattended install work with VMWare client?
                                  Specialist

                                  One other thing that I forgot to add:

                                   

                                  The template section will determine what environment the action will run in.

                                   

                                  For instance, System Migration and System Configuration actions take place in the original or target OS. Most time this would be Windows.  However, these actions only run if the target machine has a LANDesk client installed.

                                   

                                  If you want to run actions that take place in WinPE, then the template must have the actions added in the Pre-OS, OS, or Post-OS installation sections.  Keep this in mind when creating your template.

                                  • 14. Re: Can unattended install work with VMWare client?
                                    Employee

                                    Hi Jan,

                                     

                                    Actually I have tried to reboot a few times, but nothing happened and the client always stop at the LD title page after loading at RAMDISK image. And from the provision.log, I can only see these lines whenever the machine is rebooted.

                                     

                                    INFO PROV_SCHEDULE  6/16/2009 11:03:05 AM  : PXE configuration has been pushed to all servers
                                    INFO PROV_SCHEDULE  6/16/2009 11:03:05 AM  : Status: PULL_AVAILABLE, prov_schedule ends  --------------------
                                    STARTUP PHistoryTask DEBUGGING 6/16/2009 11:07:48 AM Logging started
                                    STARTUP PHistoryEntry DEBUGGING 6/16/2009 11:07:48 AM Logging started
                                    STARTUP PHistoryTask DEBUGGING 6/16/2009 11:13:26 AM Logging started
                                    STARTUP PHistoryEntry DEBUGGING 6/16/2009 11:13:27 AM Logging started
                                    STARTUP PHistoryTask DEBUGGING 6/16/2009 11:21:01 AM Logging started
                                    STARTUP PHistoryEntry DEBUGGING 6/16/2009 11:21:01 AM Logging started

                                     

                                    The 2 line repeats whenever the machine is rebooted.

                                     

                                    If I view the provision history, I can see the agent is always "waiting" (see the attached screen shot). Any idea when it does not continue after the reboot?

                                     

                                    Thanks and regards,

                                    Winnie

                                    1 2 3 Previous Next