고객사례 : Windows Server 2008과 MOSS 2007 기반의 AMD Developer Central


세계 2위의 CPU 생산 업체인 AMD에서 개발자 대상으로 기술 리소스를 제공하는 AMD Developer Central 사이트가 Windows Server 2008과 MOSS 2007 기반으로 마이그레이션 되었습니다; [사이트 방문 하기]

본 사례에 대한 보다 자세한 사항은 다음을 참조해 주십시오.

AMD Finds Deploying AMD Developer Central Internet Site with Office SharePoint Server 2007 on Windows Server 2008 is Faster and Easier to Manage

When AMD evaluated the benefits of SharePoint to manage their Internet site, they thought it made both technical and business sense.  In their evaluation they determined that Windows Server 2008 would better take advantage of their goals for built in security, performance, manageability and reliability.
They determined that the first platform to use their new business tool was their Internet developer portal designed to provide resources for developers taking advantage of their AMD processors in their code and development projects.  What better way to showcase their new
Quad-Core AMD OpteronTM processors  than building a platform using Windows Server 2008, the most secure and reliable Windows Server and with the flexibility and manageability of Office SharePoint Server 2007 web content management features.

Background
The previous design took about 1 year to complete designed with custom Java Server pages and required authors go through a process which took up to 8 hours and manual processes to make updates and changes.  The existing deployment handles 40,000 named accounts with hundreds of thousands of anonymous users.
The redesign and redeployment on Windows Server 2008 with SharePoint Server Enterprise Edition took 7 weeks.  AMD partnered with B&R consulting, a SharePoint solutions integration company that specializes in SharePoint Server deployments experienced in Windows Server 2008 and made up of top SharePoint MVPs focused on infrastructure.  In an interview with the deployment team I gathered this feedback…

Deployment Experience
Bob Fox (SharePoint MVP), Chris Reagan, Josh Carlisle, all of B & R Solutions, shared their Windows Server 2008 experience.  Bob explained that the biggest thing he noticed was the performance.  He explained, “The IISresets were quicker, the administrative interfaces loaded very quickly, and the SharePoint Server pages themselves seemed very snappy.  The event viewer had what I was looking for and the new customized views made it very easy to troubleshoot.”
Chris explained that usually one would expect to run into issues running pre release code.  He was pleasantly surprised he didn’t run into any.  He said “We had no issues.  Ramp up on the IIS 7 user interface took some getting used to, but now that I’m using it, it’s easier to manage.  Bindings and headers are the same thing, that’s one thing that stumped me for a minute.”
As far as the SharePoint deployment went they both explained it was very familiar, getting the necessary prerequisites was very straight forward and the installation if anything was easier.  They found it was the Windows Server 2008 experience itself was familiar, yet it now had more options and seemed to be less clicks to get the views and administrative interfaces, such as the improved event viewer, to do what they wanted.
As a result of the project going so quickly, they were ready for production before the servers were.  As a result they ended up reusing some reallocated servers for the deployment.  All were very surprised what they were able to get out of existing hardware that was “lying around.”  Windows Server 2008 comparatively seemed to run quicker on the same hardware.  This was a very pleasant surprise.

 

Comments (0)