Lync - Screen Sharing cannot connect to ther server now issue with multiparty application sharing and screen sharing

We use Lync for internal chatting and screen sharing and the "presence" feature. I run a small shop with 100 users spread across 5 buildings. Lync really help our users collaborate.

Although Lync is a great product, it can be slightly complicated, especially if you are a small/medium business and are NOT setting up 5 separate servers for Lync.

I ran in to an issue where two users could share content (screen or application) with each other without error. The moment a third user was added to the mix (i.e. Alice sharing content with Bill and Bob), I received "Screen sharing cannot connect to the server now". Somewhat confusing because screen sharing was working just fine between just two participants.

I do not claim to be a Lync expert. I am passing along information to help any Lync novices.

When two participants are connected, the session is peer-to-peer.

When three or more participants are connected, the Application Sharing feature depends on the Front End Server Multi Point Control Unit (MCU) to provide the sharing stream to all parties.


Error: Screen sharing cannot connect to the server now.
Lync Server 2010

Internal client to internal client(s)

Single server install

This error is commonly reported when the Application Sharing Server (ASMCU) service is not running on the Lync Server Front End pool. If the ASMCU service is not installed on the Lync Front End it is likely because the components have not been enabled within the Lync Topology.

Step 1
Verify Application Sharing service is enabled in topology builder.
If not, enable it and publish the topology. Rerun component setup on FE pool using the Lync Deployment Wizard.

Step 2
Verify "Lync Server Application Sharing" and "Lync Server Web Conferencing Services" are actively running on FE pool. If not, try to start them. Check Lync Application Event logs if start fails.

*In my case the "Lync Server Application Sharing service" was bombed. Starting the service resolved the issue. The service started successfully.

If the service fails to start, check event log and begin Lync debug logging (another topic).

Step 3
Verify whether the user has the appropriate conferencing policy applied and that the policy applied has EnableAppDesktopSharing = TRUE.

Get-CsConferencingPolicy


Good luck w/ Lync. Next steps: Lync migration to 2013 on-prem.

credit to NextHop/LyncMd

http://blogs.technet.com/b/nexthop/archive/2012/11/05/lyncmd-troubleshooting-lync-server-2010-application-sharing-internal-and-remote-scenarios.aspx

Lync 2010 server stops - Certificate Expired

The Lync server stop responding for all users. Lo and behold the certificate had expired. The last certificate was installed/updated 2 years ago. Fairly painless to update the certificate (i.e. install a new certificate) on the Server. We use an Internal Windows CA. Lync can use (and by default) a simple SSL cert.

Today, the Lync client bombs for all users. Lync 2010 client reads "there was a problem verifying the certificate from the server...". The login process seems to hang indefinitely.

I open the Lync Control Panel and get a security alert. View certificate yields the following. I should have reminded myself to update the certificate. It is unfortunate that the process isn't automated nor is there a good system of alerting for impending certificate expiration.

Look at the details of the cert. I am noting the SAN entries

The rest is fairly simple. Open the Lync Deployment Wizard. Select "Request, Install or Assign...".

For my installation, I was able to accept all the default of the Certificate generation  since I had previously received (installed) a certificate from the same CA server.

During the cert generation wizard, I am verifying that the auto-generated Subject Alternative Names (SAN) matches what I had previously. Notice the SIP.<domainname>.com SAN was not there. No sweat because it is added on the next screen.

.

Make sure the SIP domain is correct. Again, for me, all I had to do was accept the default.

Next, next, next and the new cert is generated and installed. From the Wizard I select "start services" for good measure.

I will be upgrading to on-prem Lync 2013 very soon. 

Good Luck.

Outlook not displaying e-mail attachment, attachment not stripped by Exchange

I ask a user to send me an e-mail w/ attachment. I receive the e-mail - no attachment. I call the sender, the sender swears that she sent the attachment. The e-mail with attachment shows in her "sent items".

My first thought is that Exchange stripped the attachment. The problem with this theory is that the attachment type is not banned, i.e. the attachment is a simple PDF not an .exe or a .vbs or anything like that.

Coincidentally, I look down at my smartphone (Driod - Galaxy S5) and sure enough, the e-mail with attachment is looking right at me. Now I am confused.

Additionally, I open OWA and the e-mail with the attachment is there but it looks a little out of the norm.

Take a look:

Outlook - No attachment icon (little paperclip), no attachment in e-mail

OWA - No attachment icon, attachment DOES show in the e-mail when you open it

After through scouring of the Interwebs, I found some suggestions. This was difficult to research because most posts improperly referred to Exchange attachment blocking, virus filtering, etc. I saw a bunch of posts regarding MIME types but the resolution did not apply.

The problem exists w/ Exchange 2007 and 2010. I didn't confirm 2013.
Resolution is:

Exchange 2010:
1.Stop the Exchange Transport service.
2.Locate the EdgeTransport.exe.config file. This file is located in the following path:
<drive> :\Program Files\Microsoft\Exchange Server\Bin\
3.In the EdgeTransport.exe.config file, add the following entry between the <appSettings> element and the </appSettings> element:
<add key="TreatInlineDispositionAsAttachment" value="true" />
4.Restart the Transport service

Exhcnage 2007
[shell]
set-OrganizationConfig -ShowInlineAttachments:$true


Good luck.

Basic configuration of Server Core Domain Controller

Recently I was tasked with configuring a Windows 2012 server Core as a domain controller from scratch. The process is well documented and fairly painless. I figured I would aggregate and post the process.

Assumptions:

• This process doesn't cover the basic installation of the OS. This assumes you have installed the OS for the first time as CORE and you are logged in for the first time with administrative credentials.
• We don't use IPv6 (yet). I lilke to unbind and disable the adapters and protocol needed for IPv6. If you use IP6 don't follow this guide.
• You already have an existing domain infrastructure. This process adds an additional domain controller to an existing domain.
• In my example the domain is called LAB.LOCAL.
• You will be installing DNS on the domain controller.
• You don't wish to change the default NTDS and SYSVOL locations.
• You understand what the directory services restore mode password is.

In this process we will:

• disable unneeded adapters
• disable "IP Helper" service (iphlpsvc)
• rename computer
• set IP/DNS addresses
• install AD

disable 6to4, isatap adapter, Teredo tunnel adapter

From the command line:

netsh int ipv6 isatap set state disabled

netsh int ipv6 6to4 set state disabled
netsh interface teredo set state disable

disable IP Helper service
sc config iphlpsvc start= disabled
(there is a space between = and disabled)

Start Powershell
powershell

unbind IPv6
Get-NetAdapterBinding -InterfaceAlias Ethernet | Select-Object Name,DisplayName,ComponentID

Pay attention to the name displayed for the adapter you intend to modify. Petri insider’s tip: In a fresh Server core installation with one network adapter installed, the name will be Ethernet by default.

Disable-NetAdapterBinding -InterfaceAlias Ethernet -ComponentID ms_tcpip6

Get-NetAdapter

For the next few steps I want to mention that you could alternatively use sconfig to rename the computer and set the IP + DNS address.
To start sconfig just type "sconfig" at the command line.

Set IP Address
New-NetIPAddress -InterfaceAlias Ethernet -IPAddress 10.0.0.10 -DefaultGateway 10.0.0.1 -PrefixLength 24



(if you mess up the IP address)
remove-netipaddress -ipaddress x.x.x.x -defaultgateway x.x.x.x

Set DNS address
Set-DnsClientServerAddress -InterfaceAlias Ethernet -ServerAddress 10.0.0.100

*make sure everything looks right
ipconfig /all

Rename Computer
Rename-Computer -NewName NewComputerNAME

Reboot
(even though this is a command line command, it will work within powershell)
shutdown /r /t 1

Log back in, start PowerShell, Add computer to domain
Add-Computer -DomainName domain.local -DomainCredential (Get-Credential)

Reboot

shutdown /r /t 1

Install AD
*log back in with (administrative) domain credentials, start powershell

Install-WindowsFeature AD-Domain-Services –IncludeManagementTools

(wait a few minutes)

Install-ADDSDomainController -DomainName lab.local -InstallDNS:$True –Credential (Get-Credential)

You will be asked for a SafeModeAdministratorPassword. This is the Directory Services Restore Mode Password.

"the target server will be configured as a domain controller..."

continue with this operation? Y

(a series of warnings)

The first warning lets you know that Windows Server 2012 has defaults for certain security settings that can affect very old OSes on the network such as Windows NT 4.0. The second warns that a DNS Server delegation can’t be created. Since we’re installing DNS on this server as part of the DC promotion process, both of these errors are safe to ignore.

Reboot when complete

Credit to:
Petri, setup domain controller
http://www.petri.com/setup-domain-controller-windows-2012-server-core.htm

set and remove IP address from powershell:

https://technet.microsoft.com/en-us/library/hh826150.aspx

Quick Reference for server core tasks
https://technet.microsoft.com/en-us/library/jj592694.aspx

Uninstall program from the command line, fails as non-admin, fails as admin with RUNAS

Uninstall program using "Run As" as admin fails when a non-admin is currently logged in and UAC is disabled.

The problem is as follows:
Generally helpdesk has a need to uninstall/reinstall a program on an end-user's PC whilst the end-user is logged in. Another case is admin simply needs to uninstall a program\app\driver from a non-admin end user's computer.

The problem is that if UAC is turned OFF (never notify), you cannot remove(uninstall) a program, even though you are logged in as an ADMIN, via the runas command. The process fails.
When I say UAC is disabled, I mean User Account Control is set to "never notify"

For Example:
Joe User (non admin) is currently logged in.
UAC is disabled on the user's PC (see image above).
You, a domain admin, are at the user's PC - either in person or via a screen sharing technology.
You run (from command line) "runas /user:BillyTheAdmin@domain.local cmd"
You are prompted for your password - you enter your password
A new command line opens with your credentials, you type "appwiz.cpl"
   (Alternatively you could have run "runas /user:BillyTheAdmin@domain.local appwiz.cpl")
add\remove programs opens, you select the program you wish to remove, click Uninstall.
You are prompted with "You must be an administrator.... The process fails, the app is not uninstalled/removed.

In the above scenario, IF UAC was ENABLED you would be prompted again for your username/password and the process would succeed.

*Note: To access the user account control settings as an admin by running the following:
C:\Windows\System32\UserAccountControlSettings.exe

To work around the issue and AVOID logging out the user you can uninstall\remove apps from the command line. In this example, I want to remove the Live Meeting 2007 client.

1. Open a command prompt as an administrator
    In my example, run "runas /user:BillyTheAdmin@domain.local cmd"

2. Input WMIC and press Return. You will see a prompt that looks like this:
wmic:root\cli>

3. At the new prompt, execute the following command:
product get name

This will generate a list of installed applications. On my computer (very fast PC) this took 30 seconds to return results, be patient.

4. At the prompt, execute the following command:
product where name="exact product name" call uninstall
where application name is the name of the program you wish to uninstall (use the exact name provided by the previously generated list).

In the image below, the output is from "product get name". I want to uninstall the live meeting client.

5. When prompted, input "y" to confirm that you wish to uninstall the application and press Return. In the image below the line is very long (I tried to capture it, sorry if the image appears small).

The application will be uninstalled. You will get a quasi-useless return code.

Type "Exit" to leave WMIC
Type "Exit" to close the cmmand line

Lync 2010, disable "suggested contacts" from Outlook 2010

We use Lync 2010. In my scenario, I ONLY want to see GAL/GAB, Lync Enabled users in Lync. Your situation may differ.

By default Lync 2010 pulls from Outlook's contacts when using "Search" in Lync. I find this feature annoying because we don't use Lync for calls of any kind. We only use Lync for IM and Presence internally. Hence, seeing my Outlook Contacts in Lync is of ZERO use to me. All of my Contacts show up as "Presence Unknown".

example: Tom Smith is a GAL, internal, Lync enabled user. Tom Jones of from my contact list.



Very simple Solution:

On Lync Server (mgt shell)
set-CsClientPolicy -Identity global -ExcludedContactFolders "Contacts"

This will now exclude Outlook Contact from populating Lync searches....great.

Fast Forward, upgrade Office from '07 to 2010.
Lync is now showing contacts again. This time from Outlook's "Suggested Contacts", a new feature of Outlook 2010. Suggested Contacts is a new contact folder starting in Outlook 2010. I find this feature completely useless but that is another topic.

To Get Lync to stop pulling suggested contacts into Lync searches do this:

set-CsClientPolicy -Identity global -ExcludedContactFolders "Contacts;Suggested Contacts"

To view the policy:

Get-CsClientPolicy -identity global

Check the settings:

Error delegating, Outlook 2010, The Delegates were not saved correctly, cannot activate send-on-behalf-of list, KB2593557

Outlook 2010, error delegating AGAIN.

I had a previous post with problems delegating calendar access in Outlook 2007. Now I am having problems with users delegating Inbox access in Outlook 2010.

Error looks like:

Again, KB2593557 claims to fix the problem but it does NOT! It only suppresses the error.

Add "Write personal information" (and Read personal information) to the "SELF" object in AD on the ACL.

As I looked through my users (randomly), I found some user account already had this set properly and others did not. I do not know how or why this came about but I intend on fixing it.

I figured that I would set the settings at once for all users
use this script

--== Begin Script ==--
$mailboxes = Get-Mailbox

foreach ($mailbox in $mailboxes)
 {
 $user = $mailbox.alias
 $mailboxname = $mailbox.name
 Write-Host "Processing... $user,$mailboxname"
 Add-ADPermission -Identity "$mailboxname" -User 'NT Authority\self' `
    -AccessRights ReadProperty, WriteProperty -Properties 'Personal Information'
 }

--== End Script ==--

Save as .ps1, run from Exchange Management Shell