USMT migrates unwanted executable files

M

m4olivei

I want to use USMT to migrate Desktop Shortcuts, Internet Favorites,
Network Drives and Network Printers only, for our users. I have
accomplished this but at the same time USMT also migrates a number of
executable file which I dont want. Specifically it takes a number of
executables from the c:\winnt\system32 file (ex. calc.exe,
cleanmgr.exe, ping.exe, telnet.exe, etc.). I use only the Sysfiles.inf
file and a custom .inf file I wrote to handle the favorites and
shortcuts. How can I make USMT not migrate these unwanted .exe files?

Thanks,
m4olivei
 
G

glenn fincher

I want to use USMT to migrate Desktop Shortcuts, Internet Favorites,
Network Drives and Network Printers only, for our users. I have
accomplished this but at the same time USMT also migrates a number of
executable file which I dont want. Specifically it takes a number of
executables from the c:\winnt\system32 file (ex. calc.exe,
cleanmgr.exe, ping.exe, telnet.exe, etc.). I use only the Sysfiles.inf
file and a custom .inf file I wrote to handle the favorites and
shortcuts. How can I make USMT not migrate these unwanted .exe files?

From the USMT.CHM help file delivered with USMT:

Executable files (such as Calc.exe, Notepad.exe, Wscript.exe,) and other
files that are not being specified by the .inf rules sometimes get copied
into the store but are not applied to the destination computer.

Cause: This is not an issue with the compressed store. In a uncompressed
store, these files are copied to the store by design because they are needed
for migration calculations on the destination computer. In a uncompressed
store, Scanstate stores all the files that are

1.. pointed to by a shortcut (.lnk file or icon)
2.. used in defining an environment variable in an [Component.Environment]
section
3.. used in a [Component.Detect] section
Scanstate stores these files and performs the calculations on the
destination computer. The calculations are performed on the destination
computer so that if the administrator modifies the store, it does not cause
any previous calculations to be invalid. In addition, the files listed in
the [OSFilesEnvironment.Environment.9X] and
[OSFilesEnvironment.Environment.NT] sections of Usmtdef.inf are also
migrated.
This means that when one of these files points to a large file on a shared
network resource (like an .exe file), Scanstate may copy the file from the
network share to the store location. This might be undesired behavior
because it consumes network bandwidth.

Solution: The only way to prevent the copying of files referenced by
[Component.Environment] or [Component.Detect] sections is to remove these
references. Also, if you do not need to migrate the shortcuts to the files
that are referenced in [OSFilesEnvironment.Environment.9X] and
[OSFilesEnvironment.Environment.NT] sections, you can remove them from
Usmtdef.inf. However, neither of these modifications are supported.
If you want to prevent the copying of a shortcut file or icon to the store,
there is an unsupported modification that will cause shortcuts to be
migrated as normal files. If you choose to do this, it is likely that some
shortcuts will not work on the destination computer. The shortcuts will not
work if the target file that they point to is not there, or if the path
information was not correctly updated.

Hope this helps!

Glenn Fincher

Entirenet, LLC
 
M

m4olivei

Oh man, thanks alot. I hate that documenation so much, seems like just
when you thought you got all you could about it theres hidden details
that you missed.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top