Month: February 2016

SCVMM 2012R2 – Error 25100 – Unable to Delete Logical Network

· Leave a comment ·

SCVMM 2012R2 – Error 25100 – VMM is Unable to delete the logical network

This error will occur when you are trying to delete a logical network which still has resources bound to it.

After creating some virtual machines that were bound to this logical network, I realized there was no communication between the VMs. This was a result of not selecting the VLAN-based independent network  as I chose “one connected network”. I went back to each VM and removed the network adapter/logical network. I then tried to delete the logical network and was presented with this error.

Error

Within the SCVMM Fabric and right-clicking the Logical Network in question and viewing its Dependent Resources, I was able to view that there were numerous “Temporary Templates” still associated to the Logical Network. Since time was not of the essence, I could not wait for SQL and/or SCVMM to flush the data on its own time/interval. So, therefore I forcefully removed the dependencies. Here is how:

As mentioned, if you right-click on the Logical Network and view its Dependent Resources, you will get something similar to this. Take note of the name of the string.

List of Dep Resources

Now, launch the SCVMM PowerShell Console (Run as Administrator), and run the following cmdlet, “Remove-SCVMTemplate -VMTemplate “<templateID>“.

PSCode

If the template ID was inputted correctly, you should have got the following output:

PSResult

You will need to repeat this cmdlet for all of the dependent template IDs.

 

Hope that helps!

Another Win for Windows 2012R2 Minimal UI

· Leave a comment ·

As mentioned before, Windows 2012R2 allows System Administrators to run their OS in a stripped down Core mode with no UI what so ever and only access to PowerShell and Command Prompt, or with the full UI, which includes File Explorer, System Task Bar, Internet Explorer and so on. There is a middle ground between the two, that is Minimal UI. I won’t get into the specifics in this post, but this essentially allows SysAdmins to have UI access to applications such as Event Viewer, Hyper-V, Failover Manager, Window Services, Administrative Tools etc., but at the same time running their OS in a much more refined, less resource intensive environment, thus a smaller footprint.

Windows 2012R2 UI Options:

  1. GUI (traditional experience)
  2. Core (stripped down, no Server Manager, only PowerShell and Command Prompt)
  3. Minimal UI (Server Graphical Shell removed)

What’s my point? Well, as Microsoft releases patches every month, this typically applies to machines with security vulnerabilities, and that starts usually with applications and their UI’s, ie. Internet Explorer. Since the Windows 2012R2 Minimal UI is not running your typical applications such as IE (Internet Explorer) and a System Task bar there are far less patches to be applied to the OS with Minimal UI, and especially Core.

Today, I was patching some servers, and getting them up to date for February, and the results speaks for themselves. Not only is the server with Minimal UI faster and more snappy but take a look at the number of patches needed this month for the server with the full UI versus the server with the Minimal UI.

Windows 2012R2 with full UI

withUI

Windows 2012R2 with Minimal UI

withoutUI

I hope this is enough incentive for you to consider using Minimal UI or even Core if you are that comfortable with PowerShell and Command Prompt.

Also, as you can see in the Minimal UI screenshot above, SysAdmins still have access to tools like Hyper-V manager, etc.

 

Cheers!

Configuring Memory Consumption for SQL Server 2012 R2

· Leave a comment ·

Naturally (by default) SQL will consume all the memory available within its environment. There are times some applications require a minimum of memory allocated to the SQL instance before you can proceed with the application install. Below is how you can configure the minimum and maximum memory allocation your SQL instance can consume.

For starters, I am going to assume you understand how much memory (RAM) is available to your SQL server, and you have done the math behind any other SQL instances that may be within your SQL server…

In my case, I am going to ensure my application will always have a minimum of 12GB of memory, and a maximum of 14GB. The server itself has 16GB, and I will leave 2GB for the OS.

Launch your SQL Server Manager > right-click on the named instance > select Properties > select the Memory tab > define your settings here.

1

2

 

That is it!