## Installing ADFS to Server Core (2016)

by on Oct.03, 2016, under Tech Stuff

This post assumes you have already completed your installation of Windows Server 2016 and configured IP addressing, domain join, etc.
(* this can easily be accomplished by running ‘sconfig.cmd’ when you first login so it’s not worth a full post)

To get started, login as a domain administrator for the system and complete the following commands on the prompt presented:

– ‘powershell’

This should install all necessary feature related items for ADFS on the system.

Another key component will be your SSL cert. Whatever you will be using, preferably a certificate for adfs.yourdomain.com or *.yourdomain.com, I recommend you export it out with private key in PFX format. Once completed, you’ll need to make sure you copy your certificate pfx out to the machine(s) and then execute the following:

– ‘certutil -importpfx <Path to certificate file>’

You can confirm your certificate installation and snag the thumbprint by executing the following:

– ‘dir cert:\LocalMachine\My’

If you’re setting up the first machine in a farm execute the following commands:

(this method uses a domain user/service account):
– ‘$ADFSCred = Get-Credential’ (input the credentials for your service account) – ‘Install-AdfsFarm -CertificateThumbprint:<thumbprint> -FederationServiceDisplayName:”Test Lab” – FederationServiceName:”adfs.testlab.com” -ServiceAccountCredential$ADFSCred -OverwriteConfiguration’

(this method used a group managed service account (the $is required): – ‘Install-AdfsFarm -CertificateThumbprint:<thumbprint> -FederationServiceDisplayName:”Test Lab” – FederationServiceName:”adfs.testlab.com” -GroupServiceAccountIdentifier <DOMAIN>\<serviceaccount>$ -OverwriteConfiguration’

This should get the initial setup of ADFS running for you on the main machine.

To add additional machines to the farm (up to four using WID) you install all features, SSL certificate, etc. however, instead of installing the farm, you will add a node. You will execute this from each member node you wish to add, assuming SERVER1 is the name of the initial ADFS instance you setup and you’re running this on SERVER2.

(this method uses a domain user/service account):
– ‘$ADFSCred = Get-Credential’ (input the service account credentials you listed above) – ‘Add-AdfsFarmNode -ServiceAccountCredential$ADFSCred -PrimaryComputerName SERVER1 -CertificateThumbprint <thumprint> -OverwriteConfiguration’

(this method used a group managed service account (the $is required): – ‘Add-AdfsFarmNode -GroupServiceAccountIdentifier <DOMAIN>\<serviceaccount>$ -PrimaryComputerName SERVER1 -CertificateThumbprint <thumprint> -OverwriteConfiguration’

You should see a success message. If you do not, you can troubleshoot by testing out the farm configuration with the following commands:

– ‘$ADFSCred = Get-Credential’ (input the service account credentials) – ‘Test-AdfsFarmJoin -ServiceAccountCredential$ADFSCred -PrimaryComputerName SERVER1’
*** If you plan on migrating from 2012R2 to 2016, you will need to set your newly installed 2016 secondary as a primary.

From  your secondary box, run the following command:

You can then run the following to check it’s role:

If you have other secondary machines, make sure to update their configuration to point to the new primary:

Once you’ve verified your new machine is running primary, you remove the old instances from the farm with Remove-ADFSFarmNode.

## Disk Cleanup Utility on Win 2008 R2

by on Jul.06, 2016, under Tech Stuff

Ok, so the convenience of using the disk cleanup utility is sometimes nice for a quick cleanup of service pack files, etc. But it’s missing on 2008 R2. What a pain.

Two ways to get this:

1. Install the desktop experience. Not the best route as this installs all kinds of stuff you don’t want on your server but it works.
2. Manually copy the files from that overgrown beast that is WinSxS (finally something it’s good for) and run the utility directly. (my preference)

To install, copy the following files to the correct destination:

• cleanmgr.exe
• copy to: c:\windows\system32
• cleanmgr.exe.mui
• copy to: c:\windows\system32\en-us
• Install the following update: https://support.microsoft.com/en-gb/kb/2852386 (reboot may be necessary)

## Vera Scene/Device Mode Manipulation

by on Feb.11, 2016, under Tech Stuff

Anyone who’s into home automation with Vera devices, this is for you. Just filing this one under ‘random things I don’t want to forget’.

Use this Luup code in a scene to modify your home mode on an action. For instance, you come inside or wake up in the morning and disarm your alarm but want the home mode to change from Night, Away, etc to Home.

luup.call_action(“urn:micasaverde-com:serviceId:HomeAutomationGateway1″,”SetHouseMode”, {Mode = value}, 0)

Where Mode = value, value = 1 – Home, 2 – Away, 3 – Night, 4- Vacation

ex Scene Configuration:

Step 1 Trigger – ‘Vista Alarm is DISARMED’
Step 2 Device Actions – Leave Empty
Step 3 Finish the Scene – Use the provided code under the section ‘ Also, execute the following Luup code:’
luup.call_action(“urn:micasaverde-com:serviceId:HomeAutomationGateway1″,”SetHouseMode”, {Mode = 1}, 0)

## Updating HP Virtual Connect Modules With VCSU

by on Aug.20, 2015, under Tech Stuff

Ok, since there really isn’t a very good tutorial out there on this nor are there good resources to find the right links to this stuff, here’s a post for you and for me.

So you need update your Virtual Connect Module, right? Should be just as easy as updating the OA, right? riiiiight. Because HP, that’s why.

Ok, so a few things you’ll need:

2. A current version of the VCM firmware. (make sure you get the right firmware for your device type)
a. Flex-10/10D Module
b. FlexFabric 10Gb/24-port Module
c. FlexFabric-20/40 F8 Module
3. You don’t need this, but it’s handy. VCSU Useful Commands.

Now that you’ve made it through all that, the easy part. First we’re going to check the current version of the module, do this by running the vcsu utility with the following:

(yes, you really want to pass all of those lovely credentials, even if they are the same login/password for both the OA and the VCU)

You should then see some results sort of like this:

Now to update. This is very similar to your version check, except changing version to update and adding the switch and path at the end.

You should now see something like the following:

At this point you should now be updated.

I’ll try to keep these updated with the most current links as I update my equipment, however, if someone hits it and it’s out of date, please let me know and I’ll go update it.

### Looking for something?

Use the form below to search the site:

Still not finding what you're looking for? Drop a comment on a post or contact us so we can take care of it!

### Blogroll

A few highly recommended websites...

### Archives

All entries, chronologically...