Switching from 2003 to 2008 and Citrix profiles

[a.evans]

Hi

I just wanted to check a couple of things to make sure what's happening is correct.

We are migrating our profiles from v1 to v2 and at the same time make them into citrix profiles.

all the profiles are currently stored in the same location. Normally when windows has been automatically creating the profiles we end with something like j.blogs.domain and j.blogs.domain.v2

If we try to have Profile Migrator create the new profile as described in the same target directory it fails saying there are no profiles to migrate. If we chose a different location it works fine but creates j.blogs.domain without the v2.

Is this why it's failing (a folder already exists with that name) and even though this is for use with citrix profile management is it going to have a problem on 2008 without the v2?

Thanks

[holger]

Hi,

let me clear that up for you.

In general Profile Migrator creates user profiles according to the behavior of Windows and Citrix Profile Management.
Windows will create a user profile using the path specified in the GPO or in the AD user object. .V2 will be appended automatically according to the profile type. This appendix must not be specified in the configured path.
CPM however uses its own GPO or ini files for configuration. The user store specified there will be used to store and retrieve the user profile. CPM in contrast to Windows will not append .V2 for V2 profiles.

That being said Profile Migrator will append .V2 every time you are migrating to V2 profiles and did not select to create CPM profiles.
If you selected to create CPM profiles Profile Migrator will not append .V2 to the target path, because it assumes that CPM will be using the migrated profiles and CPM will not find them if the directories have a .V2 appendix.
In your case this will result in a conflict, because the source and the target path are the same, as you have already figured out.

I would suggest that you select a new directory for the migrated profiles that will be used with CPM. You can use %USERNAME% and %USERDOMAIN% in the text box for the path to the migrated profiles in Profile Migrator to specify any path that will suit your needs.

I hope that helped you get further. Please let me know if you have more questions.

[a.evans]

OK that all makes great sense, thanks

One other thing I've noticed is that with the update profile path set, no changes seem to be occurring in AD

[holger]

What settings did you specify in the migration project?
You can send the log and project file to . We'll than have a look at it for further analysis.

[holger]

Thank you for sending the files. I reproduced the issue in our environment.
The setting that prevents the profile path in the AD user object from being updated is “Create target profiles in Citrix Profile Management format”.
If you deactivate this option, the profile path will be updated.
The reason for this is that CPM does not use the AD user object profile path in any way and therefore it does not need to be changed by Profile Migrator.