Desktop wallpaper is not migrating.

Jeff Gulack

unread,

Dec 4, 2007, 6:02:01 PM12/4/07

to

I have successfully migrated user documents and setting using
USMTscanstate/loadstate, but the target machine does not receive the source
wallpaper.

Using USMT 3.0.1.
source - XP sp2
target - XP sp2

Terry Dolan [MSFT]

unread,

Dec 4, 2007, 8:24:00 PM12/4/07

to

Can you provide any more information? Are you running USMT with the /c
switch? Is there anything in the log file that indicates that the wallpaper
couldn't be copied?

Pedro de Paula

unread,

Dec 5, 2007, 10:20:05 AM12/5/07

to

Is there any group policy in your lab/production environment that is
preventing the correct restore settings? Have you written any components in
the XML control files?

Regards

--
Pedro de Paula
Consultant
Portugal

Jeff Gulack

unread,

Dec 5, 2007, 2:57:12 PM12/5/07

to

I am not using /c . And in regards to that, the scan does not error out.

Th scanstate log file has a line item that seems to identify the file as
being migrated successfully. The file is being used on the source machine as
the current wallpaper during the scan.

The loadstate log, which I'm looking at for the first time has nothing but
warnings, but I believe they are not specific, rather general.
The first one is -
"State data store failed calling CoInitializeEx in apartment-threaded mode."
I won't list the rest at this point.

Let me know if I can provide anything further.
Thx.

Jeff Gulack

unread,

Dec 5, 2007, 2:59:06 PM12/5/07

to

There are no group policies that I believe would prevent the setting being
restored.

I have not written anything to the basic migration files. In fact, USMT is
new to me and I'm trying to get to know the process by using all the defaults.

Matt

unread,

Dec 5, 2007, 3:14:01 PM12/5/07

to

This may be a stupid suggestion, but did you try to reboot after the loadstate?
Matt

Jeff Gulack

unread,

Dec 5, 2007, 4:12:00 PM12/5/07

to

Yes, I did.

I have since found that the wallpaper file migrates. It just does not get
set as the current wallpaper. I just have the beautiful "grass and sky"
thing (bliss) that was there before I ran loadstate.

Terry Dolan [MSFT]

unread,

Dec 5, 2007, 7:53:00 PM12/5/07

to

You should try running scanstate and loadstate with the logging verbosity set
to 13. /v:13, and then look through the log file to see if there is a
warning that this didn't get set properly.

Also, if you are running loadstate or scanstate with the /c switch, a
failure to gather or apply the wallpaper setting would likely not stop the
migration.

Jeff Gulack

unread,

Dec 6, 2007, 11:23:03 AM12/6/07

to

I am using /v:13. The log file only shows the successful migration of the
wallpaper file. I don't see anything related to applying the file as the
current wallpaper.

As for /c. I am not using this switch. At this point, while I'm testing
and learning how to use USMT I want to see as much detail as possible
including failures.

ArthurH

unread,

Dec 17, 2007, 4:17:01 AM12/17/07

to

I have something quite similar. But it applies to cookies not being migrated.

I know cookies are not migrated by default with USMT, so I create a
migcookies.xml and it works well. There are no syntax errors in that and the
loadstate logfile states the xml file is readable. The cookies are
transferred too, but they are not "recognized" as the cookies for the profile
I migrated.

In the log file I have a couple of these lines:
Info [0x080000] V2VArbitrate: Arbitrating migration unit
<eh004076>\Cookies (CMXEAgent)
Info [0x080000] V2VArbitrate: Source migration unit
<eh004076>\Cookies (CMXEAgent) has an equivalent on the destination
destination

If I run loadstate.exe again, with exactly the same options, the files are
migrated again and the cookies are in use as I expect them to be. But I think
I should not be required to run it twice.

This is the command I am running for loadstate:
C:\WINDOWS\usmt301\LOADST~1.EXE c:\temp\<userid>
/config:C:\windows\usmt301\config.xml /i:miguser.xml /i:migsys.xml
/i:migapp.xml /i:testmig.xml /i:Migcookies.xml /lac /v:13
/l:C:\APPS\LOGS\loadstate.log

Does anybody have an idea?

airs...@gmail.com

unread,

Jan 16, 2008, 5:50:03 PM1/16/08

to

I'm experiencing a similar problem, however, my settings and such do
get transferred over but the wallpaper does not. In my case what
isn't coming over is the wallpaper file itself, located on an old 2000
box under c:\winnt. The registry setting for the wallpaper does come
over, but Vista displays a blank screen because that file does not
exist in the new OS. Any ideas how to get it to come over? I could
always script it as part of the USMT process, but I think USMT should
be smart enough to do it itself.