La herramienta de Microsoft por excelencia para el manejo y administración de proyectos a nivel corporativo es Project Server, actualmente versión 2007. Este se integra con SharePoint para ofrecer interesantes beneficios para el almacenamiento de documentos relacionados a proyectos, tareas o entregables (deliveries), y de igual forma para apoyar un poco con la parte de colaboración –permisos, flujos, etc-
Bueno, pues se ha liberado un nuevo Kit de apoyo a la medición de Performance para implementaciones de Project Server 2007, un whitepaper o documento y también un lab.
The white paper answers the following often asked questions:
This white paper contains a description of an actual performance tuning lab for Microsoft Office Project Server 2007. The first chapter (“Running a Project Server 2007 Performance Test Lab”), describes how to run performance tests against a Office Project Server 2007 deployment by using Visual Studio Team System 2008 and a set of community-based tools built for the purpose. The second chapter (“Test Environment”), documents the specifics of the lab environment that was used for the tests we ran for collecting data for this white paper. The third chapter (“Test Results”), describes in detail the test scenarios that were conducted, and it summarizes the data collected for every scenario.
This white paper contains a description of an actual performance tuning lab for Microsoft Office Project Server 2007.
The first chapter (“Running a Project Server 2007 Performance Test Lab”), describes how to run performance tests against a Office Project Server 2007 deployment by using Visual Studio Team System 2008 and a set of community-based tools built for the purpose.
The second chapter (“Test Environment”), documents the specifics of the lab environment that was used for the tests we ran for collecting data for this white paper.
The third chapter (“Test Results”), describes in detail the test scenarios that were conducted, and it summarizes the data collected for every scenario.
The Project Server 2007 Performance Lab Kit contains two Visual Studio solutions/tools to help you test your farm environment for capacity planning purposes: the “EPMTestTools” and the “EPM Stress Test” solution.
Para más información consultar el Blog de Christophe Fiessinger
Muy recomendable!!
Cuando usar una Web Application independiente: (Que es una Web Application, o Aplicación Web desde el punto de vista de SharePoint, para qué me sirve o cuando necesito una?)
Generally speaking, use dedicated Web applications to:
Separate content available to anonymous users from content available to authenticated users.
Isolate users. For example, you can ensure that partners do not have access to intranet content by placing partner sites in a separate Web application.
Enforce permissions. A dedicated Web application provides the opportunity to enforce permissions by policies by using the Policy for Web Application page in Central Administration. For example, you can create a policy to explicitly deny write access to one or more groups of users. Policies for a Web application are enforced regardless of permissions configured on individual sites or documents within the Web application.
Optimize database performance. Applications achieve better performance if they are placed in Web applications with other applications of similar data characteristics. For example, the data characteristics of My Sites typically include a large number of sites that are small in size. In contrast, team sites typically encompass a smaller number of very large sites. By placing these two different types of sites in separate Web applications, the resulting databases are composed of data with similar characteristics, which optimizes database performance.
Optimize manageability. Because creating separate Web applications results in separate sites and databases, you can implement different limits for each site's Recycle Bin, expiration, and size, and negotiate different service-level agreements. For example, you might allow more time to restore sites that are not critical to your business.
Respecto al uso de site Collections: (Que es un Site Collection o Colección de Sitios, desde el punto de vista de SharePoint, para qué me sirve o cuando necesito una?)
A site collection is a set of Web sites that have the same owner and share administration settings. Each site collection contains a top-level Web site and can contain one or more subsites.
The recommended guideline for acceptable performance is to implement fewer than 50,000 site collections per Web application. Scaling out by distributing site collections across multiple database servers provides additional storage capacity and throughput.
Site collections introduce several sharing and isolation opportunities that affect permissions, navigation, and feature deployment.
The following items can be shared within a site collection and cannot be shared across site collections:
Master pages
Page layouts
Images
Site templates
Additionally, permissions and navigation are isolated at the site collection level in the following ways:
Subsites within a site collection can inherit permissions from the top-level site.
Site collections cannot inherit permissions from other site collections.
There is no built-in navigation from one site collection to another.
Finally, Office SharePoint Server 2007 aggregates search results across site collections based on a user’s permissions, regardless of the number of site collections or databases (depending on search scopes).
Finalmente, sobre sites: (Que es un Site o sitio, desde el punto de vista de SharePoint, para que me sirve o cuando necesito uno?)
A site is one or more related Web pages that are hosted inside a site collection.
The guideline for acceptable performance is to implement fewer than 250,000 sites per site collection. You can create a very large total number of Web sites by nesting the subsites. For example, 100 sites, each with 1000 subsites, is 100,000 Web sites. The maximum recommended number of sites and subsites is 125 sites with 2,000 subsites each, for a total of 250,000 sites.
Sites include built-in navigation from one subsite to another within a site collection. There is no built-in navigation from one site collection to another.
As with site collections, separate sites are vulnerable to cross-site scripting attacks from other sites within the domain.
From within each site, you can add user or group accounts to the Owners group for that site.
Ahora, dentro de los sitios almacenamos información y/o documentos. (finalmente, como manejamos y utilizamos la información que almacenamos o subimos a un sitio de SharePoint –que finalmente se almacena en la base de datos previamente definida de SQL Server-).
SharePoint sites are flexible and can help you accomplish many different things. However, to have a useful and successful site or group of sites, you need to be able to focus the sites on some primary objectives. That is, you need to know what you are trying to accomplish with a site before you can design it. For example:
Do you want to communicate with others in your organization by posting bulletins or announcements and gathering feedback?
Do you want to foster team collaboration by giving team members a place to share ideas and work on projects together?
SharePoint sites can assist with both of these objectives. If you have multiple objectives, you might best be served by creating multiple, possibly interrelated, sites. However, you can have multiple objectives for a single site. If you are limited to a single site, organize the site so that users looking for the communication point can find it right away, and users looking to share information and ideas or store documents know where to start.
Review the following objectives. Consider which of these objectives most closely align with your needs for each site you are designing.
Document storage and workflow are key functions of many sites, even sites that are primarily used for communication or collaboration. However, sometimes you might need a dedicated document storage site for your organization. Whether you require a special site for document storage depends on many factors, such as how many documents need to be stored, how many people are contributing documents, who needs to act on the documents, and so on. You will have time to explore how to structure document storage later in the planning process. For more information, see Plan document libraries (Windows SharePoint Services).
Document storage sites or document storage sections of other sites often include the following features:
The ability to check documents in or out, track changes to documents, and keep multiple versions of documents.
The ability to route documents for approval or through specific processes before publishing them to a larger audience.
Note:
Windows SharePoint Services 3.0 includes a workflow capability that you can use to create a custom workflow process to route documents for approval.
The ability to tag documents with metadata, so that documents can be more efficiently sorted and managed.
Para más info: Plan document libraries y Plan site and features
A mi la tecnología, siempre evolucionando, cambiando, adaptándose y ayudándonos a mejorar la forma en como nos comunicamos, trabajamos, y compartimos nuestras vidas.
Te imaginas como será el futuro?
Microsoft Office Labs Vision 2019
<a href="http://video.msn.com/?mkt=en-GB&playlist=videoByUuids:uuids:a517b260-bb6b-48b9-87ac-8e2743a28ec5&showPlaylist=true&from=shared" target="_new" title="Future Vision Montage">Video: Future Vision Montage</a>
Para más información consulta estos sitios:
http://www.psfk.com/2009/03/microsoft-2019.html
http://www.istartedsomething.com/20090228/microsoft-office-labs-vision-2019-video/
Dentro de las capacidades que ofrece Microsoft Office SharePoint Server (MOSS) 2007, hay algo llamado Content Deployment o publicación de contenido. Si recuerdan dentro de aquel diagrama ya conocido de funcionalidades del producto –una como esfera de colores-, tenemos algo que es la Administración de Contenido, lo cuál provee una serie de habilidades para administrar la información que se genera o crea, edita, revisa, autoriza y finalmente se publica.
Piensen en el siguiente escenario: cuando las empresas generan contenido mediante alguna aplicación interna (podría ser, haciendo uso de algún sitio o aplicación web dentro de la Intranet), para que posteriormente se revise, autorice y publique dicha información al sitio público a cierta sección o página web disponible para los usuarios en Internet. Hay empresas que tenían o tienen el producto de Microsoft para crear portales públicos y publicar información, Microsoft Content Management Server (MCMS) 2002 o cualquier otro producto.
En la versión de SharePoint 2007, hubo una integración de las versiones anteriores (2003): SharePoint 2003 –producto para crear Intranets Corporativas- y por otro lado MCMS 2002 –producto para crear Portales Públicos, como por ejemplo: www.empresa.com- como ya comentamos anteriormente;e ahora fueron mejorados e integrados en un solo producto: SharePoint 2007.
Entonces, la funcionalidad de manejar todo el ciclo de vida de la información documental desde la creación (inicio) hasta la publicación del contenido (final), ha sido incorporada a SharePoint 2007 (partiendo de la funcionalidad básica que ofrecía MCMS 2002), y todas las características que están incluidas en un set de capacidades orientadas a esto se llama Web Content Management (WCM)
Existe la información necesaria para saber como funciona y configurar la parte de Replicación de contenido (Content Deployment) una vez aceptada o autorizada donde se creó para posteriormente su publicación en automático hacia dicho portal o sitio con permisos para el público anónimo en cuestión., sin la necesidad de copiar manualmente o hacer el backup y restore de el ambiente de creación al de publicación final. Es muy recomendable también descargar el último SDK de MOSS 2007 para mayor información.
A continuación, del blog de Stefan Gossner, tenemos una serie de mejores práticas sobre Content Deployment que vale la pena tener en cuenta para cuando vayamos a configurar esta funcionalidad en nuestra implementación de MOSS 2007.
En unos días será liberado oficialmente el CU de Abril, el cual se recomienda instalar después de haber aplicado el Service Pack 2 tanto para WSS 3.0 como para MOSS 2007
WSS the uber package http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=968850&kbln=en-us
MOSS the current available packages http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=968859&kbln=en-us
Para más información:
http://blogs.technet.com/stefan_gossner/archive/2009/05/01/the-april-cumulative-update-for-wss-v3-and-moss-2007-has-been-released-yesterday.aspx
http://blogs.msdn.com/joerg_sinemus/archive/2009/05/01/should-i-install-sp2-and-or-april-cu.aspx
Bueno, pues finalmente se llevó a cabo el Segundo Seminario Latinoamericano de SharePoint, ahora en México, el primero se llevó a cabo en Costa Rica.
Después de un par de meses de arduo trabajo, logística, preparación, coordinación de las platicas y temas con los speakers y ver los detalles, estabamos casi listos.
En esta ocasión también contamos con expositores internacionales como por ejemplo Hector Insua, MVP SharePoint Bolivia y Joel Olson, toda una personalidad en el mundo de SharePoint.
Compartiendo algunos post de algunos expositores sobre el evento:
Vladimir Medina
Impresiones de Hector Insua en Mexico
Impresiones de Joel Oleson en Mexico
Hector Insua
2do Simposio - Volviendo de México!
Joel Olson
Seminario Latinoamericano de SharePoint
Where's Waldo I mean Joel- This week is Virginia & DC
Tuvimos aproximadamente 250 registrados y como 200 presenciales!
Para ver mas fotos del evento: https://cid-48d54a134a0e8e5a.skydrive.live.com/browse.aspx/SharePoint/FotosSimposio
Para descargar las presentaciones: http://cid-48d54a134a0e8e5a.skydrive.live.com/browse.aspx/PresentacionesSimposio
Contamos con la asistencia de gente de la Comunidad de Project y esperamos hacer cosas interesantes en un futuro, así como la de SQL Server.
Platiquemos un podo el detalle del evento, como fue…
Llegamos a montar todo aproximadamente a las 6:45 am al hotel antes de que empezara la gente a llegar., y comenzamos.
El registro empezó temprano a las 8:00 am, la gente comenzó a llegar al Hotel Fiesta Americana en Reforma #80 (anuncio en la parte inferior derecha de la vitrina).
Empezó el evento a las 9:00 am, y fue muy grato ver como casi estaba lleno desde el inicio, en el registro les repartimos la agenda del día, una encuesta, publicidad de softwareguru así como de centros de entrenamiento de Microsoft, plumas, y libretas donadas por Microsoft para anotaciones.
Comenzamos, dando la bienvenida al evento platicando que fue organizado por la Comunidad de SharePoint México, también contamos con la participación de los patrocinadores que nos apoyaron con reconocimientos como Microsoft por ejemplo y varios que ya indicamos al inicio del artículo.
Iniciamos entonces con la primera plática introductoria:
Introducción a SharePoint 2007 [Expositores: Luis Du Solier y Haaron González]
Continuamos con la segunda plática:
Desarrollo de WebParts en SharePoint 2007 [Expositor Misael Monterroca]
La tercer plática del día:
Experiencia de usuario en sitios de SharePoint 2007 [Expositores: Rodrigo Díaz, y Mauricio Angulo]
Y para cerrar las pláticas de la mañana que tenían un enfoque más orientado a desarrolladores o developers,
Aplicaciones de negocio basadas en Office 2007 (OBA) y SharePoint 2007 [Expositor: Haaron González]
Terminamos las pláticas de la mañana y continuamos con los temas de los It Pros y Gerentes de TI
Comenzando con la primer plática de la tarde:
Windows Server 2008 y SQL Server 2008 con SharePoint 2007. [Expositores: Hector Insua, Rubén Colomo, el equipo de SQL PASS y Vladimir Medina].
Después tuvimos la ponencia de Joel Olson
10 Steps to Successful SharePoint Deployment [Expositor: Joel Olson, invitado especial desde Estados Unidos]
Luego tuvimos también la participación de Tomas Hernández, experto en SQL y Reporting Services de Microsoft.
Manejo de reportes como apoyo a la toma de decisiones. [Expositor Tomás Hernández]
(a partir de este momento se me terminó el espacio para tomar fotos en mi cámara, en cuanto me pasen mas actualizo el artículo, una disculpa)
Para terminar cerramos con broche de oro, con el Product Marketing Manager de SharePoint de Microsoft México.
Impacto de SharePoint en la prodictividad empresarial. [Expositor: Francisco Hernández]
Queremos agradecer a nuestros principales patrocinadores:
Y a otros patrocinadores que también nos apoyaron.
Walkthrough to Get Your Applications Ready for Windows 7
First Order of Business: Compatibility for Windows Client Applications
The first order of business is application compatibility. Generally, if your Windows client application runs under Windows Vista, you're probably compatible. But to be safe, check out the Windows 7 Application Compatibility Guide. The Guide highlights changes that could affect your application. it also points out differences in performance, reliability, and usability, and provides links to detailed white papers and other developer guidance.
First Order of Business: Compatibility for Web Applications
The browser that ships on Windows 7 is Internet Explorer 8. And users of Windows XP, Windows Vista, Windows Server 2003 or Windows Server 2008 are getting notified through Automatic Update to update to Internet Explorer 8. So if you haven't done so already, be sure both your Web application and your customer-facing Web site are compatible with Internet Explorer 8.
Light up Windows 7
Next, you can light up Windows 7 features in your application. Lighting up your application in Windows 7 gives the users a better experience and shows you are among the development leaders. Many of the features are relatively easy to implement too. Lighting up Windows 7 is about adding to your application, not about rewriting or major revisions. Some of the features can be implemented in just a few lines of code.
Fast Track to Get Started
Before I dive into the main features for line of business applications, you'll want to get:
So you have the tools. Here's a list of what features you can light up: Windows 7 Touch, Taskbar, Libraries, Sensor and Location, PowerShell, and much more.
Fore more info please visit: http://blogs.msdn.com/usisvde/archive/2009/04/25/walkthrough-to-get-your-applications-ready-for-windows-7.aspx
Se ha liberado el Service Pack 2 para Windows SharePoint Services 3.0 y Microsoft Office SharePoint Server (MOSS) 2007
We are happy to announce that Service Pack 2 for Office SharePoint Server 2007 and Windows SharePoint Services 3.0 has been released to the Microsoft Download Center. It includes all the fixes prior to SP2, and also several enhancements to improve server farm performance, availability and stability. Plus, a new stsadm operation has been added to help customers prepare for the upgrade to the next version of SharePoint. We recommend installing this new service pack and to help, I’ve assembled links to the KB articles, downloads, install steps and benefits.
Download Links
Service Pack 2 for Windows SharePoint Services 3.0, x86 & x64 http://www.microsoft.com/downloads/details.aspx?FamilyId=79BADA82-C13F-44C1-BDC1-D0447337051B&displaylang=en
Service Pack 2 for Office SharePoint Server 2007, x86 & x64 http://www.microsoft.com/downloads/details.aspx?FamilyId=B7816D90-5FC6-4347-89B0-A80DEB27A082&displaylang=en
Slipstream Builds For Windows SharePoint Services 3.0
Windows SharePoint Services 3.0 with SP2, x64 http://www.microsoft.com/downloads/details.aspx?FamilyId=9FB41E51-CB03-4B47-B89A-396786492CBA&displaylang=en Windows SharePoint Services 3.0 with SP2, x86 http://www.microsoft.com/downloads/details.aspx?FamilyId=EF93E453-75F1-45DF-8C6F-4565E8549C2A&displaylang=en
Benefits
Customers can be benefited from the following enhancements with Service Pack 2.
Service Pack 2 includes many fixes and enhancements designed to improve performance, availability, and stability in your server farms, including:
Service Pack 2 continues to improve SharePoint interoperability with other products and platforms.
A new preupgradecheck operation is added to stsadm tool. It can be used to scan your server farm to establish whether it is ready for upgrade to SharePoint Products and Technologies "14". It identifies issues that could present obstacles to the upgrade process. It checks for several SharePoint Products and Technologies "14" system requirements, including the presence of Microsoft® Windows Server® 2008 and a 64-bit hardware, and provides feedback and best practice recommendations for your current environment, together with information on how to resolve any issues that the tool discovers.
The full explanation of SP2 benefits can be downloaded here: http://go.microsoft.com/fwlink/?LinkId=148551
Para más información consulta el Blog del Equipo de Producto de SharePoint en http://blogs.msdn.com/sharepoint
Celebremos y agradezcamos lo que la naturaleza nos provee.
Y de paso les comparto algunos links relacionados.
Microsoft’s Top 10 Business Practices for Environmentally Sustainable Data Centers (celebrating Earth Day)
How to Reduce Energy Consumption, Waste, and Costs while Increasing Efficiency and ROI
Innovating to improve the Planet – un interesante sitio altamente recomendable que tiene mucho que ver con el ahorro de energía y utilización de los recursos.
Recordemos uno de los Top 10 points según Gartner más importantes del 2008, referente a las TI
Y claro, no podía faltar, Why SharePoint is Green?
How MOSS Can Help Improve Business Processes
http://www.cmswire.com/cms/enterprise-cms/how-moss-can-help-improve-business-processes-003996.php
SharePoint Solutions: Smart Investments in a Recession
http://www.networkworld.com/community/node/39057
Getting Directions for SharePoint
http://visualstudiomagazine.com/features/article.aspx?editorialsid=2634
CIA, NSA Adopting Web 2.0 Strategies
http://www.informationweek.com/news/internet/web2.0/showArticle.jhtml?articleID=215801627
SmartTools for SharePoint
http://smarttools.codeplex.com/
For the purposes of determining the amount of memory required for the computers running SQL Server 2005, first determine whether the planned deployment is small, medium, or large in terms of memory consumption.
Determine your deployment size by using the following table:
If your deployment parameters are generally less than the listed values, your deployment can be considered small.
If your deployment parameters are approximately equivalent to the listed values, your deployment can be considered medium.
If your deployment parameters are generally greater than the upper limits of most of the listed values, your deployment can be considered large.
Content database size
50 GB
Number of content databases
20
Number of concurrent requests to SQL Server 2005
200
Users
1000
Number of items in regularly accessed list
2000
Number of columns in regularly accessed list
For SQL Server 2005, 4 gigabytes (GB) is the minimum required memory, 8 GB is recommended for medium size deployments, and 16 GB and greater above is recommended for large deployments.
Other factors that can influence your memory needs include:
The use of SQL Server 2005 mirroring.
The frequent use of files larger than 15 megabytes (MB).
Para más información: http://technet.microsoft.com/en-us/library/cc298578.aspx, http://technet.microsoft.com/en-us/library/cc298801.aspx
Overview of Microsoft Windows SharePoint Services
Using Windows SharePoint Services to Manage Visio Drawings
Accessing Documents Stored on a SharePoint Site from Visio
Viewing a SharePoint Task List as a Visio PivotDiagram
Viewing a SharePoint Task List as a Visio Flow Diagram
Viewing a SharePoint Calendar List as a Visio Diagram
Techniques for Sharing Visio Data from a SharePoint Site
http://msdn.microsoft.com/en-us/library/bb229690.aspx#Visio2007IntegratingSharePoint_TechniquesforSharingVisioDatawithSharePoint
Un interesante caso de estudio de una empresa que implementó MOSS como solución de colaboración y almacaneje de documento a gran escala, muy interesante (http://technet.microsoft.com/en-us/library/cc262067(TechNet.10).aspx)
This paper presents the key decision points, architecture design and definition, and test criteria and results from a scalability and performance test conducted at the Microsoft Partner Solutions Center (MPSC) in Redmond, Washington. It is intended to provide strategic information about designing a high-volume, high-availability enterprise solution that can easily grow.
You can download this paper to read and print it in three formats:
Microsoft Office Word 2007 (.docx) (http://go.microsoft.com/fwlink/?LinkId=120881&clcid=0x409)
Word 2003 (.doc) (http://go.microsoft.com/fwlink/?LinkID=120890&clcid=0x409)
PDF (http://go.microsoft.com/fwlink/?LinkId=120891&clcid=0x409)
Ya viene el Service Pack 2 de SharePoint 2007, programado para el 28 de Abril, más información aquí (Service Pack 2 for the 2007 Microsoft Office System due to ship April 28th)
Algunas noticias sobre la nueva versión de SharePoint –> SharePoint 14 ahora SharePoint 2010, más información aquí (http://blogs.msdn.com/sharepoint/archive/2009/04/14/microsoft-sharepoint-14-is-now-microsoft-sharepoint-2010.aspx)
Estimados amigos, ya tenemos programado el Segundo Seminario Latinoamericano de SharePoint, ahora en México. El año pasado se llevó a cabo el primer seminario como todo un éxito en Costa Rica.
Ahora estaremos llevando a cabo el segundo evento de esta interesante iniciativa en la Ciudad de Mexico., gracias a la Comunidad de SharePoint en México.
Datos importantes:
Fecha: 23 de Abril (Jueves)
Lugar: Hotel Fiesta Americana (Salón Sonora – 2o Piso), Reforma #80 Mexico Df.
Cuota de recuperación: 250 pesos mexicanos (se paga en efectivo al llegar al lugar)
Url de registro: http://msevents.microsoft.com/CUI/EventDetail.aspx?EventID=1032413075&Culture=es-MX
Conoce los temas de plática y expositores:
Para mayor información: ldusolier@sharepoint.com.mx o ldusolier@live.com.mx
Ya es una noticia muy publicada y mencionada, pero no dejaré paras la oportunidad. A partir del 1o de Abril, Microsoft ofrece la opción de descargar SharePoint Designer 2007, sin costo adicional. SharePoint Designer 2007 es la siguiente versión para los que conozcan o hayan trabajado con Front Page 2003.
Interesante estrategia para permitirle a los usuarios y clientes sacarle más provecho a las herramientas y que usen los productos.
El sitio oficial de la información sobre sharePoint Designer: http://www.microsoft.com/spd
Aquí tenemos el mensaje del equipo de producto, directamente desde su blog.
SharePoint Designer available as a free download
Una sección de preguntas y respuestas para entender mejor esto.
Q&A on SharePoint Designer 2007 Licensing Changes
Una carta dirigida a los clientes sobre SharePoint Designer 2007
Letter to SharePoint Designer Customers
Entrevista en video a Tom Rizzo. Sr. Director of Product Management for sharePoint
Descárgalo Aqui, y comienza a generar mas funcionalidad en tu implementación de SharePoint 2007. Por ejemplo ya sabes como crear flujos de trabajo usando sharePoint Designer sin código?, o como agregar el Data View WebPart mediante el uso de SharePoint Designer?, qué es el Data View Web Part y cómo me puede servir?
Si quieres conocer más de SharePoint Designer y como usarlo para generar mayor valor a tu implementación de SharePoint 2007, te recomiendo descargues (también gratuito) el Office sharePoint Designer 2007 Training Kit (versión standalone o versión para Portal).
Office SharePoint Server 2007 Training (a continuación un poco de información en inglés).
Microsoft Office SharePoint Server 2007 offers a rich set of features that allow you to build and maintain powerful intranets and Internets for your company. You can manage workflow, maintain version control, connect to business intelligence applications, track key performance indicators for your business, add blogs and wikis to improve knowledge transfer and enhance collaboration, and more.
The Microsoft Office SharePoint Designer 2007 Training (Standalone Edition) leads the learner step-by-step through SharePoint Designer features using easy to understand videos. Built with the SharePoint platform integration in mind and engineered to work efficiently with Microsoft Windows SharePoint Services and Microsoft Office SharePoint Server 2007, SharePoint Designer will help you customize your SharePoint sites to make it an even more powerful tool for productivity. SharePoint Designer is the ideal tool for Information Workers to build composite applications, design and customize workflows and tailor SharePoint sites to their branding needs.
If you are a server administrator and want to install the Portal Edition to your Office SharePoint Server site, click here. The Portal Edition allows you to add or remove content to help your users learn about Office SharePoint Designer.
En caso de que descarguen la versión standalone una vez que entren podrán ver un directorio de videos tutoriales muy interesantes como podrán apreciar a continuación:
Los nuevos planes de búsqueda empresarial con Fast, más información en el blog de EmpresaProductiva.com
SharePoint y PerformancePoint Server, un artículo interecente de igual forma en el blog de EmpresaProductiva.com
Por último, las 3 grandes promociones para clientes que tienen SharePoint Enterprice Cal o Performance Point Server en el blog de EmpresaProductiva.com
IIS not serving pages - Page cannot be displayed
http://blogs.msdn.com/sudeepg/archive/2007/09/11/iis-not-serving-pages-page-cannot-be-displayed.aspx
Designing pages for quicker downloads
http://technet.microsoft.com/en-us/library/cc263099.aspx
SharePoint Warm-up Scripts
http://sharepoint.microsoft.com/blogs/fromthefield/Lists/Posts/Post.aspx?ID=56
Other Browsers
http://sharepoint.microsoft.com/blogs/fromthefield/Lists/Posts/Post.aspx?ID=30
Limiting the Page Payload with IIS HTTP Compression
http://andrewconnell.com/blog/archive/2008/11/15/Limiting-the-Page-Payload-with-IIS-HTTP-Compression.aspx
The Kid, nos comparte un excelente post acerca de tips y recomendaciones de como hacer un debugging en SharePoint, aquí les dejo el artículo.
http://blog.thekid.me.uk/archive/2007/07/25/debugging-tips-for-sharepoint-and-wss-exceptions.aspx
Que es Software as a Service, que es Software más Servicios, y cual es la diferencia. Un reciente Post en el Blog de Empresa Productiva nos comparte un video muy atractivo que nos explica en unos cuantos minutos el potencial de estos conceptos, y la visión que tiene Microsoft, por lo que les invito a que visiten este post.
Que te parece?
Alguna vez han tenido que hacer troubleshooting con SharePoint?, cuando están teniendo algún problema, empiezan a revisar por ejemplo el Log de Application dentro del Event Viewer, o los ULS (que cliente usan para revisar los ULS?), e identifican Evend ID’s pero no saben a qué se refiere o necesitan tener más información al respecto.
Conozcamos un poco acerca del modelo de salud y correcto funcionamiento de Windows SharePoint Services (WSS) 3.0 y Microsoft Office SharePoint Server (MOSS) 2007, así como los eventos relacionados.
Windows SharePoint Services 3.0 health model
Windows SharePoint Services 3.0 farm (Health model)
A server farm typically consists of a database server running either Microsoft SQL Server 2005 or Microsoft SQL Server 2000 SP3a or later, and one or more servers running Internet Information Services (IIS) and Windows SharePoint Services 3.0. In this configuration, the front-end servers are configured as Web servers. The Web server role provides Web content and services such as search.
Windows SharePoint Services 3.0 Web application (Health model)
A Web application is comprised of an Internet Information Services (IIS) site that has a unique application pool. When you create a new Web application, you also create a new database and define the authentication method used to connect to the database.
Events and error reference (Office SharePoint Server)
Active Directory events (Office SharePoint Server)
Baseline server events (Office SharePoint Server)
Converter log errors (Office SharePoint Server)
Excel Services error messages (Office SharePoint Server)
Setup and post-setup configuration errors (Office SharePoint Server)
Services events used in Office SharePoint Server 2007
Virus scanner events (Office SharePoint Server)
Web site and SQL Server events (Office SharePoint Server)
Microsoft ha lanzado el sitio www.EmpresaDosCero.com , un sitio con videos divertidos donde usted puede aprender “en lenguaje simple” y a través del marketing digital, la magia de la Web2.0 y cómo puede ser aplicado a la vida de los empleados en el trabajo. Esto es lo que llamamos La Empresa2.0. Les sugiero que vean los videos y se los reenvíen a sus compañeros de trabajo, clientes, Socios, amigos y familiares. Les garantizo que ellos cambiarán su percepción sobre lo que realmente significa la productividad en los negocios del siglo 21.
Referencia: http://www.empresaproductiva.com/archive/2009/02/11/iw-en-el-siglo-21-web2-0.aspx
SharePoint Diagnostics (SPDiag) Tool v1.0 for SharePoint Products and Technologies
The real power of Office SharePoint Server 2007 and Windows SharePoint Services 3.0 is that they can be endlessly customized to meet a wide variety of business needs. The Protean nature of SharePoint is at once its most powerful feature and its most formidable; the complexity of your SharePoint environment can increase by orders of magnitude when you begin to shape it to suit your needs. This complexity can make troubleshooting SharePoint issues a daunting task, as many different data points from different sources must be correlated and analyzed.
What I like about ForeFront Security for SharePoint
ForeFront Security for SharePoint has some additional functionalities that most administrators are interested in having in their farm management tool-box. Specifically, this product advertising to have the following features…
Integrating External Document Repositories with SharePoint Server 2007
This article presents a complete architecture and sample code for integrating an external repository with Office SharePoint Server 2007. The solution enables you to view and manage documents in an external repository through the Office SharePoint Server 2007 user interface (UI). While some repository vendors provide Web parts that enable document browsing and viewing, this solution goes far beyond these basic capabilities to provide a complete integration of the repository. Using this architecture, end users can create libraries in Office SharePoint Server 2007 that include documents from an external repository without copying those documents into Office SharePoint Server 2007. Users are also able to maintain the documents by using Office SharePoint Server 2007 capabilities such as check-in, check-out, edit properties, version history, and document upload and download. The solution also enables complete integration of external documents with SharePoint workflows, list columns, task lists, and other libraries.
SPDisposeCheck v1.3.1 is released
SPDisposeCheck is a tool to help SharePoint Developers follow memory management best practices when using the SharePoint API with IDisposable objects including SPSite and SPWeb. This tool is not supported by Microsoft and is recommended to be used on Developer workstations and not on production SharePoint Server installations.
Visio 2007 shapes for MOSS 2007 and WSS 3.0.
Each of the libraries below contains all the shapes that are required to produce informative and professional results quickly and simply. These sets, can be used by dedicated professionals, casual designers or novice users to deliver impressive domain specific drawings and diagrams.
Common error situation when using backup/restore to transfer a database to a new farm on MOSS 2007
In the past I have seen the following problem a couple of times: a customer creates a backup of a content database on one server farm (e.g. using STSADM -o backup or a DB backup in SQL) and restores the backup on a different farm and attaches the content database to a web application.
In all previous years, the only conclusion regarding technology was that there was no universal platform for designing good intranets. Winners typically used an extraordinarily wide diversity of implementation packages.
Although this conclusion continues to hold this year, it is less pronounced.
Among the winning intranets, many are built on a single intranet platform that integrates most of the supporting features they need — including a content management system (CMS) and search. Some winners supplement their main platform with a few selected tools for specialized purposes — mainly Web analytics. If we were to hazard a prediction, it would be that traffic statistics, search log analysis, and other analytics tools will be substantially beefed up and integrated in future releases of the main intranet software platforms.
In total, the 10 winners were built on 26 different products — substantially fewer than the 41 used in 2008 or the 49 used in 2007. Most impressively, fully half of the winning intranets used SharePoint, especially the recent MOSS platform (Microsoft Office SharePoint Server 2007). As the following chart shows, SharePoint use has grown dramatically in recent years. This is particularly impressive given that, from 2003–2006, the winning intranets didn't use earlier versions of SharePoint at all.
Microsoft SharePoint has seen substantially increased use among well-designed intranets in recent years. (In 2007, Microsoft's own intranet was a winner, and they obviously used their own software, so the 2007 dot should be a notch lower if you consider only third-party projects.)
For more info:
http://www.useit.com/alertbox/intranet_design.html
http://www.nngroup.com/reports/intranet/design/
http://blogs.msdn.com/sharepointdesigner/archive/2008/11/14/spd-licensing-101.aspx
Test Drive
http://www.runaware.com/microsoft/en-us/2007office/td?action=launch_wizard