I intend to write a How-To for posting in the near future.IBM SPSS Statistics+ AMOS v23 direct download the latest version. To date, we are still continuing to monitor the system for old installs, but for the most part, SCCM did what we needed it to do.
#Spss 23 software install#
We were also able to monitor the progress and check on computers that weren't getting the install or were having issues.
#Spss 23 software software#
To date, the software has been deployed to about 150 staff members, and we were able to remove the old software off of a majority of the machines as well. Overall, when the deployment was working, we were satisfied with the results. The completion metric for the deployment checks for that file to exist and then reports back to the console that the install completed. txt file that was not a normal part of the install. So I decided to have the copy script copy over a dummy. Using the metric of the file date/time wasn't working. The installer failed to move the file because it needed a pre-requisite that the file was in fact modified. When I set up the deployment, everything was smooth, until the deployment started. I set the copy script to copy over the correct deployment file and put it into the Program Files install folder. I called up a xcopy batch script that I had written for a previous deployment in SCCM for our printer installs.
#Spss 23 software how to#
Then the new problem came, how to overwrite the file that was created during the install? Once I modified the file the software was properly licensed and functioning properly. He suggested that I try modifying a file within the installation folder to indicate the licensing type. Within two hours I had a call back from a direct developer. I ended up calling IBM Tech Support to get a ticket opened. It did not appear so, since they used the server licensing model. I went back to the web to look for what to do, figuring other colleges and universities had this problem. I returned from vacation and the need for the new software grew greater. Oh well, have to address when I get back. The worst part was, I was leaving for a week of vacation. The deployment to the labs was scheduled to begin in SCCM within an hour. However, a researcher reported that while the software had licensed, the license had not properly initialized. I was able to successfully deploy the MSI and license, and considered the software was a success since there were no licensing errors. I received the MSI file of the installer, and turned to the internet on how to license the product without having the end user run the activation wizard.
We were more focused on getting SPSS 23 installed, and then handling the uninstalls of 20 and 22 afterward. A good majority of the college was on SPSS 22, which included our six computer labs which hold about 130 computers altogether. I first ran a query to check our Device Collections in System Center to see what versions of SPSS were running across our college. Running a report in SCCM, we discovered we had over 300 machines running older versions of SPSS and needed to get them all updated before the deadline. Each year, the license expires in May with a 30 day grace period. The university uses the Authorized user license model for IBM SPSS instead of a server based model.
0 kommentar(er)
