I have finally gotten Solid Edge V20 and the Viewer deployed through my organization on Sept. 27th. We deploy SE to over 100 users and the Viewer to over 400 users across about 10 geographic locations in one night over a couple hours. All went well considering this was the first deployment since the new Packaging Specialist started, and it was done on a brand new version of the deployment system we use.
We use Microsoft's System Center Configuration Manager (SCCM) which was just upgraded from SMS 2003. http://www.microsoft.com/systemcenter/configmgr/default.mspx. It allows inventorying PC's throughout the org, as well as pushing software to the PC's. To be able to push the software, you must use the MSI supplied by Solid Edge and repackage it as an EXE. Since the MSI is used, you must also install .NET and ISSCRIPT separately (which can also be added to the EXE package). We found that the ISSCRIPT.MSI must be modified to work with SCCM due to the fact that it installs an IDRIVER.EXE that runs as the interactive user (the logged on user) rather than the launching user (the SCCM client) which causes the SE install to fail under SCCM.
In any case, it all went smoothly, and the only issues we had were due to a couple individuals that just got missed during the upgrade. They were easy to identify since we use Insight and the server would no longer allow them to connect since it had also been upgraded (by hand).
Now all I have for a while are Service Updates, which are really easy.
We use Microsoft's System Center Configuration Manager (SCCM) which was just upgraded from SMS 2003. http://www.microsoft.com/systemcenter/configmgr/default.mspx. It allows inventorying PC's throughout the org, as well as pushing software to the PC's. To be able to push the software, you must use the MSI supplied by Solid Edge and repackage it as an EXE. Since the MSI is used, you must also install .NET and ISSCRIPT separately (which can also be added to the EXE package). We found that the ISSCRIPT.MSI must be modified to work with SCCM due to the fact that it installs an IDRIVER.EXE that runs as the interactive user (the logged on user) rather than the launching user (the SCCM client) which causes the SE install to fail under SCCM.
In any case, it all went smoothly, and the only issues we had were due to a couple individuals that just got missed during the upgrade. They were easy to identify since we use Insight and the server would no longer allow them to connect since it had also been upgraded (by hand).
Now all I have for a while are Service Updates, which are really easy.
Comments
Joan Kuree
I would appreciate if a staff member here at grundey.blogspot.com could post it.
Thanks,
John