<?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: Logged on with a temporary profile</title>
	<atom:link href="http://www.1stbyte.com/2009/07/01/logged-on-with-a-temporary-profile/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.1stbyte.com/2009/07/01/logged-on-with-a-temporary-profile/</link>
	<description>Company site for Greg Fischer { GregTheGeek }</description>
	<lastBuildDate>Sun, 05 Feb 2012 15:01:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Shawn</title>
		<link>http://www.1stbyte.com/2009/07/01/logged-on-with-a-temporary-profile/comment-page-1/#comment-921</link>
		<dc:creator>Shawn</dc:creator>
		<pubDate>Mon, 23 May 2011 05:36:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.1stbyte.com/?p=173#comment-921</guid>
		<description>Phoenix:

This applies only to Active Directory and New Roaming Profiles:

I just ran into this exact same problem: after setting up the profile
 path in Active Directory, the user recieves an error that they are 
using a temporary profile.  This ultimatly had to do with the &quot;profile 
path&quot; I had entered &quot;\sbserverusershares%username%&quot;.

The server will try to append and extension indicating the 
profile/windows version to the path, in my case it was &quot;.V2&quot; making the 
path &quot;\sbserverusersharesjohn.V2&quot;.  Unfortunately, the user does not 
have permission to modify the &quot;UserShares&quot; folder
 so a temporary profile was used for that session.  This can be resolved
 by adding a trailing backslash making the profile path a folder named 
&quot;\sbserverusersharesjohn.V2&quot;.  To make thing more windows like, I 
ultimately made the profile path
 &quot;\sbserverusershares%username%PROFILE&quot; and windows translated this 
to &quot;\sbserverusersharesjohnPROFILE.V2&quot;.

This applies to existing roaming profile that started acting up:

For roaming profiles that started acting up, you will be heading for 
more of an up hill battle: the profile can exist on multiple machines, 
and the server, and will replicate from machine to server to machine.  
You will want to rename the user profile
 folder on the server or current workstation as this is the current 
copy.  From there, go to each and every workstation that has the profile
 in question log in, and rename it.  Once the use logs in again, it will
 create a fresh new profile. 
 Copy his documents, favorites, PSTs, and so on back into his new 
profile.  Make sure to do this on all machines that have a copy of the 
profile, otherwise a login on the wrong machine could corrupt his 
profile again.

Workgroup/standalone computers:

This is usually due to a corrupt user profile, corrupt default 
profile, corrupt user account, file system, or windows problems.  Start 
by renaming the profile and letting windows create a new profile.  Copy 
back the users data.  The second
 step is to rename the users profile directory, delete the user, create a
 new user, and copy the users data back. 

A fatally corrupted file system can be causing user profile issues.  
Run a check disk and retry the proceeding steps.  If that fails, windows
 could be to blame.  But always give web searches a good try before 
blowing away Windows.

 

Shawn Zernik
Internetwork Consulting
 </description>
		<content:encoded><![CDATA[<p>Phoenix:</p>
<p>This applies only to Active Directory and New Roaming Profiles:</p>
<p>I just ran into this exact same problem: after setting up the profile<br />
 path in Active Directory, the user recieves an error that they are<br />
using a temporary profile.  This ultimatly had to do with the &#8220;profile<br />
path&#8221; I had entered &#8220;\sbserverusershares%username%&#8221;.</p>
<p>The server will try to append and extension indicating the<br />
profile/windows version to the path, in my case it was &#8220;.V2&#8243; making the<br />
path &#8220;\sbserverusersharesjohn.V2&#8243;.  Unfortunately, the user does not<br />
have permission to modify the &#8220;UserShares&#8221; folder<br />
 so a temporary profile was used for that session.  This can be resolved<br />
 by adding a trailing backslash making the profile path a folder named<br />
&#8220;\sbserverusersharesjohn.V2&#8243;.  To make thing more windows like, I<br />
ultimately made the profile path<br />
 &#8220;\sbserverusershares%username%PROFILE&#8221; and windows translated this<br />
to &#8220;\sbserverusersharesjohnPROFILE.V2&#8243;.</p>
<p>This applies to existing roaming profile that started acting up:</p>
<p>For roaming profiles that started acting up, you will be heading for<br />
more of an up hill battle: the profile can exist on multiple machines,<br />
and the server, and will replicate from machine to server to machine. <br />
You will want to rename the user profile<br />
 folder on the server or current workstation as this is the current<br />
copy.  From there, go to each and every workstation that has the profile<br />
 in question log in, and rename it.  Once the use logs in again, it will<br />
 create a fresh new profile. <br />
 Copy his documents, favorites, PSTs, and so on back into his new<br />
profile.  Make sure to do this on all machines that have a copy of the<br />
profile, otherwise a login on the wrong machine could corrupt his<br />
profile again.</p>
<p>Workgroup/standalone computers:</p>
<p>This is usually due to a corrupt user profile, corrupt default<br />
profile, corrupt user account, file system, or windows problems.  Start<br />
by renaming the profile and letting windows create a new profile.  Copy<br />
back the users data.  The second<br />
 step is to rename the users profile directory, delete the user, create a<br />
 new user, and copy the users data back. </p>
<p>A fatally corrupted file system can be causing user profile issues. <br />
Run a check disk and retry the proceeding steps.  If that fails, windows<br />
 could be to blame.  But always give web searches a good try before<br />
blowing away Windows.</p>
<p> </p>
<p>Shawn Zernik<br />
Internetwork Consulting<br />
 </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ron</title>
		<link>http://www.1stbyte.com/2009/07/01/logged-on-with-a-temporary-profile/comment-page-1/#comment-429</link>
		<dc:creator>Ron</dc:creator>
		<pubDate>Tue, 25 Aug 2009 19:43:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.1stbyte.com/?p=173#comment-429</guid>
		<description>I am having the same issue. I am running Server 2008 and Windows 7 RC. When I populate the profile path in active directory with \\filesvr\profiles\%username%  - Windows 7 will log on using the temp profile and give the warning. I take out the AD profile path and it will load fine. My issue I NEED roaming profiles! I am stuck and need help please.</description>
		<content:encoded><![CDATA[<p>I am having the same issue. I am running Server 2008 and Windows 7 RC. When I populate the profile path in active directory with \\filesvr\profiles\%username%  &#8211; Windows 7 will log on using the temp profile and give the warning. I take out the AD profile path and it will load fine. My issue I NEED roaming profiles! I am stuck and need help please.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

