How to get SharePoint-sites directory in your Windows profile

SharePoint-sites-directory
When you connect your SharePoint library, you expect an SharePoint-sites directory in your profile. In this blogpost you will find some helpful information to get the SharePoint-sites directory in Windows 7.

If you click in SharePoint, connect to office. It take some days when the SharePoint-sites directory appear within your profile (c:\users\username\sharepoint-sites). If you follow the steps below, you can speedup this process.

First of all. Be aware that the webclient services is used to connect to the webdav pages of SharePoint. This process will start automatically when needed. But if you reading this post, it might be helpful to check this services on your workstation.

There are two important registry keys. Check if the following registry keys exist:
[HKEY_CURRENT_USER\Software\AppDataLow\Microsoft\Office\15.0\Common\Portal]
"PersonalSiteURL"="https://personal.organisation.com/personal/username/"
"LinkPublishingTimestamp"=hex:1f,b0,e5,59,00,00,00,00

Just replace the PersonalSiteURL with your own data.
If the registry keys already exist and you have no Sharepoint-sites directory? You can try to clear all of the registry values and try again to 'connect to office' in SharePoint. Otherwise add the registry keys to your HKEY_CURRENT_USER with proper values.
Connect-to-office

Please follow the steps to get the sharepoint-sites directory

  1. Add registry keys
  2. Add the shortcut document Library by clicking "Connect to office" in Sharepoint
  3. Copy the url of the document Library (from "Open with Explorer")
  4. Open and create a new document in Word 2010 or 2013
  5. Save the document with "Save As"
  6. In the Save As window, past the url of the document Library.
  7. Save the document within this Sharepoint Library
  8. Now you have create a SharePoint-sites folder in (c:/users/username)
User-profile-sharepoint

Don't leave the registry keys empty

If you leave the registry key empty, your Office suite will crash! I got the following message in the event log:

Application name with error: lync.exe, version: 15.0.4933.1000, timestamp: 0x59082bf7
Name of module with error: MSVCR100.dll, version: 10.0.40219.325, timestamp: 0x4df2be1e
Exception code: 0xc000000d
Error offset: 0x0008af8a
Error Processing Id: 0x15d0

Please fill in a timestamp value in the registry.

Comments

Post a Comment

Popular posts from this blog

Error when opening LCM via PRISM

Image
After the upgrade to AOS 5.1.5, my LCM console gave the following message. Json Rpc request for unkown Rpc object LifeCycleManager Error message You can solve this issue by doing the following steps: 1). Verified that the PRISM shows: JSON RPC request error. 2). verified from ~$ zkls /appliance/logical/pyleaders/lcm_leader/   one of the CVM was not listed. I have 9. n_0000000096 n_0000000097 n_0000000098 n_0000000099 n_0000000100 n_0000000101 n_0000000102 n_0000000103 3). Verified One of the CVM .101 has .genesis_restart_required_path file. ~$  allssh "ls -latr ~/.genesis_restart_required_path" 4). Removed the file and restarted genesis on all the CVMs. ~$  rm .genesis_restart_required_path ~$  allssh genesis restart 5). Verified the issue does not exist anymore.
Read more

Azure AD Connect DB corrupt

Image
ADSync SQL connection problem I've got in a situation that our Azure AD Connect Synchonisation Server Manager was giving the status " stopped-database-connection-lost ". Only we did't mention this message, because every object was synced successful. After some problems with Azure Active Directory self-service password reset, I've decide to check the event logs. Event logs I found differend events errors, most of them mentioned the following error " The server encountered an error because the connection to SQL Server failed. ". When I opened Azure AD Connect tool, the configuration wizard was not giving me any errors of database problems. Event 6322, ADSync The server encountered an error because the connection to SQL Server failed. Event 6075, ADSync The management agent "domain.local" failed on run profile "Delta Import" because the connection to the server database was lost. E...
Read more

Get the Exchange 2010 DB whitespace back

Image
For exchange administrators it is sometime necessary to see how our Exchange databases are doing. You don't want that the database and transaction log on the datastores run out of disk space. Most of the time I want to see the blank space that is within a database. This blank space is sometimes called: Free space Free database pages Available Mailbox Space White space Checking White Space in Exchange 2010 Get the Whitespace from all the databases, run the following command: Get-MailboxDatabase -Status | Sort-Object availablenewmailboxspace | ft name,databasesize,availablenewmailboxspace -auto Show all softdeleted and disabled mailboxes in Exchange 2010 After you choose the DB you want to clear the whitespace, please check the softdeleted and disabled mailbox accounts per database with the following command: Get-MailboxStatistics -Database " DB1 " | Where-Object {$_.DisconnectDate -Notlike $NULL} | Format-Table DisplayName, DisconnectDate, MailboxG...
Read more