Skip to content

Take it behind the barn and shoot it… unless there’s still hope.

Take it behind the barn and shoot it… unless there’s still hope. published on No Comments on Take it behind the barn and shoot it… unless there’s still hope.

You get used to tools that are created to make your life easier.

Life is great, until you run into an environment that is too old for those tools to work.

In this case, I’m referring to the ability to do some PowerShell against an old active directory domain running on a 2003 functional level.

Here comes the savior, a tool called Quest ActiveRoles Management Shell. This tool was developed by Quest Software a while back (before Dell acquired them). It used to be free (up until version 1.5.1). Dell decided to change that and start charging.

There is a site that kindly still provide access to the last free version that was released.

Quest ActiveRoles Management Shell

To give an example of what can be accomplished;

let’s say you want to get a list of users from active directory who are currently configured to have their password never expire. You simply run the following:

Get-QADUser -PasswordNeverExpires

you can also add “-SizeLimit 0” in order to get more than the normal 1000 maximum results. You can also pipe the results into a a change by using “| Set-QADUser” followed by the attributes you want to change.

This is just a tiny example of what can be done, all against a 2003 active directory domain that would normally not support it.

Enjoy

Simon

Multiple network interface card. Default gateway. View Connection Server. View agent

Multiple network interface card. Default gateway. View Connection Server. View agent published on No Comments on Multiple network interface card. Default gateway. View Connection Server. View agent

While building a small isolated multi-tenant VDI environment, I’ve ran into a small issue that can be fixed rather easily.

Conditions which might trigger the issue:

  • VM with two NICs
  • Both NICs are configured on different subnets
  • NIC facing View Connection Server is not the VM’s default gateway

In this situation, you have to tell the View Agent which subnet to use in order for the View Connection Server to be able to talk to it.

Solution:

Modify the registry of the template used for example:

HKLM\Software\VMware, Inc.\VMware VDM\Node Manager\subnet = 172.16.15.0/24 (REG_SZ)

Enjoy one less headache

Simon