Hi all,
I'm having issues installing eViews 11 through SCCM
We currently deploy through GPO using a batch file that registers the installation, however through SCCM it just isn't installing.
Has anyone else done it and can share their configuration of the Application or Package please?
Many thanks
EDIT: To add to this, it sits are 'Downloading (0% Complete)', other applications are fine and install, so I know its no the environment.
eViews installation via SCCM
Moderators: EViews Gareth, EViews Jason, EViews Steve, EViews Moderator
-
- EViews Developer
- Posts: 870
- Joined: Tue Sep 16, 2008 3:50 pm
Re: eViews installation via SCCM
Can you identify at which point in the deployment you are seeing the "Downloading ..." message? The EViews installer doesn't download any components. All the required components are within the installer. This would have me believe there is an issue with the SCCM configuration.
Please email me at jason@eviews.com for a faster response.
Please email me at jason@eviews.com for a faster response.
Re: eViews installation via SCCM
To update:
I've tried running the installer through SCCM with cached content, running it directly from the installer location, running it through Powershell....All sorts.
The installer 'runs' but other than that, it doesn't actually install.
Can anyone who has SCCM, please try and do a test deployment through it? And let me know?
I've tried running the installer through SCCM with cached content, running it directly from the installer location, running it through Powershell....All sorts.
The installer 'runs' but other than that, it doesn't actually install.
Can anyone who has SCCM, please try and do a test deployment through it? And let me know?
Re: eViews installation via SCCM
Further update:
Got it working for the most part along with registering the application, only 'issue' is it leaves the 'Registered' window open which is a bit of a pain.
For anyone that cares, in SCCM:
-Create a Standard Application
-For the 'Deployment Type' under the 'Content' tab, leave it blank
--'Programs' tab I have used the following for 'Install':
--'Programs' tab I have used the following for 'Uninstall':
-'Detection Method' tab I used Registry detection
--Type: Registry
--Hive: HKEY_LOCAL_MACHINE
--Key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
--Value: {8B48E17F-1487-4641-8005-802689C290BC}
--Data Type: String
--Registry Setting must exist
-'User Experience tab' is set to Install for System and Whether or not a user is logged on
Contents of the PowerShell Script:
The 'eViewsSoftwareLocation' in the Script contains the eViews.exe file and the created .ISS files (assuming you are using that)
I could probably try and clear it up a bit more but for whatever reason the original batch file didn't want to work, running it from the local SCCM Cache also wasn't working, hence copying it down locally to execute.
One of the main things stopping my original PowerShell tests from working was the license code in the command line didn't have spaces between the ' - ' characters...Yet when recording the installation it didn't seem to complain about it.
Add logging if required.
Got it working for the most part along with registering the application, only 'issue' is it leaves the 'Registered' window open which is a bit of a pain.
For anyone that cares, in SCCM:
-Create a Standard Application
-For the 'Deployment Type' under the 'Content' tab, leave it blank
--'Programs' tab I have used the following for 'Install':
Code: Select all
powershell.exe -executionpolicy Bypass -file \\ServerFQDN\eViewsSoftwareLocation\InstalleViews.ps1
--'Programs' tab I have used the following for 'Uninstall':
Code: Select all
MsiExec.exe /X{8B48E17F-1487-4641-8005-802689C290BC}
-'Detection Method' tab I used Registry detection
--Type: Registry
--Hive: HKEY_LOCAL_MACHINE
--Key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
--Value: {8B48E17F-1487-4641-8005-802689C290BC}
--Data Type: String
--Registry Setting must exist
-'User Experience tab' is set to Install for System and Whether or not a user is logged on
Contents of the PowerShell Script:
Code: Select all
New-item -Name "TEMPeViewsfiles" -Type Directory -Path "C:\" -Force -Verbose
Start-Sleep -s 5
Copy-Item -Path '\\ServerFQDN\eViewsSoftwareLocation\*' -Destination 'C:\TEMPeViewsfiles\' -Verbose
Start-Sleep -s 5
& 'C:\TEMPeViewsfiles\EViews11Installer(64-bit).exe' -s '-f1C:\TEMPeViewsfiles\eViewsScript.iss'
echo Waiting 60s
Start-Sleep -s 60
Write-Host "Attempting to Register eViews installation"
& 'C:\Program Files\eViews 11\EViews11_x64.exe' /registerlicense "*Insert - License - Code*" "*Joe Bloggs*"
Start-Sleep -s 10
Write-Host "Removing Temporary folder TEMPeViewsFiles from C:"
Remove-Item -path C:\TEMPeViewsfiles -Recurse -Verbose
Write-Host "If 'True' is displayed below, installation was successful"
$TRUE
Write-Host "eViews 11 Installed, check exit code below"
$LASTEXITCODE
The 'eViewsSoftwareLocation' in the Script contains the eViews.exe file and the created .ISS files (assuming you are using that)
I could probably try and clear it up a bit more but for whatever reason the original batch file didn't want to work, running it from the local SCCM Cache also wasn't working, hence copying it down locally to execute.
One of the main things stopping my original PowerShell tests from working was the license code in the command line didn't have spaces between the ' - ' characters...Yet when recording the installation it didn't seem to complain about it.
Add logging if required.
Return to “Installation and Registration”
Who is online
Users browsing this forum: No registered users and 4 guests