Federal Desktop Core Configuration : Scripted management

Source code for New and Updated Local Group Policy utilities

Aaron Margosis — Tue, 15 Sep 2009 20:35:00 GMT

Visual Studio 2008 source and project files for the new ImportRegPol utility and the updated Set_FDCC_LGPO and Apply_LGPO_Delta utilities for managing Local Group Policy Objects.

Note that these are all now Visual Studio 2008 projects.

New and Updated Local Group Policy Utilities

Aaron Margosis — Tue, 15 Sep 2009 20:30:00 GMT

A customer requested an addition to the local group policy toolset posted on the FDCC blog. While working on the new utility, I needed to upgrade the other two. The full set is attached to this post, with documentation. The source code for all of them is attached to a separate post.

The new utility, ImportRegPol, takes a registry policy file (registry.pol) as input. It can import its contents into the local group policy of the local computer (Computer or User configuration), or simply read it and output Notepad-editable text that can be consumed by Apply_LGPO_Delta.

While working on it, I discovered and corrected subtle shortcomings in Set_FDCC_LGPO and Apply_LGPO_Delta. The main shortcoming had to do with when a value or set of registry policy values were to be deleted: if the settings were present when Set_FDCC_LGPO or Apply_LGPO_Delta was run, they would be deleted, but those deletion “commands” were not saved in the policy store. So, if the settings were to be reintroduced, gpupdate from local policy would not remove them. The new implementations insert the deletion “commands” into the policy store so that they can be applied whenever policy refreshes. This required extending the input file syntax for Apply_LGPO_Delta and the log file output for Set_FDCC_LGPO, both of which have been bumped to v2.0.

While I was at it, I upgraded those utilities to Visual Studio 2008 and enabled ASLR and DEP. In addition, the new version of Apply_LGPO_Delta does not perform an OS check, so it is no longer restricted only to Windows XP and Vista, and will run on any supported version of Windows. Set_FDCC_LGPO still runs only on XP (SP2 or higher) or Vista (RTM or higher), because NIST hasn’t defined FDCC settings for any other versions of Windows.

Here is more information on the new ImportRegPol utility:

ImportRegPol

ImportRegPol is a non-interactive tool that imports the settings from a Registry Policy (registry.pol) file into the Computer or User configuration of the local group policy of the current computer. It can also parse a registry.pol file and produce an editable text file that can be consumed by Apply_LGPO_Delta v2.0.

Introduction

Administrators frequently apply policies by copying registry.pol files into the Group Policy folders. This technique is not supported by Microsoft, and has the unfortunate side effect of destroying any previously existing policies. ImportRegPol reads the reference policy file and uses supported application programming interfaces (APIs) to add settings to local policy.

The format of registry policy files is a documented, binary file format, normally produced by Group Policy editors such as GpEdit.msc. However, there aren’t any good viewers or editors for directly manipulating those files. For this reason, the Apply_LGPO_Delta utility uses a custom, Notepad-editable text file format to define specific changes to apply to local group policy. The log file format produced by ImportRegPol is compatible with Apply_LGPO_Delta v2.0. ImportRegPol can be run in a “parse-only” mode to read a registry.pol file and produce an equivalent input for Apply_LGPO_Delta.

The utility requires administrative rights to import policies, but does not require administrator rights for parse-only mode. Note that the in-use registry.pol files in the GroupPolicy folders can be used for input only in parse-only mode.

Command line syntax and usage:

The ImportRegPol command line syntax is described below. All parameters are case-insensitive. The command line must include -m or -u followed by the absolute or relative path to a registry policy file. All other parameters are optional.

ImportRegPol.exe –m|-u path\registry.pol [/parseOnly] [/log LogFile] [/error ErrorLogFile] [/boot]

-m path\registry.pol   [for Computer configuration] or

-u path\registry.pol   [for User configuration]

                        Path\registry.pol specifies the absolute or relative path to the input registry policy file (which does not need to be named “registry.pol”).

/parseOnly             Reads and validates the input file but does not make changes to local group policy. In conjunction with the /log option, can be used to convert a registry policy file to an input file for Apply_LGPO_Delta.

/log LogFile           Writes detailed results to a log file. If this option is not specified, output is not logged nor displayed. The logged results for the registry policy settings can be used as input for Apply_LGPO_Delta.

/error ErrorLogFile   Writes error information to a log file. If this option is not specified, error information is displayed in a message box dialog.

/boot                  Reboots the computer when done.

This utility is not a console app, so you won’t see a console window appear, and if you start it from a CMD prompt, it will run in the background – CMD won’t wait for it to complete. You can check in TaskMgr to see when it completes. If you want CMD to wait for ImportRegPol to complete, run the utility with "start /wait".

Update: Importing FDCC Group Policy Objects Script Error Resolved

Mandy Tidwell — Wed, 30 Jan 2008 18:23:00 GMT

Author: Joel Yoker, Principal Consultant

A reader recently sent in a question about the GPO Import script and a syntax error they received at line 356. We were able to reproduce the error and it appears to be a "cut and paste" error between the blog post and Notepad. It appears that that carriage returns are added between each line when you cut the text from the blog post in Internet Explorer and paste it directly into Notepad.

Here are the lines that are causing the syntax error:

WScript.Echo "USAGE: cscript.exe //nologo " & WScript.ScriptName & " [/OPTIONS]" & _

VbCrLf & _

Etc...

If you take out the extra lines added during the “cut and paste”, the script runs fine and the "& _" sections of the statement work without the syntax error. Essentially, this block of code needs to look like this:

WScript.Echo "USAGE: cscript.exe //nologo " & WScript.ScriptName & " [/OPTIONS]" & _

VbCrLf & _

VbCrLf & "Script to import FDCC Group Policy Objects (GPO)" & _

VbCrLf & "into a given Active Directory domain. (Note: Requires" & _

Etc...

Script a Custom Power Management Policy

Mandy Tidwell — Wed, 30 Jan 2008 11:33:00 GMT

Author: Paul Fox, Senior Consultant

Scenario: A customer wants a custom power plan for their laptop images. This is a frequent request to meet new Green initiatives in Federal and State governments.

Here are the steps to incorporate a scripted power configuration. The resulting install.cmd can be embedded into a task sequence of Microsoft Deployment Toolkit.

Note: Powercfg.exe is included in Vista, Windows XP SP2 and Windows Server 2003 operating systems.

1. Configure a power plan through the Control Panel -> Power Options UI

2. Determine the GUID of your new power plan

C:\>Powercfg –l

Existing Power Schemes (* Active)

-----------------------------------

Power Scheme GUID: 381b4222-f694-41f0-9685-ff5bb260df2e (Balanced) *

Power Scheme GUID: 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c (High performance)

Power Scheme GUID: a1841308-3541-4fab-bc81-f71556f20b4a (Power saver)

3. Export the power plan

C:\ >powercfg -export <plan>.pow <guid_power_plan>

3. Import the <plan.pow> as an Application into MDT server

4. Create an Install.cmd batch file in notepad and call it as a command line parameter when importing into MDT’s Applications, contents as follows:

Note: In this script powercfg.exe will generate the GUID for the imported power plan. You can also assign a GUID to the power plan by passing it with the import command.

powercfg -import filename [GUID]

filename

Specifies a fully qualified path to a file generated by using the powercfg -export option.

GUID

(optional) Represents the settings loaded into a power scheme. If not supplied, Powercfg will generate and use a new GUID

Modify the import and set active portions with:

Set MYGUID=A6319DFD-EEF4-4644-9D74-9724744F1971

Powercfg.exe –import C:\scheme.pow %MYGUID%

Powercfg.exe –setactive %MYGUID%

If you generate your own GUID it is recommended to us a GUID generating utility (e.g. GUIDGEN included in developer tools)

:: Run Power Management Policy

:: Copy files locally, execute then delete

echo

cd \users\public\downloads

mkdir powermgmt

cd powermgmt

copy "\\<MDT_Server>\distribution$\Applications\Laptop Power Management\*.*" \users\public\downloads\powermgmt

:: Import power plan

c:\windows\system32\powercfg -import C:\users\public\downloads\powermgmt\<plan>.pow

:: Get the GUID of the power plan

c:\windows\system32\powercfg -l > plans.txt

findstr /C "<plan_displayname>" plans.txt > import_plan.txt

:: Set power plan to active

for /F "tokens=4 delims= " %%i in (import_plan.txt) do c:\windows\system32\powercfg -setactive %%i

:: Delete

cd ..

rd /Q /S powermgmt

5. Open Control Panel -> Power Options UI and you will see you custom plan as “active.”

More information about Powercfg.exe can be found at http://technet2.microsoft.com/WindowsVista/en/library/1d58b934-f56a-4796-b2df-7be2eb9c03bc1033.mspx?mfr=true

Importing FDCC Group Policy Objects

David L. Dixon — Sun, 02 Dec 2007 05:55:00 GMT

This post authored by Joel Yoker, a Principal Consultant with Microsoft Federal...

As the February deadline approaches for the implementation of FDCC settings approaches, management of the FDCC Group Policy Objects (GPOs) is a common question Federal IT professionals (IT Pros) have today. FDCC GPO management spans a few areas, including settings review, initial import and linking, and ongoing import and linking. NIST and OMB have taken a very simple, systematic approach by providing exported GPOs with all of the FDCC settings included in them. This removes the need for Federal organizations to go through the previously cumbersome process of reading several hundred pages of settings and definitions and attempting to craft their own GPOs to contain these settings. This significantly reduces the time to implement and human error often associated with implementing any standards in Group Policy. This leaves many IT Pros with the question – How do I get these backed up GPOs into my organization’s Active Directory environment? First, let’s look at what we have.

Currently, when you download the quarterly zip file containing the GPOs (found at http://fdcc.nist.gov/download_fdcc.html), you will notice that there are three categories of FDCC GPOs:

1. Vista GPOs (found in the “\Vista” folder)

2. XP GPOs (found in the “\XP” folder)

3. Common GPOs (found in the “\Both” folder)

Note that in the future as new Windows platforms are released or are deprecated, the platform choices will likely change. The Vista and XP GPOs contain platform specific settings in the following GPOs:

· FDCC <Quarter> <Year> <Platform> Security Settings – Contains low level operating system security settings including User Rights Assignment, local audit policy, security options, services configuration and system ACLs

· FDCC <Quarter> <Year> <Platform>-Specific Additional Settings - Contains additional platform settings such as error reporting

· FDCC <Quarter> <Year> <Platform> Firewall Settings – Contains Domain and standard profile settings for the Windows Firewall

The “Common” GPOs contains settings which apply to either platform in the following GPOs:

· FDCC <Quarter> <Year> IE7 Settings – Contains Internet Explorer settings, including zone information, URL Action settings, etc

· FDCC <Quarter> <Year> Additional Settings - Contains behavioral settings for users and computers

· FDCC <Quarter> <Year> Account Policy – Contains settings such as Password policy, Kerberos policy, etc.

The key concept here is that if you are running one platform within your organization, such as Windows Vista, you would need to import six (6) GPOs in total – The platform specific GPOs and the Common GPOs. If you are running both platforms, you would import all nine (9) GPOs. If you only deploy the platform specific settings, you are only deploying half of the FDCC GPO solution, so take care to understand which GPOs contain which settings for your organization.

Now that we have an understanding of the GPOs included in the FDCC releases, how do we get them into our environment? First, you need to have the Group Policy Management Console (GPMC) running. For Windows Server 2003, the SP1 version of GPMC can be found here: http://www.microsoft.com/downloads/details.aspx?FamilyID=0a6d4c24-8cbd-4b35-9272-dd3cbfc81887&displaylang=en. For Windows Vista RTM and Windows Server 2008, this toolset is included in the platform. Once GPMC is installed, the following simple steps must be followed to import the settings in your environment:

Step 1: Create a new empty GPO

Step 2: Run the GPMC “Import Settings Wizard” by right-clicking the new GPO and selecting “Import Settings…” from the context menu

Step 3: Import the FDCC GPO settings into your new empty GPO

Step 4: Review the imported settings and link the new FDCC GPO accordingly

Note to manage and review the Vista FDDC GPOs in your Windows Server 2003 environment, you will need to establish the ADMX central store in your forest. Steps to do this are outlined here: http://technet2.microsoft.com/WindowsVista/en/library/02633470-396c-4e34-971a-0c5b090dc4fd1033.mspx?mfr=true.

While this procedure is all well and good, it can still be a bit cumbersome to create new GPOs and walk through the wizard over and over again. After all, we have to do this every quarter and depending on how many domains and forests you might have, this can be a daunting task. To help with that, I have written a little script to make it easy to import the FDCC GPOs based on the GPMC scripting examples provided with the GPMC download. It uses the object model from GPMC, so you will still need to ensure that GPMC is installed and working on your platform. The script is pretty simple and requires a single argument – the folder path where you unzipped the FDCC GPOs (specified in the PATH argument).

cscript Import_FDCC_GPO_v1.1.vbs /PATH:”C:\FDCC\FDCC-Q3-2007-Final-GPO-20070730\FDCC Q3 2007 Final GPOs”

The script takes a bit of the guesswork out of importing the FDCC GPOs. First, it enumerates the GPO folders in the FDCC download and allows you to choose which GPO you wish to import. Next, it enumerates the GPOs in the FDCC export and allows you to choose which GPO you wish to import. Once these choices are made, it creates a new empty GPO with a new GUID and the exact name of the FDCC GPO in your environment. After final confirmation, it then imports the settings found in the downloaded FDCC GPOs. An example of the script execution is provided below:

$cscript Import_FDCC_GPO_v1.1.vbs /PATH:"C:\FDCC\FDCC-Q3-2007-Final-GPO-20070730\FDCC Q3 2007 Final GPOs"

The following FDCC GPO Folders are available:

1) Both

2) Vista

3) XP

Enter the number of the FDCC GPO Folder you wish to import: 2

1) FDCC Q3 2007 Vista-Specific Additional Settings

2) FDCC Q3 2007 Vista Security Settings

3) FDCC Q3 2007 Vista Firewall Settings

Enter the number of the FDCC GPO you want to import: 2

STEP 1: Starting GPO Import for FDCC Q3 2007 Vista Security Settings...

Creating GPO...

New GPO created

STEP 2: Align new GPO to FDCC GPO for import ...

Found GPO "FDCC Q3 2007 Vista Security Settings" for importing

STEP 3: Import FDCC GPO? (y or n) y

Importing "FDCC Q3 2007 Vista Security Settings"...

"FDCC Q3 2007 Vista Security Settings" successfully imported.

Would you like to import another FDCC GPO from this path? (y or n)

Based on user input, the script will loop through all of the FDCC GPOs and import them individually. GPOs are not linked since each organization will first need to carefully review the imported settings and each Active Directory environment is obviously different. The script also takes two optional arguments: /? – to display the script help information and /v – to display verbose debugging information while the script executes.

Just as the NIST and OMB exported FDCC GPOs attempt to make implementation and standardization of the settings easier, this script should take some of the bite and guesswork out of importing these GPOs into your organization’s Active Directory environment. I have included the source for the script below. Enjoy and hopefully this helps get your organization headed in the right direction with respect to FDCC!

' =========================================

' = FDCC GPO Import Script

' = Version 1.1

' = Last updated 11:37 AM 12/1/2007

' = Joel Yoker <joely@microsoft.com>

' =========================================

'On error Resume Next

' strDbg toggles display messages on and off (VALUE: 1 = on, 0 = off)

If WScript.Arguments.Named.Exists("V") Then

WScript.Echo vbCrLf & "Debugging ON" & vbCrLf

strDbg = 1

Else

strDbg = 0

End If

' Ensure this script is being run from the command line by calling the IsCScript function

If Not IsCScript() Then

WScript.Echo WScript.ScriptName & " must be run with CScript."

Call DisplayUsage

WScript.Quit 1

End If

' Check and see what arguments were passed and perform the functions required

' per what arguments are passed. Arguments are documented in DisplayUsage subroutine

If WScript.Arguments.Named.Exists("?") Then

Call DisplayUsage

Else

If WScript.Arguments.Named.Exists("PATH") Then

strFDCCGPOPath = WScript.Arguments.Named.Item("PATH")

Call ImportFDCCGPO(strFDCCGPOPath)

Else

wscript.echo "ERROR: /PATH is required" & vbCRLF

Call DisplayUsage

End If

' Subroutines

Sub ImportFDCCGPO(gpoBackupFolderFullPath)

'Create Objects

Set gpm = CreateObject("gpmgmt.gpm")

Set gpmConstants = gpm.GetConstants

Set RootDSE = GetObject("LDAP://RootDSE")

adsiDomain_DN = RootDSE.Get("DefaultNamingContext")

dnsDomain = ConvertToDNS(adsiDomain_DN)

'Create a GPM domain object

set gpmDomain = gpm.GetDomain(dnsDomain,"",gpmConstants.UsePDC)

wscript.echo "The following FDCC GPO Folders are available: "

' Initialize strChoice

strChoice = "y"

' Get the Folder of the GPOs to restore

strFolderPath = gpoBackupFolderFullPath

arrSF = EnumSubFolders(strFolderPath)

For i = 0 to Ubound(arrSF)

rs1 = i + 1 & ") "

rs1 = rs1 & arrSF(i)

WScript.Echo rs1

WScript.Stdout.write vbCrLf & "Enter the number of the FDCC GPO Folder you wish to import: "

rs1 = int(WScript.StdIn.ReadLine)

If strDbg <> 0 Then WScript.Echo

'If strDbg <> 0 Then WScript.Echo "** Choice: " & rs1

restoreGPOFolder_ID = rs1 - 1

'If strDbg <> 0 Then WScript.Echo "** FolderArray number: " & restoreGPOFolder_ID

gpoBackupSubFolder = arrSF(restoreGPOFolder_ID)

If strDbg <> 0 Then WScript.Echo "** Subfolder: " & gpoBackupSubFolder

gpoBackupFolderFullPath = gpoBackupFolderFullPath & "\" & gpoBackupSubFolder

If strDbg <> 0 Then WScript.Echo "** New GPO Backup Path: " & gpoBackupFolderFullPath

If strDbg <> 0 Then WScript.Echo

do while strChoice <> "n"

' Get the GPOs in the folder

set gpmBackupSearchCriteria = gpm.CreateSearchCriteria()

gpmBackupSearchCriteria.Add gpmConstants.SearchPropertyBackupMostRecent, gpmConstants.SearchOPEquals, True

Set gpmBackupDir = gpm.GetBackupDir(gpoBackupFolderFullPath)

Set gpmBackup_List = gpmBackupDir.SearchBackups(gpmBackupSearchCriteria)

For i=1 To gpmBackup_List.Count

With gpmBackup_List.Item(i)

rs = i & ") "

rs = rs & .GPODisplayName

End With

WScript.Echo rs

WScript.Stdout.write vbCrLf & "Enter the number of the FDCC GPO you want to import: "

rs = int(WScript.StdIn.ReadLine)

If rs >= 1 AND rs <= gpmBackup_List.Count Then

restoreGPO_ID = gpmBackup_List.item(rs).ID

set gpmImportGPO = gpmBackupDir.GetBackup(restoreGPO_ID)

importGPODisplayName = gpmImportGPO.GPODisplayName

WScript.Echo vbCrLf & "STEP 1: Starting GPO Import for " & importGPODisplayName & "..."

Else

WScript.Echo vbCrLf & "Please run the script again and select a number in the displayed range."

WScript.Quit()

End If

If strDbg <> 0 Then WScript.Echo "Importing into " & adsiDomain_DN

' Create a new GPO with the name of the GPO selected

wscript.echo " Creating GPO..."

strNewGPODisplayName = importGPODisplayName

Set objNewGPO = gpmDomain.CreateGPO()

objNewGPO.DisplayName = strNewGPODisplayName

If strDbg <> 0 Then wscript.echo vbCrLf

If strDbg <> 0 Then wscript.echo "----CREATING NEW GPO----"

If strDbg <> 0 Then wscript.echo "--Name: " & objNewGPO.DisplayName

If strDbg <> 0 Then wscript.echo "--GUID: " & objNewGPO.ID

If strDbg <> 0 Then wscript.echo "--Path: " & objNewGPO.Path

If strDbg <> 0 Then wscript.echo "------------------------"

wscript.echo " New GPO created"

'Search the production domain to verify that a GPO of the same name exists

WScript.Echo vbCrLf & "STEP 2: Align new GPO to FDCC GPO for import ..."

set gpmGPOSearchCriteria = gpm.CreateSearchCriteria()

'gpmGPOSearchCriteria.Add gpmConstants.SearchPropertyGPODisplayName, gpmConstants.SearchOPContains, cstr(importGPODisplayName)

gpmGPOSearchCriteria.Add gpmConstants.SearchPropertyGPOID, gpmConstants.SearchOpEquals, objNewGPO.ID

set gpmProductionGPOCollection = gpmDomain.SearchGPOs(gpmGPOSearchCriteria)

If gpmProductionGPOCollection.count = 1 Then

WScript.Echo " Found GPO " & Chr(34) & objNewGPO.DisplayName & Chr(34) & " for importing"

For Each item In gpmProductionGPOCollection

If strDbg <> 0 Then wscript.echo vbCrLf

If strDbg <> 0 Then wscript.echo "----FOUND GPO----"

If strDbg <> 0 Then wscript.echo "--GUID: " & item.ID

If strDbg <> 0 Then wscript.echo "-----------------"

set gpmProductionGPO = item

Else

wscript.echo " Unable to find " & objNewGPO.DisplayName & " in " & adsiDomain_DN

wscript.quit

End If

WScript.StdOut.Write vbCrLf & "STEP 3: Import FDCC GPO? (y or n) "

rs = wscript.StdIn.ReadLine

If StrComp(rs,"y",vbTextCompare) = 0 Then

WScript.Echo " Importing " & Chr(34) & objNewGPO.DisplayName & Chr(34) & "..."

Set gpmResult = gpmProductionGPO.Import(0,gpmImportGPO)

Set gpmResult_Status = gpmResult.Status

If gpmResult_Status.count <> 0 Then

For i=1 to gpmResult_Status.Count

WScript.Echo gpmResult_Status.Item(i).Message

gpmResult.OverallStatus()

Else

WScript.Echo " " & Chr(34) & objNewGPO.DisplayName & Chr(34) & " successfully imported."

End If

Else

WScript.Echo " Operation aborted. Exiting..."

End If

' Prompt to see if we need to loop again

WScript.StdOut.Write vbCrLf & "Would you like to import another FDCC GPO from this path? (y or n) "

strChoice = wscript.StdIn.ReadLine

wscript.echo vbCrLf

Loop

wscript.echo "Exiting FDCC GPO import script"

End Sub

Sub DisplayUsage()

' Documents every named argument and how the script is to be used

WScript.Echo "USAGE: cscript.exe //nologo " & WScript.ScriptName & " [/OPTIONS]" & _

VbCrLf & _

VbCrLf & "Script to import FDCC Group Policy Objects (GPO)" & _

VbCrLf & "into a given Active Directory domain. (Note: Requires" & _

VbCrLf & "administrative rights to perform the action)" & _

VbCrLf & _

VbCrLf & "Enumerates FDCC GPO backups, creates new GPO with " & _

VbCrLf & "same name, and imports FDCC settings into new GPO" & _

VbCrLf & _

VbCrLf & "Switches:" & _

VbCrLf & "/PATH (required) - The path of the FDCC GPOs" & _

VbCrLf & _

VbCrLf & "Examples: " & _

VbCrLf & "To specify that FDCC GPO subfolders were extracted" & _

VbCrLf & "to a folder called C:\FDCC type the following:" & _

VbCrLf & _

VbCrLf & "cscript " & WScript.ScriptName & " /PATH:C:\FDCC\FDCC-Q3-2007-Final-GPO-20070730\FDCC Q3 2007 Final GPOs" & _

VbCrLf & _

VbCrLf

wscript.quit

End Sub

' Functions

Function ConvertToDNS(distinguishedName)

' ConvertToDNS - Converts the DN of a domain to a FQDN

'Skip past the first "DC=" in the DN

initialStrip = Mid(distinguishedName,4)

'Replace the remaining typeful prefixes with periods

rs = Replace(initialSTrip,",dc=",".",1,-1,1)

'Return the FQDN

ConvertToDNS = rs

End Function

Function EnumSubFolders(strFolderPath)

Set objFSO = CreateObject("Scripting.FileSystemObject")

Set objFolder = objFSO.GetFolder(strFolderPath)

Set objSubFolder = objFolder.SubFolders

intSize = 0

For Each folder in objSubFolder

ReDim Preserve arrSubFolders(intSize)

arrSubFolders(intSize) = folder.name

intSize = intSize + 1

EnumSubFolders = arrSubFolders

End Function

Function IsCScript()

' This function returns whether the script is being run from cscript (command line)

Dim objRegExp

Set objRegExp = New RegExp

objRegExp.IgnoreCase = True

objRegExp.Pattern = "cscript.exe$"

IsCScript = objRegExp.Test(WScript.FullName)

Set objRegExp = Nothing

End Function