The entire relocation process is described in this TechNet article: http://207.46.196.114/WindowsServer/en/library/af6646aa-2360-46e4-81ca-d51707bf01eb1033.mspx?mfr=true, the core for moving to local drives: http://207.46.196.114/WindowsServer/en/library/af6646aa-2360-46e4-81ca-d51707bf01eb1033.mspx?mfr=true and for network drives: http://technet2.microsoft.com/WindowsServer/en/library/dd498633-5d65-4a14-b68d-edcb85fada651033.mspx
Once you have completed the preparation of your target volumes and restarted in Directory Services Restore Mode, it’s quite easy with a few ntdsutil commands, so there is usually no need to reinstall and reconfigure Active Directory using dcpromo. This article discusses the volume configuration of Active Directory files and folders and here are the Active Directory best practices.
With the arrival of ASP.NET MVC and the complementary IIS7 file-extension-less request pipeline it’s finally possible to turn ugly “classic ASP.NET” query string URLs into pretty and orderly REST-style URLs, functionality that PHP had for ages. Out with http://mysite.com/catalog.aspx?category=1&product=100, here comes the more pleasing http://mysite.com/widgets&gadgets/the-useful-&-beautiful-widget
However, the ampersand in the latter will generate a “400 Bad Request” response with the default settings in IIS 7 because the ampersand (&) is not acceptable in the request for security reasons. As discussed here, it takes two measures to fix this and make the URL (I did not have to take the third measure quoted in the post, which is setting ValidateRequest=”false” in the ASP.NET MVC view page):
- AllowRestrictedChars http://support.microsoft.com/kb/820129
- Interestingly enough, enable VerificationCompatibility (http://support.microsoft.com/default.aspx?scid=kb;EN-US;826437), a measure designed for pre-SP1 ASP.NET 1.1, but necessary here even with ASP.NET 3.5 to get the ampersand URLs working.
Hope it helps.
Windows Live Writer for Windows Server and Windows XP Professional x64 Edition
Blogging Software, Windows Live Writer, Windows Server 1 Comment »I’ve posted about this nonsensical issue before. As the source link quoted in that post is now dead and the issue continues with the latest version of WLinstaller.exe, here’s the msi source for direct download. It installs fine on Windows Server 2008 (x64) and Windows Server 2003 (32 bit x86). Not sure if it installs on XP Professional x64 as I haven’t tried it, it should though.
And while we’re at it, here are the other files (msi sources):
Windows Live Mail for Windows Server and Windows XP Professional x64 Edition
Windows Live Messenger for Windows Server and Windows XP Professional x64 Edition
Windows Live Photo Gallery for Windows Server and Windows XP Professional x64 Edition
Windows Live Toolbar for Windows Server and Windows XP Professional x64 Edition
Windows Live One Care - Family Safety for Windows Server and Windows XP Professional x64 Edition
Windows Live Sign-In Assistant for Windows Server and Windows XP Professional x64 Edition
Positively no support or warranty.
Once you’ve followed these instructions to install PHP hosted on IIS7 using FastCGI (there’s also a video by Scott Hanselman), you’ll probably want to install MySQL and make it work with PHP. However, with your php.ini in its current state you’ll likely get an error message when you start a MySQL-based app, such as Wordpress:
Your PHP installation appears to be missing the MySQL which is required for WordPress.
There’s a lot of information out there to fix this on Windows, and much advice involves copying and grabbing dlls and stuff. Much of it is superfluous, and it boils down to this with your current configuration:
- Edit your php.ini (in C:\PHP\ or wherever you installed php), and uncomment the following line:
;extension=php_mysql.dll
hint: remove the semicolon
- Change this line:
extension_dir = “./”
to this:
extension_dir = “C:\php\ext” - Save php.ini and restart the web server in IIS Manager
- That’s all
Hope it helps.
Recent Comments