Exclude all files in program files EXCEPT migrate specific extensi

[Andrew King Pit,Pa]

Is it possible to setup rules that will exclude the program files folder, but
still migrate specifc extensions that may be found there? For example, I
would like to exclude the program files folder, but still scan for XLS files
and migrate XLS files from any folder/subfolder of program files. I would
also like to relocate those files to c:\data\migratedProgramFilesData.

Also... I want to migrate any "unknown" folder from any fixed disk. There
are a number of know folders that are excluded, but I want the USMT to
migrate any unexpected folder.

Any ideas?

The only thing I can think of would be to take a fresh image and create a
script to scan the program files folder and create a list of all the default
files and setup a long exclude list to exclude those files... then leave the
overall rule in place to take everything and let the long list of excludes
knock out most of the program files fluff.

So... what I am looking to do is be able to exclude for example c:\program
files\* [*] while also including c:\program files\* [*.xls]. It seems to me
that the XLS files should be migrated but in testing they are not migrated
unless the program files folder exclusion is omitted... in which case I get a
lot of files I do not want.
--
Andy King
Enterprise Software Admin
Pittsburgh, Pa

[Soorya Vamsi]

Directory names take precedence over file extensions.
So, you cannot exclude a folder but migrate xls files in it. But there is a
work around for it.
You can add that particular extension in the miguser.xml file. This will
exactly do, what you require. It will acquire all the specified extension
files from all your disk and migrate no folders and keep it in the
%SYSTEMDRIVE%\data folder.
Please see the last component in the miguser.xml for more details.

For including "unknown" folders, the only way is to include *\* and exclude
"known" folders.

[Andrew King Pit,Pa]

I see those rules, but I would like to keep the directory structure entact,
so that instead of a single folder with lots of files from who knows where,
there woudld be a folder with the files (with the extensions I was looking
for), but still with their original path.

I would like to have all the "program files" folders scanned for
extensions... but I would like to keep the folder structure... but not to
co-mingle the migrated files with the program files folder on the new pc.

Would something like this then in theory accomplish that?

'INclude everything
<include>
<objectSet>
<script>MigXmlHelper.GenerateDrivePatterns ("* [*]", "Fixed")</script>
</objectSet>
</include>

'Exclude program files folders from all drives
<Exclude>
<objectSet>
<script>MigXmlHelper.GenerateDrivePatterns ("\Program Files\* [*]",
"Fixed")</script>
</objectSet>
</Exclude>

'Include *.doc from all folders/subfolders from any fixed drive
<include>
<objectSet>
<script>MigXmlHelper.GenerateDrivePatterns ("* [*.doc]", "Fixed")</script>
</objectSet>
</include>
'Re-home the files to c:\data\migratedProgramFiles
<locationModify
script="MigXmlHelper.RelativeMove('%CSIDL_PROGRAM_FILES%\*','c:\data\migratedProgramFiles')">
<objectSet>
<script>MigXmlHelper.GenerateDrivePatterns ("* [*.doc]", "Fixed")</script>
</objectSet>

With this in mind... that including *.doc will find documents anywhere and
include the documents even if a more detailed folder is excluded... such as
exclude c:\projects
include c:\*\*.doc
...with the result being that c:\progjects\example.doc will be migrated.

I will need to use the unconditional exclude to really exclude folders,
otherwise the files will be found and migrated even in excluded folders. If
I am correct, unless I specify the folder should be re-directed the file will
be migrated to the target computer in the same path. In the miguser.xml file
you suggested I check there is an option to uncomment a relocation option
that will "move" the files to a specific folder..

So the options would be to let them migrate to the same location on the new
pc (default).
Move them to a new location (without any preceeding folder tree)
Re-home them to a new location, which will move the file to a new folder
root, but preserver the folder tree.

Is this more or less correct?

--
Andy King
Enterprise Software Admin
Pittsburgh, Pa

[Andrew King Pit,Pa]

My last post was incorrect.
Excluding a specific folder takes precedence over a specifc file inclusion
(at least in my testing)
So if I include *.txt
and exclude c:\program files\*
Text files are not migrated from program files.

So - I think the safest option would be to include *.*, then exclude folders
you know you want to exclude AND form "top-level" folders where you expect
lots of unknown subfolders exclude extensions you know you do not want.

So for example, I am going to test including *.*, then excluding known
program files subfolders I do not want, and excluding extensions I do NOT
want to migrate from program files. For example exclude progam files\*
[*.dll] And [*.exe].

I'm still thinking about how to re-direct migratred data that is specificly
in program files to a new home - such as data\migratedProgramFiles, such that
an unknown folder on the root will migrate to the root on the target machine,
but a folder inside program files will get migrated to a new location...
minus the file extensions I know I do not want.

--
Andy King
Enterprise Software Admin
Pittsburgh, Pa

[Andrew King Pit,Pa]

Eventually you can figure out many things by yourself.

I was trying to user the generatedrive paths helper script with a
enviornmental variable... apparently this doesn't work. My thought was to
find multiple program files folders if they were to exist on say c: and d:
drives but duh... the enviornmental variables will have the full path
including the drive letter so you cannot use them together. So if you want
to look for a program files folder on multiple drives you will need to use at
least two rules. Such as in the miguser.xml example:

<pattern type="File">%CSIDL_PROGRAM_FILES%\* [*]</pattern>

<script>MigXmlHelper.GenerateDrivePatterns ("\Program Files\* [*]",
"Fixed")</script>

You can see one rule will find the program files folder in its primary
location and the second will find the program files folder on any drive. I
would think that only the second would be necessry?

Also I have stumbled on a number of syntax problems in my own USMT syntax,
maybe you can avoid them.
If you use the generatedrive patterns helper script - envision the return is
[driver letter + colon.] ie c: d: e: etc. So your pattern used along with
the returned drive letter will need to begin with a preceeding backslash.

I don't know/have not figured out yet when to use move vs relative move...
or more specifically when you would use relative move. using move will
"re-root" a file in that the file and the structure in which it sits will be
trasferred to the folder your specify.

[Abhishek Agrawal]

Relative move will create only the part of the source hierarchy while Move
will create full source folder hierarchy.

e.g. if you say "RelativMove("C:\data", "D:\c-data\data\")"
and if you have file c:\data\b\a.txt then the file created will be
"D:\c-data\data\b\a.txt" while in the same case move will create
"D:\c-data\data\data\b\a.txt"

thanks,
Abhi

"Andrew King Pit,Pa" <AndrewK...@discussions.microsoft.com> wrote in
message news:442602E7-55D3-47B8...@microsoft.com...