REM - SET VARIABLE FOR TAG - Rename PDF File and Copy to Folder on Server (L:\Certificates)įor /f "skip=2 tokens=2 delims=," %%i in ('wmic bios get serialnumber /FORMAT:csv') do (set "servicetag=%%i")
%WinDir%\killdisk.exe -ea -em=3 -bm -fp -logpath=l:\ -certpath=x:\ REM Options = -logpath & -certpath (Path were it will save the files) REM Options = -fp (Finger Print = When computer boots, displays when it was wiped) REM Options = -bm (BatchMode = no user interaction) REM Options = -em=3 (US DoD 5220.22-M ECE (7 passes, verify) REM net use l: \\server.fqdn\DiskWipeResults /user:domain\useraccount PASSWORD REMOVED (in TS NOW) REM - MAP NETWORK DRIVE FOR LOGS (Done in TS Step) REM Poor Mans way to pause the script for a short period allowing users to remove the flash Drive. REM FingerPrints Computer with Wipe Results.Įcho Remove Flash Drive From Machine if Present and Close this Box >X:\Windows\FlashWarning.txtĮcho Will Automatically Continue in 30 seconds >X:\Windows\FlashWarning.txtĮcho Flash Drive WILL BE ERASED if NOT Removed >X:\Windows\FlashWarning.txt REM Creates Logs on Network Drive (L:) Which you map in a task sequence step before the Script.
REM Script to Wipe Computer using Active KillDisk to meet State Requirements You’ll then point your TS at this package to grab the files needed. Create a Package in ConfigMgr, (no program), and distribute the contents.Download Scripts here (Contents shown below), and add it to your Package Source.Next we’ll use a Batch File that will run the process and log the results to the server.C:\Program Files\LSoft KillDisk Suite X.X (Use 9.2 and above to support 圆4 Boot Media).Copy the Files from your test machine to your Package Folder.On your Source Server, create a Folder where you will keep the Package Contents.First, install Active Kill Disk and Register it on a Test Computer.Active Kill Disk did offer some additional functionality, so I’ve redone this post with Active Kill Disk for those of you who might want to try this. This is very similar to the sdelete TS I made, however sdelete was not approved by our security team, so I had to reinvent with Active Kill disk. For those of you who have Active Kill Disk, and want to automate it with ConfigMgr, this is how I’ve done it.
0 kommentar(er)
