MSTSC (MicroSoft Terminal Services Client - better way of remebering the command) had /console option for win 2003 for various reasons like using high previlege 0 session , reclaiming a session, connecting without using CAL etc which is not there for windows 2008 as session 0 is only for services and not for applications. There is /admin option which is used for reasons like elevated mode and can connect even when TS is in drain mode as described here
http://windowsitpro.com/article/articleid/97716/what-is-the-admin-switch-in-microsoft-terminal-services-client-mstsc-for-windows-2008-and-vista.html
Also intresting /span option can be used to grab multiple monitors.
Saturday, 20 June 2009
Friday, 5 June 2009
Add KnowledgeBase Template from Application Templates
Application Templates can provide good starting point.
http://technet.microsoft.com/en-us/windowsserver/sharepoint/bb407286.aspx
We will use the KnowledgeBase to get a working base and build on top it in future.
We will get a Keyword list, Articles with recently added, relevant articles, action to add a article page and tag and as per documentation - The template enables team members to upload existing documents or create new ones using Web-based content creation tools. Items are tagged with relevant identifying information so that others can more easily find the documents and learn from the collective knowledge in their organization. The template can be utilized in a 'top down' approach, where a centralized knowledge department 'pushes down' relevant content to the rest of the business or a 'bottom up' approach, where knowledge is captured and shared by all users as a normal part of doing business.
Overall good starting point.
Later on as we refine the functionality it will be stapeled to this site definition.
Remember to install ApplicationTemplateCore solution.
I am currently looking at the further customisation of this template particularly *** solution shall post back soon on that.
http://technet.microsoft.com/en-us/windowsserver/sharepoint/bb407286.aspx
We will use the KnowledgeBase to get a working base and build on top it in future.
We will get a Keyword list, Articles with recently added, relevant articles, action to add a article page and tag and as per documentation - The template enables team members to upload existing documents or create new ones using Web-based content creation tools. Items are tagged with relevant identifying information so that others can more easily find the documents and learn from the collective knowledge in their organization. The template can be utilized in a 'top down' approach, where a centralized knowledge department 'pushes down' relevant content to the rest of the business or a 'bottom up' approach, where knowledge is captured and shared by all users as a normal part of doing business.
Overall good starting point.
Later on as we refine the functionality it will be stapeled to this site definition.
Remember to install ApplicationTemplateCore solution.
I am currently looking at the further customisation of this template particularly *** solution shall post back soon on that.
Thursday, 4 June 2009
Defining the Knowledge Management solution on SharePoint/MOSS
The earlier post focussed on use and key role of Wikis and Blogs and My Sites and Search in Knowledge Management. Wikis and Blogs (Usually in case of Wiki content is dynamic i.e. a Wiki page gets modified continuously where as in case of Blog the content i.e. post is static and gets enhanced using say comments ) Team site discussions and Surveys are also important in this regard.
It’s important to understand that maximum value is delivered by un-structured, informal way of knowledge sharing such as wikis and blogs. Its most simple form and with maximum value and can hit the ground running in KM initiative. These can be developed at minimal level using WSS 3.0 as platform. I say this because KM is usually perceived as massive organisational initiative which it is but that doesn't mean that KM is limited to big organisations with lot of infrastructure to support but even very small organisations can do KM with WSS 3.0 without lot of customisation efforts and can start KM initiatives around these areas and slowly add more managed capabilities around it. It will be more agile way of doing it. SharePoint as extensible platform can take the KM initiative to any extent.
Let’s start the whole KM initiative with basics first and enhancing it one by one so that one can pick up only what is needed and get going with KM. I will embed the links to posts for actual implementation in these so that this post remains a central point more like a wiki :)
Let’s say we are doing it for Suman Technologies (STL here after). STL has fully appreciated importance of KM and let’s hit the ground running by implementing it.
SR No
Requirements
Implementation Guidance Links
RC 1.0
Build a Corporate portal.
I will just use OOTB Team site collaboration template. I may add something like branding, navigation etc but let’s be more focussed on KM at this point.
RC 2.0
Build a knowledge repository for STL - Content addition
This is start of KM. KB repository will act as storage of KM assets which organisation cannot afford to lose or let them remain dispersed in collaboration portal in scattered manner (need to get 'start' meaning right here. By that I meant one of KM specific thing which happens to appear as first in this requirement listing here as I feel existence of knowledge base repository is optional if you agree with my 'natural selection' approach to KM assets in case of minimal KM. Building such repository usually bogs down KM initiative only to find later that design is in need of enhancement if not outright convoluted when KM system becomes fully functional. No defiance of Enterprise Architecture, Design Governance, Security and Capacity planning etc etc, I myself is advocator of it, Agile (success is built on top of more granular successes) side of mine says it can be done incrementally. The extent of this largely depends on organisation in picture bear in mind KM is for everyone as small as individual consultant like me to large organisations like NASA, Govt and Public sector bodies and High end and Large Consulting organisations with varying security, structured-ness, management and control, capacity needs. Its about leveraging lively benefits of unstructured , informal mode and using technology and add ons - starting with SharePoint / MOSS , WCM and publishing and metadata management and taxonomies and aggregation across site collections / external systems to custom components, WebParts using .net, Ajax, Advanced federated Search and Analytics or something as advanced as Bayesian inference (this would be the last reference to this hereafter :)) , see its limited by imagination only, rather than mandating the users, to add structure to it and managing it)
Implementation -
http://mossuk.blogspot.com/2009/06/add-knowledgebase-template-from.html
RC2.1
Allow users to add kb content - articles, documents, presentations, spreadsheets, videos, and links to external or internal content to knowledge repository from Collaboration Portal in controlled manner. KB content after submission should undergo approval before getting published on KB repository.
RC2.2
Allow the users to attach meta data tags to kb content.
RC 2.2.1
Meta data tags shall be centrally managed in KB repository and need to be mapped to one or more taxonomical areas of the KB repository. User should be prompted predictive text as she types a tag.
RC 2.2.2
There should be suggested tags area to give the User hint based on content what tags can be reused.
RC 2.2.3
Should Tag be a new one i.e. doesn't already exist, a Tag review task shall be assigned to Central KM authority as part of KB content approval.
RC 2.2.4
Content approver should be able to reclassify, change tags for the content before approving. Content approver should be able to reject/ request modification to Author adding notes
RC 2.3
Content can be uploaded to KB repository portal itself.
RC 2.4
KB repository will provide Hierarchical as well Tag driven navigation.
RC 2.5
All users should have contributory rights to KB Repository.
RC 2.6
Content can remain in Draft status and alert shall be sent to author after specified after specified days requesting completion date, after that there should be alert after that tentative date and after certain cycles of alert content can be expired with proper intimation to user
RC 2.7
Author shall get email when content is published including link to it.
RC 2.8
It should be possible to bulk load content into KB repository from existing WSS 2.0 portal
RC 2.9
It shall be possible to bulk load content into KB repository from existing ASP based KB web site.
RC 2.10
KB repository should allow creating discussion threads.
RC 2.11
KB repository should provide for applying configurable expiration policies
RC 2.12
KB repository shall audit content access and provide content usage report
RC 2.13
KB repository shall provide for allowing certain content to be restricted in view and download which might be specified by content author or approver and should provide item level security in such cases. Integration with RMS should be possible.
RC 2.14
In certain cases it shall be possible to add watermark to content
RC 2.15
In certain cases it shall be possible to prevent printing of content but viewer should be able to request if needed.
RC 2.16
Virus check shall be performed on the content and certain type of content can be blocked as part of configurable policy.
RC 2.17
It should be possible to submit/promote the article which has been created as a blog post by the user on her personal My Site
RC 2.18
System shall be able to find out and report broken links.
RC 3.0
KB Repository - view, search and aggregation
RC 3.1
All STL employees can have reader access to KB portal except areas where it would be role based. The content served would be security trimmed.
RC 3.2
KB Repository home page will have WebParts for Recently added content, Most viewed, Tag Cloud which would allow drilling down further.
RC 3.3
Search can be performed for content in the form for keyword, free text, scope limited and results would be delivered (security trimmed) with ability to filter based scope, meta tags, rating etc
RC 3.4
User can rate the article or add comment. It shall be possible to (default) or not to moderate the comment by application of policy. Comments shall be captured and stored with content
RC 3.5
if the article has been created from a post then there should be ability to synchronise either way including comments.
RC 3.6
It shall be possible in future, to exchange information in discussions internet forum on STL 's customer internet portal where customers have asked certain questions about products / services.
RC 4.0
My Sites
RC 4.1
My Sites shall be provisioned for users whenever user first time navigates ‘My Site’ in collaboration portal in global navigation
RC 4.2
My Site will allow manage user profiles management allowing administrator to update profile attributes and users provide data
RC 4.3
My site will enable user to view her calendar, manage personal documents, view and track colleagues
RC 4.4
My Sites will allow users to create a personal blog, It will be possible to push/publish the blog post to KB Repository
RC 4.5
My site blog shall integrate with MS word / one note
RC 4.6
My Site will provide navigation back to portal, user’s links within portal as well as internal applications
It’s important to understand that maximum value is delivered by un-structured, informal way of knowledge sharing such as wikis and blogs. Its most simple form and with maximum value and can hit the ground running in KM initiative. These can be developed at minimal level using WSS 3.0 as platform. I say this because KM is usually perceived as massive organisational initiative which it is but that doesn't mean that KM is limited to big organisations with lot of infrastructure to support but even very small organisations can do KM with WSS 3.0 without lot of customisation efforts and can start KM initiatives around these areas and slowly add more managed capabilities around it. It will be more agile way of doing it. SharePoint as extensible platform can take the KM initiative to any extent.
Let’s start the whole KM initiative with basics first and enhancing it one by one so that one can pick up only what is needed and get going with KM. I will embed the links to posts for actual implementation in these so that this post remains a central point more like a wiki :)
Let’s say we are doing it for Suman Technologies (STL here after). STL has fully appreciated importance of KM and let’s hit the ground running by implementing it.
SR No
Requirements
Implementation Guidance Links
RC 1.0
Build a Corporate portal.
I will just use OOTB Team site collaboration template. I may add something like branding, navigation etc but let’s be more focussed on KM at this point.
RC 2.0
Build a knowledge repository for STL - Content addition
This is start of KM. KB repository will act as storage of KM assets which organisation cannot afford to lose or let them remain dispersed in collaboration portal in scattered manner (need to get 'start' meaning right here. By that I meant one of KM specific thing which happens to appear as first in this requirement listing here as I feel existence of knowledge base repository is optional if you agree with my 'natural selection' approach to KM assets in case of minimal KM. Building such repository usually bogs down KM initiative only to find later that design is in need of enhancement if not outright convoluted when KM system becomes fully functional. No defiance of Enterprise Architecture, Design Governance, Security and Capacity planning etc etc, I myself is advocator of it, Agile (success is built on top of more granular successes) side of mine says it can be done incrementally. The extent of this largely depends on organisation in picture bear in mind KM is for everyone as small as individual consultant like me to large organisations like NASA, Govt and Public sector bodies and High end and Large Consulting organisations with varying security, structured-ness, management and control, capacity needs. Its about leveraging lively benefits of unstructured , informal mode and using technology and add ons - starting with SharePoint / MOSS , WCM and publishing and metadata management and taxonomies and aggregation across site collections / external systems to custom components, WebParts using .net, Ajax, Advanced federated Search and Analytics or something as advanced as Bayesian inference (this would be the last reference to this hereafter :)) , see its limited by imagination only, rather than mandating the users, to add structure to it and managing it)
Implementation -
http://mossuk.blogspot.com/2009/06/add-knowledgebase-template-from.html
RC2.1
Allow users to add kb content - articles, documents, presentations, spreadsheets, videos, and links to external or internal content to knowledge repository from Collaboration Portal in controlled manner. KB content after submission should undergo approval before getting published on KB repository.
RC2.2
Allow the users to attach meta data tags to kb content.
RC 2.2.1
Meta data tags shall be centrally managed in KB repository and need to be mapped to one or more taxonomical areas of the KB repository. User should be prompted predictive text as she types a tag.
RC 2.2.2
There should be suggested tags area to give the User hint based on content what tags can be reused.
RC 2.2.3
Should Tag be a new one i.e. doesn't already exist, a Tag review task shall be assigned to Central KM authority as part of KB content approval.
RC 2.2.4
Content approver should be able to reclassify, change tags for the content before approving. Content approver should be able to reject/ request modification to Author adding notes
RC 2.3
Content can be uploaded to KB repository portal itself.
RC 2.4
KB repository will provide Hierarchical as well Tag driven navigation.
RC 2.5
All users should have contributory rights to KB Repository.
RC 2.6
Content can remain in Draft status and alert shall be sent to author after specified after specified days requesting completion date, after that there should be alert after that tentative date and after certain cycles of alert content can be expired with proper intimation to user
RC 2.7
Author shall get email when content is published including link to it.
RC 2.8
It should be possible to bulk load content into KB repository from existing WSS 2.0 portal
RC 2.9
It shall be possible to bulk load content into KB repository from existing ASP based KB web site.
RC 2.10
KB repository should allow creating discussion threads.
RC 2.11
KB repository should provide for applying configurable expiration policies
RC 2.12
KB repository shall audit content access and provide content usage report
RC 2.13
KB repository shall provide for allowing certain content to be restricted in view and download which might be specified by content author or approver and should provide item level security in such cases. Integration with RMS should be possible.
RC 2.14
In certain cases it shall be possible to add watermark to content
RC 2.15
In certain cases it shall be possible to prevent printing of content but viewer should be able to request if needed.
RC 2.16
Virus check shall be performed on the content and certain type of content can be blocked as part of configurable policy.
RC 2.17
It should be possible to submit/promote the article which has been created as a blog post by the user on her personal My Site
RC 2.18
System shall be able to find out and report broken links.
RC 3.0
KB Repository - view, search and aggregation
RC 3.1
All STL employees can have reader access to KB portal except areas where it would be role based. The content served would be security trimmed.
RC 3.2
KB Repository home page will have WebParts for Recently added content, Most viewed, Tag Cloud which would allow drilling down further.
RC 3.3
Search can be performed for content in the form for keyword, free text, scope limited and results would be delivered (security trimmed) with ability to filter based scope, meta tags, rating etc
RC 3.4
User can rate the article or add comment. It shall be possible to (default) or not to moderate the comment by application of policy. Comments shall be captured and stored with content
RC 3.5
if the article has been created from a post then there should be ability to synchronise either way including comments.
RC 3.6
It shall be possible in future, to exchange information in discussions internet forum on STL 's customer internet portal where customers have asked certain questions about products / services.
RC 4.0
My Sites
RC 4.1
My Sites shall be provisioned for users whenever user first time navigates ‘My Site’ in collaboration portal in global navigation
RC 4.2
My Site will allow manage user profiles management allowing administrator to update profile attributes and users provide data
RC 4.3
My site will enable user to view her calendar, manage personal documents, view and track colleagues
RC 4.4
My Sites will allow users to create a personal blog, It will be possible to push/publish the blog post to KB Repository
RC 4.5
My site blog shall integrate with MS word / one note
RC 4.6
My Site will provide navigation back to portal, user’s links within portal as well as internal applications
Tuesday, 2 June 2009
Wikis and Blogs and Search can they deliver Knowledge Management?
I recently deliberated a lot on how SharePoint can be leveraged for Knowledge Management. I had been preoccupied with KM as more formal way of managing intelectual assets and KM also shall provide measurement of value addition.
When it comes to Wiki/Blog its about knowledge sharing. Good thing about blog is once its placed on mysite it actually ecourages postings of useful stuff as 'its on users own site' and can give some sort pride/recognition which traditional KM portals built using web technologies fail to achieve. A Top Blogger web part on corporate team site would do the trick anyway. So its great and spot on for motivating poeple to share , one of the hardest thing to achieve.
That was about Sharing , is it different from management?
Does it provide any measurable statistics about knowledge asset leverage and increased agility/productivity - Answer is (mine) some charts and graphs cannot be more important than universal truth of blogs as most effective tool for knowledge sharing on internet.
So what about the assets and their management - if someone is looking for something, she can search , read related blogs which show up in result, if found intresting contact the author , inquire if any artifacts can be shared? there you go , reuse the artifacts. Now someone would say whats the gurantee such artefact would be preserved by or shared by that author - well if the artefact is important enough be sure 90% chances it would kept by the author and is there any KM system which automatically captures 100% assets ? so its a very good deal without much cost. Now what if author doesn't want to share - that falls against the spirit of blogging and chances are rare - should it be the case you know auhtor also has a boss in the organsiation who can provide more guidance on that.
Secondly preservation of such assets on long term basis - if the asset is good it would live in the organisation for good no of years even if not with original source so theory of natural selection would apply.
Preservation of articles / posts - well they are in the list anyway.
So making KM informal does seem derive lot of value than costly solutions and all with just wikis, blog sites and my sites and search which would exists in collaboration portal anyway. So stop worrying about KM as such, you got it already.
One key technical point to note with mysite customization - feature stapling is solution as its done using self service mode.
Also Ajax rating control can be added to Post pagelayout and rating as column to Post Content Type.
Should any one be still worried about the statistics and really want to go what KM has been traditionally since mid 90's then it is achievable (you know the 'a lot' word which follows deliberated :)) with some design thought before hand which I would post in future but I would like to hear if thats needed , what you think ... should put this on InformationZen as new topic ...
When it comes to Wiki/Blog its about knowledge sharing. Good thing about blog is once its placed on mysite it actually ecourages postings of useful stuff as 'its on users own site' and can give some sort pride/recognition which traditional KM portals built using web technologies fail to achieve. A Top Blogger web part on corporate team site would do the trick anyway. So its great and spot on for motivating poeple to share , one of the hardest thing to achieve.
That was about Sharing , is it different from management?
Does it provide any measurable statistics about knowledge asset leverage and increased agility/productivity - Answer is (mine) some charts and graphs cannot be more important than universal truth of blogs as most effective tool for knowledge sharing on internet.
So what about the assets and their management - if someone is looking for something, she can search , read related blogs which show up in result, if found intresting contact the author , inquire if any artifacts can be shared? there you go , reuse the artifacts. Now someone would say whats the gurantee such artefact would be preserved by or shared by that author - well if the artefact is important enough be sure 90% chances it would kept by the author and is there any KM system which automatically captures 100% assets ? so its a very good deal without much cost. Now what if author doesn't want to share - that falls against the spirit of blogging and chances are rare - should it be the case you know auhtor also has a boss in the organsiation who can provide more guidance on that.
Secondly preservation of such assets on long term basis - if the asset is good it would live in the organisation for good no of years even if not with original source so theory of natural selection would apply.
Preservation of articles / posts - well they are in the list anyway.
So making KM informal does seem derive lot of value than costly solutions and all with just wikis, blog sites and my sites and search which would exists in collaboration portal anyway. So stop worrying about KM as such, you got it already.
One key technical point to note with mysite customization - feature stapling is solution as its done using self service mode.
Also Ajax rating control can be added to Post pagelayout and rating as column to Post Content Type.
Should any one be still worried about the statistics and really want to go what KM has been traditionally since mid 90's then it is achievable (you know the 'a lot' word which follows deliberated :)) with some design thought before hand which I would post in future but I would like to hear if thats needed , what you think ... should put this on InformationZen as new topic ...
Friday, 29 May 2009
MOSS Service Pack 2 bug - time bomb
It appears that applying service pack 2 to MOSS server will result into interprise license being converted to trail one.
Bellow are the related posts -
http://sharepointservices.wordpress.com/2009/04/28/service-pack-2-is-now-released/
http://support.microsoft.com/kb/971620
http://blogs.msdn.com/sharepoint/archive/2009/05/21/attention-important-information-on-service-pack-2.aspx
Bellow are the related posts -
http://sharepointservices.wordpress.com/2009/04/28/service-pack-2-is-now-released/
http://support.microsoft.com/kb/971620
http://blogs.msdn.com/sharepoint/archive/2009/05/21/attention-important-information-on-service-pack-2.aspx
Tuesday, 19 May 2009
UKAzure Net
Just attended UKAzure Net Inuagural Meeting at MS campus. There was something for architects as well as devs ( and pizzas for everyone :)).
As with any new platform, there is paradigm shift needed to over come 'not hosted here' mind set (off / on premises - new cloud parlance I will say ) and leverage platform and services which does justice to project budget or rather its a good way to get financials aligned with what project/business really needs.
The Vista Squad showed fantastic apps which were developed using Azure platform. I am sure it will be showcased somewhere soonn if not yet so will update later rather than trying draw some incomplete picture. In nutshell there is nice API to code against. I was really happy to see the API, devs back in business :)I hope to pick up on Azure soon and blog at.
http://azureuk.blogspot.com/
I will add sharepoint specific cloud to current blog.
As with any new platform, there is paradigm shift needed to over come 'not hosted here' mind set (off / on premises - new cloud parlance I will say ) and leverage platform and services which does justice to project budget or rather its a good way to get financials aligned with what project/business really needs.
The Vista Squad showed fantastic apps which were developed using Azure platform. I am sure it will be showcased somewhere soonn if not yet so will update later rather than trying draw some incomplete picture. In nutshell there is nice API to code against. I was really happy to see the API, devs back in business :)I hope to pick up on Azure soon and blog at.
http://azureuk.blogspot.com/
I will add sharepoint specific cloud to current blog.
Monday, 11 May 2009
Visual Studio - OS (VISTA/2008) - Admin prev - WSPBuilder
UAC - user access control makes Visual studio to run as standard user even when logged on user has admin previleges which is good.
Same is applicable for Windows 2008, in order to WSPBuilder to deploy solution i.e. create timer job Admin previlege will be required. Now solution is to run VS as Administrator ( right click option ).
Given than entire solution is usually loaded in visual studio of which one of the project is WSPBuilder which packages everything (getting various components as post build event actions of other projects), running VS as admin just for the sake of WSP deploy would defeat the purpose of promoting development as non-admin.
There should be better solution to this, probably configuring 'Deploy' / 'Attach to worker process' options of WSPBuilder to run as Administrator. I will post back if I could get such a solution.
Well I tried creating new process to runas administrator (i.e. the process which WSP add on creates which is wsptoools exe). The downside is its not possible to get it working without disabling IO redirects taking away ability to show the o/p of wsp tool in the output window and also it gives approval popups and shows the shell windows.
There should be way to grab the real admin user token and associate with new process or applying local machine policy. Should post back again once I progress more in that direction in spare time.
Same is applicable for Windows 2008, in order to WSPBuilder to deploy solution i.e. create timer job Admin previlege will be required. Now solution is to run VS as Administrator ( right click option ).
Given than entire solution is usually loaded in visual studio of which one of the project is WSPBuilder which packages everything (getting various components as post build event actions of other projects), running VS as admin just for the sake of WSP deploy would defeat the purpose of promoting development as non-admin.
There should be better solution to this, probably configuring 'Deploy' / 'Attach to worker process' options of WSPBuilder to run as Administrator. I will post back if I could get such a solution.
Well I tried creating new process to runas administrator (i.e. the process which WSP add on creates which is wsptoools exe). The downside is its not possible to get it working without disabling IO redirects taking away ability to show the o/p of wsp tool in the output window and also it gives approval popups and shows the shell windows.
There should be way to grab the real admin user token and associate with new process or applying local machine policy. Should post back again once I progress more in that direction in spare time.
Subscribe to:
Posts (Atom)
