Para conocer los security updates o actualizaciones de seguridad mayores o genéricos puedes consultarlos en TechNet (http://technet.microsoft.com/en-us/library/cc263467.aspx#section2):
Major updates for Office SharePoint Server 2007 | Name | Description and Microsoft.SharePoint.portal.dll version number |
| Office SharePoint Server 2007 | The RTM version of Office SharePoint Server. Microsoft.SharePoint.portal.dll version number: 12.0. 4518.1016 |
| October public update (2007) | For more information about the software updates in the October public update, see Microsoft Knowledge Base article 937832: Description of the security update for SharePoint Server 2007: October 9, 2007 (http://go.microsoft.com/fwlink/?LinkId=102083&clcid=0x409). Microsoft.SharePoint.portal.dll version number: 12.0. 6036.5000 |
| Service Pack 1 | Service Pack 1 (SP1) includes a number of hot fixes across Office SharePoint Server 2007 and Windows SharePoint Services 3.0, new Stsadm commands for repartitioning databases and renaming host site collections, and updates to product documentation that address performance and capacity planning concerns. For more information about what this service pack contains, read the introductory white paper, Service Pack 1 for Windows SharePoint Services 3.0 and Microsoft Office SharePoint Server 2007 (http://go.microsoft.com/fwlink/?LinkId=105704&clcid=0x409). Microsoft.SharePoint.portal.dll version number: 12.0.6219.1000 |
| Post Service Pack 1 rollup | This rollup provides fixes that were made after the code was locked for SP1. For more information, see the following KB article, Description of the SharePoint Server 2007 post-2007 Microsoft Office servers Service Pack 1 hotfix package: July 23, 2008 (http://support.microsoft.com/kb/955586). Microsoft.SharePoint.portal.dll version number: 12.0. 6300.5000 |
| Infrastructure Update (IU) | This update fixes issues in Office SharePoint Server 2007 and adds new Enterprise Search features to SharePoint Server 2007. For more information, see Description of the Microsoft Office Servers Infrastructure Update (http://go.microsoft.com/fwlink/?LinkID=121886&clcid=0x419) and Issues that are fixed in Microsoft Office Servers by the Microsoft Office Servers Infrastructure Update (http://go.microsoft.com/fwlink/?LinkId=133369&clcid=0x409). Microsoft.SharePoint.portal.dll version number: 12.0.6320.5000 |
| August Cumulative Update | For more information about this update, refer to the following KB articles, Cumulative update packages for the 2007 Microsoft Office core suite applications and for 2007 Microsoft Office servers (http://go.microsoft.com/fwlink/?LinkId=133370&clcid=0x409) and Description of the SharePoint Server 2007 hotfix package (Coreserver.msp): August 26, 2008 (http://go.microsoft.com/fwlink/?LinkId=133371&clcid=0x409). Microsoft.SharePoint.portal.dll version number: 12.0.6327.5000 |
| October Cumulative Update | To learn about the issues that are fixed in this update, see Description of the SharePoint Server 2007 hotfix package (Coreserver.msp): October 28, 2008 (http://go.microsoft.com/fwlink/?LinkId=133374&clcid=0x409), Description of the SharePoint Server 2007 hotfix package (Coreservermui.msp): October 28, 2008 (http://go.microsoft.com/fwlink/?LinkId=133376&clcid=0x409), and Description of the SharePoint Server 2007 hotfix package (Dlc.msp): October 28, 2008 (http://go.microsoft.com/fwlink/?LinkId=135715&clcid=0x409). Microsoft.SharePoint.portal.dll version number: 12.0.6331.5000 |
| December Cumulative Update | This update contains hotfixes for all the Office SharePoint Server 2007 issues that have been fixed since the release of Office SharePoint Server 2007. For more information, see Description of the SharePoint Server 2007 cumulative update package (MOSS server-package): December 16, 2008 (http://go.microsoft.com/fwlink/?LinkId=139508). Microsoft.SharePoint.portal.dll version number: 12.0.6335.5000 This update contains: |
| February Cumulative Update | To learn about the issues that are resolved in this update see Description of the Microsoft Office SharePoint Server 2007 cumulative update package: February 24, 2009 (http://go.microsoft.com/fwlink/?LinkId=146627&clcid=0x409) Microsoft.SharePoint.portal.dll version number: 12.0.6341.5002 |
| Service Pack 2 | Service Pack 2 (SP2) provides full support for Windows Server 2008 and Internet Information Services (IIS) 7, extended browser support, new operations and properties for the Stsadm command line tool, improved functionality for existing features, and hot fixes for known issues. Service Pack 2 includes SP1 and all the updates released up to this service pack. For a description of SP2, see Description of 2007 Microsoft Office servers Service Pack 2 (SP2) and of 2007 Microsoft Office servers Language Pack Service Pack 2 (SP2)(http://go.microsoft.com/fwlink/?LinkID=149890) Microsoft.SharePoint.portal.dll version number: 12.0.6420.1000 |
| April Cumulative Update | The April cumulative update (CU) provides very important fixes for Stsadm, in particular the mergecontentdbs operation. For more information, see Description of the Windows SharePoint Services 3.0 Cumulative Update Server Hotfix Package (Sts.msp): April 28, 2009. For a description of this update, see Description of the SharePoint Server 2007 Cumulative Update Server Hotfix Package (MOSS server-package): April 30, 2009 (http://go.microsoft.com/fwlink/?LinkID=149891). Microsoft.SharePoint.portal.dll version number: 12.0.6504.5000 |
Y a continuación comparto algunas variaciones:
12.0.0.6020 – WSS3.0/MOSS2007 RTM + KB936867 + KB932091
12.0.0.6421 – WSS3.0/MOSS2007 SP2 + HotFix for WSS (KB941653)
Si alguien conoce otras variaciones con gusto puede compartirlas.
Gracias a Jhonatan Figueroa por compartir las pantallas de error.
A continuación información del Hot Fix para solucionar este error (http://support.microsoft.com/kb/938888).
This article describes the 2007 Microsoft Office issue that is fixed in the 2007 Office hotfix package that is dated June 17, 2007.
This article describes the following items about the hotfix package:
- The issues that the hotfix package fixes.
- The prerequisites for installing the hotfix package.
- Whether you must restart the computer after you install the hotfix package.
- Whether the hotfix package is replaced by any other hotfix package.
- Whether you must make any registry changes.
- The files that the hotfix package contains.
Issues that the hotfix package fixes
This hotfix fixes the following issue:
929360 (http://support.microsoft.com/kb/929360/ ) You cannot create a new document or check out an existing document in a Windows SharePoint Services 3.0 document library when you have multiple versions of Office installed
This hotfix package fixes the following issue that was not previously documented in a Microsoft Knowledge Base article:
- Internet Explorer crashes (stops responding) when you try to open an Office document in a SharePoint document library
You connect to a document library in a Microsoft Office SharePoint Server 2007 site or in a Microsoft Windows SharePoint Services 3.0 site by using Windows Internet Explorer 7 or Microsoft Internet Explorer 6. However, when you try to open a Microsoft Office document, Internet Explorer crashes (stops responding).
This problem occurs if the following conditions are true, in the order in which they are presented: - You install a Microsoft Office 2003 product on the computer.
- You install one or more 2007 Office system programs on the computer.
- You repair or update the installation of an Office 2003 product.
In this scenario, the older version of the Name.dll file becomes the registered version. When the Owssupp.dll file is used, it tries to use functionality that is not available. This condition causes Internet Explorer to crash (stop responding).
Hotfix information
The following file is available for download from the Microsoft Download Center:
Collapse this imageExpand this image
Download the 2007 Office hotfix package (KB938888) package now.
stsadm can inadvertently delete a root site collection if erroneous URL path used
ERROR:
No content databases are available for this operation. Create a content database , and then try the operation again. To create a content database, click "Content databases" on the Application Management page, select the Web application to use, and then click "Add a content database".
Going to the now dead root site you get:
404 FILE NOT FOUND
http://support.microsoft.com/default.aspx/kb/968474
Microsoft Office SharePoint Server 2007 unsupported scenarios using stsadm -o export /import of subsites
Microsoft Office SharePoint Server 2007 does not support stsadm -o import of subsites based on the publishing feature as a root site collection as this subsite would have orphaned information stored in the root site the subsite was exported from.
http://support.microsoft.com/kb/968483
Mensaje de error cuando intenta tener acceso a un servidor local mediante su nombre COMPLETO o su alias CNAME después de instalar Windows Server 2003 Service Pack 1: "acceso denegado " o " ningún proveedor de red acepta la ruta de acceso de red determinado"
http://support.microsoft.com/kb/926642/es
Error message when you try to access a server locally by using its FQDN or its CNAME alias after you install Windows Server 2003 Service Pack 1: "Access denied" or "No network provider accepted the given network path"
http://support.microsoft.com/kb/926642
Para los que ya han aplicado el SP2 de SharePoint 2007 (WSS/MOSS), existe un known issue y lo que hace es cambiar la licencia del producto a una de Trail Version por unos cuantos meses. Para más información: Service Pack 2 expiration date issue
El workaround era cambiarla de nuevo manualmente o esperar a que se liberera el Update para que ese cambio se hiciera en automático, finalmente ha sido liberado.
Información importante del Blog del equipo de producto de SharePoint:
The update is applicable to all of the products that this issue affected (see the list in the KB linked below).
Installation instructions and download links for x86 and x64 are available in this KB: http://support.microsoft.com/kb/971620
The direct download link for x86 is: http://download.microsoft.com/download/2/F/5/2F51AB71-1325-49D2-9CB9-18DEC4780E99/office2007-kb971620-fullfile-x86-glb.exe
And for x64: http://download.microsoft.com/download/5/B/B/5BBD34A9-C528-42B0-8A5F-9A8997B25C32/office2007-kb971620-fullfile-x64-glb.exe
We will be updating the existing Service Pack 2 download package with a new package that includes this fix within the next 4-6 weeks.
Thank you for your patience.
FAQ
Q: How can I tell if the update has worked?
A: The License Type text on the Convert License Type page in Central Administration no longer contains the word “trial”.
Q: I applied the update and now I can’t enter anything in the Convert License Type page in Central Administration, is this right?
A: This is expected behavior if your license type is “Office SharePoint Server with Enterprise Client Access License”.
Para el artículo completo favor de consultar: Service Pack 2 Update
A continuacion la invitación, te esperamos.

http://mssharepoint.multiply.com (Pagina de la Comunidad)
http://sharepointmx.mvps.org (Blogs)
http://www.sharepoint.com.mx (PodCasts)
Los Administradores de SharePoint sabes que aparte de la Administración que podemos hacer del producto por medio de la interfaz gráfica o del sitio buen de Administración llamado Administración Central o Central Administration, tenemos también la opción de usar un comando, llamado stsadm.
Por ahí está también la versión gráfica del comando…
Pero tenemos toda la referencia del mismo en este artículo en TechNet, que les recomiendo revisar.
http://technet.microsoft.com/en-us/library/cc263384.aspx
Recién se liberó un nuevo diagrama dinpamico que le ayuda a los administradores de SharePoint a identificar y encontrar el comando que requiera según la actividad que desee efectuar, esta muy simpático.
Cuentan con un diagrama inicial, y algunos filtros para buscar, dentro de la caja de texto ingresar la palabra que les interesa relacionada a la acción, por ejemplo create, para crear un site.
Y en automático el diagrama se modifica para presentar las opciones posibles referentes a la acción que se está buscando realizar.
Este simpático nuevo aditamento de TechNet lo pueden encontrar en esta dirección:
http://technet.microsoft.com/en-us/office/sharepointserver/cc948709.aspx
Les recomiendo de igual forma ver los mapas que mindsharp pone disponibles sobre el stsadm y varias otras cosas interesantes sobre SharePoint.
Por último, la recomendación del uso del pipe o “|”.
Esa me gusta mucho, ejemplo, si quiero crear u sitio pero no recuerdo como se llama la operación exactamente, podría escribir lo siguiente:
stsadm | find “create”
Y a continuación me regresaría en la línea de comando una lista únicamente de los operadores que tienen la palabra create, como por ejemplo createsite.
Si quieren conocer más información sobre esta opción, les invito a que consulten el artículo a travéz de los amigos PFEs de US (From The Field).
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:
- Key metrics for performance
- Test scenarios (open, save, publish projects, submit timesheet, submit task updates, etc...)
- Test results for:
- Access PWA Home Page
- Submit Task Updates, Approve Task Updates
- Submit Timesheets, Approve Timesheets
- Etc...
- Microsoft Office Project Server 2007 Performance Testing (white paper)
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?)
Site collections
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.
Capacity
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.
Sharing and isolation
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?)
Sites
A site is one or more related Web pages that are hosted inside a site collection.
Capacity
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.
Sharing and isolation
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.
Configurable elements
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-).
Identify primary objectives for sites
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
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
Video: Future Vision Montage
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.
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.
Aqui tomandonos una foto antes de que empiece el evento, Joel Olson y un servidor Luis Du Solier |
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).

Vladimir apoyando en el registro |
Yola apoyando en el registro y recibiendo gente |
Hector ayudando en el registro |
Todos apoyando desde temprano. |
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]
Luis Du Solier dando la Introducción a SharePoint 2007 |
Haaron González dando una introducción al desarrollo sobre SharePoint 2007 |
|
Continuamos con la segunda plática:
Desarrollo de WebParts en SharePoint 2007 [Expositor Misael Monterroca]
Misael dando la sesión de desarrollo en SharePoint 2007 |
Misa haciendo su tremendo demo |
|
|
La tercer plática del día:
Experiencia de usuario en sitios de SharePoint 2007 [Expositores: Rodrigo Díaz, y Mauricio Angulo]
El buen hablando sobre Silverlight |
Aqui Roky compartiéndonos un demo muy interesante sobre Silverlight en un sitio de SharePoint 2007 |
Mauricio platicando un poco sobre User Experience |
Mauricio controlanto totalmente la audiencia! |
|
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]
Haaron explicando el por qué de las Aplicaciones basadas en Office (OBA) o como pueden ayudar a las empresas. |
Al término de esta plática comenzamos con los premios, en esta foto estamos obsequiando un teléfono Windows Mobile, patrocinado por Microsoft. |
|
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].
Hector abriendo la sesión platicandonos sobre Windows Server 2008 |
Rubén apoyando con el tema de Windows Server 2008 y virtualización. |
Nuestros amigos de SQL Pass abordando el tema de ventajas y beneficios con SQL Server 2008 |
Vladimir platicandonos un poco acerca de los beneficios de SQL Server 2008 y SharePoint 2007 |
Aqui regalamos otro teléfono Windows Mobile, felicidades! |
|
|
Después tuvimos la ponencia de Joel Olson
10 Steps to Successful SharePoint Deployment [Expositor: Joel Olson, invitado especial desde Estados Unidos]
Joel iniciando tu plática |
Teniendo una dinámica con la audiencia |
Platicando algunas cosas interesnates sobre que considerar en proyectos exitosos |
Al final nos tomamos una foto (de izquierda a derecha): Joel Olson, Yolanda Lopez, Luis Du Solier, Haaron González, Hector Insua, Vladimir Medina –Es una foto para recordar-. |
|
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.
Y sobre todo agradecer a Arisay Mackey por habernos ayudado en algo muy importante, en haber generado la invitación del Simposio, muchas gracias!
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.
- Performance and Availability Improvements
Service Pack 2 includes many fixes and enhancements designed to improve performance, availability, and stability in your server farms, including:
- New Timer job automatically rebuilds content database index to improve database performance.
- When a content database is marked as read-only, the user interface will be modified so users cannot perform tasks that require writing to the database.
- Performance enhancement across nearly all the components.
- Improved Interoperability
Service Pack 2 continues to improve SharePoint interoperability with other products and platforms.
- Broader support of browsers
Internet Explorer 8 is added into Level 1 browser support.
FireFox 2.0/3.0 is added into Level 2 browser support. - Provide improved client integration user experience with Form Based Authentication. Now the client application can store user credentials instead of asking for them every time. For more technical details please refer to the updated articles on TechNet.
Configure forms-based authentication (Office SharePoint Server
http://technet.microsoft.com/en-us/library/cc262201.aspx
Configure forms-based authentication (Windows SharePoint Services)
http://technet.microsoft.com/en-us/library/cc288043.aspx
- Getting Ready for SharePoint Server 2010
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
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:
More Posts
Next page »