0

Windows Store requires Windows Firewall

If you are trying to install or get updates for modern apps (apps obtained through the Windows Store) and the process fails, you should check to see if the Windows Firewall service is running.

You may have experienced the message before that reads: “something happened and this app couldn’t be installed. Please try again.” I’ve seen this before myself and usually after trying again it works. But, if you receive the message along with the error code 0x0073d0a, it could indicate the Window Firewall has been turned off.

You can check the Applications and Services event logs, but the easiest way to verify that the Windows Firewall is running or not is to just open the app.

Do this:

  1. Open the Search charm and search for Firewall.
  2. Choose Check firewall status.
  1. Verify the Firewall state.
0

How to install .NET Framework 3.5 on Windows Server 2012 and Windows Server 2012 R2

If you have an application that you want to run on Windows Server 2012 that requires the .NET Framework 3.5, you will most likely run in to a problem when trying to install it. If you are trying to install .NET Framework 3.5 from the Server Manager GUI, you will see this when installing the feature:

“Do you want to specify an alternate source path? One or more installation selections are missing source files…”

Continue Reading

0

“Database cannot be started in this edition of SQL Server” error when restoring or Upgrading a Microsoft Dynamics CRM 2013 database

I followed my own article here for upgrading from SQL Evaluation to SQL Standard.  I had my Dynamics 2013 environment already stood up and unexpectedly already used for development work.

After the ‘upgrade’ steps, the database appeared to be in (suspect) mode and I didn’t have a backup (but a checkpoint via hyperv at least).

Anyway, I uninstalled the SQL Standard from programs and features.  Reinstalled the Evaluation version (which is Enterprise by the way) and ran this script on Microsoft’s support site against the CRM databases.

I then followed my article and the databases successfully stayed in normal operating non-suspect mode.

Continue Reading

0

Windows Server 2012 R2 Getting Error 800B0001 When Checking for Updates

I recently added some new Windows Server 2012 R2 servers to my environment for a project I’m working on. So far I really like this operating system, and I’m getting used to where everything is. That being said, I have ran into a few issues and one of them is an error I’ve been getting when trying to update these servers from my Windows 2008 R2 WSUS server.
<—more!—>
When I check for updates I get an error numbered 800B0001 that looks like this:

To fix this error here is what you have to do:

  • On your WSUS server install  WSUS-KB2720211-x64 and WSUS-KB2734608-x64 
  • Open your WSUS management console and manually perform a  synchronization
  • Next, on your affected servers run the following:

net stop wuauserv
rd /s /q %windir%softwaredistribution
net start wuauserv

The issue should be fixed now. If you have a lot of servers/workstations with this issue you might want to run those commands as a part of a start up script.

0

PowerShell Script to clean up WSUS

I was rebuilding my work’s Windows Server Update Services (WSUS) server the other day, and while configuring it I thought about how nice it would be to automate the cleanup process. You know, decline superseded updates, decline obsolete updates etc.
<–more!–>
Normally one would have to do this manually by running the Server Cleanup Wizard, but who has time for that?

Well SpiceWorks community member Wouter-Trust created an awesome PowerShell script that works like a charm! You can find his post here and you can download his script here.

I have my script running once a week to free up disk space, and generally optimize our patch deployment process.

0

TechNet – Migrate Roles and Features to Windows Server

http://technet.microsoft.com/en-us/library/jj134039.aspx

Migration documentation and tools ease the process of migrating server roles, features, operating system settings, and data from an existing server that is running Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, or Windows Server 2012 R2 to a computer that is running Windows Server 2012 R2. By using migration guides linked to on this page (and where appropriate, Windows Server Migration Tools) to migrate roles, role services, and features, you can simplify deployment of new servers (including those that are running the Server Core installation option of Windows Server 2012 R2 or Windows Server 2012, and virtual servers), reduce migration downtime, increase accuracy of the migration process, and help eliminate conflicts that could otherwise occur during the migration process.

  Continue Reading