{"id":660,"date":"2012-02-14T19:08:49","date_gmt":"2012-02-14T19:08:49","guid":{"rendered":"http:\/\/read.virtualizeplanet.com\/?p=660"},"modified":"2012-02-14T19:08:49","modified_gmt":"2012-02-14T19:08:49","slug":"defective-clone-rouge-local-profile","status":"publish","type":"post","link":"https:\/\/read.virtualizeplanet.com\/?p=660","title":{"rendered":"Defective Clone – Rouge Local Profile"},"content":{"rendered":"

\"\"<\/a><\/p>\n

I found an issue in my lab and I think it would be useful to post about it on my blog. In my lab I was running \u00a0a 2003 Domain, vSphere 5 and VMware View 5.0. Everything was working just fine until recently when I upgraded my Domain to 2008. Straight away I noticed that my XP desktops no longer attached to the domain using VMware View Quickprep. This is common issue which is well documented and fixed with this hotfix from Microsoft:<\/p>\n

http:\/\/support.microsoft.com\/kb\/944043<\/a><\/p>\n

Then I noticed my Windows 7 View desktops acting erratic but only for one user. I use ProfileUnity<\/a> on my lab to manage profiles and my first thought was \u201cdelete the profile for this user\u201d\u00a0 user being \u201cricky\u201d. Actually this made no difference at all. I just couldn\u2019t put my finger on it, and then I remember something. When I setup my master View linked clone image for my Windows 7 desktops I remember I logged in with the user \u201cricky\u201d so that meant there was a local cache copy of a profile for \u201cricky\u201d in the master image.<\/p>\n

What I did next was open up the master image, logged on as Administrator and deleted the local cache copy of the profile folder for \u201cricky\u201d<\/p>\n

I found this wasn\u2019t enough. In the registry there is a key also associated with this profile which I had to delete and is found:<\/p>\n

[HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\ProfileList\\S-1-5-21-45054391-3288665767-689454583-1000]<\/strong><\/p>\n

The key at the end S-1-5-21-blah blah blah will differ from user to user. To find the right one just delete the one that has the username in the ProfileImagePath string.<\/p>\n

This fixed the problem and I can only guess that the issue lay in a change in SIDs when upgrading the domain. Whatever it was my domain had its knickers in a twist with this user profile. <\/strong><\/p>\n

You could argue there is a GPO that cleans up local cache profile, however that only works when you logout. My issue was the rouge local cache profile was embedded in the View linked clone master.<\/p>\n","protected":false},"excerpt":{"rendered":"

I found an issue in my lab and I think it would be useful to post about it on my blog. In my lab I was running \u00a0a 2003 Domain, vSphere 5 and VMware View 5.0. Everything was working just fine until recently when I upgraded my Domain to 2008. Straight away I noticed that […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5,14,6,4],"tags":[],"class_list":["post-660","post","type-post","status-publish","format-standard","hentry","category-citrix","category-lwl","category-vdi","category-vmware"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t