User downloads and installs it, but the software won't work until (s)he reboots. You put your eval version on the web for users to download it. Have a nice think performing a reboot when reboot is necessary is a good idea in general. : You guys can't ever get things right the first time. Well, it Ummm, let me send someone over to have a look at your computer. : I called you this morning, and you told me my connection to such-and-such would work by now. Try in 30 minutes - you should be able to connect. : I need to be able to connect to so-and-so system. Why would you want to auto restart anyway? In most cases they wont need it after first boot and you're just making them spend more time waiting for the computer to boot.Ĭorrect, in most cases they won't. ![]() Does that mean it installs fine when I deploy it using the User scope? I tried this and it didn't work either.Īs for restart, I think I'll let the user choose that. I noticed the quoted text specifically says this is nessesary when "configured for the Computer scope". Is there some way to do this using Orca? I don't have any of those package programs you need to pay for. Isn't that half the point of msi files? To deploy them? ![]() You'd think if that was nessesary in order to deploy it, they would've made the msi that way to begin with. Tell the repackaged MSI to download then execute the vpnclient_setup.msi from local machine. Embed vpnclient_setup.msi into your custom MSI package.Ģ. Repackage the MSI package using AdminStudio from InstallShield or Package Studio from WISE.ġ. Windows software deployment of the VPN client MSI to an active directory client via a Group Policy Object configured for the Computer scope. Copy the installation files to a local drive and restart the install. Error 28006: Trying to install the VPN Client from a network drive momentarily disconnects network drives and can cause the installation to fail. An error is logged in the event log on the client computer: When using Active Directory and Group Policy to automate the VPN client install on domain computers, the install fails. Unable to install vpn client via Active Directory Msiexec /i "\\srv-file\Z\Software\Internet and Networking\Cisco VPN 5.x Client\vpnclient_setup.msi" transforms=\\srv-file\Z\Software\Internet and Networking\Cisco VPN 5.x Client\vpnclient_wonetworkcheck.mstīelow is KB article from the Cisco web site. As long as its eventually installed, I have that much less work to do on new machines as well, and I can tell users without it to just reboot while connected here instead of them needing to wait for me to install for them, ect. I realize this wont install for remote computers until they boot while on the network. Again I ask myself, why does it let me install from a network location manually, but not via group policy? Why would it let me install by double clicking from a network location, but not via group policy from a network location? I am also able to install using the transform command line you suggested from a network location, but unable to push out the msi and mst file via group policy. When I drop that line and save the msi, it lets me install from a network location by manually double clicking the msi file located at the same place (on the network). I thought that was what this posting was about, trying to get Cisco VPN to install automatically, probrably from a network location. So, what do you do in a situation like this other than try and repackage? Use VBScript? Shoot yourself? That's about where I'm at. I've run into this paradox before but I had forgotten. The problem is that I end up trying to run msiexec ( to install the vpn client ) while msiexec is still running ( the msiexec thread that launched the script and is waiting for the script to finish before it exits ). Then I made a msi file to call my batch file ( because this is being deployed via Active Directory so there must be an MSI ). I tested the script and the script works. Start /wait msiexec /i c:\vpntemp\vpnclient_setup.msi -qn Xcopy \\server\software\ciscov~1\vpnclient_setup.msi c:\vpntemp /y Xcopy \\server\software\ciscov~1\*.pcf c:\vpntemp /y So, my brilliant solution was to write a script ( batch file ) to make a temporary directory on the workstation, copy over the install files, launch the install program, then remove teh temporary directory. ![]() The installation of the Cisco VPN client causes a network disconnect during the install, so installing it FROM a network drive or share fails.
0 Comments
Leave a Reply. |