Jump to content


Search the Community

Showing results for tags 'custom hook tsconfig .vbs'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Cloud
    • Azure
    • Microsoft Intune
    • Office 365
    • Windows 365
  • General Stuff
    • General Chat
    • Events
    • Site News
    • Official Forum Supporters
    • Windows News
    • Suggestion box
    • Jobs
  • MDT, SMS, SCCM, Current Branch &Technical Preview
    • How do I ?
    • Microsoft Deployment Toolkit (MDT)
    • SMS 2003
    • Configuration Manager 2007
    • Configuration Manager 2012
    • System Center Configuration Manager (Current Branch)
    • Packaging
    • scripting
    • Endpoint Protection
  • Windows Client
    • how do I ?
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows Vista
    • Windows XP
    • windows screenshots
  • Windows Server
    • Windows Server General
    • Active Directory
    • Microsoft SQL Server
    • System Center Operations Manager
    • KMS
    • Windows Deployment Services
    • NAP
    • Failover Clustering
    • PKI
    • Hyper V
    • Exchange
    • IIS/apache/web server
    • System Center Data Protection Manager
    • System Center Service Manager
    • System Center App Controller
    • System Center Virtual Machine Manager
    • System Center Orchestrator
    • Lync
    • Application Virtualization
    • Sharepoint
    • WSUS

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Location


Interests

Found 1 result

  1. Ok, following the instructions exactly on the guide located here: http://blogs.technet...lone-media.aspx my tsconfig.ini reads as: [CustomHook] CommandLine=”cscript.exe X:\ExpiredUFDCheck.vbs” the .vbs at the root of my boot image is as follows: ' // *************************************************************************** ' // ' // File: ExpiredUFDCheck.vbs ' // ' // Version: 1.0 ' // ' // Purpose: Check to see if stand-alone media is expired ' // ' // Usage: cscript ExpiredUFDCheck.vbs ' // ' // *************************************************************************** On Error Resume Next ' // --------------------------------------------------------------------- ' // Find the environment variable %configpath% for location of UFD ' // --------------------------------------------------------------------- 'Set objShell = CreateObject("WScript.Shell") 'Set objExecObject = objShell.Exec("%comspec% /c echo %configpath%") 'configPath1 = objExecObject.StdOut.ReadAll() 'configPath = Mid(configPath1, 1, Len(configPath1) -2) ' // ----------------------------------------------------------------------------------------- ' // Find the environment variable %TEMP% for location of tool files (e.g. shutdown.exe) ' // ----------------------------------------------------------------------------------------- Set objShell = CreateObject("WScript.Shell") Set objExecObject = objShell.Exec("%comspec% /c echo %temp%") temp = objExecObject.StdOut.ReadAll() tempdir = Mid(temp, 1, Len(temp) -2) ' // --------------------------- ' // Find driver letter for UFD '// ---------------------------- Set FSO = CreateObject("Scripting.FileSystemObject") Set Drives = FSO.Drives For Each DiskDrive In Drives If DiskDrive.DriveType = "1" Then USBPath = DiskDrive.Path End If Next ' // ----------------------------------------------------------------- ' // Query WMI for creation date of the Policy.xml file on the UFD ' // ----------------------------------------------------------------- strComputer = "." Set objWMIService = GetObject("winmgmts:" & "{impersonationLevel=impersonate}!\\" & strComputer & "\root\cimv2") ' // ---------------------------- ' // Media Check - Policy.xml ' // ---------------------------- Set colFiles = objWMIService.ExecQuery("Select * From CIM_DataFile Where Name = '" & USBPath & "\\SMS\\Data\\Policy.xml'") ' // ----------------------------------------- ' // Set the date 3 months ago from today ' // ----------------------------------------- dt3MonthsAgo = DateAdd("m", -3, Now) ' // ----------------------------------------------------------------------------------------------------------- ' // If the Policy.xml file creation date is less than the date 3 months ago from today, it is an expired UFD. ' // ----------------------------------------------------------------------------------------------------------- For Each objFile in colFiles dtCreationDate = WMIDateStringToDate(objFile.CreationDate) dtEndDate = DateAdd("m", 3, dtCreationDate) If dtCreationDate < dt3MonthsAgo then Set WshShell = CreateObject("WScript.Shell") Command = TEMPDIR & "\scripts\Shutdown.exe /s /t 0" MsgBox "This task sequence expired on " & dtEndDate, vbMsgBoxSetForeground, "Expired Task Sequence" Set oExec = WshShell.Exec(Command) Else WScript.Quit(1) End If Next ' // ----------------------------------------------------------------------------------------- ' // Converting the WMI date query response to a simple date format. (e.g. 09/21/2010) ' // ----------------------------------------------------------------------------------------- Function WMIDateStringToDate(dtmInstallDate) WMIDateStringToDate = CDate(Mid(dtmInstallDate, 5, 2) & "/" & Mid(dtmInstallDate, 7, 2) & "/" & Left(dtmInstallDate, 4) & " " & Mid(dtmInstallDate, 9, 2) & ":" & Mid(dtmInstallDate, 11, 2) & ":" & Mid(dtmInstallDate, 13, 2)) End Function I set the bios to have the following date: 7/18/13 when I boot from the standalone usb key, I get this: on pressing "ok" the machine is SUPPOSED to shut down. Instead the expiration notice disappears and I can hit "next to execute the task sequence. The workstation is not shutting down when "ok" is pressed. When I change the Bios to make the Task Sequence valid, it throws an 8005 error becasue of "WScript.Quit(1)" at the end of the script. Thank you for the help in advance!!!!
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.