Lync 2010 Spell Check

Hi
Is there a way to get spell checking working with Lync 2010 without having to set up third party software? I have Office 2010 installed and I did read somewhere that if you download and install Office 2013 proofing tools it should work, but it hasn't.
Any help would be great
Thanks
EverJay

Check out Matt Landis' write up here. If you don't want 3rd party, basically the only other option is to run Windows 8
http://windowspbx.blogspot.ca/2011/10/lync-30-second-tip-of-day-7-spell.html
If this helped you please click "Vote As Helpful" if it answered your question please click "Mark As Answer"
Georg Thomas | Lync MVP
Blog www.lynced.com.au | Twitter
@georgathomas
Lync Edge Port Check (Beta)

Similar Messages

Enable OWA 2010 Spell Check On As Default?

The default setting for the Outlook Web App for Exchange 2010 is off and if users want spell check in OWA, they have to go into Options and find the check box to enable it.
We would like to set the OWA spell check default to be enabled, so that the users only have to go into the options if they want to turn it off.
How can we set the default setting to be spell check enabled for OWA 2010?

We need to get Windows 8.1 Pro licenses for every computer (to join them to the domain), but we would not need to purchase a separate volume license for every computer.
My understanding is that we only need a single 8.1 Pro volume license to obtain the Volume license media and activation key and then we can apply that to all the computers in our organization that are already otherwise licensed to have the version of the
OS.
We only need Volume licensing for the purpose of reimaging so we won't have to deal with manually entering a different retail key on every system and manually activating each one.
It appears we could use the $100 Pro Pack to upgrade each system from Bing to Pro, but the Pro Pack upgrade would then be tied to the OEM license which is tied to the hardware, so you lose the licenses if the computers are replaced. However, I think
if we buy the full $199 Windows 8.1 retail media for each system, we could reuse the license in the future if we replace these systems due to damage or loss

Outlook 2010 Spell Checker AutoCorrect Issue

I have a senior executive who is running Office Professional 2010 Plus (32-bit) on Windows 7 Enterprise. His Outlook spell checker has been working fine up to very recently (not sure of the exact date of his issue).
AutoCorrect is turned on in Outlook.
When he types an E-mail, if a word is typed incorrectly, Outlook will not flag it with the red curly lines until he presses the Enter button one time. From that point forward, incorrect words will be marked once he presses the spacebar. No correction
occurs until the Enter button is pressed one time.
I ran a repair on Office on his machine and disabled then re-enabled "Check Spelling as you type."
Can anyone advise what is wrong .. that the user must press the Enter key one time to start the spell checker. It is not doing it on either of my 2 machines.
Any help would be greatly appreciated. Thank you!
David Langer Helpdesk Analyst Kimco Realty Corporation [email protected]

Compare the AutoCorrect setting from the File > Options > Mail > Spelling and AutoCorrect > AutoCorrect Options, is there any difference between yours and the following one?
Tony Chen
TechNet Community Support

Office 2010 spell check not working

Hi,
I cant get my spell check to work or underline any incorrect words. I have tried reinstalling word, deleting normal.dotm also the suggestions here
http://social.technet.microsoft.com/Forums/en-US/office2010/thread/eb94c560-9bc3-4b51-a2dc-bee5cef46bb0 and here
http://support.microsoft.com/kb/970826 and still no joy.
If I email a doc to somebody else their spell checker will also not pick up and wrong spellings in my doc
Any ideas?
Celtic

Hi,
Thank you for using
Microsoft Office for IT Professionals Forums.
From your description, please try the following methods:
1.
Open the problem document.
2.
Press the
Ctrl+A keys to select the entire text.
3.
From the
Review tab, select Language then Set Proofing Language…
4.
In the
Language dialog make sure the correct language is selected.
5.
Verify the checkbox
Do not check spelling or grammar is unchecked.
6.
Click
OK.
7.
Click the
File tab.
8.
Under
Help, click Options.
9.
Under
Correcting spelling and grammar in Word, click Recheck Document.
10.
To recheck the spelling and grammar, click
Yes when you see the following message: This operation resets the spelling checker and the grammar checker so that Word will recheck words and grammar you previously checked and chose to ignore. Do you want to continue?
11.
In the
Word Options dialog box, click OK to get back to the document.
12.
On the
Review tab, in the Proofing group, click
Spelling & Grammar.
Please take your time to try the suggestions and let me know the results at your earliest convenience. If anything is unclear or if there is anything
I can do for you, please feel free to let me know.
Sincerely
Rex Zhang
Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Word 2010 spell check gets disabled after Windows Updates

Each time the computer receives updates, the proofing settings seem to revert to disabled. The settings getting reset are
- Check spelling as you type
- Mark grammar errors as you type
- Check grammar with spelling
I only notice the issue in Word and have tried running a repair on Office. Any help is appreciated

Hi,
Just checking in to see if the information was helpful. Please let us know if you would like further assistance.
Thanks,
Melon Chen
Forum Support
Come back and mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback on our support, please click
here

2010 OUTLOOK SPELL CHECKER

Outlook 2010 spell checker stopped working.
Its not auto correcting, or when you go to spell check it says all ok - when there are errors
i have checked the language is set ok, everything seems the same as it was
any ideas?

please check read actical from below link.
http://blog.lanlogic.net/blog/spell-check-in-outlook-2010-not-working/
https://support.office.com/en-au/article/Choose-how-spell-check-and-grammar-check-work-71fd027a-be9c-42b0-8055-75f46324a16a

SBC between Lync 2010 and ExUM 2010

Can we integrate Lync 2010 to ExUM 2010 voice mail if there is a session border controller connected in between them using TLS SIP Trunks?

Hi, SBC allow different parts of the network to communicate through the use of a variety of techniques such as below, is one of ways connection mediation server to telephone network provider; Integration Lync 2010 with ExUM 2010 rather than make them communication
together, furthermore, they are need to be making MTLS connection, query contact object from AD and apply dialplan to let inbound dialing.
NAT traversal
SIP normalization via SIP message and header manipulation
IPv4 to IPv6 interworking
VPN connectivity
Protocol translations between SIP, SIP-I, H.323
So if you need to integrate premise Lync 2010 with hosted ExUm 2010, I would suggest you make them integrated as Mark said.
More information about how SBC worked in Lync 2010, please check this document.
Multiple Gateway Support:
http://technet.microsoft.com/en-us/library/gg398971.aspx
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Article ID: 2809243 Need Readme for Lync 2010.

Tried to find the new CU for Lync 2010 and found Article ID: 2809243, but this only contains readme for Lync 2013. Does anyone know where to find the right one for Lync 2010?

Check here for a current list including the April 2014 update:
http://support.microsoft.com/kb/2493736
Direct link to the April update:
http://support.microsoft.com/kb/2957044
I'd stick with the first link, and run the LyncServerUpdateInstaller and back end database updates when you're aware of new releases. It just makes life easy.
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
SWC Unified Communications

IE10 Spell Check on Infopath 2010 Browser Enabled Forms

We are rolling out some new InfoPath browser enabled forms in SharePoint 2010. We are hoping to use the Internet Explorer 10 spell check functionality, as I know the InfoPath spell check functionality isn't available in browser enabled forms.
What we've found is that IE10 spell check functionality appears to only work in Rich Text multiline boxes. Single Line or Plain Text multi-line text boxes don't support the spell check, which is causing some frustration.
I found this page that outlines how IE10's spell check engine works:
http://ie.microsoft.com/testdrive/Browser/SpellChecking/
It specifies that: "Spellchecking is active by default on <textarea> and
contenteditable elements, and off by default for text boxes. Web developers can override the defaults using the <tt>spellcheck</tt> attribute."
I assume this means that it doesn't interpret the single line and plain text controls as textarea or contentditable elements.
So, any idea how to set the spellcheck attribute in InfoPath, or otherwise force this? Thanks!

Hi,
I understand that you want to enable spelling check in InfoPath browser enabled forms. You can add a Content Editor Web Part in your NewForm.
1. Right click the Add new item link in your list/library
2. Copy the URL and open it in a new tab
3. Add a Content Editor Web Part and add below JS code:
<script language="javascript" src="/_layouts/1033/SpellCheckEntirePage.js?rev=zYQ05cOj5Dk74UkTZzEIRw%3D%3D" type="text/javascript"></script>
<script language="javascript" type="text/javascript">
function CheckSpelling()
SpellCheckEntirePage('/_vti_bin/SpellCheck.asmx', '/_layouts/SpellChecker.aspx');
</script>
<a onclick="CheckSpelling();" href="javascript:"><img alt="Spell Check" src="_layouts/1033/images/RTE2SPCHK.GIF" style="border-bottom: 0px; border-left: 0px; border-top: 0px; border-right: 0px"/></a>
4. When you click Add new item link, you can see a spell check button in your page.
Thanks,
Kenon Yin

2010 Publishing Site - Disable automatic spell check

We have a 2010 publishing site.. and evertime you publsih a page it does an automatic spell check. Can this be disabled?
I found how to disable spell check on lists but I need to stop the auto check on page publish.
Thanks!
sayitfast

I also experienced this issue.
So i tried uncommenting the registerSpellingHandler() line in the Spellcheck.js files like suggested by sayitfast. This worked for me in my dev environment. But i didn't like messing around with the default SharePoint files under the 15 hive in the prod
environment.
So i searched a bit more and found a decent solution for this. You can disable the spell check for certain fields by setting the "excludeContentFromSpellCheck" attribute to "true" on text area and input controls that you dont want to be spell checked. I
did this on all my page layouts. Now i dont get false positives anymore.
The solution i found was this one: http://blog.cube4.com.au/?p=1016
This worked for SharePoint 2013. I dont know if this would work for SharePoint 2010 also.

Lync 2010 Voice & Video Support on Windows 2012 R2 SP1 RDSH & RDVH

Hello - We have successfully demonstrated RDSH & RDVH using Windows 2012 R2, Windows 8 virtual desktops and Dell T10 Zero clients. RemoteFX has been successfully tested as well for Printing across RDSH & RDVH environments.
Problem at hand is that we are unable to showcase Lync 2010 Voice & Video calling across both these environments (RDSH & RDVH).
RDSH Environment
In an RDSH environment, we observe that a Platronics headset connected to the Dell T10 thin client is able to get redirected to the RDSH Server using RemoteFX and in-turn the RDSH Server is able to detect the connected hardware. However, the Lync 2010 client,
published using RDSH, is UNABLE to detect the connected audio device.
As for Logitech Webcam connected to the Dell T10 thin client, we have no issues with device detection and the Lync 2010 client is able to see the connected Webcam device.
RDVH Environment (Pooled Desktop)
As for the RDVH environment, we observe that both the Platronics headset & Logitec Webcam connected to the the Dell T10 thin client are UNABLE to get redirected to the RDVH Server using RemoteFX. We have enabled RemoteFX via Group policy in this environment.
Queries:
A. Could you help providing some direction into troubleshooting/isolating the audio-device detection issue on Lync clients in an RDSH environment.
B. Could you help providing some direction into troubleshooting/isolating the audio & webcam re-direction issue in an RDVH environment. FYI, our test bed server does NOT support GPU and wanted to check if that would be a limitation towards detection
of these devices?
Thanks
Srinath
sgopalkr

Hi Dharmesh,
Thank you for a response.
We had already enabled Audio and Video playback option.
But when we have tested with windows 7 desktop machine, the audio devices are detecting in Lync client in both RDVH and RDSH
environment and we are able to make audio calls. So we are planning to test with the different thin clients. Post we will update the same.
Thanks.
Manikandan

For Your Consideration: Ultimate Lync 2010 client install with SCCM 2007

While the subject of my post may be very presumptuous, I submit the following for your consideration to answer the often-asked question about how to deploy Lync 2010 client with SCCM.
Background:
I cannot understand why Microsoft made the Lync install so darned confusing, complex, and convoluted.
After our Lync 2010 FE server was up and running and all users migrated off our OCS server to the Lync environment, I spent about a month and a half trying to figure out how to:
1. Uninstall the OCS 2007 R2 client
2. Install all prerequisites for the Lync client
3. Install Lync on all user workstations silently.
While researching this, the simple answer I kept seeing given to this question was, "just use the .exe with the right switches according to the TechNet article here: http://technet.microsoft.com/en-us/library/gg425733.aspx". Well, my response is, I
tried that and while the program installed itself correctly pushed through SCCM, because I was doing it using an administrative account (i.e. the SYSTEM account) due to our users not having admin rights, when the install was done, Lync would automatically
start up, but in the SYSTEM context so that the user couldn't see it was running, they go to run it and it won't run for them. I was unable to find any switch or option to prevent the automatic launch. I suppose the simple solution to that would
be to have the user reboot, but that's unnecessarily disruptive and was contrary to the desire to make this a silent install.
The next simplest answer I saw was, "extract the MSI and use that with the right switches". Problem with that is that the MSI by itself doesn't remove the OCS client or install the prerequisites, and also either requires a registry change to even allow
the MSI to be used or a hacked MSI that bypasses the registry key check. I tried to put a package together to uninstall OCS, install the prereqs, and use a hacked MSI, but I never could get the MSI hacked properly. The other problem I ran into
was detecting if the OCS client was running in a predictable way so I could terminate it, properly uninstall it, and then do the rest of the installations. It was this problem that ultimately led me to the solution that I'm about to detail and that has
worked marvellously for us.
Solution:
As I said before, when I first looked at this problem, I started by building a typical software deployment package (Computer Management -> Software Distribution -> Packages) and then created the programs to do the install. My first attempt was
just with the .exe file provided as-is by Microsoft using the switches they document in the link above for IT-Managed Installation of Lync, and...well, the end result wasn't quite as desirable as hoped. So, my next attempt was to extract all the prerequisite
files and the Lync install MSI (both for x86 and x64), attempt to hack it to get around the "UseMSIForLyncInstallation" registry key, and make the command-lines to terminate OCS and uninstall it.
In the past when I had an install to do with SCCM that also required uninstalling an older version of a given application, I typically used the program-chaining technique. That's where you have, for example, 3 or more programs that run in a package
in a sequence and you have Program 3 be set to run after Program 2 does and then set Program 2 to run after Program 1 so you get the desired sequence of Programs 1-2-3 running in that order. So, I created programs to 1) kill Communicator.exe 2) uninstall
Communicator 2007 R2 by doing an "msiexec /uninstall {GUID}" 3) install Silverlight 4) install Visual C++ x86 5) optionally install Visual C++ x64, and then 6) install the Lync x86 or x64 client. That final step was always the point of failure because
I couldn't get the hacked MSI for the Lync Client install to work. I also realized that if Communicator wasn't running when the deployment started, that step would fail and cause the whole process to bail out with an error. That's one of the downsides
of program-chaining, if one step fails, SCCM completely bails on the deployment. This is what also led me to the key to my solution: TASK SEQUENCES.
I'm not sure how many people out there look in the "Operating System Deployment" area of SCCM 2007 where Task Sequences normally live, but I also wonder how many people realize that Task Sequences can be used for more than just Operating System deployments.
One of the biggest advantages of a task sequence is you can set a step to ignore an error condition, such as if you try to terminate a process that isn't running. Another advantage is that task sequences have some very good built-in conditionals that
you can apply to steps, for example, having the sequence skip a step if a certain application (or specific version of an application) is not installed on the machine. Both of those advantages factor highly into my solution.
OK, for those who already think this is "TL;DR", here's the step-by-step of how to do this:
First, you need to extract all the files from the LyncSetup.exe for your needed architectures. We have a mix of Windows XP and Windows 7 64-bit, so my solution here will take both possibilities into account. To extract the files, just start up
the .exe like you're going to install it, but then when the first dialog comes up, navigate to "%programfiles%\OCSetup" and copy everything there to a new location. The main files you need are: Silverlight.exe, vcredist.exe (the x64 LyncSetup.exe includes
both x86 and x64 Visual C++ runtimes, you need them both, just rename them to differentiate), and Lync.msi (this also comes in an x86 and x64 flavor, so if you have a mix of architectures in your environment, get both and either put them into their own directories
or rename them to reflect the architecture).
For my setup, I extracted the files for the x86 and x64 clients and just dumped them each into directories named after the architectures.
Next, move these files into a directory to your SCCM file server, whatever it might be that you deploy from, in our case, it was just another volume on our central site server. Go to the SCCM console into Computer Management -> Software Distribution
-> Packages and then create a new package, call it something meaningful, and then point to the directory on your SCCM file server for the source files.
Now you need to create 3 to 5 programs inside the package:
1. Name: Silverlight
   Command Line: x86\Silverlight.exe /q     (remember, inside my main Lync install folder on my distribution point, I have an x86 directory for the files from the x86 installer and an x64 folder for the files from the x64 installer.
The fact is the Silverlight installer is the same in both, so you only need one of them.)
   On the Environment tab: Program can run whether or not a user is logged in, runs with administrative rights, Runs with UNC name
   On the Advanced tab: Suppress program notifications
   All other options leave default.
2. Name: Visual C++ x86
    Command Line: x86\vcredist_x86.exe /q
   On the Requirements tab: Click the radio button next to "This program can run only on specified client platforms:" and then check off the desired x86 clients.
   Environment and Advanced tabs: same as Silverlight
   (If you have only x64 clients in your environment, change all x86 references to x64. If you have a mixed environment, create another program identical to this one, replacing references to x86 with x64.)
3. Name: Lync x86
    Command Line: msiexec /qn /i x86\Lync.msi OCSETUPDIR="C:\Program Files\Microsoft Lync" (The OCSETUPDIR fixes the issue with the Lync client wanting to "reinstall" itself every time it starts up)
    Requirements, Environment, and Advanced tabs: Same as with Visual C++ and Silverlight
    (Same deal as above if you have all x64 clients or a mix, either change this program to reflect or make a second program if necessary)
Now you need to make the Task Sequence. Go to Computer Management -> Operating System Deployment -> Task Sequences. Under the Actions pane, click New -> Task Sequence. In the Create a New Task Sequence dialog, choose "create a
new custom task sequence", Next, enter a meaningful name for the task sequence like "Install Microsoft Lync", Next, Next, Close.
The task sequence will have up to 12 steps in it. I'll break the steps down into 3 phases, the prereqs phase, uninstall OCS phase, and then Lync install phase.
Prereqs Phase:
These are the easiest of the steps to do. Highlight the task sequence and then in the Actions pane, click Edit.
1. Click Add -> General -> Install Software. Name: "Install Microsoft Silverlight". Select "Install a single application", browse to the Lync package created earlier and then select the Silverlight program.
2. Add -> General -> Install Software. Name: "Install Microsoft Visual C++ 2008 x86". Install Single Application, browse to the Lync package, select the Visual C++ x86 package.
As before, if you're an all-x64 environment, replace the x86 references with x64. If you have a mixed environment, repeat step 2, replacing x86 with x64.
3. Add -> General -> Run Command Line. Name: "Enable Lync Installation". This step gets around the UseMSIForLyncInstallation registry requirement. The Lync client MSI simply looks for the presence of this key when it runs, so
we'll inject it into the registry now and it doesn't require a reboot or anything. It just has to be there before the client MSI starts.
Command Line: reg add "hklm\Software\Policies\Microsoft\Communicator" /v UseMSIForLyncInstallation /t REG_DWORD /d 1 /f
Uninstall OCS Phase:
This part consists of up to 6 Run Command Line steps. (Add -> General -> Run Command Line)
4. Name: "Terminate Communicator". Command Line: "taskkill /f /im communicator.exe". On the Options page, check the box next to "Continue on error". This will terminate the Communicator process if it's running, and if it's not, it'll
ignore the error.
5. Name: "Terminate Outlook". Command Line: "taskkill /f /im OUTLOOK.exe". Check the "Continue on error" on the Options page here too. Communicator 2007 hooks into Outlook, so if you don't kill Outlook, it might prompt for a reboot
because components are in use.
(NOTE: If necessary, you could also add another step that terminates Internet Explorer because Communicator does hook into IE and without killing IE, it might require a restart after uninstalling Communicator in the next steps. I didn't run into
this in my environment, though. Just repeat step 5, but replace OUTLOOK.EXE with IEXPLORE.EXE)
6. Name: "Uninstall Microsoft Office Communicator 2007". Command Line: "msiexec.exe /qn /uninstall {E5BA0430-919F-46DD-B656-0796F8A5ADFF} /norestart" On the Options page: Add Condition -> Installed Software -> Browse to the
Office Communicator 2007 non-R2 MSI -> select "Match this specific product (Product Code and Upgrade Code)".
7. Name: "Uninstall Microsoft Office Communicator 2007 R2". Command Line: "msiexec.exe /qn /uninstall {0D1CBBB9-F4A8-45B6-95E7-202BA61D7AF4} /norestart". On the Options page: Add Condition -> Installed Software ->
Browse to the Office Communicator 2007 R2 MSI -> select "Match any version of this product (Upgrade Code Only)".
SIDEBAR
OK, I need to stop here and explain steps 6 and 7 in more detail because it was a gotcha that bit me after I'd already started deploying Lync with this task sequence. I found out after I'd been deploying for a while that a tech in one of our remote
offices was reinstalling machines and putting the Communicator 2007 non-R2 client on instead of the R2 client, and my task sequence was expecting R2, mostly because I thought we didn't have any non-R2 clients out there. So, at first I just had our Help
Desk people do those installs manually, but later on decided to add support for this possibility into my task sequence. Now, when you normally uninstall something with msiexec, you would use the Product Code GUID in the command, as you see in steps 6
and 7. All applications have a Product Code that's unique to a specific version of an application, but applications also have an Upgrade Code GUID that is unique for an application but common across versions. This is part of how Windows knows that
Application X version 1.2 is an upgrade to Application X version 1.1, i.e. Application X would have a common Upgrade Code, but the Product Code would differ between versions 1.1 and 1.2.
The complication comes in that Communicator 2007 and Communicator 2007 R2 have a common Upgrade Code, but different Product Codes and the "MSIEXEC /uninstall" command uses the Product Code, not the Upgrade Code. This means that if I didn't have step
6 to catch the non-R2 clients, step 7 would be fine for the R2 clients, but fail on non-R2 clients because the Product Code in the MSIEXEC command would be wrong. Luckily, we only had one version of the non-R2 client to deal with versus 4 or 5 versions
of the R2 client. So, I put the command to remove Communicator 2007 non-R2 first and checked for that specific product and version on the machine. If it was present, it uninstalled it and then skipped over the R2 step. If non-R2 was not present,
it skipped that step and instead uninstalled any version of the R2 client. It's important that steps 6 and 7 are in the order they are because if you swap them, then you'd have the same outcome as if step 6 wasn't there. What if neither is on the
machine? Well the collection this was targeted to included only machines with any version of Communicator 2007 installed, so this was not a problem. It was assumed that the machines had some version of Communicator on them.
8. Name: "Uninstall Conferencing Add-In for Outlook". Command Line: "msiexec.exe /qn /uninstall {730000A1-6206-4597-966F-953827FC40F7} /norestart". Check the "Continue on error" on the Options Page and then Add Condition ->
Installed Software -> Browse to the MSI for this optional component and set it to match any version of the product. If you don't use this in your environment, you can omit this step.
9. Name: "Uninstall Live Meeting 2007". Command Line: "msiexec.exe /qn /uninstall {69CEBEF8-52AA-4436-A3C9-684AF57B0307} /norestart". Check the "Continue on error" on the Options Page and then Add Condition -> Installed Software
-> Browse to the MSI for this optional component and set it to match any version of the product. If you don't use this in your environment, you can omit this step.
Install Lync phase:
Now, finally the main event, and it's pretty simple:
10. Click Add -> General -> Install Software. Name: "Install Microsoft Lync 2010 x86". Select "Install a single application", browse to the Lync package created earlier and then select the "Lync x86" program. As before, if you
only have x64 in your environment, replace the x86 with x64, or if you have a mixed environment, copy this step, replacing x86 references with x64.
And the task sequence is done! The final thing you need to do now is highlight the task, click Advertise in the Actions pane, and deploy it to a collection like you would with any other software distribution advertisement. Go get a beer!
Some final notes to keep in mind:
1. You can't make a task sequence totally silent...easily. Users will get balloon notifications that an application is available to install. The notifications cannot be suppressed through the GUI. I've found scripts that supposedly
hack the advertisement to make it be silent, but neither of them worked for me. It was OK, though because in the end we wanted users, especially laptop users, to be able to pick a convenient time to do the upgrade. The task sequence will appear
in the "Add/Remove Programs" or "Programs and Features" Control Panel. You can still do mandatory assignments to force the install to happen, you just can't make it totally silent. On the plus side, the user shouldn't have to reboot at any point
during or after the install!
2. In the advertisement setup, you can optionally show the task sequence progress. I've configured the individual installs in this process to be silent, however, I did show the user the task sequence progress. This means instead of seeing
5 or 6 Installer windows pop up and go away, the user will have a single progress bar with the name of the step that is executing.
3. One step that I didn't consider when I actually did this was starting the Lync client as the user when the install was complete. The user either had to start the client manually or just let it start on its own at the next logon. However,
while I was writing this, I realized that I could possibly start the client after installing by making another Program in the Lync Package with a command line that was along the lines of "%programfiles%\Microsoft Lync\communicator.exe" and then in the Environment
tab, set it to "Run with user's rights" "only when a user is logged on".
4. My first revision of this task sequence has the Prereqs phase happening after the OCS uninstall phase, but I kept running into problems where the Silverlight installer would throw some bizarre error that it couldn't open a window or something wacky
and it would fail. Problem was, I couldn't re-run the task sequence because now it would fail because OCS had been uninstalled, so that's why the Prereqs happen first. It ran much more reliably this way.
5. For some reason that baffles me, when I'd check the logs on the Site Server to monitor the deployment, I'd frequently see situations where the task sequence would start on a given machine, complete successfully, almost immediately start again, and
then fail. I'm not sure what is causing that, but I suspect either users are going to Add/Remove Programs and double-clicking the Add button to start the install instead of just single-clicking it, or the notification that they have software to install
doesn't go away immediately or Lync doesn't start up right after the install, so they think the first time it didn't take and try it a second time.
I hope this helps some of you SCCM and Lync admins out there!

On Step 8 I found multiple product codes for the Conferencing Add-In for Outlook. Here's a list of the ones I found in the machines on my network:
{987CAEDE-EB67-4D5A-B0C0-AE0640A17B5F}
{2BB9B2F5-79E7-4220-B903-22E849100547}
{13BEAC7C-69C1-4A9E-89A3-D5F311DE2B69}
{C5586971-E3A9-432A-93B7-D1D0EF076764}
I'm sure there's others one, just be mindful that this add-in will have numerous product codes.

Bug? Mailto: in combination with Office 2013 Spell Checking.

Dear community,
For one of our sollutions we use the mailto protocol to send a hyperlink which users can use to automatically open a predefined new-email-window.
This works fine with Office Professional Plus 2010 [EN-US] (32bit) in combinatione with Microsoft Office Language Pack 2010 - Dutch/Nederlands (32bit).
However, Office Professional Plus 2013 [EN-US] (32bit), in combination with Microsoft Office Language Pack 2013 - Dutch/Nederlands (32bit), crashes whenever the spellingcheck is started.
The mailto-command we use to reproduce this problem is (enter command in Internet Explorer, open with Outlook):
mailto:[email protected]?subject=%20Actie%20vereist&body=%5b2103162%2f335159076094968874376260057075247208793%5d
During analyses we concluded:
- Office Configuration Analyzer Tool 1.2 (Full Scan) did not find any related issues.
- Spellchecker crashes while checking the text within the body.
- Uninstalling Microsoft Office Language Pack 2013 - Dutch/Nederlands solves the problem, but obviosly, we want to keep the Dutch spelling check functionality.
- Standard Englsh (U.S.) spellchecking functions without problems.
- This problem is reproducable on any computer running Office Professional Plus 2013 [EN-US] in combination with the Dutch (Nederlands) spelling check. Tried multiple hardware configurations (Intel based) and multiple OS's (Windows 7 Enterprise
(64bit), Windows 8.1 Enterprise (64bit), Windows 8.1 Pro (64bit). All with the same result.
Is there way to solve this issue, without loosing Outlook 2013 as client and Dutch Spelling Check capabilities?
Kind regards,
Leon Kandelaars.

Hi Steve,
Thanks for your reaction.
Q - Do you mean Outlook crashes when we click the Spelling & Grammar button under Review tab?
A - Yeah, if you try to edit the mail and have 'check spelling as you type' activated, it wil crash as well.
Q - If we copy the email body and paste it to a new email message, will this issue continue?
Does this   issue happen with other Office 2013 programs? Please try to use 'spell check' in word and check if the same issue occurs.
A - If you copy the generated body to a new email or Word 2013, the spelling check will in both cases crash the application.
Q - In addition, we can also have a look at the event log to see if we can find anything useful.
A - The crash generates an "Application" "Hang error". I've generated 2 (1 with Outlook, 1 with Word):
Generated mail, spellcheck crashes Outlook:
Log Name:      Application
Source:        Application Hang
Date:          10-3-2015 9:52:31
Event ID:      1002
Task Category: (101)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      xxxx.xxxx.xxx.nl
Description:
The program OUTLOOK.EXE version 15.0.4693.1000 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
Process ID: 87c
Start Time: 01d05b0effb4e6f8
Termination Time: 0
Application Path: C:\Program Files (x86)\Microsoft Office\Office15\OUTLOOK.EXE
Report Id: bf3cde85-c702-11e4-a8c6-485ab6f00dbb
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Application Hang" />
    <EventID Qualifiers="0">1002</EventID>
    <Level>2</Level>
    <Task>101</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-03-10T08:52:31.000000000Z" />
    <EventRecordID>14242</EventRecordID>
    <Channel>Application</Channel>
    <Computer>xxxx.xxxx.xxx.nl</Computer>
    <Security />
</System>
<EventData>
    <Data>OUTLOOK.EXE</Data>
    <Data>15.0.4693.1000</Data>
    <Data>87c</Data>
    <Data>01d05b0effb4e6f8</Data>
    <Data>0</Data>
    <Data>C:\Program Files (x86)\Microsoft Office\Office15\OUTLOOK.EXE</Data>
    <Data>bf3cde85-c702-11e4-a8c6-485ab6f00dbb</Data>
    <Binary>55006E006B006E006F0077006E0000000000</Binary>
</EventData>
</Event>
Copied body to Word, spellcheck crashes Word:
Log Name:      Application
Source:        Application Hang
Date:          10-3-2015 9:57:15
Event ID:      1002
Task Category: (101)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      xxxx.xxxx.xxx.nl
Description:
The program WINWORD.EXE version 15.0.4693.1000 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
Process ID: 964
Start Time: 01d05b0fe8e683af
Termination Time: 0
Application Path: C:\Program Files (x86)\Microsoft Office\Office15\WINWORD.EXE
Report Id: 6a7dd15f-c703-11e4-a8c6-485ab6f00dbb
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Application Hang" />
    <EventID Qualifiers="0">1002</EventID>
    <Level>2</Level>
    <Task>101</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-03-10T08:57:15.000000000Z" />
    <EventRecordID>14247</EventRecordID>
    <Channel>Application</Channel>
    <Computer>xxxx.xxxx.xxx.nl</Computer>
    <Security />
</System>
<EventData>
    <Data>WINWORD.EXE</Data>
    <Data>15.0.4693.1000</Data>
    <Data>964</Data>
    <Data>01d05b0fe8e683af</Data>
    <Data>0</Data>
    <Data>C:\Program Files (x86)\Microsoft Office\Office15\WINWORD.EXE</Data>
    <Data>6a7dd15f-c703-11e4-a8c6-485ab6f00dbb</Data>
    <Binary>55006E006B006E006F0077006E0000000000</Binary>
</EventData>
</Event>

Lync 2010 and Lync 2013 blinking icon in taskbar not working properly

Hi,
We're experiencing a strange behaviour. Lync IM notifications are supposed to work this way below:
1) Notification bubble on the right-bottom corner
2) After a few seconds, a blinking icon in the task bar
3) After a few seconds, a coloured icon remains in the task bar
Some of our users, both Lync 2010 and Lync 2013, go 1) and 2) but then icon won't remain in the task bar, so they don't realize they have a conversation waiting (Windows XP and Windows 7).
If they open the icon, the conversation is there and coloured, and they can answer.
In my computer, it has also happened but most of the time it works fine (testing it, maybe it works 15 times and fails 1). Nevertheless, a lot of people is suffering from this strange behaviour.
We have looked into the causes but haven't found anything.
Any clue?
Thanks!

How long have you seen the problem?
What version of your Lync client? Try to update your Lync client to the latest version.
Try to repair office 2013.
Uninstall and reinstall Lync 2010.
Please install Lync 2013 or Lync 2010 on a fresh installation of Window to check if you can still see this problem.
Lisa Zheng
TechNet Community Support

Lync 2013 domain discovery not working, but Lync 2010 works flawlessly

We are using Lync 2013 and Lync 2010 in our company. Upon installation Lync 2010 can connect absolutely fine with for example [email protected], but when we use Lync 2013 we receive a DNS error saying it cannot resolve the domain when using the same
method. I have to manually enter the internal and external servers on each deployment of Lync 2013 to sipdir.online.lync.com:443 in order for successfully login to Lync 2013. We are upgrading all users to Lync 2013 and I want to avoid having to do this
on every deployment. This has always been an issue and not something that recently became an issue.
I have double checked my CNAME and SRV from my host provider and everything is as it should be. Contacting MS support they made me change my preferred DNS to 8.8.8.8 on the network adapter for the PC, but that breaks everything you connect to internally and
is not a solution to this issue.
Any ideas?

Hi,
The forum you posted is for Lync Server On Premise only. The issue is more related to Lync online, you can also post a question on Office365 forum for assistance. Thank you for your understanding.
http://community.office365.com/en-us/f/166.aspx
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Lync 2010 Spell Check

Similar Messages

Maybe you are looking for