Monthly Archives: October 2014

Virtual Machine: Configuring for daily development use

Every time I create or given a new Development Virtual Machine (VM) I find myself repeating the same steps.

Make sure the VM has been added to the Domain

  • Start > right click: Computer > Properties > Change settings
  • In some circumstances you may need to remove and re-add the machine the domain and restart the machine after each action

Stop “Server Manager > Dashboard” form opening on start-up

  • Manage > Server Manager Properties > Check: “Do not start Server Manager automatically at logon”
  • Click OK and close the “Server Manager > Dashboard” window.

Disable the Shutdown Tracker

  • Ctrl + R > Enter: “gpedit.msc” > Click: OK
  • Navigate to: “Computer Configuration\Administrative Templates\System”
  • Double click “Display Shutdown Event Tracker”
  • Select: Disabled > Click: OK

Enable Shutdown without Logging

  • Ctrl + R > Enter: “gpedit.msc” > Click: OK
  • Navigate to: “Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\”
  • Double click “Shutdown: Allow system to be shut down without having to log on”
  • Select: Enable > Click: OK

Update User Account Control Settings

  • Run > Search “User Account Control Settings”
  • Click: Settings > “Change User Account Control settings”
  • Change to your required level and click OK

Configure Power Saving

  • Run > Search “Power Saving”
  • Click: Settings > “Change power-saving settings”
  • Change plan settings to “High performance”
  • Choose when to turn off the screen: Never
  • Change when the computer sleeps: Never

Restart the VM​

 

Virtual Machine: SharePoint failing to create a Web Application

So your Virtual Machine doesn’t quite have enough resources to create a new Web Application using Central Admin, then you have two choices PowerShell or the workaround I’m going to describe today.

Before I describe the workaround let me describe why you might be here in the first place. Normally you would open SharePoint 2013 Central Administration and from the home page click on “Manage web applications”. At this point you click the “New” button, fill out the form and wait. If you are unlucky then you will see the “Something went wrong” screen. Unfortunately SharePoint has probably created a Content Database, an IIS Application Pool and an empty IIS Site. If so then you can try the deleting the assets using the GUI however it will almost certainly fail. Or just run the following PowerShell (and be patient):

Remove-SPWebApplication http://sitename -Confirm -DeleteIISSite -RemoveContentDatabases

The workaround:

Open the Internet Information Services (IIS) Manager window, right click on Application Pools node, select “Add Application Pool…”, enter a name (e.g. “SharePoint – site.domain.com”) and click OK.

One your new Application Pool has been created select it and click on “Advanced Settings…” (on the right, under Actions). And then follow these actions:

  1. Change the Identity to be an AD account
  2. Change Idle Time-out (minutes) from 20 to 0
  3. Change the values for the following properties to 420:
    • Ping Maximum Response Time (seconds)
    • Shutdown Time Limit (seconds)
    • Startup Time Limit (seconds)
  4. Click OK

Now you are ready to create you Web Application using SharePoint 2013 Central Administration. Navigate to “Manage web applications” and click the “New” button. Fill out the form, but this time select your new Application Pool before clicking OK and wait. Assuming all went OK then open the IIS Manager window and navigate back your new Application Pool’s Advanced Settings and change the values for the following properties back to 90:

  • Ping Maximum Response Time (seconds)
  • Shutdown Time Limit (seconds)
  • Startup Time Limit (seconds)

Job done.​