KIP Print

For those using KIP plotters, and the new KIP Print software. Here is a helpful heads up on how to silently deploy this out to your clients.

Start by running through the installation on a client machine. Add your plotters, and pen settings, etc. After you have one client machine setup with all of your customizations.

On 64bit clients, navigate into - C:\ProgramData\IPS\IPSPRINT

Copy the IPSPrint.ini file into your working folder for your deployment script. Next copy out your pen setting file, from - C:\ProgramData\IPS\IPSPRINT\PENS out.

Now that you have the customized settings file, along with your pen settings, you can setup your silent deployment package.

Start by installing the product with defaults silenty using;
call "\\serveranme\_SilentDeploy\files\KIPPrint_v.7.4.502.exe" /s /v/qn

For those running a mixed architecture environment, you will want to check the OS architecture. We can by using the following to check for x64.
"%PROCESSOR_ARCHITECTURE%"=="AMD64"

If you are running a mixed archtitecture, you will want to push the custom settings out to the correct location on the x86 clients. Below is an example of a full script. You will see the OS arch check, then the custom settings *.ini file being copied into the correct location.

call "\\serveranme\_SilentDeploy\_SilentDeploy\files\KIPPrint_v.7.4.502.exe" /s /v/qn

if not "%PROCESSOR_ARCHITECTURE%"=="AMD64" goto x86

xcopy "\\serveranme\_SilentDeploy\files\nj\default.pen" c:\ProgramData\IPS\IPSPRINT\PENS /e /q /y

xcopy "\\serveranme\_SilentDeploy\files\nj\IPSPrint.ini" c:\ProgramData\IPS\IPSPRINT /e /q /y

goto pen

:x86

xcopy "\\serveranme\_SilentDeploy\files\nj\default.pen" "%allusersprofile%\Application Data\IPS\IPSPRINT\PENS" /e /q /y

xcopy "\\serveranme\_SilentDeploy\files\nj\x86\IPSPrint.ini" "%allusersprofile%\Application Data\IPS\IPSPRINT" /e /q /y

:pen

If you do not want to overwrite the default files, you can use the rename command to rename the files prior to overwriting them.

 

That's all there is to preparing kipprint for silent deployment to multiple machines. This can be packaged and deployed through SCCM also, if your organization uses SCCM.

MS updates and ESRI ArcGIS - be aware!

Critical Information Regarding Microsoft Update and ArcGIS

A recent Microsoft update (deployed as KB 2732673, KB 2775511, or KB 2824408) may result in data corruption when using ArcGIS on a Windows 7 system and writing data to remote data storage on a Windows Vista, 7, 2008/2008 R2, or 2012 system. This data corruption appears as truncation of a write request and has shown up in file geodatabases and shapefiles. Microsoft has acknowledged the problem, identified the affected component as RDBSS.sys, and provided further details. Esri and Microsoft are working closely to understand what has changed in the RDBSS.sys component and how to resolve the problem. Microsoft recommends not installing the above-referenced updates. How Microsoft Made These Updates Available KB 2732673 and KB 2824408 are hotfixes to address specific issues. The KB 2775511 update is a cumulative update that is available exclusively at http://catalog.update.microsoft.com. Because it is available only through the Windows update catalog, the KB 2775511 update is not considered a security update by Microsoft and is not being deployed broadly. What You Need to Do If you have not yet installed the patches listed above, do not install them, per Microsoft's recommendation. If you have installed the patches listed above, Microsoft recommends uninstalling them until a solution is found.  See Esri Knowledge Base article 41119 for further information and updates. See Microsoft Knowledge Base articles for more information on Microsoft updates: http://support.microsoft.com/kb/2732673 http://support.microsoft.com/kb/2775511 http://support.microsoft.com/kb/2824408