Skip to main content

Auto Updates on Server Core and scregedit.wsf

By
This is somewhat interesting. Auto updates are not running when server core is installed. The command line to do this is a bit different. Not all tasks can be managed on Server Core via the command line or an MMC. For those tasks, Microsoft provided a script called SCRegEdit.WSF. Automatic updates is one of those things this script takes care of. The script also:

· Enable automatic updates
· Enable Remote Desktop for Administration
· Enable Terminal Server clients on previous versions of Windows to connect to a server running a Server Core installation
· Configure DNS SRV record weight and priority
· Manage IPsec Monitor remotely

You will want to add enabling Automatic Updates to your deployment procedure for Server Core.
Below are the command lines for each of these tasks.
Enable automatic updates
· Enable automatic updates
- Cscript c:\Windows\system32\scregedit.wsf /AU 4
· Disable automatic updates
- Cscript c:\Windows\system32\scregedit.esf /AU 1
· Options 2 and 3 are not available because the pop up balloon is not part of Server Core.

Enable Remote Desktop for Administrators
· Enable Remote Deskop from Windows Vista/2008:
o Cscript %windir%\system32\SCRegEdit.wsf /ar 0
· Enable Remote Desktop from Windows XP/2003 and earlier
- Cscript %windir%\system32\SCRegEdit.wsf /ar 0
- Cscript %windir%\system32\SCRegEdit.wsf /cs 0 and press Enter.

Enable Terminal Server clients on previous versions of Windows to connect to a server running a Server Core installation

· Enable
- cscript c:\windows\system32\scregedit.wsf /cs 0
· Disable
- cscript c:\windows\system32\scregedit.wsf /cs 1

Enable Terminal Server clients on Windows Vista/2008 to connect to a server running a Server Core installation

· Enable
- cscript c:\windows\system32\scregedit.wsf /ar 0
· Disable
- cscript c:\windows\system32\scregedit.wsf /ar 1

Configure DNS SRV record priority
· Enable
- cscript c:\windows\system32\scregedit.wsf /dp xxx
- xxx can be 0 through 65535
- Microsoft recommends 200
Configure DNS SRV record weight
· Enable
- cscript c:\windows\system32\scregedit.wsf /dw xxx
- xxx can be 0 through 65535
- Microsoft recommends 200

Manage IPsec Monitor remotely
· Enable
- cscript c:\windows\system32\scregedit.wsf /im 0
· Disable
- cscript c:\windows\system32\scregedit.wsf /im 1

Comments

Post a Comment

Popular posts from this blog

How to list all the AD LDS instances on a server

By
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.
Post a Comment
Read more

How to run GPResult on a remote client with PowerShell

By
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.
Post a Comment
Read more

Where did a User’s Account Get Locked Out?

By
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...
18 comments
Read more