Month: July 2018

Hyper-V CPU Musings

Hyper-V CPU Musings

Recently I had the opportunity arise where I was able to test a few CPU core configurations on an unused host.

My gold here is to see if a CPU virtualization penalty exists and secondarily to see what effect hyperthreading has on CPU performance in a single VM setting.

Specs of the host:  Dual Xeon Gold 6144, 512GB RAM, SSD

HyperV version:  Windows 2016 (long term branch)

To start, here are the Cinebench R15 scores before HyperV was installed:

Hyperthreading enabled got a score of 3427 (left) whereas hyperthreading disabled got a score of 2680:

                            

Next, installed Hyper-V, built a VM running the full GUI of 2012R2, fully updated.

First test, hyperthreading disabled, VM has 16 cores assigned:

Nice!! only 2 points off of the physical.

Now, enable hyperthreading at the host level.  VM still has 16 cores assigned:

Ouch, 1021 points lower (-38%).  Keep in mind all we did was enable hyperthreading on the host.  A 38% penalty just in that setting.

Next test, assign 32 cores to the same VM:

Above 3000 again.  191 points off (-5%) the physical install benchmark above.

And just because, 24 cores assigned to the VM:

Here we have 511 points off the physical host (-15%).

Conclusion:

What did I learn?  With hyperthreading disabled, there is a virtualization penalty, but it barely registers.

It’s when hyperthreading is enabled that one has to be careful.  That large of a hit (-38%) is interesting to say the least.

That being said, with hyperthreading enabled and you assign all available logical cores to the VM, it wasn’t too shabby.

***DISCLAIMER*** I am not responsible for this breaking or damaging any of your stuff.  Copyrights belong to their original owners***

Intel Hyperthreading… worth it?

Intel Hyperthreading… worth it?

In a recent post, I listed a benchmark using Cinebench R15 on a pair of Xeon Gold 6144 CPU’s.  In that post, I mentioned that hyperthreading was enabled.  How much of a difference did that make?

To recap, here’s the full 16 physical/32 logical benchmark:

And now, hyperthreading disabled:

And there we go.  Hyperthreading adds another 747 points, for an increase of nearly 28%.

Oddly, that goes in line with something I read before where hyperthreading can add up to a 25% increase in performance (on physical hardware).  Sadly I can’t remember where I read that, or when.

***DISCLAIMER*** I am not responsible for this breaking or damaging any of your stuff.  Copyrights belong to their original owners***

Upgrading to a current gen Xeon… worth it?

Upgrading to a current gen Xeon… worth it?

Recently I had a chance to introduce a new server into our environment spec’d out to use two CPU’s from Intel’s Xeon Gold family with the same amount of cores as the server it was replacing.  Could their be an increase in CPU performance?

Let’s find out, using a quick and easy way to measure:  Cinebench R15

The old server (Dell R720XD) running two Intel Xeon E5-2667 v2 processors (Ivy Bridge, 8 cores each):

The new server (Dell R740XD) running two Intel Xeon Gold 6144 processors (Skylake-SP, 8 cores each)

BIOS and Power management settings were set to maximum (no power savings, max performance)

So first, 16 cores of Xeon E5-2667v2 (Hyperthreading enabled)

A score of 2464.  No slouch.

Next, 16 cores of Xeon Gold 6144 (Hyperthreading enabled)

Wow, 3427! Almost 1000 points higher, which if my math is right is nearly 40% faster.

Keep in mind this is one benchmark, YMMV, but it’s an easy way of showing the difference you can gain in three generations of CPU’s.

***DISCLAIMER*** I am not responsible for this breaking or damaging any of your stuff.  Copyrights belong to their original owners***

Clearing AX Client Cache for All Users on a RDS Host

Clearing AX Client Cache for All Users on a RDS Host

It’s AX code update time, and you’re needing to clear out everyone’s AX client side cache on your RDS host servers.

That’s a lot of user folders to do through.

Here’s what I do:

Let’s start with some assumptions.

  1. You have the AX client deployed using Remote Desktop Services (RemoteAPP)
  2. You are not using User Profile Disks

If that describes your environment, read on.  If not, or if it’s close, keep reading.  You may be able to modify my solution to fit your needs.

The goal:  Remove all local AX cache files for all users in the following locations:

  1. All files/folders starting with “vsa” located here: c$\users\%username%\Appdata\Local\Microsoft\Dynamics AX\
  2. All files ending in “*.kti” or “.auc” located here: c$\users\%username%\Appdata\Local

Requirements:

  1. User running the Powershell script must have full rights to each user folder on each RDS host server.  Domain Admin members in AD would be a good place to start for the quick and dirty way.
  2. You must run this on each RDS host server.

What it does:

  1. Users the command “get-childitem” under “c:\users” to generate a list of all folders
  2. Using “foreach”, it loops through every folder
  3. In each folder, it does a “get-item” under the specific AX client cache directories get all files/folders, then another “for-each” to delete them

The code:

#Specify Directory containing User folders
$userfolderlist = get-childitem -path c:\users -directory

#Remove AX Client Cache files for each folder
foreach ($item in $userfolderlist)
{
write-host "Removing Test AX cache for username $item"
            get-item "C:\Users\$item\AppData\Local\Microsoft\Dynamics Ax\vsa*" | foreach ($_) {remove-item $_.fullname -recurse}
            get-item "C:\Users\$item\AppData\Local\*.kti" | foreach ($_) {remove-item $_.fullname -recurse}
            get-item "c:\Users\$item\AppData\Local\*.auc" | foreach ($_) {remove-item $_.fullname -recurse}
            }

***DISCLAIMER*** I am not responsible for this breaking or damaging any of your stuff.  Copyrights belong to their original owners***

Clearing AX Client Cache for One User in a RDS Environment Using Powershell

Clearing AX Client Cache for One User in a RDS Environment Using Powershell

“You should clear that person’s AX cache”.

How many times have you heard that?  If you are running Dynamics 2012 (R2 in my case), this post may help.

Let’s start with some assumptions.

    1. You have the AX client deployed using Remote Desktop Services (RemoteAPP)
    2. You are not using User Profile Disks
    3. You have multiple RDS Hosts people connect to

If that describes your environment, read on.  If not, or if it’s close, keep reading.  You may be able to modify my solution to fit your needs.

The goal:  Remove all local AX cache files for one user in the following locations:

  1. All files/folders starting with “vsa” located here: \\%hostname%\c$\users\%username%\Appdata\Local\Microsoft\Dynamics AX\
  2. All files ending in “*.kti” or “.auc” located here: \\%hostname%\c$\users\%username%\Appdata\Local
  3. Additionally, be able to do this for Production, Test, Dev, and Training AX RDS servers

Requirements:  User running the Powershell script must have full rights to each user folder on each RDS host server.  Domain Admin members in AD would be a good place to start for the quick and dirty way.

What it does:

  1. Prompts the person to enter the AD username of the desired user of whose cache you want cleared (line 5)
  2. Prompts the person to make sure that user has had their RDS session closed, otherwise the AX client may still be running, thus locking the files you want to delete (line 6)
  3. Asks if you are sure (line 8).  If you enter Y, the script continues, otherwise a N will skip over everything until line 64.
  4. Asks which AX environment you want to do this in (line 13)
  5. Connects to the RDS server for the environment specified in step 4.

There are if/else statements from here on out (line 17, 24, 31, and then 38) that are hard coded for specific servers dependent on which AX environment you chose.

The code:

#This script will connect to AX RDS servers and delete the AX client cache
#Make sure the user has been logged out of the RDS box first otherwise the files will be locked

#Provide the Active Directory Username
$axuser = read-host 'Enter the AD username'
write-host "Make sure that $axuser has been logged out of their RDS session before proceeding"

$Yousure = read-host 'Are you sure you want to continue? Y/N'
If ($yousure -match "y")
 {

#Provide the AX Environment
write-host "Possible AX Environments:  Test, Training, Dev, Prod"
$axenvironment = read-host 'Enter the AX Environment'
    
#Connect to AX environment chosen and delete local cache    
    If ($axenvironment -match "Test")
        {
            write-host "Removing Test AX cache for username $axuser"
            get-item "\\axtestrds\c$\Users\$axuser\AppData\Local\Microsoft\Dynamics Ax\vsa*" | foreach ($_) {remove-item $_.fullname -recurse} 
            get-item "\\axtestrds\c$\Users\$axuser\AppData\Local\*.kti" | foreach ($_) {remove-item $_.fullname -recurse} 
            get-item "\\axtestrds\c$\Users\$axuser\AppData\Local\*.auc" | foreach ($_) {remove-item $_.fullname -recurse}
        }
        else { If ($axenvironment -match "Training")
            {
                write-host "Removing Training AX cache for username $axuser"
                get-item "\\TrainingRDS\c$\Users\$axuser\AppData\Local\Microsoft\Dynamics Ax\vsa*" | foreach ($_) {remove-item $_.fullname -recurse} 
                get-item "\\TrainingRDS\c$\Users\$axuser\AppData\Local\*.kti" | foreach ($_) {remove-item $_.fullname -recurse } 
                get-item "\\TrainingRDS\c$\Users\$axuser\AppData\Local\*.auc" | foreach ($_) {remove-item $_.fullname -recurse } 
            }
                else { If ($axenvironment -match "Dev")
                    {
                        write-host "Removing Dev AX cache for username $axuser"
                        get-item "\\DevRDS\c$\Users\$axuser\AppData\Local\Microsoft\Dynamics Ax\vsa*" | foreach ($_) {remove-item $_.fullname -recurse } 
                        get-item "\\DevRDS\c$\Users\$axuser\AppData\Local\*.kti" | foreach ($_) {remove-item $_.fullname -recurse } 
                        get-item "\\DevRDS\c$\Users\$axuser\AppData\Local\*.auc" | foreach ($_) {remove-item $_.fullname -recurse } 
                    }
                    else { If ($axenvironment -match "Prod")
                        {
                            write-host "Removing Prod AX cache for username $axuser"
                            get-item "\\ProdRDS02\c$\Users\$axuser\AppData\Local\Microsoft\Dynamics Ax\vsa*" | foreach ($_) {remove-item $_.fullname -recurse} 
                            get-item "\\ProdRDS02\c$\Users\$axuser\AppData\Local\*.kti" | foreach ($_) {remove-item $_.fullname -recurse} 
                            get-item "\\ProdRDS02\c$\Users\$axuser\AppData\Local\*.auc" | foreach ($_) {remove-item $_.fullname -recurse} 
                            get-item "\\ProdRDS03\c$\Users\$axuser\AppData\Local\Microsoft\Dynamics Ax\vsa*" | foreach ($_) {remove-item $_.fullname -recurse} 
                            get-item "\\ProdRDS03\c$\Users\$axuser\AppData\Local\*.kti" | foreach ($_) {remove-item $_.fullname -recurse} 
                            get-item "\\ProdRDS03\c$\Users\$axuser\AppData\Local\*.auc" | foreach ($_) {remove-item $_.fullname -recurse} 
                            get-item "\\ProdRDS04\c$\Users\$axuser\AppData\Local\Microsoft\Dynamics Ax\vsa*" | foreach ($_) {remove-item $_.fullname -recurse} 
                            get-item "\\ProdRDS04\c$\Users\$axuser\AppData\Local\*.kti" | foreach ($_) {remove-item $_.fullname -recurse } 
                            get-item "\\ProdRDS04\c$\Users\$axuser\AppData\Local\*.auc" | foreach ($_) {remove-item $_.fullname -recurse } 
                            get-item "\\ProdRDS05\c$\Users\$axuser\AppData\Local\Microsoft\Dynamics Ax\vsa*" | foreach ($_) {remove-item $_.fullname -recurse} 
                            get-item "\\ProdRDS05\c$\Users\$axuser\AppData\Local\*.kti" | foreach ($_) {remove-item $_.fullname -recurse } 
                            get-item "\\ProdRDS05\c$\Users\$axuser\AppData\Local\*.auc" | foreach ($_) {remove-item $_.fullname -recurse } 
                            get-item "\\1075rds09\c$\Users\$axuser\AppData\Local\*.auc" | foreach ($_) {remove-item $_.fullname -recurse} 
                            }
                                else { write-host "You did not enter the right command"
                                    }
                        }
                    }
                }

#Reminder to clear usage data in AX Client
write-host "Now that cache has been cleared, connect to AX client on $axenvironment and clear the usage data for $axuser"
}
else 
                    {write-host "You chose not to continue.  Well played"
                    }

***DISCLAIMER*** I am not responsible for this breaking or damaging any of your stuff.  Copyrights belong to their original owners***

Copy AX Security Roles to Another User Using Powershell

Copy AX Security Roles to Another User Using Powershell

As anyone who is an admin for Dynamics AX 2012 (R2 in my case) can attest, assigning user security roles can be a monotonous chore, especially if you have a high number of users that need specific roles.

Initially when my company implemented AX, user security roles were added via the AX client.  User to copy on one side, user to add on the other.  Click assign roles for each one you need to copy.

Ugh.

About a year later I was looking into other options and found that while there isn’t much Powershell for AX 2012, one of the things you can do is add or remove security roles.  Tell me more!

Let’s start, shall we?

Below in this first image, we have one Leia Organa, new hire to our company.

Oddly, according to HR she needs to have the same roles as her brother:

At this point, you need to be on a computer that is configured with an AX connection to the AOS service, AX management utilities installed, and the user you are running this as in Windows needs to have security or system admin permissions in the AX environment.  In my case, I run this directly on the AOS server.  YMMV

Anyway, the code:

#Load AX Powershell functions
. "C:\Program Files\Microsoft Dynamics AX\60\ManagementUtilities\Microsoft.Dynamics.ManagementUtilities.ps1"

$axuserold = read-host 'Enter the AD username of the person to copy from'
$axusernew = read-host 'Enter the AD username of the person to copy to'

get-axsecurityrole -axuserid $axuserold | foreach ($_) {add-axsecurityrolemember -axuserid $axusernew -aotname $_.aotname}

What it does:

Step 1:  Enter the Active Directory user name of the person to copy from (pauses for input):

Step 2:  Enter the Active Directory user name of the person to copy to (pauses for input):

Hit enter, and once completed the window goes away.

What does it do?

It uses the Powershell command “get-axsecurityrole” for a specific user you mention, and then using the “foreach” option Powershell has it uses the command “add-axsecurityrolemember” to add that role to the user you specify.  It loops through each role the originated user has and adds it in.

Finally, Leia is good to go:

This has saved me countless hours of tediously adding roles to new people to the organization.  Hopefully this can help you out as well.

***DISCLAIMER*** I am not responsible for this breaking or damaging any of your stuff.  Copyrights belong to their original owners***