For users to embrace VDI, administrators need to ensure that their profiles are properly delivered and backed up.Desktop virtualization complicates user profile management, because virtual desktops are often built from a single golden image that's not customized for each user.Admins have to put policies in place to configure user profiles, determine when they will be updated and ensure that they can be recovered if lost or damaged.These frequently asked questions about profiles will help you understand best practices for user profile management in your VDI environment.Finally, because I continue to develop SPServices – most frequently based on user input – it’s highly likely that I’ll make a new option or function available to meet your needs. Unless you need anonymous access or cross site access, SPServices is actually a detriment to your Share Point sustainability. Like it or not COM is the future and web services are the past.
This interaction is consistent between Share Point 20, so there’s no relearning when you upgrade.There is a bug existing in Dynamics CRM that prevents users from updating any details in the root Business Unit because the parent Business Unit is required but has no value.But what if a business requirement is you need to rename the business unit? In this blog, two workarounds will be presented to fix this issue.Obviously, keeping bugs to a minimum is an ever-present goal. Main stream support for Share Point 2007 ends in October and v Next is just over the horizon.Oh, and it’s free to use on Codeplex, under the MIT License. Microsoft has some pretty smart people and I would not be surprised in the least if they addressed the anonymous access issue in Share Point 15 as well as some of the other limitations. SPServices is a great tool that I have used quite effectively, but if you are using Share Point 2010, want better performance, a better development experience, and a technology that will definitely exist in v Next then you have to use the Client Object Model.