Citrix NetScaler documentation script version 2
The Citrix NetScaler documentation script version 2 has been a huge success from the moment Carl announced during Citrix Synergy last may. The script has been downloaded over 1.500 times already and we still see a daily demand for it. I’ve also received a huge amount of response with new ideas or just a basic thank you, all of this gave me the energy to start working on a new release. This was supposed to be a release with some new requested functionality but in the end the script has been completely rewritten from start to end.
Before I start with explaining what has changed I want to point out that, although I started this script, this truly has been a team effort. The script wouldn’t have been this great if it wasn’t for Carl Webster and Iain Brighton. Webster developed an amazing PowerShell template to get started with documenting and outputting to Microsoft Word. Iain has written all of the functions I use in the script to make sure I’m getting all the values out in a way it’s readable.
Please have a look at the team page to see a list of everyone who helped me develop and test the script.
Citrix NetScaler documentation script version 1
The Citrix NetScaler platform offers a huge amount of features and a massive amount of configuration possibilities. The flexibility that this gives us also introduces complexity, especially since you configure a service on a Citrix NetScaler once and changes are made only every so often. The starting point for reducing complexity is having a complete and up to date configuration document.
In my experience with customers, especially in enterprise environments, is that documentation is never completely accurate. Even if it would be accurate, what is configured when no configuration is made? Is the default, non-configured setting Enabled or Disabled?
Announcement – Citrix NetScaler documentation script
Today, I’m proud to bring you the Citrix NetScaler documentation script. The script will be released in a joint venture with Carl Webster and is part of his already amazing collection of documentation scripts.
The Citrix NetScaler documentation script wouldn’t be as stable, readable and fast if it wasn’t for Iain Brighton. Iain has been of great help creating functions and performance enhancements in the last few weeks.
If you want to know more keep on reading and I’ll show what we’ve done and how to get the script.
To finish the Powershell Microsoft Active Directory blog post series here is a script which I used for a customer. The script is used for moving the Terminal Server Home Drives of all TS users to a Central Directory. The central directory is based on the ServernameShare%USERNAME% value. The TS Home Drive location was set manually and different location were used. We needed to change this to one single location. Doing this manually would take us months so we need to automate these tasks.
With the introduction of Microsoft App-V v4.5 Microsoft introduced the manifest.xml file. To read more about the manifest file please read this blog post by Rodney Medina MVP on App-V and owner of Softrgidblog.com.
The PowerShell App-V script I will show you today will perform two actions. One is adding the Virtual Application to the App-V client by using the manifest file and the second is performing a full load of the added Virtual Applications.
Here we are with already the latest part in the Powershell and Active Directory blog series. In part 3/4 we worked with getting information from AD Object attributes which are not defined in the schema. In this part we will work on modifying the settings on these attributes.
Back again with a new post in the Powershell and Active Directory series of posts. Remember when I said I will show you how to work with attributes that are not schema attributes? By default you can do a $var.schemaatrributename like $user.name or $user.DistinguishedName. This is not possible for for example the TerminalServiceHomeDrive attribute because this strange enough is not a schema attribute.