When trying to deploy DHCP on a member server (not a DC), you receive the following error:
Attempt to configure DHCP server failed with error code 0x8007005. Access is denied.
When you go to Authorize the server you receive “Access Denied” as well.
This is caused by permission issues on the user’s account. To fix this, first right click on IPv4 and then select Properties. Click on the Advanced tab and then click on Credentials. Inside of here, enter in the credentials you want to use as the service account to run DHCP.
Next, open up Server Manager, expand Configuration, expand Local Users and Groups. Click on DHCPAdministrators, and then add your service account.
Next, restart the DHCP Server service. Inside of server manager, right click on the DHCP server and click Authorize. Restart the service one last time, and each of your DHCP scopes should now be up (with green checkmarks).
After installing Lync 2013 RTM, I noticed that the Lync Logging Tool doesn’t exist. As you can see below, when you search for the tool under Server 2012, it is missing from the list of Apps.
You can manually grab a copy of the Microsoft Lync Server 2013 Debugging Tools (this includes both OCSLogger.exe and Snooper.exe) from here: http://www.microsoft.com/en-us/download/details.aspx?id=35453
Once installed, you can access the tool by browsing to: C:\Program Files\Microsoft Lync Server 2013\Debugging Tools\OCSLogger.exe
You receive the following error when executing the New-CsCommonAreaPhone command via PowerShell.
New-CsCommonAreaPhone : Filter failed to return unique result, “[LineURI : tel:+15555555555] [PrivateLine : tel:+15555555555] “
At line:1 char:1
+ New-CsCommonAreaPhone -LineUri “tel:+15555555555” -RegistrarPool “lync.mydomain …
+ CategoryInfo : NotSpecified: (:) [New-CsCommonAreaPhone], InvalidOperationException
+ FullyQualifiedErrorId : System.InvalidOperationException,Microsoft.Rtc.Management.AD.Cmdlets.NewOcsCommonAreaPhoneCmdlet
This means that the phone number has been assigned to either another user or response group. Make sure the number is not in use by Lync.