Example 4, Migrating additional application settings, Migrating – Lenovo ThinkPad R50p User Manual

Page 70: Additional, Application, Settings, Example

Advertising
background image

Example

4

The

following

code

example

selects

the

entire

contents

of

the

%USERPROFILE%

folder

that

is

the

User

Profile

Path

of

the

current

logon

user,

excluding

all

files

with

a

.dat

extension

and

“Local

Settings”

subfolder.

<Inclusions>

<IncDescription>

<Description>%USERPROFILE%\</Description>

</IncDescription>

</Inclusions>

<Exclusions>

Migrating

additional

application

settings

To

create

custom

application

files,

you

must

have

a

thorough

knowledge

of

the

application,

including

the

storage

locations

of

customized

settings.

By

default,

System

Migration

Assistant

is

pre-configured

to

migrate

settings

for

several

applications.

You

can

also

create

a

custom

application

file

to

migrate

settings

for

additional

applications.

This

file

must

be

named

application.xml

or

application.smaapp

and

located

in

the

c:\%RR%\Migration\bin\Apps,

where

Apps

specifies

the

application

and

c

is

the

drive

letter

of

the

hard

disk

drive.

Priority

is

given

to

the

application.smaapp

file

when

both

the

application.smaapp

file

and

application.xml

custom

applications

file

of

the

same

application

exist.

To

support

a

new

application,

you

can

copy

an

existing

application

file

and

make

the

necessary

changes.

For

example,

Microsoft_Access.xml

is

an

existing

application

file.

Consider

the

following

points

about

application

files:

v

application.xml

By

default,

only

application.xml

exists.

The

<tag>

enclosed

with

″<!--″

and

″-->″

is

treated

as

comments.

For

example:

<!--Files_From_Folders>

<!-Files_From_Folder>%AppData

Directory%\Adobe\Acrobat\Whapi\*.*

/s

</Files_From_Folder>

<Files_From_Folder>%Personal

Directory%\*.pdf</Files_from_Folder>

</Files_From_folders-->

Each

command

must

be

described

in

a

separate

section.

Each

section

begins

with

a

command

enclosed

by

tags,

for

example,

<AppInfo>

or

<Install_Directories>.

You

can

enter

one

or

more

fields

in

a

section;

each

field

must

be

on

a

separate

line.

If

the

application

file

contains

syntax

errors,

the

operation

continues

and

writes

the

errors

to

the

log

file.

62

Rescue

and

Recovery

4.2

Deployment

Guide

Advertising