LDMS 8.7 SP3 Answers to common questions Presented by: LANDesk Support June 7th 2007

LDMS 8.7 SP3Answers to common questions

Presented by: LANDesk Support

June 7th 2007

Agenda

Macintosh OSD

LANDesk MetaData

LANDesk Application Virtualization

Question / Answer

2

Macintosh OSD for LDMS 8.7 SP3

Presented by: John Harris

Macintosh OSD

Link to download the Macintosh OSD White Paper for LANDesk Management Suite 8.7 SP3

http://kb.landesk.com/article.asp?article=4225&p=5

4

Macintosh OSD

Differences from 8.6 and 8.7 Mac OSD We use Software Distribution to start the OSD task.

– We no longer use the OSD pane in the LANDesk Console

– This will change in the next release There is no need to install the LANDesk Agent on the

NETBoot image

2

Macintosh OSD

Basics of Macintosh OSD The strategy is to NetBoot the Mac so that the local

drives are not in use and can be captured or modified Mac OS X Server comes with the NetBoot service

and tools to administer the service. Mac OS X server can run on any Mac

A NetBoot image holds the entire Mac OS. While an image may be several GB, the Mac OS is loaded on demand. What isn’t used doesn’t cross the network. Note: this is like the windows vboot state

A standard Xserve on a 10 Mbs switched network can NetBoot up to 50 Macs

3

Macintosh OSD

Starting the OSD Task1. Client gets sent the mac.osd file from the Core Server

2. The client will then unpack the file and run the initiate_OSD script

3. Client will create a folder named the Mac address on the OS X Server Share– This is in the /Users/Shared/LANDesk/Profiles

4. Client will send status to the Core Server

5. Client will gather profile information– Computer name

– Network name

– Default boot partition

– LDMS UUID file

4

Macintosh OSD

Starting the OSD task (cont.)6. Client will copy scripts and log files to the folder on

the OS X Server

7. The client will then set the Netboot option for boot up

8. The client sends status to the Core Server

9. The client reboots to the Netboot image

10.The client reboots

5

Macintosh OSD

Imaging the client machine1. The client now is booted into the NETBoot OS

2. The client runs the deploy_OSD script from the share on the OSX Server

3. Client will run the deploy_OSX script from the share on the OSX Server

4. The workstation image is deployed to the local Partition

5. Set the local boot partition

6. Client sends status to the Core Server

6

Macintosh OSD

Finishing the task1. Client machine reboots to the newly imaged partition

2. A small script will run when the machine boots up to restore the client name and UUID to the client

3. Client deletes the Mac address folder and profile information on the OS X Server

4. Client sends status to the Core Server

5. Task has been completed

7

Macintosh OSD

Deploying a Workstation Image Create a Macintosh Distribution Package with the

following Attributes:– On the General window, set the Package Location field

to the location of the Mac.osd file

Example: http://landesk01/ldlogon/mac/mac.osd

13

Macintosh OSD

Macintosh OSD

Install/Uninstall options for OSD Package On the Install/Uninstall window, set the Command

Line field to the following: – -m ImageName.dmg –a 192.168.1.1 –i NetBootImage

[-f Image_1234567890.nbi] [-d] Syntax for the command line:

– -m ImageName.dmg • The name of the Mac OS X workstation image saved in /Users/Shared/LANDesk/Images/ on the

Xserve.

– -a 192.168.1.1 • The IP Address of the Xserve.

– -i NetBootImage • The name of the NetBoot image on the Xserve.

– -f Image_1234567890.nbi • The name of the NetBoot image file on the Xserve. Required for re-imaging PowerPC based

Macintosh devices. 15

Macintosh OSD

Macintosh OSD

Creating the Task Create a Software Distribution Task with the

Macintosh OSD Distribution Package and the desired Delivery Method

Target the Macintosh OSD Software Distribution Task with the Macintosh devices from Inventory that is to be re-imaged

Schedule the Software Distribution Task– Once the Software Distribution Task is executed, the

targeted Macintosh devices will be rebooted using the NetBoot image on the Xserve and reimaged with the Mac OS X workstation image, as defined in the Distribution Package.

17

Macintosh OSD

17

Macintosh OSD

Notes

This task with run out of band. This means that the task will say that it has partially completed when the task is still active and the results will be updated even if the task is in a completed state.

In the Scheduled Tasks pane there is a result column. This is where the status of the task will be updated. This will not refresh with the auto refresh in Task pane. Click the refresh button to see if there is a new result.

17

LANDesk MetaData

Presented by: Rob Nielsen

Chapter One: Definitions and BNF

Grammar Description and MetaData definitions

LANDesk® Software Confidential

Definitions

BNF– Grammar used to identify how we use the metadata

and reference data within the LANDesk Database. MetaData

– Description of the Data. A logical way of storing information about the data so we know where to go to retrieve it later.

20


Chapter Two: MetaData tables

MetaData table names and their purpose


Tablenames and Purpose

Table names– MetaObjects– MetaAttributes– MetaObjAttrRelations– MetaObjRelations

Purpose– MetaObjects: Contains parent information about

objects in the LANDesk inventory tree.– MetaAttributes: Contains child information about

objects in the LANDesk inventory tree.– MetaObjAttrRelations: Contains relationships between

child objects and parent objects.– MetaObjRelations: Contains relationships between

parent objects within the LANDesk inventory tree.

22


Chapter Three: Example of MetaData use

Applying use of the BNF and the MetaData tables.


Conclusion and examples

Identifying an attribute and its parent. Identify an Object and its children DBREPAIR Brief discussion of unmodeleddata

24



Presented by: Mike Gord


Common questions What is app virtualization and who needs it? How do I get code / support / training? What are the steps to create and deliver a virtual

application with LANDesk 8.7SP3? Where did my changes/files go? How do I handle apps with file associations? Which apps do not work? How do I troubleshoot an app that misbehaves?

2


What is app virtualization? Various virtual layers:

– Hardware (ie, Intel VT, AMD Virtualization)– OS (ie, VMware, VirtualPC)– Application (ie, Microsoft Softgrid, Altirus SVS)

LDAPV apps (single EXE) contain a virtual OS– Virtual file system, Virtual registry– Process manager, memory manager, loader, SCM

Application requests are serviced by virtual OS– Over 400 subsystems and APIs replaced– Reads virtual OS first, then system– Writes are stored in a “sandbox”

2


How do I get code / support / training? Eval

– http://www.landesk.com/tools/trial/virtualization.aspx

Forum– http://thinstall.com/thintalk/index.php

Documentation– https://thinstall.com/help/index.php

Demos– http://thinstall.com/sales/demo.php

2


Steps to create / deliver a virtual application Snapshot the application

– Clean PC– Run from network

Build the EXE– Modify Package.ini– Manage build directories– Run build.bat

Create the distribution package(s)– Define location of virtual app storage, icons– Use dependent packages for suites

2


Where did my changes / files go? Sandbox

– %APPDATA% or %THINSTALL_SANDBOX_DIR%– \Thinstall in same dir as EXE causes a local sandbox

Isolation modes– Defined in ##Attributes.ini, registry is defined per value– Full – reads and writes in virtual environment only– Merged – reads and writes to both– Write Copy – reads both, writes to sandbox– Defaults

Merged – My Documents, Desktop Full – Directories created by app Write Copy – All other directories

2


How do I handle apps with file associations? File type association must be added to the system

registry to point to virtual EXE files on a per-user or per-machine basis.

http://thinstall.com/thintalk/viewtopic.php?t=165 Insert .VBS files in same dir as package.ini

– Use function callbacks to control execution– Function OnFirstParentStart– Function OnFirstParentExit– Function OnLastProcessExit

Rebuild the app

2


Which apps do not work? Applications requiring installation of kernel-mode

device drivers (ODBC drivers will work because they are user-mode)

Products such as anti-virus and personal firewalls Scanner drivers and printer drivers VPN clients

2


How do I troubleshoot misbehaviors? Tracing

– Start Log Monitor– Run the app, kill the app immediately after error– Generate trace file– Scroll to the bottom and read the Potential Errors

Detected section

2