Hi, I have a script that I'm currently using in order to Uninstall SAS for Windows 9.3. To start, you have to stop the following services: I'm using a CMD file by the way. sc stop "SAS PC Files Server" sc stop "SAS Document Conversion" The next step is to delete the following font files as everytime I tried to uninstall SAS manually, this files are "Read Only" and the uninstall can't proceed if the files are still there, so I delete them. if exist "%ProgramFiles%\SAS 9.3\ReportFontsforClients\9.3\sasmono.ttf" del /Q "%ProgramFiles%\SAS 9.3\ReportFontsforClients\9.3\sasmono.ttf" if exist "%ProgramFiles%\SAS 9.3\ReportFontsforClients\9.3\sasmonob.ttf" del /Q "%ProgramFiles%\SAS 9.3\ReportFontsforClients\9.3\sasmonob.ttf" Then, I uninstall the application "SAS Document Conversion" using the following command line: "C:\Program Files\SAS 9.3\SASTextAnalyticsDocumentConversion\1.21\Uninstall.exe" /S The fun part is to Uninstall SAS 9.3 using the command line: "C:\Program Files\SAS 9.3\SASDeploymentManager\9.3\sasdm.exe -uninstall -wait -quiet -noreboot -provision -responsefile "C:\Program Files\SAS 9.3\response.uninstall.properties" -datalocation "C:\Logs\sasuninstall" -loglevel 2 To really automate a silent Uninstall the "-responsefile" should be there, otherwise you can have a command line that will popup the SASDM screen to start the Manual Uninstall to chose your components: "C:\Program Files\SAS 9.3\SASDeploymentManager\9.3\sasdm.exe -uninstall -wait -noreboot -provision -datalocation "C:\Logs\sasuninstall" -loglevel 2 Why you should use a response file? Well, SAS 9.3 has 200 or more components depending on what components you have chosen and many of them will be called during the installation process, so hundreds of entries will be made on the registry God knows where exactly. It will be hard to get all of them and spect that your machine will behave correctly after removing them manually, is a no go for a business perspective. This app should be stable and also the machine where you are installing it. Well, once the SASDM has been completed all the tasks, now you have to clean up the following folders that SASDM leaves behind: if exist "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\SAS\" rd /q /s "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\SAS\" if exist "C:\Program Files\SAS 9.3\" rd /q /s "C:\Program Files\SAS 9.3" if exist "C:\ProgramData\SAS\" rd /q /s "C:\ProgramData\SAS" And, finally the following regkeys: reg delete "HKEY_LOCAL_MACHINE\SOFTWARE\SAS Institute Inc." /f reg delete "HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SAS Institute Inc." /f I've been using this method since 2014, and I've delivered SAS 9.3 to more than 500 machines, but they have the same License and components installed. We're using SCCM 2012, and the process is really smooth if the machines are in good shape. Otherwise SAS 9.3 will go mad with your registry and you risk to have many machines to be sent to be reimaged. Hope this could help anybody ! Joel E.
... View more