Skip Ribbon Commands
Skip to main content
Home
February 17
New Windows 8 Logo 'Smash or Trash'

Windows 8

With Windows 8, we approached the logo redesign with a few key goals on mind.
1. We wanted the new logo to be both modern and classic by echoing the International Typographic Style (or Swiss design) that has been a great influence on our Metro style design philosophy. Using bold flat colors and clean lines and shapes, the new logo has the characteristics of way-finding design systems seen in airports and subways.
2. It was important that the new logo carries our Metro principle of being “Authentically Digital”. By that, we mean it does not try to emulate faux-industrial design characteristics such as materiality (glass, wood, plastic, etc.). It has motion – aligning with the fast and fluid style you’ll find throughout Windows 8.
3. Our final goal was for the new logo to be humble, yet confident. Welcoming you in with a slight tilt in perspective and when you change your color, the logo changes to reflect you. It is a “Personal” Computer after all.
Win8Logo_01_thumb
We hope you enjoy our new logo.
Sam Moreau
Principal Director of User Experience for Windows

February 12
Top 50 Interview Questions

What is Microsoft Windows SharePoint Services? How is it related to Microsoft Office SharePoint Server 2007?
Windows SharePoint Services is the solution that enables you to create Web sites for information sharing and document collaboration. Windows SharePoint Services -- a key piece of the information worker infrastructure delivered in Microsoft Windows Server 2003, Internet Explorer, and MS Office system and it serves as a platform for application development.
Office SharePoint Server 2007 builds on top of Windows SharePoint Services 3.0 to provide additional capabilities including collaboration, portal, search, enterprise content management, business process and forms, and business intelligence.
What is Microsoft SharePoint Portal Server?
SharePoint Portal Server is a portal server that connects people, teams, and knowledge across business processes. SharePoint Portal Server integrates information from various systems into one secure solution through single sign-on and enterprise application integration capabilities. It provides flexible deployment and management tools, and facilitates end-to-end collaboration through data aggregation, organization, and searching. SharePoint Portal Server also enables users to quickly find relevant information through customization and personalization of portal content and layout as well as through audience targeting.
What is Microsoft Windows Services?
Microsoft Windows Services is the engine that allows administrators to create Web sites for information sharing and document collaboration. Windows SharePoint Services provides additional functionality to the Microsoft Office System and other desktop applications, as well as serving as a platform for application development. SharePoint sites provide communities for team collaboration, enabling users to work together on documents, tasks, and projects. I call it “The environment for easy and flexible deployment, administration, and application development”.
What is the relationship between Microsoft SharePoint Portal Server and Microsoft Windows Services?
Microsoft SharePoint Products and Technologies (including SharePoint Portal Server and Windows SharePoint Services) deliver highly scalable collaboration solutions with flexible deployment and management tools. Windows SharePoint Services provides sites for team collaboration, while Share Point Portal Server connects these sites, people, and business processes—facilitating knowledge sharing and smart organizations. SharePoint Portal Server also extends the capabilities of Windows SharePoint Services by providing organizational and management tools for SharePoint sites, and by enabling teams to publish information to the entire organization.
Who is Office SharePoint Server 2007 designed for?
SharePoint is fundamentally designed for information workers, but it is designed in such a way that it assists a wide spectrum of users and support staff. Key stakeholders are:
·         business users,
·         business administrators,
·         IT administrators,
·         IT developers.
The true beauty of SharePoint is the way that conduct of tasks can be devolved to the lowest possible level:
·         many tasks can be achieved by business users without IT support;
·         if a business user cannot perform a function, then in many cases a business administrator can assist;
·         in the unlikely even that a business administrator cannot perform the task, then there is a large world-wide community that has developed thousands of 'add-ins' and web-parts that can be easily installed by an IT administrator; in the even more unlikely event that a ready-made 'add-in' is not available, then SharePoint provides a highly structured environment for developers.
SharePoint also provides a framework which is designed to simplify IT development and ongoing administration, in the first instance developers should endeavor to:
·         develop as a web-part in order to preserve all other site functionality without losing the ability for business users to maintain the site;
·         if the desired functionality cannot be developed as a web-part, then SharePoint provides a range of other (reversible) development options;
·         the option for business users to reset components to the 'site definition' is invaluable and great caution should be exercised when making changes that alter components at this level;
·         generally, (perhaps only as a last resort) is it rarely necessary to customize SharePoint in such a way that the full set of default functionality is altered.
 What are the main benefits of Office SharePoint Server 2007?
Office SharePoint Server 2007 provides a single integrated platform to manage intranet, extranet, and Internet applications across the enterprise.
Business users gain greater control over the storage, security, distribution, and management of their electronic content, with tools that are easy to use and tightly integrated into familiar, everyday applications. Organizations can accelerate shared business processes with customers and partners across organizational boundaries using InfoPath Forms Services–driven solutions.
• Information workers can find information and people efficiently and easily through the facilitated information-sharing functionality and simplified content publishing. In addition, access to back-end data is achieved easily through a browser, and views into this data can be personalized. Administrators have powerful tools at their fingertips that ease deployment, management, and system administration, so they can spend more time on strategic tasks.
• Developers have a rich platform to build a new class of applications, called Office Business Applications, that combine powerful developer functionality with the flexibility and ease of deployment of Office SharePoint Server 2007. Through the use of out-of-the-box application services, developers can build richer applications with less code.
How does SharePoint empower business users?
SharePoint is a set of powerful technologies that provide a large range of functions to users and administrators without the need to engage IT or developers. Once the basic SharePoint service is deployed, users can self-serve with a minimum of IT support.
By default, all users can personalize their user experience; this includes such things as adding, removing or updating web-parts on any web-part page. These user changes can then be saved as a personal view. This is particularly useful because it allows users to create pages which contain the information that is relevant to them and it allows users to hide information (eg information that does not relate to their department or role). By default, all users can also create custom personal views in SharePoint. This is particularly helpful for large lists of information and gives users the ability to filter large lists of information to only show the information that is relevant to them, perhaps their department or division.
SharePoint also empowers users at the administration level. It is normal for users to be given the ability to alter "site settings", this is done by nominating one or more users to have "Full Control" of the user experience for any site. A user with "Full Control" can add additional web-parts, customize web-parts by adding metadata, and change the default view for all users. In effect, a user with "Full Control" over a site can create a rich user experience for the group of users that are using the particular site without any IT support or development skills.
It is also common for selected expert users to be appointed as "Site Collection Administrators" in order to facilitate the management of multiple sites which are called a site collection. The "Site Collection Administration" function also allows selected users to view all deleted items across an entire site, as well as turn on or off global features.
All of the functions listed above can normally be managed by business users and do not require IT support. No coding is required. All of these functions are managed by SharePoint through the SharePoint user interface. Thus, because there is no coding, there is no requirement for change control, testing or development protocols. A change log is still suggested.
For this reason, SharePoint is ideal for work-teams or project-teams that need to collaborate on a defined task. SharePoint gives the business user/ or team the ability to create a "site" that is highly customised for their particular needs without any need for IT support or development tools.
Indeed, all of the functionality listed above can generally be supported without the need for significant levels of governance. Some central governance is normally suggested, in order to do such things as maintain some control over different site collections, to maintain user groups, to share common infrastructure and to ensure that sites are managed through their lifecycle.
However,.. if (and many would say only if) the standard set of functions is insufficient, and additional functionality is required, then SharePoint provides a very strong set of tools and an excellent framework for developers. The beauty of SharePoint is that it is only at this point that IT support is really required.
And even then, many companies will find that the only IT support they require is to install "add-ons" from the SharePoint user community to their SharePoint server. Deployment of additional web-parts or "add-ons" generally requires specialist server administrator skills to deploy.
Business users can achieve a lot in SharePoint without writing a line of code or using development tools like Microsoft SharePoint Designer or similar development tools.
What is the difference between Microsoft Office SharePoint Server 2007 for Internet sites and Microsoft Office SharePoint Server 2007?
Microsoft Office SharePoint Server 2007 for Internet sites and Microsoft Office SharePoint Server 2007 have identical feature functionality. While the feature functionality is similar, the usage rights are different.
If you are creating an Internet, or Extranet, facing website, it is recommended that you use Microsoft Office SharePoint Server 2007 for Internet sites which does not require the purchase client access licenses. Websites hosted using an “Internet sites” edition can only be used for Internet facing websites and all content, information, and applications must be accessible to non-employees. Websites hosted using an “Internet sites” edition cannot be accessed by employees creating, sharing, or collaborating on content which is solely for internal use only, such as an Intranet Portal scenario. See the previous section on licensing for more information on the usage scenarios.
What suites of the 2007 Microsoft Office system work with Office SharePoint Server 2007?
Office Outlook 2007 provides bidirectional offline synchronization with SharePoint document libraries, discussion groups, contacts, calendars, and tasks.
Microsoft Office Groove 2007, included as part of Microsoft Office Enterprise 2007, will enable bidirectional offline synchronization with SharePoint document libraries.
Features such as the document panel and the ability to publish to Excel Services will only be enabled when using Microsoft Office Professional Plus 2007or Office Enterprise 2007.
Excel Services will only work with documents saved in the new Office Excel 2007 file format (XLSX).
How do I invite users to join a Windows SharePoint Services Site? Is the site secure?
SharePoint-based Web sites can be password-protected to restrict access to registered users, who are invited to join via e-mail. In addition, the site administrator can restrict certain members' roles by assigning different permission levels to view post and edit.
Can I post any kind of document?
You can post documents in many formats, including .pdf, .htm and .doc. In addition, if you are using Microsoft Office XP, you can save documents directly to your Windows SharePoint Services site.
Can I download information directly from a SharePoint site to a personal digital assistant (PDA)?
No you cannot. However, you can exchange contact information lists with Microsoft Outlook. But all pages are mobile enabled!
How long does it take to set up the initial team Web site?
It only takes a few minutes to create a complete Web site. Preformatted forms let you and your team members contribute to the site by filling out lists. Standard forms include announcements, events, contacts, tasks, surveys, discussions and links.
 Can I create custom templates?
Yes you can. You can have templates for business plans, doctor's office, lawyer's office etc.
How can I make my site public? By default, all sites are created private.
If you want your site to be a public Web site, enable anonymous access for the entire site. Then you can give out your URL to anybody in your business card, e-mail or any other marketing material. The URL for your Web site will be: http:// asapsharepoint.com
Hence, please take special care to name your site. These Web sites are ideal for information and knowledge intensive sites and/or sites where you need to have shared Web workspace. Remember: Under each parent Web site, you can create up to 10 sub-sites each with unique permissions, settings and security rights.
How do the sub sites work?
You can create a sub site for various categories. For example:
·         Departments - finance, marketing, IT
·         Products - electrical, mechanical, hydraulics
·         Projects - Trey Research, Department of Transportation, FDA
·         Team - Retention team, BPR team
·         Clients - new clients, old clients
·         Suppliers - Supplier 1, Supplier 2, Supplier 3
·         Customers - Customer A, Customer B, Customer C
·         Real estate - property A, property B
The URLs for each will be, for example:
·         http://asapsharepoint.com/finance
·         • http://asapsharepoint.com
You can keep track of permissions for each team separately so that access is restricted while maintaining global access to the parent site.
 How do I make my site non-restricted?
If you want your site to have anonymous access enabled (i.e., you want to treat it like any site on the Internet that does not ask you to provide a user name and password to see the content of the site), follow these simple steps:
Login as an administrator
1.       Click on site settings
2.       Click on Go to Site Administration
3.       Click on Manage anonymous access
4.       Choose one of the three conditions on what Anonymous users can access:
Entire Web site - Lists and libraries or Nothing.
Default condition is nothing; your site has restricted access. The default conditions allow you to create a secure site for your Web site.
What are picture libraries?
Picture libraries allow you to access a photo album and view it as a slide show or thumbnails or a film strip. You can have separate folder for each event, category, etc
What are the advantages of a hosted SharePoint vs. one that is on an in-house server?
·         No hardware investment, i.e. lower costs
·         No software to download - ready to start from the word go
·         No IT resources - Anyone who has used a Web program like Hotmail can use it
·         Faster deployment
Can I ask users outside of my organization to participate in my Windows SharePoint Services site?
Yes. You can manage this process using the Administration Site Settings. Simply add users via their e-mail alias and assign permissions such as Reader or Contributor.
 
Are there any IT requirements or downloads required to set up my SharePoint site in the cloud?
No. You do not need to download any code or plan for any IT support. Simply complete the on-line signup process and provide us your current and correct email address. Once you have successfully signed up and your site has been provisioned, we will send a confirmation to the email address you provided.
I am located outside of the United States. Are there any restrictions or requirements for accessing the Windows SharePoint Services?
No. There are no system or bandwidth limitations for international trial users. Additionally language packs have been installed which allow users to set up sub-webs in languages other than English. These include: Arabic, Danish, Dutch, Finnish, French, German, Hebrew, Italian, Japanese, Polish, Portuguese (Brazilian), Spanish and Swedish.
Are there any browser recommendations?
Yes. Microsoft recommends using the following browsers for viewing and editing Windows SharePoint Services sites: Microsoft Internet Explorer 5.01 with Service Pack 2, Microsoft Internet Explorer 5.5 with Service Pack 2, Internet Explorer 6, Netscape Navigator 6.2 or later.
What security levels are assigned to users?
Security levels are assigned by the administrator who is adding the user. There are four levels by default and additional levels can be composed as necessary.
·         Visitor/Reader - Has read-only access to the Web site.
·         Contributor - Can add content to existing document libraries and lists.
·         Web Designer - Can create lists and document libraries and customize pages in the Web site.
·         Administrator - Has full control of the Web site.
 How secure are Windows SharePoint Services sites hosted by Microsoft?
Microsoft Windows SharePoint Services Technical security measures provide firewall protection, intrusion detection, and web-publishing rules. The Microsoft operation center team tests and deploys software updates in order to maintain the highest level of security and software reliability. Software hot-fixes and service packs are tested and deployed based on their priority and level of risk. Security related hot-fixes are rapidly deployed into the environment to address current threats. A comprehensive software validation activity ensures software stability through regression testing prior to deployment.
What is the difference between an Internet and an intranet site?
An internet site is a normal site that anyone on the internet can access (e.g., www.msn.com, www.microsoft.com, etc.). You can set up a site for your company that can be accessed by anyone without any user name and password. The internet is used for public presence and a primary marketing tool managed typically by web programmers and a system administrator.
An intranet (or internal network), though hosted on a Web site, can only be accessed by people who are members of a specific network. They need to have a login and password that was assigned to them when they were added to the site by the site administrator. The intranet is commonly used as an internal tool for giving employees access to company information. Content is driven by business relevance, business rules and has increasingly become a common tool in larger organizations. An intranet is becoming more and more the preferred method for employees to interact with each other and the central departments in an organization, whether or not the organization has a Web presence.
What is a workspace?
A site or workspace is when you want a new place for collaborating on Web pages, lists and document libraries. For example, you might create a site to manage a new team or project, collaborate on a document or prepare for a meeting.
What are the various kinds of roles the users can have?
A user can be assigned one of the following roles:
·         Reader - Has read-only access to the Web site.
·         Contributor - Can add content to existing document libraries and lists.
·         Web Designer - Can create lists and document libraries and customize pages in the Web site.
·         Administrator - Has full control of the Web site.
Can more than one person use the same login?
If the users sharing that login will have the same permissions and there is no fear of them sharing a password, then yes. Otherwise, this is discouraged.
How customizable is the user-to-user access?
User permissions apply to an entire Web, not to documents themselves. However, you can have additional sub webs that can optionally have their own permissions. Each user can be given any of four default roles. Additional roles can be defined by the administrator.
Can each user have access to their own calendar?
Yes there are two ways to do this, by creating a calendar for each user, or by creating a calendar with a view for each user
How many files can I upload?
There is no restriction in place except that any storage consumed beyond that provided by the base offering may have an additional monthly charge associated with them.
What types of files can I upload / post to the site?
The only files restricted are those ending with the following extensions: .asa, .asp, .ida, .idc, .idq. Microsoft reserves the right to add additional file types to this listing at any time. Also, no content that violates the terms of service may be uploaded or posted to the site.
Can SharePoint be linked to an external data source?
SharePoint data can be opened with Access and Excel as an external data source. Thus, SharePoint can be referenced as an external data source. SharePoint itself cannot reference an external data source.
But 3rd pary software can do this for you: http://www.layer2.de/en/products/pages/sharepoint-business-data-list-connector.aspx
Can SharePoint be linked to a SQL database?
SharePoint 2007 Portal Server (MOSS2K7) allows connections to SQL based datasources via the Business Data Catalog (BDC). The BDC also allows connecting to data via Web Services. Or you can link lists directly with sql queries in the list settings using the BDLC found here: http://bit.ly/p30tJ .
Can I customize my Windows SharePoint Services site?
YES! Windows SharePoint Services makes updating sites and their content from the browser easier than ever.
SharePoint includes tools that let you create custom lists, calendars, page views, etc. You can apply a theme; add List, Survey and Document Library Web Parts to a page; create personal views; change logos; connect Web Parts and more.
To fully customize your site, you can use Microsoft FrontPage 2003. Specifically, you can use FrontPage themes and shared borders, and also use FrontPage to create photo galleries and top ten lists, utilize standard usage reports, and integrate automatic Web content.
Will Microsoft Office SharePoint Server 2007 run on a 64-bit version of Microsoft Windows?
Windows SharePoint Services 3.0, Office SharePoint Server 2007, Office Forms Server 2007, and Office SharePoint Server 2007 for Search will support 64-bit versions of Windows Server 2003.
How Office SharePoint Server 2007 can help you?
Office SharePoint Server 2007 can help us:
Manage content and streamline processes. Comprehensively manage and control unstructured content like Microsoft Office documents, Web pages, Portable Document Format file (PDF) files, and e-mail messages. Streamline business processes that are a drain on organizational productivity.
Improve business insight. Monitor your business, enable better-informed decisions, and respond proactively to business events.
Find and share information more simply. Find information and expertise wherever they are located. Share knowledge and simplify working with others within and across organizational boundaries.
Empower IT to make a strategic impact. Increase responsiveness of IT to business needs and reduce the number of platforms that have to be maintained by supporting all the intranet, extranet, and Web applications across the enterprise with one integrated platform.
Office SharePoint Server 2007 capabilities can help improve organizational effectiveness by connecting people, processes, and information.
Office SharePoint Server 2007 provides these capabilities in an integrated server offering, so your organization doesn't have to integrate fragmented technology solutions itself.
What are the features that the portal components of Office SharePoint Server 2007 include?
The portal components of Office SharePoint Server 2007 include features that are especially useful for designing, deploying, and managing enterprise intranet portals, corporate Internet Web sites, and divisional portal sites. The portal components make it easier to connect to people within the organization who have the right skills, knowledge, and project experience.
What are the advanced features of MOSS 2007?
·         User Interface (UI) and navigation enhancements
·         Document management enhancements
·         The new Workflow engine
·         Office 2007 Integration
·         New Web Parts
·         New Site-type templates
·         Enhancements to List technology
·         Web Content Management
·         Business Data Catalog
·         Search enhancements
·         Report Center
·         Records Management
·         Business Intelligence and Excel Server
·         Forms Server and InfoPath
·         The “Features” feature
·         Alternate authentication providers and Forms-based authentication
What are the features of the new Content management in Office SharePoint 2007?
The new and enhanced content management features in Office SharePoint Server 2007 fall within three areas:
1.       Document management
2.       Records management
3.       Web content management
Office SharePoint Server 2007 builds on the core document management functionality provided by Windows SharePoint Services 3.0, including check in and check out, versioning, metadata, and role-based granular access controls. Organizations can use this functionality to deliver enhanced authoring, business document processing, Web content management and publishing, records management, policy management, and support for multilingual publishing.
Does a SharePoint Web site include search functionality?
Yes. SharePoint Team Services provides a powerful text-based search feature that helps you find documents and information fast.
 Write the features of the search component of Office SharePoint Server 2007?
The search component of Office SharePoint Server 2007 has been significantly enhanced by this release of SharePoint Products and Technologies. New features provide:
·         A consistent and familiar search experience.
·         Increased relevance of search results.
·         New functions to search for people and expertise.
·         Ability to index and search data in line-of-business applications and
·         Improved manageability and extensibility.
·
What are the benefits of Microsoft Office SharePoint Server 2007?
·         Provide a simple, familiar, and consistent user experience.
·         Boost employee productivity by simplifying everyday business activities.
·         Help meet regulatory requirements through comprehensive control over content.
·         Effectively manage and repurpose content to gain increased business value.
·         Simplify organization-wide access to both structured and unstructured information across disparate systems.
·         Connect people with information and expertise.
·         Accelerate shared business processes across organizational boundaries.
·         Share business data without divulging sensitive information.
·         Enable people to make better-informed decisions by presenting business-critical information in one central location.
·         Provide a single, integrated platform to manage intranet, extranet, and Internet applications across the enterprise.
  Will SharePoint Portal Server and Team Services ever merge?
The products will come together because they are both developed by the Office team.
What does partial trust mean the Web Part developer?
If an assembly is installed into the BIN directory, the code must be ensured that provides error handling in the event that required permissions are not available. Otherwise, unhandled security exceptions may cause the Web Part to fail and may affect page rendering on the page where the Web Part appears.
How can I raise the trust level for assemblies installed in the BIN directory?
Windows SharePoint Services can use any of the following three options from ASP.NET and the CLR to provide assemblies installed in the BIN directory with sufficient permissions. The following table outlines the implications and requirements for each option.
Option Pros Cons
Increase the trust level for the entire virtual server. For more information, see "Setting the trust level for a virtual server" Easy to implement.
In a development environment, increasing the trust level allows you to test an assembly with increased permissions while allowing you to recompile assemblies directly into the BIN directory without resetting IIS. This option is least secure.
This option affects all assemblies used by the virtual server. There is no guarantee the destination server has the required trust level. Therefore, Web Parts may not work once installed on the destination server.
Create a custom policy file for your assemblies. For more information, see:
"How do I create a custom policy file?" Recommended approach. This option is most secure.
An assembly can operate with a unique policy that meets the minimum permission requirements for the assembly.
By creating a custom security policy, you can ensure the destination server can run your Web Parts.
Requires the most configuration of all three options. Install your assemblies in the GAC
Easy to implement. This grants Full trust to your assembly without affecting the trust level of assemblies installed in the BIN directory. This option is less secure.
Assemblies installed in the GAC are available to all virtual servers and applications on a server running Windows SharePoint Services. This could represent a potential security risk as it potentially grants a higher level of permission to your assembly across a larger scope than necessary
In a development environment, you must reset IIS every time you recompile assemblies.
Licensing issues may arise due to the global availability of your assembly.
 
Does SharePoint work with NFS?
Yes and no. It can crawl documents on an NFS volume, but the SharePoint database or logs cannot be stored there.
How is SharePoint Portal Server different from the Site Server?
Site Server has search capabilities but these are more advanced using SharePoint. SPS uses digital dashboard technology which provides a nice interface for creating web parts and showing them on dashboards (pages). SS doesn't have anything as advanced as that. The biggest difference would be SPS document management features which also integrate with web folders and MS Office.
What would you like to see in the next version of SharePoint?
A few suggestions: SPS and STS on same machine 1. Tree view of Categories and Folders 2. General Discussion Web Part 3. Personalization of Dashboards 4. Role Customization 5. Email to say WHY a document has been rejected for Approval 6. More ways to customize the interface 7. Backup and restore an individual Workspaces 8. Filter for Visio 9. Better way to track activity on SPS 10. Ability to Save as from Adobe to space on My Network Places 11.
Why SharePoint is not a viable solution for enterprise wide deployments?
Planning an enterprise deployment using SharePoint features is a very difficult task unless you can establish a Service Oriented Architecture, using AD for managing security with well defined roles based information access(EISA). Sounds reasonable, although it seems difficult to deploy with the tools limitations in document storage.
Document management does not scale beyond a single server, but scales great within a single server. For example, a quad Xeon machine with 4GB of RAM works great for a document management server that has about 900,000 - 1,000,000 document, but if you need to store 50,000,000 document and want to have them all in one single workspace then it does not scale at all. If you need a scenario like this, you need to plan your deployment right and it should scale for you, it just does not right out of the box. If you are using your server as a portal and search server most for the most part it scales great. You can have many different servers crawl content sources and have separate servers searching and serving the content.
If you have < 750,000 documents per server and fewer than 4 content sources and fewer than 50,000 users, SPS should scale just fine for your needs with the proper planning.
What are the actual advantages of SharePoint Portal Services (SPS) over SharePoint Team Services (STS)?
SharePoint Portal Services (SPS) has MUCH better document management. It has check-in, check-out, versioning, approval, publishing, subscriptions, categories, etc. STS does not have these features, or they are very scaled back. SharePoint Portal Services (SPS) has a better search engine, and can crawl multiple content sources. STS cannot. STS is easier to manage and much better for a team environment where there is not much Document Management going on. SPS is better for an organization, or where Document Management is crucial.
How Does SharePoint work?
The browser sends a DAV packet to IIS asking to perform a document check in. PKMDASL.DLL, an ISAPI DLL, parses the packet and sees that it has the proprietary INVOKE command. Because of the existence of this command, the packet is passed off to msdmserv.exe, who in turn processes the packet and uses EXOLEDB to access the WSS, perform the operation and send the results back to the user in the form of XML.
How do I open an older version of a document?
Normally, all previous versions are located in the shadow, so if you right click a published document from within the web folders, go to properties and then the third tab, versions you can view older versions.
If you want to do this in code:
strURL = "url of the last published version"  Set oVersion = New PKMCDO.KnowledgeVersion  Set prmRs = oVersion.VersionHistory(strURL)  Set oVersion = Nothing 
prmRS will contain a recordset, which contains the url to the old versions in the shadow.
 Why do the workspace virtual directories show the error “stop sign” symbol in the IIS snap-in?
If World Wide Web Publishing Service (W3SVC) starts before Microsoft Exchange Information Store (MSExchangeIS), “stop sign” symbols appear under the Default Web Site folder of the Internet Information Services console in Microsoft Management Console (MMC).
There is a dependency between the local paths of the SharePoint Portal Server virtual directories and the MSExchangeIS. You must start MSExchangeIS first, followed by W3SVC.
Complete the following steps to prevent the stop signs from appearing each time you restart:
Change the Startup type for W3SVC to Manual. 1. Restart the server. The MSExchangeIS service starts automatically. 2. Start W3SVC. 3.
What newsgroups are available?
There are two,
·         microsoft.public.sharepoint.portalserver
·         microsoft.public.sharepoint.portalserver.development.  
What is SharePoint from a Technical Perspective?
Technically SharePoint illustrates neatly what Microsoft's .net strategy is all about: integrating Windows with the Web. Microsoft has previously made accessing stuff on a PC easier, (Windows) then on a network (NT) and now on the web (.NET). SharePoint is an application written to let a user access a web accessible directory tree called the Web Storage System.
SharePoint was written with a set of technologies that allow the programmer to pass data, functions, parameters over HTTP, the web's medium. These are XML, XSL and SOAP, to name a few I understand the basics of!
To the user it looks easy, like Hotmail, but every time they click a button or a link, a lot has to happen behind the scenes to do what they want to do quickly and powerfully. Not as easy as you might think, but SharePoint does it for you. Accessing this Web storage system and the server itself is also done using technologies like ADO, CDO, PKMCDO, LDAP, DDSC, ADSC. More on these later. SharePoint is a great example of how the Internet Platform can be extended and integrated into an existing well adopted technology, Windows.
What is SharePoint from an Administration Perspective?
Administering SharePoint mainly consists of setting it up, which is much easier than you expect, adding the content, which can be just dragging and dropping in whole directory structures and files, and then organizing the files better by giving them categories or other metadata. This is done either through the Web interface or through the SharePoint Client: a program what means you can access SharePoint as a Web folder and then right-click files to select options like "edit profile". Or add files by dragging them in individually or in bulk.
Setting the security is also important, using NT accounts, either NT4 or Active Directory (or both in mixed mode) you can give users access to files/folders the same way as you do in standard Windows. Users can be grouped and the groups given access privileges to help manage this better. Also SharePoint has 3 Roles that a User or Group can be given on a particular item. Readers can see the item (i.e. document/file or folder) but not change it, Authors can see and edit items and coordinators can set security privileges for the part of the system they have control over. Thus, you could set 12 different coordinators for 12 different folder trees, and they could manage who can do what within that area only.
What is SharePoint from a Users Perspective?
From a Users perspective SharePoint is a way of making documents and folders on the Windows platform accessible over the web. The user visits the SharePoint Portal web page, and from there they can add documents, change documents & delete documents. Through this Portal, these documents are now available for discussion, collaboration, versioning and being managed through a workflow. Hence the name "Share-Point". Details about the document can be saved too, such as: who wrote it, when, for whom, its size, and version, category or target audience. These can then be used to find the document through SharePoint's Search facility. Even documents not "in" SharePoint can be included in the search engine's index so they become part of the portal. All in all, it's a great way to get stuff up on the web for users with average technical skills, and for administrators to manage the content.
What are the various SharePoint 2003 and Exchange integration points?
Link to Outlook - This is a button on contacts or events lists that lets Outlook 2003 add a pst file named SharePoint Folders and it links to the data on the site. It’s read-only, but you could make the home page for that PST be the SharePoint site for easier viewing. The link to outlook feature seems more to be where some can public a calendar, but not want too much collaboration. For example, a holiday schedule, company meeting schedule, etc, can be made available for people to be able to view from Outlook without having to go to a web browser. Another nice thing about OL2K3 is that you can compare these calendars with others side by side.
Searching Public Folders
With SPS you can index Exchange’s public folders with the search engine so that all that precious public folder content is searchable. You’ll want to look at content sources and indexing in Sharepoint administration.
Displaying Public Folders in a web part
Since exchange web-enables public folders, you can create a web part that displays that content. IE, http://exchangeserver/Public/IT/Helpdesk will display the IT/Helpdesk public folder via OWA. So you add the Page Viewer web part to a page and point it at that URL. The key here is to add ?cmd=contents to the end of the url if you don’t want the navigator pane on the left.
Smart web parts
Some of the web parts that come with SPS allow you to add a web part to a page that actually takes the users outlook info (calendar, inbox, contacts, tasks) and put them into the page.
The SmartPart Web Part project template for Visual Studio allows developers to create quickly a project which contains the base infrastructure to:
* write a web user control (ASCX)    * wrap the user control in a SmartPart instance    * generate a SharePoint Solution file (WSP) for easy deployment    * generate a setup package for a wizard driven installation
Can SharePoint compare two document versions?
"In Word 2003, you can compare documents side by side. Open two documents. Then, from the Window menu of one of them, select the Compare Side By Side command. If you have only two documents open, the command will automatically choose to compare them. If you have three or more documents open, you'll have to select which document to compare with the current file.
A floating toolbar with two buttons will open. If the button on the left is selected, Word will scroll both documents at the same time. Press the button on the right side of the toolbar to return to where the cursor was located when you started comparing."
What are the integration differences between SPS 2003 and the various Office versions?
SPS webpage can detect you have installed the Office 2003 and run local dll to implement some SPS function, e.g. multi-file upload only works when you have office 2003 installed.
Integration with Office XP is gone.
You will get guys telling you that you can integrate with SPSv2 if you install a backwards compatible document library - but that’s really just putting a bit of SPS 2001 on the server.
Believe me, check-in, check-out, which are themselves very basic, are not available from inside Office XP, or even from the context menu in Windows Explorer.
The ONLY option you have is to use the web interface to check-in or check-out.
Source: http://it.toolbox.com/wiki/index.php/Sharepoint_Interview_questions#
 

January 25
How ASAP SharePoint Specialist increase End User Adoption

We’ve all been there. After many months, and hour upon hour of planning and coordination, your new -- vastly improved – SharePoint-based website launches. The site embodies SharePoint best practices for file storage and content dissemination, and its new user interface and information architecture leave no debate about the proper places to store content.

Fast forward six months.

The site sits quietly. Occasionally a new employee uploads a document or adds an event to a calendar, maybe even starts an event workspace, but other than that the site sits virtually unused while the V:// shared drive keeps humming away.

It’s no secret that a successful SharePoint implementation relies on user adoption, but how can we, as site collection administrators and content managers, effectively change user behavior?

Invite your end users to the project kick-off
Is it so ridiculous to have the people sitting around the table be a sampling of the people who will actually be using the site? No. But, time and time again we keep our website redesign projects close to our IT or Communications chests and we don’t take them to our information workers before it’s far too late. There are key end users in your organization. You know who these people are – they make things happen in your office. You need their buy in. Get it from the start. Five questions to ask your key end users at the project kick-off meeting:
  • What one website feature would make your job easier?
  • What concerns do you have about using this tool?
  • What concerns do you have about changing your processes?
  • How can we help make that transition better?
  • Would you be willing to offer your input and feedback throughout this redesign process?
Trust me. They’ll be flattered you asked, and you’re already on your way to building an evangelist.

Define your governance plan and ownership early in the process
Governance is always an afterthought. When the site is near completion someone mentions that the team should document its processes and best practices -- maybe it happens, maybe it doesn’t.  The project governance committee should be in place soon after the project kick off meeting, and the committee should work in tandem with the rest of the project team throughout the project lifecycle to draft and implement an effective governance plan. Governance doesn’t come easy, and a solid plan takes time to develop and even more time to socialize with staff and end users. The only way to do this effectively is to start early.
Three key elements of a good governance plan:
  • Definitions of roles and responsibilities – specifically. 'IT will be responsible for monitoring the site servers' is not specific. 'The XXXX position on the IT team will be responsible for monitoring the servers and keeping accurate logs of the status on a monthly basis' is a specific responsibility.
  • Guidelines for enforcement - guidelines that are actually enforced. If we never got tickets for speeding, would we think about driving the speed limit?
  • Updates - the plan is not just emailed to users for posterity and never revisited. The governance plan is a living, breathing document and should be frequently revised. All staff should be acquainted, and re-acquainted with its key tenets on a regular basis.
Training, training, training
And not just training in front of a computer screen – “training” at town hall meetings, “training” during office happy hours, “training” in your weekly office newsletter. Unless a user is convinced that his or her job will be made better, easier, and more efficient by your new SharePoint site, that user isn’t going to give changing his or her behavior a second thought. For many of us the allure of a SharePoint implementation lies in its ability to offer a vast sharing and collaboration platform that’s compatible with much of the software we already have in place at our organizations. It takes users away from their C:// drives and forces them into knowledge sharing.  On several projects, recently, I’ve seen the training process be the “make it” moment of the project. Users walked away from their training experience excited to use the new site, and bolstered by the ease of the system that was once daunting to them – training is as much about socialization as it is about actually learning new skills.  A solid and comprehensive training plan will lead to user adoption.
Four keys to a successful training plan:
  • Start really early, and the first meeting doesn’t even need to involve a computer. Your first training session should be a high-level overview of the project and the top benefits the new site will offer end users. Get them excited.
  • Mix departments and users. In many ways SharePoint is about getting out of silos. Make that clear by mixing up your training sessions.
  • Tough love. The old system IS going to go away. Give a date. Give a time. Whatever you need to do. It’s like taking away a baby’s pacifier. It’s very, very painful for the parents (maybe more than for the baby!), but eventually it has to be done. Communicate this during your trainings and ensure that you will do everything you can to make this transition easier on your users. But acknowledge that you’re all equal partners in this and that they will have to make changes and try new methods.
  • Don’t discount one-on-one training. Sure, it’s time consuming, but the best training plans offer several group sessions combined with options for further one-on-one training.  A simple one-on-one session can turn a doubter into a believer in just a few short hours.
Users need a take-away post training so they know you aren’t leaving them high-and-dry once their sessions are complete. It can’t hurt to point out during any and all training sessions that there are tons of free training materials on the internet. For starters:

User adoption is never easy and rarely happens overnight. It needs to begin at the outset of a project to fully take root prior to launch, and continue well after a site has launched. Successful user adoption plans put the users first, and continually communicate the following: We chose SharePoint because, XXXXX XXXXX. It’s going to make your jobs easier because of YYYYY YYYYYY. And we’re 100 percent behind this project and our users. This technology is here to support you.
 
Souces:

January 25
Resumes in 2012


It seems everyone has an opinion on what a résumé should contain, how many pages it should be and how it should be formatted. So as we enter into a new year, what are the universally agreed-upon elements that are in, and which ones are now passé? Here are some of the best practices when it comes to crafting your résumé in 2012:

Stop trying to make "objective statements" happen
The days of including a career objective and/or professional summary are over. It's a waste of valuable space. Instead, just address this with a sentence in your cover letter about how the position you're applying for fits into your overall career plan. Get to business by starting with accomplishments and facts that are relevant to the job posting.
Be concrete
Use numbers and proof of what you've done. "Increased sales by 35 percent through client profiling campaign" is better than "Increased sales in my region." Stop putting generic tasks down, and instead, get creative in portraying what you did in your role or how you brought forth new ideas for products, processes, efficiency, etc. The more you can quantify your efforts with actual numbers or data, the better positioned you'll be.
Cover letters are back
Like the "two page versus one page" debate, the subject of cover letters is heated. While some recruiters say they don't bother looking at them, others say some job seekers have grown lazy and won't take the time to write one or tailor one specifically to the company to which they are applying. It's a perfect opportunity to sell yourself, and it's where you can infuse personality into your application. But once you craft a terrific cover letter, don't just push it out to every job prospect. Take the extra few minutes to tailor it to why you want that specific job at that specific company and why your skills would benefit the overall organization if hired.
Keywords are your friend
If a recruiter or manager can put your résumé side-by-side with the job requirements and check off the same keywords, you've made his life so much easier. Instead of using a lot of useless jargon on your résumé, pay attention to the keywords in the job posting. Be sure to use them in your résumé and cover letter, because even applicant tracking systems are based on keyword searches. Just as you use keywords to search for jobs, employers are using keywords to find your résumé.
Get creative with quick response codes
Young professionals are using QR codes -- bar codes that can be scanned by smartphones to download or link to information -- on the back of business cards and on their résumé to link to online portfolios. As you network and attend career fairs, you're able to pass out business cards with the QR code that can link recruiters and other contacts to either your portfolio or LinkedIn profile so they can instantly connect with you.
Wow with visual résumés
More people are using tools to help illustrate their work history through sites such as Vizualize.me. These sites offer tools to help individuals present the information on their résumés in a unique way that stands out. Just remember that you still need a traditional format to hand out or attach to make it easy for saving in company databases.
Give video a chance
In this tough economy, job seekers are going to creative lengths to get their name, talents and personality in front of employers, like this résumé video for a Google position. If you're going to create something like this, make sure you're providing substance or showing off your soft skills within the video instead of just doing something flashy to get the recruiter's attention.
Social media are here to stay
If you're not using social media to promote yourself, you're missing out. Just as employers use multiple avenues to push out job postings, you as a job seeker need to use all the channels available to you to put yourself in front of recruiters. Using Twitter, Facebook or LinkedIn as a means to give updates on your career or connect with other professionals gives your résumé legs and can make you more memorable as a candidate. But since companies are screening candidates through social media, make sure your online profiles are either professional facing or locked for outside viewing.
 
 
Justin Thompson is a writer and blogger for CareerBuilder.com and its job blog, The Work Buzz. He researches and writes about job search strategy, career management, hiring trends and workplace issues.

 

January 18
5 Things 2 look for in an great interview

 

In my career I have reviewed thousands of resumes and conducted hundreds of employment interviews for both The Trademark Company and other businesses for which I have worked. In doing so, I got to see the good, the bad, and the downright ugly in terms of resumes, interviewing skills, and the like. For other CEOs looking to hire, here's what I think makes a great candidate stand out from the good ones.

1.  Attention to detail

How many times have you heard this one, right? Pay attention to detail. Let me say it again: PAY ATTENTION TO DETAIL!

There’s a great story at the end of the movie Coming to America with Eddie Murphy. It goes something like this:

A man goes into a restaurant. He's having a bowl of soup and he says to the waiter, “Waiter come taste the soup.” The waiter says, “Is something wrong with the soup?” He says “Taste the soup.” The waiter says again, “Is there something wrong with the soup? Is the soup too hot?” The man says again, “Will you taste the soup?“ “What's wrong, is the soup too cold?" Replies the waiter.  “Will you just taste the soup?!”  “All right, I'll taste the soup,” says the waiter, “where's the spoon??” “Aha. Aha! ...”

At this point you may be asking yourself, “So what does this have to do with identifying a great candidate?”

Not less than two months ago I received a wonderful e-mail from an applicant seeking to work for The Trademark Company. The e-mail was personally crafted. The note struck a wonderful tone emphasizing capability and a willingness to learn more about what we do here. Most importantly, the candidate emphasized attention to detail. I was sold. I was ready to open up the resume and see what they had to offer. And then, “Aha. Aha! ...”

The applicant had failed to attach a resume. In the blink of an eye, all of the time spent preparing for this submission--researching me, the company, and the job’s requirements--vanished into thin air. Poof!

Some CEOs may have overlooked this and just asked for the resume. But you can’t say you have an eye for detail and then fail to deliver on the point. Everything job candidates do, from cover letter to resume and beyond, must prove that point. Otherwise they are just wasting your time. I passed on that candidate.

2.  Proofread

My contracts professor in law school told this one to the class one day. Although he was an otherwise socially challenged individual, this story has always stayed with me.

It seems that at some juncture he was involved in delivering a speech on some topic that involved a “public option.”  He had written and prepared the speech but had left the PowerPoint slide presentation to one of his assistants.

Well, as he began delivering his speech–a seemingly dry speech–he could not understand why a wave of chuckles and murmurs would, from time to time, arise from the audience. It was not until he neared the end of his presentation that he glanced up at the screen projecting the bullet points of his speech behind him. And right there, right in that moment, he understood with perfect clarity why his speech had evoked the unexpected reaction from the crowd.

If you omit the letter “L” from the word “public,” it won’t be flagged by spell check. It will, however, be picked up by anyone else reading the slides as you deliver your speech on the “pubic option.”

This could very well be you at your next sales presentation: pissed and embarrassed because you overlooked your employee's failure to proofread his resume during the hiring process. So, check the candidate's resume and cover letter for misspellings that spell check might have missed. In so doing you will make sure that you hire someone that's thorough and doesn't rely on spell check to do their job.

3.  Preparedness

One of the first things I always do after an interviewee leaves is to ask every single person who came into contact with them what they thought. Why you might ask? You never know what little windows into your prospective employee this may provide.

Once I asked one of our receptionists what she thought of a particular interviewee. I was very surprised to hear what she had to say. She said she thought the interviewee was pleasant but did have some trouble when she first arrived: It seems that the prospective employee had no idea who she was interviewing with, so the receptionist had to call around the office for 10 minutes until she could figure out who to notify that their appointment had arrived.
I thought this displayed a lack of preparedness on the interviewee’s part, especially as she was interviewing for a job that had primary scheduling responsibilities for me and would require her to know and keep track of all of our most important customers.

In another case, after a 45-minute interview the interviewee stood and said, “Mark, thanks for the second interview.” Big problem: My name is actually Matt. Nevertheless, I shrugged it off--perhaps I had misheard the applicant, or maybe he had simply had a momentary lapse. However, when I walked him to the door he proudly reiterated my name, “Mark, again thanks. I look forward to hearing from you.” Every fiber in my being yearned to reply, “Well, if I meet this Mark fellow, I’ll be sure to have him call you.” I did not. I also did not call him back.

A candidate should know everything about you that they can find out and engage you on a level that you will enjoy and that moves you one step closer to offering them the job.

4.  Phone and e-mail correspondence

Another thing that also gets overlooked is professionalism in e-mail and phone communications. I pay attention to the candidate's e-mail address and how they answer their personal phone.

Sure we all have private lives, but we all have to be professional in dealing with employers--and, most importantly, prospective employers. So if a candidate's e-mail address is "bigsexy@gmail.com" or “hunkaburninlove@yahoo.com,” think twice about hiring him. Gmail, Yahoo and other companies have a great price point for new e-mail addresses: free. There's no excuse for not having a professional-looking e-mail address.

For me, an interview starts when I call you to set up the interview. Recently I called an applicant, and they must have been at a the reunion tour of Van Halen--because when the candidate answered, all I could hear was “Ain't Talkin' 'Bout Love” blasting through my phone. I mean, it was so loud I could actually see people in my office starting to bob their heads to the tunes.
After a few attempts shouting into the phone--“Is [Name Omitted] there?”--finally the music departed and I was able to hear once again. The heads stopped bobbing in my office and the person on the other end said, “Speaking.” Ahhhh. Well, I know they love music...and that they lack judgement.

5.  Honesty is overrated

Yes, you want your potential employee to answer questions truthfully, but answering too truthfully may also show a lack of judgment. For instance, I often ask the hypothetical question, "If you were hired and six months after you were hired another opportunity presented itself, would you go on an interview for that opportunity?" You would be surprised at how many people say they would. Wrong answer!

Let’s take one of my more infamous examples. Once I was asking a prospective employee to explain an 18-month gap in his employment history. To this day I remember his response verbatim. It went like this: "Man, the whole work thing ... ya' know ... like, wow."  I was left mouth agape and speechless. Needless to say: He did not get the job.

 

Read more: http://www.inc.com/matthew-swyers/5-things-i-look-for-in-a-jgreat-job-interview.html

January 18
Writing the right Requirements

 

Have you ever wondered why SharePoint requirements are so difficult to create when engaging a business or project team? When an individual creates a wish list for a product or service, the list is typically short, sweet and to the point. However, when a team gets together, and people begin to discuss their collective needs, the same list becomes exhaustive and difficult to navigate.

At the end of that effort, the Project Manager is left with a convoluted mess of both needs and wants, while the end product still seems months (or longer) away from the pending reality that is the implementation and effective use of SharePoint.

As Project Manager, the first question to ask when defining SharePoint requirements is what initial functionality is needed to increase efficiencies. The Project Manager must explain to his or her project team and end users that SharePoint is not just a “thing” or “system”; rather, it is a collection of products, and it must be viewed by the business in the same way it views Microsoft Office.

Simply stating that the business “needs” document management is the same as saying the business needs Microsoft Word, a simple statement with a huge impact. What is the maturity of the business? What systems are currently in use? How is information being stored? How will you retrain end users?

In any requirements effort, it’s important to provide an appropriate amount of consulting, training and explanation in order to equip the business with the SharePoint knowledge to make the necessary requirements decisions. Henry Ford famously said, “If I had asked people what they wanted, they would have said a faster horse.” Before cars became a universal form of transportation, horses were the accepted method—it was the frame of reference people could articulate. To put that into the SharePoint context, if you don’t see the vision of SharePoint and understand what its capabilities are, how can you define your requirements?

Here are some steps to get your SharePoint requirements written right!
First, assist the project managers out there with suggestions on how to engage the business unit, define a user community and create a phased approach to your SharePoint project.
Second, focus on the process behind eliciting and prioritizing requirements, and the third will suggest how to document and action your requirements into meaningful, tangible, actionable statements that your developers can begin working on immediately.

When working with your team on eliciting and prioritizing requirements, your first task is creating a measurable baseline and common understanding of the goals and expectations for your requirements. Without this common framework and measurement, you and your team are destined for failure.

Think of this as the equivalent to preparing for a trip. Before leaving home, you would have your initial requirements in hand: the duration of your trip, the weather at your destination, you’re planned activities while away, and what clothes you'll need to pack. These are your variable requirements, those which you have no control over and have external dependencies (you can pack all you’d like, but the airline can still lose your luggage).

Next, you would confirm that your fixed requirements are in place; these are things that you would have a difficult time replacing while away, such as cash, medication, glasses or contact lenses. The point is, what takes priority on your list and what makes one item more important than another? This is the question your team needs to ask to be efficient and effective when writing requirements.

Review:  You engage the business unit, defining a user community, and creating a phased approach to your SharePoint project requirements.
 

Focus on strategies toward effectively creating and documenting your requirements into meaningful, tangible, actionable statements.

A common practice in requirements sessions is to get the team together and to simply talk through how your existing portal or intranet operates, while an analyst sits in the corner and furiously attempts to capture the information. Though this approach is unstructured and takes a strong project manager to control the session, it can uncover some valuable information on the high-level needs you’ll want to build into SharePoint. The difficult part will be documenting the information in a format to appropriately leverage the information and have it be useful in the overall process.

In order to have meaningful and result-driven requirements sessions, follow these steps to success:

Plan: The adage “measure twice, cut once” is relevant when planning and executing requirements sessions. Spend time measuring the needs of business users and the strategic objectives the business wants SharePoint to provide. Create a schedule that shows when and where participants should meet, the details of the meeting, and the anticipated outcome for each session; also, be sure to invite participants well in advance to ensure their availability.
Finally, when planning your meeting, set each session up for no more than two hours. Enforcing the two-hour rule ensures that participants are fresh and remain interested in the conversation.

Discuss: Start the session by outlining your objectives and expectations to the group. Show some sample portals that have been developed in SharePoint (e-mail me for screenshots) to build excitement for what you’re about to undertake. Discuss the importance of having transparency in your communication, and that each point is a steppingstone toward a formidable SharePoint solution. Then begin by asking some high-level questions to generate thought and feedback. How will the portal change the day-to-day work completed by staff? How can you best leverage portal functionality to empower users?

January 12
Use SharePoint 2010 Document ID to Avoid Broken LInks

In SharePoint 2007 if you rename or move a document then all the existing links to it will be broken. Naturally, this leads to angry users and headaches for IT support and staff in general.

Simply put, it affects productivity, especially if happens often. With SharePoint 2010 this issue is resolved by the introduction of Document ID functionality. Basically, each document gets a unique ID that, regardless of its location, remains the same.

This means that when you move or rename a document this ID will not change. So you end up with a static or permanent link to your documents. You will see later in this tip how this unique ID is used in a special URL to access the document.
Let's see how you can configure and use Document IDs in SharePoint 2010.
1. Browse to your SharePoint site and navigate to the site settings page. Click on the Site Collection Features link located under Site Collection Administration section. Locate the Document ID Service and click Activate.
 
2. Browse to the Site Settings page and click on the Documents ID Settings link located under Site Collection Administration section as shown below.
3. On the Document ID settings page you can put custom characters in a text box (as shown below) which will be added in the start of Document IDs. If you are using them, make sure they are unique and are not repeated. For the search scope -- which lets you select the search scope that will be used to search for documents based on their IDs -- leave it to default (unless you want to use another scope).
4. You are done, but SharePoint 2010 will start assigning the IDs to the documents once it runs the relevant time jobs. If you look at the figure in step 3, there is text in red mentioning this point.
To get IDs assigned immediately, you have to run the jobs manually and then schedule them with the frequency that suits your needs. To do this, run Document ID assigned job and Document ID enable/disable job, browse to SharePoint Central Administration'Monitoring'Review Job Definitions and click on each of these links (one at a time and click Run Now).
 
You can also change the schedule of this timer so that it meet your needs, although in the figure above it is set to run after one minute. But this may not be the ideal setting for production environments.
5. Browse to your site collection and upload a document into a document library and verify that the document is assigned with a Document ID. You can view the document properties as shown in the figure below.
Please note that your ID will be different.
6. The document ID field is in the form of URL, if you click on it or see the properties of the link (as shown below) you will notice that document id itself is passed as a query string to a SharePoint page DocIdRedir.aspx.
 
Now you can pass this link/URL to the users and they can access the document and this link/URL will remain valid even if you rename or move the document.

 

That's pretty powerful, isn't it? Your IT department and your customers will thank you.
 
Source: www.sharepointbriefing.com 

January 11
Sharepoint 2010: Solution: Central Administration General Settings Error

Problem:
Getting error message under Central Administration -> Manage web applications -> General Settings

 

Error:
Updates are currently disallowed on GET requests. To allow updates on a GET, set the ‘AllowUnsafeUpdates’ property on SPWeb.
Solution:
Run this powershell script:

 

$w = get-spwebapplication http://yoursharepointsite
$w.HttpThrottleSettings
$w.Update()

 

Src:

https://tolgaizgi.wordpress.com/2011/07/19/sharepoint-2010-solution-central-administration-general-settings-error/

 

 

 

January 08
Change SharePoint Site Icon
  1. Browse to SharePoint Site, from action menu click All site content
  2. Under Document Libraries, click Style Library link
  3. If you installed two or more language, then you will find a folder for each language
  4. You can browse to Themable folder under each installed language or you can create new folder and name it “Themable” on the root of the document library
  5. Click the Themable folder and create a new folder under it, name it as “CompanyLogo”
  6. Open the folder “CompanyLogo” and upload you logo by clicking documents tab from the Ribbon then click upload document button
  7. Browse to your logo and click OK
  8. From the opened dialog, you can change the file name and set a title for the file and click Save
  9. Hover over the file, and open the file menu and click “Publish a Major Version”
  10. Write comment in the Publish Major Version dialog and click OK
  11. Go to site settings by clicking the action menu and select Site settings
  12. Under the Look and Feel Group, click Title, description, and icon link
  13. In Logo URL and Description section, fill “/Style Library/Themable/CompanyLogo/Logo.png” in the URL section
  14. Click “Click here to Test” link to make sure that you provide the right URL then click OK
Your logo now should replace the default SharePoint logo.

 

March 16
How to use PowerShell to configure the Developer Dashboard

Run PowerShell as an administrator - Type this:

$dash =

[Microsoft.SharePoint.Administration.SPWebService]::Content Service.DeveloperDashboardSettings;

$dash.DisplayLevel = 'OnDemand';

$dash.TraceEnabled = 'true';

$dash.Update()

1 - 10Next
 

 About this blog

 
dm115.jpg

 
Welcome to ASAP SharePoint Services Blogs. Use this space to provide a brief message about this blog or blog authors. To edit this content, select "Edit Page" from the "Site Actions" menu.