Please do not modify the name of the file, because this name is what PrimalScript and PowerShell Studio will use to find that remote machine on a network. The file is named with your computers name and a. The default location for this is your desktop. Once finished, you should see something like this:Ĭlick on the “Save” button to save the newly built cache files to an export file. Once you do that the status changes to show this:ĭepending on platform and PowerShell versions installed this process takes a few minutes to complete. If you leave the CacheExport tool on your server, you can do this later on as needed if you install new versions of any module or additional modules or products on that server. Click on “Rebuild all cache files” if anything is not present. Most likely you see a status as shown above. Please make sure to allow it to run, otherwise this just won’t work. As this requires elevation you may get the corresponding prompt. Unless you have anything else SAPIEN already installed on that machine, CacheExport will launch RegisterControls.exe. We designed this process to be installation free, so anything that needs to happen will be done by the utility.
Otherwise all extracted files are marked as originating from another machine and you get a few extra dialog to acknowledge. Copy the zip file to the server before unpacking. We are using a Windows 2008R2 server as an example here. Unless you really want to use it there the CacheExport tool is all you need. Note that it is not required to install the full product on your server. So just take that file, copy it to a flash drive, on a network share or wherever you need it to be so you can access it from your server. It’s called CacheExport.zip and you can find that in the products installation folder under “Redistributables”. To make this as simple as possible, we packed all the files required into a zip file.
As a first step you need to get the PowerShell cache information our products use from your target machine. PrimalScript and SAPIEN PowerShell Studio support a mechanism which allows you to do that. Just as an example, try installing Microsoft SharePoint 2010 modules on your 32 bit Windows XP/Vista/7/8 machine.
One of the challenges you face while developing any PowerShell script is that modules that reside on your target platform are not available on your local computer.
0 kommentar(er)
