- Server 2003 SP1 roaming profiles
- Posted by Patrifick on May 21st, 2006
Hi,
would anybody know how to convert server 2003 roaming profiles to server
2003 with SP1 roaming profiles.
We are creating large upgrade on our network with citrix enviroment. At this
moment we are running servers 2003 without SP1 and roaming profiles are in
the form of a user name. After upgrade the user roaming profiles and changes
its name to "username.forest". The problem begins when users connect to a
server and their profile is downloaded partialy only. Application data and
some other folders are created from scratch. This gives lots of issue for
certain applications to which needs to have particulat setup and is one of
those not downloaded. I have notice that it might have something to do with
ntuser.dat. I have tried to rename the folder but it didn't help as well.
Thank you
patrick
- Posted by Frankster on May 21st, 2006
I believe this renaming may be occurring because a user profile with
<username> already exists on the local box but is not accessible for some
reason. If you rename the existing local <username> profile, then logon, I
believe it will create another profile with the desired name and without the
".xxxxx" extension. However, you may have to then copy the contents of the
old profile into the new profile and set permissions accordingly. Or just
recreate all the profile customizations.
-Frank
"Patrifick" <Patrifick@discussions.microsoft.com> wrote in message
news:21B584C7-097A-48CA-9B01-75FBFE57E83D@microsoft.com...
- Posted by Patrifick on May 21st, 2006
I am afraid I did tried all of those. What I've noticed server 2003 sp1 check
the ntuser.dat if it is not from the current version it will re-create it
self with particular folders
"Frankster" wrote:
- Posted by Frankster on May 21st, 2006
When I upgraded my W2K3 network (with roaming profiles) to SP1 I had no
issue like this. It's hard to believe it is because of SP1. Unless something
in SP1 is not allowing access to the original profiles.
Also note, to test, you would have to delete/rename ALL of the affected
users' profiles on that machine, because if you renamed only the <username>
profile, it would continue to use the *good* <username.forest> profile from
before (rename/delete that one too).
-Frank
"Patrifick" <Patrifick@discussions.microsoft.com> wrote in message
news:2D6D5A11-DC5D-4ECF-A31A-AF7A76563A76@microsoft.com...
- Posted by Patrifick on May 21st, 2006
easyly said than done, byu deleting it users would loose all their settings
which I cannot afford to happen. We got several hundred of them, which is
un-questionable solution.
Thanks anyway that you are brainstorming. Maybe somebody else will have
similar issue.
"Frankster" wrote:
- Posted by Frankster on May 21st, 2006
Maybe you missed the "rename" in "rename/delete". Maybe you also missed that
after renaming, creating a new profile, you could copy the contents of the
previously renamed <username> profile over the newly created <username>
profile.
-Frank
"Patrifick" <Patrifick@discussions.microsoft.com> wrote in message
news:7B2F8AAF-02BD-49E8-974C-C13CC9A7FD62@microsoft.com...
- Posted by rach on May 22nd, 2006
Do you have a single label domain name? For example, you domain is
called xyz and does not have a domain extension?
If so, rename the current profiles from User to User."domain name"
ie user.xyz.
I have not done a domain rename to correct the actual problem of the
single name, but this should get you working. The one problem you will
have is if you do not have rights to the users profile, in which case
you would have to take ownership of the users profile folder, do the
rename, and then assign the correct permissions again to the folder and
make the user the owner of the folder.
Rach
- Posted by Patrifick on May 22nd, 2006
Hi,
Yes, at the present moment we have single domain.
I have done this as I mentioned earlier, but it always re-created
application data and some other folders.
many thanks
Patrick
"rach" wrote:
- Posted by Frankster on May 23rd, 2006
He asked if you had a single label domain name, not a single domain.
-Frank
"Patrifick" <Patrifick@discussions.microsoft.com> wrote in message
news:72CCE81F-8D7C-42F8-B8BE-C069353DED1E@microsoft.com...
- Posted by Patrifick on May 23rd, 2006
sorry, I have probably miss read it, the format is
username - profile withou SP1
username.domain - after user profile with sp1
domain.com - domain name
Thank you
"Frankster" wrote:
- Posted by Frankster on May 23rd, 2006
Okay, you do not have a single label domain name (that would be simply
"domain" without the "com").
Anyway, the scenario you describe happens when, for some reason, the user
cannot access the previous profile upon logging on. If the profile was named
"fred", and it still exists on the hard drive, and he cannot access it upon
logon, Windows will auto-create a new profile of another name (fred.domain).
The part to understand is that this is happening because fred cannot access
his old profile for some reason. The fix (which I have done many times) is
to rename or remove (your choice) the old profile "fred". Then, upon loging
on, Windows should be clear to auto-create a profile using the straight
logon name that you prefer (fred).
I have seen this behavior since Windows NT, then in W2K, then in W2K3. I
don't believe it has anything to do with SP1 (other than the possibility of
tighter security causing profile access issues).
Either way, if you recreate the profile and copy the contents of the old
profile into the new, it should work for you. Have you tried it?
-Frank
"Patrifick" <Patrifick@discussions.microsoft.com> wrote in message
news:4B6C0DFD-41CB-4E85-B9BC-7311DF9C3290@microsoft.com...
- Posted by Patrifick on May 23rd, 2006
yes, i tried to do it before as mentioned above, but I will do it again to
double check.
What I have noticed before. That there is some issue with ntuser.dat, that's
why it recreates some part of the profiles and mostly application data, which
holds all the setup.
To me this is puzzling as well, as I did it on a different domain and it
works. Could it be that users are loging into various server in the citrix
enviroment?
thank you Patrick
"Frankster" wrote:
- Posted by Patrifick on May 23rd, 2006
Hi, I found this. This is almost exactly what is happening
http://support.citrix.com/forums/thr...tart=0񵔖
Patrick
"Frankster" wrote:
- Posted by Frankster on May 24th, 2006
Yes, Citrix/TS has everything to do with it. Maybe should have mentioned
that sooner 
According to the reference you posted, maybe you will have to recreate
everything. Sorry. I'm a CCA (Citrix Certified Admin) but I've never
upgraded a Citrix W2K3 server to SP1.
One thing to check out... you know... Citrix/TS has a specific profile
location that can be created on the TS tab of AD Users and Computers.
Perhaps that could be of use. But, I guess you are in "recovery" mode now,
not design mode.......!
-Frank
"Patrifick" <Patrifick@discussions.microsoft.com> wrote in message
news:812DAB8E-A64A-4CAD-B9AE-3B10E6CA9DF7@microsoft.com...
- Posted by Patrifick on May 24th, 2006
Frankster,
thank you for your help, but I have mentioned that we have citrix enviroment
earlier on the initial post.
Thank you again.
Patrick
"Frankster" wrote:
- Posted by Frankster on May 24th, 2006
Yes, I see you did. Sorry.
-Frank
"Patrifick" <Patrifick@discussions.microsoft.com> wrote in message
news:53EF4272-2CDF-4F65-8F7B-64FBA653387C@microsoft.com...
- Posted by rach on May 24th, 2006
I would recommend you call Microsoft, as I have only ever had this
problem after going to Service Pack 1, if Microsoft finds it is a
problem with them, you won't be charged for the support call. This has
not been specifically a Citrix issue for me as it happened in both
Citrix and in using RDP client to connect to the terminal servers, but
to make sure you are "covered" log into the server using the Microsoft
RDP client, and you should have the same problem, therefore when you
call Microsoft, you can tackle it from that end. Again, the only times
this has been a problem for me was when the enviroment was a single
level domain name, and in calling Microsoft at that time, there was no
resolution other then trying a domain rename, or simply appending the
domain extension to existing profiles.
Some things I would look at also:
1. If you create a brand new user, log in using RDP client, does the
profile still get the .domain extension?
2. If so, that is what happened to me as well, and renaming all my
profiles to the username.domainname, then going and setting the Owner
of the profile to the user, and then replacing permissions on the files
in the folder of each user fixed made this work for me.
3. If you are not getting newly created users with the .domain
extension, I would then try just step 2 on the existing profiles. 
- Posted by Patrifick on May 24th, 2006
thanks I will do it next, as I am off for the rest of this.
thanks everybody
"rach" wrote: