Marc Valk dot Net
blogging about…… Microsoft, Cloud Computing and all other things I find interesting
SharePoint Search Error “Access is Denied”
2 Jun 2010If you are like me and did a single box farm installation of SharePoint 2010, you might get to an error whenever you have configured your search.
I configured the search to crawl my local SharePoint Sites and when it did a full crawl it gave me the following error:
Access is denied. Verify that either the Default Content Access Account has access to this repository, or add a crawl rule to crawl this repository. If the repository being crawled is a SharePoint repository, verify that the account you are using has “Full Read” permissions on the SharePoint Web Application being crawled.
This error is caused by the local loopback check.
You can disable the loopback check by setting the DisableLoopbackCheckregistry key. To set the DisableLoopbackCheck registry key, follow these steps
- Click Start, click Run, type regedit, and then click OK.
- In Registry Editor, locate and then click the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
- Right-click Lsa, point to New, and then click DWORD Value.
- Type DisableLoopbackCheck, and then press ENTER.
- Right-click DisableLoopbackCheck, and then click Modify.
- In the Value data box, type 1, and then click OK.
- Quit Registry Editor, and then restart your computer.
You can now also browse your site on your local server
- No Comments
- Tags: SharePoint
I have some users in AD, which had a wrong Telephone property specified.
The value was correct specified in the Mobile Phone property, so I wanted to copy this value from every user into the Telephone property.
A picture says more than a 1000 words.
Off course, PowerShell comes to mind.
First I tried it with the standard AD commands get-aduser en set-aduser.
Get-ADuser will give you the Telephone property and mobilephone property, but set-aduser will not let you update the telephone property, it only support 47 properties and Telephone isn’t one of them.
Next stop: Quests PowerShell AD commands.
You can use get-qaduser and set-qaduser.
So I tried the command:
get-qaduser –SearchRoot ‘Domain/OU/OU’ | set-qaduser – PhoneNumber $_.mobilePhone
This gave me an empty PhoneNumber property in AD.
After trying a lot and searching the internet, I stumbled upon this forum post, who else than Shay Levy would give me the answer.
get-qaduser -SearchRoot ‘Domain/OU/OU’ | % {set-qaduser $_ -telephonenumber $($_.MobilePhone)}
- No Comments
- Tags: Powershell
Preview of the “new hotmail”
18 May 2010A preview of what’s coming in the new hotmail. Amongs others: sweep (get rid of clutter) and integration with office live workspaces and skydrive.
read more @ source
- No Comments
- Tags: Microsoft
New distribution group: couldn’t find object
17 May 2010On creating a new distribution group in Exchange you could get the following error:
Couldn’t find object “<user object in AD>”. Please make sure that it was spelled correctly or specify a different object. Reason: the recipient <user object in AD> isn’t the expected type.
You probably logged in with an administrator account, which has no mailbox associated with it. When you create a mailbox, you will automatically be the manager of the distribution group.
To bypass this (without creating a admin user mailbox), use the powershell command: New-DistributionGroup and specify the “ManagedBy” parameter
- No Comments
- Tags: Exchange
Exchange 2010: setting room permissions
17 May 2010To set permission’s on a room mailbox in Exchange 2010, you have to execute the PowerShell command Add-MaiboxFolderPermission.
Add-MailboxFolderPermission -identity <roomname>@<domain.com> -user <email address of user who needs access> -AccessRights <AccessRight>
The parameter AccessRight specifies the permissions for the user, you can use the following values:
- ReadItems The user has the right to read items within the specified folder.
- CreateItems The user has the right to create items within the specified folder.
- EditOwnedItems The user has the right to edit the items that the user owns in the specified folder.
- DeleteOwnedItems The user has the right to delete items that the user owns in the specified folder.
- EditAllItems The user has the right to edit all items in the specified folder.
- DeleteAllItems The user has the right to delete all items in the specified folder.
- CreateSubfolders The user has the right to create subfolders in the specified folder.
- FolderOwner The user is the owner of the specified folder. The user has the right to view and move the folder and create subfolders. The user can’t read items, edit items, delete items, or create items.
- FolderContact The user is the contact for the specified public folder.
- FolderVisible The user can view the specified folder, but can’t read or edit items within the specified public folder.
AccessRight also accepts a Roles definition as a value:
- None FolderVisible
- Owner CreateItems, ReadItems, CreateSubfolders, FolderOwner, FolderContact, FolderVisible, EditOwnedItems, EditAllItems, DeleteOwnedItems, DeleteAllItems
- PublishingEditor CreateItems, ReadItems, CreateSubfolders, FolderVisible, EditOwnedItems, EditAllItems, DeleteOwnedItems, DeleteAllItems
- Editor CreateItems, ReadItems, FolderVisible, EditOwnedItems, EditAllItems, DeleteOwnedItems, DeleteAllItems
- PublishingAuthor CreateItems, ReadItems, CreateSubfolders, FolderVisible, EditOwnedItems, DeleteOwnedItems
- Author CreateItems, ReadItems, FolderVisible, EditOwnedItems, DeleteOwnedItems
- NonEditingAuthor CreateItems, ReadItems, FolderVisible
- Reviewer ReadItems, FolderVisible
- Contributor CreateItems, FolderVisible
So.. for example if I wanna give all users the rights to review the calendar of the Meetingroom and a user named John Doe will receive the contributer permission, I use the following commands:
- Add-MailboxFolderPermission -identity meetingroom@domain.com -user john.doe@domain.com -AccessRights contributer
- Add-MailboxFolderPermission -identity meetingroom@domain.com -user Default -AccessRights reviewer
- No Comments
- Tags: Exchange
recreating folder structure
17 May 2010I needed to recreate a folder structure from one computer to another.
To be ahead of some comments I foresee, one computer did not have powershell or any internet connection (to download powershell), and I was not allowed to install anything.
To solve the problem I used “old school” DOS commands.
- Open a command prompt
- navigate to the correct folder
- execute the command: “dir /s /b /ad > createfolders.bat”
- edit the just created createfolders.bat file with an advanced text editor which supports macro’s (like download notepad++ )
- Make a macro that put’s the command “md” (make directory) on every single line, and removes the part in front of the line you don’t need (like d:\ or so)
- Copy and execute this batch file onto your computer on which you want to recreate the folder structure
Simpel.. ain’t it.
- (2) Comments
- Tags: Tips & Tricks
Creating a PowerShell Profile
5 May 2010You can create a PowerShell profile to set your environment (aliases, modules you want to import, functions,etc..)
First of all check if a profile already exists with the command
test-path $profile
This will return true or false. If no profile exists you can create one with the following command:
new-item -type file -path $profile -force
This will create a Microsoft.PowerShell_profile.ps1 file in “%UserProfile%\My Documents\WindowsPowerShell”. The commands you enter in this file will apply to the current user and thePowerShell Shell.
You can now edit this profile with notepad, just type:
notepad $profile
I just entered the command import-module ActiveDirectory, this will automatically load the AD module whenever I start PowerShell.
note:
Their are 4 different profiles in PowerShell:
%windir%\system32\WindowsPowerShell\v1.0\profile.ps1
This profile applies to all users and all shells.
%windir%\system32\WindowsPowerShell\v1.0\ Microsoft.PowerShell_profile.ps1
This profile applies to all users, but only to the Microsoft.PowerShell shell.
%UserProfile%\My Documents\WindowsPowerShell\profile.ps1
This profile applies only to the current user, but affects all shells.
%UserProfile%\My Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1
This profile applies only to the current user and the Microsoft.PowerShell shell.
Edit:
I just received some nice scripts from @shayLevy (thx) via Twitter.
Check these out (V2 scripts):
A nicer one 
And last but best 
- No Comments
- Tags: Powershell
When I wanted to create a test user for SCOM 2007 to monitor Exchange, I constantly ran into the error (whenever I ran the script
new-TestCasconnectivityUser.ps1):
CreateTestUser : Mailbox could not be created. Verify that OU ‘Users’ exists and that password meets complexity requirements.
I checked google, and all solutions pointed to the fact that there was more than one users OU.
When I edited the script and replaced the variable $OrganizationalUnit with a different OU, I still received the same error.
The solution came when I created a new OU in AD and edited the script again, now I changed the $OrganizationalUnit parameter to contain the newly created OU. After that the script ran perfectly.
- No Comments
- Tags: Exchange, Powershell
Cloud versus On Premise.
- No Comments
- Tags: Cloud Computing
Original Source: here
Coca-Cola Enterprises, the soft drink bottling and distribution company, is the world’s largest marketer, producer, and distributor of Coca-Cola products, with around 75,000 employees worldwide and sales in over 200 countries. Coca-Cola Enterprises is an extremely successful corporation but all enterprises, no matter the size and success, can improve. “The tools that we had weren’t really working…we weren’t really generating a lot of dialogue among employees,” says Coca-Cola Public Affairs employee Lauren Sayeski. Coca-Cola Enterprises looked for a solution and in September of 2009 they launched their Global Employee Portal through SharePoint and Microsoft Online Services.
….Read more @ source