User Profile Service Account AD Access

This is all the AD guy's need to do to grant the account access to AD to sync.

Use this procedure to grant Replicate Directory Changes permission on a domain to an account.

The Replicate Directory Changes permission enables the synchronization account to read AD DS objects and to discover AD DS objects that have been changed in the domain. The Grant Replicate Directory Changes permission does not enable an account to create, modify or delete AD DS objects.

To grant Replicate Directory Changes permission on a domain

1. On the domain controller, click Start, click Administrative Tools, and then click Active Directory Users and Computers.
2. In Active Directory Users and Computers, right-click the domain, and then click Delegate Control.
3. On the first page of the Delegation of Control Wizard, click Next.
4. On the Users or Groups page, click Add.
5. Type the name of the synchronization account, and then click OK.
6. Click Next.
7. On the Tasks to Delegate page, select Create a custom task to delegate, and then click Next.
8. On the Active Directory Object Type page, select This folder, existing objects in this folder, and creation of new objects in this folder, and then click Next.
9. On the Permissions page, in the Permissions box, select Replicating Directory Changes (select Replicate Directory Changes on Windows Server 2003), and then click Next.
10. Click Finish.

https://technet.microsoft.com/en-us/library/hh296982(v=office.14).aspx#RDCdomain

Disable JIT

Here is the registry keys to delete the Just-In-Time-Debugger

• HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug\Debugger
• HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\DbgManagedDebugger

On a 64-bit operating system also delete the following registry keys:

• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\AeDebug\Debugger
• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\DbgManagedDebugger

SharePoint 2010 Administration Service wont Start

Hi
lately I don't get to the blog allot...So mostly posting issues that i get more than once and cant remember the steps to resolve.

Admin service won't start.
This has worked in more than one occasion for me:

Open mmc.exe
Add Group Policy Object Editor and select Local Computer on Object. In some instances you need to select Manage cert's for where you can select Computer.

Browse to Computer Configuration -> Windows Settings -> Security Settings -> Public Key Policies and open Certificate Path Validation Settings.

Browse to Network Retrieval Tab, check "Define these policy settings"
Uncheck Auto update Cert in the Microsoft Root as below

 Now you can try and start your service again.

SharePoint and Special Characters

Ok, this some of these issues I always know the basics but there come a time that I need to delve into the details...

As all of you time is always an issue so I expect to have a few edits on this topic...
The clients I consult to is mostly on SP2010 at the moment so that is what im basing my research on...SP2013 with Fast search might be similar.

At the time of this pose SP2016 announcements are coming out and apparently documents will have some kind of id, so you can move it around without breaking links....Lets hope they use this ID in the URL to get rid of some of the issues with log file names.

SharePoint Foundation is different to the other versions.

Good read:
http://www.networkworld.com/article/2222853/microsoft-subnet/10-essential-sharepoint-search-hints.html

Bottom Line:
What should I use in my SharePoint File Name:
Underscore "_"

What Should I Not use in my file names:

Hyphen "-" (Can cause other issues, see Susans Post below for details)

Do not Smush words together without separator. (Search wont recognise the words)

Then there is a bunch that is not allowed (They will be blocked by SharePoint)

All I need for now...This topic seems to have allot of opinions....Susans post above had the best detail I could find in the topic so for now I am going with her recommendation.

Cheers for now

Test and Troubleshoot mail with PowerShell

Hi,

The old way was with Telnet
http://daniecsp.blogspot.com/2013/06/sending-test-mail-with-telnet.html

Bit easyer with PowerShell:

Send-Mailmessage -To Destination@domain.com -From Source@domain.com -Subject testing -Body testing -SmtpServer OURSERVER

One thing I'm not sure yet is how the error reporting works but usually PowerShell is pretty good.