Vmware UAG – It is the right damned password!!!

*Tap tap tap tap*

Login failed

*Tap tap tap tap*

Login failed

Yes…You are typing the correct password. When setting up the UAG, there’s a minimum password complexity…It just doesn’t tell you that you met it or not… Honestly it’s up there with the firewall changes for VROPS they don’t tell you about, plus calling Domains ‘Realms’…

Anyway! Easily fixed – Root password on the console screen should be fine and do the following:

echo ‘adminPassword=P@ssw0rd’ > /opt/vmware/gateway/conf/firstboot.properties
chown gateway /opt/vmware/gateway/conf/firstboot.properties
supervisorctl restart admin

Lo and Behold! You can access the WebUI again…

One of my colleagues wrote a UAG Firewall rules generator which is worth a look!

https://veffort.wordpress.com/2017/02/20/vmware-access-point-firewall-rule-generator/

vRealize For Operations – Unable to pair the broker agent for Horizon

I actually wrote some documentation on this for my team, when I encountered the issue. Then I lost it. Hence setting up a website to store everything I come across, on!

This issue came about myself after I upgraded the version of VROPS I had installed and I couldn’t for the life of me understand why the agent simply refused to connect. So after much messing around, I found the following vmware KB:

VMware vRealize Operations Manager for Horizon 6.2 Broker Agent fails to pair with the Horizon adapter (2140844)

Yep, they decided to leave out the necessary ports allowed through the firewall on the appliance. Thanks vmware!

If you aren’t comfortable using VI – which for the uninitiated, can be a nightmare, you can take a copy of the file (download it/FTP it off etc) and make the changes, then re-upload it.

Don’t forget the restart the firewall service – also when I rebooted the VROPs server once, it lost the settings, so rookie mistake or something more…sinister… Not sure, don’t care, just had to do this again! 😉

 

Windows update KB3177467 – Causing crashing and boot loop

Oh those were the days. MS updates smashing their way into your infrastructure, leaving Exchange a gibbering wreck, W7 desktops not booting, WSUS not wanting to remove the updates… So glad those days are…gone… Oh wait, no, still happening!

In a physical environment, an update causing an issue with a desktop is a pain the backside – you have multiple options and ways to mitigate this. In a VDI environment… Well, you can imagine the carnage (Like Carmageddon without cars? Desktopgeddon? VDIGeddon? Ok, I’ll stop now.)

After trying multiple solutions, finally stumbled on someone else who had the problem way back in October 2016 and got it sorted out:

Update KB3177467 causing boot loop

DFSR Troubleshooting and considerations

When you have a few DFS servers, everything seems fairly manageable. Add a few more…Yeah… All good… Get an issue, oh joy! Look at all these servers I need to examine in minute detail!

So I’ll start with an MS Blog that deals with config mistakes

Common DFSR Mistakes and Oversights

Might be a few banged heads on the desk (your own!) when you read some of that!

And put together by my own fair hand, some troubleshooting from the DFSR Management tool and some useful DFSR Diag commands

DFSR Management Tool

Verify topology simply checks the servers are contactable, which is useful, but does not verify replication.

DFS Management includes the ability to run a propagation test and generate two types of diagnostic reports—a propagation report and a general health report:

Propagation test    Tests replication progress by creating a test file in a replicated folder.

Propagation report    Generates a report that tracks the replication progress for the test file created during a propagation test.

Health report    Generates a report that shows the health of replication and replication efficiency.

To create a diagnostic report for DFS replication

Click Start , point to Administrative Tools , and then click DFS Management .

In the console tree, under the Replication node, right-click the replication group that you want to create a diagnostic report for, and then click Create Diagnostic Report .

Follow the instructions in the Diagnostic Report Wizard.

Perform all 3 tests and save the resulting xml/html report file.

DFSRdiag

This is the command line tool for DFSR – useful commands are:

dfsrdiag ReplicationState /all – verbose output

pollad – checks in with Active Directory

List DFS replication groups:

dfsradmin rg list

List replicated folders in a replication group:

dfsradmin rf list /rgname:<REPL_GROUP>

List members of a replication group:

dfsradmin mem list /rgname:<REPL_GROUP>

List the local folders that correspond to replicated folders of a replication group:

dfsradmin membership list /rgname:<REPL_GROUP> /attr:RfName,MemName,LocalPath

Show backlog between 2 members of a replication group:

dfsrdiag backlog /rgname:<REPL_GROUP> /rfname:<REPL_FOLDER> /smem:<SRV_A> /rmem:<SRV_B> [/v]

dfsrdiag backlog /rgname:<REPL_GROUP> /rfname:<REPL_FOLDER> /smem:<SRV_B> /rmem:<SRV_A> [/v]

Using the ‘Replicate Now’ command within the GUI or command line, kicks off replication again but is more used for when you have a schedule and want to replicate out of that schedule, whereas we can use it to tell it to start replication again.

Within the DFSR GUI – choose the Replication group, choose the ‘Connections’ tab and right click the Sending Server (usually you have a specific server that’s authoritative, but you can choose the sending member to be whichever you believe is most up to date and Microsofts black magic algorithm will attempt to resolve any file conflicts) and choose ‘Replicate Now’

A huge problem in DFSR is when you have an issue with Conflicted, Deleted and pre-existing files. Thankfully if you do get a conflict and file loss, they become Deleted…And you can get them back. This is the MS blog on this, but a few years ago when I had to do this, it took a great deal of work. It’s not just about getting the files back – who’s going to know which one they were working on? Or which is the most up to date? You do end up needing end user involvement and for me personally, that was making the data recovered available for a certain amount of time with the users expressly informed that they needed to check it themselves and there was just no way of doing that for them.

Restoring Conflicted, Deleted and PreExisting files with Windows PowerShell

DFSR Setup and considerations

DFSR is actually relatively easy to setup.

There’s no need for me to re-invent the wheel or explain in tiny detail, as most of it has all been done before.

So, to start

MS blog about how it can work for you.

DFS Replication in Windows Server 2012 R2

How to set it up

DFSR Setup with screenshots

Another MS blog about how if you have a huge estate, you better use DFSRADMIN command line! (Yeah you’d better!)

DFS Replication and command line

 

Add multiple ESXi Hosts to vCenter (PowerCLI)

So if you’ve read some of my previous posts, you probably figured out that I’ve built a fair few environments from scratch and hate having to rinse and repeat manually. For my last infrastructure project I have some various scripts and tools to sort that out!

The following link lets you add ESXi Hosts to vCenter via PowerCLI, by Hostname range, IP Range, or text file/CSV. I used textfile and name using this method and it worked perfectly.

This ties in with DNS entry creation as well as it means you can quickly and easily add all your hosts and create the DNS entries for them as well.

Add Add multiple ESXi Hosts to vCenter with PowerCLI

DNS Bulk records creation

Horizon View Client Install – Windows

And now for something completely different.

I mean, now for the Horizon View Windows Install!

Download the Horizon View Client from the following site:

https://my.vmware.com/web/vmware/details?downloadGroup=CART17Q1_WIN_440&productId=578&rPId=15156

1win2win

Now, you may not want USB redirection (or it may not work) and also it’s environment dependent whether you want to Log in as current user.

win3

Enter your Default connection server

win4

Continuing on from if you chose to log in as current user

win5win6win7win8win9

Run the app, log in and go forth!