Quantcast
Channel: VMware Communities : All Content - VMware View
Viewing all articles
Browse latest Browse all 9103

Persona Manager with Roaming Profiles

$
0
0

Hi folks, hope you can help me here!

 

NOTE - I have updated this question.

The original question is further below!

 

We want to use persona management with roaming profiles; the profile path is set in the users AD "profile path" attribute.

We set this up, as defined from Microsoft: How to configure a user account to use a roaming user profile in Windows Server 2003, Windows 2000 Server, or Windows N…

Particularly note the comment on that link:

Use the following format for the user profile path:

\\server_name\shared_folder_name\user_profile_folder_name

For example, if you want to store the user's roaming profile in a folder that has the same name as the user account in a shared folder that is named "Profiles" on a server that is named "Server1," type the following path:

\\Server1\Profiles\%username%

 

However, when using persona management (assuming it is setup correctly), we get errors in the PM log:

[0][10/23/2013 11:23:56:0116][RTOVPHelper!RTOTestConnection] Failed to get attributes of remote profile: \\ourdomain.com\userpathlocation\Profile\%username%.V2, 0x80070002

 

As a test, if I change the roaming profile "profile path" attribute from \\Server1\Profiles\%username% to \\Server1\Profiles\realusernamethen persona manager no longer has an issue.

It appears that it cannot interpret the %username% variable!

 

Is this correct? Am I missing something? Can anyone shed some light on this situation?

 

Thanks.

 

 

 

 

 

 

ORIGINAL QUESTION BELOW:

 

 

 

Users can use many devices and may use a physical or virtual device in any location - they are not tied to a desk.

We traditionally use roaming profiles in our physical environment. This works well - their profile goes with them (we have some redirection setup).

When the user logs into virtual, Persona Manager is not happy. It says: "Persona Management is Disconnected - please contact an administrator"

 

 

 

Checking the PM log, the only things that stick out are:

....

[0][10/23/2013 11:23:30:0066][RTOProcessLogonEvent      ] LOGON: Set Logon Event: User: testuser, Event: 0x278

[0][10/23/2013 11:23:30:0066][RTOProcessLogon           ] Finished Processing LOGON Event: User: testuser

[0][10/23/2013 11:23:30:0066][RTOGetUserProfileInfo     ] User: testuser, Sid: S-1-5-21-199048513-897128045-483988704-295896

[0][10/23/2013 11:23:30:0066][RTOGetUserProfileInfo     ] Failed Opening User Profile Key: User: testuser, 0x2

....

[0][10/23/2013 11:23:40:0224][VMWPopulateOfflineFiles   ] Failed Opening Remote Folder: User: testuser, Session: 1, Path: \\ourdomain.com\userpathlocation\Profile\%username%.V2, 0x80070002

....

[0][10/23/2013 11:23:55:0710][RTOVPHelper!RTORefreshWorker] Failed Creating Desktop Refresh Event: ProcessId: 5116, Event: Global\RTOVPHELPER_DESKTOP_0000000000459176, 0x80070005

....

[0][10/23/2013 11:23:56:0116][RTOVPHelper!RTOTestConnection] Failed to get attributes of remote profile: \\ourdomain.com\userpathlocation\Profile\%username%.V2, 0x80070002

 

(.... indicates other log entries in between that have been omitted)

As we are using roaming profiles, the profile path, \\ourdomain.com\userpathlocation\Profile\%username%.V2, is held within the users AD object. (NOTE: It's actually \\ourdomain.com\userpathlocation\Profile\%username% so the .V2 is added by PM/Win7).

If I am correct, 0x80070002 should equate to error 2, "the system cannot find the file specified", but it DOES exist. If I enter \\ourdomain.com\userpathlocation\Profile\%username%.V2 into explorer, it appears.

It almost appears that it is not expanding the environment variable %username%.

 

 

 

The PM group policies are set up in the virtual environment:

Manage user persona: ENABLED

Persona repository location: ENABLED>>> Share Path: BLANK>>> Override Active Directory user profile path if it is configured: ENABLED

Logging filename: ENABLED>>> Local log file pathname: BLANK

 

 

 

Roaming Profile repository is set up as per this KB article:

VMware KB: Persona Management not working when configured as per the View 5.0 Administration Guide

 

 

 

Does anyone have any ideas? I was thinking the issue is the %USERNAME% in the roaming profile path, but this should be fine, should it not?

Please let me know if you need more info.


Viewing all articles
Browse latest Browse all 9103

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>