If you receive this error:
The Lync 2010 client or the Office Communicator client does not download the corporate address book and displays a notification: “Cannot Synchronize Address Book”
Give the following a shot:
- Shutdown the Lync client
- Force the Lync client to download the address book immediately the next time it starts:
- Open the registry to HKLM\Software\Policies\Microsoft\Communicator
- Modify (or Create) the DWORD the registry key “GalDownloadInitialDelay” and set it to 0 (that is a zero)
- This can also be done from the command line:
- reg add HKLM\Software\Policies\Microsoft\Communicator /v GalDownloadInitialDelay /t REG_DWORD /d 0 /f
- Delete the Existing Local Address Book Files:
- On Windows 7 or Vista machines, open Windows Explorer to the directory:
- Delete the files GalContacts.db and GalContacts.db.idx
- Restart the Lync client.
• The address book should be available in less than an hour.
I found the solution here: http://blog.insidelync.com/2012/02/lync-address-book-client-synchronization-errors-and-common-problems/ Give it a read, it’s very thorough.
If you receive this error inside of the Lync Server event log on your Front End server:
User authentication with NTLM protocol failed with error SEC_E_UNSUPPORTED_FUNCTION. This indicates a potential mismatch between security policy settings on the client and server computers.
Cause: This error can occur if the settings in “Network security: Minimum session security for NTLM SSP based (including secure RPC) clients” policy on the client computer are not the same as the settings in the “Network security: Minimum session security for NTLM SSP based (including secure RPC) servers” policy on this server. By default, the “Require 128-bit encryption” setting is disabled for computers running Windows Server 2008, Windows Vista, Windows Server 2003, Windows 2000 Server, or Windows XP. For computers running Windows 7 or Windows Server 2008 R2, this setting enabled by default.
Ensure that the “Network security: Minimum session security for NTLM SSP based (including secure RPC) clients” policy settings on the computers from which users log on are the same as “Network security: Minimum session security for NTLM SSP based (including secure RPC) servers” policy settings on this server.
Here is the fix:
1. Open up Group Policy Editor (Start->Run->gpedit.msc) (Or if you are on a domain, open up group policy editor on the domain controller)
2. Expand Local Policies under Computer Configuration
3. Select Security Options
4. Scroll Down and find the following policies:
- Network security: Minimum session security for NTLM SSP based (including secure RPC) clients
- Network security: Minimum session security for NTLM SSP based (including secure RPC) servers
5. Change both policies to have “Require 128-bit encryption” checked
Reboot the machine(s)
Copied right from Microsoft’s KB, here is how to extend a partition/disk.
- At a command prompt, type diskpart.exe.
- Type list volume to display the existing volumes on the computer.
- Type Select volume volume number where volume number is number of the volume that you want to extend.
- Type extend [size=n] [disk=n] [noerr]. The following describes the parameters:
- The space, in megabytes (MB), to add to the current partition. If you do not specify a size, the disk is extended to use all the next contiguous unallocated space.
- The dynamic disk on which to extend the volume. Space equal to size=n is allocated on the disk. If no disk is specified, the volume is extended on the current disk.
- For scripting only. When an error is thrown, this parameter specifies that Diskpart continue to process commands as if the error did not occur. Without the noerr parameter, an error causes Diskpart to exit with an error code.
- Type exit to exit Diskpart.exe.
When the extend command is complete, you should receive a message that states that Diskpart successfully extended the volume. The new space should be added to the existing drive while maintaining the data on the volume.
The original KB article can be found here: http://support.microsoft.com/kb/325590
Today I was faced the challenge of installing VMware Tools on a Ubuntu server via command line. I stumbled accross a step-by-step tutorial on the exact steps to accomplish this task. I am reposting for archival purposes, but all credit goes to @justinschier from http://ghosttx.com/2012/03/how-to-install-vmware-tools-v4-on-ubuntu-11-10-server/
Written: March 13, 2012
Last Updated: April 27, 2012
Tested With: Ubuntu 12.04 LTS Server, Ubuntu 11.10 Server
All the guides I found on the Internet, including VMWare’s website were outdated in some way, so I decided to write a guide of my own. I just went through these steps from start to finish on a fresh server and had no problems.
Use Install VMWare Tools option in VMWare Client/Console to attach media
Update the server
sudo apt-get update
sudo apt-get upgrade
- Create the mount point
sudo mkdir -p /media/cdrom
- Mount the ISO
sudo mount /dev/cdrom /media/cdrom
You should see the message: mount: block device /dev/sr0 is write-protected, mounting read-only
- Change Directory
- Copy the tar file to your /tmp directory
sudo cp VM*.tar.gz /tmp
- Install Build tools if necessary
sudo apt-get install linux-headers-server build-essential
- Change Directory
- Unmount the ISO
sudo umount /media/cdrom
- Expand the tar
sudo tar xzvf VM*.tar.gz
- Change Directory
- To prevent a potential error in the install script on Ubuntu 11.10, create a special directory
Unable to create symlink “/usr/lib64/libvmcf.so” pointing to file ”/usr/lib/vmware-tools/lib64/libvmcf.so/libvmcf.so”.
sudo mkdir /usr/lib64
- Run the Install Script. The -d flag automatically answers the default to all questions. To customize it, just omit the -d.
sudo ./vmware-install.pl -d
Let me know if this worked for you!
Also, please follow me on Twitter: @justinschier
If you have ever wanted to view how big your hard drive/partition sizes are in Linux, but only have access to the command line interface, here is the command to do it:
df -H (This will show the partition sizes in MB, GB, TB, etc.)
fdisk -l | grep Disk (This will show the physical disks and their corresponding sizes)