ErikTatum10's Posts

Hi, Looks like this needs some engineering clarification, so I am here to help. The issue is not caused by customers adding quotes, but rather something adding them internally in the VMware... See more...
Hi, Looks like this needs some engineering clarification, so I am here to help. The issue is not caused by customers adding quotes, but rather something adding them internally in the VMware product.  This matter has been fully resolved in 7.12 and later.  If you are transitioning from Composer to Instant Clones and have previously configured scripts, you may still find issues in 7.12 and earlier depending on what you have configured.  To clarify this further, Composer supports the following scenario, which is not yet supported in Instant Clones 7.12: <interpreter path> <script path> e,g, C:\Windows\System32\cscript.exe C:\Temp\Script.vbs You can very easily work-around this by creating either a cmd or bat file, e.g. C:\Temp\Script.bat, and within it you can use the above scenario. Please be sure to use absolute paths inside your scripts. Erik
Hi Tom, Dedicated instant clones in coming in a future release.  I think this might be what you are looking for. Thanks, Erik
Hi, You used the words "profile folder" in your question, but are asking about a change to the product that is for redirected folders only.  If you want admins to have access to the profile fo... See more...
Hi, You used the words "profile folder" in your question, but are asking about a change to the product that is for redirected folders only.  If you want admins to have access to the profile folder, please use the Microsoft GPO setting that does this.  Otherwise, you would need to update to 5.3 or later to get this feature for folder redirection.  The admin template just provides the configuration interface that enables the product code that implements the change.  If you choose to update to a newer version of Persona, I would suggest you bypass 5.3 and go to 6.0 or later to pick up more bug fixes and a more stable build. Thanks, Erik
Unfortunately at this time, we have no version of Persona that supports W2K12 dedup.  However, the best way for that to happen is for you to open a support request with VMware GSS.  Other custome... See more...
Unfortunately at this time, we have no version of Persona that supports W2K12 dedup.  However, the best way for that to happen is for you to open a support request with VMware GSS.  Other customers have been requesting support for this, but opening an SR is like casing your vote. If you can please reproduce the issue with debug level logging enabled in Persona and provide the log bundle to GSS, that would be very helpful. Thanks, Erik
Another idea might be to enable folder redirection for the larger folders in the profile, put the redirected folder share on different storage (perhaps a larger disk) than the CPS, and implement ... See more...
Another idea might be to enable folder redirection for the larger folders in the profile, put the redirected folder share on different storage (perhaps a larger disk) than the CPS, and implement disk quotas there to limit the amount of space the user can consume. Thanks, Erik
Hi, Sorry for the delay.  I looked at your case myself yesterday and you should be seeing some activity now based on my input.  GSS will be in touch with you shortly for next steps. If you ... See more...
Hi, Sorry for the delay.  I looked at your case myself yesterday and you should be seeing some activity now based on my input.  GSS will be in touch with you shortly for next steps. If you have any questions, don't hesitate to ask. Thanks, Erik
Hello.  I am sorry you are having these issues and not getting a resolution. For #1, can you please share the service request number with me so I can take a look at your case and see if I can... See more...
Hello.  I am sorry you are having these issues and not getting a resolution. For #1, can you please share the service request number with me so I can take a look at your case and see if I can help move it along? For #2, I fixed a similar issue in 6.0.  So, you might consider trying 6.0 to see if it helps.  The issue I fixed was a case where users logged on, deleted some items from the desktop, then logged off before the first replication interval happened.  If that sounds like what's happening in your environment, this may work for you. Thanks, Erik
I am sorry to hear you had so many issues with Persona.  If you would reconsider Persona, we'd be happy to work with you to resolve the issues. Thanks, Erik
Persona was first introduced in View 5.0 and has been in all releases since.  It is included in 6.0 and later as well.  You must have a Premier license to have access to Persona Management. Pl... See more...
Persona was first introduced in View 5.0 and has been in all releases since.  It is included in 6.0 and later as well.  You must have a Premier license to have access to Persona Management. Please let me know if you have further questions. Thanks, Erik
Sorry Jason, looks like this hasn't gone as smoothly as it should have.  I've asked the support person to pass it over to engineering so we can take a look at it.  Once we have the ticket and you... See more...
Sorry Jason, looks like this hasn't gone as smoothly as it should have.  I've asked the support person to pass it over to engineering so we can take a look at it.  Once we have the ticket and your logs we can investigate further. Thank you for your patience.  We'll get it sorted out. Thanks, Erik
Microsoft documents their stance on WRP + DFS-R in the following KB.  Perhaps there is something there that can be helpful for you. Information about Microsoft support policy for a DFS-R and ... See more...
Microsoft documents their stance on WRP + DFS-R in the following KB.  Perhaps there is something there that can be helpful for you. Information about Microsoft support policy for a DFS-R and DFS-N deployment scenario Thanks, Erik
Hi Carlos, The {d24f2895-651a-40cc-8e5c-c037b9994104} folder is a temporary folder that is created during each replication cycle.  It's used to cache the changes that are being replicated to t... See more...
Hi Carlos, The {d24f2895-651a-40cc-8e5c-c037b9994104} folder is a temporary folder that is created during each replication cycle.  It's used to cache the changes that are being replicated to the central profile store.  Replication is done is two phases, upload and commit.  Once all the changes are uploaded to the {d24f2895-651a-40cc-8e5c-c037b9994104} folder the upload phase is complete and the changes are then committed to the profile.  Once the commit phase is complete the {d24f2895-651a-40cc-8e5c-c037b9994104} folder and its contents are deleted. Sometimes certain failures can result in the {d24f2895-651a-40cc-8e5c-c037b9994104} folder sticking around after the replication cycle has ended.  The purpose of this folder and how it's managed is to ensure your profile remains in a crash-consistent state, which means your data does not become corrupt or lost due to a replication failure. So, given that background, does this answer your question or you do feel like you are experiencing some sort of replication failure and the {d24f2895-651a-40cc-8e5c-c037b9994104} folder is staying beyond the replication cycle? Thanks, Erik
Hi Jay, In the most recent versions of Persona I have added some special logging that helps identify when files are being deleted, who deleted them, and why.  Ideally it would be best for you ... See more...
Hi Jay, In the most recent versions of Persona I have added some special logging that helps identify when files are being deleted, who deleted them, and why.  Ideally it would be best for you to work with VMware support to get a copy of this build and some help troubleshooting this.  Do you already have an SR for this?  If so, could you please let me know the SR number? Thanks, Erik
Hi, Usually when this happens it's a replication failure related to one of many possible causes.  However, one of the most common causes is incorrect permissions on the CPS.  I would highly re... See more...
Hi, Usually when this happens it's a replication failure related to one of many possible causes.  However, one of the most common causes is incorrect permissions on the CPS.  I would highly recommend you review details in the following sections of our documentation and make sure the permissions you have configured meet the minimum requirements documented.  https://pubs.vmware.com/horizon-view-60/topic/com.vmware.horizon-view.desktops.doc/GUID-4D2B6E8D-FF52-4C9E-9F5C-B5BF824CE0ED.html If that isn't the issue, then I'd suggest enabling debug level logging, reproducing the issue, and examining the log.  Search the log for "syncengine" and see what failures are appearing.  Typically we do this type of analysis for customers when they open SRs, but it's hard to do via this medium. Let me know if that doesn't help. Thanks, Erik
Thank you Mathias.  Right now GSS is looking into the issue and waiting for some details from you.  They will work through some information gathering and troubleshooting steps with you.  If they ... See more...
Thank you Mathias.  Right now GSS is looking into the issue and waiting for some details from you.  They will work through some information gathering and troubleshooting steps with you.  If they are unable resolve the issue it will be forwarded to another internal team called CPD, which includes a team of engineers knowledgeable about Persona issues.  If they need assistance I will assist from that point. Regards, Erik
Hi Cameron, For the purposes of this explanation, power outage, reset, and crash are the same. I'm not sure whether you have floating or persistent desktops, but that's important because it... See more...
Hi Cameron, For the purposes of this explanation, power outage, reset, and crash are the same. I'm not sure whether you have floating or persistent desktops, but that's important because it affects the way this all works.  Floating desktops create interesting challenges in power outage scenarios with respect to data loss.  On persistent desktops  the local profile is on the desktop and if the machine crashes the data can be recovered on the next logon (assuming the data was successfully written to disk before the power went out).  This is not the case with floating desktops unless the user is lucky enough to get reassigned to the same desktop on the next logon, which is not likely. That said, here's some details of how the replication engine works.  Every ten minutes (default) or whatever you have configured, the changes made during that interval are uploaded to a hidden temporary directory in the root of the roaming profile.  This folder name is a guid that starts with {d2...}.  Once that step is complete, the data is merged into the roaming profile itself.  If something like a crash or a reset happens before or during the upload to the temp directory, the upload is considered invalid and thrown out.  Anything else would result in a corrupt profile (i.e. a partial upload would result in a profile that is not in a crash-consistent state).  So, if a user changes a file and the machine goes down before all of the data from the delta is uploaded, the changes would be lost on a floating desktop scenario.  The replication engine is designed to ensure a crash-consistent state in the roaming profile in all cases where it's possible for us to ensure that. So, if the VM of a logged on user gets reset or crashes, it's very likely the user can lose data for the reasons I explained above. If the host goes down, I think this is a similar scenario as the VM crashing.  If the datastore hosting the desktop goes down, I think this is again a crash scenario.  If the connection to the central profile store is lost during the user's session, Persona will cache the changes locally and replicate them once the connection is restored.  Again, things get complicated if the user logs off while the CPS is disconnected on a floating desktop or if refresh on logoff is enabled. You are correct, "{08C31585-259A-4341-9982-78E42EAF6106}\computername.0.lck" is created by Persona and it is how we ensure only a single session is replicating to the roaming profile.  I'm sorry the support person told you this is not created by Persona.  They were definitely wrong.  Unfortunately, if the desktop loses power while Persona is holding this lock, sometimes the file server will not receive the signal to release the lock.  This not really a Persona bug as much as it is a catch-22 within the file system.  Imagine you and I were on the phone and I pulled the plug on my end, but you kept hearing my voice.  You wouldn't know to hang up because I kept talking and didn't say goodbye.  Basically, the file server isn't hearing "goodbye" and doesn't release the lock.  The file server should release the lock when the Persona service process stops (even if Persona didn't close it explicitly), but that doesn't happen cleanly in a this kind of situation, so it doesn't get the "goodbye" message.  I am not sure if this a persistent bug in Windows, NTFS, etc of it's a design issue that Microsoft cannot work-around. The profile will not work correctly again until the lock is cleaned up.  At this time, the only way I currently know to clean up the orphaned file locks is to reboot the file server. So, yes, we can expect data loss to happen if the desktop is reset unexpectedly and the data hasn't been replicated yet in some cases.  Sounds like this may be what you are experiencing.  Profile corruption is a term often misused.  In your case, I think you are seeing data loss due to the outages, not profile corruption.  I would expect your roaming profile to be in a crash consistent state, but missing the last set of changes the user made.  Is that what you are seeing? I hope this helps to answer your questions.  If not, please feel free to ask more. Thanks, Erik
The "Failed Creating Table" error is cosmetic in nature and not something to worry about.  You are seeing the non-English characters due to a trivial mistake in the code.  It does not affect the ... See more...
The "Failed Creating Table" error is cosmetic in nature and not something to worry about.  You are seeing the non-English characters due to a trivial mistake in the code.  It does not affect the functionality of the product. I am "the" person who can fix this issue for you, so if you can give me a case number or open a new case, I will make sure it gets fixed.  I would ask you to private message me the logs, but I don't think that's the best way for me to get and document all of the details for your case that I need to root cause the issue. Thanks, Erik
Hi, I'm sorry you are having this issue.  I'm happy to help, but I think the most efficient way to get this resolved is for you to open a support case so we can get the right details and peopl... See more...
Hi, I'm sorry you are having this issue.  I'm happy to help, but I think the most efficient way to get this resolved is for you to open a support case so we can get the right details and people on the case.  Is that an option for you?  If you already have a case, please let me know the case number and I will follow-up on it. Regards, Erik
I believe this is happening because Microsoft is resetting the permissions on the folder.  In the shipping versions of Persona, Microsoft creates the roaming profile folder, so Persona plays no p... See more...
I believe this is happening because Microsoft is resetting the permissions on the folder.  In the shipping versions of Persona, Microsoft creates the roaming profile folder, so Persona plays no part in that or configuring the security on the folder.  That's all handled via Microsoft and inheritance rules on the CPS based on the security requirements we have documented in the View Admin Guide.  You could certainly verify that it's Microsoft doing this with Procmon.  I will give this a try myself and see if there is anything I can come up with to help. Thanks, Erik
Hi Wayne, We are definitely talking about two different issues.  Your issue is related to junctions in the profile and how the Persona replication mechanism handles them.  I was talking about ... See more...
Hi Wayne, We are definitely talking about two different issues.  Your issue is related to junctions in the profile and how the Persona replication mechanism handles them.  I was talking about refresh on logoff shutting down the machine before Persona finished replicating.  I fixed your issue (unless you find otherwise) and it will be shipped in 5.3.3 and later.  Your issue does not effect all customers either for some reason and the original poster does not seem to be experiencing it. Thanks, Erik