Change Server Core’s Background

Many Network Administrators prefer to manage the roles and features of Server Core remotely using a graphical interface provided by RSAT. However, you may be at an organization that requires you to either be at a Server Core console, or to Remote Desktop into the server itself. If you have one or two Server Cores, this may not be a big deal. But what if you have 5, 10, or more? While working with a software development company I noticed that the screen background and text color was used to denote the set of code being used. I thought this would be a good idea to flag which Core you were working on.

To change the background color:

Expand HKEY_Current_User\Control Panel\Color.

You will see the Background setting is at 29 95 122. These are the RGB values (Red, Green, Blue) for the background color. The number determines the brightness of each color component for each pixel. Setting a value to 0 turns it off. Setting it to 255 makes it as bright as possible.

Double click Background and enter the values that you want. In this example, I selected 0 22 200.

Click OK

Now close the Registry Editor

Log off and then log back on. You will see the blue is now more intense.

(Before)

(After)

You may want to script this one out if multiple users need to have the same background. If you log in as another user, you will have to repeat this process.

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