Deadline greyed out in WSUS

When approving an update in an environment where the users have control over when an updated is applied, you will often find users who are unwilling to update their clients. Fortunately for the update administrator, Microsoft included a Deadline feature in WSUS to force an update through should a user decide to not bother with the required updates.

When you attempt to approve the update, our group of updates, you may noticed that the Deadline option is not available.

Simply approve the updates normally.

Now, right click the update again and select Approve. This time the Deadline option is available to you.

Setting Deadlines is a good practice in that you will be assured that updates are applied in a reasonable time and users will have the flexibility to delay an update until a time that is convenient to them. Make sure you communicate to your users any implementation of deadlines so they are not caught off guard. A standard period of time will for every deadline should be considered. Should a high priority update be forced on the users with a shorter than usual deadline, make sure you communicate this to them in a timely fashion to help avoid unnecessary interruptions to your organizations workflow.

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.

Sticky Key problem between Windows Server 2012 and LogMeIn

This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this. First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .

Jason Yoder, MCT

Search This Blog