When you have a SharePoint farm and you want to use accounts from another domain you need a partial (one-way) or a full (two-way) trust between those domain.
A full trust is not always desirable and there your problem begins. After setting up the one-way trust you can authenticate with an account from the trusted domain, but the SharePoint People Picker doesn't show any accounts from this domain.
It has been documented by others before, but as I ran into this recently I'll give my summary how I fixed this.
When you have a SharePoint farm and you want to use accounts from another domain you need a partial (one-way) or a full (two-way) trust between those domains.
A full trust is not always desirable and there your problem begins. After setting up the one-way trust you can authenticate with an account from the trusted domain, but the SharePoint People Picker won’t show any accounts from this domain.
It has been documented by others before, but as I ran into this recently, I will give my summary how I fixed this. This solution is the same for WSS 3.0/SharePoint 2007 as SharePoint 2010.
The other day I attended a meeting where the presenter switched from a PowerPoint slide to demonstrate an application. When he made the switch it was quite obvious the beamer was setup to only display the 4:3 slides to the maximum of the white screen. Since his desktop was in a 16:10 resolution the application was falling of the screen on both sides.
While I was preparing a presentation myself I wanted to be sure my presentation would be in the same resolution as my desktop as I would be switching between my slides and Visual Studio.
The other day I attended a meeting where the presenter switched from a PowerPoint slide to demonstrate an application. When he made the switch, it was quite obvious the beamer was setup to only display the 4:3 slides to the maximum of the white screen. Since his desktop was in a 16:10 resolution the application was falling off the screen on both sides. Which was quite a distraction.
When I was preparing a presentation myself, I wanted to be sure my presentation would be in the same resolution as my desktop as I would be switching between my slides and Visual Studio.
With the launch of Visual Studio 2010 this week a lot of people will start upgrading to the new version. After the installation was complete I noticed the Surface project and item templates were not available.
In this post I explain how to get the entries in Visual Studio 2010.
With the launch of Visual Studio 2010 this week a lot of people will start upgrading to the new version. After the installation was complete, I noticed the Surface project and item templates were not available.
In this article I explain how to get the entries in Visual Studio 2010.
Today the Microsoft Virtualization Team announced the availability of the new beta version of the Linux Integration Services for Hyper-V.
In this post I will try the new features.
Virtual machines will be able to use up to 4 virtual CPU’s.
Virtual machines will be able to synchronize their time with the parent partition.
Virtual machines will be able to shutdown gracefully from the Hyper-V manager.
In this post I will try the new features.
Linux Integration Services for Hyper-V 2.0
First, I got a VM (Virtual Machine) installed as described in my previous post Running CentOS 5.x on Hyper-V. I used the current released stable version of the LIS (Linux Integration Services): Version 2.0.
My Hyper-V host only has a dual-core CPU. So, it is impossible for me to test the 4 CPU support. I could not find any differences with 2 CPU’s.
Shutdown from Hyper-V Console
With the current version of the LIS when I press the shutdown button, I get the following error:
Time synchronization
With the current version of the LIS I had a lot of trouble with the clock of the VM getting out of sync very fast. I did a post to fix this: Correcting time drift with CentOS on Hyper-V.
I did not implement the mentioned fix on the VM I created for this post, to demonstrate the problem:
Linux Integration Services for Hyper-V 2.1 Beta
To get the beta drivers you need to download them from the Microsoft Connect website.
I installed the new drivers in exact the same way as the 2.0.
Not only the new version number is displayed, also the new Shutdown and Timesync channels are mentioned!
Shutdown from Hyper-V Console
Pressing the shutdown button now gives a more expected result:
Time synchronization
With the new LIS the time is pretty much stable, nothing the NTP service cannot handle. There is no need to change the boot command in grub anymore.
I wanted to use the new REST services in SharePoint 2010.
But when I navigated to the ListData.svc service. I got the following error: “Could not load type 'System.Data.Services.Providers.IDataServiceUpdateProvider' from assembly 'System.Data.Services, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'.”