Can you use %username% with mapping a drive location with GPO preferences?

First off, I need to point something out. If all of you remember, I was not able to get my Vista to accept my GPO preferences. That is because I needed to install a new set of client-side extensions (CSEs). Once I tried out this problem on my Windows 7 VMs, no problem. You can get the Vista and XP CSEs here:

Windows Vista (x86): http://go.microsoft.com/fwlink/?LinkId=11185

Windows Vista (x64):http://go.microsoft.com/fwlink/?LinkID=111857

Windows XP (x86): http://go.microsoft.com/fwlink/?LinkId=111851

Windows XP (x64): http://go.microsoft.com/fwlink/?LinkId=111862

You will also need to install XMLLite on your XP SP2 or later machines.

http://go.microsoft.com/fwlink/?LinkId=111843

OK, now on to the question. The answer is yes you can. I did find a condition did exist though. The folder with the users name must already exist in share on the network drive you are mapping to. Having to make all those extra folders manually totally goes against my business 2.0 attitude. You could write a script, but that would take effort. In the User preferences of that same GPO, is the Folder option. Using this option I created a new folder at location \\ServerName\ShareName\%UserName%. This time the mapped drive worked.

Comments

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...

Jason Yoder, MCT

Search This Blog