Lync 2010 client virtualization white paper is now revised with topics like the support of Lync 2010 over a VMware View 5.0 VDI configuration and that for Citrix XenDesktop 4. This builds on top of previously updated information (Feb 2012) around user remote FX and USBR with Lync client virtualization, qualified Lync 2010 phones and devices, and expanded references. Download the updated Lync 2010 client virtualization white paper / support policy here.
Archive for July, 2012
Having looked at how to retrieve TCP IPv4 and IPv6 network information (the ‘getters’ in programming parlance), it is now time to turn our attention to edit basic network related settings with PowerShell v3. This can be realized in Windows Server 2012 (Server core or GUI), Windows 8 but not supported in down-level Windows versions (even with Windows Management Framework 3.0).
Prior to making any networking changes on the command line (or PowerShell IDE), ensure that all TCP/IP property dialog boxes are closed otherwise an error is almost certain to result:
Set-NetAdapterBinding : The operation cannot continue because another application is in the process of changing
At line:1 char:1
+ Set-NetAdapterBinding -Name “Public” -ComponentID ms_server -Enabled $False -Ver …
+ ~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidArgument: (MSFT_NetAdapter…25280BECA}:…):ROOT/StandardCi…dingSettingData) [
+ FullyQualifiedErrorId : Windows System Error 87,Set-NetAdapterBinding
By now you must have heard of or read about the many great new features in the new Lync 2013 Preview (client) from multiparty video and content sharing, multi-tab IM “tabbed conversations” and the exciting Skype integration / federation functionality.
Unlike in the past with Office Communicator 2007 R2 client, it is possible to use Lync 2013 to sign-in to an existing Lync Server 2010 CU6 backend infrastructure, both internally and remotely through the Lync Server 2010 Access Edge server.
Now that you have downloaded, installed and brought the public Lync 2013 Preview bits up and running, you may find that a number of favorite (Lync 2010) features are no longer part of the new re-designed unified communications client, potentially affecting the way you work and impacting overall productivity.
Here is a short top 5 list of the missing features in Lync 2013 that you may have grown to love or did not even know exist in the first place (in Lync 2010 client): Continue Reading »
- Office Professional Plus 2013 Preview x86, x64
- via TechNet/MSDN Susbcriber Download (link download menu)
- or use “Download Microsoft Office 365 ProPlus Preview” (at end of page “download the .msi package now“)
- includes Word 2013, Excel 2013, PowerPoint 2013, Lync 2013, Outlook 2013, Access 2013, OneNote 2013, Skydrive Pro, InfoPath, Publisher, Visio Viewer, etc.
- Visio 2013 Preview*
- Project 2013 Preview*
- Lync Server 2013 Preview (Download link)
- Documentation of Lync Server 2013 (link)
- Exchange Server 2013 Preview (Download link)
- Documentation of Exchange Server 2013 (link)
- The Office Next Blog (link)
- Lync Server 2013 Preview TechNet Forum / Newsgroup (link)
- Exchange Server 2013 Preview TechNet Forum / Newsgroup (link)
* via TechNet or MSDN subscriber downloads
With Windows 8 and Windows Server 2012, PowerShell v3 firmly establishes itself as the “go-to” choice for almost everything an IT administrator needs to manage the Windows operating system platform. Be it administration of storage disk pool, network configuration, remote access and control, security, group policy, Active Directory user or Branch Cache, there is (surely) a cmdlet* or two to fit your management needs.
Although still supported, the veteran netsh utility covering the networking, security and firewall space, is gradually going to make way for its cmdlet counterparts as evidenced here:
PS C:\Windows\system32> netsh
In future versions of Windows, Microsoft might remove the Netsh functionality
for Windows Firewall with Advanced Security.
Microsoft recommends that you transition to Windows PowerShell if you currently
use netsh to configure and manage Windows Firewall with Advanced Security.
Type Get-Command -Module NetSecurity at the Windows PowerShell prompt to view
a list of commands to manage Windows Firewall with Advanced Security.
Visit http://go.microsoft.com/fwlink/?LinkId=217627 for additional information
about PowerShell commands for Windows Firewall with Advanced Security.
Starting with this tutorial, I am going to help get you up to speed with the essence of working with PowerShell v3 that really matters to IT Professionals, ease the pain along the way and bridge the learning gap towards efficient IT automation. What better way to begin than looking at common TCP and IPv4, IPv6 networking tasks? This works on Windows Server 2012 full GUI graphical version or Windows Server 2012 Server Core Edition, and Windows 8 client. No connectivity = no remote access ¿de verdad?
Continue Reading »
An der Worldwide Partner Konferenz 2012 (WPC), die zurzeit in Kanada/Toronto stattfindet, wurde das grob Datum der nächsten Generation von Windows Server 2012 (und Windows 8 client) bekannt gegeben. Das Betriebssystem wird generelle im September 2012 auf das Markt erscheinen (mehr hier).
Bereiten Sie sich heute für den effizienten private Cloud Einsatz vor und sicheren die Zukunft mit den aktuellsten EB-Zürich Kurs Angeboten (Windows Server 2012 PowerShell training courses in Zurich):
- Windows PowerShell V3 Kurs (link)
- Windows Server 2012: Basics Kurs (link)
- Windows Server 2012: Update Kurs (link)
Chances are that you have all you absolutely need to successfully configure and put into production the federation feature in your Lync Server 2010 infrastructure. Besides opening the prescribed firewall ports and assignment of appropriate certificates, your public DNS servers must be setup with the required A (host) as well as SRV records*. Only then can you and your peers** with on-premise Lync setup be able to automatically lookup and discover each other’s SIP domain to hit the right Lync Server 2010 Access Edge Server#.
Provided that an organization seeking to Lync federate is not on your block or black list, everything just works auto-magically thereafter. That is to say, Lync 2010 client users simply need to enter the SIP address of their correspondences in the “Find a contact or dial number” field and way they go (IM and/or audio and video, if permitted).
Problem is - what happens if your public DNS service provider or your own external DNS Servers do not support SRV records? Does that mean you are ‘doomed’ in your little island with no means to extend the wonders of Lync UC to federate with your outside contacts**?