Skip to main content

TechEd 2012 Day 3

 

Today I spent quite a bit of time with PowerShell V3 and Server 2012.  On the PowerShell front, I got to listen to a team of hard core Group Policy admins give us some tips on better management of our GPOs with PowerShell.  Next up I picked up some tips on increasing the reusability of of my script code.  The final PS session of the day was the most interesting.  We covered a lot of the new features that will make PS work with the cloud and improve its reach to the level that will require every Network Admin to be able to use it.

On the Server side, I sat through the basic principles of implementing the private cloud model.  I did a hands on lab to learn more about the Online Backup Service for Windows Server 2012.  My other lab actually allowed my to take a workgroup client, connect to direct access, and join it to the domain.  This feature has potential where you may have a remote workforce that uses personal devices, but need the manageability of Active Directory. What really caught my eye is the Hyper-V Replica.  Awesome technology.  Imagine providing high availability for your VMs across a site and not on a cluster.  I’m hoping to upgrade a couple of Hyper-V servers in a few weeks just to try this functionality out. 

Tomorrow I’m looking forward to some VDI and Application Virtualization.

Comments

Popular posts from this blog

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.

How to run GPResult on a remote client with PowerShell

In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.

Where did a User’s Account Get Locked Out?

Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction.  The code below is correct.   My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...