Default Domain Group Policy – What Should Be Configured?

Ever since I started working with Microsoft Active Directory (AD) in July 2001, I have always wondered what should be configured in the Default Domain Group Policy Object (GPO).  I have had a couple of my AD mentors tell me what should be in the Default Domain GPO and I have parroted their recommendation for years now because I agree with them.  I am sure I also read somewhere in the past 12 years the Best Practices for this GPO but just have never been able to find it.  This morning I finally came across an article from Microsoft that clearly states what the Best Practices are for the Default Domain GPO.

Creating a Group Policy using Microsoft PowerShell to Configure the Authoritative Time Server

Creating a Group Policy using Microsoft PowerShell to Configure the Authoritative Time Server

In my 10 Things in AD… presentations, I talk about the importance of having the domain controller that holds the Primary Domain Controller Emulator (PDCe) role configured as the authoritative time source for the forest.  In the PDF that accompanies the presentations, I include a link to a Microsoft Ask the Directory Service Team blog article.  The main problem with that article is there is not enough detail for a lot of people.  Now that Server 2008 and later include PowerShell cmdlets for Group Policy, I thought I would add some detail on creating the Group Policy with PowerShell.

What Happens to the FSMO Roles When the Domain Controller That Holds Them is Demoted

At Briforum 2013 Chicago, after my session on More Things in AD…, someone asked me a question.  The question was “What happens to the FSMO roles when the domain controller that holds them is demoted and is no longer a domain controller?”  The person asking the question was wondering, in an emergency, if a  domain controller (DC) must be quickly demoted and it is unknown if the DC holds any FSMO roles, what happens?  I gave the answer and this article is to show proof my answer was correct because the asker gave me a puzzled look.  Kind of looking at me asking “Are you sure?”

Curious Case FP2

At Synergy 2013, Citrix announced XenApp 6.5 FP2, among other things. I have been looking at this announcement with a kind of special interest, my first curious case, which you…
Documenting a Citrix XenApp 6 Farm with Microsoft PowerShell and Word – Version 3

Documenting a Citrix XenApp 6 Farm with Microsoft PowerShell and Word – Version 3

The script to document a Citrix XenApp 6 farm has proven to be very popular.  I had not always wanted to take the time to create a version of the script that would output to a Microsoft Word document because this script had not been downloaded very much.  But in the last few months, the script has been downloaded several thousands of times.  So I finally decided it was time to create a version of this script that creates a Word document.  Ryan Revord had taken the XenApp 6.0 version of the script and changed it to create a basic Microsoft Word document.  Ryan saved me a lot of work but I wanted improve on the document created by adding a cover page, Table of Contents and footer.  This article will explain the changes to the script to create a Word document.

Documenting a Citrix Provisioning Services Farm with Microsoft PowerShell and Word – Version 2

Documenting a Citrix Provisioning Services Farm with Microsoft PowerShell and Word – Version 2

The script to document a Citrix Provisioning Services (PVS) farm has proven to be very popular.  I have always wanted to take the time to create a version of the script that would output to a Microsoft Word document.  Ryan Revord had taken the XenApp 6.0 script and changed it to create a basic Microsoft Word document.  Ryan saved me a lot of work but I wanted improve on the document created by adding a cover page, Table of Contents and footer.  This article will explain the changes to the script to create a Word document.

The Curious Case of the Slow File Transfer

Let’s get started with a bit of storytelling…

It all started back in at the end of Q3 2011, I was setting up a new Citrix XenApp 6.5 farm for a migration project at the company I was outsourced at. Back then XenApp 6.5 had been released just a few months earlier.

Everything was looking fine and the migration was going smoothly. A few weeks after the last user was migrated we began seeing some strange behavior. Most of that was solved by implementing new Citrix Access Gateway (CAG)  VPX’s, but one issue remained: accessing client drive mappings was extremely slow. To make matters worse, the application being used needed to transfer PDF’s (not even large ones, mostly around 200KB) from client drives to the server. Although the copy eventually would always complete, performance was far less than what is considered acceptable. At the beginning of the weirdness, we did see some rare picadm.sys messages in the event log, but they went away later on.

Using My Citrix XenApp 6.5 PowerShell Documentation Script with Remoting

Using My Citrix XenApp 6.5 PowerShell Documentation Script with Remoting

I received an email from a reader wanting to get my Citrix XenApp 6.5 Farm PowerShell documentation script to work remotely.  After I wrote my original script and article, Citrix updated the XenApp 6.5 PowerShell SDK to support Remoting and a Default Computer Name.  Even using the new –ComputerName parameter, he was still unable to get my script to work.