This post is more than 5 years old
45 Posts
0
170259
February 14th, 2013 19:00
Quest Desktop Virtualization (vWorkspace) User Profile Management trouble
Hi, I'm working on configuring the user profile management service with virtual desktops (Win 7 VDI) by following the vworkspace 7.6 admin guide and any other docs I've found on quest.com and I'm having trouble with it, there is nothing in the metaprofiles\global folder. It does not seem to be working. I have a File Server ( vdi-storage1 ) with share c:\vdiuserprofiles\ folder created where the profiles are going to be stored. I've also installed the vWorkspace User Profile Management role on this File server and the service is running. Port 5206 is open. All the virtual desktops have pntools installed with all options and I can see the user profile agent is running. I can reach storage server (vdi-storage1) using telnet on port 5206 and ping. I even gave domain user full ntfs permissions to c:\vdiuserprofiles folder, but I dont think this is necessary.
- In the Managment Console > Resources > User Profiles (Right click "Properties")
- General : Compression:low, Log Level:Detailed, Refresh: 5 minutes
- Storage Servers: Server name: vdi-storage1, Base Folder: c:\vdiuserprofiles\metaprofiles, Global Folder: Global, TCP Port: 5206
- Silos: Name: VirtualDesktopSilo, User Profile Storage Server: vdi-storage1
- VirtualDesktopSilo Properties
- Members: Name: Windows 7 Desktops, Type: Computer Group
- User Profile Storage Server: vdi-storage1
- Auto-Save: 30 minutes
The MC did create the metaprofiles\global folder automatically when I applied the settings. I'm using default registry keys that came with vworkspace, and I've assigned all of them to domain users group. I've logged on and off multiple times on the virtual desktop. I did notice 5 second delay on the vm after I type in credentials and before it actually logs me in since I've enabled the profile managment. Did I forget something or misconfigured it?
dkgcb
45 Posts
1
April 3rd, 2013 17:00
Ok, after receiving help from Dell (Quest) suppor,t the issue happen to be with me remoting (via RDP) to VM directly instead of through the vWorkspace broker, therefore the profile could not be created because I did not have the valid farm session so it never created the profile. Once I've tested it by using the vWorkspace Connector it worked.
dkgcb
45 Posts
0
February 14th, 2013 20:00
Interesting, this is what I've found in Application log, pnmpts:
User Domain\ with sid=S-1-5-21-.......73 has logged off.
Because user has another session running or the profile wasn't imported, profile wasn't exported.
I'm thinking I have misconfigured something.
DELL-David Y
228 Posts
0
February 14th, 2013 20:00
Hi Dejan,
It sounds like the broker service was able to reach the profile storage service since it created the global storage folder. Each time you login or logoff one of the VDI's in the group there should be an entry recorded in the Windows Application event log, the source will be pnmpts. The description will show how the meta profile service processed the user. Can you check to ensure you see the event and also report back the details.
It may be this will identify the problem.
Thanks
David