Category Archives: Wordpress

Issue in Windows 2012 R2 when setting RDP users to change password upon login

We have had issues where RDP users haven’t been able to login on a remote desktop terminal server when the “user much change password at next logon” button has been checked in user properties – see screenshot #1 below. Various comments and posts online indicate that changes in the windows authentication process in recent OS versions don’t allow this change if Network Level Authentication or Credential Security Support Provider (CredSSP)  is enabled.  This is only an issue trying to force users to change their password on a RDP session – it works fine from a console session if you are local to the machine.  Here is a workaround as well as alternatives you may consider:

 

  1. Don’t use this option to force users to change their password. Instead, have them manually change it upon logon by pressing control-alt-end and following the change password prompts. Another option is to create a complex, strong password for them without having them change it upon first logon (may be safest route in certain situations) or have them select their own password but enter it with the Administrator while on the admin session and not select the change at next logon option.
  2. NOT RECOMMENDED IN GENERAL – If you still want to use this option to force password change, you could turn off NLA and change RDP security layer to the RDP native security. See screenshot #2 below on turning off NLA. See screenshot #3 below on enabling a group policy to select the RDP security layer instead of negotiate (typically the default) or SSL/TLS. Using NLA and the higher security layers are usually recommended on your server for security reasons.
  3. Note: if you are having issues logging in to the server from RDP and getting errors about domain validation (when in workgroup mode and there is no domain) and often from the MAC remote desktop client, make sure you are logging in with the full name which is “machinename\username” instead of just username. Machinename is the name given to the server, which you can see under computer properties.

 

SCREENSHOT #1

User_Properties_General_Tab

SCREENSHOT #2

Turn_off_NLA

SCREENSHOT #3

Change_RDP_Security_Layer

How do I install WordPress on windows server 2012

How do I install WordPress on windows server 2012.

You download and run the Microsoft Web Platform Installer wpilauncher.exe file.  Then click on Applications link on the top of the page and then select WordPress and click the Install button.

  1. First download and run the Microsoft Web Platform Installer wpilauncher.exe file.
  2. Second select Applications link at the top.
  3. Third select wordpress by clicking ‘Add’ next to it.
  4. Now click the ‘Install’ button at the bottom of the page.
  5. Follow the prompts to set your passwords for your WordPress site.
Microsoft Web Platform Installer for WordPress install on Server 2012 R2

Microsoft Web Platform Installer for WordPress install on Server 2012 R2

  1. The first step of the install process has you select the type of database you want to use. You can leave the default of MySQL on a Windows server and this process will install MySQL for you.
  2. Then you need to enter a root password for the database.
  3.  Assuming you did not install or configure IIS the next step will let you pick the: Web Site, WordPress application name, Web Site Name, Physical path, IP Address, Port and Host Name for the site.
  4.  Next you enter: Authentication Key, Secure Authentication Key, Logged In Key, Nonce Key, Authentication Salt, Secure Authentication Salt, Logged In Salt and Nonce Salt.
  5. On this final page you hopefully see a green check mark and a list of the products installed.  **Scroll to the bottom if you can to see the Database Name, User Name and Password.  You can save this by clicking the copy to clip board link.  At the top you can click ‘Launch WordPress’ to open your site and customize it.

You should update your web.config now WordPress Permalinks

Are you trying to use Permalinks with WordPress to have a nice page name rather than www.domain…com/?p=3 and you see the message toward the top of your page that says “You should update your web.config now”?

You might be thinking what is a web.config. This means that you are running your WordPress site on a windows server like Windows 2012R2 server and the WordPress Admin can not add the code to the web.config file which is on your server under the default install folder for WordPress.

First you need to locate your web.config file.

  • You should find it in the default root where you installed WordPress. This folder will also have the folders “wp-admin”, “wp-content” and “wp-includes”
  • You can search your server for the web.config file. Note you may have more than one. So make sure this folder has these folders “wp-admin”, “wp-content” and “wp-includes”.

If you can’t access your file system to locate this file then you can’t user permalinks. If you are hosting with godaddy you want to use a Linux server. If you are using a dedicated server you should be fine running WordPress on a Windows Server. I know of several successful sites.

Once you find your web.config file you want to open it. You can open it in WordPad or Visual Studio if you have it loaded.

You need to add the code shown below and you can add it just below the line.


	<rewrite>
			<rules>
				<rule name="Main Rule" stopProcessing="true">
					<match url=".*" />
					<conditions logicalGrouping="MatchAll">
						<add input="{REQUEST_FILENAME}" matchType="IsFile" negate="true" />
						<add input="{REQUEST_FILENAME}" matchType="IsDirectory" negate="true" />
					</conditions>
					<action type="Rewrite" url="index.php" />
				</rule>
			</rules>
		</rewrite>

Now Save your changes to the web.config file.

And now your web.config probably looks very much like the following.

<?xml version="1.0" encoding="utf-8"?>
<configuration>
	<system.webServer>
		<rewrite>
			<rules>
				<rule name="Main Rule" stopProcessing="true">
					<match url=".*" />
					<conditions logicalGrouping="MatchAll">
						<add input="{REQUEST_FILENAME}" matchType="IsFile" negate="true" />
						<add input="{REQUEST_FILENAME}" matchType="IsDirectory" negate="true" />
					</conditions>
					<action type="Rewrite" url="index.php" />
				</rule>
			</rules>
		</rewrite>
		<staticContent>
			<remove fileExtension=".svg" />
			<mimeMap fileExtension=".svg" mimeType="image/svg+xml" />
		</staticContent>
        <defaultDocument>
            <files>
                <remove value="index.aspx" />
                <add value="index.php" />
            </files>
        </defaultDocument>
	</system.webServer>
</configuration>

Credit for the code goes to Jeff Clark NOTE his code does not have the correct double quotes for the asp.net web.config file found

WordPress error Windows Server HTTP Error 403.14 Forbiden

If you see the following error after a successful install of wordpress on a IIS 7.5 on a Windows Server the fix might be to change your default document to index.php    In the case of the following error we found the default document set to index.aspx since it was inherited from the parent website, in this case a asp.net website.

Solution change your default document for your WordPress website. 

To change your default document in IIS 7.5 open IIS select/highlight/click the WordPress website (folder)

Then scroll down in the middle panel and double click the “Default Document” icon under the IIS section.  Here you can verify the default document(s) for your WordPress website and check to see if it is set to “index.php”

Actual Errors displayed in web browser
Error Summary HTTP Error 403.14 – Forbidden

The Web server is configured to not list the contents of this directory.

403 – Forbidden: Access is denied.

You might see the full error is you are viewing your wordpress website on the actual server via a browser which would like this

Server Error in Application “RIPTIDEHOSTING.COM/BLOG”

Internet Information Services 7.5

Error Summary HTTP Error 403.14 – Forbidden

The Web server is configured to not list the contents of this directory.

Detailed Error Information

Module DirectoryListingModule

Notification ExecuteRequestHandler

Handler StaticFile

Error Code 0x00000000

Requested URL http://www.riptidehosting.com:80/blog/

Physical Path C:inetpubwwwrootRiptideHositng.comblog

Logon Method Anonymous

Logon User Anonymous

Most likely causes: •A default document is not configured for the requested URL, and directory browsing is not enabled on the server.

Things you can try: •If you do not want to enable directory browsing, ensure that a default document is configured and that the file exists. • Enable directory browsing using IIS Manager. 1.Open IIS Manager. 2.In the Features view, double-click Directory Browsing. 3.On the Directory Browsing page, in the Actions pane, click Enable.

•Verify that the configuration/system.webServer/directoryBrowse@enabled attribute is set to true in the site or application configuration file.

Links and More InformationThis error occurs when a document is not specified in the URL, no default document is specified for the Web site or application, and directory listing is not enabled for the Web site or application. This setting may be disabled on purpose to secure the contents of the server. View more information »