<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Workstation Migration Assistant 1.01</title>
	<atom:link href="http://dcunningham.net/2008/06/11/workstation-migration-assistant-101/feed/" rel="self" type="application/rss+xml" />
	<link>http://dcunningham.net/2008/06/11/workstation-migration-assistant-101/</link>
	<description>Tech Tools and IT Infrastructure thoughts...</description>
	<lastBuildDate>Wed, 10 Mar 2010 23:58:17 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Dan</title>
		<link>http://dcunningham.net/2008/06/11/workstation-migration-assistant-101/comment-page-1/#comment-271</link>
		<dc:creator>Dan</dc:creator>
		<pubDate>Mon, 14 Jul 2008 09:47:47 +0000</pubDate>
		<guid isPermaLink="false">http://dcunningham.net/?p=83#comment-271</guid>
		<description>Eli,

You don&#039;t have the .NET Framework 2.0 installed. As per the ReadMe file:

&lt;strong&gt;Please note that the Workstation Migration Assistant requires the Microsoft .NET Framework 2.0 to function. If you don’t have it installed, you’ll receive an error when you try to run WMA&lt;/strong&gt;

Dan</description>
		<content:encoded><![CDATA[<p>Eli,</p>
<p>You don&#8217;t have the .NET Framework 2.0 installed. As per the ReadMe file:</p>
<p><strong>Please note that the Workstation Migration Assistant requires the Microsoft .NET Framework 2.0 to function. If you don’t have it installed, you’ll receive an error when you try to run WMA</strong></p>
<p>Dan</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan</title>
		<link>http://dcunningham.net/2008/06/11/workstation-migration-assistant-101/comment-page-1/#comment-270</link>
		<dc:creator>Dan</dc:creator>
		<pubDate>Mon, 14 Jul 2008 09:46:19 +0000</pubDate>
		<guid isPermaLink="false">http://dcunningham.net/?p=83#comment-270</guid>
		<description>Doug,

I&#039;ll see what I can do about updating the documentation more.

Regarding the other items:
- Changing the path layout would undermine the automatic detection aspect of the Restore. It&#039;s possible to match the username from backup to restore (since it would be the same user performing both), but computer-name could change, and the date *definitely* could change. Maybe it&#039;s something I&#039;ll investigate in the future but right now, I want to make the app as simple to use as possible, removing as much complication as possible.
- Again, being able to select one or all profiles keeps things simple, and definitive exclusions can still be made in the .Exe.Config file. Something I&#039;ll look into in the future maybe.
- Exclusion of accounts older than a specified date is something I&#039;ll definitely put in the next version. Forgot about it, thanks for pointing it out.

Running WMA from the Network is already possible, and is in the ReadMe file, but I didn&#039;t clarify about the USMT part:

&lt;strong&gt;Extract the files to a local folder. It IS possible to run WMA from a network location, however this requires modifying the .NET security restrictions on each workstation you intend to run on. This can be done by running the following command from an Administrator Elevated command-prompt:

&quot;C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\caspol&quot; -quiet -m -ag &quot;LocalIntranet_Zone&quot; -url &quot;\\UNCPATH\WMA\App\*&quot; FullTrust -n &quot;Workstation Migration Assistant Assembly&quot; -d &quot;Grants full trust&quot;

Where \\UNCPATH\WMA\App is the full path to the Workstation Migration Assistant&lt;/strong&gt;

One this is done, just copy the local USMT folder to the same folder and it won&#039;t need to be installed on every machine.

Cheers, Dan</description>
		<content:encoded><![CDATA[<p>Doug,</p>
<p>I&#8217;ll see what I can do about updating the documentation more.</p>
<p>Regarding the other items:<br />
- Changing the path layout would undermine the automatic detection aspect of the Restore. It&#8217;s possible to match the username from backup to restore (since it would be the same user performing both), but computer-name could change, and the date *definitely* could change. Maybe it&#8217;s something I&#8217;ll investigate in the future but right now, I want to make the app as simple to use as possible, removing as much complication as possible.<br />
- Again, being able to select one or all profiles keeps things simple, and definitive exclusions can still be made in the .Exe.Config file. Something I&#8217;ll look into in the future maybe.<br />
- Exclusion of accounts older than a specified date is something I&#8217;ll definitely put in the next version. Forgot about it, thanks for pointing it out.</p>
<p>Running WMA from the Network is already possible, and is in the ReadMe file, but I didn&#8217;t clarify about the USMT part:</p>
<p><strong>Extract the files to a local folder. It IS possible to run WMA from a network location, however this requires modifying the .NET security restrictions on each workstation you intend to run on. This can be done by running the following command from an Administrator Elevated command-prompt:</p>
<p>&#8220;C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\caspol&#8221; -quiet -m -ag &#8220;LocalIntranet_Zone&#8221; -url &#8220;\\UNCPATH\WMA\App\*&#8221; FullTrust -n &#8220;Workstation Migration Assistant Assembly&#8221; -d &#8220;Grants full trust&#8221;</p>
<p>Where \\UNCPATH\WMA\App is the full path to the Workstation Migration Assistant</strong></p>
<p>One this is done, just copy the local USMT folder to the same folder and it won&#8217;t need to be installed on every machine.</p>
<p>Cheers, Dan</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan</title>
		<link>http://dcunningham.net/2008/06/11/workstation-migration-assistant-101/comment-page-1/#comment-269</link>
		<dc:creator>Dan</dc:creator>
		<pubDate>Mon, 14 Jul 2008 09:35:34 +0000</pubDate>
		<guid isPermaLink="false">http://dcunningham.net/?p=83#comment-269</guid>
		<description>Arthur,

- Click Start &gt; Run, type Notepad &quot;C:\WMA\MigAssistant.Exe.Config&quot; where WMA is your WMA folder.
- Look for: &lt;code&gt;MigrationMaxSize&lt;/code&gt;
- Change the value from 20480 to something higher, 81920 is around 80GB
- If you need to change the storage location...
- Look for: &lt;code&gt;MigrationNetworkLocation&lt;/code&gt;
- Change the value to the required path

If a USB drive is attached, it will automatically be detected and you will be asked if you want to use it as the storage device, unless it 2GB or below in size. This is to prevent the prompt appearing when a small USB device is attached, like a Flash key.

Dan</description>
		<content:encoded><![CDATA[<p>Arthur,</p>
<p>- Click Start > Run, type Notepad &#8220;C:\WMA\MigAssistant.Exe.Config&#8221; where WMA is your WMA folder.<br />
- Look for: <code>MigrationMaxSize</code><br />
- Change the value from 20480 to something higher, 81920 is around 80GB<br />
- If you need to change the storage location&#8230;<br />
- Look for: <code>MigrationNetworkLocation</code><br />
- Change the value to the required path</p>
<p>If a USB drive is attached, it will automatically be detected and you will be asked if you want to use it as the storage device, unless it 2GB or below in size. This is to prevent the prompt appearing when a small USB device is attached, like a Flash key.</p>
<p>Dan</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: eli</title>
		<link>http://dcunningham.net/2008/06/11/workstation-migration-assistant-101/comment-page-1/#comment-268</link>
		<dc:creator>eli</dc:creator>
		<pubDate>Sun, 13 Jul 2008 10:03:45 +0000</pubDate>
		<guid isPermaLink="false">http://dcunningham.net/?p=83#comment-268</guid>
		<description>not working - Application Error
The application failed to initialize properly (0x0000135). Click ok to terminate the application


xp sp3 english</description>
		<content:encoded><![CDATA[<p>not working &#8211; Application Error<br />
The application failed to initialize properly (0&#215;0000135). Click ok to terminate the application</p>
<p>xp sp3 english</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Doug MacKenzie</title>
		<link>http://dcunningham.net/2008/06/11/workstation-migration-assistant-101/comment-page-1/#comment-267</link>
		<dc:creator>Doug MacKenzie</dc:creator>
		<pubDate>Sat, 12 Jul 2008 21:50:18 +0000</pubDate>
		<guid isPermaLink="false">http://dcunningham.net/?p=83#comment-267</guid>
		<description>Hello Dan

I am looking at you application to streamline the USMT tool, as you say it is very criptic to use and documentation leaves much to be desired. I have been using version 2.6 for a few years now as the means to migrate users data as our company refreshs computers. On average 150 to 600 oomputers a year. We have scripted the program with batch files and it works. The GUI of yours brings the use to a new level. I am not sure about some of the settings in your config file and do echo the other users that a bit more explanation would be nice. I changed the config file and migrated profiles as large as 26 gig without a problem.
A couple of comments.
Would it be possible to have a setting to allow for the way the profile path is created.
 We currently use Store\Date\ComputerName\USMT3

The option to select other that one or all profiles would be great.

As we have many shared units that need 5-8 profiles backed up and all on these machines is not practical as they can have as many as 60 profiles on them.
We currently use the days feature to limit the profiles selected. This is a workaround and not the best solution.
The other feature that I see would be great if possible would be for your application to run from a network installed location of USMT and not reqire USMT to be installed on each computer.

Thanks for all your effort and it is a great tool.

Doug MacKenzie</description>
		<content:encoded><![CDATA[<p>Hello Dan</p>
<p>I am looking at you application to streamline the USMT tool, as you say it is very criptic to use and documentation leaves much to be desired. I have been using version 2.6 for a few years now as the means to migrate users data as our company refreshs computers. On average 150 to 600 oomputers a year. We have scripted the program with batch files and it works. The GUI of yours brings the use to a new level. I am not sure about some of the settings in your config file and do echo the other users that a bit more explanation would be nice. I changed the config file and migrated profiles as large as 26 gig without a problem.<br />
A couple of comments.<br />
Would it be possible to have a setting to allow for the way the profile path is created.<br />
 We currently use Store\Date\ComputerName\USMT3</p>
<p>The option to select other that one or all profiles would be great.</p>
<p>As we have many shared units that need 5-8 profiles backed up and all on these machines is not practical as they can have as many as 60 profiles on them.<br />
We currently use the days feature to limit the profiles selected. This is a workaround and not the best solution.<br />
The other feature that I see would be great if possible would be for your application to run from a network installed location of USMT and not reqire USMT to be installed on each computer.</p>
<p>Thanks for all your effort and it is a great tool.</p>
<p>Doug MacKenzie</p>
]]></content:encoded>
	</item>
</channel>
</rss>
