Archive for September, 2011

Remote Desktop Access – It’s easy with Ammyy Admin, multi-task remote control software

September 30, 2011

You can easily share a remote desktop or control a server over the Internet with Ammyy Admin. No matter where you are, Ammyy Admin makes it safe and easy to quickly access a remote desktop within a few seconds.

Ammyy Admin is trusted by more than 4 000 000 personal and corporate users.

Remote desktop sharing becomes easy with Ammyy Admin.

Download

Microsoft Lync videos/podcasts/PPTs from teched Berlin 2010

September 29, 2011

Check out the Lync videos from Microsoft teched Europe 2010. Also available as podcasts and PPT slides. Enjoy!

Microsoft Lync 2010 technology explained

Advanced SIP-Based solutions built on the Microsoft Unified Communications …

The new Microsoft Lync 2010 SDK: Integrating, Extending and Adding Contextual …

Conferencing with Lync Server 2010: What’s new, what’s behind the scenes

Microsoft Lync Server 2010: Voice Deployment

Microsoft Lync Server 2010: Voice Architecture and Planning for high …

Microsoft Lync Server 2010: Management, Administration and Delegation

Deployment, upgrade and co-existence scenarios with Microsoft Lync Server 2010

Deploying Lync Server 2010 as a primary telephony solution

Announcing The Release Of Service Pack 1 (SP1) for Microsoft Project and Project Server 2010

September 28, 2011

Service Pack 1 (SP1) for Microsoft Project Standard 2010, Microsoft Project Professional 2010 and Microsoft Project Server 2010 has been released to the Microsoft Download Center. SP1 contains a number of products updates based on customer feedback, as described in this announcement last May:  Announcing Service Pack 1 for Microsoft Project & Project Server 2010.

Before you install SP1 it is essential that you understand its content described in the links below, and thoroughly read the guidance documented on TechNet and test out SP1 in a separate environment prior to a production rollout.

The following TechNet article provides information on how to deploy Microsoft Project and Project Server 2010 SP1: Deploy Service Pack 1 for Project Server 2010.

We strongly recommend that you deploy the June 2011 Cumulative Update for Microsoft Project and Project Server 2010 when you install SP1. You can download the June 2011 Cumulative Update from the KB Articles from the links below:

The following TechNet article provides information on how to deploy Project Server Cumulative Updates: Updates for Project Server 2010

There will be a webcast on July 6th, 2011 at 8:00 am Pacific Time to give an overview of this Service Pack (which will be recorded for later viewing): TechNet Webcast: Information about Project 2010 and Project Server 2010 Service Pack 1 (Level 200). Please check out these posts for additional SP1 production information: Office 2010 and SharePoint 2010 Service Pack 1 Availability and Service Pack 1 for SharePoint 2010 Products is Now Available for Download.

Microsoft Project Server and SharePoint 2007 and 2010 August CU 2011 Announcement

September 20, 2011

The August 2011 Cumulative Updates for Microsoft Project and Project Server 2010 have now been released.  *** Update 9/7/2011 – rollup package now posted **** We did find a late issue with the SharePoint Foundation CU during our testing which we have identified and will need to re-build.  This does however mean that the server rollup patches will be delayed too – as they contain the SharePoint Foundation bits.  The current estimate is that these rollup packages will be available late next week.  The server rollup patch is the preferred patch because it contains the fixes for all of the server technologies used by Project Server 2010  The individual server patch is available should you need an August fix for Project Server before next week.  It should also allow you to start testing the Project specific fixes right away. 

This delay does not affect the August 2011 Cumulative Update for Project and Project Server 2007.

As always, we want to encourage you to test any CUs with a recent copy of your production database before deploying into production so that we can catch any problems, and fix them, in test before they start impacting a live environment.

We should also remind you that we recommend applying Service Pack 1 – http://technet.microsoft.com/en-us/library/hh272536.aspx.  This article makes many references to the June CU – the August CU is cumulative so does contain all that was shipped in the June CU so if you haven’t installed the June CU then you can just install the August CU (and SP1).  More details of SP1 can be found at http://blogs.msdn.com/b/project/archive/2011/06/28/announcing-the-release-of-service-pack-1-sp1-for-microsoft-project-and-project-server-2010.aspx and the downloads listed at http://support.microsoft.com/kb/2510766.  Q&A from the SP1 TechNet webcast can be found at http://blogs.msdn.com/b/brismith/archive/2011/07/11/project-server-2010-sp1-and-june-cu-questions-and-answers.aspx.

So without any further ado, here is the information:

August 2011 CU for Microsoft Project and Project Server 2010

Server Rollup Package(Recommended):

(ETA 9/9/2011)

Description of the SharePoint Server 2010 and Project Server 2010 Cumulative Update Server Hotfix Package (MOSS server-package, Project server-package): August 30, 2011

http://support.microsoft.com/kb/2553049

Individual Project Server Package:

Only required if you do not install the Server Rollup.

Description of the Project Server 2010 hotfix package (pjsrvwfe-x-none.msp): August 30, 2011

http://support.microsoft.com/kb/2553047

Project Client Package:

Description of the Project 2010 hotfix package (project-x-none.msp): August 30, 2011

http://support.microsoft.com/kb/2584056

More information on deploying the Cumulative Update:

The article below provides information on how to deploy the Project Server Cumulative Update.

Updates for Project Server 2010

http://technet.microsoft.com/en-us/projectserver/gg176680.aspx

As Project Server 2010 is now based on SharePoint Server 2010 we strongly recommend that you install the Project Server 2010 Server Rollup Package as there are a large number of individual server packages for SharePoint Server. The Project Server 2010 Server Rollup Package contains all the patches released in this Cumulative Update for SharePoint Foundation Server 2010, SharePoint Server 2010 and Project Server 2010.

For those accustomed to Project Server 2007 Cumulative Updates, you should note that the MOSS Server Rollup Package does not contain the Project Server patches. You will need to make sure that you install the MOSS + Project Server Rollup Package (the link is provided below). As in Project Server 2007, the Server Rollup Packages are much larger but they will greatly simplify your Project Server patch deployment.

Client Installation:

Installation of the client patch is straightforward and is the same as it was in Project 2007. The instructions for installing the client patch are below.

NOTE: Microsoft strongly recommends testing within a NON-Production environment prior to rollout.

  1. Download the hotfix from the link in the KB Article.
  2. Extract the patch package by running the .exe file that you downloaded.
  3. Run the extracted .exe file to apply the patch to your Project Professional/Standard client.

August 2011 CU for Microsoft Office Project and Project Server 2007

Server Rollup Packages:

Description of the Windows SharePoint Services 3.0 cumulative update package (WSS server-package): August 30, 2011

http://support.microsoft.com/kb/2553022

Description of the Office SharePoint Server 2007 cumulative update package (MOSS server-package): August 30, 2011

http://support.microsoft.com/kb/2553020

Individual Product Packages:

Description of the Office SharePoint Server 2007 hotfix package (sts-x-none.msp): August 30, 2011

http://support.microsoft.com/kb/2553019

Description of the Office Project Server 2007 hotfix package (pjsrvapp-x-none.msp, pjsrvwfe-x-none.msp): August 30, 2011

http://support.microsoft.com/kb/2553024

Description of the Office Project 2007 hotfix package (project-x-none.msp):August 30, 2011

http://support.microsoft.com/kb/2553105

More information on deploying the Cumulative Update:

The article below provides information on how to deploy the Project Server Cumulative Update.

Deploy cumulative updates (Project Server 2007)

http://technet.microsoft.com/en-us/library/dd239177.aspx

Service Pack 2 for both WSS and Office Servers 2007 are required for this Cumulative Update. The KB articles below provide information on how to download and install SP2 if you have not already done so.

Description of Windows SharePoint Services 3.0 SP2 and of Windows SharePoint Services 3.0 Language Pack SP2

http://support.microsoft.com/kb/953338

Description of 2007 Microsoft Office servers Service Pack 2 and of 2007 Microsoft Office servers Language Pack Service Pack 2

http://support.microsoft.com/kb/953334

The Server CU is released in two different versions. The first version is in Individual Packages specific to a particular product like WSS and Project Server. These are smaller downloads but they do not include language packs or patches for other products so patches for those products would have to be downloaded and installed separately.

The second version is the Server Rollup Packages. This is a set of two rollup packages which contains all the fixes for WSS, Project Server and MOSS. These packages should be used when MOSS is part of the deployment and/or you have language packs installed. The Server Rollup Packages are much larger but they will greatly simplify MOSS patch deployment.

Client Installation:

In order to install this hotfix, you will need to have Microsoft Project 2007 SP2 installed on the client.

Description of Office Project 2007 Service Pack 2 (SP2) and of Office Project Language Pack 2007 Service Pack 2 (SP2)

http://support.microsoft.com/kb/953326

Once we know that SP2 is installed, you will install the hotfix by performing the following steps:

NOTE: Microsoft strongly recommends testing within a NON-Production environment prior to rollout.

  1. Download the hotfix from either the KB Article or by using the information at the end of this email.
  2. Extract the patch package by running the .exe file that you downloaded.
  3. Run the extracted .exe file to apply the patch to your Project Professional/Standard SP1 client.

Feel free to open a support incident at http://support.microsoft.com if you run into any issues with the installation and we will be happy to help!

SharePoint Business Data List Connector – Simply connect a REAL list to external LOB data

September 13, 2011

The fast, easy and complete integration of external LOB data is a common requirement in the use of Microsoft SharePoint technology. Existing solutions, such as the Business Data Catalog (BDC) in SharePoint 2007 or the Business Connectivity Services (BCS)  in SharePoint 2010, are often too complex at the facility, require additional tools, bring with them limitations or they are available for certain SharePoint editions only.

The Business Data List Connector for SharePoint 2007 and 2010 offers a SharePoint “External List” by connecting a native SharePoint list (no Web Part) to almost any external business data in just minutes, using a very simple browser-based list settings dialogue. No additional tools are required. It can be configured easily with 3 simple settings only. Every SharePoint admin can do this. The desired data can be populated to the list and presented without any restrictions, with the full functionality of common SharePoint lists made available: views, sorting and grouping, filters, calculated fields, search, lookups can be created as usual. You can add additional internal content columns or attachments to the external data, e.g. documents, comments, ratings, tagging or other Web 2.0 content. You can take the data offline via Outlook and/or Workspace. All list types are supported, e.g. contacts, tasks, events with optional write-back (CRUD). List workflows (SPD-, VS- and Nintex-based) and notifications per RSS or email can be used to take business actions in SharePoint, if external business data records are changed. The BDLC additionally makes available any external data source to tag and use with the SharePoint 2010 Knowledge Management and Social Networking features without any restrictions.

You don’t have any limitations, that still exists with out-of-the-box BCS external lists in SharePoint 2010. While BDC-based solutions are often difficult to migrate from WSS3.0 / SharePoint 2007 to 2010, BDLC works in the same way with both SharePoint versions. It’s very simple to migrate, all connections and settings are kept working. There is a free upgrade available for BDLC from MOSS/WSS to SharePoint 2010 for all customers with Software Assurance (SA).

Existing ODBC, OLEDB, and .NET based drivers supported. You can connect to SQL Server, MySQL, Exchange, Active Directory, SharePoint, MS Office Excel, Access or text files, XML, EDI, Oracle, IBM DB2, Informix, AS400, Cache, ERP/CRM systems e.g. MS Dynamics CRM / NAV / AX, SAP, Salesforce.com, QuickBooks, Peachtree, HL7, Virtual Store, general Web Services, .NET or COM+ objects and many others.

The SharePoint Business Data List Connector is available for Microsoft Office SharePoint Server 2007 (MOSS, all editions) and also for the free Windows SharePoint Services 3.0 (WSS).  Software versions for Microsoft SharePoint Server 2010 and Windows SharePoint Servicves 4.0 / Microsoft SharePoint Foundation are also currently available.

http://www.layer2.de/en/products/Pages/SharePoint-Business-Data-List-Connector.aspx

When you try to browse Companyweb you will be prompted for authentication 3 times

September 9, 2011

You may experience authentication issues browsing http://companyweb on SBS 2003 and SBS 2008 servers after installing the cumulative security update for Internet Explorer (963027) or Internet Explorer 8.0.

When you try to browse Companyweb you will be prompted for authentication 3 times and eventually receive a blank page or 401.1. Your IIS logs will show your request failing with 401.1 Unauthorized.

Resolution

Please use one of the following resolutions depending on the version of SBS you are running.

SBS2003

On an SBS 2003 server this issue can be fixed by applying update

KB961143.

Note: You must have .NET Framework 2.0 installed before you apply this update.

SBS2008

The workaround provided in the following blog post for IE 8.0 also applied to IE 7.0 with 963027 installed.

http://blogs.technet.com/sbs/archive/2009/02/24/known-issues-after-installing-ie-8-on-small-business-server-2008-and-the-vista-clients-that-are-joined-to-the-sbs-domain.aspx.

Note:

This issue will be fixed in upcoming update rollup for SBS 2008. We will update this post when it is available.

On SBS 2008 you can also implement method #2 from

KB963027.

Microsoft Dynamics CRM 4.0 Performance and Scalability

September 8, 2011

 

“In terms of the bandwidth question, we do not currently have any bandwidth requirements published. The primary reason for this is that there are numerous factors that can all impact the amount of bandwidth consumed.

These include:

1. The amount of data being stored in CRM and being subsequently accessed in the client is one factor.
2. The amount of customizations in CRM. More fields and more entities mean more data that would need to be pulled down.
3. Which CRM client version will be installed. The Online and Offline clients have different needs.
4. The user’s settings inside of CRM. A good deal of bandwidth usage will depend on what parts of CRM the user chooses to integrate to Outlook and how often they set their sync intervals.”

Download details: Microsoft Dynamics CRM 4.0 Performance and Scalability:
http://www.microsoft.com/downloads/details.aspx?FamilyId=5852B14A-394C-4898-8374-CAF5E6479EB0&displaylang=en

Microsoft Dynamics CRM Team Blog : Performance Study – Dynamics CRM 4.0 WAN Performance using Cisco Wide Area Application Services:
https://blogs.msdn.com/crm/archive/2008/12/05/performance-study-dynamics-crm-4-0-wan-performance-using-cisco-wide-area-application-services.aspx

Project 2010 TechCenters on TechNet refreshed

September 7, 2011

It’s our pleasure to present you refreshed versions of our one-stop technical resources related to

Upgrade and Migration to Project 2010 – http://go.microsoft.com/?linkid=9676814

Business Intelligence for Project 2010 – http://go.microsoft.com/?linkid=9726143

These centers are part of the Project Server 2010 TechNet TechCenter http://technet.microsoft.com/projectserver/ee263909.aspx and their concept is to collect relevant information in one place and to give end-to-end information from getting started quickly to deep dive.

Q&A

Q: How about Demand Management and Portfolio Strategy?

A: We are working on Demand Management Center that will became one stop for information about Demand Management, Portfolio Strategy, including technicalities, like building custom Demand Management Infrastructure – including workflow. This center will live on the Project Server 2010 Center on TechNet – ttp://technet.microsoft.com/projectserver/ee263909.aspx and will be available in few weeks.

Q: I’m a developer, what’s in there for me?

A: Many of included links include pure developer resources. We have decided not to fragment the resources between TechNet and MSDN – that’s why you might find also developer-related link to MSDN content in the above TechCenters.

Other Publicly Available Project 2010 Resources

Product information and trial download

End-User Product Help

Interactive content – Videos/Sessions/Webcasts

IT Professional related – TechNet

Developer related – MSDN

Project & Project Server 2010 Demo Image

Got questions? Search or ask in the official Microsoft Forums

SharePoint 2010

SharePoint 2010 ribbon customization : how to hide Ribbon programatically

September 6, 2011

programatically hide a Ribbon

 
1
2
3
4
5
6
7
8
9
public void HideRibbon()
{
  SPRibbon current = SPRibbon.GetCurrent(this.Page);
  
  if (current != null && !this.Page.Request.IsAuthenticated)
  {
    current.CommandUIVisible = false;
  }
}

programatically hide a single ribbon button

 
1
2
3
4
5
6
public void HideRibbonItem()
{
 //if this is a System.Web.UI.Page
 SPRibbon ribbon = SPRibbon.GetCurrent(this);
 ribbon.TrimById("Ribbon.ListItem.New.NewFolder");
}

programatically hide the status bar

 
1
2
3
4
5
public void HideStatusBar()
{
   string script = "document.onreadystatechange=fnRemoveAllStatus; function fnRemoveAllStatus(){removeAllStatus(true)};";
   this.Page.ClientScript.RegisterClientScriptBlock(typeof(HideTheRibbon), "statusBarRemover", script, true);
}

programatically hide the SiteActions Menu

 
1
2
3
4
5
6
7
8
9
public void HideSiteActionsMenu()
{
  SiteActions actions = SiteActions.GetCurrent(this.Page);
  
  if (actions != null && !this.Page.Request.IsAuthenticated)
  {
       actions.Visible = false;
  }
}

Ref: http://www.elumenotion.com/Blog/Lists/Posts/Post.aspx?ID=106

Hide the SharePoint 2010 Ribbon

September 5, 2011

If you’re creating a Web site and using SharePoint 2010 as a Content Management System platform, perhaps your first challenege as a designer is what to do with that ribbon that is smack-dab in the way of your nice custom layout? At first it seems to be a challenge: For unauthenticated users the ribbon makes no sense and is irrelevant. Your first thought may be to get rid of it entirely. But then, we still need the functionality for users who are authenticated (in order to edit their content) – so we can’t get rid of it. What do we do?

There is a solution that fits the needs of designers, developers, their clients and their end-users: Enter the SP2010 Ribbon Toggler! Toggle it with a keystroke, querystring, or a button. Let’s implement it:

1. Open an editor of your choice to create a new .js file and paste the following code into it:

function ShowRibbon() {
   $(‘#s4-ribbonrow’).show();
   $(‘#s4-workspace’).height($(document).height() – $(‘#s4-ribbonrow’).height() * 2);
}function HideRibbon() {
   $(‘#s4-ribbonrow’).hide();
   var newHeight = $(document).height();
   if ($.browser.msie) { newHeight = newHeight – 3; }
   $(‘#s4-workspace’).height(newHeight);
}

2. Save your .js file as SP2010_RibbonToggler.js.
3. Open up SharePoint Designer and browse to your root site.
4. In the left tool pane called “Site Objects” click on “Site Assets.”
5. In the top tool bar, select “Import Files” and import the .js file you created. (If you’d like to create a separate “scripts” folder within Site Assets, or organize it in any way you’d like, now’s the time.)
6. In the left tool pane again select “Master Pages.”
7. Open the Master Page that you’re using for your Site. In most cases you’re probably using v4.master.
8. In the HTML markup, find the section and place the following JavaScript references within the head section:

<script type=”text/javascript” src=”http://ajax.googleapis.com/ajax/libs/jquery/1.4.2/jquery.min.js”></script&gt;
<script type=”text/javascript” src=”/SiteAssets/SP2010_RibbonToggler.js”></script>

Note: We’re first here referencing the jQuery framework. Our code uses this framework to easily and quickly access the Document Object across differing browers. We then reference our SP2010_RibbonToggler.js file. Remember to change the reference path if you put your SP2010_RibbonToggler.js file in a different location than instructed to at the beginning of this tutorial.

We now have two functions in our SharePoint site for turning on and off the ribbon! Now we just need to implement some Javascript code to use these functions. The sky’s the limit for how you want to accomplish this. At Concurrency, we like to use a keystroke combination (ctrl+shift+r) to pop up the ribbon. Here’s how to do that:

In your SP2010_RibbonToggler.js file, at the following code to it:

$(document).keydown(function (e) {
   if (e.keyCode == 17) { ks = “a”; return false; }
   if (e.keyCode == 16) { if (ks == “a”) { ks = ks + “b”; return false; } }
   if (e.keyCode == 82) {
      if (ks == “ab”) {
         ks = “”;
         if($(‘#s4-ribbonrow’).css(‘display’)==”none”) {
            //show
            ShowRibbon();
         } else {
            //hide
            HideRibbon();
         }
         return false;
      }
   }
   return true;
});

Another way to turn on and off the ribbon now is by passing a query string to the page. If we append ?ribn=1 to our site address at any time, the ribbon will show. This is how to do that:

In your SP2010_RibbonToggler.js file, at the following code to it:

$(document).ready(function(){
   if(getParameterByName(‘ribn’)==”1″) {
      ShowRibbon();
   } else {
      HideRibbon();
   }
});function getParameterByName(name) {
   name = name.replace(/[\[]/, “\\\[“).replace(/[\]]/, “\\\]”);
   var regexS = “[\\?&]” + name + “=([^&#]*)”;
   var regex = new RegExp(regexS);
   var results = regex.exec(window.location.href);
   if (results == null)
      return “”;
   else
      return decodeURIComponent(results[1].replace(/\+/g, ” “));
}

Or perhaps you only want to show the ribbon if the user has authenticated to SharePoint? Here’s how to do that:

In your SP2010_RibbonToggler.js file, at the following code to it:

$(document).ready(function(){
   if (typeof _spUserId == “undefined”) {
      HideRibbon();
   }else {
      ShowRibbon();
   }
});

In fact, you can add all of these examples to your SP2010_RibbonToggler.js file and they will all work together for you. Wouldn’t if be nice if you could download a fully functional .js file with all this working? It would …