Anith Gopal

This is a temporary post that was not deleted. Please delete this manually.

  As I mentioned in a previous blog post, where I describe how to install the Zune software on Windows Server 2008, the Windows Phone 7 tools do not install on Windows Server 2008 as easily as on other “workstation” versions of Windows (Windows Vista, Windows 7). Once again, this is perfectly understandable since a server version of Windows is not aimed for application development purposes. However, since I installed Windows Server 2008 on my machine for training purposes, and since I don’t have enough computers at home to have one dedicated for this server version of Windows, I searched for a way to force the installation of these WP7 tools

After installing Windows Server 2008 on my machine (for training purposes), I tried to install the Zune software but it told me that this version of Windows is not supported. Actually, this is quiet logical, since such a Windows version is not aimed for entertainment purposes, I found a way to force the installation of the Zune software on Windows Server 2008

This is a temporary post that was not deleted. Please delete this manually

CRM 2011 RC now allows us to specify service accounts during the setup process.  You can specify the service account for the Application Service, Deployment Web Service, Sandbox Service and Asynchronous Service to run as.  In a single server environment, you can just use NETWORK SERVICES for the installation.  However if you are installing CRM in an enterprise multi server environment, the recommendation is to have a specify service accounts each of the services.  For best practices and instructions on how to install CRM in a multi server environment, please refer to the CRM 2011 Implementation Guide . I would like to share our setup experience with the community just in case you run into a similar situation.  During our setup, we didn’t receive all green checks from the System Check wizard.  We had several warnings related the Microsoft Dynamics CRM Server User Input so I dig into the warnings with Michael from the Product Group.  Thanks for his help, he resolved for us.  Problem The reason that we got the warnings is because the admin is using the installing user account for the service accounts.  What happens is when the first organization is created, the installing user is created as the first user in the organization.  Since there is a user in the organization with the same credential as the service accounts for the asynchronous service, application service and the sandbox service, all the sudden the “SYSTEM” user is now subject to the same constraints as an actual user which means that the user must be enabled, need a user role and etc…, otherwise the system will stop functioning.  A lot of bad things could happen.  For example, some grids in CRM are populated with data that is retrieved as SYSTEM, when data is retrieved as SYSTEM, it is retrieve in GMT format. However if the Application Service is running under a service account which is also an user in CRM, when retrieving data the data will return with the users time zone setting instead of GMT.  There are more bad things could happen… Solution If it’s for a non-production environment, you may ignore the warnings and proceed with your installation.  But for production environment, this will cause problems later on.  The recommendation is to use a different service account for each of those services.  However if you preferred not to manage extra service accounts, you may use a same service account for Application Service, Deployment Web Service, Sandbox Processing Service, Asynchronous Process Service as long as the installing account is different than the service account for the services.  If you decided to use a different service account for each of the services, just create the service accounts in your AD.

Predicting resource requirements for a new business application, especially one that is customer-facing is a tricky task. It’s hard to know if you have the new Facebook or your hands.

This is a temporary post that was not deleted. Please delete this manually. (38dc0a80-c5dc-473a-a85b-2af27a5f8576 – 3bfe001a-32de-4114-a6b4-4005b770f6d7)

This is a temporary post that was not deleted. Please delete this manually. (ad460b87-fd6f-4309-ac69-2cec6b803963 – 3bfe001a-32de-4114-a6b4-4005b770f6d7)

昨天IIS团队发布了 Windows Cache Extension 1.0 for PHP 的beta测试版，这是用来提高PHP应用跑在Windows系统上的速度的 PHP加速器 。任何PHP应用程序不需要修改任何代码都可以用它来提速，所需做的只是在PHP引擎里启用这个扩展。   安装 Windows Cache Extension 1.0 for PHP – Beta 或下载: Windows Cache Extension 1.0 for PHP 5.2 – Beta Windows Cache Extension 1.0 for PHP 5.3 – Beta 按照" Using Windows Cache Extension for PHP "文章里的指示来安装、启用和配置这个扩展。 注意: 该扩展只能用于PHP的non-thread-safe版本 该扩展只能用于以FastCGI方式运行在IIS上的PHP Windows Cache Extension 1.0 for PHP 5.3只能用于PHP5.3的x86 VC9版本 特性: 支持PHP 5.2和PHP 5.3 提供PHP函数获得cache状态信息 该扩展包含3个可以被分别启用或禁用的缓存特性： PHP opcode cache – PHP是一个脚本处理引擎，它阅读包含文本和/或PHP指令的输入流，并产生另一个数据流（通常是HTML格式）。这意味着在一个web服务器上PHP引擎对每一次来自浏览器客户端的请求都要读入、解析、编译和执行一遍PHP脚本。读入、解析和编译操作给web服务器的CPU和文件系统带来额外的负载，影响PHP网页应用的总体效能。PHP opcode (字节码) cache 用来在共享内存里缓存编译好的脚本字节码，以便同一脚本文件的后续请求可以被PHP引擎重用。 File cache – 即使PHP字节码缓存启用，PHP引擎还需要访问文件系统里的脚本文件。当PHP脚本存储在远程UNC文件共享时，文件操作会带来显著的性能开销。Windows Cache Extension for PHP的文件缓存可以把PHP脚本文件的内容缓存在共享内存里，减少PHP引擎的文件系统操作。 Relative file path cache – PHP脚本频繁使用相对路径include或操作文件。每个相对文件路径需要被PHP引擎转换成绝对文件路径。当PHP应用以相对路径使用很多PHP文件时，解析相对路径到绝对路径的操作会影响性能。Windows Cache Extension for PHP提供相对文件路径缓存，减少PHP引擎需要进行的转换数量。 更多信息: Windows Cache Extension for PHP on IIS.NET Using Windows Cache Extension for PHP 您可以使用 Windows Cache Extension for PHP Forum ， mailto:iisphp 或在本文后留言来提问、汇报问题或提供特性反馈建议等。

おはようございます。Aaron です。 お久しぶりでございます。 Server 2008 R2のRTMもしましたし、MicrosoftがLinuxのKernelにもコードをチェックインしましたし、いろんな面白いことがおこっていますね。  Hyper-V v2 対応のLinux 統合コンポーネントの指名してください！ https://connect.microsoft.com/SelfNomination.aspx?ProgramID=1863&pageType=1&SiteID=495 Linux IC (Integration Components)のRC2のものです。ConnectにSign-inして、ダウンロードできます。 詳細情報はRedmond のVirtualization ブログへごらんください。 Linux ICs for Hyper-V and GPLv2 と http://blogs.technet.com/virtualization/ です。 よろしくお願いいたします。 Aaron

Hurray Good News,  Windows 7 and Server 2008 R2 have been released to Manufacturing Today. I’ve been using both of them for over 6 months now and i’m nothing but impressed

Hallo, Normalerweise schreibe ich nur ungern ab. Aber in diesem Fall erscheint es mir wichtig, da man immer wieder auf Probleme stößt, die damit einhergehen: Mein Kollege J.C