TipIf you use your computer frequently, consider not turning it off or having your computer enter when pressing the power button, rather than shutting down completely. Disable startup programsPrograms that are loaded as the computer starts up remain active in memory. Consequently, they are one of the main causes of a slow boot into Windows. Disabling programs you don't often use from automatically loading up each time the computer powers on can decrease boot time.ScanDisk and DefragUsing Microsoft and or similar disk utilities can help verify your is running free of errors while organizing stored data in the most efficient manner possible. We suggest running both of these utilities at least once every few months. Insufficient hard drive spaceFor your computer to run optimally, it needs at least 250 MB of available hard drive space. If you have less that this amount, slowdown in both general performance and the boot time can occur.Update drivers and WindowsCorrupt, incorrect, or out-of-date can cause many different issues.

1. Microsoft Lync Your Computer Is Running Slowly Windows 10
2. Microsoft Lync Your Computer Is Running Slowly In Windows 7
3. Computer Is Running Slow Microsoft

Make sure your computer has the latest drivers as well as any available Microsoft Windows updates.Registry cleanerAlthough we do not often recommend registry cleaners, in some rare situations they can help improve the overall performance of Windows including startup. If you have run through all the previous recommendations without strong results, you may want to clean your system registry.Format and reinstallAlthough you may need to backup some of your files and the process itself may be a bit time-consuming, you may want to. This process makes your computer run like it did when it was new. Hardware upgradesWe saved these options for last because they have a cost to the user associated with them.

That being said; they are some of the most effective ways to increase performance and decrease boot times. Adding random access memoryInstalling additional memory to the computer helps increase the overall speed of the computer and in some cases can decrease the boot up times. If your computer is running less than two Gigabytes of RAM, it may be time to upgrade.Adding a solid-state driveAn is the most effective way to raise performance across the board for any computer. On both desktop and laptop computers, moving Windows from a standard hard drive to a solid-state drive will dramatically lower your boot times.

Amazon.com has.

We are just finishing our project to roll out MS Lync 2013 in our XenDesktop environment. We've had more problems (Really nasty bugs!) in this project than nearly anything I've ever worked on. So I thought I should share the solutions we came up with to save the rest of you the same pain.What we are runningXenDesktop 5.6 FP1 on the ControllersVDA 7.1Receiver 4.1.2.1 (with private hotfix 61172275, that replaces DVCRenderingAdapter.dll)PVS 6.1Windows 7 x64XenServer 6.02Office 2010Lync client 2013Problem 1Lync 2013 uses something call 'pairing' to redirect the video to the local client to improve performance much like the HDX flash redirection. This requires that you have VDA 7.x and Receiver 4.x installed. There is a known bug though that if you disconnect the session and reconnect it then the pairing gets broken until you either close Lync or log out and back in again.Solution 1Install the 'Session State Monitor Tool' and configure it to close Lync on disconnect and open it again on reconnect. Add an entry to the registry to make this run at log on automatically. Not perfect but it does the job until Citrix and Microsoft come up with a better solution.Download here:DisconnectCommands: 'C:WindowsSystem32taskkill.exe /IM lync.exe /F'ReconnectCommands: 'C:Program Files (x86)Microsoft OfficeOffice15lync.exe'Problem 2Since installing VDA 7.1 the computers run slowly and IE 8 in particular goes very slow (IE 8 was required for a certian business application).

After much research it was discovered that new Adaptive Display 2nd generation was that cause (for more information read ). This can normally be turned off via Policy in XenDesktop 7.1, but we were still running XD 5.6 fp1Solution 2At Citrix's recomendation we reinstalled the VDA with the /nocitrixwddm switch to disable Adaptive Display 2nd gen. This significantly speeds up the virtual desktops. This also appears to disable 1st generation adaptive display.Problem 3Since installing the VDA without the WDDM driver (see solution 2), the mouse moved laggy on the screen.Solution 3In the mouse properties change the theme to none and disable mouse shadows.

This can be set globably by making a Group Policy preference item (see )Problem 4Since installing the VDA without the WDDM driver (see solution 2), the display was running in low resolution and low colour when working remotelySolution 4It turns out the /nocitrixwddm switch also disables adaptive display 1st generation, leaving the desktop no choice but to fall back to progressive display. I had to change the progressive display settings to fix this.Problem 5The Lync Client keeps trying to go through a mini set up the first time it us launched after the virtual desktop is rebooted.Solution 5The Lync client needs to be rearmed just like Office 2010 and Windows (see )Problem 6Because we now have a mixed environment of Office 2010 and Office 2013 (Lync clien is an office application) some things started to go wrong with some office 2010 apps. In particular Visio, Project, sharepoint designer and Access all suffered from the infamous 'mini setup at launch' after rebooting a VDI. In addition to this some the various search functions no longer worked. I tried all the know fixes for this and nothing worked, turns out if was a citrix issue, not MS.Solution 6Install the Lync client 2013 in private mode and then launch each application while still in private mode.

Basically I've come to the conclusion that any offce application should only ever be installed in Private mode, not as a new version in maintenance mode. It must be something to do with how the PVS agent interacts with office for the KMS activation that screws with the installation.Problem 7When having a video meeting in Lync with three or more people someones Citrix session will crash with an HDX Engine error.Solution 7Install Receiver version 4.1.2.1 with the private hotfix that replaces the DVCRenderingAdapter.dll (only reference number I have is 61172275)This list doesnt show the pain I went through to get this thing working, I'll update this if I remeber anything else. Problem 8The.cache files in the users profile do not save with the users profile when using Citrix UPM.

The files are located in this folder:C:Users%username%AppDataLocalMicrosoftOffice15.0Lyncsipfirstnamel.lastname@domain.comSolution 8Enable the ‘folders to mirror’ policy, this seems to make the.cache files roam with the rest of the profile. Set this to mirror the entire Lync folder C:Users%username%AppDataLocalMicrosoftOffice15.0LyncProblem 9Windows RM was no longer enabled after reinstalling the VDA 7.1Solution 9Run the 'WinRM quickconfig' commandProblem 10When using Lync with 'Pairing' active you cannot change the meeting type from IM to Video. You receive an error message saying that the device (the camera) is already in use. This is caused by the Citrix Receiver passing through the Microphone and Webcam into the XenDesktop session, when using pairing the 'Microsoft Lync VDI 2013' application on the client also trys to access the camera the same time as the Receiver. The Receiver normally wins because it is the first application to access the camera, this locks out the MS Lync VDI software and prevents using the camera.Solution 10In the desktop toolbar select preferences and 'mircophone and webcam' and 'Dont use my mircophone or webcamera'.

This should be enough to get it going, you can then identify the PID and VID of the web camera hardware you are using and block these in the HDX Policy 'Client USB device redirection rules'eg: Deny: VID=046D PID=082D # (Logitech HD Pro Webcam C920). Michael, first off - thanks for taking the time to document this! I'm in exactly the same boat at the moment with a POC deployment.I'm running XenDesktop 7.5 and all the components have the latest installs of all components but I'm particularly interested in Problems 7 and 10 which I'm also seeing.Where are you getting the Receiver 4.1.2.1 from? The latest I can find (including that which comes with XD 7.5) is 4.1.0.56461For the record, this is what we are running:. XenDesktop 7.5 on the Controllers.

VDA 7.5. Receiver 4.1.0.56461. PVS 7.1. Windows 7 x64. ESX 5.1.

Office 2010. Lync Client 2013Thanks, Gary. I haven't used it on an iPad myself sorry. There are two different ways to run lync on a Tablet DeviceVia Citrix XenDesktopFrom memory the Microsoft Lync VDI Plugin only works on Windows OS machines that are on the domain so it can authenticate to the Lync server, this pretty much limits you to a Microsoft Surface device if you want pairing to work. Obviously you will also need to install the Receiver on the tablet. Lync will still run in the virtual desktop on other tablet devices such as Andriod or iPad but without pairing (less performance).Native Lync App on tablet deviceYou can just install the Lync App localy on the tablet device or smart phone, which is a pretty decent choice in my opinion. You can use you smart phone to make good quality video calls using the Lync app with this method.

Microsoft Lync Your Computer Is Running Slowly Windows 10

Hi Gary,Sory for the late reply I was off work last week. The good news is that you dont need the private hotfix anymore as Citrix have rolled this into the latest release of the Receiver (4.1.2.3)Download here:I've also been having another strange issue where the Receiver's volume is lowered by Window and the Lyn VDI Plugin as posted here:Did my solution to problem 10) work for you?Michael, now I have to apologize for the late response! LOL I need to enable notifications on replies.I did find the 4.1.2.3 Receiver shortly after I posted and it does fix the issues with conference calls in Lync 2013.

We have been running XenDesktop for the last year and half nearly. Im quite happy with XenDesktop. We have rolled out Lync in our meeting rooms as our Video Conferencing solution. These are FAT clients and have no issues. Lync just works.Lync in the VDI is another story.

Microsoft Lync Your Computer Is Running Slowly In Windows 7

Bug after bug, I find one bug fix it and another surfaces often caused by the solution to the previous bug. The general Lync client stuff is going fairly well now, but in order to use pairing we were forced to upgrade the Receiver (4.1.2.3 seems pretty good, earlier 4.x releases were bugy) and VDA 7.1. I think most of my problems have been caused by the VDA update.Lync is going fairly well though not 100% (maybe 98% to 99% reliable). Probably exceptable to roll out company wide.The VDA has basicaly been an exercise in pain! Bug after bug after bug.

We are not using Thin Clients, when we rolled out XenDesktop we also replaced all our aging desktop computers. All of our desktop clients are PCs runnning Windows 7 x64 and are domain joined.

The reason for this was that there was not much difference in price between a Thinclient and a PC and they gave us greater flexability. The PCs were all built using MS Configuration Manager (so are all the same and the build is automated).We are using ultra small profile Lenovo ThinCentre M72e(These are extreamly good quality and very reliable)While we run pretty much everything inside the virtual desktop we have a few weird engineering apps that dont play nice and we installed these localy and used RES VDX to inject these into the desktop. The Lenovos are powerful enough to run any of the local apps whereas a Thinclient would cause issues. Hi MichaelGreat post.

Computer Is Running Slow Microsoft

Have one question for you. We are running XenDesktop 7.1, Hyper-V 2012 and Win7 VMs. Receiver is version 4.1.2.3.Did you ever come across an issue with Lync 2013 VDI plugin, where one ore more get no sound in a Lync call? If user A calls user B everything works fine. But if user B calls User A back, user B does not have any audio. User A hears user B, but not the other way.

When this happens user B needs to disconnect an reconnect the XenDesktop session to get the audio working again.